Re: IPv6 Allocation Policy

Craig and all,

  ISP are never on a broad scale going to guarantee routability
of IPv6 address as the allocation policy is flawed and IPv6 is
a serious privacy and security hazzerd in it's present form.

Craig A. Huegen wrote:

> On Thu, 15 May 2003, Brian E Carpenter wrote:
>
> > "Craig A. Huegen" wrote:
> > ...
> > > The challenge: how to define a "large multi-national end-user" such that
> > > it would embody the spirit of what we're trying to accomplish.
> >
> > What we're trying to accomplish, presumably, is keeping the size of
> > the default BGP4+ table under control while allowing large multinationals
> > to be connected at many points to multiple ISPs using today's technology.
> >
> > However, I suspect that any attempt to define "large multinational"
> > precisely is going to be hard. It would be a brave person who
> > defines N and M in "has physical sites in at least N countries,
> > and is connected worldwide to at least M different ISPs."
>
> That's precisely why I was a coward.  However, I'm not sure that N
> countries is a real factor that should be considered; really, I think the
> factors are a) number of segments/subnets, and b) number of ISP's
> contributing a prefix to the end user.
>
> I think the cleanest solution is finding some way to use the existing
> policy but slightly amended for end-user.  Let me throw what I would
> consider reasonable:  end-user networks with more than, say, 1000 segments
> and 2 discrete ISP's?
>
> On top of that, I do have one other concern...  how does an end-user
> network obtain address space that would be routable when divided into the
> separate geographic regions?  For example, if I want address space that I
> can divide into chunks, each announced from a different Internet access
> point, do I need to ask for a /32 for each of the routing points or should
> the RIR's be advising ISP's that they should do filtering, if necessary,
> at minimum_allocation + 4 bits, or something like that?  I realize the
> RIR's don't want to guarantee routability, but they really should take it
> into consideration.
>
> /cah
>
> --
> Craig A. Huegen, Chief Network Architect      C i s c o  S y s t e m s
> IT Transport, Network Technology & Design           ||        ||
> Cisco Systems, Inc., 400 East Tasman Drive          ||        ||
> San Jose, CA  95134, (408) 526-8104                ||||      ||||
> email: [email protected]       CCIE #2100      ..:||||||:..:||||||:..
>
> _______________________________________________
> global-v6 mailing list
> [email protected]
> http://mailman.apnic.net/mailman/listinfo/global-v6

Regards,

--
Jeffrey A. Williams
Spokesman for INEGroup LLA. - (Over 129k members/stakeholders strong!)
================================================================
CEO/DIR. Internet Network Eng. SR. Eng. Network data security
Information Network Eng. Group. INEG. INC.
E-Mail [email protected]
Contact Number: 214-244-4827 or 214-244-3801


_______________________________________________
global-v6 mailing list
[email protected]
http://mailman.apnic.net/mailman/listinfo/global-v6