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

--===============6663603820991146593==
Content-Type: multipart/alternative; boundary="001a113cd1f89539cd05659b24c1"

--001a113cd1f89539cd05659b24c1
Content-Type: text/plain; charset="UTF-8"

Ice,

At this point in the process, it would be necessary to make an overwhelming
technical argument - that would sway almost the whole
WG to your perspective.

I see you saying that you have a personal preference for having the IGP
Algorithm registry also be used for the BAR registry.   While
I do, of course, respect where you have technical expertise, my response -
particularly from a process perspective - is "that's nice".

Regards,
Alia

On Mon, Feb 19, 2018 at 8:15 PM, IJsbrand Wijnands <[email protected]> wrote:

> Alia,
>
> > An architectural argument can't also limit itself to the drafts in the
> title.
> >
> > If it sounded like the IANA registry was suggested as separate for BIER
> OSPF  and BIER ISIS, then your attempt to reframe the conversation might be
> reasonable.  Let me clarify - I see no current reason for an OSPF BAR
> registry and an ISIS BAR registry; it would just be a BAR registry.  Perhaps
> > that clarification is a good reason to get the IANA registry included in
> the next update?
>
> There is no reason for an individual BIER OSPF and BIER ISIS registry. The
> point is to align with what ever ISIS and OSPF are using to identify the
> algorithm.
>
> > The routing layer is separate from the BIER layer.  The BAR is for the
> BIER layer.
>
> The underlay is separate from the BIER layer, and each underlay can carry
> BIER specific information that is needed for for BIER to make the selection.
>
> Thx,
>
> Ice.
>
>

--001a113cd1f89539cd05659b24c1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Ice,<div><br></div><div>At this point in the process, it w=
ould be necessary to make an overwhelming technical argument - that would s=
way almost the whole</div><div>WG to your perspective.</div><div><br></div>=
<div>I see you saying that you have a personal preference for having the IG=
P Algorithm registry also be used for the BAR registry.=C2=A0 =C2=A0While</=
div><div>I do, of course, respect where you have technical expertise, my re=
sponse - particularly from a process perspective - is &quot;that&#39;s nice=
&quot;.</div><div><br></div><div>Regards,</div><div>Alia</div></div><div cl=
ass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Feb 19, 2018 at =
8:15 PM, IJsbrand Wijnands <span dir=3D"ltr">&lt;<a href=3D"mailto:ice@cisc=
o.com" target=3D"_blank">[email protected]</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">Alia,<br>
<span class=3D""><br>
&gt; An architectural argument can&#39;t also limit itself to the drafts in=
 the title.<br>
&gt;<br>
&gt; If it sounded like the IANA registry was suggested as separate for BIE=
R OSPF=C2=A0 and BIER ISIS, then your attempt to reframe the conversation m=
ight be reasonable.=C2=A0 Let me clarify - I see no current reason for an O=
SPF BAR registry and an ISIS BAR registry; it would just be a BAR registry.=
=C2=A0 Perhaps<br>
&gt; that clarification is a good reason to get the IANA registry included =
in the next update?<br>
<br>
</span>There is no reason for an individual BIER OSPF and BIER ISIS registr=
y. The point is to align with what ever ISIS and OSPF are using to identify=
 the algorithm.<br>
<span class=3D""><br>
&gt; The routing layer is separate from the BIER layer.=C2=A0 The BAR is fo=
r the BIER layer.<br>
<br>
</span>The underlay is separate from the BIER layer, and each underlay can =
carry BIER specific information that is needed for for BIER to make the sel=
ection.<br>
<br>
Thx,<br>
<br>
Ice.<br>
<br>
</blockquote></div><br></div>

--001a113cd1f89539cd05659b24c1--


--===============6663603820991146593==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Isis-wg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/isis-wg

--===============6663603820991146593==--