Subject: Re: [Bier] draft-ietf-bier-ipv6-requirements-04

From: Michael McBride <[email-masked]>
Date: Fri, 6 Mar 2020 18:24:10 +0000

Thank you Loa for taking the time to review the drafts and share your opinion. I agree. 

I felt further validated when I saw this email last week from Bernard on another list:

"[BA] This has been the case from the earliest days.  For example, as documented in RFC 4840, back in the early 1980s, there were 3+ approaches to the encapsulation of IP on Ethernet/IEEE 802.1.  Yet the marketplace sorted things out then, as they did later when some of the same issues arose with WiMax/802.16 (RIP).  If there are dueling approaches, it is often best to document them; rather than relying on standards bodies to "choose a winner"."

It's been over a month now with no action. Let's please start some bierv6 adoption calls especially now since many of us won't be in Vancouver to discuss in person.

Thanks!
mike

-----Original Message-----
From: Loa Andersson <[email-masked]> 
Sent: Wednesday, January 22, 2020 8:43 PM
To: Michael McBride <[email-masked]>; BIER WG <[email-masked]>
Subject: Re: [Bier] draft-ietf-bier-ipv6-requirements-04

Working Group,

I gone over the mails and drafts that Mike mention.

Even though the first option for an SDO is to aim for a single specification the path to reach that goal might be too adopt two documents and use the wg process to see if it is possible to merge the documents into a single specification, or demonstrate that one solution is superior to the other.

In the event this is not possible there is quite often technical or operational reasons. For example in the case of L2VPN we spent quite an effort to try agree on a single signaling protocol, it turned out that we couldn't. There were at that time quite a bit of talked about "let the market decide", well it turned out that the market decided that there was applicability for two solutions.

Therefore I think Mike's proposal is well founded and will give us the time needed to come up with the correct decision or even see what the market decide.

/Loa

On 16/01/2020 08:27, Michael McBride wrote:
> Hello team bier,
> 
> We've updated the bier-ipv6-req's draft, per our discussion in Singapore, and will ask for wglc in Vancouver. This gives us time to fine tune it with your additional feedback.
> 
> The purpose of this draft is to list the requirements which will help steer us towards a solution(s). There are currently two active drafts (xie-bier-ipv6-encapsulation & zhang-bier-bierin6). Both are summarized in the appendix of bier-ipv6-requirements along with several other solutions. Both have been discussed at great length and meet the majority of the req's. IMHO the bier chairs/wg should discuss adopting both of these solutions as each provide a good (yes I'm biased) unique bierv6 solution. We could either let one of the solutions prevail in the end or allow both to progress and allow the market decide.
> 
> Your further opinions appreciated.
> 
> Thanks,
> mike
> 
> -----Original Message-----
> From: BIER <[email-masked]> On Behalf Of 
> [email-masked]
> Sent: Wednesday, January 15, 2020 3:47 PM
> To: [email-masked]
> Cc: [email-masked]
> Subject: [Bier] I-D Action: draft-ietf-bier-ipv6-requirements-04.txt
> 
> 
> 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           : BIER IPv6 Requirements
>          Authors         : Mike McBride
>                            Jingrong Xie
>                            Senthil Dhanaraj
>                            Rajiv Asati
>                            Yongqing Zhu
> 	Filename        : draft-ietf-bier-ipv6-requirements-04.txt
> 	Pages           : 14
> 	Date            : 2020-01-15
> 
> Abstract:
>     The BIER WG includes, in its charter, work on developing mechanisms
>     to transport BIER natively in IPv6.  This document is intended to
>     help the WG with this effort by specifying requirements for
>     transporting packets, with Bit Index Explicit Replication (BIER)
>     headers, in an IPv6 environment.  There will be a need to send IPv6
>     payloads, to multiple IPv6 destinations, using BIER.  There have been
>     several proposed solutions in this area.  But there hasn't been a
>     document which describes the problem and lists the requirements.  The
>     goal of this document is to describe the BIER IPv6 requirements,
>     summarize the proposed solutions, and guide the working group in
>     understanding the benefits, and drawbacks, of the various solutions
>     and to help in the development of acceptable solutions.
> 
> 
> The IETF datatracker status page for this draft is:
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata
> tracker.ietf.org%2Fdoc%2Fdraft-ietf-bier-ipv6-requirements%2F&amp;data
> =02%7C01%7Cmichael.mcbride%40futurewei.com%7C0898c313efe244fdbe5808d79
> fbeb572%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C63715351377242485
> 0&amp;sdata=l6mGVOxAHb51FZg9P56%2FfJXksJOUCwrdE%2FI0PPH3kes%3D&amp;res
> erved=0
> 
> There are also htmlized versions available at:
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftool
> s.ietf.org%2Fhtml%2Fdraft-ietf-bier-ipv6-requirements-04&amp;data=02%7
> C01%7Cmichael.mcbride%40futurewei.com%7C0898c313efe244fdbe5808d79fbeb5
> 72%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637153513772424850&amp
> ;sdata=jaiD1JpYxXbjcoWdXyHztdocLRFG7SkxjfXnAV6vQ7Y%3D&amp;reserved=0
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata
> tracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-bier-ipv6-requirements-04&a
> mp;data=02%7C01%7Cmichael.mcbride%40futurewei.com%7C0898c313efe244fdbe
> 5808d79fbeb572%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C6371535137
> 72424850&amp;sdata=NgJ9k7Y0OcBuSi2GmP2dP0qJ2koUsr2kcv%2FDs%2B2k2QU%3D&
> amp;reserved=0
> 
> A diff from the previous version is available at:
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> ietf.org%2Frfcdiff%3Furl2%3Ddraft-ietf-bier-ipv6-requirements-04&amp;d
> ata=02%7C01%7Cmichael.mcbride%40futurewei.com%7C0898c313efe244fdbe5808
> d79fbeb572%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C63715351377242
> 4850&amp;sdata=kuSfTEvjzCefkIvjWOJdb%2FEczhzhTn23pPfr0peAam8%3D&amp;re
> served=0
> 
> 
> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> BIER mailing list
> [email-masked]
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> ietf.org%2Fmailman%2Flistinfo%2Fbier&amp;data=02%7C01%7Cmichael.mcbrid
> e%40futurewei.com%7C0898c313efe244fdbe5808d79fbeb572%7C0fee8ff2a3b2401
> 89c753a1d5591fedc%7C1%7C0%7C637153513772424850&amp;sdata=AZhZc4OWCy3gd
> yBSIk9SSclvlo00Lv2CkQgtrt3krRo%3D&amp;reserved=0
> 
> _______________________________________________
> BIER mailing list
> [email-masked]
> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> ietf.org%2Fmailman%2Flistinfo%2Fbier&amp;data=02%7C01%7Cmichael.mcbrid
> e%40futurewei.com%7C0898c313efe244fdbe5808d79fbeb572%7C0fee8ff2a3b2401
> 89c753a1d5591fedc%7C1%7C0%7C637153513772424850&amp;sdata=AZhZc4OWCy3gd
> yBSIk9SSclvlo00Lv2CkQgtrt3krRo%3D&amp;reserved=0
> 

-- 

Loa Andersson                        email: [email-masked]
Senior MPLS Expert
Bronze Dragon Consulting             phone: +46 739 81 21 64