<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Times New Roman, Times, serif">As one of the authors of
that document, much as I am no great fan, I have to say that no
matter how hard we try, we have great difficulty convincing people
that the prefix doesn't matter. And there is some reason to
believe that a well know prefix does matter, because it is easy
for administrators (either side of the demarc) to install filters
on well known prefixes, and at least some do.<br>
<br>
</font><font face="Times New Roman, Times, serif">My big issue with
all of this is that by the time you're done with a registration
service that might offer reverse DNS (is that what we're saying?),
those filters are really the only difference between ULA-C and PI;
and the actually necessity for them, as far as the SPs other
customers are concerned, is considerably lessened since the spaces
don't overlap.<br>
<br>
Eliot<br>
</font><br>
On 4/12/10 7:18 AM, Owen DeLong wrote:
<blockquote
cite="mid:A7330B71-7FFE-43EC-97D2-597B91775C0E@delong.com"
type="cite">
<pre wrap="">Well said. Even RFC-1918 space can be routed across the global internet due to misconfiguration, so, I fail to see how that can possibly provide the protection described.
Admittedly, the number of misconfigurations increases in inverse proportion to topological proximity, but, nonetheless, lots of routing tables see RFC-1918 space on the global internet due to misconfiguration.
Why would ULA-C or any other "special" prefix be any different?
Owen
On Apr 11, 2010, at 7:14 PM, joel jaeggli wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Oddly, I work for mondo-megacorp and I find it interesting that you're speaking for all entities that fit that category collectively.
>From my vantage point ,the security posture associated with a particular prefix, service or network internal to our administrative domain is defined by requirements not by some intrinsic nature of the prefix.
George Bonser <a class="moz-txt-link-rfc2396E" href="mailto:gbonser@seven.com"><gbonser@seven.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: joel jaeggli [<a class="moz-txt-link-freetext" href="mailto:joelja@bogus.com">mailto:joelja@bogus.com</a>]
Sent: Sunday, April 11, 2010 6:37 PM
To: George Bonser; <a class="moz-txt-link-abbreviated" href="mailto:mcr@sandelman.ca">mcr@sandelman.ca</a>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>
Subject: Re: [arin-ppml] ULA-C
Mondo-megacorp will trivially have enough gua space to address it's
extranet and the cost of aquiring space is negible compared to cost of
deploying anything inside mondo-megacorp.
Joel
</pre>
</blockquote>
<pre wrap="">
Joel, you missed the point. The do not want their financial backend systems on globally routable address space.
They do not want it to even be POSSIBLE that by some kind of misconfiguration, their systems could be reachable from the Internet. So they put it in address space that is impossible to be reached across the public Internet.
</pre>
</blockquote>
<pre wrap="">_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
</pre>
</blockquote>
<br>
</body>
</html>