Re: [Teas] WG Last Call: draft-ietf-teas-rfc3272bis-16

Hi Adrian,

On Mon, Jun 27, 2022 at 9:24 PM Adrian Farrel <adrian@olddog.co.uk> wrote:

> Hi Dhruv,
>
>
>
> Thanks for your reviews, past and present.
>
>
>
> See in line.
>
>
>
> Adrian
>
>
>
> *From:* Teas <teas-bounces@ietf.org> *On Behalf Of *Dhruv Dhody
> *Sent:* 23 June 2022 18:30
> *To:* Vishnu Pavan Beeram <vishnupavan@gmail.com>
> *Cc:* TEAS WG <teas@ietf.org>; TEAS WG Chairs <teas-chairs@ietf.org>
> *Subject:* Re: [Teas] WG Last Call: draft-ietf-teas-rfc3272bis-16
>
>
>
> Hi WG,
>
>
>
> I reviewed the document in the past. I did a pass again. Thanks, Adrian
> and the design team for a great job!
>
>
>
> Compared to details provided for other techniques, I found the details
> about RSVP-TE to be lacking. We have a section on RSVP [1] but it does not
> say much about RSVP-TE. Wouldn't it make sense to have an explicit section
> on RSVP-TE for such a comprehensive I-D?
>
>
>
> [AF] I suppose that would go after 5.1.3.2 to follow on from the last
> sentence of that section, and comes before 5.1.3.3 that would build on it.
> But you know what I am going to say…
>
>
>
> [AF] I’d be happy to receive some text.
>

[Dhruv]: Here is something for you to further refine...

RSVP-TE is a protocol extension of the RSVP for traffic
engineering as specified in [RFC3209]. RSVP-TE allows
the establishment of TE LSPs, taking into consideration
network constraint parameters such as available bandwidth.
The extension supports signaling explicit paths that could
be administratively specified, or automatically computed
by a suitable entity (such as PCE) based on the QoS and
policy requirements, taking into consideration the
prevailing network state. RSVP-TE enables the allocation
of resources (for example, bandwidth) along the path using
the PATH and RESV messages.

RSVP-TE is further extended to support Fast Reroute (FRR)
[RFC4090], Diffserv [RFC4124], Bidirectional LSPs
[RFC7551]. Support for GMPLS for RSVP-TE is specified in
[RFC3473].

To support TE for multicast services, requirements for
point-to-multipoint (P2MP) MPLS TE LSPs are documented
in [RFC4461], and signaling protocol extensions for
setting up P2MP MPLS TE LSPs via RSVP-TE is defined in
[RFC4875] where a P2MP LSP is comprised of multiple
source-to-leaf (S2L) sub-LSPs. To determine the paths for
P2MP LSPs, selection of the branch points (based on
capabilities, network state, and policies) is key.

>
>
> I also wonder if there should be some text on TE for multicast?
>
>
>
> [AF] Would that be anything that didn’t go in the RSVP-TE section?
>
>
>
[Dhruv]: I can think of BIER-TE, maybe a pointer to
https://www.ietf.org/archive/id/draft-ietf-bier-te-arch-13.html#section-3.5
or borrow some text?

Thanks!
Dhruv

> Otherwise, IMHO the document is ready to be shipped!
>
>
>
> Thanks!
>
> Dhruv
>
>
>
> [1]
> https://www.ietf.org/archive/id/draft-ietf-teas-rfc3272bis-16.html#section-5.1.3.2
>
>
>
> On Tue, May 24, 2022 at 10:52 PM Vishnu Pavan Beeram <
> vishnupavan@gmail.com> wrote:
>
> All,
>
> This starts working group last call on
>
> https://datatracker.ietf.org/doc/draft-ietf-teas-rfc3272bis/
>
>
> Given the size of the document, this will be an extended
> LC (3 weeks). The working group last call ends on June 14th.
> Please send your comments to the working group mailing list.
>
> 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.
>
> Thank you,
> Pavan (Co-Chair & Doc Shepherd)
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>
>