Thomas Narten wrote on 04/05/2005 09:04:11 PM:
> JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
> <[EMAIL PROTECTED]> writes:
>
> > >>>>> On Fri, 1 Apr 2005 06:13:22 -0700,
> > >>>>> Kristine Adamson <[EMAIL PROTECTED]> said:
> > > Thanks for the responses. But if RFC3542 is not updated, won't this
> > > adversely affect the portability of applications that references these new
> > > codes?
> > Yes, it will. However, the point is whether the portability issue is
> > serious enough to require a revision of RFC3542. Different people may
> > have different opinions on this, and I personally don't think it's big
> > enough.
> Suggestion:
> 1) Set up an issue tracker for this (and perhaps every IPv6 RFC for
> which there are some known errors/omissions?) that keeps track of
> these sorts of things. That way folk will be able to more easily
> find the list of outstanding issues (and their likely resolution),
> and we (the IETF community) won't lose track of them.
>
> 2) Although it may be overkill in this case, one could easily publish
> a (very!) short RFC just listing the additional code points, so
> that they are documened in the RFC series, and folk looking at the
> older RFC can find the new RFC via the "updated by" tag.
>
Besides adding the programming names of the new ICMPv6 code points to RFC3542, the following documents an old, minor problem with RFC3542, that was listed in the errata. This problem could also be resolved with a new, short RFC that updates RFC3542. Since there are 2 problems that could be resolved with a new RFC, do we now have sufficient reasons to publish a new RFC? Thanks!
>>>>>> On Sun, 30 Nov 2003 15:58:17 +0200 (EET),
>>>>>> Pekka Savola <[EMAIL PROTECTED]> said:
>>> And, in fact, the current implementation of the KAME project uses
>>> uint8_t for the align parameter.
>>>
>>> I don't know how to correct this one, though. Obviously, we cannot
>>> revise the document again just due to this problem.
>> Well, one could at least report it to:
>> http://www.rfc-editor.org/cgi-bin/errata.pl (link form the main page)
>Just FYI: I've reported this issue, and the errata page has just
>included the correction.
>> .. but most folks probably don't check that when reading the
>> specs..
>I tend to agree...
>JINMEI, Tatuya
>Communication Platform Lab.
>Corporate R&D Center, Toshiba Corp.
>[EMAIL PROTECTED]
Kristine Adamson
IBM z/OS Communications Server: TCP/IP Development
Phone: (919) 254-7911 T/L 444-7911
Internet e-mail:[EMAIL PROTECTED]
-------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
