[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: More CPE

> -----Mensaje original-----
> De: owner-v6ops@ops.ietf.org 
> [mailto:owner-v6ops@ops.ietf.org] En nombre de james woodyatt
> Enviado el: jueves, 10 de enero de 2008 23:53
> Para: IPv6 Operations
> Asunto: Re: More CPE
> 
> On Jan 10, 2008, at 01:54, Miguel A. Diaz wrote:
> >
> > If both RA and DHPCPv6 are setup in the WAN port, the ISP has to 
> > manage two prefix pools: one for the point-to-point link 
> (RA) and the 
> > other one for the delegated prefix (usually /48).
> 
> And, this is difficult why?  Everyone at the ISP has only one 

Not really difficult but inefficient.


> finger- so, therefore, they're unable to count up to two?
> 
> > That can be avoided by...
> 
> 
> I think you skipped a step.  I don't understand why you want 
> to spend any effort avoiding this "problem" when the 
> "solution" seems to pose a whole passle of other, new and 
> interesting problems, i.e. how to delegate a fractional 
> prefix to a customer, i.e. "all these addresses belong to 
> you, except this /64... ATTEMPT NO LANDINGS THERE!"
> 
> 

Having only one pool for address assignement has at least the
following advantages (surely others ones as well):

* better HD-Ratio. Probably you'll think is that really important in
IPv6? But any LIR has to take care of that in order to receive the IP
(v4 or v6) address space from its RIR.

* one only pool in the ISP AAA infrastructure (i.e. RADIUS), so you
reduce the configuration and maintenance resources

* you are able to reduce one route in routing table of the access
router (ISP side). See
http://www.consulintel.euro6ix.org/ietf/draft-palet-v6ops-point2point-
01.txt section 4 for more details.


Regards
Miguel




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

Bye 6Bone. Hi, IPv6 !
http://www.ipv6day.org

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.