Re: [bess] [IANA #812089] Protocol Action: 'Covering Prefixes Outbound Route Filter for BGP-4' to Proposed Standard (draft-ietf-bess-orf-covering-prefixes-06.txt)

Ronald Bonica <rbonica@juniper.net> Thu, 12 March 2015 08:40 UTC

Return-Path: <rbonica@juniper.net>
X-Original-To: expand-draft-ietf-bess-orf-covering-prefixes.all@virtual.ietf.org
Delivered-To: bess@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 232411A8BC3; Thu, 12 Mar 2015 01:40:53 -0700 (PDT)
X-Original-To: xfilter-draft-ietf-bess-orf-covering-prefixes.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-bess-orf-covering-prefixes.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04C201A8F3B for <xfilter-draft-ietf-bess-orf-covering-prefixes.all@ietfa.amsl.com>; Thu, 12 Mar 2015 01:40:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.235
X-Spam-Level:
X-Spam-Status: No, score=-101.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yRDUM1eAeYH8 for <xfilter-draft-ietf-bess-orf-covering-prefixes.all@ietfa.amsl.com>; Thu, 12 Mar 2015 01:40:51 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93FE51A870E for <draft-ietf-bess-orf-covering-prefixes.all@ietf.org>; Thu, 12 Mar 2015 01:40:48 -0700 (PDT)
Received: from mail-bn1on0142.outbound.protection.outlook.com ([157.56.110.142]:1377 helo=na01-bn1-obe.outbound.protection.outlook.com) by zinfandel.tools.ietf.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.82_1-5b7a7c0-XX) (envelope-from <rbonica@juniper.net>) id 1YVyff-0004yo-KJ for draft-ietf-bess-orf-covering-prefixes.all@tools.ietf.org; Thu, 12 Mar 2015 01:40:48 -0700
Received: from CO1PR05MB444.namprd05.prod.outlook.com (10.141.73.140) by CO1PR05MB539.namprd05.prod.outlook.com (10.141.73.26) with Microsoft SMTP Server (TLS) id 15.1.99.14; Thu, 12 Mar 2015 01:31:55 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB444.namprd05.prod.outlook.com (10.141.73.140) with Microsoft SMTP Server (TLS) id 15.1.106.15; Thu, 12 Mar 2015 01:31:53 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.61]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.61]) with mapi id 15.01.0106.007; Thu, 12 Mar 2015 01:31:53 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "drafts-approval@iana.org" <drafts-approval@iana.org>
Thread-Topic: [IANA #812089] Protocol Action: 'Covering Prefixes Outbound Route Filter for BGP-4' to Proposed Standard (draft-ietf-bess-orf-covering-prefixes-06.txt)
Thread-Index: AQHQXEsyIT9A0cX/qE+e2amxi6NIS50YDtXQ
Date: Thu, 12 Mar 2015 01:31:52 +0000
Message-ID: <CO1PR05MB442F5ABD0D80EE4AD1DCC10AE060@CO1PR05MB442.namprd05.prod.outlook.com>
References: <RT-Ticket-812089@icann.org> <20150309191547.20070.81805.idtracker@ietfa.amsl.com> <rt-4.2.9-32314-1426113111-1024.812089-7-0@icann.org>
In-Reply-To: <rt-4.2.9-32314-1426113111-1024.812089-7-0@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [66.129.241.13]
authentication-results: iana.org; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB444; UriScan:; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB539;
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(13464003)(51704005)(164054003)(377454003)(122556002)(76576001)(40100003)(86362001)(15975445007)(50986999)(74316001)(2656002)(230783001)(76176999)(110136001)(2351001)(54356999)(102836002)(46102003)(77156002)(33656002)(62966003)(19580395003)(92566002)(66066001)(1720100001)(106116001)(2900100001)(19580405001)(99286002)(87936001)(2501003)(2950100001); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR05MB444; H:CO1PR05MB442.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
x-microsoft-antispam-prvs: <CO1PR05MB4447D82BB0F3C9851D9A8CAAE060@CO1PR05MB444.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5002009)(5005006); SRVR:CO1PR05MB444; BCL:0; PCL:0; RULEID:; SRVR:CO1PR05MB444;
x-forefront-prvs: 05134F8B4F
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Mar 2015 01:31:52.2274 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR05MB444
X-OriginatorOrg: juniper.net
X-Helo-Check-Failed: Verification failed for HELO na01-bn1-obe.outbound.protection.outlook.com
X-SA-Exim-Connect-IP: 157.56.110.142
X-SA-Exim-Rcpt-To: draft-ietf-bess-orf-covering-prefixes.all@tools.ietf.org
X-SA-Exim-Mail-From: rbonica@juniper.net
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
Resent-To: draft-ietf-bess-orf-covering-prefixes.all@ietf.org
Resent-Message-Id: <20150312084051.93FE51A870E@ietfa.amsl.com>
Resent-Date: Thu, 12 Mar 2015 01:40:48 -0700
Resent-From: rbonica@juniper.net
Archived-At: <http://mailarchive.ietf.org/arch/msg/draft-ietf-bess-orf-covering-prefixes.all@tools/Vdgd3gY7ga30mNTDJTRNVo05Jp0>
Archived-At: <http://mailarchive.ietf.org/arch/msg/bess/1H2ES-VujWrz97kFOzpUXkESLfw>
X-Mailman-Approved-At: Thu, 12 Mar 2015 07:55:09 -0700
Cc: "draft-ietf-bess-orf-covering-prefixes.all@tools.ietf.org" <draft-ietf-bess-orf-covering-prefixes.all@tools.ietf.org>
Subject: Re: [bess] [IANA #812089] Protocol Action: 'Covering Prefixes Outbound Route Filter for BGP-4' to Proposed Standard (draft-ietf-bess-orf-covering-prefixes-06.txt)
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2015 08:40:53 -0000

Hi Amanda,

I have two questions.

The latest version of draft-ietf-bess-orf-covering prefixes is 06. Your reference is RFC-ietf-bess-orf-covering-prefixes-03. Does that make a difference?

Also, I assume that this string will be replaced with an RFC number when one is assigned. Is that right?

Otherwise, it looks OK.

                                         Ron


> -----Original Message-----
> From: Amanda Baber via RT [mailto:drafts-approval@iana.org]
> Sent: Wednesday, March 11, 2015 6:32 PM
> Cc: draft-ietf-bess-orf-covering-prefixes.all@tools.ietf.org
> Subject: [IANA #812089] Protocol Action: 'Covering Prefixes Outbound Route
> Filter for BGP-4' to Proposed Standard (draft-ietf-bess-orf-covering-prefixes-
> 06.txt)
> 
> Dear Authors:
> 
> ATTENTION: A RESPONSE TO THIS MESSAGE IS NEEDED
> 
> We've completed the IANA Actions for the following RFC-to-be:
> 
> draft-ietf-bess-orf-covering-prefixes-06
> 
> ACTION 1:
> 
> IANA has updated the reference for the following BGP Outbound Route
> Filtering (ORF) Type:
> 
> 65	CP-ORF	[RFC-ietf-bess-orf-covering-prefixes-03]
> 
> Please see
> http://www.iana.org/assignments/bgp-parameters
> 
> 
> ACTION 2:
> 
> IANA has updated the reference for the following Transitive Opaque
> Extended Community Sub-Type:
> 
> 0x03 	CP-ORF	[RFC-ietf-bess-orf-covering-prefixes-03]
> 
> Please see
> http://www.iana.org/assignments/bgp-extended-communities
> 
> 
> Please let us know whether the above IANA Actions look OK. As soon as we
> receive your confirmation, we'll notify the RFC Editor that this document's
> IANA Actions are complete. (If this document has a team of authors, one
> reply on behalf of everyone will suffice.)
> 
> We'll update the reference when the RFC Editor notifies us that they've
> assigned a number.
> 
> Thanks,
> 
> Amanda Baber
> IANA Request Specialist
> ICANN