Re: OSPFv2 Opaque LSAs in OSPFv3

[Kunihiro Ishiguro <[e-mail]>]

>The draft I submitted also uses the OSPFv3 built in flooding.  It is the
>only way to do it.

Exactly.  My point is opaque capability is already provided in OSPFv3.
So there is no benefit to export OSPFv2 opaque capability in OSPFv3.

>Do you plan to have a different Function Code for each OSPFv2 Opaque LSA
>Type?

Yes.  IHMO, it should be.  For example TE case, we can't apply OSPFv2
TE as it is in OSPFv3.  For Local interface IP address and Remote
interface IP address should be treated IPv6 address not IPv4 address.

So I have in my draft (sorry for referring non published draft...):

     3 - Local interface IP address (16N octets)
     4 - Remote interface IP address (16N octets)

You can easily imagine there are some difference between OSPFv2 TE and
OSPFv3 TE.

And if we mask U,S2,S1 bit, LSA Function Code 9 is alredy assingned to
Intra-Area-Prefix-LSA....  This is another concern...

>It seems to me to be much easier to have a single code point for all
>OSPFv2 Opaque LSAs.  This way, all defined OSPFv2 Opaque LSAs get
>automatically defined in v3; moreover, if a new Opaque LSA seems to be
>useful for both v2 and v3, it can be defined as an OSPFv2 Opaque LSA.

I think it is not realistic that applying OSPFv2 Opaque LSA to OSPFv3
verbatim.  We should define each LS type and it's packet format.  When
OSPFv2 Opaque LSA can be introduced to OSPFv3 without any change,
let's just define type code.  It is not a big effort.
--
Kunihiro Ishiguro