Re: [Idr] Capability Advertisement in draft-ietf-idr-bgp-extended-messages

Keyur Patel <keyur@arrcus.com> Thu, 01 August 2019 18:36 UTC

Return-Path: <keyur@arrcus.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 309BE120059; Thu, 1 Aug 2019 11:36:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netorgft1331857.onmicrosoft.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 3wV0NXDtvoVl; Thu, 1 Aug 2019 11:36:47 -0700 (PDT)
Received: from NAM05-CO1-obe.outbound.protection.outlook.com (mail-eopbgr720056.outbound.protection.outlook.com [40.107.72.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F4DE1200E5; Thu, 1 Aug 2019 11:36:47 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OKvKwgbT9VeEjuaLdFkR8saWYCBYtq1eT/T518Fc0yBqhNUosQvR+JmkudPPUx83eYndhgbC8PWRkNJN1XbeiIj92uada12vdJDHitHKva1pcRYFvFxHIoXdQfxbQrR7wr205FLeOP1x8XQW4TYKnl6W47YkDwgEaSbLVKieBqzX8DYi+LEau8EiD8VgLvr0J0ln/Z62kcVBP0l1SzokZD6JHKJppkp8XGpJJqRHVsYQygDwZSZpg/P9yzH3dOQc6E+ADUZ8FB9qwecb/cMFPeVKvlBBUDLDDiBc58Le0uqr6YTYyWUWsn8K9+Bs0OgxweZrWAkmJC8kwiK5fgKitA==
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=1KNqk0C3W6JP8RitnVm+o6EIuAoTrvA9bcr6q/09NAc=; b=lZiO+S7jWT+VaeSwiZBi0uG3jq47NoNnmNocAiPozNq0VGzpshA2SqcZOJ+qRSLVOr0tFKDYENOHVIzuzIDmxcG1uWragboWvsDF6OtTY2zV9MxnKchyVQh9vk3aUpHhc36UclgArJH4ug4cl3S7IdMDwMa0dlCeOTyV1ta7ZiXHJoc/JsZ/e4bIIfvV+diSJ+BMM7fqPlNmn17UtlMbaMlk8qHWKmJ4n4G2cQArO1ohUBWKwllqetnL8zTlUBMASthaf+mP9QejCvx4cvlgNIW8JgmrvS0eOgXkxJR2jcDb7xWwCZQiuFHCAuNjD4osziJO90Ob6jm9Rk0Oj9Wjwg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=arrcus.com;dmarc=pass action=none header.from=arrcus.com;dkim=pass header.d=arrcus.com;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=NETORGFT1331857.onmicrosoft.com; s=selector2-NETORGFT1331857-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1KNqk0C3W6JP8RitnVm+o6EIuAoTrvA9bcr6q/09NAc=; b=QUVafkOmqsSvGJ4Eg0+LftYXMJTH91MYA3LsynT/ThecS8E9HAGWhNvGboKczHWwwYPxEjHT0ZtxKh74cSer1sD2EJMuOrc7s+8WNfdour2btVtygwIy5k5oCF5VVzLo0Pn+BsyLyWSWWD3cVw9P2W+/pwt55c40MuZAQ4LBhRw=
Received: from BYAPR18MB2856.namprd18.prod.outlook.com (20.179.58.82) by BYAPR18MB2885.namprd18.prod.outlook.com (20.179.58.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.15; Thu, 1 Aug 2019 18:36:45 +0000
Received: from BYAPR18MB2856.namprd18.prod.outlook.com ([fe80::bda4:9376:3493:56c2]) by BYAPR18MB2856.namprd18.prod.outlook.com ([fe80::bda4:9376:3493:56c2%7]) with mapi id 15.20.2136.010; Thu, 1 Aug 2019 18:36:45 +0000
From: Keyur Patel <keyur@arrcus.com>
To: "Jakob Heitz (jheitz)" <jheitz@cisco.com>, 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>
Thread-Topic: [Idr] Capability Advertisement in draft-ietf-idr-bgp-extended-messages
Thread-Index: AQHVR9tp5bnPkmykrkCF+Ld4vHgCoKblOpkAgAAJhwCAACxwgIAATPSAgABtjwA=
Date: Thu, 1 Aug 2019 18:36:44 +0000
Message-ID: <2CC53E18-EB23-4E07-BFF9-D58E5424ACE0@arrcus.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:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=keyur@arrcus.com;
x-originating-ip: [70.234.233.188]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: e22ed27b-db8d-44ae-ae4c-08d716af3474
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR18MB2885;
x-ms-traffictypediagnostic: BYAPR18MB2885:
x-microsoft-antispam-prvs: <BYAPR18MB28857A60DE20CB9FBEC4A95DC1DE0@BYAPR18MB2885.namprd18.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01165471DB
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39840400004)(136003)(366004)(376002)(346002)(199004)(189003)(13464003)(66946007)(4326008)(66446008)(36756003)(6246003)(64756008)(66556008)(66476007)(5660300002)(305945005)(7736002)(256004)(81166006)(81156014)(486006)(2906002)(476003)(11346002)(66066001)(316002)(33656002)(8936002)(86362001)(110136005)(54906003)(446003)(2616005)(3846002)(6116002)(14454004)(53546011)(26005)(6506007)(68736007)(53936002)(76176011)(99286004)(6436002)(6486002)(76116006)(102836004)(71190400001)(71200400001)(8676002)(186003)(25786009)(229853002)(6512007)(15650500001)(508600001); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR18MB2885; H:BYAPR18MB2856.namprd18.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: arrcus.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: fO1ubrDo7GxfQCIKUAuM4Wa8//1uOsyW7WhjVUnNPAvyvjXkcO0bgt8hS5vdzsLY+lLcpuh6bqvDrbFA7Avdoy8/B/i0CkaDhF/AXLQB43CfbMlbWS2ZC+RdsexurPpMUDUj77h7TTo1X3hlA+N7n+sTxmyEwCCugx/FJyh4nguk4V9qiaNfKcPIojrMgiH9ER1U/S1clNVgi/B3Jx4oNTa+6L99aRnK0injaSlcyCJrsf1CAqpqlXpmU9xN/z0OJcclTE+08mYL9LvH80sXe9VQL/1btppJmu1Ih8VnkTOFFiym/eM2bnII3ziQGlqk7UFsJX97H0mkVXV+NhKocHwiUWjMTobFQrH/4WjZa9XeUVfZPgYicfQPncOBqvkJXN0JNEjvvBcctoufFICZIcx5gAS58MYAWG+tsAMwSD0=
Content-Type: text/plain; charset="utf-8"
Content-ID: <94EA3FCDDE34A749946284DB2BCFEE6B@namprd18.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: arrcus.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e22ed27b-db8d-44ae-ae4c-08d716af3474
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Aug 2019 18:36:44.9055 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 697b3529-5c2b-40cf-a019-193eb78f6820
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: keyur@arrcus.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR18MB2885
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/7vAxUF6OgN80vk1oghl0nuE_XPE>
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 18:36:52 -0000

I don’t think this level is strictness is needed. A bgp speaker is capable of sending messages only to those speakers with whom it has exchanged capabilities. 

On 7/31/19, 10:04 PM, "Jakob Heitz (jheitz)" <jheitz@cisco.com>; wrote:

    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