IETF Logo Mail Archive

Re: [sidr] wglc for draft-ietf-sidr-bgpsec-protocol-11

"Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov> Tue, 03 March 2015 23:43 UTC

Return-Path: <kotikalapudi.sriram@nist.gov>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AB271A3BA1 for <sidr@ietfa.amsl.com>; Tue, 3 Mar 2015 15:43:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 A4EF7_20ifAN for <sidr@ietfa.amsl.com>; Tue, 3 Mar 2015 15:43:19 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0128.outbound.protection.outlook.com [65.55.169.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E8BE1A212A for <sidr@ietf.org>; Tue, 3 Mar 2015 15:43:19 -0800 (PST)
Received: from DM2PR09MB0302.namprd09.prod.outlook.com (25.160.96.147) by DM2PR09MB0302.namprd09.prod.outlook.com (25.160.96.147) with Microsoft SMTP Server (TLS) id 15.1.93.16; Tue, 3 Mar 2015 23:43:16 +0000
Received: from DM2PR09MB0302.namprd09.prod.outlook.com ([25.160.96.147]) by DM2PR09MB0302.namprd09.prod.outlook.com ([25.160.96.147]) with mapi id 15.01.0093.004; Tue, 3 Mar 2015 23:43:16 +0000
From: "Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov>
To: Matthew Lepinski <mlepinski.ietf@gmail.com>
Thread-Topic: [sidr] wglc for draft-ietf-sidr-bgpsec-protocol-11
Thread-Index: AQHQObnP/eFvHk0J6E2CzGstO0tmlJzjGf4AgAcb4iqAAE0vAIAE7aoAgAD+GgCAAAaAAIAAMwz4gAT6WoCACpsfgIADKAoOgAgWoFA=
Date: Tue, 3 Mar 2015 23:43:16 +0000
Message-ID: <DM2PR09MB03026D50D5CEC38987D93A5984110@DM2PR09MB0302.namprd09.prod.outlook.com>
References: <54DA7C98.4040604@mandelberg.org> <D103DE3D.1041C%keyupate@cisco.com> <D104DC36.3310E%dougm@nist.gov> <m2wq3klab3.wl%randy@psg.com> <1423943624118.34986@nist.gov> <54E3D163.1040600@mandelberg.org> <CANTg3aAN9roAnK_3aeKnD3Y=maErB2=i5e+YaphxZe0hheWzVg@mail.gmail.com> <87ioeor29k.fsf@rebma.mikesoffice.com>
In-Reply-To: <87ioeor29k.fsf@rebma.mikesoffice.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [129.6.140.100]
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0302;
x-microsoft-antispam-prvs: <DM2PR09MB0302A70477EF4712B53EF066B4110@DM2PR09MB0302.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DM2PR09MB0302;
x-forefront-prvs: 0504F29D72
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(50986999)(76176999)(86362001)(46102003)(76576001)(33656002)(54356999)(74316001)(40100003)(122556002)(110136001)(93886004)(92566002)(106116001)(62966003)(99286002)(230783001)(77156002)(66066001)(102836002)(2900100001)(2950100001)(87936001)(2656002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR09MB0302; H:DM2PR09MB0302.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Mar 2015 23:43:16.3008 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2ab5d82f-d8fa-4797-a93e-054655c61dec
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR09MB0302
Archived-At: <http://mailarchive.ietf.org/arch/msg/sidr/9yskMfWIVwIdkf3z4Jb8PbGM6jw>
Cc: "sidr@ietf.org" <sidr@ietf.org>
Subject: Re: [sidr] wglc for draft-ietf-sidr-bgpsec-protocol-11
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2015 23:43:21 -0000

On page 5, draft-ietf-sidr-bgpsec-protocol-11 says: 

A BGP speaker SHOULD
   NOT advertise the capability of BGPsec support for a particular AFI
   unless it has also advertised the multiprotocol extension capability
   for the same AFI combination [3].

I interpret this to mean that if a BGPsec speaker intends to send IPv4 updates 
to a peer, it should advertise multiprotocol extension capability with AFI = 1. 
That is so even when it intends to send only IPv4 updates. 
The fact that multiprotocol extension capability (with AFI = 1) is advertised, does it mean that 
MP_REACH_NLRI (see page 3, RFC 4760) should be used for announcing IPv4 prefixes?
Just trying to clarify because it wasn’t clear to me reading RFC 4760.

Sriram

v2.8.7 | Report a Bug | By Email