Re: draft-andrews-6man-fragopt updated

2013-08-19 Thread C. M. Heard
On Tue, 6 Aug 2013, Mark Andrews wrote: > http://www.ietf.org/id/draft-andrews-6man-fragopt-01.txt This is an interesting draft and I see that it attempts to offer a fairly complete solution, covering not just TCP and UDP but ICMP and tunneled IPv4 and IPv6. The idea is to put L4 informat

Re: 6MAN WG Last Call:

2013-08-19 Thread Brian E Carpenter
On 20/08/2013 16:02, Fernando Gont wrote: > Hi, Mike > > On 08/19/2013 09:58 PM, C. M. Heard wrote: >> My main question is why this draft is not better integrated with >> draft-wkumari-long-headers-01 and draft-bonica-6man-frag-deprecate, >> which have overlapping or at least related subject mat

Re: 6MAN WG Last Call:

2013-08-19 Thread Fernando Gont
Hi, Mike On 08/19/2013 09:58 PM, C. M. Heard wrote: > > My main question is why this draft is not better integrated with > draft-wkumari-long-headers-01 and draft-bonica-6man-frag-deprecate, > which have overlapping or at least related subject matter. Because what's in draft-ietf-6man-oversize

Re: 6MAN WG Last Call:

2013-08-19 Thread C. M. Heard
Greetings, My main question is why this draft is not better integrated with draft-wkumari-long-headers-01 and draft-bonica-6man-frag-deprecate, which have overlapping or at least related subject matter. The thrust of draft-ietf-6man-oversized-header-chain is to require that all extension heade

Re: 6MAN WG Last Call:

2013-08-19 Thread Mark ZZZ Smith
Hi, Going by the title, it seems my comment was missed about not implying that this address generation technique is limited to SLAAC slack scenarios, but could be useful with any address configuration method (i.e, SLAAC, DHCPv6, static, +future.) There seemed to be some support for decoupling t

Re: 6MAN WG Last Call:

2013-08-19 Thread Fernando Gont
Erik, On 08/19/2013 06:40 AM, Erik Kline wrote: > I pre-apologize, as always, for my ignorance, but...is there an > implementation of this? Specifically, I'm mildly concerned about this > for link-local addresses. > > Compliant implementations cannot even begin any IPv6 link-local > operations u

Re: 6MAN WG Last Call:

2013-08-19 Thread Erik Kline
I pre-apologize, as always, for my ignorance, but...is there an implementation of this? Specifically, I'm mildly concerned about this for link-local addresses. Compliant implementations cannot even begin any IPv6 link-local operations until the secret key has been loaded from stable storage. They

6MAN - active documents

2013-08-19 Thread Ole Troan
In working group last call: draft-ietf-6man-oversized-header-chain-04(ending August 27th) draft-ietf-6man-stable-privacy-addresses-12 (ending September 2nd) *** We are awaiting document reviewer volunteers for these two. Please contact the chairs. (No prizes, but we might offer a beer

6MAN WG Last Call:

2013-08-19 Thread Ole Troan
All, This message starts the second two week 6MAN Working Group on advancing: Title : A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC) Author(s): F. Gont Filena

I-D Action: draft-ietf-6man-stable-privacy-addresses-12.txt

2013-08-19 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IPv6 Maintenance Working Group of the IETF. Title : A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration