Re: [Idr] Notification Subcode Squatting (draft-ietf-idr-bgp-open-policy)
Jeffrey Haas <jhaas@pfrc.org> Tue, 21 December 2021 19:56 UTC
Return-Path: <jhaas@pfrc.org>
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 E11133A12A9; Tue, 21 Dec 2021 11:56:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 ibUj66jgv8gN; Tue, 21 Dec 2021 11:56:31 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 2B4573A12B4; Tue, 21 Dec 2021 11:56:31 -0800 (PST)
Received: from smtpclient.apple (99-59-193-67.lightspeed.livnmi.sbcglobal.net [99.59.193.67]) by slice.pfrc.org (Postfix) with ESMTPSA id D920C1E2F5; Tue, 21 Dec 2021 14:56:29 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <BYAPR11MB3415CC196829687988EEAF51C47C9@BYAPR11MB3415.namprd11.prod.outlook.com>
Date: Tue, 21 Dec 2021 14:56:29 -0500
Cc: Sue Hares <shares@ndzh.com>, Alvaro Retana <aretana.ietf@gmail.com>, "idr@ietf.org" <idr@ietf.org>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "draft-ietf-idr-bgp-open-policy@ietf.org" <draft-ietf-idr-bgp-open-policy@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F847EA24-A338-4DB3-995D-98CF7DC7F506@pfrc.org>
References: <CAMMESsw_0+m2FKMkH1wvASM8uqj0y9cbEU7Wsi=g-fBGGzqMHw@mail.gmail.com> <013201d7f4ee$e7d70060$b7850120$@ndzh.com> <BYAPR11MB3415CC196829687988EEAF51C47C9@BYAPR11MB3415.namprd11.prod.outlook.com>
To: "Jeffrey Chiang (jefchian)" <jefchian=40cisco.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ldNKaRnTSMTZxy0v31zEKFmBOHI>
Subject: Re: [Idr] Notification Subcode Squatting (draft-ietf-idr-bgp-open-policy)
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, 21 Dec 2021 19:56:36 -0000
Jeffrey, Could you confirm there are no other unregistered subcodes in use for any of your notifications while you're in there? :-) -- Jeff (who audited Juniper's suite a while back but will do so again after the new year) > On Dec 20, 2021, at 8:20 PM, Jeffrey Chiang (jefchian) <jefchian=40cisco.com@dmarc.ietf.org> wrote: > > Cisco has implemented https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-multisession-07 many years ago. We are using the subcodes as stated in the draft, but offset by one, because at the time (and now still), subcode 7 was already used. They are > 8 - Capability Value Mismatch (was called "No Supported AFI/SAFI" in version 00) > 9 - Grouping Conflict > 10 - Grouping Required > We would like to resurrect the draft and progress it to RFC. > Are there any other implementations? > > Regards, > Jeffrey > > -----Original Message----- > From: Idr <idr-bounces@ietf.org> On Behalf Of Susan Hares > Sent: Sunday, December 19, 2021 7:41 AM > To: 'Alvaro Retana' <aretana.ietf@gmail.com>; idr@ietf.org > Cc: idr-chairs@ietf.org; draft-ietf-idr-bgp-open-policy@ietf.org > Subject: Re: [Idr] Notification Subcode Squatting (draft-ietf-idr-bgp-open-policy) > > Alvaro: > > Documenting what is out there and pragmatism is the best policy. > > Q1. Something else > > If Cisco has been squatting on the subcode 8, cisco experts should let us know: 1) how widely it is deployed, and 2) how difficult to change. > If Bird, the same questions apply. > > Pragmatism > > Q2. (b) Deprecating the code and (c) working with pragmatism to get actual implementations to registered code. > > > Sue > > PS - +1 to what Jeff Haas says as well. > > > -----Original Message----- > From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Alvaro Retana > Sent: Wednesday, December 15, 2021 3:53 PM > To: idr@ietf.org > Cc: idr-chairs@ietf.org; draft-ietf-idr-bgp-open-policy@ietf.org; Susan Hares > Subject: [Idr] Notification Subcode Squatting (draft-ietf-idr-bgp-open-policy) > > Dear idr WG: > > draft-ietf-idr-bgp-open-policy is currently in IETF Last Call. > > This document specifies a new Role Mismatch Notification (code 2, subcode 8). This value was initially allocated by IANA in 2018 [1]. > > Unfortunately, Alexander (cc'd) just pointed out that BIRD uses the same code and subcode combination for a Notification in the case where an AFI/SAFI is not supported. :-( As far as I can tell, no such Notification is specified anywhere. However, a quick search points at cisco potentially implementing the same functionality [2] [3] [4] -- some of these reports go as far back as 2010. > > > What now? > > Given that there seem to be multiple deployed implementations that use this code/subcode combination, we should avoid using it even if they are squatting on it. :-( Also, BIRD was one of the two reported implementations for draft-ietf-idr-bgp-open-policy. So I propose that we request IANA to assign a different value for the new Notification specified in this document. > > Before moving forward, I want to confirm that the WG agrees with the proposal. Please take a look at the questions below. I would like to hear from implementers at BIRD and cisco (and any other that I didn't find that might be in the same situation), and from FRR (the second implementation of draft-ietf-idr-bgp-open-policy). > > > Q1: Should a new subcode be requested for the Role Mismatch Notification > specified in draft-ietf-idr-bgp-open-policy? > > [ ]: Yes. > [ ]: No, the squatters should update their implementations. > [ ]: Something else. > > > Q2: What should we do with subcode 8? > > [ ]: It should be deprecated (i.e., no one can use it). > [ ]: Write a specification for an "unsupported AFI/SAFI" Notification. > [ ]: Something else. > > > I will keep this poll open until Jan/5, 2022. > > > Thanks! > > Alvaro. > > > > [1] https://www.iana.org/assignments/bgp-parameters/bgp-parameters.xhtml#bgp-parameters-6 > > [2] https://community.cisco.com/t5/routing/bgp-3-notification-erro/td-p/1572684 > > [3] https://www.wireshark.org/lists/wireshark-bugs/201607/msg00164.html > > [4] https://bst.cloudapps.cisco.com/bugsearch/bug/CSCsu79206 > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr
- [Idr] Notification Subcode Squatting (draft-ietf-… Alvaro Retana
- Re: [Idr] Notification Subcode Squatting (draft-i… Jeffrey Haas
- Re: [Idr] Notification Subcode Squatting (draft-i… Job Snijders
- Re: [Idr] Notification Subcode Squatting (draft-i… Susan Hares
- Re: [Idr] Notification Subcode Squatting (draft-i… Jeffrey Chiang (jefchian)
- Re: [Idr] Notification Subcode Squatting (draft-i… Gyan Mishra
- Re: [Idr] Notification Subcode Squatting (draft-i… Jeffrey Haas
- Re: [Idr] Notification Subcode Squatting (draft-i… Alvaro Retana