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 03:39 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 391821201C7 for <idr@ietfa.amsl.com>; Mon, 1 Jul 2019 20:39:15 -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=FhMuET5B; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=laQTHV5P
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 oUK_uQRXgnEV for <idr@ietfa.amsl.com>; Mon, 1 Jul 2019 20:39:13 -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 64DD11200D7 for <idr@ietf.org>; Mon, 1 Jul 2019 20:39:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2168; q=dns/txt; s=iport; t=1562038753; x=1563248353; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=521/MiO/hwsvu3Q+3wiXdiu29IdZJ9ZeXjI6zwuW9Cg=; b=FhMuET5BA0nDSsupZQ8VtNREZ5AJr0wipGA7xYdX4kz8dkzGKoJvEVvq os2dokVp7TbIpzNsk+fw2R2AKgF803nyK0TdZDzVgO0mBGuyRxFobd2bS XH2RXbvhDrD7Z0HyOj0kK/xIm28TzRxaH7OF6eOg9vsQj6oLhBTzAnBAy E=;
IronPort-PHdr: 9a23:8w5IshWLN6PfR6VNzzu71o0hmJnV8LGuZFwc94YnhrRSc6+q45XlOgnF6O5wiEPSA9yJ8OpK3uzRta2oGXcN55qMqjgjSNRNTFdE7KdehAk8GIiAAEz/IuTtank3GsdPX19o+VmwMFNeH4D1YFiB6nA=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DrAAAy0Rpd/51dJa1lHQEBBQEHBQGBVQYBCwGBQ1ADgT8gBAsohByDRwOOXoJbl0SBLoEkA1QJAQEBDAEBLQIBAYRAAheCayM2Bw4BAwEBBAEBAgEFbYo3DIVLAQEBAgESEREMAQE3AQ8CAQYCGgIZDQICAjAVEAIEDgUigwCBawMODwECiUyQYAKBOIhgcYEygnkBAQWCR4JKGIISCYEMKAGLXheBQD+BEScfgkw+hESDCjKCJowOglWbUQkCghaTexuXa6RYAgQCBAUCDgEBBYFXBSyBWHAVZQGCQYJBg3GKU3KBKY09AQE
X-IronPort-AV: E=Sophos;i="5.63,441,1557187200"; d="scan'208";a="589714338"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 Jul 2019 03:39:12 +0000
Received: from XCH-ALN-012.cisco.com (xch-aln-012.cisco.com [173.36.7.22]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id x623dC2d022780 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 2 Jul 2019 03:39:12 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-ALN-012.cisco.com (173.36.7.22) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 1 Jul 2019 22:39:11 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 1 Jul 2019 22:39:11 -0500
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 1 Jul 2019 23:39:11 -0400
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=521/MiO/hwsvu3Q+3wiXdiu29IdZJ9ZeXjI6zwuW9Cg=; b=laQTHV5PwYPQIYuU7eORZbF8zqq7pFXsuLdaRVFt4hKOb9F0vxEw9/pjKdu5eR5v6cFYJ1YIYXCUNFFlRVQJpGXnYfrxY55J6K86xxLJkva+Odu1u2NTs76qOhJcWzCm54bQwH3+Vuj1M9t3tfdmTLP7ceE6EUABdieAPyeZEA8=
Received: from DM6PR11MB3995.namprd11.prod.outlook.com (20.176.125.20) by DM6PR11MB3083.namprd11.prod.outlook.com (20.177.218.212) 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 03:39:09 +0000
Received: from DM6PR11MB3995.namprd11.prod.outlook.com ([fe80::2d85:9d53:b804:9d64]) by DM6PR11MB3995.namprd11.prod.outlook.com ([fe80::2d85:9d53:b804:9d64%3]) with mapi id 15.20.2008.018; Tue, 2 Jul 2019 03:39:09 +0000
From: "Enke Chen (enkechen)" <enkechen@cisco.com>
To: 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//+1tYA=
Date: Tue, 02 Jul 2019 03:39:09 +0000
Message-ID: <F41665B6-DD53-42F5-AD1D-F828C215809B@cisco.com>
References: <FDAC847D-60A2-4571-99CF-50458AC0E159@cisco.com> <m21rz9xn46.wl-randy@psg.com>
In-Reply-To: <m21rz9xn46.wl-randy@psg.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: 52649d0c-aa41-426e-3dd9-08d6fe9ed7bf
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:DM6PR11MB3083;
x-ms-traffictypediagnostic: DM6PR11MB3083:
x-microsoft-antispam-prvs: <DM6PR11MB3083021EBEAC5EB4E22DA267C5F80@DM6PR11MB3083.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 008663486A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(396003)(39860400002)(366004)(346002)(376002)(199004)(189003)(6436002)(6246003)(33656002)(5660300002)(68736007)(36756003)(86362001)(58126008)(486006)(64756008)(73956011)(446003)(2616005)(66446008)(476003)(76176011)(6486002)(316002)(14454004)(25786009)(8936002)(7736002)(99286004)(478600001)(6916009)(66946007)(66476007)(66556008)(2906002)(102836004)(186003)(8676002)(229853002)(256004)(54906003)(46003)(6512007)(107886003)(305945005)(76116006)(4326008)(11346002)(81156014)(15650500001)(71200400001)(81166006)(71190400001)(6506007)(91956017)(53936002)(6116002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR11MB3083; H:DM6PR11MB3995.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: E4w7KbYyK7Tqmq7ig8pyPTtxrcBJMOXx67k4bK9aeoG6pmuul9xF8Y5rC5lQLBS7u4lj+v5EAfhhmQGHQJkhWKou7/vzE8VDResL1IIV7Q7Bj/j8gHWoSCuRqsCM2uMuczTGR0ht4A4uNShhVfeMaoCDJGJJlPc0o6gkW3ZK7f7Ah2ouvSQdVT6EwQKxcghpxabT6ItMVUyvPH08kGWO7lqWq+jPhlkJ+w+D2EMEc4R+f7mL6Mx7xrQAu8yDk3doZuOGHf7CzPNA2tR83fRCI5bWSgzYiLUdo18V/Q4fBdfBB2MkdhkALFYUk22y0xdde77Jexderuhl91TQ5D4nDr5OzsPd4DBrcvR5AaDir3atGtO4QAasti2lX/Y3TiwZmQiwY/dr3VJjtniWIJNuJfaP399nPWaXo/AZ1qF743Y=
Content-Type: text/plain; charset="utf-8"
Content-ID: <9B7A1E01BB3099479A46EBD1D7F68411@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 52649d0c-aa41-426e-3dd9-08d6fe9ed7bf
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Jul 2019 03:39:09.6376 (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: DM6PR11MB3083
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.22, xch-aln-012.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/NMH9pQTTvz5Qlyq4lwGefp_xQy4>
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 03:39:15 -0000

Hi, Randy:

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.

Thanks.  -- Enke

On 7/1/19, 6:05 PM, "Randy Bush" <randy@psg.com> wrote:

    > Apologies for being late in the review cycle of this document.  But I
    > have a basic question about the BGP capability defined in Sect 3:
    > 
    > --
    >    By advertising the BGP Extended Message Capability to a peer, a BGP
    >    speaker conveys that it is able to send, receive, and properly
    >    handle, see Section 4, BGP Extended Messages.
    > --
    > 
    > The text “… to send” does not seem to be necessary, and the spec would
    > be simpler and cleaner without it.
    > 
    > IMO the capability should be about “receiving” only. As long as a BGP
    > speaker is able and willing to receive large messages (by advertising
    > the capability), its neighbor would be allowed to send such messages
    > to the speaker. It really does not matter whether the speaker is able
    > / willing / need to send any large messages to its neighbors.  (Of
    > course certain “Operational” considerations still apply, especially
    > for IBGP, as discussed in the document.)
    > 
    > What do folks think?
    
    we weny around this at least twice during the wg process.  there was a
    dislike of the possibility of extended messages being unidirectional,
    error reporting, etc.
    
    but i have no dog in this fight
    
    randy