Re: [Idr] Requesting WG adoption for draft-scudder-idr-capabilities-registry-change-02.txt

Jeff Tantsura <> Thu, 20 September 2018 15:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5AC22130DD9; Thu, 20 Sep 2018 08:17:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2av98IC4Kzkf; Thu, 20 Sep 2018 08:17:38 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::536]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 237901277CC; Thu, 20 Sep 2018 08:17:38 -0700 (PDT)
Received: by with SMTP id r1-v6so4577108pgp.11; Thu, 20 Sep 2018 08:17:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :mime-version:content-transfer-encoding; bh=WRiU2DXaf6eHtLSh/EvN0SHuEYFvLYSjVeF7jkgPIpY=; b=rOFG6NkFbJF9GPy73+ObxN+f8iKBo2/1NiPw7dFqOB5291X56P87tEA8KteIsV4s8G PDrj7eWEiRCdDSmvidv7vZULRSUHOiZIL6rEmtkt0wKv+BdIfweis4pdtepzV9yKCuxc XT1fE8ewthQf/QpM+qtP9byjmcF50aL+eMJ6denOlNddk8T/jiOEE843Zy0ay2rAHpGs rZiqn3BAM2gQXmLmSnBusL4Frv/7oOq9+wDFPgrHJxTuzDYglbYLiokgh0T7RsHxZXk2 Cxp1JHRras/Pom1NCD8iw4vcLyXlAmxFOZkK4R1aiH0IqDeV3Bax+yg85zSAqOhpxny3 z7qg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:mime-version:content-transfer-encoding; bh=WRiU2DXaf6eHtLSh/EvN0SHuEYFvLYSjVeF7jkgPIpY=; b=dhxHpKED8FccXTJoMs4VIIjCa6U0yzrH+4qh30M5/+Uv0peU8VXfH4H7sBo88IbVPq hui+wXO5LMTsQNFupujyTpoRnR8LFM8Bq7kn/UTt5VU5BAopwfmRw1FRmNMjYztQOGUK mNygLFDu2dfOpqjBRyPiZ/LFf8AFkFiRTRnDgAT1KkyndDTNRJlLiObv/ivuaWLduMpN FIqDkPVIoLeVTQFu7Xb1A7ZLU4MCOSFJn5STruplD8ONOjO3wrf7PFYpAa+q8AW18pj2 Rm+fygLkY/a6jheOxFFCZAsRMQKrGIUghB/fXb1oJNAglxdtsy1pNjHmlTMq1exd5xId FbCg==
X-Gm-Message-State: APzg51DYy9UHMN1KN+KpBChrYQz8AqEsK7xuEyK0pwoJQSldhvbuvFb7 1HHKWUudSvghEUnqRuJw35SJf3Vp
X-Google-Smtp-Source: ANB0Vda6fULN90W06QJNWV/YalBT7SjPzsLAlIoldJuFQ/k3b7sqLgl/RNlL0bpJo+TMrc7QvRcbIA==
X-Received: by 2002:a62:de04:: with SMTP id h4-v6mr41645146pfg.258.1537456657395; Thu, 20 Sep 2018 08:17:37 -0700 (PDT)
Received: from [] ([2601:640:101:a9ac:bd1f:7004:4962:6824]) by with ESMTPSA id g15-v6sm42826711pfg.98.2018. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Sep 2018 08:17:36 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/
Date: Thu, 20 Sep 2018 08:17:35 -0700
From: Jeff Tantsura <>
To: John Scudder <>, "" <>
CC: "" <>
Message-ID: <>
Thread-Topic: [Idr] Requesting WG adoption for draft-scudder-idr-capabilities-registry-change-02.txt
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <>
Subject: Re: [Idr] Requesting WG adoption for draft-scudder-idr-capabilities-registry-change-02.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 20 Sep 2018 15:17:41 -0000



On 9/19/18, 23:11, "Idr on behalf of John Scudder" < on behalf of> wrote:

    Hi All,
    People with sharp memories may recall that in 2015 I proposed we revise the BGP Capabilities registry to provide a good-sized FCFS space. I think our experience shows this works fine in practice and makes it easier for implementors to get code points in a timely fashion, helping prevent conflicts. I wrote a draft at that time but failed to follow it up. I've revised the draft and would like to propose it as a WG item. Here's the abstract:
       This document updates RFC 5492 by making a change to the registration
       procedures for BGP Capability Codes.  Specifically, the range
       formerly designated "Reserved for Private Use" is divided into three
       new ranges, respectively designated as "First Come First Served",
       "Experimental" and "Reserved".
    One thing to draw your attention to in the revised draft:
       Finally, we invite implementors who have used values in the range
       128-255 to contribute to this draft, so that the values can be
       included in the registry.
    That is, if you have a shipped implementation that's using one of the Private Use values, please contribute that information to the draft and (assuming the draft progresses) you'll automatically get a registered code point.
    --John (an individual contributor to the WG, and recusing myself as co-chair from the adoption and subsequent process)
    Idr mailing list