Re: [Idr] Changing the allocation policy for the BGP-LS registries
Donald Eastlake <d3e3e3@gmail.com> Fri, 26 July 2019 13:32 UTC
Return-Path: <d3e3e3@gmail.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 19126120133 for <idr@ietfa.amsl.com>; Fri, 26 Jul 2019 06:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level:
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 3-qF02LLbknK for <idr@ietfa.amsl.com>; Fri, 26 Jul 2019 06:32:18 -0700 (PDT)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (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 D371412012B for <idr@ietf.org>; Fri, 26 Jul 2019 06:32:17 -0700 (PDT)
Received: by mail-io1-xd31.google.com with SMTP id f4so104815697ioh.6 for <idr@ietf.org>; Fri, 26 Jul 2019 06:32:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=AR4cNxHof7gCnzTleAzfCLBgXs7zI7NsRA2zW5qOVag=; b=obmSMirGSSXJdARkIHvXkTSim3onIeO3ZbbhVTx3Hs2nhV4ThMxpibRKk3jWiqc0NW jFRDlktkwdiGurj4Mmn7SUz6hhlLvg9D2JVDuG5+ZIv5ZKtz0VvJKTcEh4hmLx0qjtm2 Gs+Mfa70CrMvreVZDaFQz3COX50zJmBCgWIMji3xADmkD48UIscAndUusg9Ip6R9J69V OInCqAmUNlrAUMaCNu6PNf8EKDUy/gyiSAXps9n11oeetIiJD2J55Zwsk2Y1sDl7mNfa d8Ji2eKlDpRhsMiQHl9FRTdavHxVXYRV/3Waniglu2zbwNWJyIzTi34HWHs/h+hvoi+d OXIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=AR4cNxHof7gCnzTleAzfCLBgXs7zI7NsRA2zW5qOVag=; b=cLYIIBzMYkGXUzk5cwd52eGy/IYaeV1k5OdHfrV1zmm010XEYN7V4oeeCER728Odcl h2f4qdYGfUe7O8CM/V58Iwtd0CbBkX+Tf6Vr/mav7b88QGJ9glaQ9CMmxt6ozCPaEjSc +rjI8pYlWXscNoMjfF/5GPAnw5+HZZrKnbqzvZeh+4tHY6DnP5OW8ufxIkpK54j9gYKf ap3wHeaDGQLYHeoIR1W9PLhsLQpnAtRcDKh9GpzCIlZ59oZ5glJZsacPk5krmxR7/Kt7 KkDI7MUSIRin1WKW7p+rUi2+Qzja6Dd5R7xhMujlLQyAPIla07NT4MaTJXZR/JgemdlC ifVw==
X-Gm-Message-State: APjAAAWuQOib7iprTHDDSAiIf8ek5h8jXQ1QJL4VPZreevigKmIhzcTp B+qcOsQEGyqC0ewBBMQRKFsNb0naRPnhKgVZyPaEi+iG8vM=
X-Google-Smtp-Source: APXvYqyUwl/povFyaOBDk5/oWHMc0KOJRfhauLZJRSe0VBWqsz3czGqNxvHkAcSSYZjeRXD59+ux/OoyvDfr1VxdRA4=
X-Received: by 2002:a02:cd82:: with SMTP id l2mr95993714jap.96.1564147937019; Fri, 26 Jul 2019 06:32:17 -0700 (PDT)
MIME-Version: 1.0
References: <0ab001d543a8$a2fbdf00$e8f39d00$@olddog.co.uk>
In-Reply-To: <0ab001d543a8$a2fbdf00$e8f39d00$@olddog.co.uk>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 26 Jul 2019 09:32:05 -0400
Message-ID: <CAF4+nEHS5b_frvGnL_HRoGrxwyLyf_KD46hdodiRaeD-2_kyww@mail.gmail.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Cc: idr wg <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000298d31058e9592d2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/76o0uF1tahNFnAhrRh-W7fDuSQU>
Subject: Re: [Idr] Changing the allocation policy for the BGP-LS registries
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: Fri, 26 Jul 2019 13:32:21 -0000
Hi Adrian, When a registry is Expert Review, the normal flow is that requests are sent to IANA who selects an Expert from the pool of Expert. The Expert evaluates the request and returns an approval/disapproval. IANA then assigned the code point(s) or not. The general escape mechanism for denial of service attacks or other abuse is for IANA to go to the IESG. See the last paragraph of Section 3.3 of RFC 8126: IANA always has the discretion to ask the IESG for advice or intervention when they feel it is needed, such as in cases where policies or procedures are unclear to them, where they encounter issues or questions they are unable to resolve, or where registration requests or patterns of requests appear to be unusual or abusive. Generally speaking, the IESG is considered to be a permanent body while, notwithstanding the apparent immortality of the IDR WG, Working Groups are considered to be ephemeral. Thus the provision in this draft naming the IDR Working Group seems problematic to me. The way this is handled for DNS, where community discussion is desired of requests for RRTYPE assignments, is to name a specific mailing list that the request must be posted to. Mailing lists can be immortal. (See Sections 3.1 and Appendix A of RFC 6895.) So, I think the draft is a good idea but needs some tweaking based on the above. Thanks, Donald =============================== Donald E. Eastlake 3rd +1-508-333-2270 (cell) 1424 Pro Shop Court, Davenport, FL 33896 USA d3e3e3@gmail.com On Fri, Jul 26, 2019 at 7:53 AM Adrian Farrel <adrian@olddog.co.uk> wrote: > > Hi team IDR, > > I'm one of the two Designated Experts for these registries. > > Chatting with the chairs yesterday there was a suggestion that we might > change (relax) the allocation policy for the registries. > > This draft is a straw man to do that. > > Discuss! > > Best, > Adrian > -- > Read some fairy stories for adults of all ages > .. Tales from the Wood > .. More Tales from the Wood > .. Tales from Beyond the Wood > .. Tales from the Castle > Get them on line https://www.feedaread.com/profiles/8604/ > Or buy a signed copy from me by post > *** Stop me in the corridor at IETF-105 to get a copy *** > > > > -----Original Message----- > From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of > internet-drafts@ietf.org > Sent: 26 July 2019 11:47 > To: i-d-announce@ietf.org > Subject: I-D Action: draft-farrel-idr-bgp-ls-registry-00.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : Updates to the Allocation Policy for the Border > Gateway Protocol - Link State (BGP-LS) Parameters Registries > Author : Adrian Farrel > Filename : draft-farrel-idr-bgp-ls-registry-00.txt > Pages : 4 > Date : 2019-07-26 > > Abstract: > RFC 7752 defines Border Gateway Protocol - Link State (BGP-LS). IANA > created a registry consistent with that document called the "Border > Gateway Protocol - Link State (BGP-LS) Parameters Registry" with a > number of sub-registries. The allocation policy applied by IANA for > those policies is "Specification Required" as defined in RFC 8126. > > This document updates RFC 7752 by changing the allocation policy for > all of the registries to "Expert Review." > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-farrel-idr-bgp-ls-registry/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-farrel-idr-bgp-ls-registry-00 > https://datatracker.ietf.org/doc/html/draft-farrel-idr-bgp-ls-registry-00 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > _______________________________________________ > Idr mailing list > Idr@ietf.org > https://www.ietf.org/mailman/listinfo/idr
- [Idr] Changing the allocation policy for the BGP-… Adrian Farrel
- Re: [Idr] Changing the allocation policy for the … Donald Eastlake
- Re: [Idr] Changing the allocation policy for the … Donald Eastlake
- Re: [Idr] Changing the allocation policy for the … Adrian Farrel