<?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 RFC2629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2629.xml">
<!ENTITY I-D.ietf-rtgwg-dt-encap SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-rtgwg-dt-encap-00.xml">
<!ENTITY I-D.ashwood-nvo3-oam-requirements SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ashwood-nvo3-oam-requirements-04.xml">

<!ENTITY I-D.ietf-sfc-oam-framework SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-sfc-oam-framework-00.xml">
<!ENTITY I-D.ietf-bier-oam-requirements SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-bier-oam-requirements-00.xml">
<!ENTITY I-D.ietf-spring-sr-oam-requirement SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-spring-sr-oam-requirement-00.xml">
<!ENTITY I-D.kumarkini-mpls-spring-lsp-ping SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-kumarkini-mpls-spring-lsp-ping-04.xml">

]>

<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>

<rfc category="info" ipr="trust200902" docName="draft-mwnpkazcap-rtgwg-common-oam-00">

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<front>
	<title abbrev='Common OAM'>Rationale for Transport-independent Common Operations, Administration and Maintenance (OAM)</title>

	<author initials='G.' surname="Mirsky" fullname='Greg Mirsky'>
		<organization>Ericsson</organization>
		<address>
			<email>gregory.mirsky@ericsson.com</email>
		</address> 
	</author>
	
	<author initials='R.' surname="White" fullname='Russ White'>
		<organization>Ericsson</organization>
		<address>
			<email>russ@riw.us</email>
		</address> 
	</author>

	<author initials='E.' surname="Nordmark" fullname='Erik Nordmark'>
		<organization>Arista Networks</organization>
		<address>
			<email>nordmark@acm.org</email>
		</address> 
	</author>

	<author initials='C.' surname="Pignataro" fullname='Carlos Pignataro'>
		<organization>Cisco Systems, Inc.</organization>
		<address>
			<email>cpignata@cisco.com</email>
		</address> 
	</author>

	<author initials='N.' surname="Kumar" fullname='Nagendra Kumar'>
		<organization>Cisco Systems, Inc.</organization>
		<address>
			<email>naikumar@cisco.com</email>
		</address> 
	</author>
	
	<author initials='S.' surname="Aldrin" fullname='Sam Aldrin'>
		<organization>Google</organization>
		<address>
			<email>aldrin.ietf@gmail.com</email>
		</address> 
	</author>

	<author initials='L.' surname="Zheng" fullname='Lianshu Zheng'>
		<organization>Huawei Technologies</organization>
		<address>
			<email>vero.zheng@huawei.com</email>
		</address> 
	</author>
	
	<author initials='M.' surname="Chen" fullname='Mach Chen'>
		<organization>Huawei Technologies</organization>
		<address>
			<email>mach.chen@huawei.com</email>
		</address> 
	</author>

	<author initials='N.' surname="Akiya" fullname='Nobo Akiya'>
		<organization>Big Switch Networks</organization>
		<address>
			<email>nobo.akiya.dev@gmail.com</email>
		</address> 
	</author>

	<author initials='S' surname="Pallagatti" fullname='Santosh Pallagatti'>
		<organization>Juniper Networks</organization>
		<address>
			<email>santoshpk@juniper.net</email>
		</address> 
	</author>

    <date day="19" month="October" year="2015" />

    <area>Routing</area>

    <workgroup>RTG  Working Group</workgroup>

    <keyword>Internet-Draft</keyword>
   
   <keyword>OAM</keyword>
	
	<abstract>
	<t>
	   This document discusses set of Operations, Administration and Maintenance (OAM) tools that can be used
	   as common OAM independent of specific encapsulation at server layer.
 Requirements toward server layer 
	   to support common OAM are listed as well.
	 </t>
	</abstract>
</front>

<middle>
  <section anchor="intro" title="Introduction">
        <t>
The introduction and development of new service layers such as Service Function Chaining (SFC) 
and Bit-Ingress Explicit Replication (BIER), is driving the need
for new Operations, Administration and Maintenance (OAM) tools.
This document discusses benefits of Common transport independent OAM 
solution  to support components of
network management framework known as Fault, Configuration, Accounting, Performance, and Security (FCAPS):
<list style="symbols">
<t>Fault monitoring and defect localization;</t>
<t>Performance measurement, both passive and active.</t>
</list>
 </t>
         
     <section title="Conventions used in this document">
         <section title="Terminology">
<t>
The term "OAM" used in this document interchangeably with longer version
"set of OAM protocols, methods and tools for a particular layer".
</t>
     <t>BIER:    Bit-Ingress Explicit Replication</t>
 
    <t>FCAPS: Fault, Configuration, Accounting, Performance, and Security 
</t>
     <t>OAM:      Operations, Administration and Maintenance</t>
     <t>SFC:      Service Function Chaining</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="use-cases" title="Use Case for Common OAM">
  <t>
Recently several new service layers have been developed in IETF. Each of 
responsible groups, e.g. SPRING, NVO3, SFC, BIER,
have formulated a set of OAM requirements, specific to their respective layer 
<xref target="I-D.ietf-spring-sr-oam-requirement"/>, <xref target="I-D.ashwood-nvo3-oam-requirements"/>,
<xref target="I-D.ietf-sfc-oam-framework"/>, and <xref target="I-D.ietf-bier-oam-requirements"/>. Proposals 
have already been put forward
to satisfy those requirements, though mostly by enhancing existing OAM tools, 
such as LSP Ping <xref target="I-D.kumarkini-mpls-spring-lsp-ping"/>. Enhancing existing tools certainly
leads to faster deployment of OAM but may create operational issues later on. For instance,
these new service layers
may be implemented a wide range of transport layers, e.g. MPLS or IPv6, so 
OAM tools that are transport-oriented like LSP Ping
would not be able to perform end-to-end for inter-domain scenario.
  </t>
  <t>
  At the same time, the Bidirectional Forwarding Detection (BFD) protocol 
  is being successfully adopted for IPv6 and MPLS
  networks,  and efforts are moving forward to define transport-independent OAM tool 
  based only on the requirements of one of these 
  new services, BIER.
  </t>
<t>
<xref target="I-D.ietf-rtgwg-dt-encap"/> raised question of common OAM for NVO3, SFC, and BIER. We want to take this further and:
 <list style="symbols">
 <t>
 analyze relevant OAM requirements and document common set of requirements
 towards OAM as well as requirements toward aservice layer to enable its
 ability to support OAM;
 </t>
 <t>
 analyze OAM solutions (proactive and on-demand CC/CV, PM, FM) being proposed and formulate 
 approach to structure OAM tools that may be re-used across several types on encapsulation.
 </t>
 </list>
</t>
</section>

  <section anchor="iana-considerations" title="IANA Considerations">
  <t>
  This document does not propose any IANA consideration. This section may be removed.
  </t>
  </section>
 
   <section anchor="security-considerations" title="Security Considerations">
   <t>
   This document does not raise any security concerns or issues in addition to ones common to networking.
   </t>
   </section> 
   
   <section anchor="ack" title="Acknowledgement">
   <t>
   TBD
   </t>
   </section>
  
  </middle>
  
    <back>
    <references title="Normative References">
     
     &RFC2119;
     
    </references>

    <references title="Informative References">
    
&I-D.ietf-rtgwg-dt-encap;
    
&I-D.ashwood-nvo3-oam-requirements;
    
&I-D.ietf-sfc-oam-framework;
    
&I-D.ietf-bier-oam-requirements;
    
&I-D.ietf-spring-sr-oam-requirement;
    
&I-D.kumarkini-mpls-spring-lsp-ping;
    
    </references>

 </back>
 </rfc>   
    
