Re: [Autoconf] Comments on adhoc-addr-model-00

[Zach Shelby <[e-mail]>]

Ulrich,

On Nov 19, 2009, at 12:53 , Ulrich Herberg wrote:

>> 2. I like the "link of undetermined properties"... however you might want to point to a document like draft-baccelli-multi-hop-wireless-communications to point out why links end up like that. RFC4861 also explains that a link might be non-transitive, so that could also be referenced.
> 
> I agree that the baccelli draft is very useful. I am undecided on
> whether to include a reference to that draft in the address model.
> While I think it could be very useful as a rationale for the address
> model, I also understand that the chairs are afraid of going this
> direction. The reason is that autoconf is only chartered for a single
> document, namely the address model. We are already years behind
> schedule. Producing a second document -- and including a reference
> from the address-model ID -- which we are not chartered for, could be
> difficult to argue for in the IESG.

Yep, makes sense. So instead just summarize the reasons why such a link might be categorized like this with a short paragraph in the adhoc-addr-model document. You may still point at RFC4861, as non-transitivity is mentioned there as well.

> 
>> 6.  The second bullet point of Section 6.2 needs some expansion not to be misunderstood. In addition to the existing sentence, also add text like: ", unless an assumption can be made about connectivity in which case the prefix may be /64." The point being that if you can assume connectivity with a router (who somehow advertises a prefix), you may be able to autoconfigure an address using a shared prefix. This is what we do in 6lowpan.
> 
> 
> One could argue that this is already implicit due to the sentence in section 3:
>   "When more specific assumptions can be made regarding the connectivity
>   between interfaces, these SHOULD be considered when configuring
>   subnet prefixes."

Right, so there could be a pointer to Section 3 at least in that bullet point to remind the reader of this exception? 

Zach

-- 
http://www.sensinode.com
http://zachshelby.org - My blog "On the Internet of Things"
http://6lowpan.net - New book - "6LoWPAN: The Wireless Embedded Internet"
Mobile: [phone]

Zach Shelby
Head of Research
Sensinode Ltd.
Kidekuja 2
88610 Vuokatti, FINLAND

This e-mail and all attached material are confidential and may contain legally privileged information. If you are not the intended recipient, please contact the sender and delete the e-mail from your system without producing, distributing or retaining copies thereof.