Re: [Teas] FW: I-D Action: draft-ietf-teas-rfc3272bis-18.txt

Hi Adrian

Text below:

RSVP-TE enables the instantiation of static MPLS LSP loose hops, strict
hops or a dynamic LSP using IGP extension for ISIS RFC 5305, OSPFV2
extension RFC 3630 and OSPFv3 extension RFC 5329 for cSPF (constrained SPF)
Traffic Engineering database (TED) using static TE metrics.  RSVP-TE has
now evolved to provide real time dynamic metrics for path selection using
RSVP-TE ISIS extension RFC 7810 and RSVP-TE OSPF extension RFC 7471 based
on IPPM STAMP RFC 8972 and TWAMP RFC 5357 performance measurements for low
latency paths. RSVP-TE provides traffic  management capabilities with ECN
style congestion notification using setup and hold RSVP-TE LSP priorities
allowing the ability to preempt LSPs based on traffic class as well as
re-optimization fallback to primary path.  Traffic management features have
been enhanced significantly with newer hardware and software capabilities.
RSVP-TE provides link affinity bits to provide a method to include or
exclude links from TED database for cSPF dynamic LSP instantiation. RSVP-TE
provides Fast Reroute (FRR) pre signaled Make before break (MBB) link, node
and path protection from Point of Local Repair (PLR) to Merge Point (MP)
with FRR extension RFC 4090, yielding approximately 50ms restoration time
for both P2P and P2MP RSVP-TE tunnels.  RSVP-TE supports Inter-AS TE with
ISIS extension RFC 5316 and OSPF extension RFC 5392 and Inter Domain MPLS
and GMPLS RSVP-TE extension RFC 5151.

RSVP-TE has historically been used when bandwidth was constrained, however
as bandwidth has increased exponentially over the years, RSVP-TE has
evolved into a bandwidth management tool to provide bandwidth efficiency
and proactive resource management.

Thanks

Gyan

On Tue, Jul 5, 2022 at 6:15 AM Adrian Farrel <adrian@olddog.co.uk> wrote:

> OK. Thanks.
>
>
>
> A
>
>
>
> *From:* Gyan Mishra <hayabusagsm@gmail.com>
> *Sent:* 04 July 2022 23:50
> *To:* adrian@olddog.co.uk
> *Cc:* TEAS WG <teas@ietf.org>
> *Subject:* Re: [Teas] FW: I-D Action: draft-ietf-teas-rfc3272bis-18.txt
>
>
>
> Hi Adrian
>
>
>
> I am working on some text to Dons questions as well as additional RSVP-TE
> related details to the new section created.
>
>
>
> Thanks
>
>
>
> Gyan
>
>
>
> On Mon, Jul 4, 2022 at 6:07 PM Adrian Farrel <adrian@olddog.co.uk> wrote:
>
> OK.
>
> We now have a small Appendix section to cover CR-LDP.
>
> Does anyone else have a further proposal to address Don's comments or are
> we
> done?
>
> Cheers,
> Adrian
>
> -----Original Message-----
> From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of
> internet-drafts@ietf.org
> Sent: 04 July 2022 23:04
> To: i-d-announce@ietf.org
> Cc: teas@ietf.org
> Subject: I-D Action: draft-ietf-teas-rfc3272bis-18.txt
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Traffic Engineering Architecture and
> Signaling WG of the IETF.
>
>         Title           : Overview and Principles of Internet Traffic
> Engineering
>         Author          : Adrian Farrel
>   Filename        : draft-ietf-teas-rfc3272bis-18.txt
>   Pages           : 97
>   Date            : 2022-07-04
>
> Abstract:
>    This document describes the principles of traffic engineering (TE) in
>    the Internet.  The document is intended to promote better
>    understanding of the issues surrounding traffic engineering in IP
>    networks and the networks that support IP networking, and to provide
>    a common basis for the development of traffic engineering
>    capabilities for the Internet.  The principles, architectures, and
>    methodologies for performance evaluation and performance optimization
>    of operational networks are also discussed.
>
>    This work was first published as RFC 3272 in May 2002.  This document
>    obsoletes RFC 3272 by making a complete update to bring the text in
>    line with best current practices for Internet traffic engineering and
>    to include references to the latest relevant work in the IETF.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-teas-rfc3272bis/
>
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-teas-rfc3272bis-18
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-rfc3272bis-18
>
>
> Internet-Drafts are also available by rsync at
> rsync.ietf.org::internet-drafts
>
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>
> --
>
> [image: Image removed by sender.] <http://www.verizon.com/>
>
> *Gyan Mishra*
>
> *Network Solutions Architect *
>
> *Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*
>
> *M 301 502-1347*
>
>
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*

*M 301 502-1347*

Re: [Teas] FW: I-D Action: draft-ietf-teas-rfc3272bis-18.txt

Attachment: image002.jpg