yes, I believe that is correct.

On Fri, May 13, 2022 at 12:58 PM Amanda Baber via RT <iana-mat...@iana.org>
wrote:

> Hi all,
>
> This question relates to both 6874 and 6876:
>
> Should "priv:" be removed from the ALTO Cost Metrics and ALTO Endpoint
> Property Types registries? See
>
> https://www.iana.org/assignments/alto-protocol
>
> If so, should we add the note "Note: Identifiers prefixed with 'priv:' are
> reserved for Private Use (see RFC 7285, Section 10.8.2)" to the top of each
> registry?
>
> We'll need Martin to sign off on any registry changes.
>
> thanks,
>
> Amanda Baber
> IANA Operations Manager
>
> On Thu May 12 22:09:51 2022, rfc-edi...@rfc-editor.org wrote:
> > The following errata report has been verified for RFC7285,
> >  "Application-Layer Traffic Optimization (ALTO) Protocol".
> >
> > --------------------------------------
> > You may review the report below and at:
> > https://www.rfc-editor.org/errata/eid6876
> >
> > --------------------------------------
> > Status: Verified
> > Type: Technical
> >
> > Reported by: Mohamed BOUCADAIR <mohamed.boucad...@orange.com>
> > Date Reported: 2022-03-09
> > Verified by: Martin Duke (IESG)
> >
> > Section: 14.3
> >
> > Original Text
> > -------------
> > +------------+--------------------+
> > | Identifier | Intended Semantics |
> > +------------+--------------------+
> > | pid        | See Section 7.1.1  |
> > | priv:      | Private use        |
> > +------------+--------------------+
> >
> > Table 4: ALTO Endpoint Property Types
> >
> >
> > Corrected Text
> > --------------
> > +------------+--------------------+
> > | Identifier | Intended Semantics |
> > +------------+--------------------+
> > | pid        | See Section 7.1.1  |
> > +------------+--------------------+
> >
> > Table 4: ALTO Endpoint Property Types
> >
> > Note: Identifiers prefixed with "priv:" are
> > reserved for Private Use (see Section 10.8.2.)
> >
> >
> > Notes
> > -----
> > priv: is not an identifier, but a prefix.
> >
> > --------------------------------------
> > RFC7285 (draft-ietf-alto-protocol-27)
> > --------------------------------------
> > Title               : Application-Layer Traffic Optimization (ALTO)
> > Protocol
> > Publication Date    : September 2014
> > Author(s)           : R. Alimi, Ed., R. Penno, Ed., Y. Yang, Ed., S.
> > Kiesel, S. Previdi, W. Roome, S. Shalunov, R. Woundy
> > Category            : PROPOSED STANDARD
> > Source              : Application-Layer Traffic Optimization
> > Area                : Transport
> > Stream              : IETF
> > Verifying Party     : IESG
>
>
_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

Reply via email to