<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd"[
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC6428 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6428.xml">
<!ENTITY RFC6310 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6310.xml">
<!ENTITY RFC5885 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5885.xml">
<!ENTITY RFC5085 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5085.xml">
<!ENTITY RFC5880 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5880.xml">
<!ENTITY RFC5881 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5881.xml">
<!ENTITY RFC4446 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4446.xml">
<!ENTITY RFC4447 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4447.xml">
]>


<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc rfcedstyle="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>

<rfc number="7189" category="std" ipr="trust200902" submissionType="IETF" consensus="yes">

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<front>


	<title abbrev="VCCV for MPLS-TP">Virtual Circuit Connectivity
Verification (VCCV) Capability&nbsp;Advertisement&nbsp;for&nbsp;MPLS&nbsp;Transport&nbsp;Profile&nbsp;(MPLS&nbhy;TP)</title>

	<author initials='G.' surname="Mirsky" fullname='Greg Mirsky'>
		<organization>Ericsson</organization>
		<address>
			<email>gregory.mirsky@ericsson.com</email>
		</address> 
	</author>
 
    <date month="March" year="2014" />

    <area>Routing</area>

   <keyword>PW VCCV</keyword>

   <keyword>MPLS-TP CC/CV/RDI</keyword>

	<abstract>
 
	<t>
	This document specifies how signaling and selection processes for Pseudowire (PW) Virtual Circuit Connectivity Verification (VCCV) are modified
	to ensure backward compatibility and allow use of proactive Connectivity Verification (CV), Continuity Check (CC), and Remote Defect
	Indication (RDI) over MPLS Transport Profile (MPLS-TP) PWs. This document introduces four new CV types and, to accommodate them, 
	a new VCCV Extended CV parameter for PW Interface Parameters Sub-TLV is defined.
    </t>
	</abstract>
</front>

<middle>
  <section anchor="intro" title="Introduction">
      <t>
         Proactive Connectivity Verification (CV), Continuity Check (CC), and Remote Defect Indication (RDI) for the MPLS Transport Profile <xref target="RFC6428"></xref>
         are applicable to all constructs of the MPLS-TP, including pseudowires
(PWs). If the control plane is used to operate and 
         manage PWs
 then the procedures defined in <xref target="RFC5085"/> and <xref target="RFC5885"></xref> 
         should be used to select the proper type of Control Channel and the corresponding
         type of Connectivity Verification. This document specifies how signaling and selection processes are modified to ensure 
         backward compatibility
 and allow use of proactive CV-CC-RDI over MPLS-TP PWs.
         </t>
         
     <section title="Conventions Used in This Document">
         <section title="Terminology">

            <t>BFD:            Bidirectional Forwarding Detection
</t>
            <t>CC:              Continuity Check
</t>
            <t>CV:               Connectivity Verification
</t>
            <t>PE:               Provider Edge
</t>
            <t>VCCV:          Virtual Circuit Connectivity Verification
</t>
         </section>    
         
        <section title="Requirements Language">
             <t>
	  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
                "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 
	  "OPTIONAL" in this document are to be interpreted as described in 
	  <xref target="RFC2119"></xref>.
             </t>
          </section>
      </section>
     </section>
      
     <section anchor="cc-cv-pw" title="MPLS-TP CC-CV on Pseudowires">
          <t>
             PW VCCV can support several CV Types, and it can support an arbitrary combination of CV modes
             advertised in the CV Types field of the VCCV Interface Parameter sub-TLV <xref target="RFC4446"/> <xref target="RFC4447"/>.
             Currently, six types of CV have been defined for PW VCCV. This document
             introduces four new CV types and, to accommodate them, a new VCCV Extended CV parameter
             for the PW Interface Parameters Sub-TLV is defined.
          </t>
          <section anchor="vccv-ext-sub-tlv" title="VCCV Extended CV Advertisement Sub-TLV">
             <t>
                The format of the VCCV Extended CV Advertisement is a TLV where
