IETF Logo Mail Archive

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

Petr Lapukhov <petr@fb.com> Sat, 12 March 2016 21:05 UTC

Return-Path: <prvs=2879f8d98d=petr@fb.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 C308912D855 for <idr@ietfa.amsl.com>; Sat, 12 Mar 2016 13:05:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.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 AOUnSlRuIfcU for <idr@ietfa.amsl.com>; Sat, 12 Mar 2016 13:05:36 -0800 (PST)
Received: from mx0a-00082601.pphosted.com (mx0a-00082601.pphosted.com [67.231.145.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1291812D6FF for <idr@ietf.org>; Sat, 12 Mar 2016 13:05:36 -0800 (PST)
Received: from pps.filterd (m0044010.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.11/8.16.0.11) with SMTP id u2CL2UDG026674; Sat, 12 Mar 2016 13:05:34 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fb.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=qyRDzRWKkSlJVaQxFpW15CVo/sPa9RhTyZ7HClaxqS8=; b=KZrfbJXc9VaUQj61nIH+PldixSSOV6LaIusUQ5EIK26h2kF7gCxBwCoBWXF8xtjEuPpJ nZohwM9dhXLMktT9QTexQU8SEbQyXpRUxkLpKZofzTp7iiSvCXjY+EzDA1/SfERZJART Xr47aLJGWd9YPeYw0n4iExJauiFWLRNZFUc=
Received: from mail.thefacebook.com ([199.201.64.23]) by mx0a-00082601.pphosted.com with ESMTP id 21mg8nhpsa-1 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NOT); Sat, 12 Mar 2016 13:05:34 -0800
Received: from PRN-CHUB18.TheFacebook.com (192.168.16.72) by PRN-CHUB07.TheFacebook.com (192.168.16.17) with Microsoft SMTP Server (TLS) id 14.3.248.2; Sat, 12 Mar 2016 13:05:34 -0800
Received: from PRN-MBX01-2.TheFacebook.com ([169.254.3.204]) by PRN-CHUB18.TheFacebook.com ([fe80::6964:6730:1d3b:b80c%13]) with mapi id 14.03.0248.002; Sat, 12 Mar 2016 13:05:33 -0800
From: Petr Lapukhov <petr@fb.com>
To: "Jakob Heitz (jheitz)" <jheitz@cisco.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: draft-lapukhov-bgp-opaque-signaling
Thread-Index: AdF8nS8FQTTx9jiyQtWM4z1Bl2FmugABRu++
Date: Sat, 12 Mar 2016 21:05:33 +0000
Message-ID: <3F437107848A5140A6A19222EFFB3481200E2389@PRN-MBX01-2.TheFacebook.com>
References: <2d12cade49ac4ec19a7f2c80aee3b72d@XCH-ALN-014.cisco.com>
In-Reply-To: <2d12cade49ac4ec19a7f2c80aee3b72d@XCH-ALN-014.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.52.123]
Content-Type: multipart/alternative; boundary="_000_3F437107848A5140A6A19222EFFB3481200E2389PRNMBX012TheFac_"
MIME-Version: 1.0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-03-12_10:, , signatures=0
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/6fLO2AuK2mceHSDTk5EemWeQ74Y>
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:05:38 -0000

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