Re: [alto] Francesca Palombini's No Objection on draft-ietf-alto-cost-mode-03: (with COMMENT)

[[e-mail]]

Re-,

Sure. Please use the same diff provided below to track the changes.

Thanks.

Cheers,
Med

De : Francesca Palombini <[e-mail]>
Envoyé : mardi 31 mai 2022 15:24
À : BOUCADAIR Mohamed INNOV/NET <[e-mail]>; The IESG <[e-mail]>
Cc : [e-mail]; [e-mail]; [e-mail]; [e-mail]
Objet : Re: Francesca Palombini's No Objection on draft-ietf-alto-cost-mode-03: (with COMMENT)

Thanks Med! This looks good, I think it still is missing a pointer to the requirements for the Identifier listed in Section 3.2 - I believe you need to include that in some way in the IANA Considerations section, to allow people to find the right restrictions on Identifiers strings when registering values. This can be done really easily:

OLD:
                                  Identifier:  The name of the ALTO cost mode.
NEW:
                                  Identifier:  The name of the ALTO cost mode. See section 3.2 for allowed encoding.

Or something like that.

Francesca

From: [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Date: Tuesday, 31 May 2022 at 15:18
To: Francesca Palombini <[e-mail]<mailto:[e-mail]>>, The IESG <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>, [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>, [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>, [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Subject: RE: Francesca Palombini's No Objection on draft-ietf-alto-cost-mode-03: (with COMMENT)
Hi Francesca,

Thank you for the review.

The names of the fields are self-descriptive, but no problem to add some text as you can see in the proposal at: https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-1d0c46574a7af725&q=1&e=b3db017b-812a-4079-92bf-47431008fe46&u=https%3A%2F%2Ftinyurl.com%2Fcost-mode-latest

Added a note for the "priv" case so that it is easily available from the IANA registry itself.

Cheers,
Med

> -----Message d'origine-----
> De : Francesca Palombini via Datatracker <[e-mail]<mailto:[e-mail]>>
> Envoyé : mardi 31 mai 2022 14:27
> À : The IESG <[e-mail]<mailto:[e-mail]>>
> Cc : [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>;
> [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
> Objet : Francesca Palombini's No Objection on draft-ietf-alto-
> cost-mode-03: (with COMMENT)
>
> Francesca Palombini has entered the following ballot position for
> draft-ietf-alto-cost-mode-03: No Objection
>
> When responding, please keep the subject line intact and reply to
> all email addresses included in the To and CC lines. (Feel free to
> cut this introductory paragraph, however.)
>
>
> Please refer to
> https://www.ietf.org/about/groups/iesg/statements/handling-ballot-
> positions/
> for more information about how to handle DISCUSS and COMMENT
> positions.
>
>
> The document, along with other ballot positions, can be found
> here:
> https://datatracker.ietf.org/doc/draft-ietf-alto-cost-mode/
>
>
>
> ------------------------------------------------------------------
> ----
> COMMENT:
> ------------------------------------------------------------------
> ----
>
> # ART AD Review of draft-ietf-alto-cost-mode-03
>
> cc @fpalombini
>
> Thank you for the work on this document.
>
> Many thanks to Jaime Jimenez for his ART ART review:
> https://mailarchive.ietf.org/arch/msg/art/AdWmf0LOQ2JPGOZRQWVqTczv
> lwA/, and
> thanks to the authors for addressing his comment.
>
> I only have one comment about the IANA section - I do not believe
> it rises as a
> DISCUSS, but I strongly think it should be addressed before
> publication.
>
> Francesca
>
> ## Comments
>
> ### IANA considerations
>
> Section 4:
> >   This document requests IANA to create a new subregistry
> entitled
> >   "ALTO Cost Modes" under the "Application-Layer Traffic
> Optimization
> >   (ALTO) Protocol" registry available at [ALTO].
>
> Please add a paragraph going over the different fields in the
> registry, listing
> them and providing a short description.
>
> In the definition for the "Identifier" field you should either
> repeat or point
> to the constraints defined in Section 3.2, including the fact that
> identifiers
> prefixed with "priv:" are reserved for Private Use (Section 4.1 of
> [RFC8126])
> (which I believe is more precise than just saying "_Cost modes_
> prefixed with
> "priv" are reserved ..." at the end of the section).
>
> ## Notes
>
> This review is in the ["IETF Comments" Markdown format][ICMF], You
> can use the
> [`ietf-comments` tool][ICT] to automatically convert this review
> into
> individual GitHub issues.
>
> [ICMF]: https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-9faa09361356e426&q=1&e=b3db017b-812a-4079-92bf-47431008fe46&u=https%3A%2F%2Fgithub.com%2Fmnot%2Fietf-comments%2Fblob%2Fmain%2Fformat.md
> [ICT]: https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-85de72c60dc0c7a6&q=1&e=b3db017b-812a-4079-92bf-47431008fe46&u=https%3A%2F%2Fgithub.com%2Fmnot%2Fietf-comments
>
>


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.