 |
 |
 |
Minutes of the 10 February teleconference were approved.
Minutes of the IAB meetings at IETF 59 were approved.
It was noted that Bernard Aboba has agreed to serve on the ICANN Nominations Committee for 2004 as a liaison from the IAB.
IESG
Rob Austein:, Bert Wijnen:
IESG had a retreat in April. A report has been passed to the IAB.
Harald, with feedback from the IESG, has prepared an ID to describe how IESG will handle individual submissions that come in via RFC-Editor. The RFC-Editor is agreeable to this approach. Next step is IETF Last Call for comment/input. I-D name is draft-iesg-rfced-documents-01.txt
IESG has a small team (Bert and Bill) to prioritize a number of ID_tracker wish list items. These, once implemented by secretariat, will improve the usability of the tool.
IESG is reviewing old I-Ds that have been in RFC-Editor queue for a long time to see what we can do to unlock them.
IESG is working on a revised IDnits web page. Current draft is at: http://www.ops.ietf.org/IDnits.html. IAB comments are welcome.
RFC Editor
Joyce Reynolds:
The RFC Editor funding arrangements from ISOC for 2004 has been completed.
The RFC Editor has added tags to allow direct links into the RFC Editor queue page. E.g., http://www.rfc-editor.org/queue.html#draft-ietf-ips-fcovertcpip
The RFC Editor Errata page is now linked from the search engine.
The IESG's suggestion to add a tag for working groups to our RFC INDEX file is in process. We asked the IETF Secretariat to provide WG history from their databases.
We have received a first cut at working group to RFC mapping from the Secretariat, and are working to improve format.
We are working with Marshall Rose with XML for RFCs to create the desired format we require.
RFC Editor has started a discussion on maintaining rfc-info service, for email retrieval of RFCs, on the rfc-interest mail list.
IRTF
Vern Paxson:
The SIREN RG has closed.
Chartering a HIP-related RG is imminent.
Reviewing a request to charter an "Internet information retrieval service" RG.
ISOC
Lynn St Amour:
As part of effort to get RFC Editor contract formally extended through 2004, ISOC with IAB involvement, re-iterated their financial support to RFC Editor for 2004 (approx. $575K). Contract negotiations completed, paperwork being finalized.
ISOC Board of Trustee Elections complete, announcements scheduled for April 15th, 2004.
ISOC, IETF, IAB, IPv6 etc. all participated in the UN session on Internet Governance held at the end of March.
Administrative Restructuring
Leslie Daigle:
The current activity is to take what was heard in Seoul at IETF59 and revise the drafts accordingly. The intention is to provide revised drafts by 3rd May to allow for review by the IESG, IAB and the ISOC Board of Trustees.
ITU-T
Scott Bradner:
GSC-9: Hiroshi Esaki will be attending for the IETF.
W3C
Leslie Daigle:
The IAB agreed to allow the IAB comments on the W3C Technical Architecture Group's report to be published in the W3C forums.
ICANN - TLG
Geoff Huston, Rob Austein:
ICANN - Liaison to the Board
John Klensin:
John Klensin has alerted the IAB that he has been offered some technical consulting work for ICANN. The proposed activity is clarification to ICANN staff in getting across IDN technology and associated practical considerations.
The IAB discussed this and determined this does not appear to represent a conflict of interest with John's role as IAB liaison to the ICANN Board.
The IAB considered further actions in the IDN space, and noted that while there is considerable activity at present there are still some issues in the use of such names. Patrik Faltstrom and John Klensin will consider if there is some further matters that would benefit from an IAB considerations document on aspects of this topic.
The IAB considered an ICANN request relating to the preparation of an informational document on the forms of checks an application should undertake on the validity of names in various contexts. The IAB concluded that this topic was already considered in RFC 3696, and that there was nothing further the IAB wished to add to the material contained in that document. This conclusion is to be
IEEE 802
Bernard Aboba:
The IAB was informed of a number of specific action items coming out of the IEEE 802/IETF Liaison meetings held earlier in the year.
An Area Director query relating to waiving of the fee for allocation of an EtherType in an IETF standards track document was considered. IEEE 802 has a procedure by which this fee may be waived on request.
RSSAC
Rob Austein:
No items reported
Thomas Narten reported on the results of an initial analysis of document progress based on the RFC Editor Queue data that related to the processing rate of documents in the IANA state.
The IAB noted the concerns expressed in the report, and considered ways in which the IANA could be assisted to address this matter of a recent drop in effective throughput. It was noted that while the throughput in measuring the time taken to create new protocol parameter registries could be objectively measured through the regular examination of the document status within the publication process. Similar measurements of the responsiveness of IANA in responding to requests relating to registration of protocol parameters within established registries was not readily available to the IAB. It was noted that some form of ticketing support may be useful in ensuring that all IANA requests are responded to promptly.
The IAB decided to commence publication of the IANA document queue status on a monthly basis, listing the documents where IANA actions have been required. Other approaches to assist in addressing this issue of an expanding backlog of IANA actions will be explored with IANA staff.
The IAN considered a proposal to host a messaging workshop. The IAB agreed to proceed with the arrangements, noting that the objective here is intended to generate some additional perspectives on the architecture of messaging applications, and is not intended to be focused on reworking current IETF and IRTF activities.
The IAB considered a number of candidate areas for further study including:
- The future of congestion control when deployed in conjunction with real time traffic
- How do we evolve the Internet routing architecture?
- DoS resistant architectures.
- The tension between auto-configuration and security.
- Living with NATs.
- The Hostile Internet
- ID / Locator split in the architecture
- The role and use of identity realms
To review these and other relevant technical topics in more detail, the IAB agreed to have monthly technical discussions (IAB Tech telechats). The first will focus on the topic of NATs.
The IAB considered the implications of the IESG draft concerning the proposed IESG handling of individual submissions to the RFC Editor.
The IAB had a number of concerns relating to the potential shift in the preferred method of RFC publication from the "IETF" publication track to an individual submission track, procedures and accountabilities in the area of technical review of individual submissions
It was noted that this was within the scope of the IETF Newtrk WG, and IAB consideration was directed towards any additional actions that were appropriate at this point in time.
An "IAB Considerations" section will be considered for inclusion in the IESG draft on this topic.
- Use of protocol parameter values by CARP / VRRP
The IAB was informed of a potential clash of protocol parameter values in an open source implementation of CARP. More information will be sought from the open source developers on this subject.
- Telechat time
IAB telechats will commence at 2100 UTC (i.e. 5pm US EDT) during the southern hemisphere winter.
These minutes were prepared by Geoff Huston; comments should be sent to iab-execd@iab.org. An online copy of these and other minutes is available at: http://www.iab.org/documents/IABmins/
The IAB Web page is at http://www.iab.org
|
Index of IAB Meeting Minutes |
|