[radext] [IANA #1240729] Errate for RADIUS types

[Amanda Baber via RT <[e-mail]>]

Alan/Rob,

Does this mean that RFC 8044 should be listed as an additional reference for 144? I see that the IANA Considerations section for RFC 6519 didn't specify any entry for the Data Type field, so it's not clear that an additional reference would be needed.

(If Alan's answer is yes, Rob, we would need you to sign off again.)

thanks,
Amanda

On Wed Oct 05 15:00:03 2022, [e-mail] wrote:
> FYI:  RFC 8044 defines "text" as "UTF-8 data", and "string" as "opaque
> data"
> 
> https://www.rfc-editor.org/rfc/rfc8044#section-3.4
> 
> https://www.rfc-editor.org/rfc/rfc8044#section-3.5
> 
> This errata corrects what appears to be an error when RFC 8044 was
> published.  That document contained updates for the full IANA registry
> in the I-D, which was removed before the RFC was published:
> 
> https://datatracker.ietf.org/doc/html/draft-ietf-radext-datatypes-08
> 
> Look for "DS-Lite" and see it's "text".
> 
> > On Oct 5, 2022, at 10:52 AM, Amanda Baber via RT <iana-
> > [e-mail]> wrote:
> >
> > Warren and Rob,
> >
> > Can one of you sign off on this registry fix submitted by Alan DeKok?
> > See below.
> >
> > thanks,
> >
> > Amanda Baber
> > IANA Operations Manager
> >
> > On Wed Oct 05 14:12:10 2022, [e-mail] wrote:
> >> https://www.iana.org/assignments/radius-types/radius-types.xhtml
> >>
> >> Contains the following entry:
> >>
> >> 144     DS-Lite-Tunnel-Name     text    [RFC6519]
> >>
> >> However RFC 6519 says:
> >>
> >> The data type of the DS-Lite-Tunnel-Name RADIUS attribute is a
> >> string
> >> with opaque encapsulation, according to Section 5 of [RFC2865].
> >>
> >> As such, the "Data Type" field for "DS-Lite-Tunnel-Name" should be
> >> changed to "string".
> >>
> >> Alan DeKok.
> >