1 / 14

IAB Report

IETF 76 November 12, 2009 Olaf M. Kolkman. IAB Report. About the IAB. IAB Charter RFC2850 http://www.iab.org/about/overview.html IAB Homepage http://www.iab.org/ Documents http://www.iab.org/documents/selected-iab-documents.html Minutes http://www.iab.org/documents/iabmins/indext.html

taariq
Download Presentation

IAB Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IETF 76 November 12, 2009 Olaf M. Kolkman IAB Report

  2. About the IAB • IAB Charter RFC2850http://www.iab.org/about/overview.html • IAB Homepagehttp://www.iab.org/ • Documentshttp://www.iab.org/documents/selected-iab-documents.html • Minuteshttp://www.iab.org/documents/iabmins/indext.html • Goal: no more than 1 or 2 meetings behind • Batch of minutes posted this week • Correspondencehttp://www.iab.org/documents/correspondence/index.html • The IAB

  3. Document ActivityDocuments published • RFC5620: RFC Editor Model (Version 1) AUTH48 • RFC5694: Peer-to-Peer (P2P) Architecture: Definition, Taxonomies, Examples, and Applicability • RFC 5704: Uncoordinated Protocol Development Considered Harmful

  4. Documents ActivityOngoing • IAB thoughts on IPv6 Network Address Translation • draft-iab-ipv6-nat-02Comments from the call for comments have been incorporated. • Submission to the RFC editor pending • IAB Thoughts on Encodings for Internationalized Domain Names • draft-iab-idn-encoding-01 Inspiration for today's plenary

  5. Document Activitywhat happened to? • On RFC Streams Headers and Boilerplates • draft-iab-streams-headers-boilerplates-08 MISSREF: draft-housley-iesg-rfc3932bis • Defining the Role and Function of IETF Protocol Parameter Registry Operators • draft-iab-iana-04(update imminent) • Evolution of the IP model • draft-iab-ip-model-evolution-01(update imminent)

  6. Signing .ARPA • We received an implementation plan from IANA on the way forward w.r.t. signing .arpa. • Two step approach: • Temporary setup: quarter 4, 2009 • Integration in the architecture developed to maintain the root: quarter 2, 2010 • IAB has responded positively to that plan

  7. Inter Organizational:appointments • Thomas Narten is reappointed as the IETF liaison to the ICANN BoT • Fred Baker appointed as liaison to the Smart Grid Interoperability Panel • Henk Uijterwaal appointed the IETF-selected member on the 2010 ICANN NomCom

  8. Inter organizational:IAB commentary • Commented on White Paper: Modernising ICT Standardisation in the EU - The Way Forward (White Paper) • http://www.iab.org/documents/correspondence/2009-08-28-IAB-EuroICT-Reply-final.pdf • Provided comments to the ICANN CEO and ICANN BoT on the “Scaling the Root Study” • http://www.iab.org/documents/correspondence/2009-10-14-ICANN-Scaling-the-Root.html

  9. Organizational:RFC Editor Model (recap) • Model described in RFC5620 • RFC Editor model implementation responsibilities: • IAOC responsible for selecting RFC Production Center and RFC Publisher • IAB responsible for appointing • RFC Series Advisory Group (RSAG) done • An ad hoc advisory committee assists during the selection of the RSE and ISE (ACEF) done • The RFC Series Editor (RSE) • The Independent Submissions Editor (ISE)

  10. RFC Editor implementation status I • IAOC awarded RFC publisher and RFC Production Center contracts to AMS • Sandy Ginoza and Alice Hagens are core members of the production center crew. • Independent Submission Editor • Significant delays because of focus on the RSE function • Interviews are being held by the ACEF

  11. RFC Editor Implementation status II • RFC Series Editor function • Call for nominations: July 8 • Close nominations: August 15 • Advice from the ACEF: • No suitable match between function, expectation and candidates • Advice to seek somebody to manage the transition • IAB defined the transitional RSE and calls for candidates

  12. RFC Editor Implementation Status III • What is different with respect to previously • Less uncertainty about the state of the Production and Publication functions • More focus on transitional aspects: • refine the role of RSE after initial transition • possibly propose modifications to the RFC Editor Model • different type of commitment • No disclosure of names of candidates

  13. RFC Editor Implementation status IV • Call for nominations is now open evaluation will start November 23 • IAB believes this approach is in line with RFC5620 and general community consensus. • Community feedback is welcomed and will be taken into account • ISI and Bob Braden are willing to extend their current contract and consult during the transition • More information: http://www.ietf.org/mail-archive/web/ietf-announce/current/msg06709.html http://www.iab.org/documents/correspondence/2009-11-04-Transitional-RSE-SOW.pdf

  14. Worth Mentioning • No Appeals

More Related