Re: [sidr] Protocol Action: 'BGP Prefix Origin Validation State Extended Community' to Proposed Standard (draft-ietf-sidr-origin-validation-signaling-11.txt)

"Jakob Heitz (jheitz)" <jheitz@cisco.com> Sat, 04 March 2017 05:23 UTC

Return-Path: <jheitz@cisco.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49F751293EE; Fri, 3 Mar 2017 21:23:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 YxKW9FGAqVhn; Fri, 3 Mar 2017 21:23:55 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C886128DF6; Fri, 3 Mar 2017 21:23:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2174; q=dns/txt; s=iport; t=1488605035; x=1489814635; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=tV9YZKJxUQchbasnrCTKd4F96yug3xoUabFFp4P0SrQ=; b=fFsTEAC7fjwgip4xC/tgclNEvDuoG+BLipxPBIrv2XuJpfrgjVN2dIYr TX+oTKRH82SQCOi/Fa7yxT4txamWEiQSH3KO339EH+F/UUl7yOYP2UaOX mit6fQ2CAVf55DcnP8FrngHCQppiX0I2adfOe2VcLzwJimOXiRtl+Yy6I I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A7AQBcTrpY/5ldJa1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1GBa41skScflTeCDYYiAoJmPxgBAgEBAQEBAQFiKIRwAQEBAwE?= =?us-ascii?q?6PwUHBAIBCBEEAQEBHQEFBAcyFAkIAgQOBRSJXwi1HIsDAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBHYZOggUIgmKEPhaDNIIxAQSVdYY3AZIykR+TOgEfOIEDVhVQAYR?= =?us-ascii?q?4gUp2h1MrghABAQE?=
X-IronPort-AV: E=Sophos;i="5.35,239,1484006400"; d="scan'208";a="391871568"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Mar 2017 05:23:54 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v245Ns7I026227 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 4 Mar 2017 05:23:54 GMT
Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 3 Mar 2017 23:23:53 -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.1210.000; Fri, 3 Mar 2017 23:23:53 -0600
From: "Jakob Heitz (jheitz)" <jheitz@cisco.com>
To: Keyur Patel <keyur@arrcus.com>
Thread-Topic: [sidr] Protocol Action: 'BGP Prefix Origin Validation State Extended Community' to Proposed Standard (draft-ietf-sidr-origin-validation-signaling-11.txt)
Thread-Index: AQHSbB8KL4goLDO+zUCyR+oqQEK9nqF2Wu8wgAEcsQCADL9tgIAATY4AgAA/IwCAAAGigP//nPfggABrq4CAAABngP//nBXwgABvTQD//5z+sA==
Date: Sat, 4 Mar 2017 05:23:53 +0000
Message-ID: <6AFE0652-9306-4608-B029-106BD153D38E@cisco.com>
References: <148414831932.11019.14685466226406323027.idtracker@ietfa.amsl.com> <904eb4e5f3b54f8fb5eeddba482566c6@XCH-ALN-014.cisco.com> <AF3156BF-6CC9-4DDF-8C7A-4D6EDB9668AB@cisco.com> <D4DF2B46.74CF0%dougm@nist.gov> <m27f45x5jx.wl-randy@psg.com> <yj9oo9xhr8tj.wl%morrowc@ops-netman.net> <m2tw79vg94.wl-randy@psg.com> <4f0301f24b794a5c8ea0ab9e86f97eb0@XCH-ALN-014.cisco.com> <m2pohxvetm.wl-randy@psg.com> <yj9olgslr71w.wl%morrowc@ops-netman.net>, <b0af2bd3b7424c9fa0e41c7e5776beab@XCH-ALN-014.cisco.com>, <316227B7-8EB3-43C4-A164-926DDCDBA8FD@arrcus.com>
In-Reply-To: <316227B7-8EB3-43C4-A164-926DDCDBA8FD@arrcus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/jSHMAZ2oRdx9KpyJKgv6SxlT_ak>
Cc: "draft-ietf-sidr-origin-validation-signaling@ietf.org" <draft-ietf-sidr-origin-validation-signaling@ietf.org>, "sidr@ietf.org" <sidr@ietf.org>, Chris Morrow <morrowc@ops-netman.net>, "sidr-chairs@ietf.org" <sidr-chairs@ietf.org>, "sandy@tislabs.com" <sandy@tislabs.com>
Subject: Re: [sidr] Protocol Action: 'BGP Prefix Origin Validation State Extended Community' to Proposed Standard (draft-ietf-sidr-origin-validation-signaling-11.txt)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 04 Mar 2017 05:23:57 -0000

I pasted from the draft.

Thanks,
Jakob.


> On Mar 3, 2017, at 9:18 PM, Keyur Patel <keyur@arrcus.com> wrote:
> 
> Jacob,
> 
> Ebgp Peers are out of scope. Imho, implementations are free to implement receipt and processing of a community from a ebgp peer as a knob. The standard doesn't have to accommodate knobs.
> 
> Regards,
> Keyur
> 
> Sent from my iPhone
> 
>> On Mar 3, 2017, at 8:40 PM, Jakob Heitz (jheitz) <jheitz@cisco.com> wrote:
>> 
>>  However it SHOULD be possible to
>>  configure an implementation to send or accept the community when
>>  warranted.  An example of a case where the community would reasonably
>>  be received from, or sent to, an EBGP peer is when two adjacent ASes
>>  are under control of the same administration.  A second example is
>>  documented in [I-D.ietf-sidr-route-server-rpki-light].
>> 
>> Thanks,
>> Jakob.
>> 
>>> -----Original Message-----
>>> From: Chris Morrow [mailto:morrowc@ops-netman.net]
>>> Sent: Friday, March 03, 2017 8:38 PM
>>> To: Randy Bush <randy@psg.com>
>>> Cc: Jakob Heitz (jheitz) <jheitz@cisco.com>om>; Chris Morrow <morrowc@ops-netman.net>et>; Montgomery, Douglas (Fed)
>>> <dougm@nist.gov>ov>; Alvaro Retana (aretana) <aretana@cisco.com>om>; draft-ietf-sidr-origin-validation-signaling@ietf.org;
>>> sandy@tislabs.com; sidr-chairs@ietf.org; sidr@ietf.org
>>> Subject: Re: [sidr] Protocol Action: 'BGP Prefix Origin Validation State Extended Community' to Proposed Standard
>>> (draft-ietf-sidr-origin-validation-signaling-11.txt)
>>> 
>>> At Sat, 04 Mar 2017 13:36:05 +0900,
>>> Randy Bush <randy@psg.com> wrote:
>>>> 
>>>>> The ext-comm may come from an ebgp neighbor.
>>> 
>>> ebgp neighbor? the text talks about ibgp, and about explicitly ignoring ebgp senders of this community (by default).
>>> 
>>> right?
>>> 
>>>> 
>>>> ok.  saves a character.  my kind of change :)
>>>> 
>>>> "Similarly, a receiving BGP speaker, in the absence of validation
>>>>  state set based on local data, SHOULD derive a validations state from
>>>>  the last octet of the extended community, if present."
>>>> 
>>>> randy