Hi,
I see now that all the documents are standards track so scratch the first 
comment. I’m not sure where I got the “experimental”…
Thanks,
Acee

From: BIER <bier-boun...@ietf.org<mailto:bier-boun...@ietf.org>> on behalf of 
Acee Lindem <a...@cisco.com<mailto:a...@cisco.com>>
Date: Sunday, June 18, 2017 at 2:40 PM
To: "gjs...@gmail.com<mailto:gjs...@gmail.com>" 
<gjs...@gmail.com<mailto:gjs...@gmail.com>>, 
"b...@ietf.org<mailto:b...@ietf.org>" <b...@ietf.org<mailto:b...@ietf.org>>, 
OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>>
Subject: Re: [Bier] WGLC: draft-ietf-bier-ospf-bier-extensions-05

Hi Greg, Authors,

I support publication. Also, I have two comments.

   1. It is somewhat strange to make protocol drafts standards track while the 
architecture and encapsulations are experimental.
   2. The OSPF encoding will not support the second example in 
https://www.ietf.org/id/draft-ietf-bier-mpls-encapsulation-07.txt. In this 
example, the BSL 256 and 512 are intermixed. While with the encoding, they 
would need to be two separate ranges of labels.

I also have some editorial comments but I’ll just pass them to the authors.

Thanks,
Acee

From: BIER <bier-boun...@ietf.org<mailto:bier-boun...@ietf.org>> on behalf of 
Greg Shepherd <gjs...@gmail.com<mailto:gjs...@gmail.com>>
Reply-To: "gjs...@gmail.com<mailto:gjs...@gmail.com>" 
<gjs...@gmail.com<mailto:gjs...@gmail.com>>
Date: Wednesday, June 14, 2017 at 5:34 PM
To: "b...@ietf.org<mailto:b...@ietf.org>" 
<b...@ietf.org<mailto:b...@ietf.org>>, OSPF WG List 
<ospf@ietf.org<mailto:ospf@ietf.org>>
Subject: [Bier] WGLC: draft-ietf-bier-ospf-bier-extensions-05

BIER, OSPF

At BIER WG meeting, IETF97 in Chicago, we decided to move forward to WGLC for 
some of our docs. We learned that even once published the IESG has a process to 
change the track of the RFC if the WG makes the case to move the work from 
Informational to Standards track. The feedback from operators is that RFC 
status was more important than track, and we won't be able to meet our charter 
requirements to change track without deployment experience and operator support.

This email starts a two week timer for feedback on the draft:
https://datatracker.ietf.org/doc/draft-ietf-bier-ospf-bier-extensions/

WGLC to run in parallel in both BIER and OSPF WGs due to the scope of the work.

Thanks,
Greg
(BIER Chairs)


_______________________________________________
OSPF mailing list
OSPF@ietf.org
https://www.ietf.org/mailman/listinfo/ospf

Reply via email to