Re: [Teas] WG Last Call on draft-ietf-teas-rsvp-te-srlg-collect-05

[Vishnu Pavan Beeram <[e-mail]>]

Authors, Hi!

I'm in the process of updating the Shepherd's write-up for this document.
I'm expecting you to submit another rev for this draft (addressing the nits
that were raised during the LC). I found a few other nits (pasted below)
during my review. Please see if you can take care of these as well in the
next rev.

I'll resubmit the publication request as soon as the new version shows up.

Regards,
-Pavan

**
Section 1.

- s/This document provides a mechanism to collect the SRLGs used by a
LSP,/This document provides a signaling mechanism to collect the SRLGs used
by a LSP,
[Comment - signaling mechanism as opposed to routing mechanism; The
introduction section doesn’t explicitly say (maybe it should) that this
mechanism is useful in scenarios where the SRLG info cannot be obtained via
IGP-TE (via routing)]

- s/Note that specification of the the use of the collected SRLGs is
outside the scope of this document./Note that specification of the use of
the collected SRLGs is outside the scope of this document.
[Comment - You may even consider removing the above line altogether (given
that the document does discuss an applicability example in 1.1)]


Section 3.1:

- Fix indentation for the whole section


Section 3.2:

- Fix indentation for the whole section.

- s/SRLG information is for each hop is added to the Path RRO during Path
message processing./SRLG information is added by each hop to the Path RRO
during Path message processing.

- Consider removing the following line [Comment - it doesn’t seem to be
bringing in any additional value in this section]:
The endpoints of the LSP can make use of the collected SRLG information,
for example, for routing, sharing and TE link configuration purposes.


Section 3.3:

- Fix indentation for the whole section.

- s/This means that that the signaling procedure needs to be capable of
updating the new SRLG information./This means that the signaling procedure
needs to be capable of updating the new SRLG information.


Section 3.4:

- Fix indentation for the whole section.


Section 4.1:

- Fix indentation for the first paragraph.


Section 6.1 - Policy Configuration:

- Fix the bullets; All bullet points “o” are squeezed together in one
paragraph.


Section 8.2 ROUTE_RECORD Object

- Fix the indentation of the table (align it with the table in 8.1)


Section 8.3 Policy Control Failure Error subcodes

- Fix the indentation of the table (align it with the table in 8.1)



On Fri, May 13, 2016 at 8:15 PM, Vishnu Pavan Beeram <[e-mail]>
wrote:

> The WG LC for this document is now closed.
>
> Matt (and other authors),
> Please go ahead and publish a new revision addressing the minor comments
> received during the LC.
>
> Regards,
> -Pavan (and Lou)
>
> On Fri, May 13, 2016 at 6:07 PM, Shah, Himanshu <[e-mail]> wrote:
>
>> *Sorry for the late reply.. (On PTO..)*
>>
>>
>>
>> *While adding of “completion flag” (or similar to “partial bit” used in
>> BGP) would have been a nice feature*
>>
>> *to have, the SRLG collect draft by itself is an important feature to
>> have, so..*
>>
>>
>>
>> *I support progressing the document to publication.*
>>
>>
>>
>> *Thanks,*
>>
>> *Himanshu*
>>
>>
>>
>> *From:* Teas [mailto:[e-mail]] *On Behalf Of *Vishnu Pavan
>> Beeram
>> *Sent:* Thursday, April 28, 2016 4:42 PM
>> *To:* [e-mail]
>> *Subject:* [Teas] WG Last Call on draft-ietf-teas-rsvp-te-srlg-collect-05
>>
>>
>>
>> All,
>>
>> This starts a two week working group last call on
>> draft-ietf-teas-rsvp-te-srlg-collect-05.
>>
>> The working group last call ends on Thursday, May 12th. Please
>> send your comments to the TEAS mailing list.
>>
>> As is always the case, positive comments, e.g., "I've reviewed this
>> document and believe it is ready for publication", are welcome!
>> This is useful and important, even from authors.
>>
>> Note, IPR has been disclosed on this draft.
>>
>>
>> Thanks,
>> Pavan (and Lou)
>>
>
>