draft-ietf-teas-rsvp-ingress-protection-15.txt   draft-ietf-teas-rsvp-ingress-protection-16.txt 
Internet Engineering Task Force H. Chen, Ed. Internet Engineering Task Force H. Chen, Ed.
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Experimental R. Torvi, Ed. Intended status: Experimental R. Torvi, Ed.
Expires: September 2, 2018 Juniper Networks Expires: September 2, 2018 Juniper Networks
March 1, 2018 March 1, 2018
Extensions to RSVP-TE for LSP Ingress FRR Protection Extensions to RSVP-TE for LSP Ingress FRR Protection
draft-ietf-teas-rsvp-ingress-protection-15.txt draft-ietf-teas-rsvp-ingress-protection-16.txt
Abstract Abstract
This document describes extensions to Resource Reservation Protocol - This document describes extensions to Resource Reservation Protocol -
Traffic Engineering (RSVP-TE) for locally protecting the ingress node Traffic Engineering (RSVP-TE) for locally protecting the ingress node
of a Point-to-Point (P2P) or Point-to-Multipoint (P2MP) Traffic of a Point-to-Point (P2P) or Point-to-Multipoint (P2MP) Traffic
Engineered (TE) Label Switched Path (LSP). It extends the fast- Engineered (TE) Label Switched Path (LSP). It extends the fast-
reroute (FRR) protection for transit nodes of an LSP to the ingress reroute (FRR) protection for transit nodes of an LSP to the ingress
node of the LSP. The procedures described in this document are node of the LSP. The procedures described in this document are
experimental. experimental.
skipping to change at page 23, line 13 skipping to change at page 23, line 13
will not be registered with IANA and MUST NOT be mentioned by RFCs. will not be registered with IANA and MUST NOT be mentioned by RFCs.
It is suggested to use the following Private Use range: It is suggested to use the following Private Use range:
o 124-127 Reserved for Private Use o 124-127 Reserved for Private Use
It is for an experimental implementation to choose a value from the It is for an experimental implementation to choose a value from the
Private Use range, and to agree with cooperating implementations Private Use range, and to agree with cooperating implementations
participating in the same experiments what values to use. participating in the same experiments what values to use.
+====================+===============+============================+ Within each object class, there is an 8-bit Class Type (also known as
| Class Names | Class Numbers | Class Types | a C-Type). The following list is a suggested registry for use by
+====================+===============+============================+ experiments:
| INGRESS_PROTECTION | TBD | 1: INGRESS_PROTECTION_IP |
| |(124 suggested)| |
+--------------------+---------------+----------------------------+
Within the object (Class Name: INGRESS_PROTECTION, Class Type: 1),
there is an 8-bit Sub-object Type. The following list is a suggested
registry for use by experiments:
Value Name Definition Value Name Definition
----- ---- ---------- ----- ---- ----------
0 Reserved 0 Reserved
1 BACKUP_INGRESS_IPv4_ADDRESS Section 4.1.1 1 BACKUP_INGRESS_IPv4_ADDRESS Section 4.1.1
2 BACKUP_INGRESS_IPv6_ADDRESS Section 4.1.2 2 BACKUP_INGRESS_IPv6_ADDRESS Section 4.1.2
3 INGRESS_IPv4_ADDRESS Section 4.1.3 3 INGRESS_IPv4_ADDRESS Section 4.1.3
4 INGRESS_IPv6_ADDRESS Section 4.1.4 4 INGRESS_IPv6_ADDRESS Section 4.1.4
5 TRAFFIC_DESCRIPTOR_INTERFACE Section 4.1.5 5 TRAFFIC_DESCRIPTOR_INTERFACE Section 4.1.5
6 TRAFFIC_DESCRIPTOR_IPv4_PREFIX Section 4.1.5 6 TRAFFIC_DESCRIPTOR_IPv4_PREFIX Section 4.1.5
 End of changes. 2 change blocks. 
11 lines changed or deleted 4 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/