<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
    which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
    There has to be one entity for each item to be referenced. 
    An alternate method (rfc include) is described in the references. -->
<!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 RFC3552 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3552.xml">
<!ENTITY I-D.narten-iana-considerations-rfc2434bis SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.narten-iana-considerations-rfc2434bis.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs), 
    please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
    (Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space 
    (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="std" docName="draft-xu-ospf-routable-ip-address-00"
     ipr="trust200902">
  <front>
    <title abbrev="">Carrying Routable IP Addresses in OSPF RI LSA</title>

    <author fullname="Xiaohu Xu" initials="X.X." surname="Xu">
      <organization>Huawei</organization>

      <address>
        <!--
       <postal>
         <street></street>
-->

        <!-- Reorder these if your country does things differently -->

        <!--
         <city>Soham</city>

         <region></region>

         <code></code>

         <country>UK</country>
       </postal>

       <phone>+44 7889 488 335</phone>
-->

        <email>xuxiaohu@huawei.com</email>

        <!-- uri and facsimile elements may also be added -->
      </address>
    </author>

    <author fullname="Uma Chunduri" initials="U.C." surname="Chunduri">
      <organization>Ericsson</organization>

      <address>
        <!--
       <postal>
         <street></street>
-->

        <!-- Reorder these if your country does things differently -->

        <!--
         <city>Soham</city>

         <region></region>

         <code></code>

         <country>UK</country>
       </postal>

       <phone>+44 7889 488 335</phone>
-->

        <email>uma.chunduri@ericsson.com</email>

        <!-- uri and facsimile elements may also be added -->
      </address>
    </author>

    <author fullname="Manav Bhatia" initials="M.B." surname="Bhatia">
      <organization>Alcatel-Lucent</organization>

      <address>
        <!--
       <postal>
         <street></street>
-->

        <!-- Reorder these if your country does things differently -->

        <!--
         <city>Soham</city>

         <region></region>

         <code></code>

         <country>UK</country>
       </postal>

       <phone>+44 7889 488 335</phone>
-->

        <email>manav.bhatia@alcatel-lucent.com</email>

        <!-- uri and facsimile elements may also be added -->
      </address>
    </author>

    <!--

-->

    <date day="4" month="June" year="2014"/>

    <abstract>
      <t>This document proposes two new TLVs within the body of the OSPF
      Router Information (RI) Opaque LSA, called Routable IPv4 Address TLV and
      Routable IPv6 Address TLV. Here the OSPF means boths OSPFv2 and
      OSPFv3.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t>There are several situations where it is required for OSPF routers in
      one area to find correlations between routable IP addresses and
      capabilities of OSPF routers in another area. One example is the Entropy
      Label Capability (ELC) advertisement <xref
      target="I-D.xu-ospf-mpls-elc"/> across the OSPF domain. In this example,
      assume the ELC TLV orginated by a router in one area is propagated to
      another area, those routers in the latter area need to find routable IP
      addresses of the router originating that ELC TLV before inserting the
      Entropy Label (EL) for packets going to the Label Switch Path (LSP)
      tunnel towards one of the above routable IP addresses. Another example
      is the S-BFD discriminator distribution <xref
      target="I-D.bhatia-ospf-sbfd-discriminator"/> across the OSPF domain. In
      this example, assume the S-BFD Discriminator TLV orginated by a router
      in one area is propagated to another area, those routers in the latter
      area need to find routable IP addresses of the router originating that
      S-BFD Discriminator TLV so as to set up S-BDF seesions with that
      originating router.</t>

      <t>However, in the OSPF Router Information (RI) Opaque LSA as defined in
      <xref target="RFC4970"/>, which is used by OSPF routers to announce
      their capabilities, there is no such field for containing routable IP
      addresses of the originating router. Therefore, this document propose
      two new TLVs within the body of OSPF RI LSA, called Routable IPv4
      Address TLV and Routable IPv6 Address TLV, which are used to carry
      routable IPv4 and IPv6 addresses respectively. Here the OSPF means boths
      OSPFv2 and OSPFv3. </t>

      <section 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>
      </section>
    </section>

    <section anchor="Abbreviations_Terminology" title="Terminology">
      <t>This memo makes use of the terms defined in <xref
      target="RFC4970"/>.</t>
    </section>

    <section title="Routable IPv4 Address TLV">
      <t>A new TLV within the body of the OSPFv2 RI Opaque LSA, called
      Routable IPv4 Address TLV is defined to carry one or more routable IPv4
      addresses of the router originating the RI LSA. The Type of this TLV is
      TBD, the Length is variable (multiple of 4), and the Value field
      contains one or more routable IPv4 addresses of the router originating
      the RI LSA. This TLV is only applicable to OSPFv2. The scope of the
      advertisement depends on the application but it is recommended that it
      SHOULD be domain-wide.</t>
    </section>

    <section anchor="ELC_ISIS" title="Routable IPv6 Address TLV">
      <t>A new TLV within the body of the OSPFv3 RI Opaque LSA, called
      Routable IPv6 Address TLV is defined to carry one or more routable IPv6
      global addresses of the router originating the RI LSA. The Type of this
      TLV is TBD, the Length is variable (multiple of 16), and the Value field
      contains one or more routable IPv6 global addresses of the router
      originating the RI LSA. This TLV is only applicable to OSPFv3. The scope
      of the advertisement depends on the application but it is recommended
      that it SHOULD be domain-wide.</t>
    </section>

    <section anchor="Acknowledgements" title="Acknowledgements">
      <t>Thanks Karsten Thomann, Anton Smirnov, Joel Jaeggli, Joel M. Halpern,
      Wes George, Les Ginsberg and Acee Lindem for their valuable comments on
      the initial idea of this draft.</t>

      <!---->
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>This document includes a request to IANA to allocate two TLV type
      codes for the new RI LSA TLVs proposed in this document
      respectively.</t>

      <!---->
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>This document does not introduce any new security risk.</t>

      <!---->
    </section>
  </middle>

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

      <?rfc include="reference.RFC.4970"?>

      <!---->
    </references>

    <references title="Informative References">
      <?rfc include="reference.I-D.xu-ospf-mpls-elc"?>

      <?rfc include="reference.I-D.bhatia-ospf-sbfd-discriminator"?>

      <!---->
    </references>
  </back>
</rfc>
