-06 candidate

Arifumi Matsumoto <arifumi@nttv6.net> Tue, 17 January 2012 12:44 UTC

Return-Path: <arifumi@nttv6.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 350FF21F84A5 for <ipv6@ietfa.amsl.com>; Tue, 17 Jan 2012 04:44:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.999
X-Spam-Level:
X-Spam-Status: No, score=-99.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IqLAZ2OpJWAH for <ipv6@ietfa.amsl.com>; Tue, 17 Jan 2012 04:44:15 -0800 (PST)
Received: from leo.nttv6.net (leo.nttv6.net [192.47.162.93]) by ietfa.amsl.com (Postfix) with ESMTP id 4052821F849D for <ipv6@ietf.org>; Tue, 17 Jan 2012 04:44:15 -0800 (PST)
Received: from radiko.smartstream.ne.jp (localhost.nttv6.net [127.0.0.1]) by leo.nttv6.net (8.14.5/8.14.4) with ESMTP id q0HCgEK5038594; Tue, 17 Jan 2012 21:42:14 +0900 (JST) (envelope-from arifumi@nttv6.net)
Subject: -06 candidate
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/mixed; boundary="Apple-Mail-15-604434390"
From: Arifumi Matsumoto <arifumi@nttv6.net>
In-Reply-To: <CAC1-dtnt+NKnqJaj-osfxwDf=uLpfv62hBBGDzftGL8KA6jdEA@mail.gmail.com>
Date: Tue, 17 Jan 2012 21:39:45 +0900
Message-Id: <6DDA8D20-8D10-4B6E-B101-9812FD83B781@nttv6.net>
References: <4EB3F3D6.4090302@innovationslab.net> <CAC1-dtnas++ahkBmpdyq7DbyAEg0W6bZY16qGzKmsP10vC39FQ@mail.gmail.com> <4EEA3D20.7020603@innovationslab.net> <CAKFn1SFvs0PzBXtEWWo814Oe5TJmbQEJBm5FeYJY5xzrr=KFSw@mail.gmail.com> <4EEA5793.8080800@gmail.com> <CAKFn1SHA-=cQ_=5rJVLVMvQYXoTL_D1dCR=uWZK-qFrcGp6P-w@mail.gmail.com> <4EEA7AF8.2090508@gmail.com> <0D0150C3-9E05-4839-ACF1-0E7196420D2F@ecs.soton.ac.uk> <CAKFn1SFp_r7EJ6CpM8EF2zkcJz1z34CdEcRt2i5xcsrWkCBQwQ@mail.gmail.com> <EMEW3|bd681ced736eee0700e443f9acc256d8nBFAnB03tjc|ecs.soton.ac.uk|0D0150C3-9E05-4839-ACF1-0E7196420D2F@ecs.soton.ac.uk> <CAC1-dtnt+NKnqJaj-osfxwDf=uLpfv62hBBGDzftGL8KA6jdEA@mail.gmail.com>
To: Chris Grundemann <cgrundemann@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 6man Mailing List <ipv6@ietf.org>, draft-ietf-6man-rfc3484-revise@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2012 12:44:18 -0000

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.

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