Re: [Bier] Call for adoption: draft-wijnandsxu-bier-non-mpls-bift-encoding-01

Toerless Eckert <tte@cs.fau.de> Tue, 06 March 2018 17:43 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 98BC212895E for <bier@ietfa.amsl.com>; Tue, 6 Mar 2018 09:43:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.96
X-Spam-Level:
X-Spam-Status: No, score=-3.96 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 42q3rD4DNT_7 for <bier@ietfa.amsl.com>; Tue, 6 Mar 2018 09:43:44 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 753741270AC for <bier@ietf.org>; Tue, 6 Mar 2018 09:43:44 -0800 (PST)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 46E3258C5A0; Tue, 6 Mar 2018 18:43:39 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 03E36B0DC54; Tue, 6 Mar 2018 18:43:38 +0100 (CET)
Date: Tue, 06 Mar 2018 18:43:38 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Eric C Rosen <erosen@juniper.net>
Cc: gjshep@gmail.com, BIER WG <bier@ietf.org>
Message-ID: <20180306174338.GB5640@faui40p.informatik.uni-erlangen.de>
References: <CABFReBrfrJU9u=ugG6Fs2dmZ+5vSs5pxySajfv9B7yvPuDW+hQ@mail.gmail.com> <938789da-1902-1a0e-98af-b2476204be62@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <938789da-1902-1a0e-98af-b2476204be62@juniper.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/Wy2jSOCA6xgacqtIzTSrRcDNf9Y>
Subject: Re: [Bier] Call for adoption: draft-wijnandsxu-bier-non-mpls-bift-encoding-01
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.22
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, 06 Mar 2018 17:43:47 -0000

Eric, *

Q1: Is there any text you could point me to that would give
me an idea how a non bsl-sd-si encoding of the bift-id would
be beneficial (non-mpls of course) ?

Q2: What would be the harm of deploying software (non-mpls)
that would only support this bift-id encoding ? Specific example
welcome.

Thanks
    Toerless

On Tue, Feb 27, 2018 at 09:58:45AM -0500, Eric C Rosen wrote:
> I am strongly opposed to the adoption of this draft.
> 
> The premise of the draft is that in non-MPLS networks, operators may
> want to assign a domain-wide unique BIFT-id that denotes, in every
> BFR, the BIFT associated with a given <SD,SI,BSL> triple.
> 
> That may be true.  However, there are many procedures that can be
> used to assign domain-wide unique BIFT-ids.  There is no reason for
> the WG to give the appearance of endorsing any one procedure over
> any of the thousands of others.  This is really a decision for the
> network operators.  So I think the document is not very useful.
> 
> I do however think the document is harmful.  It will inevitably
> result in the deployment of software (if not hardware) that cannot
> process non-MPLS BIER packets in which the BIFT-id is not formed
> according to the rules of this draft.
> 
> Yes, yes, the draft says that the use of this encoding is OPTIONAL,
> and the draft is merely Informational.  That won't help us much when
> some implementation (either from a vendor, or open source) gets
> deployed that requires the use of this encoding.
> 
> Drafts that are harmful but not useful should not be adopted by the WG.
> 
> If this draft proceeds, I suggest it be turned into an Independent
> Submission, so that it can be made clear that the draft just
> describes a suggestion by the authors.
> 
> 
> 
> 
> 
> On 2/26/2018 1:07 PM, Greg Shepherd wrote:
> >In Singapore we had solid support to
> >adopt draft-wijnandsxu-bier-non-mpls-bift-encoding as a WG draft.
> >
> >This is a call to the list for adoption. Please read and reply
> >with/without support to this thread:
> >
> >https://datatracker.ietf.org/doc/draft-wijnandsxu-bier-non-mpls-bift-encoding/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dwijnandsxu-2Dbier-2Dnon-2Dmpls-2Dbift-2Dencoding_&d=DwMFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=-DXB84eU9m4cIlq2OOcCJCQQAwJXQQswyu3F0kG0VNo&m=l-KKk7BthqSx7OjcMbxS5nkQZLR40fjA3UQvFQzbEas&s=jcUd-KEqRjNnt4plMdrqae2oeOhQSHIV_oZGcxtxnrg&e=>
> >
> >Thanks,
> >Greg
> >
> >
> >_______________________________________________
> >BIER mailing list
> >BIER@ietf.org
> >https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bier&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=-DXB84eU9m4cIlq2OOcCJCQQAwJXQQswyu3F0kG0VNo&m=l-KKk7BthqSx7OjcMbxS5nkQZLR40fjA3UQvFQzbEas&s=AjVaQdEtidRkJYHuMaOE3AynPR5gmY4zjT7WulICH1Q&e=
> 

> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier


-- 
---
tte@cs.fau.de