Harald Alvestrand — IETF/IESG Chair
Jun-ichiro Itojun Hagino
Mike St. Johns
Bert Wijnen — Liaison from the IESG
Vern Paxson — IRTF Chair
Joyce Reynolds — Liaison from the RFC Editor
NEXT SCHEDULED MEETING
- Roll call, Agenda Bash and Previous Minutes
- Review of Action Items
- Review of Documents
- IAB Liaison Reports
- Updates from IETF Liaisons
- Review of recent questions to the IAB
- IAB plans for Vienna IETF meeting
- Other Business
- Nomcom Confirmation Discussion
0. Roll call, Agenda Bash and Previous Minutes
Minutes of the 13 May Teleconference were considered. An amendment was proposed and the amended minutes will be circulated to the IAB for adoption.
1. Review of Action Items
Regarding the drafting work on IAB Considerations on Discovery Mechanisms and IPv6, the IAB considered this in further detail. It was noted that there is a concept of ‘liveness’ in connecting a server to a network and have it be discovered by potential clients in a timely manner. There is no single clear solution here, and while anycast and multicast represent feasible mechanisms, both approaches have drawbacks, particularly in larger environments. There is also a need for some associated directory structure, and while the DNS or SLPv2 can be used in such a mode, again there are issues here. The DNS approach is one taken from the DNS SD rendezvous efforts, and it is considered reasonable to write down the issues that were exposed in considering this approach. A related issue is the level of IP configuration support that is provided from the link layer, where reliance on link level responses seriously impairs roaming and impairs interoperability. There are also issues that have been noted with DHCP level discovery and there are concerns about the security associated with this form of approach. These areas will be considered at length in the proposed IAB considerations document.
2. Review of Documents
3. IAB Liaison Reports
Rob Austein:, Bert Wijnen:
- The IETF Secretariat is attempting to streamline various routine interactions, for example, the Do-Not-Publish and No-Problem responses from IESG to the RFC Editor in response to queries from the RFC Editor about individual submissions.
- The General Area now has a directorate.
- Question of whether to ban an individual from posting to the IPR WG list: this is understood to be the first time that the RFC 2418 3.2 procedure for blocking WG mailing list postings from an individual has ever been invoked (in particular, the part that requires explicit approval of the whole IESG prior to taking such an action).
- Leslie Daigle and Harald Alvestrand visited the RFC Editor office on Friday, June 27th. A productive all day meeting was held with the RFC Editor staff.
- A Peer-to-Peer RG has been chartered.
- The Reliable Multicast RG has closed.
- There will be an informal BOF in Vienna regarding possibly forming an RG on the topic of IP Mobility.
Lynn St Amour:
- The next ISOC Board meeting will be held on the 12th and 13th July, 2003 in Vienna, Austria Austria Center Vienna. ISOC Board meetings are open to the Public. All are welcome.
- ITU’s Internet Policy Manual. The ITU-T has released a call for support for an
Internet Policy Manual that the ITU intends to draft. The ISOC Board is very concerned about this and will be preparing a response/plan of action at its upcoming Board meeting.
WSIS. ISOC submitted statement of concern re WSIS to WSIS and ITU (abstract below), two main concerns: WSIS remains too broad and un- focused to be really helpful and we are concerned by statements in the draft documents that imply the need for new, intergovernmental organizations to “manage” the Internet. The ISOC Board continues to discuss ways to influence WSIS and we are encouraging all our chapters to work this actively with their local governments. Full text at http://www.isoc.org/isoc/conferences/wsis/comments.shtml.
Statement of Concern
With just over six months left before the Summit, the Internet Society is concerned that there is not yet a well-defined list of specific actions and initiatives that might be endorsed at the Summit. The draft Plan of Action and Declaration of Principles sets out many worthy goals, but does not make clear how those goals can and will be achieved. In addition, the draft documents attempt to address almost every aspect of the Information Society as well and many issues are not directly related to information technology or telecommunications. We would hope that the Summit would endorse a much shorter document that instead focuses on a few specific areas and have the assembled governments commit to specific actions that they will take to foster the continued growth of the Internet and the Information Society. In particular, we would recommend attention be focused on how governments can foster competition in the IT and telecommunications marketplace, how they can promote the use of open standards and open source software, how they can ensure free expression in cyberspace, and how they can foster public sector applications of the Internet, such as e-government, online education, and e-health.
“Managing the Internet”:
We are very concerned by statements in the draft documents that imply the need for new, intergovernmental organizations to “manage” the Internet. In particular, proposals to replace ICANN and create a new mechanism for managing root servers, domain names and IP addresses is unnecessary, will lead to significant disruption, and is unlikely to succeed. The unprecedented growth and innovation that we have seen in the Internet sector is due in large part to the lack of regulation and constraints on technology development. In addition, the processes employed have been open, democratic and inclusive and it’s hard to see how these could be improved by a new intergovernmental body. In 1985, no one could have predicted or planned the explosive growth of the Internet and the World Wide Web. Today, as the Grid, Web services, and new wireless Internet technologies promise to again transform the way we gather, process, and share information, we should continue to support the decentralized, bottom-up innovation that has made the Internet the powerful tool it is today. Non-governmental organizations such as the Internet Engineering Task Force, ICANN, and the World Wide Web Consortium, have proven very flexible and nimble and have enabled the global Internet community to quickly find consensus on how best to adopt and use new Internet technologies. Individual governments can and should support such organizations and ensure the full participation of their citizens in their activities.
4. Updates from IETF Liaisons
draft on the ‘how to process a liaison statement.
ICANN Board Liaison
5. Review of recent questions to the IAB
SNMP protocol action
David Waitzman has requested the IAB’s view on a proposal that advocates moving all SNMP documents and MIB documents to HISTORIC, NOT RECOMMENDED status as of June 2006.
It was noted in the IAB discussion of this proposal that SNMP V1 and SNMP V2c documents are already HISTORIC status, and that current IETF efforts in the network management area are concentrated on configuration-related issues. It was also noted that there is no clear candidate technology that could replace SNMP V3 at present that has been introduced into the IETF for consideration with respect to standardization, this was not a clear outcome of the 2002 IAB workshop on Network Management, and that such a protocol action regarding SNMP and MIBs would have to be based on a consensus view of the IETF, consistent with the definition of “historic” as contained in RFC2026.. These views will be conveyed in response.
ENUM Instructions to RIPE NCC
The RIPE NCC has informed the IAB that the wording in the ENUM
request template describing the three different role contacts ( sections 2.2. to 2.4.) could be confusing or even misleading. The RIPC NCC has proposed a clearer wording for these roles. Patrik Fältström will review the proposal and recommend an IAB response.
DNS URI question
The IAB discussed the DNS URI proposal in response to a query from Paul Vixie on the IAB’s input regarding the use of a hostpart in the DNS URI specification. The issues identified include consideration of the transitive properties of DNS queries, and whether the outcomes of a resolution of a URI should be dependant on explicit reference to a particular query point. It was decided to consider this further at the next IAB meeting before drafting any response to the query.
IPv6.ARPA delegation Instructions regarding 2002::/16
In accordance with the IANA Considerations of RFC 3152, the IAB approved the request to delegate 188.8.131.52.IP6.ARPA to the Regional Internet Registries. An IAB instruction to this effect will be sent to the IANA.
6. IAB plans for Vienna IETF meeting
The IAB reviewed the schedule for IETF-57. The IETF Liaison to the ICANN Board will be invited to the IAB meeting with the ICANN CEO. The IAB will undertake a technical review of the IMPP documents at its technical meeting on Tuesday if time and resources permit.
7. Other Business
7.1 Affiliation Listings for IAB members
The IAB decided to support an expanded member listing page that details each IAB member’s affiliation, and also allow a brief CV and a pointer to a personal web page. The Executive Director was tasked to implement this addition to the IAB web pages.
7.2 Followup: Liaison appointments to Non-International Bodies
No further considerations were raised by the IESG in respect to this proposal. The IAB will publish this as an adopted procedure on the IAB web page.
8. Nomcom Confirmation Discussion
The IAB met in closed session, without the IETF Chair, to consider the NomCom nomination for the IESG Internet Area mid-term vacancy.
The IAB decided to publish a statement regarding information requested from the Nomcom in making a nomination. The IAB position is that in making its confirming decision the IAB desires the submission of material from the Nomcom that includes the Nomcom’s view of the qualifications required for the vacant position, and the Nomcom’s summary of the candidate’s qualifications that the Nomcom found has relevant to support their nomination.
ACTIONS and DOCUMENTS
- IETF Protocol Parameter Registration
Leslie Daigle, Harald Alvestrand
Status: Followup actions after meeting with US DoC
- A registry selection criteria and conditions document is to be drafted (gih)
- DNS and IDN Document
Rob Austein, Patrik Fältström, Geoff Huston
Status: Coordinate IETF document between Ads and WGs
- Document on Internet Identity realms being drafted. A second document to answer the specific issues about IDN may be needed.
- IAB input to Security Architecture
James Kempf, Charlie Kaufman
Status: Prepare classification matrix to identify particular issues relating to the interaction of their WG activities and security considerations
- Questionnaire to be posted to wg chairs list
- IAB Workshop on DOS Attacks
Status: Initial scoping activity: a taxonomy paper on the various forms of attack. Also look at the role of a workshop and the potential players.
- Initial draft prepared for IAB review
- Address Architecture
Status: Circulate Harald’s formulation of the constrained address architecture issue to the IAB
- This is the proposal for an open IAB meeting / possible BOF at the next IETF mtg.
- Close this following the Open Meeting, and open up followup actions
- WG Status
Leslie Daigle, All
Status: Provide the IAB with periodic summaries of the current status of those working groups that they actively follow.
- Leslie to provide some guidelines for this activity
- IAB Open Meeting
Leslie Daigle, Geoff Huston
Status: Schedule IAB Open Meeting on IETF Agenda
- Geoff: prepare introduction
- Response to SNMP query
Status: Draft response to query regarding IAB position on proposal to assign all SNMP and MIB documents to Historic
- Response to ENUM query
Status: Draft response to RIPE NCC proposal to alter the definition of role contacts in the ENUM registry
- IANA instruction for IP6.ARPA
Status: Draft instructions to IANA concerning instruction to delegate 184.108.40.206.IP6.ARPA to the RIRs
- IAB Member details web page
Status: Add an expanded members web page with affiliations, etc, to the IAB web site.
- Liaisons Procedure
Status: Post the adopted procedure on the IAB web page
- Notification Mechanisms
Leslie Daigle, Ted Hardie, James Kempf
Status: James Kempf to draft a note on the topic of architectural issues relating to notification mechanisms. Circulate the note to Lisa Dusseault, Ted Hardie, Leslie Daigle and Ned Freed. Need to look at Lemonade WG work again as Lemonade was the prime motivator here.
- Note to be filed with IAB Documents
- RFC Editor Charter
Status: Circulate draft RFC editor Charter to IAB
- ARIN Teredo Allocation Request
Status: Draft a note indicating hat the IAB would be opposed to the RIR allocation for Teredo, and pass it to the IESG for review before responding to the RIRs
- IAB liaison procedure
Status: Pass a copy of the procedure to the IESG for information
- Security considerations, including common security attacks
Status: RFC Editor (submitted 13-Feb)
- (current) AUTH
- Security Mechanisms for the Internet
draft-iab-secmech-02.txtCharlie Kaufman, Steve Bellovin
- (current) incorporate comment into final draft (03)
- (next) Submikt 03 to RFC Editor
- A survey of Authentication Mechanisms
- (current) 01 draft being prepared, with expansion of current [TODO] sections of the -00 draft
- Internet Architecture and End-to-End
draft-iab-e2e-futures-03.txtJames Kempf, Rob Austein
- (current) final review prior to IETF Call
- (next) IETF Call for Input
- Internationalized Resource Identifiers
- (current) Leslie to review the draft
- Service Identification in packets
draft-iab-service-considerations-01.txtMike St Johns, Geoff Huston
- (current) 02 draft being prepared with call for input comments included
- (next) submit 02 to RFC Editor
- Transport Controls for VOIP
draft-iab-congestion-00.txtSally Floyd, James Kempf
- (current) review and discussion
- IANA Definition
- (current) revised per IAB comments
- (next) Review document progress in August
- ISOC Trustee Appointment Process
Status: IAB review
- (current) IETF Call for Input
- IAB Research Agenda
draft-iab-research-funding-01.txtSally Floyd, Vern Paxson, Ran Atkinson, Mike St Johns, John Crowcroft
- (current) Document the need for funding for further research for the Internet, including documenting important topics for research.
- (next) The document under development covers the need for research in general and identifies specific areas of research.
- (next) Sally – feedback appreciate – there are as yet unwritten sections and assistance will be coopted
- (next) Bernard – wireless research is underfunded – will send mail
- (next) Sally – there is a commented out section referencing Rob on DNS
- (next) Patrik to write section on issues around address scoping and related routing and application interactions
- (next) Review progress in August
- IAB Overview
Status: IAB review – proposed updates requested
- (current) ekr to consider undertaking editor role.
- IAB Considerations on Discovery Mechanisms and IPv6
Bernard Aboba, James Kempf
- (current) Redraft as a descriptive framework plus individual proposed contributions as desired
- IAB Research Agenda – Operational Areas
Geoff Huston, Rob Austein, James Kempf
- (current) Document the need for funding for further research for the Internet, including documenting important topics for research relating to operational activities
- (next) Document focusing on operational concerns.
The IAB Web page is at http://www.iab.org