Greetings,

We are unable to verify this erratum that the submitter marked as editorial.  
Please note that we have changed the “Type” of the following errata 
report to “Technical”.  As Stream Approver, please review and set the 
Status and Type accordingly (see the definitions at 
https://www.rfc-editor.org/errata-definitions/).

You may review the report at: 
https://www.rfc-editor.org/errata/eid6874

Please see https://www.rfc-editor.org/how-to-verify/ for further 
information on how to verify errata reports.

Further information on errata can be found at: 
https://www.rfc-editor.org/errata.php.

Thank you.

RFC Editor/cs


> On Mar 8, 2022, at 12:50 AM, RFC Errata System <rfc-edi...@rfc-editor.org> 
> 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/eid6874
> 
> --------------------------------------
> Type: Editorial
> Reported by: Mohamed BOUCADAIR <mohamed.boucad...@orange.com>
> 
> Section: 14.2
> 
> Original Text
> -------------
> 
>                   +-------------+---------------------+
>                   | Identifier  | Intended Semantics  |
>                   +-------------+---------------------+
>                   | routingcost | See Section 6.1.1.1 |
>                   | priv:       | Private use         |
>                   +-------------+---------------------+
> 
>                        Table 3: ALTO Cost Metrics
> 
> Corrected Text
> --------------
> 
>                   +-------------+---------------------+
>                   | Identifier  | Intended Semantics  |
>                   +-------------+---------------------+
>                   | routingcost | See Section 6.1.1.1 |
>                   +-------------+---------------------+
> 
>                        Table 3: ALTO Cost Metrics
> 
> Notes
> -----
> priv: is not a cost metric 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
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

Reply via email to