Re: [Bier] Paul Wouters' Discuss on draft-ietf-bier-bar-ipa-12: (with DISCUSS)

Alvaro Retana <aretana.ietf@gmail.com> Mon, 18 April 2022 19:27 UTC

Return-Path: <aretana.ietf@gmail.com>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A5AB3A1122; Mon, 18 Apr 2022 12:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001] autolearn=ham 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 Cq0E1mzdaOWh; Mon, 18 Apr 2022 12:27:31 -0700 (PDT)
Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (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 6BD9D3A1111; Mon, 18 Apr 2022 12:27:31 -0700 (PDT)
Received: by mail-wm1-x333.google.com with SMTP id ay11-20020a05600c1e0b00b0038eb92fa965so103336wmb.4; Mon, 18 Apr 2022 12:27:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc:content-transfer-encoding; bh=GUAUfYogY+LjnG/kvv/uBvGp+xyCcuON4HA0Gojss3o=; b=Lg6tIM6eW/VJjJ73mO/eMmHJlQoi/oOiskldpote40nwMl4ST9q3DUUNhyelBsN3AV mgXSDc435xBU+UHLF1LDf4bgyIEoADM0aggLlR+qFrgN1sJvsZsOjJywno2sOcNwn8I+ JoWZs7ZgrIIjsoyhy/HJ8sHtOOTyhn8IWf+EoglI8cALug5xKcKO06M1ZhtoJjvYtgAW 4dNMIsVO+3ZJ3cNZxOEd5Ca5B2DJLwZwAuEx6wxPnYmErQIL2QR+fNkYrk2FkYoHurcY WpFSA0Uu2L+I+dggnMygBgwioGAelackBM+NZYOqf+mcalflcIxRJNDaDFTZZ+Hv1cKy URNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc:content-transfer-encoding; bh=GUAUfYogY+LjnG/kvv/uBvGp+xyCcuON4HA0Gojss3o=; b=pykjg7qeQJB2qWGF1grtzyk8v3Y6WCxebVuIUNZOWOuKGuLBV0bkh0xQjjQG9rRvfE aKmbnp6EYu6K0Sr5QmV/34eZ8TJhT5fkFHq2cpw3skiT4GJvhZXyAe5xQi66rperw+/f jMnUIeRyDbyyPJvdL7vT8trTeSC2RODT5xBiDwssbs+oEnR7LU3iDEqVdqZIXby7pWY3 VGn9ef3SXVSEVsPAtkWttcEaOgk7G2A6QITOD/OTOpUGIA8v8Ypz5OonTba7T0RZzP2H jdjYJfkwFWSG+mdTyOADUNYJh9fFA6PkHsQEE3peHcfJLw+I/8veXiup+PGCsK/HBIxr 8XHw==
X-Gm-Message-State: AOAM530x2FeWVCMlUYOCqxozLgOomxtUUT+Hb/GWwDQpA8LLT40MSwQM ys3Y+YbnVtyzj7UOK0tz5K/1354qMYt9mpIUpbw=
X-Google-Smtp-Source: ABdhPJwM8MjXXfO6ae8ts3Ox5ANDldGGB5//e2xasjr7ZP6e3tWQnOHTKDIBM+IcUS0u8OMnyCMBSdxZVJlKAkobcG8=
X-Received: by 2002:a1c:2b41:0:b0:392:9543:9782 with SMTP id r62-20020a1c2b41000000b0039295439782mr6917046wmr.124.1650310049546; Mon, 18 Apr 2022 12:27:29 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Mon, 18 Apr 2022 21:27:27 +0200
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <165030763443.2585.7951051000362988637@ietfa.amsl.com>
References: <165030763443.2585.7951051000362988637@ietfa.amsl.com>
MIME-Version: 1.0
Date: Mon, 18 Apr 2022 21:27:27 +0200
Message-ID: <CAMMESsxy60Hh+awpUFiBQnNuS9gFyg2AgKQaYomXXjKM5Tm3Mw@mail.gmail.com>
To: Paul Wouters <paul.wouters@aiven.io>, The IESG <iesg@ietf.org>
Cc: draft-ietf-bier-bar-ipa@ietf.org, Greg Mirsky <gregimirsky@gmail.com>, bier@ietf.org, bier-chairs@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/1xYN3r50I1B5QtHU-wKr8tujHoc>
Subject: Re: [Bier] Paul Wouters' Discuss on draft-ietf-bier-bar-ipa-12: (with DISCUSS)
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Apr 2022 19:27:34 -0000

On April 18, 2022 at 2:47:15 PM, Paul Wouters wrote:


Paul:

Hi!

Thanks for the review!


Just replying to your first point.  I'll let the authors address the second one.


Alvaro.


> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> [1]
> This document could instruct IANA to rename "240-254 Experimental Use" to
> "240-254 Private and Experimental Use", since that is what this document
> states:
>
> If a BAR value is not specified in a RFC but only privately used for
> a deployment, it MUST be within the "240-254 Experimental Use" range
> of the registry.

I think that renaming the range makes sense.


> Furthermore, the statement implies there are two different allocation types
> here ("RFC" and "privately used"), but the IANA Registry shows 3 types:
>
> 0-127 Standards Action
> 128-239 Specification Required
> 240-254 Experimental Use
>
> The "Specification Required" could be a non-RFC specification.

Standards Action covers Standards Track RFCs.

Specification Required covers RFCs not on the Standards Track and non-RFCs.

Private and Experimental Use don't require documentation, or registration.

I see three. ;-)

I'm not sure if you were looking for an additional change (beyond the
registration policy of the range).  ??


> If this is done, the Abstract should mention the IANA Registry is updated and
> the IANA Considerations section should be updated.

Yes.