Re: [OSPF] Picky nits in draft-ietf-ospf-te-node-addr-04.txt

[Rahul Aggarwal <rahul at juniper.net>]

Hi Acee,

<snipped>

>
> If the draft is enhanced to support prefixes (which would satisfy the
> ASON requirement), then I'd suggest the Node IPv6 Local Address Sub-
> TLV use the OSPFv3 method of packing OSPFv3 prefixes into even
> multiples of 32-bit words.
>

Thanks for the suggestion. I have made the change.

rahul

> A.4.1.  IPv6 Prefix Representation
>
>     IPv6 addresses are bit strings of length 128.  IPv6 routing
>     protocols, and OSPF for IPv6 in particular, advertise IPv6 address
>     prefixes.  IPv6 address prefixes are bit strings whose length ranges
>     between 0 and 128 bits (inclusive).
>
>     Within OSPF, IPv6 address prefixes are always represented by a
>     combination of three fields: PrefixLength, PrefixOptions, and
> Address
>     Prefix.  PrefixLength is the length in bits of the prefix.
>     PrefixOptions is an 8-bit field describing various capabilities
>     associated with the prefix (see Appendix A.4.2).  Address Prefix is
>     an encoding of the prefix itself as an even multiple of 32-bit
> words,
>     padding with zero bits as necessary.  This encoding consumes
>     ((PrefixLength + 31) / 32) 32-bit words.
>
> Thanks,
> Acee
>
>
> >
> > ===
> > Section 4.2
> > s/SHOULD not/SHOULD NOT/
> >
> > Having said "SHOULD NOT" don't you need to say what happens if, or
> > why an implementation MAY vary this?
> >
> > You need to clarify:
> > - What happens if > 1 Node Attribute TLV in an OSPF TE LSA
> > - What happens if a router advertises two OSPF TE LSAs each with a
> > Node Attribute TLV
> > - What happens if > 1 sub-TLV of the same type in a Node Attribute TLV
> >
> > ===
> > Section 5
> >
> > This is a brave section given the current climate :-)
> >
> > Aren't you advertising information that was not previously
> > advertised? Doesn't that increase the risk if the protocol is
> > compromised?
> > ===
> > Section 6
> >
> > Suggest you point the IANA at the registry and subregistry by name,
> > to make sure they understand where to make the assignment.
> >
> > Don't you need IANA to manage a new registry for the sub-TLV type
> > values?
> > ===
> >
> >
> >
> > _______________________________________________
> > OSPF mailing list
> > OSPF at ietf.org
> > https://www1.ietf.org/mailman/listinfo/ospf
>
>

_______________________________________________
OSPF mailing list
OSPF at ietf.org
https://www1.ietf.org/mailman/listinfo/ospf