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

"Azinger, Marla" <Marla.Azinger@FTR.com> Mon, 26 September 2011 18:13 UTC

Return-Path: <marla.azinger@ftr.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACF3D21F8DBA for <ietf@ietfa.amsl.com>; Mon, 26 Sep 2011 11:13:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WVt14LSMy+WC for <ietf@ietfa.amsl.com>; Mon, 26 Sep 2011 11:13:38 -0700 (PDT)
Received: from frontiercorp.com (mail04.frontiercorp.com [66.133.172.21]) by ietfa.amsl.com (Postfix) with ESMTP id 9263D21F8DB6 for <ietf@ietf.org>; Mon, 26 Sep 2011 11:13:37 -0700 (PDT)
Received: from ([10.162.69.10]) by mail04.frontiercorp.com with ESMTP with TLS id 4LZG4M1.287042039; Mon, 26 Sep 2011 14:16:17 -0400
Received: from nyrofcswnqtr01.corp.pvt (10.160.66.132) by nyrofcswnexht01.corp.pvt (10.162.69.10) with Microsoft SMTP Server (TLS) id 8.1.375.2; Mon, 26 Sep 2011 14:16:17 -0400
Received: from ROCH-EXCH1.corp.pvt ([10.160.69.50]) by nyrofcswnqtr01.corp.pvt ([10.160.66.132]) with mapi; Mon, 26 Sep 2011 14:16:17 -0400
From: "Azinger, Marla" <Marla.Azinger@FTR.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>, Benson Schliesser <bschlies@cisco.com>
Date: Mon, 26 Sep 2011 14:16:15 -0400
Subject: RE: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC
Thread-Topic: Last Call: <draft-weil-shared-transition-space-request-03.txt> (IANA Reserved IPv4 Prefix for Shared Transition Space) to Informational RFC
Thread-Index: Acx8XIZBanfbTBLRTWexvZKAUGhYNwAGj51A
Message-ID: <2E2FECEBAE57CC4BAACDE67638305F1049E4061E71@ROCH-EXCH1.corp.pvt>
References: <CAA1817B.15807%bschlies@cisco.com> <3A6D3564-CB18-48E7-9058-5E5BA6FB04B5@muada.com>
In-Reply-To: <3A6D3564-CB18-48E7-9058-5E5BA6FB04B5@muada.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-esp: ESP<10>= SHA:<0> SHA_FLAGS:<0> UHA:<10> ISC:<0> BAYES:<0> SenderID:<0> DKIM:<0> TS:<0> SIG:<> DSC:<0> TRU_urllinks: <0> TRU_spam1: <0> TRU_playsites: <0> TRU_ru_spamsubj: <0> TRU_freehosting: <0> TRU_phish_spam: <0> TRU_scam_spam: <0> TRU_stock_spam: <0> TRU_embedded_image_spam: <0> TRU_money_spam: <0> URL Real-Time Signatures: <0> TRU_legal_spam: <0> TRU_watch_spam: <0> TRU_misc_spam: <0> TRU_profanity_spam: <0> TRU_html_image_spam: <0> TRU_adult_spam: <0> TRU_spam2: <0> TRU_medical_spam: <0> TRU_lotto_spam: <0> TRU_marketing_spam: <0>
X-Mailman-Approved-At: Mon, 26 Sep 2011 12:34:43 -0700
Cc: "draft-bdgks-arin-shared-transition-space@tools.ietf.org" <draft-bdgks-arin-shared-transition-space@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-weil-shared-transition-space-request@tools.ietf.org" <draft-weil-shared-transition-space-request@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Sep 2011 18:13:39 -0000

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@muada.com]
Sent: Monday, September 26, 2011 7:56 AM
To: Benson Schliesser
Cc: Jari Arkko; draft-bdgks-arin-shared-transition-space@tools.ietf.org; ietf@ietf.org; draft-weil-shared-transition-space-request@tools.ietf.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.