IETF Logo Mail Archive

Re: [Idr] Update to update to BGP-LS registries

Donald Eastlake <d3e3e3@gmail.com> Sat, 27 July 2019 00:38 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 62FF91201DD for <idr@ietfa.amsl.com>; Fri, 26 Jul 2019 17:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 MYFhZKJ2cVqR for <idr@ietfa.amsl.com>; Fri, 26 Jul 2019 17:38:20 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 6D9EF1201D7 for <idr@ietf.org>; Fri, 26 Jul 2019 17:38:20 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id m24so108406830ioo.2 for <idr@ietf.org>; Fri, 26 Jul 2019 17:38:20 -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:content-transfer-encoding; bh=Daa9DODS0dYwUUpSIpnPWc1WGJYMT/9c/ZJrJDH0mRU=; b=ivtdV665EhZgzxTd63hT6X9CWXEiXMwieezzJg94I51WHq9O/P2TnJapS0niodbAlj EKdER/MC4Kqt4pl2kWWZfSNC5Qtz8oaJW1TEVy1wjSzGKFsjfUI6xrGgubErOoUaJNws JQQQWeLfjvnjp7TlN9NxFNrwS4qYsd9FaG7XnSs4bsVIY0heJQHYD2CpoQ76ZtqI7Z46 vCQvZII+0EcowJoYdvmgauvLhqSw2PCsneAo0pr2GtF3vfvQnGhOobbxXgl4lAmJXYF2 TnCQ+THsnNo9nLcCqp9EyH2J3ajKN5mbllA49xybhxpb2nnP+/AUQUN9ISa/T5OtXYzi PPjA==
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:content-transfer-encoding; bh=Daa9DODS0dYwUUpSIpnPWc1WGJYMT/9c/ZJrJDH0mRU=; b=eyXgNxZUK/8vGQuPKhaLCLt0Dixg/SLkWN3VToGS3GuqV55qgl2SQ/tI+XYkEtEbfS g8d8SR4taiGD8SZZzyp6EbEE3q/PlWe994IRhgzaDwb6XFcR6sxeXa9K26o79XbZBLIn 2aK1KFnf4HnLyLj8/A3lsaFWJxEJMiR5NoX9hDiv5rZB2ivAZRU/mGz4OG9clv0bmwnz prcpPG6MXmacglDWh29zkSGtGSeGgD7O4wcJuzm1ljahos6njstHxbys+GOHFkd0BIER LhMGwiD6uPGFK1t9W6yEAsn/pTHECN3OIJ2H1d5Iza4J8XMRZUcAhKHgHvk2yAM6v7bp vA3w==
X-Gm-Message-State: APjAAAUdqPdkB7La+A6KxW8DQFxjPZLQY65SwUUHxJ6mot/zBj8d4P/s f2mK/95z0XPBTx3eqQYB/0ZNgvMe93N06DVuENE=
X-Google-Smtp-Source: APXvYqxlLWDVDN7fJN5/0cYxrlpvbjCwLR6yvsdueLDuHbAHliossNGdGptHPxXuJWZKPPFX0PtyDyWFJ3xPeAXOM5U=
X-Received: by 2002:a5d:960f:: with SMTP id w15mr16984185iol.24.1564187899598; Fri, 26 Jul 2019 17:38:19 -0700 (PDT)
MIME-Version: 1.0
References: <0b0a01d543bf$f5336ba0$df9a42e0$@olddog.co.uk> <DM5PR11MB2027839B3DD1CE0786AF3289C1C00@DM5PR11MB2027.namprd11.prod.outlook.com> <E9AC1BEC-2013-4E93-9E02-0BBF23A2850D@juniper.net> <DM5PR11MB20279E5CFEACA444111D2293C1C00@DM5PR11MB2027.namprd11.prod.outlook.com>
In-Reply-To: <DM5PR11MB20279E5CFEACA444111D2293C1C00@DM5PR11MB2027.namprd11.prod.outlook.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 26 Jul 2019 20:38:07 -0400
Message-ID: <CAF4+nEF4X64vxma=18Bi8iyzr1qEb0pkjFrgRF=aBo4u1rjvKQ@mail.gmail.com>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
Cc: idr wg <idr@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Llsf2LIJej-wUYzZC7in181uc4c>
Subject: Re: [Idr] Update to update to 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: Sat, 27 Jul 2019 00:38:22 -0000

Hi Ketan,

On Fri, Jul 26, 2019 at 7:11 PM Ketan Talaulikar (ketant)
<ketant@cisco.com> wrote:
>
> Hi John,
>
> ...
>
> The point regarding process overheads and additional gatekeepers that you referred to was with the Early Allocation Process defined in RFC7120. However, I believe we are talking "allocation" under Specification Required and not "early allocation" - so the process described in RFC7120 does not apply? I somehow got the impression that RFC7120 was more about the schemes that were more stringent that Specification Required as described in RFC8126. I may be wrong.

First sentence of the Abstract of RFC 7120:

   This memo describes the process for early allocation of code points
   by IANA from registries for which "Specification Required", "RFC
   Required", "IETF Review", or "Standards Action" policies apply.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 1424 Pro Shop Court, Davenport, FL 33896 USA
 d3e3e3@gmail.com

> ...
>
> Thanks,
> Ketan

v2.23.0 | Report a Bug | By Email