Re: [tcpm] Auth Option obsoleting MD5 Option in IANA registry

I was the one who probably raised this issue earlier and the meaning of
the term "obseletes" and we had use that for a lack of a better term.
TCP-MD5 will continue to exist and we will have to support it as long as
it exists.

That said my real question is : What is the purpose of IANA noting that
this "kind" is obsolete? They cannot allocate to another option, is it
pure book keeping activity?

-Anantha

> -----Original Message-----
> From: tcpm-bounces@ietf.org [mailto:tcpm-bounces@ietf.org] On 
> Behalf Of Eddy, Wesley M. (GRC-MS00)[ASRC AEROSPACE CORP]
> Sent: Friday, March 05, 2010 10:56 AM
> To: tcpm@ietf.org
> Subject: [tcpm] Auth Option obsoleting MD5 Option in IANA registry
> 
> Following IANA's review of the TCP-AO draft, it was noted 
> that some entries in the TCP options registry have notes of 
> being obsoleted by other options:
> http://www.iana.org/assignments/tcp-parameters/tcp-parameters.xhtml
> One example, is Kind=6, which in the "Meaning"
> column indicates that it's obsoleted by Kind=8.
> 
> It's proposed that since the TCP AO document obsoletes the 
> TCP MD5 RFC, that the option assigned to TCP AO obsolete 
> Kind=19, the MD5 Signature Option, and this would be noted in 
> the IANA registry.
> 
> I think this should be easily agreed to by TCPM, since AO was 
> created to obsolete the MD5 option, but if there are any 
> objections to this, now is a good time to make them :).
> 
> --
> Wes Eddy
> MTI Systems
> 
> 
> _______________________________________________
> tcpm mailing list
> tcpm@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpm
> 