Re: Guidelines for Numbering IPv6 Point-to-Point Links and Easing the Addressing Plans

[JORDI PALET MARTINEZ <jordi.palet@consulintel.es>]

Hi Ole,

See below, in-line.

Regards,
Jordi




> De: Ole Troan <ot@cisco.com>
> Responder a: <owner-v6ops@ops.ietf.org>
> Fecha: Sun, 05 Mar 2006 19:10:30 +0900
> Para: <jordi.palet@consulintel.es>
> CC: "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>
> Asunto: Re: Guidelines for Numbering IPv6 Point-to-Point Links and Easing the
> Addressing Plans
> 
>>> using the first (or any) subnet of a larger prefix, breaks the
>>> conceptual model of DHCP prefix delegation. the prefix is delegated to
>>> the requesting router and cannot be used to number the link between
>>> the delegating and requesting router.
>> 
>> I just re-read the DHCP-PD document, and is not so clear to me that this
>> breaks the model (I mean strictly there is no any text that is against this
>> usage). Also, we have actually tested this, even with Cisco, and it works
>> ;-)
>> 
>> If you mean that DHCP-PD concept is to delegate the complete prefix to the
>> requesting router, well, the user owning the CPE will not complain having
>> one less /64, but also is not so clear to me that we are stealing from them
>> a /64 because this is actually used to connect it ;-)
> 
> how is the requesting router supposed to know that it can't use that
> prefix on a downstream link?

This is not a "must" document, just info from operational experience. I'm
not stating that this is the only way and that should be done like this.
Also, it may depend on if the CPE is using the 1st /64 or something
different. I don't see this is stated in the DHCP-PD document, so I guess is
a decision of each implementation or I miss something ?.

> 
> cheers,
> Ole
> 




**********************************************
The IPv6 Portal: http://www.ipv6tf.org

Barcelona 2005 Global IPv6 Summit
Slides available at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.