[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: AW: Guidelines for Numbering IPv6 Point-to-Point Links and Easing the Addressing Plans
Hi Olaf,
I guess is a question of taste, I've seen this opinion from some ISPs, but
also the contrary one from many others.
Both models are valid. May be the document will be more complete describing
both choices, and up to each one to decide which he/she prefers.
Regards,
Jordi
> De: "Bonness, Olaf" <Olaf.Bonness@t-systems.com>
> Responder a: <owner-v6ops@ops.ietf.org>
> Fecha: Wed, 1 Mar 2006 11:41:59 +0100
> Para: <ot@cisco.com>, <jordi.palet@consulintel.es>
> CC: "v6ops@ops.ietf.org" <v6ops@ops.ietf.org>
> Asunto: AW: Guidelines for Numbering IPv6 Point-to-Point Links and Easing the
> Addressing Plans
>
>>
>> 4. Routing Aggregation of the Point-to-Point Links
>>
>> Following this approach and assuming that a shorter prefix is
>> typically delegated to a customer, in general a /48 [4], it is
>> possible to simplify the routing aggregation of the point-to-point
>> links. Towards this, the point-to-point link may be numbered using
>> the first /64 of a given /48.
>>
>> 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.
>
> My assumption from a service provider point of view would be to use a
> dedicated sub-preaefix (e.g. /48)of my own aggregate to address the
> point-to-point links (e.g. /64) to the custumers (in the case I have to do
> this).
>
> cu
> Olaf
>
**********************************************
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.