draft-ietf-mpls-tp-requirements-07.txt   draft-ietf-mpls-tp-requirements-08.txt 
skipping to change at page 1, line 16 skipping to change at page 1, line 16
Expires: November 19, 2009 AT&T Expires: November 19, 2009 AT&T
M. Betts, Ed. M. Betts, Ed.
Nortel Networks Nortel Networks
N. Sprecher N. Sprecher
Nokia Siemens Networks Nokia Siemens Networks
S. Ueno S. Ueno
NTT NTT
May 18, 2009 May 18, 2009
MPLS-TP Requirements MPLS-TP Requirements
draft-ietf-mpls-tp-requirements-07 draft-ietf-mpls-tp-requirements-08
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 3, line 36 skipping to change at page 3, line 36
2.8.1.3. Reversion . . . . . . . . . . . . . . . . . . . . 22 2.8.1.3. Reversion . . . . . . . . . . . . . . . . . . . . 22
2.8.2. Restoration . . . . . . . . . . . . . . . . . . . . . 22 2.8.2. Restoration . . . . . . . . . . . . . . . . . . . . . 22
2.8.3. Triggers for protection, restoration, and reversion . 23 2.8.3. Triggers for protection, restoration, and reversion . 23
2.8.4. Management plane operation of protection and 2.8.4. Management plane operation of protection and
restoration . . . . . . . . . . . . . . . . . . . . . 23 restoration . . . . . . . . . . . . . . . . . . . . . 23
2.8.5. Control plane and in-band OAM operation of recovery . 24 2.8.5. Control plane and in-band OAM operation of recovery . 24
2.8.6. Topology-specific recovery mechanisms . . . . . . . . 25 2.8.6. Topology-specific recovery mechanisms . . . . . . . . 25
2.8.6.1. Ring protection . . . . . . . . . . . . . . . . . 25 2.8.6.1. Ring protection . . . . . . . . . . . . . . . . . 25
2.9. QoS requirements . . . . . . . . . . . . . . . . . . . . . 28 2.9. QoS requirements . . . . . . . . . . . . . . . . . . . . . 28
2.10. Security requirements . . . . . . . . . . . . . . . . . . 28 2.10. Security requirements . . . . . . . . . . . . . . . . . . 28
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
4. Security Considerations . . . . . . . . . . . . . . . . . . . 29 4. Security Considerations . . . . . . . . . . . . . . . . . . . 29
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 29 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 29
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.1. Normative References . . . . . . . . . . . . . . . . . . . 29 6.1. Normative References . . . . . . . . . . . . . . . . . . . 29
6.2. Informative References . . . . . . . . . . . . . . . . . . 30 6.2. Informative References . . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 31
1. Introduction 1. Introduction
Bandwidth demand continues to grow worldwide, stimulated by the Bandwidth demand continues to grow worldwide, stimulated by the
skipping to change at page 14, line 27 skipping to change at page 14, line 27
7 MPLS-TP MUST support traffic engineered point to point (P2P) and 7 MPLS-TP MUST support traffic engineered point to point (P2P) and
point to multipoint (P2MP) transport paths. point to multipoint (P2MP) transport paths.
8 MPLS-TP MUST support unidirectional, co-routed bidirectional and 8 MPLS-TP MUST support unidirectional, co-routed bidirectional and
associated bidirectional point-to-point transport paths. associated bidirectional point-to-point transport paths.
9 The end points of a co-routed bidirectional transport path MUST 9 The end points of a co-routed bidirectional transport path MUST
be aware of the pairing relationship of the forward and reverse be aware of the pairing relationship of the forward and reverse
paths used to support the bidirectional service. paths used to support the bidirectional service.
10 The intermediate nodes of a co-routed bidirectional transport 10 All nodes on the path of a co-routed bidirectional transport path
path at each (sub-)layer MUST be aware of the pairing in the same (sub-)layer as the path MUST be aware of the pairing
relationship of the forward and the backward directions of that relationship of the forward and the backward directions of the
transport path. transport path.
11 The end points of an associated bidirectional transport path MUST 11 The end points of an associated bidirectional transport path MUST
be aware of the pairing relationship of the forward and reverse be aware of the pairing relationship of the forward and reverse
paths used to support the bidirectional service. paths used to support the bidirectional service.
12 The intermediate nodes of an associated bidirectional transport 12 Nodes on the path of an associated bidirectional transport path
path at each (sub-)layer SHOULD NOT be aware of the pairing where both the forward and backward directions transit the same
relationship of the forward and the backward directions of that node in the same (sub-)layer as the path SHOULD be aware of the
transport path. pairing relationship of the forward and the backward directions
of the transport path.
13 MPLS-TP MUST support bidirectional transport paths with symmetric 13 MPLS-TP MUST support bidirectional transport paths with symmetric
bandwidth requirements, i.e. the amount of reserved bandwidth is bandwidth requirements, i.e. the amount of reserved bandwidth is
the same between the forward and backward directions. the same between the forward and backward directions.
14 MPLS-TP MUST support bidirectional transport paths with 14 MPLS-TP MUST support bidirectional transport paths with
asymmetric bandwidth requirements, i.e. the amount of reserved asymmetric bandwidth requirements, i.e. the amount of reserved
bandwidth differs between the forward and backward directions. bandwidth differs between the forward and backward directions.
15 MPLS-TP MUST support the logical separation of the control and 15 MPLS-TP MUST support the logical separation of the control and
 End of changes. 4 change blocks. 
9 lines changed or deleted 10 lines changed or added

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