[ppml] IRTF RRG: finer allocation of IPv4 space
BillD at cait.wustl.edu
Tue Nov 6 09:12:53 EST 2007
Thank you Robin for you invitation and your work in this area.
Denizens of the ppml and all those interested in addressing policy and the future of Internet communications and governance should be interested in solutions to the scaling of Internet routing. It is the bigger problem (IMO) that faces this community more than v4 exhaustion and v6 adoption. A solution to scalable routing and more efficient allocations and assignments of addresses solve many policy issues that seem quite sticky at the moment.
From: ppml-bounces at arin.net on behalf of Robin Whittle
Sent: Mon 11/5/2007 10:40 PM
To: ppml at arin.net
Subject: [ppml] IRTF RRG: finer allocation of IPv4 space
Denizens of PPML may be interested in joining the IRTF Routing
Research Group list:
The RRG is discussing several ITR-ETR (Ingress Tunnel Router -
Egress Tunnel Router) schemes which are intended primarily to help
the routing system scale well with growing demand for more
multihomed end-user networks - for both IPv4 and IPv6.
I think it would be great to have more hands on deck on the RRG list
to discuss and critique the various proposals.
At some stage, the RRG will recommend to the IETF what new
architectural proposals should be developed further. I think this
is likely to consist of one of the ITR-ETR schemes (or perhaps some
combination of bits of them) and one or more enhancements to BGP.
All of these ITR-ETR schemes enable address space to be assigned to
end-user networks in finer divisions than is currently practical
with BGP. Each such division does not involve a BGP advertised
prefix - and in principle, individual IP addresses can be assigned.
This means all these schemes all capable of enabling new management
structures for IPv4 address space, including assigning space in
increments as small as 128, 64, 32 ... 8, 4, 2 or 1 IP addresses.
All these schemes are intended primarily to resolve the problems in
routing scaling, for both IPv4 and IPv6, with incremental deployment
and no changes to hosts or most BGP routers. While they are all, in
principle, capable of enabling a much more efficient use of IPv4
space, for many more end-user networks, with multihoming and
portability of addresses between ISPs, only my proposal - Ivip - has
this as an explicit goal.
The proposals are:
Also of interest:
Two proposals, applicable to all ITR-ETR schemes,
for coping with the problems of Path MTU Discovery,
MTU limits etc. in the tunnel between the ITR and
The late 2006 IAB workshop on the routing and addressing
My comparison of LISP-CONS/NERD, eFIT-APT and Ivip.
Two recent IPv4 ping surveys find just over 100 million
ping-responsive IPv4 addresses, which is around 4% of
Geoff Huston's "train wreck" presentation, in which he
estimates that only 5 to 20% of advertised IPv4 address
space is actually used by a hosts.
Randy Bush's presentation on the difficulties of introducing
IPv6, and how every network using IPv6 will need some IPv4
space for a long time to come.
You are receiving this message because you are subscribed to the ARIN Public Policy
Mailing List (PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/ppml Please contact the ARIN Member Services
Help Desk at info at arin.net if you experience any issues.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ARIN-PPML