[Idr] Changing the allocation policy for the BGP-LS registries

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 26 July 2019 11:52 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id ACD75120317 for <idr@ietfa.amsl.com>; Fri, 26 Jul 2019 04:52:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id E1bSov3quJ9r for <idr@ietfa.amsl.com>; Fri, 26 Jul 2019 04:52:49 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C51E12031C for <idr@ietf.org>; Fri, 26 Jul 2019 04:52:48 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com []) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id x6QBqkqq016618 for <idr@ietf.org>; Fri, 26 Jul 2019 12:52:46 +0100
Received: from vs3.iomartmail.com (unknown []) by IMSVA (Postfix) with ESMTP id 5C7062203A for <idr@ietf.org>; Fri, 26 Jul 2019 12:52:45 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown []) by vs3.iomartmail.com (Postfix) with ESMTPS id 47A3A22032 for <idr@ietf.org>; Fri, 26 Jul 2019 12:52:45 +0100 (BST)
Received: from LAPTOPK7AS653V ([]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id x6QBqhBu018086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <idr@ietf.org>; Fri, 26 Jul 2019 12:52:44 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'idr wg'" <idr@ietf.org>
Date: Fri, 26 Jul 2019 12:52:42 +0100
Organization: Old Dog Consulting
Message-ID: <0ab001d543a8$a2fbdf00$e8f39d00$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-Product-Ver: IMSVA-
X-TM-AS-Result: No--18.616-10.0-31-10
X-imss-scan-details: No--18.616-10.0-31-10
X-TMASE-Result: 10--18.615700-10.000000
X-TMASE-MatchedRID: P91FwNUhsTxtf00mfgWygqJVTu7sjgg1c1tWSEjKtCPYzrtfmGrd4imJ Jz1i9Oa+Cr1jbh1tiICMZEL1McgH2rjAlyhiLbFWMpVOsYwN78O6RT5cFp54ymNDqjXOO0YenLx Qb6qDSvs6kayhM9Vk/vI20EwvUhtqUIac17N84UqdVNZaI2n6/wVyeo9hM9SHVYXF0d2fUVnTc/ sT0qtBNtJL4TMt4sMwNzEl8hyfFn3u3/vWgZeBHfizkVL8JSXbGbJMFqqIm9wP75yVmSHRgFpq2 K/Emlk1SigCc/Xd+DTHBvqhRdA8skcektnBd6J6rHi4Tq/VwTogT/sXtGXrf2tEzrC9eANpWiMH 3xEQxoPr7B4BsaM0lCwFWNfPp1pFsvWDuWpU+ZEdt2/pSR7zwPXuWpt5ue195Gmp8Ji1bXPEBpj owVhUR+QIqkSHEKcwFUKlOh2bR0t8MMUv6gq5XoicBKfMHlV8V7J1rOWMhubB8fZdmGC6EIryaz G1GFY77KPXJ/mtxsPiBiWevqr/K01+zyfzlN7y/sToY2qzpx66wydv7pFISbDszp3K5gqDjoczm uoPCq2UTGVAhB5EbQ==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/l_ATr0ElizsFViJYgHU-Ebkpgl4>
Subject: [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 11:52:52 -0000

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.


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
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

        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

   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:

There are also htmlized versions available at:

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:

I-D-Announce mailing list
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt