Re: -06 candidate

Oops,

I attached an old version.
Here is the newer one.

On 2012/01/17, at 21:39, Arifumi Matsumoto wrote:

> Hi,
> 
> sorry for the delay.
> I put together the remaining issues to be fixed in -06 version.
> 
> Several points,
> 
> - regarding the site-local deprecation, if I noticed only the examples
> section should be updated. And, I'm now wondering if the examples
> should be updated or not.
> 
> - regarding the informative reference, please tell me how exactly to
> refer to them in informative way.
> 
> Let me have your quick look at this, before submission.
> 
> <draft-ietf-6man-rfc3484-revise-06.txt>
> On 2012/01/13, at 5:24, Chris Grundemann wrote:
> 
>> On Fri, Dec 16, 2011 at 03:49, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>>> Well, there are two questions here.
>>> 
>>> One is whether the WG believes the update as described in draft-ietf-6man-rfc3484-revise-05 is correct and complete.  I have not seen (yet) any significant technical concerns raised.  The last of those were discussed and (we believe) resolved in Quebec.  Are there any more?
>> 
>> It appears that there is general agreement here, with possibly a few
>> technical/content nits that probably need to be sorted in a final
>> revision, raised by Dave and documented in message:
>> https://www.ietf.org/mail-archive/web/ipv6/current/msg14984.html
>> 
>>> The other is whether the WG believes we should publish an update, or a complete fresh version of RFC3484.  This was discussed previously in the WG and the update path preferred.  If a fresh version is now deemed more appropriate, I am fine to work on that with the other authors if required.
>> 
>> My understanding is that there is also general agreement here; that
>> this should be published as an update (after being re-organized a bit)
>> now, and then followed up with a replace (bis) I-D. As I have
>> previously stated; the changes in this update are needed and are
>> time-sensitive, the sooner this update can become an RFC the better.
>> 
>>> We just need a decision so we can progress this - it's been so close to release for a long time.  Many of the changes in the update have been implemented in a number of platforms already.
>> 
>> Agreed, let's get this done! =)
>> 
>> Cheers,
>> ~Chris
>> 
>> PS - I don't want to step on any toes here, but I'd be happy to take a
>> stab at a revision based on the current feedback if the authors would
>> like, I could probably get it done by the end of next week, possibly
>> sooner.
>> 
>>> Tim
>> 
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>> 
>> 
>> 
>> -- 
>> @ChrisGrundemann
>> weblog.chrisgrundemann.com
>> www.burningwiththebush.com
>> www.theIPv6experts.net
>> www.coisoc.org
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>> 
> 
> 
> --
> Arifumi Matsumoto
> NGN System Architecture Project
> NTT Service Integration Laboratories
> E-mail: arifumi@nttv6.net
> TEL +81-422-59-3334 FAX +81-422-59-6364
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--
Arifumi Matsumoto
 NGN System Architecture Project
 NTT Service Integration Laboratories
 E-mail: arifumi@nttv6.net
 TEL +81-422-59-3334 FAX +81-422-59-6364

Re: -06 candidate

Attachment: draft-ietf-6man-rfc3484-revise-06(1).txt