Re: [Teas] RSVP-TE text in draft-ietf-teas-rfc3272bis
Adrian Farrel <adrian@olddog.co.uk> Thu, 07 July 2022 10:43 UTC
Return-Path: <adrian@olddog.co.uk>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC6EDC15CF34 for <teas@ietfa.amsl.com>; Thu, 7 Jul 2022 03:43:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_OBFU_JPG_ATTACH=0.01, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RGkJpXCI2DOX for <teas@ietfa.amsl.com>; Thu, 7 Jul 2022 03:43:08 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE9ACC15CF31 for <teas@ietf.org>; Thu, 7 Jul 2022 03:43:07 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta6.iomartmail.com (8.14.7/8.14.7) with ESMTP id 267Ah4ep006237; Thu, 7 Jul 2022 11:43:04 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 49D104604B; Thu, 7 Jul 2022 11:43:04 +0100 (BST)
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 338004604A; Thu, 7 Jul 2022 11:43:04 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs3.iomartmail.com (Postfix) with ESMTPS; Thu, 7 Jul 2022 11:43:04 +0100 (BST)
Received: from LAPTOPK7AS653V (93.197.bbplus.pte-ag1.dyn.plus.net [81.174.197.93] (may be forged)) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.7/8.14.7) with ESMTP id 267Ah2wG002253 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 7 Jul 2022 11:43:03 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Gyan Mishra' <hayabusagsm@gmail.com>
Cc: 'TEAS WG' <teas@ietf.org>
References: <165697222560.27478.2338137252302838593@ietfa.amsl.com> <049301d88ff2$701ff5f0$505fe1d0$@olddog.co.uk> <CABNhwV1yJX0uAriNsc4K8EuhFXqHAtHdNqu1prCzh+9UaFBp6Q@mail.gmail.com> <04e001d89058$216be2f0$6443a8d0$@olddog.co.uk> <CABNhwV24pqB8b-RhvQENNYHNegwc6kfRnt_uHiysawC38cdFtg@mail.gmail.com> <05cd01d89099$5fea0d40$1fbe27c0$@olddog.co.uk> <CABNhwV35t7+sStriKEQb3rtevsWKrKnZpMCkNoaz+tjSy4Q4tg@mail.gmail.com> <010301d8917d$e8c14770$ba43d650$@olddog.co.uk> <CABNhwV3cYP3pqw1UVNG1FmMAS+=6Ee89Xngeyga_vwPgcjuDZg@mail.gmail.com>
In-Reply-To: <CABNhwV3cYP3pqw1UVNG1FmMAS+=6Ee89Xngeyga_vwPgcjuDZg@mail.gmail.com>
Date: Thu, 07 Jul 2022 11:43:02 +0100
Organization: Old Dog Consulting
Message-ID: <018a01d891ee$55d78020$01868060$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_018B_01D891F6.B79E3210"
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AQJ6xDUikB2z9j37yjU0p1ek/ZsZfAK4AiS2AdC+zCcBAzhsWAHjwZhdAY/F5M4CHhnEVAIqUnInAoKnONSrr/8+MA==
X-Originating-IP: 81.174.197.93
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-27000.007
X-TM-AS-Result: No--37.948-10.0-31-10
X-imss-scan-details: No--37.948-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-27000.007
X-TMASE-Result: 10--37.947600-10.000000
X-TMASE-MatchedRID: 7u3eoxEoplA0QDP3j4T8uQJbm0s4Rkn0jrVn4cme+w7HbztUafrIJqST 6+/Cd0YP4dOsNKuqfayHjmbFYjMX2zxIZLzl0pWIQz86IKjayBOVUcz8XpiS9IiAeZ2rVOJt6X1 QHIGAi3uPd1lLIAtF4rAYI/DJMXiv0kiQ3AKprjJGmygMKaQXUuQ0jDxGUAJDArRmBtM54pQWn6 /ikoy0woV7eoB5lAIDXJaGnOmQZy0Q8nn4qZx1aaEe/yf6jZsgjPAf+2Ld9LVYL/tox9XQkQ0UK NNtdi1cXRy9DgTwN1RLtBtfUVMvKi6iR694qthWyEWUXyOwgqEdZEkR8Y/meSqNqCcMugBSUZFd cE0uFTFEotrrfbJfNKBRz1PCB3BWUAvrWhvWeD39dk7KkTJ3x07OAEf3BE8yUh4weWPqOWQDLr9 vPVWwiArewfr9uhLV88cLohcr5LA9X2XFMrVier5GKLocCueSRHSgjCgw/JXgNBpYDGtSzuQydR Uvl3QTuojzzl0fW4sOzHzVz3SW/Hm6vS/eQOsMZZn0Jtll/5uJJ72DuZB0nFHewY36PuY0L31P6 4kiV5EuDhoR+qZH1+rSTlZpjLcHczVqmQFagAIqXuKH5Jbj7E7nLUqYrlslbo9qnUw920dLpCLN 4NR43phchs7B6T9BLHH6CMWMLLXa2wtrEP04wbeNXXhVTPU8+s0+QZYAcN/1csXkzgSq1OHMs9r Q0YdlS1Tj+kqv+huQiUqgvBUFUDwNakGbUKNlOY0uFdPXUM65bvv/Lz3qyEsY9G/RZ3FCr1MJnT sKi0/FQNPEve+5IF1bBFlamKmoZmGkOF0fx8wNH8W+VHPtpknrQVDWVC8AIeaM1LLgEiKvXSmSd lcYmrLn+0Vm71Lcpz9dqB3JWUSmJOmLY8y0botkBWmEtb9tqxB32o9eGclVaBFytIQUtw==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/Nhzh8KAKhNOnOh2_sZQY-3Gfk1Q>
Subject: Re: [Teas] RSVP-TE text in draft-ietf-teas-rfc3272bis
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2022 10:43:11 -0000
Thanks, Gyan. I posted -19 so we are up-to-date with all text changes. There still remain the issues raised by Don wrt the Appendixes: I will use a separate thread for that. Cheers, Adrian From: Gyan Mishra <hayabusagsm@gmail.com> Sent: 06 July 2022 13:49 To: Adrian Farrel <adrian@olddog.co.uk> Cc: TEAS WG <teas@ietf.org> Subject: Re: RSVP-TE text in draft-ietf-teas-rfc3272bis Looks Excellent! Ready for publication! Gyan On Wed, Jul 6, 2022 at 5:18 PM Adrian Farrel <adrian@olddog.co.uk <mailto:adrian@olddog.co.uk> > wrote: OK, Gyan. Merged and polished gives us… 5.1.3.4. RSVP-TE RSVP-TE is a protocol extension of RSVP (Section 5.1.3.2) for traffic engineering. The base specification is found in [RFC3209]. RSVP-TE enables the establishment of traffic engineered MPLS LSPs (TE LSPs), using loose or strict paths, and taking into consideration network constraints such as available bandwidth. The extension supports signaling LSPs on explicit paths that could be administratively specified, or computed by a suitable entity (such as a PCE, Section 5.1.3.11) based on QoS and policy requirements, taking into consideration the prevailing network state as advertised by IGP extension for ISIS in [RFC5305], for OSPFV2 in [RFC3630], and for OSPFv3 in [RFC5329]. RSVP-TE enables the reservation of resources (for example, bandwidth) along the path. RSVP-TE includes the ability to preempt LSP based on priorities, and uses link affinities to include or exclude links from the paths of LSPs. The protocol is further extended to support Fast Reroute (FRR) [RFC4090], Diffserv [RFC4124], and bidirectional LSPs [RFC7551]. RSVP-TE extensions for support for GMPLS (see Section 5.1.3.5 are specified in [RFC3473]. 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. RSVP-TE has evolved to provide real time dynamic metrics for path selection for low latency paths using extensions to ISIS [RFC7810] and OSPF [RFC7471] based on STAMP [RFC8972] and TWAMP [RFC5357] performance measurements. RSVP-TE has historically been used when bandwidth was constrained, however, as bandwidth has increased, RSVP-TE has developed into a bandwidth management tool to provide bandwidth efficiency and proactive resource management. What do you think? Thanks, Adrian From: Gyan Mishra <hayabusagsm@gmail.com <mailto:hayabusagsm@gmail.com> > Sent: 05 July 2022 19:18 To: adrian@olddog.co.uk <mailto:adrian@olddog.co.uk> Cc: TEAS WG <teas@ietf.org <mailto:teas@ietf.org> > Subject: Re: [Teas] FW: I-D Action: draft-ietf-teas-rfc3272bis-18.txt Hi Adrian I was expanding on what you already had in 5.1.3.4 so I was thinking you could just add on / integrate into what you already have. Thanks Gyan On Tue, Jul 5, 2022 at 2:02 PM Adrian Farrel <adrian@olddog.co.uk <mailto:adrian@olddog.co.uk> > wrote: Thanks Gyan, Do you propose that that replace Section 5.1.3.4 or should I try to integrate it? Cheers, Adrian From: Gyan Mishra <hayabusagsm@gmail.com <mailto:hayabusagsm@gmail.com> > Sent: 05 July 2022 18:17 To: adrian@olddog.co.uk <mailto:adrian@olddog.co.uk> Cc: TEAS WG <teas@ietf.org <mailto:teas@ietf.org> > Subject: 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 <mailto:adrian@olddog.co.uk> > wrote: OK. Thanks. A From: Gyan Mishra <hayabusagsm@gmail.com <mailto:hayabusagsm@gmail.com> > Sent: 04 July 2022 23:50 To: adrian@olddog.co.uk <mailto:adrian@olddog.co.uk> Cc: TEAS WG <teas@ietf.org <mailto: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 <mailto: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 <mailto:i-d-announce-bounces@ietf.org> > On Behalf Of internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> Sent: 04 July 2022 23:04 To: i-d-announce@ietf.org <mailto:i-d-announce@ietf.org> Cc: teas@ietf.org <mailto: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 <mailto: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 <mailto:Teas@ietf.org> https://www.ietf.org/mailman/listinfo/teas -- <http://www.verizon.com/> Gyan Mishra Network Solutions Architect Email gyan.s.mishra@verizon.com <mailto:gyan.s.mishra@verizon.com> M 301 502-1347 -- <http://www.verizon.com/> Gyan Mishra Network Solutions Architect Email gyan.s.mishra@verizon.com <mailto:gyan.s.mishra@verizon.com> M 301 502-1347 -- <http://www.verizon.com/> Gyan Mishra Network Solutions Architect Email gyan.s.mishra@verizon.com <mailto:gyan.s.mishra@verizon.com> M 301 502-1347 -- <http://www.verizon.com/> Gyan Mishra Network Solutions Architect Email gyan.s.mishra@verizon.com <mailto:gyan.s.mishra@verizon.com> M 301 502-1347
- [Teas] I-D Action: draft-ietf-teas-rfc3272bis-18.… internet-drafts
- [Teas] FW: I-D Action: draft-ietf-teas-rfc3272bis… Adrian Farrel
- Re: [Teas] FW: I-D Action: draft-ietf-teas-rfc327… Gyan Mishra
- Re: [Teas] FW: I-D Action: draft-ietf-teas-rfc327… Adrian Farrel
- Re: [Teas] FW: I-D Action: draft-ietf-teas-rfc327… Gyan Mishra
- Re: [Teas] FW: I-D Action: draft-ietf-teas-rfc327… Adrian Farrel
- Re: [Teas] FW: I-D Action: draft-ietf-teas-rfc327… Gyan Mishra
- [Teas] RSVP-TE text in draft-ietf-teas-rfc3272bis Adrian Farrel
- Re: [Teas] RSVP-TE text in draft-ietf-teas-rfc327… Gyan Mishra
- Re: [Teas] RSVP-TE text in draft-ietf-teas-rfc327… Adrian Farrel
- Re: [Teas] RSVP-TE text in draft-ietf-teas-rfc327… Gyan Mishra