Le 21 juil. 2011 à 06:09, Jacni Qin a écrit : > Hi Remi, > > Thanks, inline please, > > On Wed, Jul 20, 2011 at 5:45 PM, Rémi Després <[email protected]> > wrote: > Hi, Jacni, > > ... > > In addition to Satoru's answer, an ISP that has many IPv4 prefixes can: > - use only a few, or even only one, of its shortest IPv4 prefixes, and > - use IPv4 address sharing to support as many CE's as needed. > > Example: an ISP has a /10, a /11, another /11, a /14, a /15, and a /16 (a > real example I met). > It can: > - use three domains (the /10 and the two /11's), or > - use only the /10, extending Port-set ID by one bit to support as many CE's > In both cases, no entropy due to the fragmented IPv4 space needs to be > exported to the IPv6 addressing plan. > > Jacni>: Ok, I got you point,
Thanks. > Another question is to make sure that continuous IPv6 pools (with EA) are > assigned on multiple Access Gateways (BNG) within the same 4rd domain. I don't understand the question. Could you clarify? > Plus, the reality is even more complicated, > For example, there are group/HQ and branches. The shorter prefixes are > probably held by the group level, and several/many 4rd domains (according to > the sizes of cities under given branch) will be maintained by the branches > who can only get fragmented spaces, since a large amount of these spaces come > from leftover prefixes returned. Again, not sure to get the question. The simple approach is "one IPv6 prefix" => "one 4rd prefix" (no fragmented spaces). Changing the length of one changes the length of the other. Cheers, RD > > > Cheers, > Jacni > > > Leftover IPv4 prefixes can then be returned to the community (for free... or > for a price, whatever applies). > > Regards, > RD > >> >> >> Cheers, >> Jacni >> >> _______________________________________________ >> Softwires mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/softwires > >
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
