[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: IPv6

Wojciech Dec (wdec) wrote:
>     Woj> Indeed... What's the IPv6 document being referred to here? If
>     it happens to be draft-lourdelet-radext-ipv6-access, then it does
>     not define any new tagging scheme.

  Uh... have you compared it to RFC 2868?

3.3 IPv6-Prefix

  Defines an IPv6 prefix with a tag.  There are NO existing tagged IPv6
attributes.  RFC 2868 defines tagged integers and strings *only*.  This
data type is new.

3.5 IPv6-Route-Option-Lifetime

  Defines an 8-bit tag, followed by a 32-bit integer.  RFC 2868 defines
a 32-bit integer where the 8-bit tag over-writes the highest 8 bit of
the integer.  This data type is new.

  3.6 and 3.7 have the same issue.

3.8.  Auth-IPv6-Prefix-User-ID

  Defines an 8-bit tag followed by a 64-bit integer.  There are NO
existing attributes that are tagged 64-bit integers.  This data type is new.


  This draft defines a number of new tagged data types which are not
previously used in any RFC, or on any vendor equipment, or in any
specification from another standards body.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>