Re: [Idr] [Re: Idr] I-D Action: draft-ietf-idr-bgp-extended-messages-31.txt

"Enke Chen (enkechen)" <enkechen@cisco.com> Tue, 02 July 2019 17:24 UTC

Return-Path: <enkechen@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 DEC4A1206BD for <idr@ietfa.amsl.com>; Tue, 2 Jul 2019 10:24:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, 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 header.b=bcNYM6HS; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=xT9Wzte0
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 00LVoT2kZXco for <idr@ietfa.amsl.com>; Tue, 2 Jul 2019 10:24:01 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DC911206B2 for <idr@ietf.org>; Tue, 2 Jul 2019 10:24:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18393; q=dns/txt; s=iport; t=1562088241; x=1563297841; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=HX8KcKssZink4PGYTjVYRnTzM+hB79zT/UkZilaRVOs=; b=bcNYM6HSL7yiVDwee6OuNrJcvcQf5+N2BBbzWER5dL6T19LTDjpsVQ7o zSxFTWXxIBUdm5/BNqFMr5o5/0pzdcIccNfeVMrB+ZKPguVom7O0kncYS G1xmpNrvsM5ZeRK2ZqBxNio0ltzIhqJva34PoIYVLMYStuKDmf268iyvl w=;
IronPort-PHdr: =?us-ascii?q?9a23=3A31HYCxXFsZoFdgsaSvk99s9jpEXV8LGuZFwc94?= =?us-ascii?q?YnhrRSc6+q45XlOgnF6O5wiEPSA9yJ8OpK3uzRta2oGXcN55qMqjgjSNRNTF?= =?us-ascii?q?dE7KdehAk8GIiAAEz/IuTtank3GsdPX19o+VmwMFNeH4D1YFiB6nA=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ATAADukRtd/4MNJK1mGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBVQMBAQEBCwGBFC9QA2pVIAQLKIQcg0cDjl2CW4lLiSWEVIE?= =?us-ascii?q?ugSQDVAkBAQEMAQEtAgEBhEACF4ICIzYHDgEDAQEEAQECAQVtijcMhUoBAQE?= =?us-ascii?q?EEhEdAQE3AQ8CAQgOAwMBAigDAgICHxEUCQgCBAENBSKDAAGBHU0DHQGaSAK?= =?us-ascii?q?BOIhgcYEygnkBAQWCR4JIDQuCEgmBNAGLXheBQD+BEScfgkw+ghqCShYCglI?= =?us-ascii?q?ygiaOZoR8iFqNPUAJAoIWkAqDcxuXbY0wiS6NfgIEAgQFAg4BAQWBVgExgVh?= =?us-ascii?q?wFWUBgkGCQYNxilNygSmOAgEB?=
X-IronPort-AV: E=Sophos;i="5.63,444,1557187200"; d="scan'208,217";a="574794496"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 Jul 2019 17:23:59 +0000
Received: from XCH-RCD-006.cisco.com (xch-rcd-006.cisco.com [173.37.102.16]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id x62HNxsW005551 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 2 Jul 2019 17:23:59 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-006.cisco.com (173.37.102.16) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 2 Jul 2019 12:23:59 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 2 Jul 2019 13:23:56 -0400
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 2 Jul 2019 12:23:55 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HX8KcKssZink4PGYTjVYRnTzM+hB79zT/UkZilaRVOs=; b=xT9Wzte0WpbjX7v39JDHDdjcpQkK0uIZbLWtprweh0zfulMc+cTULT9DC8ou+HQgEXFK5mSFTQ6t4TKASB403UZMepu8R+jkbUi1QSFgI7FDlWmUZY7JrN4X2jNml1Rq7iRV3VRrOHujgv4Kf40oy/cEY0Az1Ee4YjFR5IllPG0=
Received: from BY5PR11MB3990.namprd11.prod.outlook.com (10.255.162.95) by BY5PR11MB4209.namprd11.prod.outlook.com (52.132.255.214) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2032.20; Tue, 2 Jul 2019 17:23:55 +0000
Received: from BY5PR11MB3990.namprd11.prod.outlook.com ([fe80::7026:24f1:c19f:e2f4]) by BY5PR11MB3990.namprd11.prod.outlook.com ([fe80::7026:24f1:c19f:e2f4%5]) with mapi id 15.20.2032.019; Tue, 2 Jul 2019 17:23:55 +0000
From: "Enke Chen (enkechen)" <enkechen@cisco.com>
To: Alvaro Retana <aretana.ietf@gmail.com>, Randy Bush <randy@psg.com>
CC: "idr@ietf.org" <idr@ietf.org>, "Enke Chen (enkechen)" <enkechen@cisco.com>
Thread-Topic: [Idr] [Re: Idr] I-D Action: draft-ietf-idr-bgp-extended-messages-31.txt
Thread-Index: AQHVMGkZ+oPfPergskydQyI9JyIwSaa2g4KA//+1tYCAARu4gP//yrIA
Date: Tue, 2 Jul 2019 17:23:54 +0000
Message-ID: <39882C53-D2F1-406D-A21E-E008F4A530F2@cisco.com>
References: <FDAC847D-60A2-4571-99CF-50458AC0E159@cisco.com> <m21rz9xn46.wl-randy@psg.com> <F41665B6-DD53-42F5-AD1D-F828C215809B@cisco.com> <CAMMESsxBDJrPMVdHyiJ3rQWyZaMB_4w-9qm+TD_8c0jtB+AOeA@mail.gmail.com>
In-Reply-To: <CAMMESsxBDJrPMVdHyiJ3rQWyZaMB_4w-9qm+TD_8c0jtB+AOeA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1a.0.190609
authentication-results: spf=none (sender IP is ) smtp.mailfrom=enkechen@cisco.com;
x-originating-ip: [2001:420:c0c8:1005::171]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 68fdbf82-04ed-4cb9-2a33-08d6ff120f4b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BY5PR11MB4209;
x-ms-traffictypediagnostic: BY5PR11MB4209:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BY5PR11MB420977962DB3B01962E284A1C5F80@BY5PR11MB4209.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 008663486A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(376002)(366004)(396003)(39860400002)(346002)(189003)(199004)(6436002)(54896002)(53936002)(6512007)(236005)(6306002)(110136005)(33656002)(186003)(53546011)(58126008)(229853002)(14454004)(54906003)(76176011)(102836004)(68736007)(6506007)(8936002)(81156014)(81166006)(8676002)(25786009)(99286004)(66556008)(71200400001)(4326008)(476003)(2616005)(36756003)(316002)(486006)(11346002)(446003)(107886003)(7110500001)(256004)(2420400007)(6116002)(5660300002)(71190400001)(73956011)(2906002)(46003)(66946007)(66446008)(6246003)(66476007)(64756008)(76116006)(7736002)(6486002)(86362001)(15650500001)(478600001); DIR:OUT; SFP:1101; SCL:1; SRVR:BY5PR11MB4209; H:BY5PR11MB3990.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: ftn6HCCtnulzmr/PUcxzesT1sPBWDbZMxhHpmOyRpGgB5tPzg54CVMS5WXjEGcJ1N6TrnTPQ6bq/QGXR/XKzRkvZK8iDzZCPNAVdVWWfDjmQuuHIAaFeaWSb/vdmcHx918n6eXtVRBcFTYJ5/JPDHltb2HejsK0yWvzzl7+Gt+0Azn3g2FEoLN/68rj6ITDjtGWpVamALqZJi+6o8nqOe2cggo+KDxYcpXp2DwiPNr+CXtAXQgnLkrvxihcaM+/AKphN8WfWfRVVEQWw2g6LpP9dEOUqMca0/F8UvQbtyay6WozkP27LvxH5DZraVpJz3qolYjOC7dCRI57AyROJGjnR5uch2lYRNuNqFNyWxcaBL45Yj+5X/jCxAbw7Myp2k3zVlSGFlp3t7eAK058pNbTSe6kXUmSt8FNbYsmF6gk=
Content-Type: multipart/alternative; boundary="_000_39882C53D2F1406DA21EE008F4A530F2ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 68fdbf82-04ed-4cb9-2a33-08d6ff120f4b
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Jul 2019 17:23:54.8883 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: enkechen@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR11MB4209
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.16, xch-rcd-006.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/0pwjF-drwRKe0LuZ_eliBqM8HnU>
Subject: Re: [Idr] [Re: Idr] I-D Action: draft-ietf-idr-bgp-extended-messages-31.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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, 02 Jul 2019 17:24:04 -0000

Hi, Alvaro:

It seems to me that these are two separate issues, the capability itself,
and the requirement for capability advertisement by both sides. The topic
I brought up initially is the former.

Regarding the text your cited from RFC 5492, that is about the latter,
and that is a change from the original capability spec, and I am not sure
why the change was made. Looking at the first usage (multi-protocol), it
explicitly talks about the “bi-directional”.

Even given the text in RFC 5492, I do not see any reason for including
the “send” portion in the capability definition for large messages.

Thanks.  -- Enke


RFC 5492:

   A BGP speaker that supports a particular capability may use this
   capability with its peer after the speaker determines (as described
   above) that the peer supports this capability.  Simply put, a given
   capability can be used on a peering if that capability has been
   advertised by both peers.  If either peer has not advertised it, the
   capability cannot be used.

RFC 3392:



   A BGP speaker that supports a particular capability may use this

   capability with its peer after the speaker determines (as described

   above) that the peer supports this capability.


RFC 4760 Multiprotocol Extension for BGP-4:


   To have a bi-directional exchange of routing information for a

   particular <AFI, SAFI> between a pair of BGP speakers, each such

   speaker MUST advertise to the other (via the Capability Advertisement

   mechanism) the capability to support that particular <AFI, SAFI>

   route.


From: Alvaro Retana <aretana.ietf@gmail.com>
Date: Tuesday, July 2, 2019 at 7:10 AM
To: "Enke Chen (enkechen)" <enkechen@cisco.com>, Randy Bush <randy@psg.com>
Cc: "idr@ietf.org" <idr@ietf.org>
Subject: Re: [Idr] [Re: Idr] I-D Action: draft-ietf-idr-bgp-extended-messages-31.txt

On July 1, 2019 at 11:39:39 PM, Enke Chen (enkechen) (enkechen@cisco.com<mailto:enkechen@cisco.com>) wrote:

Enke:

Hi!

Were there any specific issues for the capability to be unidirectional? It's not
clear to me how requiring the capability to be bidirectional would help.

rfc5492 says this: "Simply put, a given capability can be used on a peering if that capability has been advertised by both peers.  If either peer has not advertised it, the capability cannot be used.”

IOW, it is not so much that the meaning can’t be something else…but that this is how it was designed.

Alvaro.