Hi Hemant,
AFAICS, there are four ways to go about this.
- Errata to RFC4862 (for minor/editorial changes)
- 4862bis (probably a bit premature)
- New standards track document that will end up updating RFC4862
- New informational document (probably guidelines to implementers)
From what I have seen, you are probably best off with option 4. I do
not see any of the issues mentioned in the draft as a protocol problem.
If implementations are getting this wrong, the problem is best solved
by writing implementation guidelines, not by protocol modifications.
Cheers
Suresh
Hemant Singh (shemant) wrote:
Tatuya,
We take it, after your recent changes to 2462bis -08 version, some day
soon this I-D will become a new RFC (say RFC xxxx). So when can we
expect to add updates to the new RFC?
Will you start a another xxxxbis right after this one is published?
When will the IPv6 working group be closed? Will there be any provision
for incorporating late-breaking changes?
- Wes
-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:[EMAIL PROTECTED]
Sent: Monday, July 09, 2007 7:38 AM
To: [email protected]
Subject: release candidate of 2462bis (Re: Revisit: one remaining
cornercase in DAD)
At Sat, 07 Jul 2007 03:09:23 +0900,
JINMEI Tatuya <[EMAIL PROTECTED]> wrote:
I tend to agree (I also thought this as an option myself). Thanks for
the suggestion.
I've updated the AUTH48 version of rfc2462bis with this fix. Other
(major) changes since the latest version of I-D (rfc2462bis-08) are:
- Updates to RFC references:
+ RFC3041 -> RFC4941 (which will be published at the same timing)
+ RFC3513 -> RFC4291
- Wording clarification about interface identifiers
(see discussion in the thread that began with this post:
http://www1.ietf.org/mail-archive/web/ipv6/current/msg05163.html)
Note that I didn't include any change about the strictness of DAD. I
didn't see any consensus on including that at this very final stage.
I'm about to submit this version to the RFC editor, but a copy of the
release candidate is available here:
http://www.jinmei.org/rfc4862-candidate.txt
just in case.
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba
Corp.
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