the format is as follows:
             </t>   
         <figure align="left" anchor="vccv-ext-cv-param"
                title="VCCV Extended CV Parameter Format">
          <artwork><![CDATA[    
 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 | Type = 0x19 |    Length     |   CV Type    |   Reserved     |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
        </figure>

             <t>
             The Length field is the length of the sub-TLV, including type and the Length field itself. The minimum length is 4.
             It is recommended that extensions to the sub-TLV be done in 4-byte increments.
             </t>
             <t>
              The Reserved field MUST be set to zeroes on transmit and ignored on receive.
             </t>

             <t>
                The CV Type field is a bitmask that lists types of CV monitoring that a PE is capable
of supporting. The VCCV Extended CV parameter sub-TLV MUST appear in combination
                with the VCCV parameter sub-TLV. If the VCCV parameter sub-TLV is missing, then the VCCV
                Extended CV parameter sub-TLV SHOULD be ignored.  
             </t>
       
          </section>
          
          <section anchor="cc-cv-types" title="MPLS-TP CC-CV Types">
              <t>
              <xref target="RFC6428"/> defines coordinated and independent modes of monitoring point-to-point
              bidirectional connection that can be applied to monitoring PWs. 

At the same time, <xref target="RFC6310"/>
              defines how BFD-based Operations, Administration, and Maintenance
(OAM) can map to the status of an Attachment Circuit.
              Thus, there could be four MPLS-TP CV types for each combination of mode and functionality:
              </t>
              
 <texttable anchor="bitmask_values_tbl" title="Bitmask Values for MPLS-TP CV Types">
    <ttcol align='center'>Modes</ttcol>
    <ttcol align='center'>Fault Detection Only</ttcol>
    <ttcol align='center'>Fault Detection and Status Signaling</ttcol>
    <c>Independent Mode</c>
    <c>0x01</c>
    <c>0x02</c>
    <c>Coordinated Mode</c>
    <c>0x04</c>
    <c>0x08</c>
</texttable>                           
          </section>
          
     <section anchor="cc-cv-operation" title="MPLS-TP CC-CV Type Operation">
        <t>
            According to <xref target="RFC6428"/>, connectivity verification is part of MPLS-TP CC/CV
            operation that can be used with VCCV Control Channel Type 1 <xref
target="RFC5085"/>. If VCCV Control Channel Type 1 is 
            selected, then PEs MAY select one of the MPLS-TP
 CC-CV types as the VCCV CV mechanism to be used for this PW.      
        </t>
     </section>
     
     <section anchor="cv-type-select" title="CV Type Selection">

        <t>
           CV selection rules that have been defined in Section 7 of <xref
target="RFC5085"/> and updated in Section 4
           of <xref target="RFC5885"/> are augmented in this document.
        </t>
        <t>   
            If VCCV Control Channel Type 1 is chosen according to Section 7 of <xref target="RFC5085"/>
            and a common set of proactive CV types that are advertised by both PEs includes
            MPLS-TP CC-CV types and some BFD CV types, then MPLS-TP CC-CV takes precedence
            over any type of BFD CV. If multiple MPLS-TP CV types are advertised by both PEs, then
 the
            following list (ordered by descending priority) is used:
        </t>
  
        <t>
          <list style="numbers">
          <t>
0x08 - Coordinated mode for PW Fault Detection and AC/PW Fault Status Signaling 
</t>
          
          <t>
0x04 - Coordinated mode for PW Fault Detection only
</t>
          
          <t>
0x02 - Independent mode for PW Fault Detection and AC/PW Fault Status Signaling
</t>
          
          <t>
0x01 - Independent mode for PW Fault Detection only </t>
          </list>
           </t>
       </section>   
     </section>
 
     <section anchor="iana-consider" title="IANA Considerations">
     <t>
     The PW Interface Parameters Sub-TLV registry is defined in <xref target="RFC4446"/>. 
     </t>
     <t>
     IANA has reserved a new PW Interface Parameters Sub-TLV type as follows:
     </t>

  <texttable anchor="ext-vccv-param-tbl" title="New PW Interface Parameters Sub-TLV">
    <ttcol align='center'>Parameter ID</ttcol>
    <ttcol align='left'>Length</ttcol>
    <ttcol align='center'>Description</ttcol>
    <ttcol align='left'>Reference</ttcol>
    <c>0x19</c>
    <c>variable</c>
    <c>VCCV&nbsp;Extended&nbsp;CV&nbsp;Parameter</c>
    <c>This&nbsp;document</c>
    </texttable>
  
     <section title="VCCV Extended CV Types">
     <t>
         IANA has set up a registry of VCCV Extended CV Types. These are 8-bit
         values. Extended CV Type values 0x01, 0x02, 0x04, and 0x08 are specified in
         <xref target="cc-cv-types"/> of this document. The remaining values (0x10
         through 0x80) are to be assigned by IANA using the "IETF Review" policy defined in
         <xref target="RFC5226"/>. A VCCV Extended Connectivity Verification Type description and a reference to an
         RFC approved by the IESG are required for any assignment from this registry.    
     </t>
 <texttable anchor="cv_types_tbl" title="VCCV Extended Connectivity Verification (CV) Types">
    <ttcol align='center'>Bit(Value)</ttcol>
    <ttcol align='left'>Description</ttcol>
    <c>Bit&nbsp;0&nbsp;(0x01)</c>
    <c>Independent mode for PW Fault Detection only</c>
    <c>Bit&nbsp;1&nbsp;(0x02)</c>
    <c>Independent mode for PW Fault Detection and AC/PW Fault Status Signaling</c>
    <c>Bit&nbsp;2&nbsp;(0x04)</c>
    <c>Coordinated mode for PW Fault Detection only</c>
    <c>Bit&nbsp;3&nbsp;(0x08)</c>
    <c>Coordinated mode for PW Fault Detection and AC/PW Fault Status Signaling</c>
    <c>Bit&nbsp;4&nbsp;(0x10)</c>
    <c>Unassigned</c>
    <c>Bit&nbsp;5&nbsp;(0x20)</c>
    <c>Unassigned</c>
    <c>Bit&nbsp;6&nbsp;(0x40)</c>
    <c>Unassigned</c>
    <c>Bit&nbsp;7&nbsp;(0x80)</c>
    <c>Unassigned</c>
</texttable> 
   
     </section>
     </section>
     
     <section anchor="security" title="Security Considerations">
     <t>
     Routers that implement the additional CV Type defined herein are subject to the same security considerations
     as defined in <xref target="RFC5085"/>, <xref target="RFC5880"/>, <xref target="RFC5881"/>, and <xref target="RFC6428"/>.  This specification does not raise any
     additional security issues beyond those.
     </t>
     </section>
      
     
      <section title="Acknowledgements">
         <t>
           The author gratefully acknowledges the thoughtful review, comments,
and explanations provided by Dave Allan and Carlos Pignataro.
         </t>  
      </section>

  </middle>
  
    <back>
    <references title="Normative References">
     &RFC2119;

     &RFC6428;

     &RFC6310;

     &RFC5885;

     &RFC5085;

      &RFC5880;

      &RFC5881;

      &RFC4446;

      &RFC4447;

    </references>

    <references title="Informative References">

    <?rfc include='reference.RFC.5226'?>

 <!--?rfc.include='reference.IANA'?-->
    </references>
 </back>
 </rfc>   
    
