IETF Logo Mail Archive

Re: [GROW] FW: New Version Notification for draft-manderson-routing-intent-00.txt

Terry Manderson <terry.manderson@icann.org> Wed, 29 June 2011 00:32 UTC

Return-Path: <terry.manderson@icann.org>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 752C81F0C52 for <grow@ietfa.amsl.com>; Tue, 28 Jun 2011 17:32:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Px-5dKjawBZ5 for <grow@ietfa.amsl.com>; Tue, 28 Jun 2011 17:32:10 -0700 (PDT)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by ietfa.amsl.com (Postfix) with ESMTP id 0BBBF1F0C4A for <grow@ietf.org>; Tue, 28 Jun 2011 17:32:10 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Tue, 28 Jun 2011 17:32:09 -0700
From: Terry Manderson <terry.manderson@icann.org>
To: Benson Schliesser <bschlies@cisco.com>, "grow@ietf.org" <grow@ietf.org>
Date: Tue, 28 Jun 2011 17:32:04 -0700
Thread-Topic: [GROW] FW: New Version Notification for draft-manderson-routing-intent-00.txt
Thread-Index: Acwwc9UY+GDIXULvSFKvk1tfwwGVuwAARNJHACq8jaAAB8vl0AAnA6c5AAl2VWwAASIgCgD7n1Z2
Message-ID: <CA30AFA4.16F62%terry.manderson@icann.org>
In-Reply-To: <CA294418.1102E%bschlies@cisco.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [GROW] FW: New Version Notification for draft-manderson-routing-intent-00.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2011 00:32:10 -0000

Hi Benson,

Not speaking to the utility of that particular proposal, but I would think
that the policy (ARIN Draft Policy 2011-5) might also need to be reposted as
an IETF RFC to modify the IANA address registry. (in much the same way
rfc3849 came from the APNIC allocation)

If that were the case then the IANA address registry would reflect it.

Otherwise, I am not aware of any provision for an individual RIR to set a
particular prefix's status without some global policy work being done.

Cheers
Terry


On 24/06/11 10:27 AM, "Benson Schliesser" <bschlies@cisco.com> wrote:

> 
> 
> On 6/23/11 6:54 PM, "Terry Manderson" <terry.manderson@icann.org> wrote:
> 
>> The obvious example (and please - I don't care to buy into the brouhaha of
>> 6to4 going historic) is "192.88.99.0/24 reserved for 6to4 Relay Anycast"
>> 
>> The designated status is reserved, but it is routable.
> 
> Thanks for the clarification, Terry.  Your explanation makes sense.
> 
> Out of curiosity:  In the event that an RIR sets aside a block to be Non
> Routable (such as ARIN Draft Policy 2011-5) would the PRI designation be
> ALLOCATED Non Routable, or something else?
> 
> Cheers,
> -Benson
>

v2.23.0 | Report a Bug | By Email