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

Gaurav Dawra <> Fri, 21 September 2018 06:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A2DCD130DFC; Thu, 20 Sep 2018 23:03:22 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 RwcIol-RPZjD; Thu, 20 Sep 2018 23:03:20 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::62a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0FD30130DCB; Thu, 20 Sep 2018 23:03:20 -0700 (PDT)
Received: by with SMTP id b97-v6so5467610plb.0; Thu, 20 Sep 2018 23:03:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/MuiIWDjBhsNf1oeN7SAHUeRxdAE39en2IgaqmIyCDM=; b=lQ11sJCvP4JQ20i24a0wpo4Ol6LORrGWQICsFxrN4SyWZ6Aa9IgBj3cUZEMZcN10G+ QiPLSUGPwP1FEoC6LvlX6nB1vRVqzqZ0TmiGz1VvNzrEJFOAYWw3tLFaffJnzNULX2wA OQTqjuiXkS9k9y/hLQAtyWH41vIw9eLfhQmiedGuEiNyMLOwth9bjun1ml3mi2D0x/cp GGa1gsV9Jqs3XEXaQ0Jz6K2g0z87TqCfxn+PxswhecUNK2BF3VEm2kRDSNxvh2P5sIsS O0sn5rm3xGMiuMWMYL5NVBZG1FL+JGl6UDn6odBns4KCkJl+G5paoW6zsZGGW/WRb8Vs rocw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/MuiIWDjBhsNf1oeN7SAHUeRxdAE39en2IgaqmIyCDM=; b=LG6xSGVhXVS7zGXK3noPIMd/sagwxx1EMSHqIxEce0Z4IOEORCitKXHmff7SUVfDgj Bm1j4kLfwxaVD56QhM8rlLa/iuua098uunkXbLKLxBvBBTZercyIsScRG4LFSPB7t1c0 1QS46w6wPrXCHFdNHNJlSIOCODggQoeGXXYNStKw/+RWWce1c8Sq/RvDf5FgeYM1yE9D +3YabaaHCiMBrvKeJeeZV83gA/1wGDvFW2AtBjjn7pdwju9YCxNJoKv/rwIsuf9p1FVs 0ruIx9WrzBEuRHKKLrdi00+z3SccaSArPO0a4ThoC0+kCBfSsI3pniezwU6SKS6NQ/ST Swmg==
X-Gm-Message-State: APzg51AGsxRxZWue1GwWqmU5dcD9eqfOJOdIVVmPPB1Y6z2K8Tn8rPmb EHcUpUk3vlkd4lVpo1hE0dAGf/XD
X-Google-Smtp-Source: ANB0VdYZuN6TmDOXe1gEzVDq3Hx01FfXMNtHiZiZhlha12MqhyOMXC0aLYrZzema27ifiTIvMnoEDw==
X-Received: by 2002:a17:902:a715:: with SMTP id w21-v6mr42675987plq.61.1537509798970; Thu, 20 Sep 2018 23:03:18 -0700 (PDT)
Received: from ?IPv6:2601:646:9300:4fc9:b139:3380:a967:ade0? ([2601:646:9300:4fc9:b139:3380:a967:ade0]) by with ESMTPSA id z11-v6sm28689587pgz.62.2018. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Sep 2018 23:03:17 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Gaurav Dawra <>
X-Mailer: iPhone Mail (15F79)
In-Reply-To: <>
Date: Thu, 20 Sep 2018 23:03:16 -0700
Cc: "" <>, "" <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: John Scudder <>
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: Fri, 21 Sep 2018 06:03:23 -0000

Makes sense. Support!


Sent from my iPhone

> On Sep 19, 2018, at 11:10 PM, John Scudder <> 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.
> Thanks,
> --John (an individual contributor to the WG, and recusing myself as co-chair from the adoption and subsequent process)
> _______________________________________________
> Idr mailing list