<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC1195 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1195.xml">
<!ENTITY RFC3277 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3277.xml">
<!ENTITY RFC5029 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5029.xml">
<!ENTITY RFC3784 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3784.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="std" docName="draft-hegde-isis-link-overload-00" ipr="trust200902">
<front>
<title abbrev="ISIS link overload"> ISIS Link Overload</title>
<author initials="S." surname="Hegde" fullname="Shraddha Hegde">
<organization>Juniper Networks, Inc.</organization>
<address>
<postal>
<street>Embassy Business Park</street>
<city>Bangalore</city>
<region>KA</region>
<code>560093</code>
<country>India</country>
</postal>
<email>shraddha@juniper.net</email>
</address>
</author>
<author initials="P." surname="Sarkar" fullname="Pushpasis Sarkar">
<organization>Juniper Networks, Inc.</organization>
<address>
<postal>
<street>Embassy Business Park</street>
<city>Bangalore</city>
<region>KA</region>
<code>560093</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>
<date day="9" month="March" year="2015"/>
<area>Routing</area>
<workgroup>IS-IS IGP</workgroup>
<keyword>MPLS</keyword>
<keyword>IGP</keyword>
<keyword>ISIS</keyword>
<abstract>
<t>  Many ISIS deployments run on overlay networks provisioned by means of pseudo-wires or L2-circuits.
when the devices in the underlying    network go for maintenance, it is useful to divert the traffic away
   from the specific node(s), to some alternate paths, before the maintenance is actually scheduled.  Since
   the nodes in the underlying network are not visible to ISIS, existing
   Avoidance of traffic blackhole mechanism described in <xref target="RFC3277"/> cannot be used.
It is useful for routers in IS-IS routing domain to be able to
advertise a  link being in overload state to indicate impending maintenance activity in the underlying network devices.
 </t>
<t>This document describes the protocol extensions to disseminate
link overload information in IS-IS protocol.</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> It is useful for routers in IS-IS routing domain to be able to advertise a  link being in overload 
state to indicate impending maintenance activity on the link. This document provides mechanisms to 
advertise link overload state in the Link attributes TLV as defined in <xref target="RFC5029" />
 </t>
</section>



<section title='ISIS Link overload bit'>
<t> The link-attribute sub-TLV is carried within the TLV 22 and has a
   format identical to the sub-TLV format used by the Traffic
   Engineering Extensions for IS-IS (<xref target="RFC3784" />): 1 octet of sub-type, 1
   octet of length of the value field of the sub-TLV followed by the
   value field -- in this case, a 16 bit flags field.</t>

   <t>The following bit represents the Link in overload.</t>
   
   <t>Link Overload:  0x04     When set, this indicates that the
   link is overloaded.</t>



</section>

<section title='Elements of procedure'>
<t>The Link attributes sub TLV with link-overload bit set indicates that the Link which carries the
 sub TLV is overloaded. The node that has the link going  for maintenance, sets metric of the link to MAX-METRIC and re-originates the 
LSP. The metric in the reverse direction also need to change to divert the traffic from reverse direction.
The node SHOULD originate Link attributes sub TLV and set the overload bit and originate the LSP and flood it
in the respective IS-IS level.
 </t>
 <t>When the originator of the Link attributes sub TLV, purges the LSP or
   re-originates it without the Link Overload bit set, the metric on the
   remote node SHOULD be changed back to the original value.</t>
<t>Based on the link type of the overloaded link, actions listed below MAY be
   taken by the receiver.</t>

<section title='Point-to-point links'>

<t>When a link attributes sub TLV with link overload bit set is received for a point-to-point link the receiver SHOULD identify the local link which corresponds to the
overloaded link and set the metric to MAX-METRIC. Receiver node MUST re-originate  the LSP with the changed metric and flood 
into the ISIS level.</t>
</section>

<section title='Broadcast links'>
<t>Broadcast networks in ISIS are represented by a star topology where the Designated Intermediate System (DIS) is the central point to
which all other routers on the broadcast network connect.  As a result, routers on the broadcast  network advertise only 
their adjacency to the pseudo-node.As a result, routers on
   the broadcast network advertise only their adjacency to the pseudo-

   node.  Routers that do not act as DIS do not advertise
   adjacencies with each other.  DIS originates pseudo-node which
   contains adjacenices with all the neighbors.  For the Broadcast
   links, the MAX-METRIC on the outgoing link cannot be changed since
   all the adjacencies are on same link.  Setting the link cost to MAX-
   METRIC would impact paths going via all neighbors. 
<t>When a link-attributes sub TLV with link-overload bit set is received by the remote end for a broadcast link. </t></t>
<vspace blankLines="1" />
<t>-	If it’s non DIS for that link, SHOULD not take any action.</t>
<t>-	If receiving node is DIS for the link, it  MUST set the metric from the pseudo-node to the originator of the link overload bit to MAX-METRIC and
    MUST re-originate the pseudo-node  LSP and flood into the ISIS	Level.</t>
	
<vspace blankLines="1" />
</section>

		
</section>


<section title='Backward compatibility'>
   <t>The mechanism described in the document is fully backward compatible.It is required that the originator and receiver of 
   link-overload bit understand the extensions defined in this document and in case of  broadcast links the originator 
   and the DR need to understand the extensions. Other nodes in the network compute based on increased metric and hence the feature is
   backward compatible.</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>
This specification updates one ISIS registry:
ISIS Link attributes Sub TLV
<vspace blankLines="1"/>
   i) 0x04 - Link overload bit

</t>
</section>
<section title='Acknowledgements'>
</section>


</middle>
<back>
<references title='Normative References'>
<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 &quot;International Organization for Standardization&quot;"/>
          <date month="Nov" year="2002"/>
        </front>
    </reference>  
&RFC1195;
&RFC3277;
&RFC5029;
&RFC2119;
&RFC3784;
</references>
<references title='Informative References'>

</references>
</back>
</rfc>