New Version Notification for draft-brandt-6man-lowpanz-01.txt

2013-04-23 Thread Anders Brandt
A new version of I-D, draft-brandt-6man-lowpanz-01.txt has been posted to the IETF repository. Filename:draft-brandt-6man-lowpanz Revision:01 Title: Transmission of IPv6 packets over ITU-T G.9959 Networks Creation date: 2013-04-22 Group: Individual

RE: last call comments for draft-ietf-6man-stable-privacy-addresses-06

2013-04-23 Thread Christian Huitema
Sorry I wasn't clear: what is the benefit of specifying the algorithm, when simply popping out another PRF will in just about any instance do the job (unless you are reinitializing the PRF with the same seed)? There seems to be a disconnect here: We want an algorithm that, roughly

RE: last call comments for draft-ietf-6man-stable-privacy-addresses-06

2013-04-23 Thread Christian Huitema
And I would observe that the DAD problem cannot be solved ina reliable way. Could you please elaborate? (Moving to the ipv6 mailing list, as this is way too detailed for the main IETF list.) The goal is to use the same address when repeatedly visiting the same network. However, since we

Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06

2013-04-23 Thread Fernando Gont
On 04/23/2013 12:55 PM, Christian Huitema wrote: And I would observe that the DAD problem cannot be solved ina reliable way. Could you please elaborate? (Moving to the ipv6 mailing list, as this is way too detailed for the main IETF list.) The goal is to use the same address when

Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06

2013-04-23 Thread Fernando Gont
On 04/23/2013 01:37 PM, Fernando Gont wrote: On 04/23/2013 12:55 PM, Christian Huitema wrote: And I would observe that the DAD problem cannot be solved ina reliable way. Could you please elaborate? (Moving to the ipv6 mailing list, as this is way too detailed for the main IETF list.) The

Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06

2013-04-23 Thread Fernando Gont
On 04/23/2013 11:41 AM, Christian Huitema wrote: You might argue that, clearly, the autoconf prefix needs to be part of the seed (I'd personally not expect developers to figure this one out). This is the kind of attitude that really does not go well with actual developers. You are basically

RE: last call comments for draft-ietf-6man-stable-privacy-addresses-06

2013-04-23 Thread Christian Huitema
If I'm the guy producing a spec, my goal is to produce a spec that is clear as possible, and only leave open those bits that are necessary to leave open. Well, that might work for internal specs when you are managing a project, but that's probably not the right way to approach standards. A

Re: last call comments for draft-ietf-6man-stable-privacy-addresses-06

2013-04-23 Thread Fernando Gont
On 04/23/2013 07:45 PM, Christian Huitema wrote: If I'm the guy producing a spec, my goal is to produce a spec that is clear as possible, and only leave open those bits that are necessary to leave open. Well, that might work for internal specs when you are managing a project, but that's