[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Isis-wg] Error in IANA TLVs listing



Tony -

> -----Original Message-----
> From: isis-wg-bounces at ietf.org [mailto:isis-wg-bounces at ietf.org] On
Behalf
> Of Tony Li
> Sent: Thursday, September 10, 2009 8:07 PM
> To: Mike Shand (mshand)
> Cc: isis mailing list
> Subject: Re: [Isis-wg] Error in IANA TLVs listing
> 
> 
> Mike,
> 
> mike shand wrote:
> > I'm not really sure how that would help unless we could get the
names
> > changed in ISO/IEC 10589 itself. I rather doubt both the ability to
do
> > that, and the desirability, even if we could.
> 
> 
> Having it in an RFC would allow us to submit it to JTC1 on the fast
> track.

Being one of a small group of folks who actively worked on getting the
most recent ISO 10589 update (2002) out I think I can authoritatively
(and hopefully non-offensively) chuckle at this statement.

Let's save our efforts for something more substantive and settle for
consistency. Folks have lived with the overloaded name for 20+ years - I
don't see any pressing need to change this.

   Les

>  We could then also amend the IANA registry in anticipation of
> this being approved.  Please see RFC 3563, section 3.4.2.
> 
> 
> > We would simply be replacing the potential confusion caused by
having
> > two TLVs with the same name, but different numbers and which are
used in
> > different PDUs, with the confusion caused by having a TLV (2) which
is
> > called "Intermediate System Neighbors" in ISO/IEC 10589 (and
probably
> > much documentation and code based on that) and called "IS
reachability
> > TLV" in some obscure RFC.
> 
> 
> ... and an update of 10589.
> 
> 
> Tony
> _______________________________________________
> Isis-wg mailing list
> Isis-wg at ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg