Re: Last Call: draft-gont-intarea-obsolete-eid-option-01.txt (Obsoleting the Endpoint Identifier (EID) Option) to Proposed Standard
On 10/05/2012 03:58 PM, Noel Chiappa wrote: Have the original authors [sic - JNC] been contacted? Alas, the author of the ID which defines this option, Charlie Lynn, is no longer with us: http://www.postel.org/pipermail/end2end-interest/2004-June/004195.html I can probably give as good a judgement on it as anyone, though. FWIW, being unaware of this, I tried to contact Charles Lynn a couple of years ago when I was going through each of the then-currently-specified IPv6 options. I seem to recall checking with Noel regarding whether EID had ever been deployed (but my memory may certainly fail). Looking at the ID defining the option: http://ana-3.lcs.mit.edu/~jnc/nimrod/eidoption.txt (dunno why the obsoletion ID doesn't give a URL for it), Yep, it should. -- for some reason the I-D is referencing only http://ana-3.lcs.mit.edu/~jnc/nimrod/ but not the specific I-D that specified the option. -- I will add a specific reference in the next rev of the I-D - thanks! the obsoletion ID is slightly inaccurate: it wasn't just meant to be used with the Nimrod routing architecture, but rather the endpoint name format supported by that option is totally general, allowing any endpoint name format to be used. Please let me know if you have any suggestions on how to tweak the text to improve this. Thanks! Best regards, -- Fernando Gont e-mail: ferna...@gont.com.ar || fg...@si6networks.com PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
Re: Last Call: draft-gont-intarea-obsolete-eid-option-01.txt (Obsoleting the Endpoint Identifier (EID) Option) to Proposed Standard
On Oct 4, 2012, at 20:23, The IESG iesg-secret...@ietf.org wrote: The IESG has received a request from an individual submitter to consider the following document: - 'Obsoleting the Endpoint Identifier (EID) Option' draft-gont-intarea-obsolete-eid-option-01.txt as Proposed Standard Have the original authors been contacted? Also, I see no reason why this RFC would need to be standards track. Lars smime.p7s Description: S/MIME cryptographic signature
Re: Last Call: draft-gont-intarea-obsolete-eid-option-01.txt (Obsoleting the Endpoint Identifier (EID) Option) to Proposed Standard
From: Eggert, Lars l...@netapp.com The IESG has received a request from an individual submitter to consider the following document: - 'Obsoleting the Endpoint Identifier (EID) Option' draft-gont-intarea-obsolete-eid-option-01.txt as Proposed Standard Have the original authors [sic - JNC] been contacted? Alas, the author of the ID which defines this option, Charlie Lynn, is no longer with us: http://www.postel.org/pipermail/end2end-interest/2004-June/004195.html I can probably give as good a judgement on it as anyone, though. Looking at the ID defining the option: http://ana-3.lcs.mit.edu/~jnc/nimrod/eidoption.txt (dunno why the obsoletion ID doesn't give a URL for it), the obsoletion ID is slightly inaccurate: it wasn't just meant to be used with the Nimrod routing architecture, but rather the endpoint name format supported by that option is totally general, allowing any endpoint name format to be used. (In fact, one large faction of the Namespace Research Group wanted to use a format for endpoint names which would have made use of the 'variable length' capability of this option, but I digress..) I don't see any particular reason to not obsolete this option, though; no recent proposal uses a separate header option for endpoint identification in IPv6. Recent work on adding endpoint names has either i) used part of the IPv6 address as an EID (e.g. ILNP), or interpreted the existing IPvN address as an EID (e.g. LISP). And, in any event, if we decide we need it, we can always bring it back (according to the obsoletion ID, it's merely to be marked obsolete, not re-assigned). Noel
Last Call: draft-gont-intarea-obsolete-eid-option-01.txt (Obsoleting the Endpoint Identifier (EID) Option) to Proposed Standard
The IESG has received a request from an individual submitter to consider the following document: - 'Obsoleting the Endpoint Identifier (EID) Option' draft-gont-intarea-obsolete-eid-option-01.txt as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the i...@ietf.org mailing lists by 2012-11-01. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document formally deprecates the IPv6 Endpoint Identification (EID) option (hex value 0x8a), thus cleaning up the corresponding IANA registry, and possibly serving as a basis for providing advice about the filtering of packets containing this option. The file can be obtained via http://datatracker.ietf.org/doc/draft-gont-intarea-obsolete-eid-option/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-gont-intarea-obsolete-eid-option/ballot/ No IPR declarations have been submitted directly on this I-D.
