Re: [Bier] Roman Danyliw's Discuss on draft-ietf-bier-bar-ipa-12: (with DISCUSS and COMMENT)

Alvaro Retana <aretana.ietf@gmail.com> Tue, 19 April 2022 21:03 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 489933A16A0; Tue, 19 Apr 2022 14:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, URIBL_BLOCKED=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 MCPiEJJ0BsQt; Tue, 19 Apr 2022 14:02:59 -0700 (PDT)
Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) (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 342DD3A16AA; Tue, 19 Apr 2022 14:02:59 -0700 (PDT)
Received: by mail-wm1-x335.google.com with SMTP id q20so11452126wmq.1; Tue, 19 Apr 2022 14:02:59 -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=ZGb3XOIAIKAAzDkPoR4vb3nB42Q+HVpSBw2BeP6CfHs=; b=nSUgecrkzItXTrfe+n+/4r5xIbgWLF9HVLRrS1GDFm3o9mAar37mgcwzdFengqFZDV f8htyYfejGcL0bg/LuhJot6qc8ganyAVmlidreqzJVzQfkMObDcYrpTHvUR1DLzULzzC Ulnskw4WUHNUY1rzNGCS2GP15yuYUDpOVJOF5CyfcAVxB3lI3KhqHG12r07tMVQgOuqf +We/EzvzmZ3OLp7hh7Gsnlgo6wN8XgLqT5zlwzxjEjJ4nkyvKBOLqwAKvpt6CthL35OV grQ5qgE8vED/i7+s4gurCzMehqeDxHAw3Fxjm2t7zByZJaQ/6hiRhdtyTDkqBAGLvYa6 aUQA==
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=ZGb3XOIAIKAAzDkPoR4vb3nB42Q+HVpSBw2BeP6CfHs=; b=c6cSQygGr+uA4FOybHfGgOUHG3Oa6fOgUx+Ut/v1KHor0Xfif4i7NX4ypjzaddE5YP ZxSm/tiaYJC0qLpUENTnWND51s8aALIfLd4QFL0WfYzCRRyVn9QarzkNDk0el6uKT1YK Ro+rw3aPWsn07wGW3xqLZDu1Asr1eYDNu3MlSvlHkSPNBQ9ufWchJ4oFAdoPhim3JOZL fLxAVAWGCLi7jV0EmJ8HpLrgIOHbp+KNZAP1AWPkQtMQuaTzGV0PjMhSCOXL5EcV/eC/ 0KV64R475HhURpq7gVr8kkPQBjJnBNMuLsb99Gv6X4iF0iZ+sGE2wLLQ8zSj6BTF+4wh syew==
X-Gm-Message-State: AOAM533VADOQdbi5dDuBKqAc6KGDPwSByfmAxxqqygTxqds2fYKBWA89 0Z8Jaejf308FjwURiDsrcKp8iqYLT7xglzXm86wLXcksb88=
X-Google-Smtp-Source: ABdhPJyuWPhqA5u46B6s1N2vxoH9BB2w0jc0rYTSVHqo4+bmiqO6z7OCx35FbJAuz6o8wLH0fDimWFKhAl74W9lHXqI=
X-Received: by 2002:a1c:2b41:0:b0:392:9543:9782 with SMTP id r62-20020a1c2b41000000b0039295439782mr398847wmr.124.1650402176927; Tue, 19 Apr 2022 14:02:56 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 19 Apr 2022 23:02:56 +0200
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <165039109029.1472.7819950843781020588@ietfa.amsl.com>
References: <165039109029.1472.7819950843781020588@ietfa.amsl.com>
MIME-Version: 1.0
Date: Tue, 19 Apr 2022 23:02:56 +0200
Message-ID: <CAMMESsxoBjWPvUu__VTB6DhzD3eQmNmC4oahVTATZ0udr7ULpg@mail.gmail.com>
To: The IESG <iesg@ietf.org>, Roman Danyliw <rdd@cert.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/n1cYO0jqm0H_Ss5ZTno9vOWrBkM>
Subject: Re: [Bier] Roman Danyliw's Discuss on draft-ietf-bier-bar-ipa-12: (with DISCUSS and COMMENT)
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: Tue, 19 Apr 2022 21:03:05 -0000

On April 19, 2022 at 1:58:30 PM, Roman Danyliw wrote:


Roman:

Hi!  Thanks for the review!


> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> ** Section 2.
>
> 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.
>
> If this document is redefining “experimental use” to be “privately used for a
> deployment” please provide the appropriate applicability statement that bounds
> this “deployment”.

Paul suggested changing the name/registration policy of the range to
"Private and Experimental Use".  Would this new registration policy
address your concern?

If not, please help me out on what you're looking for.



> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thank you to Vincent Roca for the SECDIR review.
>
> ** Section 2. I support Paul Wouter’s DISCUSS on his concerns on:
>
> 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.
>
> This text suggests that BAR values will be either published in an RFC or NOT.
> The current ranges in that IANA registry
> (https://www.iana.org/assignments/bier/bier.xhtml#bier-algorithm) suggest that
> that only 0-127 is an RFC (Standards Action), but 128 – 239 could be either RFC
> or other specification (Specification Required).

Paul made the same comment, but I didn't get it.  I get it now! :-)

Yes, we need to clarify the part about "not specified in a RFC".

Thanks!

Alvaro.