FYI… This updates the discussion of TTE. Specifically it talks a bit more about suuport for RSVP-TE.
Thanks, Tony > Begin forwarded message: > > From: "internet-drafts at ietf.org" <mailforwa...@cloudmails.net> > Subject: New Version Notification for draft-li-rtgwg-tte-02.txt > Date: December 3, 2024 at 10:02:03 AM PST > To: "Andy Smith" <andy.j.sm...@oracle.com>, "Bin Wen" <bin_...@comcast.com>, > "Colby Barth" <cba...@juniper.net>, "Luay Jalil" <luay.ja...@verizon.com>, > "Tony Li" <tony...@tony.li> > Reply-To: internet-dra...@ietf.org > > A new version of Internet-Draft draft-li-rtgwg-tte-02.txt has been > successfully submitted by Tony Li and posted to the > IETF repository. > > Name: draft-li-rtgwg-tte > Revision: 02 > Title: Tactical Traffic Engineering (TTE) > Date: 2024-12-03 > Group: Individual Submission > Pages: 13 > URL: https://www.ietf.org/archive/id/draft-li-rtgwg-tte-02.txt > Status: https://datatracker.ietf.org/doc/draft-li-rtgwg-tte/ > HTMLized: https://datatracker.ietf.org/doc/html/draft-li-rtgwg-tte > Diff: https://author-tools.ietf.org/iddiff?url2=draft-li-rtgwg-tte-02 > > Abstract: > > Conventional traffic engineering approaches for resource management > used by RSVP-TE and SR-TE often leverage estimates of the ingress > traffic demands, during path placement. Unforeseen and/or dynamic > events, can skew these estimates by significant enough margins to > result in unexpected network congestion. Recomputed paths that > address the new demands may take a considerable amount of time, > leaving the network in a sub-optimal state for far too long. > > This document proposes one mechanism that can avert congestion on a > real-time basis. > > > > The IETF Secretariat > >
_______________________________________________ rtgwg mailing list -- rtgwg@ietf.org To unsubscribe send an email to rtgwg-le...@ietf.org
