Re: OSPFv2 Opaque LSAs in OSPFv3

[Kunihiro Ishiguro <[e-mail]>]

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

I'm resending thie mail...I send from wrong from address....so you may
receive two mail.

BTW I haven't submitted the draft but I prepared TE extensions to
OSPFv3.  I just define a new LS type for TE then use OSPFv3 built in
flooding mechanism.  I believe this is straight forward way to do it.
--
Kunihiro Ishiguro


Network Working Group                                       K. Ishiguro
Internet Draft                                         IP Infusion Inc.
Expiration Date: May 2003                                     T. Takada
                                                       IP Infusion Inc.
                                                           October 2002


            Traffic Engineering Extensions to OSPF version 3

               draft-ishiguro-ospf-ospfv3-traffic-00.txt

<SNIP>...

2. Applicability

   OSPFv3 has a very flexible mechanism for adding new LS type.  Even
   the implementation does not know the LS types, the LSA is properly
   flooded by LS type field.  This document add a new LSA type Traffic
   Engineering LSA to OSPFv3.


3. Traffic-Engineering-LSA

   New LSA Traffic-Engineering-LSA is introduced.

3.1 LS Type

   Traffic-Engineering-LSA is defined as Area scope LSA.

   LSA function code  LS Type  Description
   --------------------------------------------------------------------
   10                 0x2000a  Traffic-Engineering-LSA

3.2 LSA Format Overview

   This is LSA header format.


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


3.3 TLV Header

   The LSA payload consists of one or more nested Type/Length/Value

<SNIP>....