Re: [Idr] New BGP capability to advertise running daemon version

Job Snijders <job@ntt.net> Fri, 02 August 2019 09:07 UTC

Return-Path: <job@instituut.net>
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 B4E9512004E for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 02:07:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.201, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 Z72zTY3uoZXm for <idr@ietfa.amsl.com>; Fri, 2 Aug 2019 02:07:42 -0700 (PDT)
Received: from mail-ed1-f54.google.com (mail-ed1-f54.google.com [209.85.208.54]) (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 0405912006E for <idr@ietf.org>; Fri, 2 Aug 2019 02:07:41 -0700 (PDT)
Received: by mail-ed1-f54.google.com with SMTP id i11so8221977edq.0 for <idr@ietf.org>; Fri, 02 Aug 2019 02:07:41 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=LFQ9ZMW2GNDmCZAMC0q/uKqwkd0UHOuib2buqUHT0S8=; b=JXpPlB505sDp6t5zBQCh3AfUAMi1YPK8urXuyxkZ4f241EtCDf5t3zvS+eEGTR2SnE gS4ZLySkI47+meZGmGWvNpeSYjq/6QIW6doHA3lzBkwqsrLZH3Ok4MiFI6v1yi6PezOh ALo4t4F4to9inleejnUst9hsMRcYskxpkqXBAEebb1us19Koxo9U/Q9oxf/RIfJunLVB /vbXpBXk1RgI230tKZXr2aH5DGNhIHyNMGftRjpHLeODXmIe4ARsxwD64Zes2Vnap1TU zN26fY2qzK0i4BsjRHwyYIiIZbmD+DnXnzc8Lx1M9FCRfjFAQTljvGUMa70XKyLWzJY+ 7PNg==
X-Gm-Message-State: APjAAAV5AsWFR8SKhWtv2McZaowu4YWKt2v7dyyHz5UZvYt+R3Ih0yRR QenECl/4t2KrRBJWUeLgFHQ/pGJk82U=
X-Google-Smtp-Source: APXvYqxVfpYkO9I/8MmwOVmKreLa3zOhQ80EF+yhDDNZaFkp9uIC+IXKYQU6QWlUzCJ7RRFpYHdz/g==
X-Received: by 2002:a17:907:2101:: with SMTP id qn1mr105843217ejb.3.1564736859936; Fri, 02 Aug 2019 02:07:39 -0700 (PDT)
Received: from localhost ([2001:67c:208c:10:dc7a:9bf9:5f88:6fd6]) by smtp.gmail.com with ESMTPSA id ng6sm5727742ejb.13.2019.08.02.02.07.38 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Fri, 02 Aug 2019 02:07:39 -0700 (PDT)
Date: Fri, 2 Aug 2019 11:07:38 +0200
From: Job Snijders <job@ntt.net>
To: Donatas Abraitis <donatas.abraitis@gmail.com>
Cc: idr@ietf.org
Message-ID: <20190802090738.GM54992@hanna.meerval.net>
References: <CAPF+HwV3EEUza3FyiXsd_oSkj80OwY-tE2DgFWnynq1FL2tLHg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPF+HwV3EEUza3FyiXsd_oSkj80OwY-tE2DgFWnynq1FL2tLHg@mail.gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/_NTH6kbOTpE-oWdydZrtJvhyLrQ>
Subject: Re: [Idr] New BGP capability to advertise running daemon version
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, 02 Aug 2019 09:07:44 -0000

Dear Donatas,

Welcome to IDR! 

On Fri, Aug 02, 2019 at 09:07:43AM +0300, Donatas Abraitis wrote:
> The implementation and details are posted in this draft:
> https://www.ietf.org/id/draft-abraitis-bgp-version-capability-00.txt
> 
> Waiting for comments.

I won't comment on the idea itself, but I note the following text in
your document:

    "IANA has assigned capability number 74 for the Version Capability
    described in this document.  This registration is in the BGP
    Capability Codes registry." 

Looking at https://www.iana.org/assignments/capability-codes/capability-codes.xhtml
I see that this is not the case, which means that the draft is
'squatting' on capability number 74, making it harder for anyone in the
future to actually use number 74 when IANA assigns it to someone.

Please update your draft ASAP to read as following:

    "IANA is requested to assign a capability number for the Version
    Capability in this document from the BGP Capabilities Codes
    registry."

The IANA registries are not self-service "pick what you want", but
fortunately most of them allow allocation of code points through a
simple procedure. Please follow the process the group agreed upon.
I recommend reading https://tools.ietf.org/html/rfc7120

It is critical for interopability (not just for this draft, but also
future unrelated BGP drafts) that we ensure codepoints are assigned by
the IANA; in cases where this didn't happen, the codepoints often are
marked as 'deprecated', see https://tools.ietf.org/html/rfc8093 as an
example.

Kind regards,

Job