One document matched: draft-psarkar-isis-node-admin-tag-00.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?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="std" docName="draft-psarkar-isis-node-admin-tag-00" ipr="trust200902">

  <!-- ***** FRONT MATTER ***** -->

  <front>
     <title>Advertising Per-node Admin Tags in IS-IS</title>


    <author initials="P." surname="Sarkar" fullname="Pushpasis Sarkar" role="editor">
      <organization>Juniper Networks, Inc.</organization>
      <address>
      <postal>
      <street>Electra, Exora Business Park</street>
      <city>Bangalore</city>
      <region>KA</region>
      <code>560103</code>
      <country>India</country>
      </postal>
      <email>psarkar@juniper.net</email>
      </address>
    </author>

    <author fullname="Hannes Gredler" initials="H." surname="Gredler">
      <organization>Juniper Networks, Inc.</organization>
      <address>
      <postal>
      <street>1194 N. Mathilda Ave.</street>
      <city>Sunnyvale</city>
      <region>CA</region>
      <code>94089</code>
      <country>US</country>
      </postal>
      <email>hannes@juniper.net</email>
      </address>
    </author>

    <author initials="S." surname="Hegde" fullname="Shraddha Hegde">
      <organization>Juniper Networks, Inc.</organization>
      <address>
      <postal>
      <street>Electra, Exora Business Park</street>
      <city>Bangalore</city>
      <region>KA</region>
      <code>560103</code>
      <country>India</country>
      </postal>
      <email>shraddha@juniper.net</email>
      </address>
    </author>

    <author initials="H." surname="Raghuveer" fullname="Harish Raghuveer">
      <organization>Juniper Networks, Inc.</organization>
      <address>
      <postal>
      <street>Electra, Exora Business Park</street>
      <city>Bangalore</city>
      <region>KA</region>
      <code>560103</code>
      <country>India</country>
      </postal>
      <email>hraghuveer@juniper.net</email>
      </address>
    </author>

    <author fullname="Stephane Litkowski" initials="S" surname="Litkowski">
      <organization>Orange</organization>
      <address>
        <!-- postal><street/><city/><region/><code/><country/></postal -->
        <!-- <phone/> -->
        <!-- <facsimile/> -->
        <email>stephane.litkowski@orange.com</email>
        <!-- <uri/> -->
      </address>
    </author>

    <author fullname="Bruno Decraene" initials="B" surname="Decraene">
      <organization>Orange</organization>
      <address>
        <!-- postal><street/><city/><region/><code/><country/></postal -->
        <!-- <phone/> -->
        <!-- <facsimile/> -->
        <email>bruno.decraene@orange.com</email>
        <!-- <uri/> -->
      </address>
    </author>

    <date day="21" month="October" year="2013" />

    <area>Routing</area>
    <workgroup>IS-IS for IP Internets</workgroup>

    <keyword>IGP</keyword>
    <keyword>IS-IS</keyword>
    <keyword>Admin-Tag</keyword>
    <keyword>Traffic Engineering</keyword>

    <abstract>
      <t> This document describes an extension to IS-IS protocol <xref target="ISO10589"/>,  
      <xref target="RFC1195"/> to add an optional operational capability, that allows 
      tagging and grouping ofthe nodes in an IS-IS domain. This allows simple management 
      and easy control over route and path selection, based on local configured policies. 
      </t>

      <t>This document describes the protocol extensions to disseminate
      per-node admin-tags in IS-IS protocols.</t>
    </abstract>

    <note title="Requirements Language">
      <t>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 <xref
      target="RFC2119">RFC 2119</xref>.</t>
    </note>
</front>

<middle>

<section title="Introduction" anchor='intro'>
    <t> This document provides mechanisms to advertise per-node administrative tags 
    in the IS-IS Link State PDU <xref target="RFC1195"/>. In certain path-selection 
    applications like for example in traffic-engineering or LFA <xref target="RFC5286"/> 
    selection there is a need to tag the nodes based on their roles in the  network 
    and have policies to prefer or prune a certain group of nodes.
    </t>
</section>

