IETF Logo Mail Archive

Re: [Idr] draft-lapukhov-bgp-opaque-signaling

"Jakob Heitz (jheitz)" <jheitz@cisco.com> Sat, 12 March 2016 21:11 UTC

Return-Path: <jheitz@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4720112D859 for <idr@ietfa.amsl.com>; Sat, 12 Mar 2016 13:11:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 AUU1ooHM0teQ for <idr@ietfa.amsl.com>; Sat, 12 Mar 2016 13:11:34 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAF7B12D855 for <idr@ietf.org>; Sat, 12 Mar 2016 13:11:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11785; q=dns/txt; s=iport; t=1457817094; x=1459026694; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=dYMUzHqdQzCnj06v4boIFAG7eI3Qeq09qeBNvsz/h7M=; b=UrsRdOoKawp7A0bWC7I0g8vpQSro5KikWH/lF1JC+E1bll4dFxUWbe/D i6Cprv9nfEkYCIZPs5W3o9OTAR8iDM8/dwOHlQGpK9UyVTsWfuQldoGaC zszASUPfGM9+tPkn24nqKpU+73dIooc4rrhCBZaVJFSHxMh/SD01S5Wid c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D2AQAjheRW/5tdJa1dgnJMUm0GuisBDYFtIIVtAoEnOBQBAQEBAQEBZCeEQQEBAQQtXAIBCBEEAQEoBzIUCQgBAQQBEggBEogJDrxrAQEBAQEBAQEBAQEBAQEBAQEBAQEBFYYYhEKEZwmEBAWIO4R+hUqESAGFbYgLgWxLhySFMY58AR4BAUKBTDcZgUhqAQEBiHN+AQEB
X-IronPort-AV: E=Sophos; i="5.24,326,1454976000"; d="scan'208,217"; a="82201118"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Mar 2016 21:11:33 +0000
Received: from XCH-ALN-011.cisco.com (xch-aln-011.cisco.com [173.36.7.21]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u2CLBXjr010996 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 12 Mar 2016 21:11:33 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-ALN-011.cisco.com (173.36.7.21) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Sat, 12 Mar 2016 15:11:32 -0600
Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1104.009; Sat, 12 Mar 2016 15:11:32 -0600
From: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
To: Petr Lapukhov <petr@fb.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: draft-lapukhov-bgp-opaque-signaling
Thread-Index: AdF8nS8FQTTx9jiyQtWM4z1Bl2FmugABRu++AABFuBA=
Date: Sat, 12 Mar 2016 21:11:32 +0000
Message-ID: <976fb2df5f974b298a04b547afb917b7@XCH-ALN-014.cisco.com>
References: <2d12cade49ac4ec19a7f2c80aee3b72d@XCH-ALN-014.cisco.com> <3F437107848A5140A6A19222EFFB3481200E2389@PRN-MBX01-2.TheFacebook.com>
In-Reply-To: <3F437107848A5140A6A19222EFFB3481200E2389@PRN-MBX01-2.TheFacebook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.26.203]
Content-Type: multipart/alternative; boundary="_000_976fb2df5f974b298a04b547afb917b7XCHALN014ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/VULUU2aSPsbzlA2jEjgYV16kJrE>
Subject: Re: [Idr] draft-lapukhov-bgp-opaque-signaling
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Mar 2016 21:11:36 -0000

Without this problem solved, the proposal is not useful.
Everybody using it must stick to the eventual solution to ensure interoperability.
Therefore, it should be inside the scope.

Actually, BGP already has a way to distinguish applicationd: AFI and SAFI.

Jakob.

From: Petr Lapukhov [mailto:petr@fb.com]
Sent: Saturday, March 12, 2016 1:06 PM
To: Jakob Heitz (jheitz) <jheitz@cisco.com>; idr@ietf.org
Subject: RE: draft-lapukhov-bgp-opaque-signaling

Hi Jakob,

There is an ongoing discussion around avoiding NLRI (key) collisions. For now, the plan is to externally generate unique key prefix per application, e.g. application name, or UUID or some other globally unique string. Ensuring the uniqueness of those prefixes is outside the scope of the proposal, though - it's more of a deployment consideration.

Regards,

Petr

________________________________
From: Idr [idr-bounces@ietf.org] on behalf of Jakob Heitz (jheitz) [jheitz@cisco.com]
Sent: Saturday, March 12, 2016 12:26 PM
To: idr@ietf.org
Subject: [Idr] [WARNING : A/V UNSCANNABLE] draft-lapukhov-bgp-opaque-signaling

I read

http://www.ietf.org/id/draft-lapukhov-bgp-opaque-signaling-01.txt<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ietf.org_id_draft-2Dlapukhov-2Dbgp-2Dopaque-2Dsignaling-2D01.txt&d=CwMFAg&c=5VD0RTtNlTh3ycd41b3MUw&r=LU_vJaM_EQu1Ssm35j2xlA&m=y8paWUSIMD4YG8hfWC8k0b55e7qWYVRgGAwsXJKLMD4&s=-jEO1Jw88BI6pWUJf9es7WC0Q8Sm0XfBIhYRrWQCBHg&e=>


Is this intended for any and multiple applications to use?
If so, how do independent applications guarantee no duplication in NLRI?
If not, what is the target application?

Thanks
Jakob.

v2.23.0 | Report a Bug | By Email