IETF Logo Mail Archive

Re: [Idr] [spring] Comments on draft-ietf-idr-bgp-prefix-sid-01

"Stefano Previdi (sprevidi)" <sprevidi@cisco.com> Tue, 17 November 2015 07:49 UTC

Return-Path: <sprevidi@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81EF71B2BEF; Mon, 16 Nov 2015 23:49:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.086
X-Spam-Level:
X-Spam-Status: No, score=-15.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 GR2F2oOkJHJ3; Mon, 16 Nov 2015 23:49:22 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6114C1A1A1C; Mon, 16 Nov 2015 23:49:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1414; q=dns/txt; s=iport; t=1447746562; x=1448956162; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=DpnCjjf6tzsaW6rpQJrl+3GWvV0Ksbqwv7AF/9tA9aM=; b=OXnckV4UMzlS1aExS4NSeD0t+AwthQGAHLvdiEjA+zritSHcYtpGxbg8 x1Ku7ZmkVcSKir25H4T7TtsaMfSpojAVKYT5MP7tjceXvBRx5WCa4flwo jJm5NCfkqTYLIbQnM3Gzwro0PMyyq4bHlyAlSaORpBU40zVbhYGVifg/V c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D1AQDV2kpW/4QNJK1egzuBQga+XgENgWWGEAIcgS44FAEBAQEBAQGBCoQ0AQEBAwEjEUUFCwIBCBgCAiYCAgIwFRACBA4FiCYIqnyQQQEBAQEBAQEBAQEBAQEBAQEBAQEBARiBAYVTghCCboRxgwQvgRUBBJZJAY0mnEQBHwEBQoIRHYFWcoQDgQcBAQE
X-IronPort-AV: E=Sophos;i="5.20,306,1444694400"; d="scan'208";a="51249057"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 17 Nov 2015 07:49:21 +0000
Received: from XCH-RTP-007.cisco.com (xch-rtp-007.cisco.com [64.101.220.147]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id tAH7nLn0015340 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 17 Nov 2015 07:49:21 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-007.cisco.com (64.101.220.147) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 17 Nov 2015 02:49:20 -0500
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1104.000; Tue, 17 Nov 2015 02:49:20 -0500
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Eric C Rosen <erosen@juniper.net>
Thread-Topic: [spring] [Idr] Comments on draft-ietf-idr-bgp-prefix-sid-01
Thread-Index: AQHRDQaNSu+O5jvuAkmSupOY8ZJPb56PZPUAgATZkQCAAeAXgIAJFbiAgAEeYoA=
Date: Tue, 17 Nov 2015 07:49:20 +0000
Message-ID: <7E84CCA4-1BF7-4D9C-A2AF-EC16877F7A90@cisco.com>
References: <56294416.8030807@juniper.net> <5104A350-EA8D-4824-A396-1DC46140BA5D@cisco.com> <5640BA18.7060807@juniper.net> <D267B645.3D1FF%acee@cisco.com> <5649EBC7.5000505@juniper.net>
In-Reply-To: <5649EBC7.5000505@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.199.77]
Content-Type: text/plain; charset="utf-8"
Content-ID: <9349B92819408643AFC6BD847CC398B5@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/YlQwgoHW82TmfuIpiGy9_iAdgho>
Cc: idr wg <idr@ietf.org>, SPRING WG <spring@ietf.org>
Subject: Re: [Idr] [spring] Comments on draft-ietf-idr-bgp-prefix-sid-01
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 17 Nov 2015 07:49:23 -0000

> On Nov 16, 2015, at 3:44 PM, Eric C Rosen <erosen@juniper.net> wrote:
> 
> On 11/10/2015 3:00 PM, Acee Lindem (acee) wrote:
>> I agree the predominant use case will be advertisement of a loopback.
>> However, independent of whether or not the Originator-SRGB TLV is
>> included, I see no reason why a BGP Speaker could not associate a
>> label-index with a locally attached subnet.
> 
> I agree that a label-index could be associated with a prefix, I didn't mean to suggest otherwise.  But what does it mean exactly to associate an originator-SRGB with a prefix (other than a host address)?
> 
> On 11/11/2015 3:00 AM, Stefano Previdi (sprevidi) wrote:
>> I don’t want to constrain the advertisement of the Originator-SRGB to
>> a /32 (or even to a loopback interface prefix).
> 
> Do you have an example in mind where it is useful to advertise an Originator SRGB when the prefix in the NLRI is not a host address?


in fact I don’t have any good example where a /32 (/128) must be enforced…

s.

v2.23.0 | Report a Bug | By Email