Re: [Bier] I-D Action: draft-ietf-bier-bar-ipa-10.txt

Alvaro Retana <aretana.ietf@gmail.com> Thu, 10 March 2022 20:39 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 3BBC73A0D4B; Thu, 10 Mar 2022 12:39:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, HTML_MESSAGE=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 rRyV-8_pqAIs; Thu, 10 Mar 2022 12:39:36 -0800 (PST)
Received: from mail-ej1-x630.google.com (mail-ej1-x630.google.com [IPv6:2a00:1450:4864:20::630]) (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 613153A1BCB; Thu, 10 Mar 2022 12:39:33 -0800 (PST)
Received: by mail-ej1-x630.google.com with SMTP id qx21so14649897ejb.13; Thu, 10 Mar 2022 12:39:33 -0800 (PST)
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; bh=O36JJJedy0I6GW4+G3vXKv5/G4cukdqMFNSeCfLmlVg=; b=UPY90wqISW1yLT+WSeaisCYC163kFaviTr1+X+vfyCMIefBHCA14w5EPw+N3FvJjJc AQwRhQuqoDIQeJtV6HOsrWa4Teqav8bE1jjCwmekdRkU04eKz4szaBaKt7kuEtG15lkD iWYqh4qxOQKeCjgszb98OU+v1zT6WSAW00qyTbMXjHU0ocTfM94KhjX28zEhJaK90zms 2bpgBR3DqEoACmA3Qa+UnxrHO88e4MB/qOqreSr66N4OUI08haG89FITTF+m0e7UbNNQ ccmrkpEyiuFkBqaIqQh259/HdKXba6b9zy21YO2VgyO6pegjz1hWBFHfYCA7f+jR7AJq 5bmQ==
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; bh=O36JJJedy0I6GW4+G3vXKv5/G4cukdqMFNSeCfLmlVg=; b=jI4llj8vJMubQ/ZO6Je7+0dIooOcgNPY5vJbroMRNOrmPyoyolbh0Wka/opRaDIjHk omnzoTJs4xrrqZE8K+n/8J+wlRomxBLGsLWabCwb4MLivvklRil2/XbTb890mCbCuyJO 6rcMAkj4l3CCkSIgnXh3LYnFk2re6TrKE+Z2avpGH2e7ZLFCPmpXDAUSbTmjg4kGcGKY O7nPMg5P30hs7foYjXdKCzQGjjY7/dkPUqJ2/IDqDkUSmIVeAj2mwGaxLvFnnCdnLOX9 wEAYjksrIkqgLwM0J6xYKJ0S4PvE3MGnxR6YVaJ8eN3S3DudGIFu5zxL9QLnAmZi30R0 DN8A==
X-Gm-Message-State: AOAM532QEdGXrlvb/iBTAtiSWH+V9V+gVTZGHhcoEAbkD3NFAM45S71O j5cw6BZc4JK23fbrlOXaVru3xtkcKh0gGy4M9Pfnlhy7
X-Google-Smtp-Source: ABdhPJyIpDVdryTyIFC+zfFhE/SV+3NAyqUEhHAWVDTLwGsYSnNelVYO8A/FlrcJaT+D/Qin7usgHrxn2DCzizcRSmo=
X-Received: by 2002:a17:906:99c2:b0:6d7:4a6a:e35d with SMTP id s2-20020a17090699c200b006d74a6ae35dmr5689513ejn.633.1646944771229; Thu, 10 Mar 2022 12:39:31 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 10 Mar 2022 12:39:30 -0800
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <164373131723.31409.6259824263288234451@ietfa.amsl.com>
References: <164373131723.31409.6259824263288234451@ietfa.amsl.com>
MIME-Version: 1.0
Date: Thu, 10 Mar 2022 12:39:30 -0800
Message-ID: <CAMMESszM6eQgMwDG3_WVFFAonFi1t6k7TB8QDuo=Efc2ghaHtA@mail.gmail.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
Cc: bier@ietf.org, draft-ietf-bier-bar-ipa@ietf.org, BIER WG Chairs <bier-chairs@ietf.org>, Greg Mirsky <gregimirsky@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000000dcdf605d9e336ca"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/rE-NmVNUQ_nHb2KTXyG7645eAy8>
Subject: Re: [Bier] I-D Action: draft-ietf-bier-bar-ipa-10.txt
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: Thu, 10 Mar 2022 20:39:39 -0000

Jeffrey:

Hi!

We're almost there -- I have some suggestions for §2 -- mostly reordering
and simplifying:

OLD>
   The definition for the BAR and IPA fields in [RFC8401] and [RFC8441]
   are updated as following.

   ...

   When a BAR value is defined in a RFC or used in a deployment, the
   corresponding BA and BC semantics SHOULD be specified in the RFC or
   for the deployment.  For an IGP Algorithm to be used as a BIER IPA,
   its RA and RC semantics SHOULD be specified in a RFC or for the
   deployment.

   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.

   None of the components of the BAR or IPA can be unknown.  If any of
   the components is not specified, it is interpreted as "NULL"
   algorithm or constraint.  For example, the IGP Algorithm 0 defined in
   [RFC8665] is treated as having a NULL RC, i.e., no constraints.


NEW>
   The definition for the BAR and IPA fields in [RFC8401] and [RFC8441]
   are updated as follows.

   ...

   When a new BAR value is defined, the corresponding BA and BC semantics
   SHOULD be specified.  For an IGP Algorithm to be used as a BIER IPA,
   its RA and RC semantics SHOULD be specified.

   None of the components of the BAR or IPA can be unknown.  If any of
   the components is not specified, it is interpreted as a "NULL"
   algorithm or constraint.  For example, the IGP Algorithm 0 defined in
   [RFC8665] is treated as having a NULL RC, i.e., no constraints.

   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 am going to start the IETF Last Call.  Please submit these changes when
the window opens on Mar/21.

Thanks!

Alvaro.

On February 1, 2022 at 11:02:36 AM, internet-drafts@ietf.org (
internet-drafts@ietf.org) wrote:


A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Bit Indexed Explicit Replication WG of the
IETF.

Title : BIER Underlay Path Calculation Algorithm and Constraints
Authors : Zhaohui Zhang
Antoni Przygienda
Andrew Dolganow
Hooman Bidgoli
IJsbrand Wijnands
Arkadiy Gulko
Filename : draft-ietf-bier-bar-ipa-10.txt
Pages : 6
Date : 2022-02-01

Abstract:
This document specifies general rules for the interaction between the
BIER Algorithm (BAR) and the IGP Algorithm (IPA) used for underlay
path calculation. The semantics defined in this document update
RFC8401 and RFC8444.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bier-bar-ipa/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-bier-bar-ipa-10

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-bar-ipa-10


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts



_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt