Updates to MPLS Transport Profile Linear Protection
draft-ietf-mpls-psc-updates-05
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (mpls WG)
|
|
Author |
|
Eric Osborne
|
|
Last updated |
|
2014-05-15
(latest revision 2014-04-22)
|
|
Replaces |
|
draft-osborne-mpls-psc-updates
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Loa Andersson
|
|
Shepherd write-up |
|
Show
(last changed 2014-03-14)
|
IESG |
IESG state |
|
Approved-announcement to be sent::Revised I-D Needed
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Adrian Farrel
|
|
Send notices to |
|
mpls-chairs@tools.ietf.org, draft-ietf-mpls-psc-updates@tools.ietf.org
|
IANA |
IANA review state |
|
IANA OK - Actions Needed
|
Network Working Group E. Osborne
Internet-Draft
Updates: 6378 (if approved) April 22, 2014
Intended status: Standards Track
Expires: October 24, 2014
Updates to MPLS Transport Profile Linear Protection
draft-ietf-mpls-psc-updates-05
Abstract
This document contains a number of updates to the Protection State
Coordination (PSC) logic defined in RFC6378, "MPLS Transport Profile
(MPLS-TP) Linear Protection". These updates provide some rules and
recommendations around the use of TLVs in PSC, address some issues
raised in an ITU-T liaison statement, and clarify PSC's behavior in a
case not well explained in RFC6378.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 24, 2014.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
Osborne Expires October 24, 2014 [Page 1]
Internet-Draft PSC-updates April 2014
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Message Formatting and Error Handling . . . . . . . . . . . . 3
2.1. Format on the wire . . . . . . . . . . . . . . . . . . . 3
2.2. PSC TLV Format . . . . . . . . . . . . . . . . . . . . . 3
2.3. Error handling . . . . . . . . . . . . . . . . . . . . . 3
2.3.1. Malformed messages . . . . . . . . . . . . . . . . . 4
2.3.2. Well-formed but unexpected TLV . . . . . . . . . . . 4
3. Incorrect local status after failure . . . . . . . . . . . . 4
4. Handling a capabilities mismatch . . . . . . . . . . . . . . 5
4.1. Protection Type mismatch . . . . . . . . . . . . . . . . 5
4.2. R mismatch . . . . . . . . . . . . . . . . . . . . . . . 6
4.3. Unsupported modes . . . . . . . . . . . . . . . . . . . . 6
5. Reversion deadlock due to a race condition . . . . . . . . . 6
6. Clarifying PSC's behavior in the face of multiple inputs . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
10.1. Normative References . . . . . . . . . . . . . . . . . . 9
10.2. Informative References . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
This document contains a number of updates to PSC [RFC6378]. One
provides some rules and recommendations around the use of TLVs in
PSC. Three of them address issues #2, #7 and #8 as identified in the
ITU's liaison statement "Recommendation ITU-T G.8131/Y.1382 revision
- Linear protection switching for MPLS-TP networks" [LIAISON].
Another clears up a behavior which was not well explained in RFC6378.
These updates are not changes to the protocol's packet format or to
PSC's design, but are corrections and clarifications to specific
aspects of the protocol's procedures.
This document assumes familiarity with RFC6378 and its terms,
conventions and acronyms. Any term used in this document but not
Osborne Expires October 24, 2014 [Page 2]
Show full document text