Hi.
Following the
discussion about /48 boundaries I'd like a better definition of what a site
is.
My definition of an
end-user site is the office where we (MCI/UUNET) install a circuit. This
could be a large office or a small bransch office or anything in
between.
Each office is
handled separately and they request IPv4 addresses per office. Adopting this to
IPv6 it would mean that each office would get a /48. This is too much for many
of them.
Approx. 80-90% of
our sites request 32 IP-addresses or less and most likely only subnet it 2 or 4
times if they ever subnet it.
Furthermore we never
get a complete network design for all branch offices if the customer is
transnational or even national so we can't really assign a /48 to the
customer for him to subnet among his offices. We can of course change our
procedures to accomomodate thisbut this will make things a lot more difficult
for us as a LIR and also the customer.
We can't decide how
many addresses to assign to a customer based on size or revenue.
What I want is a
clear definition of what a site is by having more catagories. but I don't want a
floating boundary as catagories do simplyfies things.
I also include my
suggestions based on where I'm coming from :-)
/60 for home
networks (16 networks)
/56 for enterprises (small/medium) (256
networks)
/48 for large enterprises (65000 networks)
/47 or more for "very
large subscribers"
/64 for mobile phones (w/ bluetooth or 802.11b)
/128
for dialup PC
Please note that I'm
not a routing expert nor am I a experienced in the complete IPv6 concept with
mobil users and consumers goods etc. My main area is IP-address administration.
I
administrate IP-networks for MCI/UUNET in almost all of Europe except DE, AT and
CH.
I haven't read the
RFC's related to this so my mind is wide open ;-)
Best
regards