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

<individual mode = "technical gadfly">

Interesting take

a) The observation that this is just _one_ possible mapping  from
<SD,SI,BSL> to BIFT-id is correct but IMO acknowledged in the abstract and
intro. Albeit a section may be in order explaining
* emphasis that completely different mappings are possible and equivalently
valid
* problems should such different mappings be deployed
* emphasis that introducing such a mapping may prevent correct functioning
of deployments where some subdomains are IGP signalled (dynamic downstream
values) and some use this mapping. Not a likely deployment maybe but when
offering people a sharp stick it helps to emphasize  the pointed ends.
b) I agree that having people build HW that is specialized to just process
this one mapping and nothing else would be quite undesirable for BIER but
if this is not a standards track document I don't know how we would have
any influence on that. Leaving this kind of stuff in the dark where many do
it but it's not documented is arguably worse than having it documented with
proper yellow/red stickers saying "it's gonna hurt" ...

So, not taking any stance, just helping to explore the space ...

And my usual meta-quip I cannot resist: "This being a somewhat dirty
shortcut offered it's worth to note that such shortcuts stay dirty long
after they have been short" ;-)

</individual>

On Tue, Feb 27, 2018 at 6:58 AM, Eric C Rosen <erosen@juniper.net> 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 listBIER@ietf.orghttps://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
>
>