1 / 7

Codepoints in I-Ds

Codepoints in I-Ds. Adrian Farrel IETF-79, Beijing, November 2010. What Happens?. An I-D is stable People want to implement Code points are “suggested” in the I-D. What Could Possibly Go Wrong?. Implementations are done Interop tests are held Product is released Product is shipped

matteo
Download Presentation

Codepoints in I-Ds

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. Codepoints in I-Ds Adrian Farrel IETF-79, Beijing, November 2010 IETF-79 Beijing November 2010

  2. What Happens? • An I-D is stable • People want to implement • Code points are “suggested” in the I-D IETF-79 Beijing November 2010

  3. What Could Possibly Go Wrong? • Implementations are done • Interop tests are held • Product is released • Product is shipped • Function is deployed • RFC publication process goes ahead • IANA allocates different codepoints • For example, because of another allocation IETF-79 Beijing November 2010

  4. A Recent Example from MPLS • Not singling anyone out for punishment • Two mature drafts using the same registry • One draft requests early allocation (RFC 4020) • IANA allocates code points • Other draft is older • Contains “suggested” codepoints • It has been deployed using those codepoints • There is an overlap with the values already allocated • In theory… • You implement and deploy an I-D at your own risk IETF-79 Beijing November 2010

  5. How is this Unpicked? • Fortunately only one of the I-Ds is implemented and deployed • Fortunately we caught this early • Will need to work with IANA • Simply sort out the codepoints and re-register IETF-79 Beijing November 2010

  6. What Should Happen? • Do not identify unregistered codepoints in I-Ds • There is never any need • Interop tests can use private values • I-Ds should say “TBD” and leave it to IANA • Do early allocation where needed • RFC 4020 (and draft-iana-rfc4020bis coming soon) • It is simple (but it does expire) • Actions • Authors and WG chairs check now • Do you have codepoints in your I-Ds? • Either remove them or get early allocation • Do it soon • WG chairs (or secretaries) • Check IANA sections in all new I-Ds IETF-79 Beijing November 2010

  7. What Else Could We Do? • WGs could maintain a web page of “very early temporary allocations” • For example • http://trac.tools.ietf.org/wg/ccamp/trac/wiki • Such codepoints are NOT official allocations • You cannot rely on them • But this does help avoid confusion and overlap IETF-79 Beijing November 2010

More Related