Re: [Bier] I-D Action: draft-ietf-bier-te-isis-01.txt

Toerless Eckert <tte@cs.fau.de> Fri, 12 August 2022 15:52 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 5BDCBC15C504 for <bier@ietfa.amsl.com>; Fri, 12 Aug 2022 08:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PtPLAWZ_ZBQd for <bier@ietfa.amsl.com>; Fri, 12 Aug 2022 08:52:48 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F57CC157B3E for <bier@ietf.org>; Fri, 12 Aug 2022 08:52:41 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id E4E3558C4AF for <bier@ietf.org>; Fri, 12 Aug 2022 17:52:34 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id D19CE4EB726; Fri, 12 Aug 2022 17:52:34 +0200 (CEST)
Date: Fri, 12 Aug 2022 17:52:34 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: bier@ietf.org
Message-ID: <YvZ3Qm/12rs8LNlp@faui48e.informatik.uni-erlangen.de>
References: <165912199957.33573.9414915331218147964@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <165912199957.33573.9414915331218147964@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/vBzKR6iwEzKTp-CpfI2FyddSL-Y>
Subject: Re: [Bier] I-D Action: draft-ietf-bier-te-isis-01.txt
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 12 Aug 2022 15:52:50 -0000

A)

> No Sub-Sub-TLV is defined so far.

are ?

B) 

> Note that if each of BitPosition and DrEndBitPosition uses more
> than 2 octets, we use 4 or more octets for each of them.

I do not understand what this means. Are you implying that the field
BitPosition in your Sub-TLV could be longer than the indicated 16 bit
in Figure 1 ? If so, how would a recipient know that it is not 16 bit long ?

I also don't think the BIER/BIER-TE architecture would permit this
field to be longer than 16 bits, we (BIER/BIER-TE) only support 64k in both.

C) I think the word BitPosition and DrEndBitPosition are not correct.

What you do seemingly want to encode is what BIER (and RFC8401) calls BFR-id,
and BIER-TE unfortunately weaseled out giving a new name (unfortunately,
bfr-id does not make sense for BIER-TE even though the values themselves
do make equally sense). I guess we should have given it a name like ADJ-id,
and that is what i would suggest calling this field. Maybe add simple
explanation:

   ADJ-id = BitPosition + SI * BSL (like BFR-id in BIER)

Or else, we can also just call it bfr-id like RFC8401, just noting that
the semantic of the indicated bit is not that of a BIER bfr-id, but of
a BIER-TE foward_connected() adjacency.

In any case, bit position / BitPosition is consistently used in rfc8279 and
BIER-TE to solely refer to bits within a BitString in a packet (<= 4096), not
across all the BitString bits spossible for an SD (<= 64k).

D) I still don't think i have seen an answer giving an exxample of what
DrEndBitPosition could be. Still curious.

Cheers
    Toerless


On Fri, Jul 29, 2022 at 12:13:19PM -0700, 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           : IS-IS Extensions for BIER-TE
>         Authors         : Huaimo Chen
>                           Mike McBride
>                           Aijun Wang
>                           Gyan S. Mishra
>                           Yanhe Fan
>                           Lei Liu
>                           Xufeng Liu
>   Filename        : draft-ietf-bier-te-isis-01.txt
>   Pages           : 7
>   Date            : 2022-07-29
> 
> Abstract:
>    This document describes IS-IS extensions for distributing
>    BitPositions configured on the links in "Bit Index Explicit
>    Replication Traffic Engineering" (BIER-TE) domain.
> 
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-bier-te-isis/
> 
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-bier-te-isis-01
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-bier-te-isis-01
> 
> 
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
>