Re: [Idr] Capability Advertisement in draft-ietf-idr-bgp-extended-messages
"Enke Chen (enkechen)" <enkechen@cisco.com> Thu, 01 August 2019 05:40 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 6138212006B; Wed, 31 Jul 2019 22:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, 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=OmqAI9Cm; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Wd92uKaa
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 ddvlqc9lxOQu; Wed, 31 Jul 2019 22:40:04 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B1C512000F; Wed, 31 Jul 2019 22:40:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5182; q=dns/txt; s=iport; t=1564638004; x=1565847604; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=9RaieM75JJvI9cYjAC/b8PyKnbiMRu4ovMH5i12cZYU=; b=OmqAI9Cm/YpjsNhxiYunmEpKeyUOys5fW1SI9E7na+pI/IL5t58eTR+j +cC6sXiymODHQaypJKtcAlKDjaeX1VVRvUFBQ+JDknA+sMWq4BrQAnrZy vaiyrU0XhXtBl56i4Peg8TNOeqSdwPNUDfZ+eN8grw5KWxgmv9iUJMtLm 0=;
IronPort-PHdr: 9a23:q08e4hUzH1xS2LMugY1vbsWtb4rV8LGuZFwc94YnhrRSc6+q45XlOgnF6O5wiEPSA9yJ8OpK3uzRta2oGXcN55qMqjgjSNRNTFdE7KdehAk8GIiAAEz/IuTtank3GsdPX19o+VmwMFNeH4D1YFiB6nA=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AJAACjekJd/5pdJa1lGQEBAQEBAQEBAQEBAQcBAQEBAQGBVAMBAQEBAQsBgUQkLANtVSAECyqEHoNHA4sngjYlfpZXgS6BJANUCQEBAQwBARgLCgIBAYRAAheCOCM1CA4BAwEBBAEBAgEGbYUeDIVKAQEBAQMBARAREQwBASwLAQsEAgEIEQMBAQEBAgImAgICJQsVCAgCBAENBSKDAAGBagMdAQ6gUAKBOIhgcYEygnoBAQWFAxiCEwMGgQwoAYtfF4FAP4ERJwwTghc1PoJhAQGBYYMLMoImjlMxnBAJAoIai0+ISxuCLoIykzeNQYEyljMCBAIEBQIOAQEFgVIDM4FYcBU7KgGCQYJCg3GFFIU+AXKBKYo4BgGCSwEB
X-IronPort-AV: E=Sophos;i="5.64,333,1559520000"; d="scan'208";a="611955639"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 01 Aug 2019 05:40:00 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x715e04j028531 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 1 Aug 2019 05:40:00 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 1 Aug 2019 00:39:59 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 1 Aug 2019 01:39:58 -0400
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 1 Aug 2019 01:39:58 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cg82UjMVWjuz2qfFk8uRfrbaa6xvcLtFJvwb0qb41smyDrvuQns7BL5YsTSAtIuR/yvl2OKWSFc5HeX0F0nuASF8ARCCS39pAwahbcyxD1gT2xO64r25tz22sQNLeZPn/IATBOmzMC9LoQIbT1qfnOAmOIzVEFs0dEwg4Y8y+z2N8uFUsTsQyoiNut3VBnWu42wWqvf74Qum4aRmqvg7uWavte+02Rg3GSrZ8HZB9O1r9Lw3Q0nFYqzR9jviiVA+RkdLh7r3Uv/+yYNSj92rOys91zLy8k8ZBKNh20K+Tmef44M5mYyrXPLrnVNz9cEzNAm6asyvqaZSRPTbnh9oFw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9RaieM75JJvI9cYjAC/b8PyKnbiMRu4ovMH5i12cZYU=; b=IGBBuKKFjkFw/N2OtJELpfVnDLQHGrzKATZYXw1nIZWKQ9RNPOq/gagl32Ik8L+q0gz/C5AQU8vGnEb0ZZfs9UYB33NKxTF7y0hiicpxjw+fDG3rxrck/UX54TZ7eDGEqcP8lryYPWp9WFTbbGCY+q9YwY1jVy3JEixacdoY8eCg3+z48J/op6b//8Q6pBzPpVQDNRbJaIYdn7N7hLwcPocuepIDjIbQi5g9c1JjzAS4dTCZY3cjRUKp1nPspb73uCCVXu7LuXQy8mYaQ8eYl4zkGoKYkA8pT9ZdwatJVZW+OqbKPGmmR5AP55nLDOz0qqrOHgzm9wIJvgHMOKGFgw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=cisco.com;dmarc=pass action=none header.from=cisco.com;dkim=pass header.d=cisco.com;arc=none
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=9RaieM75JJvI9cYjAC/b8PyKnbiMRu4ovMH5i12cZYU=; b=Wd92uKaaQ2CbVBuT3GkjJyZnRIuFVwmhQdoo2eKznbLtUTq9F4cC9eHHyjsk/ugQYbDCdr43fxJQnhYgI2Ghrd+U8C95S9xTlFaMrCDrD880GAoBbBrKiZz0g21yDLhnv0JW3cVKcZKzjKA8sM32YlLhdQH2udazHYdubJg4RB8=
Received: from BY5PR11MB3990.namprd11.prod.outlook.com (10.255.162.95) by BY5PR11MB4353.namprd11.prod.outlook.com (52.132.252.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.14; Thu, 1 Aug 2019 05:39:57 +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.2115.005; Thu, 1 Aug 2019 05:39:57 +0000
From: "Enke Chen (enkechen)" <enkechen@cisco.com>
To: "Jakob Heitz (jheitz)" <jheitz@cisco.com>, Jeffrey Haas <jhaas@pfrc.org>
CC: "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "idr@ietf. org" <idr@ietf.org>, "draft-ietf-idr-bgp-extended-messages@ietf.org" <draft-ietf-idr-bgp-extended-messages@ietf.org>, Susan Hares <shares@ndzh.com>, "Enke Chen (enkechen)" <enkechen@cisco.com>
Thread-Topic: [Idr] Capability Advertisement in draft-ietf-idr-bgp-extended-messages
Thread-Index: AQHVR9vBZYyS0SwmxEOAkc+tFB2gRablOpgA//+ULgCAAKHJgIAATPWA//+UhQA=
Date: Thu, 01 Aug 2019 05:39:57 +0000
Message-ID: <6A947BF0-FC05-4423-9EAA-A56F507ED451@cisco.com>
References: <CAMMESsyvuU8_dBOeoOXPBt=-HwoF0eHvYgm5d8CgF-4o_oiP=g@mail.gmail.com> <20190731211602.GA31271@pfrc.org> <119404A5-8384-456B-9677-0445899B008F@cisco.com> <20190801002911.GB31271@pfrc.org> <BYAPR11MB3751B2E90D5CBD559EBE319CC0DE0@BYAPR11MB3751.namprd11.prod.outlook.com>
In-Reply-To: <BYAPR11MB3751B2E90D5CBD559EBE319CC0DE0@BYAPR11MB3751.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1b.0.190715
authentication-results: spf=none (sender IP is ) smtp.mailfrom=enkechen@cisco.com;
x-originating-ip: [2001:420:c0c8:1001::625]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b60c32f0-99a4-41af-aaa2-08d71642b036
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BY5PR11MB4353;
x-ms-traffictypediagnostic: BY5PR11MB4353:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BY5PR11MB4353608C00B7B7E4E682DAC8C5DE0@BY5PR11MB4353.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01165471DB
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(376002)(39860400002)(366004)(346002)(136003)(396003)(199004)(189003)(13464003)(81156014)(4326008)(81166006)(8936002)(71200400001)(46003)(71190400001)(446003)(54906003)(66556008)(8676002)(110136005)(6506007)(186003)(316002)(58126008)(229853002)(476003)(2616005)(486006)(11346002)(102836004)(2906002)(36756003)(7736002)(305945005)(53546011)(66946007)(256004)(14444005)(66476007)(76116006)(76176011)(99286004)(25786009)(15650500001)(64756008)(66446008)(5660300002)(33656002)(86362001)(6436002)(6116002)(478600001)(966005)(6486002)(6512007)(6306002)(68736007)(14454004)(53936002)(6246003)(107886003); DIR:OUT; SFP:1101; SCL:1; SRVR:BY5PR11MB4353; H:BY5PR11MB3990.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX: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: 6KtwD3rmonG52s2s4lao6iEYnUpZLwYsUVYE1YIZ9IxSTXn4pQz/rRKkA3bBt9Ft9pYyZ+BKrwMQL37hRR8ebadcvC/Fv0S1vKReKhjLTiaBgk7DAs8GoAwYJEjsexexWnTdVHtVN8fyUTSY8fp1uAFCw60Mz26vUzUHf6Ze3nSGznwMfwxwpsEYqaVbVfiASwl6FU1Dlp1RQ82KycQuPjJyJ81DzVoqGo1KvXOHIzn2Z3nkqA30D+u4S4Qbc5MdXiAU5DK0i4osm+Us9CcGDGbNTE/ZetgkqSQsdU7dT2SiXBJBVGBqoP4bJcGRDm6lrA9Lr7zqlBgFvIlynHxO5hFQGAADeJ+enGdsmg06fyaiNsQa4FYFeM9iQggnAW/Ji/kDS6hOHR2ZZs5gJQxX17QXKsh0cV3LhklhzuGfY5k=
Content-Type: text/plain; charset="utf-8"
Content-ID: <69A0F8663D543444A46E78B9AAD87589@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b60c32f0-99a4-41af-aaa2-08d71642b036
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Aug 2019 05:39:57.4820 (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: BY5PR11MB4353
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.14, xch-rcd-004.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/fDhaWWSAOsz3YA9lXmkGNNxdlTI>
Subject: Re: [Idr] Capability Advertisement in draft-ietf-idr-bgp-extended-messages
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: Thu, 01 Aug 2019 05:40:07 -0000
Hi, Jakob: I am afraid what you just proposed would make the feature non-deployable ☹ 1) I suspect that for *a long time* there will some EBGP neighbors that don't have the capability enabled. Thus the speaker will not be able to send the large messages to any neighbors... 2) Also just imagine when one of the neighbors decide disables the capability ... Requiring "simultaneous configs" over a session always make it hard for the deployment of a feature, let alone synchronizing across many neighbors. Thanks. -- Enke -----Original Message----- From: "Jakob Heitz (jheitz)" <jheitz@cisco.com> Date: Wednesday, July 31, 2019 at 10:04 PM To: Jeffrey Haas <jhaas@pfrc.org>, "Enke Chen (enkechen)" <enkechen@cisco.com> Cc: "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "idr@ietf. org" <idr@ietf.org>, "draft-ietf-idr-bgp-extended-messages@ietf.org" <draft-ietf-idr-bgp-extended-messages@ietf.org>, Susan Hares <shares@ndzh.com> Subject: RE: [Idr] Capability Advertisement in draft-ietf-idr-bgp-extended-messages I'll raise you one. A single speaker in a network that is not capable of receiving extended messages will lead to a mess of (non-edge) cases. How about: A BGP speaker MUST NOT send the extended messages capability in an OPEN message to any BGP speaker if it has received an OPEN message without the extended message capability from any BGP speaker. A BGP speaker MUST delay sending an OPEN message to any BGP speaker by one keepalive interval if that OPEN message will contain the extended message capability and it has not yet received an OPEN message from every configured BGP speaker. The stated OPEN messages are understood to be of current or future BGP sessions, not of old sessions that have been taken down. This will reduce, but not completely eliminate the mess cases. Regards, Jakob. -----Original Message----- From: Idr <idr-bounces@ietf.org> On Behalf Of Jeffrey Haas Sent: Wednesday, July 31, 2019 5:29 PM To: Enke Chen (enkechen) <enkechen@cisco.com> Cc: idr-chairs@ietf.org; idr@ietf. org <idr@ietf.org>; draft-ietf-idr-bgp-extended-messages@ietf.org; Susan Hares <shares@ndzh.com> Subject: Re: [Idr] Capability Advertisement in draft-ietf-idr-bgp-extended-messages Enke, On Wed, Jul 31, 2019 at 09:50:08PM +0000, Enke Chen (enkechen) wrote: > >> Note that RFC 6793 (4-byte ASes) require bi-directional advertisement. > > No, this statement is not correct. It is fundamental (in transition) for a BGP speaker > to be able to talk to both NEW speakers (that have advertised the capability), and OLD > speakers (that have not advertised the capability). Different encodings are used in the > UPDATE message depending on whether the 4-byte AS capability is received from a > neighbor. I should have known I wasn't pedantic enough in this comment. :-) The point here is that in order to exercise the procedures between NEW BGP speakers, (RFC 6793, §4.1), both sides must advertise and use the capability. If you have a mix, each speaks 4271 to each other with the new speaker running the transitional procedures. With regard to the extended messaging, my preference is that both sides advertise the capability in order to use the large messages. A mis-match falling back to 4271 4k PDUs is fine - symmetrically. Asymmetrically sending extended messages leads to a mess of edge cases. -- Jeff _______________________________________________ Idr mailing list Idr@ietf.org https://www.ietf.org/mailman/listinfo/idr
- [Idr] Capability Advertisement in draft-ietf-idr-… Alvaro Retana
- Re: [Idr] Capability Advertisement in draft-ietf-… Jeffrey Haas
- Re: [Idr] Capability Advertisement in draft-ietf-… Enke Chen (enkechen)
- Re: [Idr] Capability Advertisement in draft-ietf-… Jeffrey Haas
- Re: [Idr] Capability Advertisement in draft-ietf-… Jakob Heitz (jheitz)
- Re: [Idr] Capability Advertisement in draft-ietf-… Enke Chen (enkechen)
- Re: [Idr] Capability Advertisement in draft-ietf-… Enke Chen (enkechen)
- Re: [Idr] Capability Advertisement in draft-ietf-… Jakob Heitz (jheitz)
- Re: [Idr] Capability Advertisement in draft-ietf-… Randy Bush
- Re: [Idr] Capability Advertisement in draft-ietf-… bruno.decraene
- Re: [Idr] Capability Advertisement in draft-ietf-… Randy Bush
- Re: [Idr] Capability Advertisement in draft-ietf-… Robert Raszuk
- Re: [Idr] Capability Advertisement in draft-ietf-… Keyur Patel
- Re: [Idr] Capability Advertisement in draft-ietf-… Jeffrey Haas
- Re: [Idr] Capability Advertisement in draft-ietf-… Susan Hares
- Re: [Idr] Capability Advertisement in draft-ietf-… Alvaro Retana
- Re: [Idr] Capability Advertisement in draft-ietf-… Robert Raszuk
- Re: [Idr] Capability Advertisement in draft-ietf-… Enke Chen (enkechen)
- Re: [Idr] Capability Advertisement in draft-ietf-… Enke Chen (enkechen)
- Re: [Idr] Capability Advertisement in draft-ietf-… Robert Raszuk