Re: [Isis-wg] [Bier] BAR field length in draft-ietf-bier-isis-extensions and draft-ietf-bier-ospf-extensions

Peter Psenak <> Tue, 20 February 2018 17:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0CBD312D969; Tue, 20 Feb 2018 09:27:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rRrFce0rB6uX; Tue, 20 Feb 2018 09:27:57 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 410B812D963; Tue, 20 Feb 2018 09:27:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=4800; q=dns/txt; s=iport; t=1519147676; x=1520357276; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=R3utvWQYQZxCcoTiFu1XznBl0afccxB0JXgHn29yz9E=; b=k8dHm7QWOSM28mYgZCSVPc3RU5Pz2UfxMnS3Vd1Czo22uYUR7NHkcIN4 bygG32Fw/uWipYHSML9FS3o3hlDQcWxQObifZkw96/S7pZRk2ZXDdBaBl D3D/Z+jqId/udCJO+anJIHaMA4gra/z+BHxZhR+PhEOK1ev6C7WcwK7I+ U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.46,540,1511827200"; d="scan'208";a="2188126"
Received: from (HELO ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Feb 2018 17:27:54 +0000
Received: from [] ([]) by (8.14.5/8.14.5) with ESMTP id w1KHRrQ8024767; Tue, 20 Feb 2018 17:27:53 GMT
Message-ID: <>
Date: Tue, 20 Feb 2018 18:27:53 +0100
From: Peter Psenak <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Alia Atlas <>, BIER WG <>, " list" <>
References: <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [Isis-wg] [Bier] BAR field length in draft-ietf-bier-isis-extensions and draft-ietf-bier-ospf-extensions
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IS-IS working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 20 Feb 2018 17:27:59 -0000

Hi Alia,

1. I see a benefit in having the BIER a way to map to any of the IGP 
algorithms. Simply because IGPs already provide paths to all nodes in 
the domain and BIER can simply use these paths instead of computing its own.

2. Not sure if people plan to deploy the BIER in a model where it does 
its own topology related computations, independent of IGPs. If they do, 
I'm not objecting that.

The encoding of the BAR though must be done in a way that it easily 
supports both (1) and (2).

my 2c,

On 19/02/18 22:51 , Alia Atlas wrote:
> As the Sponsoring AD for draft-ietf-bier-isis-extensions-07 and
> draft-ietf-bier-ospf-extensions-12, I have been following the discussion
> on the mailing list with interest.
> I have not seen clear consensus for any change.
> Let me be clear on what I see the options are from the discussion.  Then
> I'll elaborate
> a bit on how you can express your perspective most usefully.
> 1) Current Status:  Bier Algorithm (BAR) field is 8 bits.  Currently,
> only value 0 is specified.  The drafts do not have an IANA registry -
> with the expectation that one will be created when the first additional
> use is clear.  It is possible that there will be objections from the
> IESG to progressing without an IANA registry.  Given the lack of clarity
> for future use-cases and after discussion, I decided not to force one
> after my AD review - but I will not push back against having a BIER IANA
> registry if raised by others.
> 2) Option B:  Add a BAR sub-type of 8 bits.  This would modify the
> current TLVs.
>     Define an IANA registry for the BAR type.  The meaning of the BAR
> sub-type derives
>     from the BAR type.   We can debate over the registration policy for
> the BAR type.
> 3) Option C: Change the BAR field to be 16 bits and define an IANA
> registry.  Part of the range can be FCFS with Expert Review, part can be
> Specification Required, and part can be IETF Consensus.
> 4) Option D: At some point in the future, if there is an actual
> understood and documented need, a BAR sub-type could be added a
> sub-TLV.  The length of the BAR sub-type could be determined when the
> sub-TLV is defined.
> Given
>    a) option D exists
>    b) there is currently only one defined value for BAR
>    c) I do not see strong consensus for change to one particular other
> option
> I see no current reason for a change and I certainly see absolutely no
> reason for
> a delay in progressing the documents.
> I do want to be clear about what the WG wants to do on this issue.
> Therefore, here is
> my following request.
> Please send your feedback to the mailing list as follows:
> IF you prefer or can accept the current status, please say so.  No more
> justification
> or reasoning is required. I just don't want the bulk of folks who are
> content to be
> overlooked by those suggesting change.
> IF you prefer or can accept the current status, but think there should
> be an IANA registry
> as is usual for managing code-points, please say so.  No more
> justification is needed.
> IF you prefer Option B, C, and/or D, please say so with your
> explanation.  More technical depth than "'we might need it" would be
> helpful; the availability of sub-TLVs already
> provides future proofing.
> IF you have a clear technical objection to why the Current Status is not
> acceptable,
> please express that - with clear details.
> IF you feel that additional code-points should be allocated in a BAR
> IANA Registry or
> have thoughts on the appropriate policy, please say so with your
> explanation for what
> those should be.
> Unless I see clear and strong consensus for something other than the
> Current Status,
> that will remain.
> IF there is clear and strong consensus for Option B, C, or D, or adding
> an IANA registry with particular values, then it will be possible to
> have a change up through this Weds night - with a 1 week WGLC on that
> particular technical change.
> My priority is to have the base BIER specifications published as
> Proposed Standards so that more BIER implementations and deployment can
> be done.  I would like the WG to wrap up the core work (as expressed in
> the proposed recharter) so that you all can look
> at how to use it.
> Given this topic was raised last Weds and given that there are no
> technical objections raised to the documents as are, there isn't much
> time - so please just respond to this email ASAP.  My deadline for a
> decision is 6pm EST on Weds.
> Regards,
> Alia
> _______________________________________________
> BIER mailing list