Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-communities-06.txt (2/4/2022 to 2/18/2022)
Job Snijders <job@fastly.com> Mon, 07 February 2022 14:28 UTC
Return-Path: <job@fastly.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 B0E583A0888 for <idr@ietfa.amsl.com>; Mon, 7 Feb 2022 06:28:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastly.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 J6iUO9Btbn0N for <idr@ietfa.amsl.com>; Mon, 7 Feb 2022 06:28:24 -0800 (PST)
Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 130BF3A07F5 for <idr@ietf.org>; Mon, 7 Feb 2022 06:28:24 -0800 (PST)
Received: by mail-ed1-x52e.google.com with SMTP id eg42so14680709edb.7 for <idr@ietf.org>; Mon, 07 Feb 2022 06:28:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=+gHI1AFk7nlTuDASIwJQi0jSwk9wLsxEEHT5GaFLmM0=; b=gnebQ97TgBCQoAKCLpIvF635pKywxDyQsy8FDDrn11/dAy6Ra/ZK8rkjlVzrYGUiWn aXdG0VfVC/NWkHTO9+ATvq6I61v1JxS4rZkiMngWXvCX2c2Gc1ylwHVN785t2NoRyyYm ytBChfYPHLudze/NvPublb9RkNtubnUp4QOk8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=+gHI1AFk7nlTuDASIwJQi0jSwk9wLsxEEHT5GaFLmM0=; b=vCq+ffztXnBdOvNfpRQb0wJslhpuxEtDpAxHYkwqzbk4WLtZ54ptIL66y6pSydcN75 VHE3Ro9OhKFuJ5YVv24rOvngYoRjGGUk27fQ//L55Pta/44aT6dHsgtV6FBXMRfquSLC 6RmpUwp4rf3e3b9wjEZV9BHeL89+yU+bkzeAo0Quec0TETxBKIQ3y6cjCTyce/t/KDkQ mXmwhmc6Xndor4g0mXqkrRo8vdnMl1ml0IdtllyAKlDgUXv4SiOG2XD5u68sThb6CBjZ 5lZPVEwkYSGa9sllb3nuctNwACAr9GFPs0umeW4TJqEXfVOCJonezBLUt9UjqzmXPp6/ 3IfA==
X-Gm-Message-State: AOAM530yltorGmnYG+pFojiLK4pTFZa5WW1wRqmv/6LmYDGz//pYvuTI 3pQXulWfu35P4MkBQUyBGrGQJg==
X-Google-Smtp-Source: ABdhPJxs75TRLHXPK0/Pg4QfQt0o+4yc1ZEWVtQ93psy2zrkTIqko9z/rrOOsaShUPGGOCU190xvSw==
X-Received: by 2002:a05:6402:34c2:: with SMTP id w2mr14086871edc.357.1644244100756; Mon, 07 Feb 2022 06:28:20 -0800 (PST)
Received: from snel ([2a10:3781:276:2:16f6:d8ff:fe47:2eb7]) by smtp.gmail.com with ESMTPSA id gv34sm3721449ejc.125.2022.02.07.06.28.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 07 Feb 2022 06:28:20 -0800 (PST)
Date: Mon, 07 Feb 2022 15:28:18 +0100
From: Job Snijders <job@fastly.com>
To: Keyur Patel <keyur@arrcus.com>
Cc: "idr@ietf.org" <idr@ietf.org>
Message-ID: <YgEsgptvEKG5pxHJ@snel>
References: <CAF2D873-5504-4376-9947-8BE1C19034F9@arrcus.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAF2D873-5504-4376-9947-8BE1C19034F9@arrcus.com>
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/J80VIGo8yP5_fzw_CVf9UTt1zFY>
Subject: Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-communities-06.txt (2/4/2022 to 2/18/2022)
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: Mon, 07 Feb 2022 14:28:34 -0000
Dear IDR chairs & working group, On Fri, Feb 04, 2022 at 04:27:57PM +0000, Keyur Patel wrote: > The working group last call has been issued for > draft-ietf-idr-wide-bgp-communities-06.txt, “BGP Community Container > Attribute”. Please reply to the list with your comments. This > adoption call will conclude on February 18th, 2022. > > The draft can be found at: > https://datatracker.ietf.org/doc/draft-ietf-idr-wide-bgp-communities/. > The implementation report for the draft can be found at: > https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-wide-bgp-communities. IDR tradition is to demand multiple interopable implementations exist before a document can progress towards the RFC publication status. I noticed that large parts of the draft are NOT implemented by either of the two implementations; such as: * support for T/C/R bits (section 3.1) * no targets * atoms (both 4.4.1 + 4.4.2) * RouterAttr_ While the implementation report available to us indicates that some of the features are "optional", this does not relief us from the burden of demonstrating that the "optional" feature can actually be implemented in an interoperable way. As such, the path forward is either to implement the optional features, or to remove the text from the Internet-Draft and spin it off into a separate Internet-Draft (which in turn could proceed if implementations ever show up). I strongly believe that IDR, SIDROPS, and other inter-domain working groups should not ship any text (as part of large docs) which is not directly or indirectly covered in an interopability matrix. E.g. I don't see an issue if there are 3 features, and implementation A covers features 1+2, B covers 2+3, and C covers 3+1 - in such scenarios the full feature set has multiple implementations. Unfortunately this does not appear to be the case for the 'wide communities' document. Many in this working group will probably remember that flexible/wide communities were somewhat contentious because of perceived complexity - the lack of full coverage in implementation reports, and the presence of merely 2 half implementations does not increase confidence that publication of this document will benefit operators in the long term. It is also entirely possible I am misreading the implementation report! I look forward to hear other people's thoughts on this matter. Kind regards, Job ps. I do not mind the two implementations coming from the same vendor house; I trust the two product lines to be sufficiently distinct to be viewed as independently developed implementations.
- [Idr] WG LC on draft-ietf-idr-wide-bgp-communitie… Keyur Patel
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Huaimo Chen
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Jeff Tantsura
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Gyan Mishra
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Robert Raszuk
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Melchior Aelmans
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Zhuangshunwan
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… bruno.decraene
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Job Snijders
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Robert Raszuk
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Job Snijders
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Robert Raszuk
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Huaimo Chen
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Job Snijders
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Susan Hares
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Susan Hares
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Robert Raszuk
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Susan Hares
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… 'Job Snijders'
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Huaimo Chen
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… 'Job Snijders'
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Huaimo Chen
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Susan Hares
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Robert Raszuk
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Linda Dunbar
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Job Snijders
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Lange, Andrew (Nokia - US)
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Gyan Mishra
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… lizhenqiang@chinamobile.com
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Wanghaibo (Rainsword)
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Lizhenbin
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… UTTARO, JAMES
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… xufeng@voltanet.io
- Re: [Idr] WG LC on draft-ietf-idr-wide-bgp-commun… Dongjie (Jimmy)
- Re: [Idr] Closed -- WG LC on draft-ietf-idr-wide-… Keyur Patel