>If you're doing this, I have two requests:
>a) Please avoid redefining sub-TLVs 1-16 of the Link TLV;

OK. I've used 9,10,11 in OSPFv3 TE draft. I'll change it.

>b) Make the new sub-TLVs applicable to both OSPFv2 and v3.
>
>BTW, diffserv TE and GMPLS are just subcases of TE. I'd suggest that
> draft-katz-yeung-ospf-traffic-08.txt,
> draft-ietf-tewg-diff-te-proto-01.txt and
> draft-ietf-ccamp-ospf-gmpls-extensions-08.txt
>be cited normatively in your draft.

So far I have below point to make it applicable OSPFv2 extensions to
OSPFv3.

1. IPv4 address

Whe the draft refer IPv4 address, IPv6 address support should be
there.

2. IPv6 address

When draft flood IP address to no local flooding scope, link-local
address should not be flooded. It is not valid address outside link
local.

3. Router Address TLV for Router ID

When draft use Router Address TLV for referring Router ID. That is
realy Router ID in OSPFv3 and the address may not be reachable.

4. Identification key for Network-LSA

Identification key for Network-LSA (there is a case we have to map LSA
to Network-LSA) is not same as in OSPFv2. In OSPFv3 Neighbor
Interface ID and Neighbor Router ID is needed.

--
Kunihiro Ishiguro

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