ietf
[Top] [All Lists]

RE: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC

2011-09-26 14:40:13
Iljisch

Regarding /10 and not another size:
Originally it was a /8 and then the authors and networks dug in a bit more 
investigated what was to much and what was to little and decided a /10 would be 
sufficient.

Regarding IP resources for this use:

I spoke with DoD offline.  The answer is "approval would never be given for 
that". I had also sent an official request up one of the DoD chains and it 
never got a response. So, I'm going with the answer of no.

Regarding Legacy.  From what I have witnessed in the last 6 months, if Legacy 
holders have space that's not globally routing, they are busy assessing their 
networks and making "business" decisions.  Any space that they are bound to 
maintain and also not globally route that outsiders would request they possibly 
"share" for essentially private use, is not a likely outcome.  I've not 
received any positive responses for an outcome like that.

Additionally, correcti me if Im wrong here someone, but I believe ARIN has said 
they have a /10 they can put forward for this use if the policy and requirement 
is put in place for it.

Hope this answers your questions

Cheers
Marla

-----Original Message-----
From: Iljitsch van Beijnum [mailto:iljitsch(_at_)muada(_dot_)com]
Sent: Monday, September 26, 2011 7:56 AM
To: Benson Schliesser
Cc: Jari Arkko; 
draft-bdgks-arin-shared-transition-space(_at_)tools(_dot_)ietf(_dot_)org; 
ietf(_at_)ietf(_dot_)org; 
draft-weil-shared-transition-space-request(_at_)tools(_dot_)ietf(_dot_)org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-03.txt> 
(IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC

On 23 Sep 2011, at 7:21 , Benson Schliesser wrote:

The STS may have similar
semantics as RFC1918 space, in that it's non-routable on the Internet etc.
But it is not meant to be used in the same scope.

The draft isn't sufficiently clear on this to my liking.

I think it should be explicitly stated that no services are to be hosted on 
addresses in this prefix.

There is no support for the choice for a /10. Why not a /11 or a /9?

There is no discussion on the consequences of filtering packets to/from these 
addresses, such as PMTUD black holes.

Hosting the reverse DNS for these addresses within the prefix may or may not be 
useful.

Did anyone try to talk to holders of legacy space that is not present in the 
global routing table, such as the US government, to see if their addresses can 
be reused for this purpose?


This communication is confidential.  Frontier only sends and receives email on 
the basis of the terms set out at http://www.frontier.com/email_disclaimer.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf

<Prev in Thread] Current Thread [Next in Thread>