<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2715.400" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>As far as I understand this is covered by the
Provider Independent Address space</FONT></DIV>
<DIV><FONT face=Arial size=2><A
href="http://www.ripe.net/ripe/docs/pi-pa.html">http://www.ripe.net/ripe/docs/pi-pa.html</A></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>-hph</FONT></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=pemptage@cisco.com href="mailto:pemptage@cisco.com">Peter Emptage</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=lir-wg@ripe.net
href="mailto:lir-wg@ripe.net">lir-wg@ripe.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Tuesday, May 14, 2002 3:32 PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> IPv4 Address Allocation policies
for organisations not connecting to the Internet</DIV>
<DIV><BR></DIV>
<DIV><FONT face=Arial size=2><SPAN class=312091613-14052002>There are a
limited number or organisations that for legitimate reasons require globally
unique address space apart from rfc1918 private address space, but
may not connect to or announce these prefixes on the Internet. Rfc 2050
referenced such situations as seen in the extract below.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=312091613-14052002></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=312091613-14052002>On a case by case
basis, it may be appropriate for these few organisations to become LIRs.
Perhaps the IPv4 Address Allocation policy should reference such circumstances
as rfc 2050 did?</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=312091613-14052002></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=312091613-14052002>Peter
Emptage</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=312091613-14052002>Senior Consulting
Engineer</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=312091613-14052002>Cisco
Systems</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=312091613-14052002></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN
class=312091613-14052002></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=312091613-14052002>rfc 2050 extract
section 3a</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=312091613-14052002></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2>Assignment Framework</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2> An assignment is the delegation of
authority over a block of IP<BR> addresses to an end
enterprise. The end enterprise will use<BR> addresses
from an assignment internally only; it will not sub-<BR> delegate
those addresses. This section discusses some of the
issues<BR> involved in assignments and the framework behind the
assignment of<BR> addresses.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2> In order for the Internet to scale
using existing technologies, use<BR> of regional registry services
should be limited to the assignment of<BR> IP addresses for
organizations meeting one or more of the following<BR>
conditions:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><STRONG> a)
the organization has no intention of connecting
to<BR> the
Internet-either now or in the future-but it
still<BR> requires a
globally unique IP address. The
organization<BR> should
consider using reserved addresses from
RFC1918.<BR> If it is
determined this is not possible, they can
be<BR> issued unique (if
not Internet routable) IP
addresses.</STRONG></FONT></DIV></BLOCKQUOTE></BODY></HTML>