<section title='Administrative Tag TLV'>
    <t> For the purpose of advertising per-node administrative tags within IS-IS, 
    a new TLV is proposed. Because path selection is a functional set which  
    applies both to TE and non-TE applications the same has not added as a new  
    sub-TLV in the Traffic Engingineering TLVs <xref target="RFC5305"/>.
    </t>

    <t> An administrative Tag is a 32-bit integer value that can be used to identify 
    a group of nodes in the IS-IS domain. The new TLV specifies one or more administrative 
    tag values. An IS-IS node advertises the set of groups it is part of in the specific 
    IS-IS level. As an example, all PE-nodes may be configured with certain tag value, 
    whereas all P-nodes are configured with a different tag value in.
    </t>

    <t> The new TLV defined will be carried as a new TLV in the Link State PDUs originated 
    by the router. Link State PDUs <xref target="ISO10589"/> has level-wise (i.e. L1 or L2)
    flooding scope. Choosing the flooding scope to flood the group tags are defined by the 
    policies and is a local matter. Once a group tag is decided in a specific level the 
    same will be inserted in the administrative tag TLV in the Link State PDU for the 
    same level. Implementations should allow configuring both a 'global' and 'per-level' 
    admin tag. In the absence of a specific admin tag configuration for a specific level 
    the global admin tag should be copied in to the LSP PDU for the same level.
    </t>

</section>

<section title='TLV format'>
  <section title='Per-node Admin Tag TLV'>
    <t>The new Administrative Tag TLV, like other ISIS TLVs, is formatted as Type/Length/Value 
    (TLV)triplets. <xref target="isisadmintagtlv"/> below shows the format of the new TLV.
    </t>

    <figure anchor="isisadmintagtlv" title="IS-IS per-node Administrative Tag TLV">
      <artwork>
  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      |    Length     |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                   Administrative Tag #1                       |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                   Administrative Tag #2                       |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 //                                                             //
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                   Administrative Tag #N                       |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

 Type :  TBA

 Length: A 8-bit field that indicates the length of the value
         portion in octets and will be a multiple of 4 octets
         dependent on the number of tags advertised.

 Value:  A sequence of multiple 4 octets defining the
         administrative tags.

      </artwork>
    </figure>
    <t>
      The 'Per-node Admin Tag' TLV may be generated more than once by an originating
      router. This MAY happen if a node carries more than 63 per-node admin groups
      and a single TLV does not provide sufficient space. As such occurence of the 
      'Per-node Admin Tag' TLV does not cancel previous TLV announcements, but rather 
      is cumulative.
    </t>
</section>

<section title='Ordering of tags'>
    <t> The semantics of the tag order are implementation-dependent. There is no implied 
    meaning to the ordering of the tags that indicates a certain operation or set of 
    operations that need to be performed based on the ordering.
   </t>

   <t> Each tag SHOULD be treated as an independent identifier that MAY be used in policy 
   to perform a policy action. Whether or not tag A precedes or succeeds tag B SHOULD not 
   change the meaning of the tag set.
   </t>
</section>
</section>

<section title='Applications'>
    <t> Increased deployment of Loop Free Alternates (LFA) <xref target="RFC5286"/> has 
    exposed some limitations. A recent draft on Operation management of Loop Free Alternates 
    <xref target="I-D.ietf-rtgwg-lfa-manageability"/> proposes refinements to address 
    those limitations. One of the proposed refinements is to be able to group the nodes in 
    IGP domain with administrative tags and engineer the alternate paths based on configured 
    policies.
    </t>

    <t> The proposal in this document helps provide the capability to advertise group tags 
    within IS-IS protocol and perform policy based LFA selection. The policies configured on 
    each node can then make use of these tags to prefer or prune LFAs via certain group 
    of nodes.
    </t>
</section>

<!-- HG: FIXME: add traffic-engineering reference -->

<section title='Security Considerations' anchor='sec-con'>

    <t>
    This document does not introduce any further security issues other than those discussed 
    in <xref target="ISO10589"/> and <xref target="RFC1195"/>.
    </t>

</section>

<section anchor="IANA" title="IANA Considerations">

    <t>IANA maintains the registry for the TLVs. IS-IS Administrative Tags
    will require one new type code for the TLV defined in this document.
    </t>

</section>

<section title='Acknowledgments'>
    
</section>

</middle>

<back>
  <references title='Normative References'>
    <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?>

    <reference anchor="ISO10589">
        <front>
          <title>Intermediate system to Intermediate system intra-domain
          routeing information exchange protocol for use in conjunction with
          the protocol for providing the connectionless-mode Network Service
          (ISO 8473), ISO/IEC 10589:2002, Second Edition.</title>
          <author fullname="ISO "International Organization for Standardization""/>
          <date month="Nov" year="2002"/>
        </front>
    </reference>  
  </references>

<references title='Informative References'>
   <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.1195.xml"?>
   <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.5286.xml"?>
   <?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.5305.xml"?>
   <?rfc include="http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-rtgwg-lfa-manageability-00.xml"?>
</references>
</back>
</rfc>