--- 1/draft-ietf-mpls-psc-updates-04.txt 2014-04-22 06:14:40.827017026 -0700 +++ 2/draft-ietf-mpls-psc-updates-05.txt 2014-04-22 06:14:40.851017612 -0700 @@ -1,27 +1,28 @@ Network Working Group E. Osborne Internet-Draft -Updates: 6378 (if approved) April 21, 2014 +Updates: 6378 (if approved) April 22, 2014 Intended status: Standards Track -Expires: October 23, 2014 +Expires: October 24, 2014 Updates to MPLS Transport Profile Linear Protection - draft-ietf-mpls-psc-updates-04 + 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 liaision statement, and clarify + 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 @@ -30,21 +31,21 @@ 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 23, 2014. + 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. 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