Re: [Idr] BGP-LS and the like ...

"Acee Lindem (acee)" <acee@cisco.com> Tue, 26 June 2018 17:43 UTC

Return-Path: <acee@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 7E7F7130EB5 for <idr@ietfa.amsl.com>; Tue, 26 Jun 2018 10:43:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level:
X-Spam-Status: No, score=-14.509 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 ZBkwppbEIsIr for <idr@ietfa.amsl.com>; Tue, 26 Jun 2018 10:43:13 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 099A1130E08 for <idr@ietf.org>; Tue, 26 Jun 2018 10:43:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2696; q=dns/txt; s=iport; t=1530034993; x=1531244593; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ldvEkTxfP9iPIUpQPsDz1+oPw2ZiJ3C6eDx/A0p1xFg=; b=QNBlKxZrmu57ys7vfiA/qvjTn1Bo/3I2EH1mHy3B7JrYQB+cAGf9ckrq oQP4ERRkmOW6Wtc2/AM0BcYWjJyPsv4rYNZRcpqNYfLPJKDhn4WNn/TNS D4xKnxCzuK4xI1prHAZI72v0a0HlNcAHoksFB9yKT8yPMfLsZf78AHVEQ 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CaAABJejJb/5hdJa1cGQEBAQEBAQEBAQEBAQcBAQEBAYJTSA8BAQEBIYFhKAqLc55ahQeBeguEbAKDEyE0GAECAQEBAQEBAm0ohTcGeRACAQgEOwcyFBECBA4FgyWBHGSvUh+IK4EciG2CFYEPJ4I6LogsgiQCmTEJAo8SjUqRSgIREwGBJB04gVJwFWUBgj6CIxeOF2+OZoEaAQE
X-IronPort-AV: E=Sophos;i="5.51,275,1526342400"; d="scan'208,217";a="134967704"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Jun 2018 17:43:12 +0000
Received: from XCH-RTP-006.cisco.com (xch-rtp-006.cisco.com [64.101.220.146]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id w5QHhCl7026021 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 26 Jun 2018 17:43:12 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-006.cisco.com (64.101.220.146) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 26 Jun 2018 13:43:11 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Tue, 26 Jun 2018 13:43:11 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Eric C Rosen <erosen@juniper.net>
CC: "Ketan Talaulikar (ketant)" <ketant@cisco.com>, Susan Hares <shares@ndzh.com>, Robert Raszuk <robert@raszuk.net>, "idr@ietf. org" <idr@ietf.org>
Thread-Topic: [Idr] BGP-LS and the like ...
Thread-Index: AQHUCSlP0hbR/o2HCEuysSnHVMFYDqRq2uEAgAGN2wCAAAXJgIAE8YsAgAFUwcGAAB20sYAASIIA
Date: Tue, 26 Jun 2018 17:43:11 +0000
Message-ID: <D3B9B3DE-4DE3-4AB0-9DD5-7A2903042AC4@cisco.com>
References: <CA+b+ERnS+b-OatPY+cnGX74Z+9yqF2AckgXAFnt1=osqELrdJA@mail.gmail.com> <09bc6cd3217645c4a503d5d44298d720@XCH-ALN-008.cisco.com> <05cb01d40a1c$0126d070$03747150$@ndzh.com> <71a1e810277f4dfe9ab89bb09803989b@XCH-ALN-008.cisco.com> <009301d40c97$aaeed1c0$00cc7540$@ndzh.com> <9081a0e6-362a-49a1-9008-8a1e9633cadb@juniper.net> <006701d40d55$2fecb410$8fc61c30$@ndzh.com> <3c50efa2-859c-d815-2f9e-58b961a794ee@juniper.net> <011201d40d6a$a9c23ac0$fd46b040$@ndzh.com> <f7b37727874e4f66bc74ef2b99371e6c@XCH-ALN-008.cisco.com> <b93115b1-42e1-8f46-6e7d-75b4257a4f46@juniper.net>
In-Reply-To: <b93115b1-42e1-8f46-6e7d-75b4257a4f46@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.116.152.205]
Content-Type: multipart/alternative; boundary="_000_D3B9B3DE4DE34AB09DD57A2903042AC4ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/fHIffgSOreJ8bxq8psueMEEspMA>
Subject: Re: [Idr] BGP-LS and the like ...
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.26
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, 26 Jun 2018 17:43:15 -0000


On Jun 26, 2018, at 1:23 PM, Eric C Rosen <erosen@juniper.net<mailto:erosen@juniper.net>> wrote:

On 6/26/2018 12:50 PM, Ketan Talaulikar (ketant) wrote:
If the application also receives a conflicting value of SRGB from BGP via the SRGB TLV in the Prefix SID Attribute then this could be logged as an error but I am not sure we want to discard the entire BGP Prefix SID attribute in this case.

The attribute is not malformed in this case, so there would be no reason to apply the attribute-discard procedure.

FWIW, I agree totally.

Acee