<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>RE: [ppml] IRTF RRG: finer allocation of IPv4 space</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Thank you Robin for you invitation and your work in this area.<BR>
<BR>
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.<BR>
<BR>
Bill Darte<BR>
ARIN AC<BR>
<BR>
-----Original Message-----<BR>
From: ppml-bounces@arin.net on behalf of Robin Whittle<BR>
Sent: Mon 11/5/2007 10:40 PM<BR>
To: ppml@arin.net<BR>
Subject: [ppml] IRTF RRG: finer allocation of IPv4 space<BR>
<BR>
Denizens of PPML may be interested in joining the IRTF Routing<BR>
Research Group list:<BR>
<BR>
<A HREF="http://www.irtf.org/charter?gtype=rg&group=rrg">http://www.irtf.org/charter?gtype=rg&group=rrg</A><BR>
<A HREF="http://psg.com/lists/rrg/2007/maillist.html">http://psg.com/lists/rrg/2007/maillist.html</A><BR>
<BR>
The RRG is discussing several ITR-ETR (Ingress Tunnel Router -<BR>
Egress Tunnel Router) schemes which are intended primarily to help<BR>
the routing system scale well with growing demand for more<BR>
multihomed end-user networks - for both IPv4 and IPv6.<BR>
<BR>
I think it would be great to have more hands on deck on the RRG list<BR>
to discuss and critique the various proposals.<BR>
<BR>
At some stage, the RRG will recommend to the IETF what new<BR>
architectural proposals should be developed further. I think this<BR>
is likely to consist of one of the ITR-ETR schemes (or perhaps some<BR>
combination of bits of them) and one or more enhancements to BGP.<BR>
<BR>
All of these ITR-ETR schemes enable address space to be assigned to<BR>
end-user networks in finer divisions than is currently practical<BR>
with BGP. Each such division does not involve a BGP advertised<BR>
prefix - and in principle, individual IP addresses can be assigned.<BR>
<BR>
This means all these schemes all capable of enabling new management<BR>
structures for IPv4 address space, including assigning space in<BR>
increments as small as 128, 64, 32 ... 8, 4, 2 or 1 IP addresses.<BR>
<BR>
All these schemes are intended primarily to resolve the problems in<BR>
routing scaling, for both IPv4 and IPv6, with incremental deployment<BR>
and no changes to hosts or most BGP routers. While they are all, in<BR>
principle, capable of enabling a much more efficient use of IPv4<BR>
space, for many more end-user networks, with multihoming and<BR>
portability of addresses between ISPs, only my proposal - Ivip - has<BR>
this as an explicit goal.<BR>
<BR>
The proposals are:<BR>
<BR>
LISP-CONS<BR>
<BR>
<A HREF="http://tools.ietf.org/html/draft-farinacci-lisp-04">http://tools.ietf.org/html/draft-farinacci-lisp-04</A><BR>
<A HREF="http://tools.ietf.org/html/draft-meyer-lisp-cons-02">http://tools.ietf.org/html/draft-meyer-lisp-cons-02</A><BR>
<BR>
<BR>
LISP-NERD<BR>
<BR>
<A HREF="http://tools.ietf.org/html/draft-farinacci-lisp-04">http://tools.ietf.org/html/draft-farinacci-lisp-04</A><BR>
<A HREF="http://tools.ietf.org/html/draft-lear-lisp-nerd-02">http://tools.ietf.org/html/draft-lear-lisp-nerd-02</A><BR>
<BR>
eFIT-APT<BR>
<BR>
<A HREF="http://tools.ietf.org/html/draft-jen-apt-00">http://tools.ietf.org/html/draft-jen-apt-00</A><BR>
<A HREF="http://www.cs.ucla.edu/~lixia/papers/07SIG_IP6WS.pdf">http://www.cs.ucla.edu/~lixia/papers/07SIG_IP6WS.pdf</A><BR>
<A HREF="http://tools.ietf.org/html/draft-wang-ietf-efit-00">http://tools.ietf.org/html/draft-wang-ietf-efit-00</A><BR>
<BR>
Ivip<BR>
<BR>
<A HREF="http://www.firstpr.com.au/ip/ivip/">http://www.firstpr.com.au/ip/ivip/</A><BR>
<A HREF="http://tools.ietf.org/html/draft-whittle-ivip-arch-00">http://tools.ietf.org/html/draft-whittle-ivip-arch-00</A><BR>
<BR>
TRRP<BR>
<BR>
<A HREF="http://bill.herrin.us/network/trrp.html">http://bill.herrin.us/network/trrp.html</A><BR>
<BR>
<BR>
Also of interest:<BR>
<BR>
<A HREF="http://www.firstpr.com.au/ip/ivip/pmtud-frag/">http://www.firstpr.com.au/ip/ivip/pmtud-frag/</A><BR>
<A HREF="http://tools.ietf.org/html/draft-templin-inetmtu-05">http://tools.ietf.org/html/draft-templin-inetmtu-05</A><BR>
<BR>
Two proposals, applicable to all ITR-ETR schemes,<BR>
for coping with the problems of Path MTU Discovery,<BR>
MTU limits etc. in the tunnel between the ITR and<BR>
the ETR.<BR>
<BR>
<BR>
<A HREF="http://www.iab.org/about/workshops/routingandaddressing/">http://www.iab.org/about/workshops/routingandaddressing/</A><BR>
<A HREF="http://tools.ietf.org/html/rfc4984">http://tools.ietf.org/html/rfc4984</A><BR>
<BR>
The late 2006 IAB workshop on the routing and addressing<BR>
crisis.<BR>
<BR>
<BR>
<A HREF="http://www.firstpr.com.au/ip/ivip/comp/">http://www.firstpr.com.au/ip/ivip/comp/</A><BR>
<BR>
My comparison of LISP-CONS/NERD, eFIT-APT and Ivip.<BR>
<BR>
<BR>
<A HREF="http://www.isi.edu/ant/address/">http://www.isi.edu/ant/address/</A><BR>
<A HREF="http://www.isi.edu/~johnh/PAPERS/Heidemann07c.pdf">http://www.isi.edu/~johnh/PAPERS/Heidemann07c.pdf</A><BR>
<A HREF="http://www.firstpr.com.au/ip/host-density-per-prefix/">http://www.firstpr.com.au/ip/host-density-per-prefix/</A><BR>
<BR>
Two recent IPv4 ping surveys find just over 100 million<BR>
ping-responsive IPv4 addresses, which is around 4% of<BR>
advertised addresses.<BR>
<BR>
<BR>
<A HREF="http://www.ripe.net/ripe/meetings/ripe-55/presentations/huston-ipv4.pdf">http://www.ripe.net/ripe/meetings/ripe-55/presentations/huston-ipv4.pdf</A><BR>
<BR>
Geoff Huston's "train wreck" presentation, in which he<BR>
estimates that only 5 to 20% of advertised IPv4 address<BR>
space is actually used by a hosts.<BR>
<BR>
<BR>
<A HREF="http://www.ripe.net/ripe/meetings/ripe-55/presentations/bush-ipv6-transition.pdf">http://www.ripe.net/ripe/meetings/ripe-55/presentations/bush-ipv6-transition.pdf</A><BR>
<BR>
Randy Bush's presentation on the difficulties of introducing<BR>
IPv6, and how every network using IPv6 will need some IPv4<BR>
space for a long time to come.<BR>
<BR>
- Robin<BR>
<BR>
_______________________________________________<BR>
PPML<BR>
You are receiving this message because you are subscribed to the ARIN Public Policy<BR>
Mailing List (PPML@arin.net).<BR>
Unsubscribe or manage your mailing list subscription at:<BR>
<A HREF="http://lists.arin.net/mailman/listinfo/ppml">http://lists.arin.net/mailman/listinfo/ppml</A> Please contact the ARIN Member Services<BR>
Help Desk at info@arin.net if you experience any issues.<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>