6MAN WG Last Call:

2013-02-12 Thread RJ Atkinson
I support publishing this draft as a Proposed Standard. There has been more than ample time to review the draft, and various minor updates already have been made, so this seems ready to shop. Ran IETF IPv6 working group mail

Re: 6MAN WG Last Call:

2013-02-12 Thread Ray Hunter
I have read this draft and support the work. The intention is good. The detail is thorny. Substantive Comment: I think you're going to be asked lots of questions about what constitutes an "IPv6 header chain," and to provide a tighter specification of where it ends. I'm sure there are people who

Re: [Fwd: I-D Action: draft-carpenter-6man-ug-00.txt]

2013-02-12 Thread Rémi Després
2013-02-11 23:51, Usman Latif : > Hi Remi, > > > > On 11/02/2013, at 9:13 PM, Rémi Després >> ... >>> So if I understand it correctly, if a PE-CE link already has a /127 prefix >>> assigned to it- and we wanted to use the CE as a 4rd CE, we'll have to >>> assign an additional IPv6 prefix

Re: Moving forward draft-ietf-6man-oversized-header chain?

2013-02-12 Thread Ole Troan
> FWIW, if ESP is used, the encrypted bytes are the payload (not the > header), and hence we're fine. If tunneling is being employed (whether > with IPsec or with something else), anything inside the tunnel is, > strictly speaking, a different layer -- so including everything up till > the ESP head