[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (draft-ishiguro-ospf-ospfv3-traffic) 00 01 02 03 04 05 06 07 08 09 10 11 12 13 RFC 5329

Network Working Group                                        K. Ishiguro
Internet-Draft                                                 T. Takada
Expires: September 2, 2005                              IP Infusion, Inc
                                                                A. Davey
                                                 Data Connection Limited
                                                      A. Lindem (Editor)
                                                      Cisco Systems, Inc
                                                              March 2005


            Traffic Engineering Extensions to OSPF version 3
                 draft-ietf-ospf-ospfv3-traffic-05.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on September 2, 2005.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This document describes extensions to OSPFv3 to support intra-area
   Traffic Engineering (TE).  This document extends OSPFv2 TE to handle
   IPv6 networks.  A new TLV and several new sub-TLVs are defined to
   support IPv6 networks.



Ishiguro, et al.        Expires September 2, 2005               [Page 1]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


Table of Contents

   1.  Requirements notation  . . . . . . . . . . . . . . . . . . . .  3
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Intra-Area-TE-LSA  . . . . . . . . . . . . . . . . . . . . . .  5
   4.  Router IPv6 Address TLV  . . . . . . . . . . . . . . . . . . .  7
   5.  Link TLV . . . . . . . . . . . . . . . . . . . . . . . . . . .  8
     5.1   Link ID Sub-TLV  . . . . . . . . . . . . . . . . . . . . .  8
     5.2   Neighbor ID Sub-TLV  . . . . . . . . . . . . . . . . . . .  8
     5.3   Local Interface IPv6 Address Sub-TLV . . . . . . . . . . .  9
     5.4   Remote Interface IPv6 Address Sub-TLV  . . . . . . . . . . 10
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 13
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
     8.1   Normative References . . . . . . . . . . . . . . . . . . . 14
     8.2   Informative References . . . . . . . . . . . . . . . . . . 14
       Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 14
   A.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 16
       Intellectual Property and Copyright Statements . . . . . . . . 17
































Ishiguro, et al.        Expires September 2, 2005               [Page 2]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


1.  Requirements notation

   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 RFC2119 [RFC2119].














































Ishiguro, et al.        Expires September 2, 2005               [Page 3]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


2.  Introduction

   OSPFv3 has a very flexible mechanism for adding new LS types.
   Unknown LS types are flooded properly based on the flooding scope
   bits in the LS type [OSPFV3].  This document proposes the addition of
   the Intra-Area-TE LSA to OSPFv3.

   For Traffic Engineering, this document uses "Traffic Engineering
   Extensions to OSPF" [TE] as a base for TLV definitions.  New TLVs and
   sub-TLVs are added to [TE] to extend TE capabilities to IPv6
   networks.  Some existing TLVs and sub-TLVs require clarification for
   OSPFv3 applicability.

   GMPLS [GMPLS] and the Diff-Serv MPLS Extensions [TE-DIFF] are based
   on [TE].  These functions can also be extended to OSPFv3 by utilizing
   the TLVs and sub-TLVs described in this document.



































Ishiguro, et al.        Expires September 2, 2005               [Page 4]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


3.  Intra-Area-TE-LSA

   A new LS type is defined for the Intra-Area-TE LSA.  This is
   different from OSPFv2 Traffic Engineering [TE] where opaque LSAs are
   used to advertise TE information [OPAQUE].  The LSA function code is
   10, the U bit is set, and the scope is set to 01 for area-scoping.
   When the U bit is set to 1 an OSPFv3 router must flood the LSA at its
   defined flooding scope even if it does not recognize the LS type
   [OSPFV3].



       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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |            LS age             |0|1|1|          10             |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                   Link State ID                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                    Advertising Router                         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                    LS sequence number                         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |        LS checksum           |             Length             |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |
      +-                            TLV's                            -+
      |                             ...                               |


   The Link State ID of an Intra-Area-TE LSA is an arbitrary value used
   to maintain multiple Traffic Engineering LSAs.  The LSA ID has no
   topological significance.

   The format of the TLV's within the body of a router information LSA
   is the same as the format used by the Traffic Engineering Extensions
   to OSPF [TE].  The LSA payload consists of one or more nested Type/
   Length/Value (TLV) triplets.  The format of each TLV is:


      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            |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                            Value...                           |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+




Ishiguro, et al.        Expires September 2, 2005               [Page 5]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


   The Length field defines the length of the value portion in octets
   (thus a TLV with no value portion would have a length of zero).  The
   TLV is padded to four-octet alignment;  padding is not included in
   the length field (so a three octet value would have a length of
   three, but the total size of the TLV would be eight octets).  Nested
   TLVs are also 32-bit aligned.  For example, a one byte value would
   have the length field set to 1, and three octets of padding would be
   added to the end of the value portion of the TLV.  Unrecognized types
   are ignored.










































Ishiguro, et al.        Expires September 2, 2005               [Page 6]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


4.  Router IPv6 Address TLV

   The Router IPv6 Address TLV advertises a reachable IPv6 address.
   This is a stable IPv6 address that is always reachable if there is
   connectivity to the OSPFv3 router.

   The Router IPv6 Address TLV has type 3, length 16, and a value
   containing a 16 octet local IPv6 address.  It MUST appear in exactly
   one Traffic Engineering LSA originated by an OSPFv3 router supporting
   the TE extensions.  The Router IPv6 Address TLV is a top-level TLV as
   defined in Traffic Engineering Extensions to OSPF [TE] and only one
   top-level TLV may be contained in an LSA.


       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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |              3                |            16                 |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |
      +-+-+-+-                                                 -+-+-+-+
      |                                                               |
      +-+-+-+-             Router IPv6 Address                 -+-+-+-+
      |                                                               |
      +-+-+-+-                                                 -+-+-+-+
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


      Type     A 16 bit field set to 3.
      Length   A 16 bit field that indicates the length of the value
               portion in octets. For this TLV it is always 16.
      Value    A stable and routable IPv6 address.


















Ishiguro, et al.        Expires September 2, 2005               [Page 7]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


5.  Link TLV

   The Link TLV describes a single link and consists of a set of sub-
   TLVs [TE].  All of the sub-TLVs in [TE] other than the Link ID sub-
   TLV are applicable to OSPFv3.  The Link ID sub-TLV can't be used in
   OSPFv3 due to the protocol differences between OSPFv2 and OSPFv3.

   Three new sub-TLVs for the Link TLV are defined:

      17 - Neighbor ID (8 octets)

      18 - Local Interface IPv6 Address (16N octets, where N is the
      number of IPv6 addresses)

      19 - Remote Interface IPv6 Address (16N octets, where N is the
      number of IPv6 addresses)

   The Neighbor ID Sub-TLV is mandatory for OSPF3 Traffic Engineering
   support.  It MUST be appear exactly once in a Link TLV.  All other
   sub-TLVs defined in document MAY occur at most once in a Link TLV.

5.1  Link ID Sub-TLV

   The Link ID sub-TLV is used in OSPFv2 to identify the other end of
   the link.  In OSPFv3, the Neighbor ID sub-TLV MUST be used for link
   identification.  In OSPFv3, The Link ID sub-TLV SHOULD NOT be sent
   and MUST be ignored upon receipt.

5.2  Neighbor ID Sub-TLV

   In OSPFv2, the Link ID is used to identify the other end of a link.
   In OSPFv3, the combination of Neighbor Interface ID and Neighbor
   Router ID are used for neighbor link identification.  Both are
   advertised in the Neighbor ID Sub-TLV.

   Neighbor Interface ID and Neighbor Router ID values are the same as
   described in RFC 2740 [OSPFV3] A.4.3 Router-LSAs.














Ishiguro, et al.        Expires September 2, 2005               [Page 8]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


       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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |              17               |             8                 |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |             Neighbor Interface ID                             |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |             Neighbor Router ID                                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


      Type     A 16 bit field set to 17.
      Length   A 16 bit field that indicates the length of the value
               portion in octets. For this sub-TLV it is always 8.
      Value    The neighbor's interface ID and router ID.



5.3  Local Interface IPv6 Address Sub-TLV

   The Local Interface IPv6 Address sub-TLV specifies the IPv6
   address(es) of the interface corresponding to this link.  If there
   are multiple local addresses assigned to the link then they MAY all
   be listed in this sub-TLV.  Link-local address MUST NOT be included
   in this sub-TLV.


























Ishiguro, et al.        Expires September 2, 2005               [Page 9]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


       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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |              18               |      Length (Multiple of 16)  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |
      +-+-+-+-                                                 -+-+-+-+
      |                                                               |
      +-+-+-+-             Local Interface  IPv6 Address       -+-+-+-+
      |                                                               |
      +-+-+-+-                                                 -+-+-+-+
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                         o                                     |
      |                         o                                     |
      |                         o                                     |
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |
      +-+-+-+-                                                 -+-+-+-+
      |                                                               |
      +-+-+-+-          Local Interface IPv6 Address           -+-+-+-+
      |                                                               |
      +-+-+-+-                                                 -+-+-+-+
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      Type     A 16 bit field set to 18.
      Length   A 16 bit field that indicates the length of the value
               portion in octets. For this sub-TLV, it MUST alway be a
               multiple of 16 octets dependent on the number of IPv6
               addresses advertised.
      Value    A variable length local interface IPv6 address list.



5.4  Remote Interface IPv6 Address Sub-TLV

   The Remote Interface IPv6 Address sub-TLV advertises the IPv6
   address(es) associated with the neighbor's interface.  This Sub-TLV
   and the Local Interface IPv6 address Sub-TLV are used to discern
   amongst parallel links between OSPFv3 routers.  If the Link Type is
   multi-access, the Remote Interface IPv6 Address MAY be set to ::.
   Alternately, an implementation MAY choose not to send this sub-TLV.
   Link-local addresses should not be contained in this sub-TLV.
   Neighbor addresses advertised in Link-LSAs with a prefix length of
   128 and the LA bit set MAY be advertised.




Ishiguro, et al.        Expires September 2, 2005              [Page 10]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


       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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |              19               |      Length (Multiple of 16)  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |
      +-+-+-+-                                                 -+-+-+-+
      |                                                               |
      +-+-+-+-             Remote Interface IPv6 Address       -+-+-+-+
      |                                                               |
      +-+-+-+-                                                 -+-+-+-+
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                         o                                     |
      |                         o                                     |
      |                         o                                     |
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                                                               |
      +-+-+-+-                                                 -+-+-+-+
      |                                                               |
      +-+-+-+-             Remote Interface IPv6 Address       -+-+-+-+
      |                                                               |
      +-+-+-+-                                                 -+-+-+-+
      |                                                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      Type     A 16 bit field set to 19.
      Length   A 16 bit field that indicates the length of the value
               portion in octets. For this sub-TLV, it MUST be a
               multiple of 16 octets dependent on the number of IPv6
               addresses advertised.
      Value    A variable length remote interface IPv6 address list.


















Ishiguro, et al.        Expires September 2, 2005              [Page 11]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


6.  Security Considerations

   The function described in this document does not create any new
   security issues for the OSPFv3 protocol.  Security considerations for
   the base OSPFv3 protocol are covered in [OSPFV3].














































Ishiguro, et al.        Expires September 2, 2005              [Page 12]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


7.  IANA Considerations

   The following IANA assignments are to be made from existing
   registries:

   1.  The OSPFv3 LSA type function code 10 needs to be assigned to the
       OSPFv3 Intra-Area-TE-LSA.

   2.  The Router IPv6 Address TLV type 3 needs to be assigned from the
       existing registry for OSPF TE TLVs.

   3.  The Neighbor ID Sub-TLV (17), Local Interface IPv6 Address Sub-
       TLV (18), and Remote Interface IPv6 Address Sub-TLV (19), need to
       be assigned from the existing registry for OSPF TE Sub-TLVs.





































Ishiguro, et al.        Expires September 2, 2005              [Page 13]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


8.  References

8.1  Normative References

   [OSPF]     Moy, J., "OSPF Version 2", RFC 2328, April 1998.

   [OSPFV3]   Coltun, R., Ferguson, D., and J. Moy, "OSPF for IPv6",
              RFC 2740, April 1998.

   [RFC2119]  Bradner, S., "Key words for use in RFC's to Indicate
              Requirement Levels", RFC 2119, March 1997.

   [TE]       Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering
              Extensions to OSPF", RFC 3630, September 2003.

8.2  Informative References

   [GMPLS]    Kompella, K. and Y. Rekhter, "OSPF Extensions in Support
              of Generalized MPLS",
              draft-ietf-ccamp-ospf-gmpls-extensions-12.txt (work in
              progress).

   [OPAQUE]   Coltun, R., "The OSPF Opaque LSA Option", RFC 2370,
              July 1998.

   [TE-DIFF]  Le Faucheur, F., Wu, L., Davie, B., Davari, S., Vaananen,
              P., Krishnan, R., Cheval, P., and J. Heinanen, "Multi-
              Protocol Label Switching (MPLS) Support of Differentiated
              Services", RFC 3270.


Authors' Addresses

   Kunihiro Ishiguro
   IP Infusion, Inc
   111 W. St. John Street, Suite 910
   San Jose, CA  95113
   USA

   Email: kunihiro@ipinfusion.com











Ishiguro, et al.        Expires September 2, 2005              [Page 14]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


   Toshiaki Takada
   IP Infusion, Inc
   111 W. St. John Street, Suite 910
   San Jose, CA  95113
   USA

   Email: takada@ipinfusion.com


   Alan Davey
   Data Connection Limited
   100 Church Street
   Enfield
   EN2 6BQ
   UK

   Email: Alan.Davey@dataconnection.com


   Acee Lindem
   Cisco Systems, Inc
   7025 Kit Creek Road
   Research Triangle Park, NC  27709
   USA

   Email: acee@cisco.com

























Ishiguro, et al.        Expires September 2, 2005              [Page 15]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


Appendix A.  Acknowledgments

   Thanks to Vishwas Manral, Kireeti Kompella and Alex Zinin for their
   comments.

   The RFC text was produced using Marshall Rose's xml2rfc tool.













































Ishiguro, et al.        Expires September 2, 2005              [Page 16]


Internet-Draft         OSPFv3-Traffic Engineering             March 2005


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Copyright Statement

   Copyright (C) The Internet Society (2005).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Ishiguro, et al.        Expires September 2, 2005              [Page 17]


Html markup produced by rfcmarkup 1.126, available from https://tools.ietf.org/tools/rfcmarkup/