13 May 2003, 4:00 pm – 6:00 pm US EST
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
- Rollcall, Agenda Bash and Previous Minutes
- Review of Action Items
- Review of Documents
- IAB Liaison Reports
- Updates from IETF Liaisons
- Proposal: Process for relationships with non-international bodies
- IAB plans for Vienna IETF meeting
- Review of recent and planned IAB activities
- Other Business
Rollcall, Agenda Bash and Previous Minutes
Minutes of the 8 April Teleconference were approved.
1. Review of Action Items
2. Review of Documents
3. IAB Liaison Reports
The IESG liaison to the IAB is Bert Wijnen.
An experiment has commenced in the area of provision of RT (a ticketing system) support to any WG that wants it. Levels of interest in this activity are being assessed.
The IESG is also reviewing aspects of the WG decision making process in the area of means of resolving potential deadlock situations.
The IRTF chair reported receiving a number of concerns and complaints about the state of ASRG, and is looking into modifying the RG management to address them.
“Do Not Publish” (DNP)
There has recently been a discussion between the IESG and RFC Editor on the issue of when to publish documents as RFCs that have been rejected by working groups. There is a concern that document authors will take rejected drafts from the working groups and submit them directly to the RFC Editor as individual submissions. A question has arisen whether these documents should be published before the working group publishes its output.
The RFC Editor has proposed to the IESG that the IESG may request that publication of an individual submission may be delayed by six months by sending RFC Editor a “Do Not Publish” (DNP) note containing a description of the risks posed by the document. (The RFC Editor would like to understand the specifics of the request.)
The author will receive a note including the IESG DNP message and an explanation that the draft may be resubmitted in six months. The RFC Editor feels that a timed delay is important since some working groups do not complete their work. When the draft is re-submitted, the IESG may request one additional six month delay if there is sufficient reason to believe the working group will deliver it’s output in that time.
This discussion is still in progress.
The IESG’s I-D nits document
The IESG is reviewing the I-D nits document. The IESG requested that the RFC Editor provide a review and feedback. Bert Wijnen has been sorting the nits into three categories:
- “clerical” nits which will result in a wg draft being rejected before AD review. E.g., missing security considerations.
- Nits which the AD review should flag and reject before IESG review.
- Nits which can be resolved somewhat painlessly by the RFC Editor (e.g., excessive line length in body text).
The RFC Editor conveyed to Bert Wijnen that it is willing and able to handle all the formatting and editorial nits. The RFC Editor doe not feel that documents should be held up overly long for reasons of formatting, especially since the RFC Editor will be fixing the formatting, anyway. The RFC Editor agrees that the best thing for all involved is to ensure that the semantic nits (e.g., abstract, normative/informative references, security considerations, etc.) are best addressed early on to ensure accurate review and group consensus. The RFC Editor also agrees that it is reasonable to require splitting references between normative and informative on all IESG-reviewed Informational documents.
In all cases, WG chairs and authors will be expected to have their documents nit-free before submission. The objective of this activity is to decide when to bounce a document that fails a nit check. The desire is to set a fairly high bar with the WG chairs to improve the quality of documents hitting the IESG.
New RFC Series/Category and Documented Appeals Process for DNPs
The RFC Editor is currently discussing with the IESG the possibility of a new series/category for working group Informational documents such as requirements, architecture, and framework documents, and a documented appeals process for DNPs.
ISOC has been following up on Item # 8 from the IAB Meetings during the March 2003 IETF concerning the US Homeland Security Office activities
Meetings have taken place with representative of this office, as well as comparable meetings with officials within Europe.
4. Updates from IETF Liaisons
The RSSAC has been discussing “glue” RRset maintenance and policy issues (mostly about how active a role ICANN should play about making sure that the glue RRset stays in sync with the authoritative RRset in the child zone. The questions include: how much checking should be undertaken?, Should there be tracking of changes to the authoritative RRset that the child zone admin hasn’t directly reported to ICANN?
5. Proposal: Process for relationships with non-international bodies
6. IAB plans for Vienna IETF meeting
The IAB decided to invite the CEO of ICANN to meet with the IAB on Thursday of the IETF week.
The IAB considered a proposal to hold an open meeting to undertake enumeration of the class of operational scenarios for which there is perceived to be a role for scoped, or otherwise constrained address architectures. At this stage the proposed outputs from this activity are intended to be an enumeration of the issues raised in the open meeting, followed by a subsequent architectural analysis of these issues as a means of assisting the IETF to progress with the topic of various forms of constrained address architecture proposals.
7. Review of recent and planned IAB activities
The mid-month IAB action item review has not been effective, and this will not be continued. The mid-month informal telechats were considered to be effective, and further calls will be scheduled using a SIP-based conferencing system.
IAB members were requested to provide periodic summaries of the current status and major issues being faced by those working groups in which they were actively tracking.
8. Other Business
ACTIONS and DOCUMENTS
- 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. Lisa Dusseault to assist.
- James to review and revise initial draft provided by Lisa
- IETF Protocol Parameter Registration
Leslie Daigle, Harald Alvestrand
Status: Followup actions after meeting with US DoC
- DNS and IDN Document
Rob Austein, Patrik Faltstrom
Status: Coordinate IETF document between Ads and WGs
- Revise as per drafted introduction and framework
- IAB Workshops
Status: Revisit workshops, and reconsider this along the lines of approach, topic, and logistics.
- DOS attack workshop (below).
- Other topics/approaches to consider?
- IAB input to Security Architecture
James Kempf, Charlie Kaufman
Status: Generate a survey for the WG chairs to come up with a classification matrix to identify particular issues relating to the interaction of their WG activities and security considerations
- Prepare classification matrix
- 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.
- Taxonomy document being prepared
- Address Architecture
Status: Circulate Harald’s formulation of the constrained address architecture issue to the IAB
- WG Status
Status: Provide the IAB with periodic summaries of the current status of those working groups that they actively follow.
- Response to ICANN VGRS proposal
Status: Draft response to ICANN referencing IETF role and document preparation
- ICANN CRADA report
Status: Note to ICANN from the IAB (as TLG) indicating that the IAB understands that a CRADA report on the root nameservers has been prepared, and that the IAB is under the impression that there is a substantive component of the report devoted to technical aspects of this activity. The IAB is willing to undertake a technical review of this report if so desired by ICANN under the terms of the activities encompassed by the technical liaison activity with ICANN
- IAB Conf calls using SIP
Status: Get in touch with the SIP gateway provider to see if IAB requirements can be met for a trial call in May
Mike St Johns
Status: Contact Ran to followup on briefing proposal.
Status: Contact HSSP chair and nominate a member / observer to the Panel Steering Committee
- Ran Aktinson has been nominated as an IETF Liaison
- Global Grid Forum Liaison
Status: Contact GGF chair and discuss potential liaison arrangements
- proposed liaison arrangements
- V6 Address Architecture
Status: Draft a note asking the RIRs what amount of consideration has taken place with respect to the PA / PI space issues with respect to IPv6
- note ready to send
- Security considerations, including common security attacks
Status: RFC Editor (submitted 13-Feb – Author 48 hours)
- Security Mechanisms for the Internet
draft-iab-secmech-02.txtCharlie Kaufman, Steve Bellovin
- (current) draft published
- (next) incorporate comment into final draft
- A survey of Authentication Mechanisms
- (current) Complete template section
- (next) IETF call for input
- Internet Architecture and End-to-End
draft-iab-e2e-futures-02.txtJames Kempf, Rob Austein
- (current) send pointer to the draft to the e2e interest list
- Report of IAB Network Management Workshop
Status: RFC Editor – submitted 16 April
- Internationalized Resource Identifiers
- (current) Leslie to review the draft
- Service Identification in packets
draft-iab-service-considerations-00.txtMike St Johns, Geoff Huston
- (current) draft published
- (next) revise as per comment received
- Transport Controls for VOIP
Sally Floyd, James Kempf
- (current) Document the use of transport control and congestion detection and avoidance for VOIP applications
- (next) Sally – drafting
- IANA Definition
- (current) IAB review of -02 draft
- (next) publish 02 draft
- ISOC Trustee Appointment Process
- (current) review and revise following completion of 2003 election process
- IAB Research Agenda
Sally 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 appreciated – 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
- IAB Overview
Status: IAB review – proposed updates requested
- (current) active
- IAB Considerations on Discovery Mechanisms and IPv6
Bernard Aboba, James Kempf
- (current) circulate to IAB of a draft indicating progress to date with this document
- 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