Hi Alex,

> Hard to talk without seeing the draft, but what problem
> is it trying to address? I mean, we already have a more
> generic "opaque"-like mechanism in OSPFv3, why is it not
> enough?

True, we have a generic opaque mechanism in OSPF v3. However,
if I want to do TE in OSPF v3, what do I put in the packet to let
you know that this is a TE LSA? In particular, what function code
do I put in the LSA? Should there be a new function code for each
'legacy' Opaque LSA? Etc.

The draft (see below, sorry all for the spam) just grabs a single
LSA function code for 'OSPF v2 Opaque LSAs', but otherwise keeps
everything mostly the same.

Take a look -- fortunately, it shouldn't take more than a couple
of minutes :-)

Kireeti.
-------

Network Working Group K. Kompella
Internet Draft Juniper Networks
Updates: 2740 October 2002
Category: Standards Track
Expires: April 2003

                      OSPFv2 Opaque LSAs in OSPFv3
                  draft-kompella-ospf-opaquev2-00.txt

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.

   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.

Copyright Notice

   Copyright (C) The Internet Society (2002). All Rights Reserved.

Abstract

   This memo specifies how OSPF version 2 Opaque Link State
   Advertisements can be carried in OSPF version 3.

Kompella Standards Track [Page 1]

Internet Draft OSPFv2 Opaque LSAs in OSPFv3 October 2002

1. Introduction

   RFC 2370 [OPAQUE] describes the notion of an "opaque" Link State
   Advertisement (LSA) -- as the RFC says, an LSA that provides "a
   generalized mechanism to allow for the future extensibility of OSPF".
   This has certainly proved useful, for example in defining Grace LSAs
   [HITLESS] and OSPF v2 Traffic Engineering LSAs [OSPF-TE]. RFC 2370
   also defines the format that opaque LSAs take in OSPF version 2
   [OSPFv2], and defines three flooding scopes for such LSAs:
   link-local, area-local and Autonomous System (AS)-wide.

   OSPF version 3 [OSPFv3] inherently supports the notion of opaque LSAs
   in that the flooding scope of an LSA is explicitly stated in the LSA
   header. OSPF v3 also specifies how LSAs with unrecognized function
   codes are to be handled.

   This memo specifies how OSPF version 2 opaque LSAs can be carried in
   OSPF version 3. This allows the reuse of the specifications of OSPF
   v2 Opaque LSAs, as well as the code to support them, in OSPF v3. In
   a nutshell, an OSPF v3 LS Function Code is defined to indicate that
   the LSA is of type OSPF v2 Opaque LSAs; the OSPF v3 Link State ID is
   formatted the same as in the OSPF v2 Opaque LSA; and the body of the
   OSPF v3 LSA is identical to the body of the OSPF v2 Opaque LSA.

2. Opaque LSAs

   An Opaque LSA in OSPF v2 is formatted as follows [OPAQUE, A.2]:

     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 | Options | LS Type |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | Opaque Type | Opaque ID |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | Advertising Router |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | LS Sequence Number |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | LS checksum | Length |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | |
    + +
    | Opaque Information |
    + +
    | ... |

Kompella Standards Track [Page 2]

Internet Draft OSPFv2 Opaque LSAs in OSPFv3 October 2002

   The LS Type is 9, 10, or 11 depending on whether the Opaque LSA's
   flooding scope is link-local, area-local or AS-wide (respectively).

   The above OSPF v2 Opaque LSA is formatted as follows as an OSPF v3
   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
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | LS age |1|X|Y| OSPFv2 Opaque LSA |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | Link State ID |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | Advertising Router |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | LS Sequence Number |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | LS checksum | Length |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    | |
    + +
    | Opaque Information |
    + +
    | ... |

   The U bit in the LS Type is set to 1. The LS Function Code is set to
   10 [to be ratified by the OSPF WG], indicating that the LSA type is
   'OSPF v2 Opaque LSA'. The XY bits are set to reflect the flooding
   scope:

       OSPFv2 Opaque
      LSA of LS Type X Y
      -------------- ---
                   9 0 0
                  10 0 1
                  11 1 0

   The OSPF v3 LSA's Link State ID is formatted as one octet of Opaque
   Type, and 3 octets of Opaque ID (i.e., exactly as the Link State ID
   of the OSPF v2 Opaque LSA).

   The body of the OSPF v3 LSA is octet-for-octet identical to the OSPF
   v2 Opaque Information.

Kompella Standards Track [Page 3]

Internet Draft OSPFv2 Opaque LSAs in OSPFv3 October 2002

2.1. Processing OSPF v2 Opaque LSAs

   An OSPF v3 implementation encountering an LSA of type 'OSPF v2 Opaque
   LSA' MUST follow the rules regarding handling and flooding as defined
   by the U and XY bits, as defined in [OSPFv3].

   In addition, an OSPF v3 implementation MAY further process an OSPF v2
   Opaque LSA as an OSPF v2 implementation would, e.g., it might use a
   Grace-LSA to accomplish (or assist in) hitless restart of OSPF v3; or
   it might build a Traffic Engineering database using the opaque TE
   LSAs. It is the intent of this memo to maximize code (and
   specification) reuse between OSPF v2 and OSPF v3 in this regard.

Normative References

   [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate
       Requirement Levels", BCP 14, RFC 2119, March 1997

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

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

   [OSPFv3] Coltun, R., D. Ferguson, and J. Moy, "OSPF for IPv6", RFC
       2740, December 1999

Informative References

   [HITLESS] Moy, J., "Hitless OSPF Restart", work in progress

   [OSPF-TE] Katz, D., D. Yeung, and K. Kompella, "Traffic Engineering
       Extensions to OSPF Version 2", work in progress

Security Considerations

   The flooding and handling of LSAs has already been specified in the
   [OSPFv3]; this memo only defines a new LS Function Code, and the
   format of the LS body. The OSPF v3 security mechanisms to prevent
   tampering and spoofing of LSAs suffice.

Kompella Standards Track [Page 4]

Internet Draft OSPFv2 Opaque LSAs in OSPFv3 October 2002

Acknowledgments

   Many thanks to Quaizar Vohra, with whom much of this was discussed.

Authors' Addresses

   Kireeti Kompella
   Juniper Networks, Inc.
   1194 N. Mathilda Ave
   Sunnyvale, CA 94089
   Email: kireetijuniper.net

IPR Notice

   The IETF takes no position regarding the validity or scope of any
   intellectual property 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; neither does it represent that it
   has made any effort to identify any such rights. Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11. Copies of
   claims of rights made available for publication 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 implementors or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard. Please address the information to the IETF Executive
   Director.

Kompella Standards Track [Page 5]

Internet Draft OSPFv2 Opaque LSAs in OSPFv3 October 2002

Full Copyright Notice

   Copyright (C) The Internet Society (2002). All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works. However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS 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."

Acknowledgement

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

Kompella Standards Track [Page 6]

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]