Hi,

Does the erratum ask that we remove priv: from the IANA registry as well?

https://www.iana.org/assignments/alto-protocol/alto-protocol.xhtml#cost-metrics
https://www.iana.org/assignments/alto-protocol/alto-protocol.xhtml#endpoint-property-types

I think that would be unfortunate. Perhaps some text in the Intended
Semantics can be added to say it is a prefix!

Thanks!
Dhruv

On Wed, Mar 9, 2022 at 12:20 PM RFC Errata System <[email protected]>
wrote:

> The following errata report has been submitted for RFC7285,
> "Application-Layer Traffic Optimization (ALTO) Protocol".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6876
>
> --------------------------------------
> Type: Editorial
> Reported by: Mohamed BOUCADAIR <[email protected]>
>
> 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
>
>
> Notes
> -----
> priv: is not an identifier, but a prefix.
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> 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
> [email protected]
> https://www.ietf.org/mailman/listinfo/alto
>
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto

Reply via email to