[bess] Roman Danyliw's Discuss on draft-ietf-bess-evpn-mh-split-horizon-10: (with DISCUSS and COMMENT)

Roman Danyliw via Datatracker <noreply@ietf.org> Wed, 31 July 2024 13:58 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: bess@ietf.org
Delivered-To: bess@ietfa.amsl.com
Received: from [10.244.2.81] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 83C8CC1CAE82; Wed, 31 Jul 2024 06:58:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172243429018.2152631.10249338622249987243@dt-datatracker-659f84ff76-9wqgv>
Date: Wed, 31 Jul 2024 06:58:10 -0700
Message-ID-Hash: 5PQMM7OVSJ2ILOJPYF5B7A432JTVBZGN
X-Message-ID-Hash: 5PQMM7OVSJ2ILOJPYF5B7A432JTVBZGN
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-bess.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-bess-evpn-mh-split-horizon@ietf.org, bess-chairs@ietf.org, bess@ietf.org, slitkows.ietf@gmail.com, mankamis@cisco.com, zzhang@juniper.net, matthew.bocci@nokia.com
X-Mailman-Version: 3.3.9rc4
Reply-To: Roman Danyliw <rdd@cert.org>
Subject: [bess] Roman Danyliw's Discuss on draft-ietf-bess-evpn-mh-split-horizon-10: (with DISCUSS and COMMENT)
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/FbWDQWBzCX0zPStP3zQjbEmU14U>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Owner: <mailto:bess-owner@ietf.org>
List-Post: <mailto:bess@ietf.org>
List-Subscribe: <mailto:bess-join@ietf.org>
List-Unsubscribe: <mailto:bess-leave@ietf.org>

Roman Danyliw has entered the following ballot position for
draft-ietf-bess-evpn-mh-split-horizon-10: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-mh-split-horizon/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

** Section 5.
   This document creates a registry called "EVPN ESI Label Extended
   Community Flags" for the 1-octet Flags field in the ESI Label
   Extended Community [RFC7432].
...
   In addition, the "Multihoming redundancy mode" field is initialized
   as follows:
...
   And the field "Split Horizon Type" is initialized as follows:
...
   New registrations in the "EVPN ESI Label Extended Community Flags"
   registry will be made through the "IETF Review" procedure defined in
   [RFC8126].

The above IANA guidance is ambiguous.

--  How many registries are being created – one or three?  The text explicitly
says that a registry named "EVPN ESI Label Extended Community Flags" will be
created.  However, the subsequent text says that "Multihoming redundancy mode"
and "Split Horizon Type" will be “initialized”?  Does “initialized” mean
registry creation?

-- If "Multihoming redundancy mode" and "Split Horizon Type" are new
registries, are they also following an IETF Review policy?  The text only says
that "EVPN ESI Label Extended Community Flags" uses IETF Review?


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you to Jouni Korhonen for the GENART review.