Re: [alto] WGLC for draft-ietf-alto-cost-mode-00

Hi Med and all,

Sounds good to me. In that case, I think we can end the WGLC for draft-ietf-alto-cost-mode-00.

Three individual reviews were posted to the mailing list by Peng [1], Jordi [2] and Qiao [3]. No objections have been raised and I believe a new version has already been submitted to address the comments. It seems to me that the document can proceed now.

Best,

Kai

[1] https://mailarchive.ietf.org/arch/msg/alto/O0svuhpDJbgzyMcCvsYAlVhUeGc/

[2] https://mailarchive.ietf.org/arch/msg/alto/hPsJw_Jwm9yA24ed-YO8kEVNOOk/

[3] https://mailarchive.ietf.org/arch/msg/alto/Ej1QKC0_Uuq76qCgXEn2_h9I6n8/

-----Original Messages-----
From:mohamed.boucadair@orange.com
Sent Time:2022-04-11 15:23:48 (Monday)
To: "kaigao@scu.edu.cn" <kaigao@scu.edu.cn>, "bill.wu=40huawei.com@dmarc.ietf.org" <bill.wu=40huawei.com@dmarc.ietf.org>
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WGLC for draft-ietf-alto-cost-mode-00

Hi Kai, all,

These RFCs are referring to Unicode in general, where several hyphens are supported.

RFC7285 points explicitly to US-ASCII alphanumeric characters, where U+002D is the only hyphen:

* There is no ambiguity about the intended behavior given that U+002D is provided

* Even if we reason about labels, there is also not ambiguity which hyphen is about

I don’t think there is an issue with RFC7285, but I would not object to an ** editorial ** errata.

That’s said, I’m for consistent use of labels and can fix this for the cost-mode I-D: https://github.com/boucadair/alto-cost-mode/blob/main/draft-ietf-alto-cost-mode.txt

Cheers,

Med

De : alto <alto-bounces@ietf.org> De la part de kaigao@scu.edu.cn
Envoyé : lundi 11 avril 2022 02:19
À : bill.wu=40huawei.com@dmarc.ietf.org
Cc : alto@ietf.org
Objet : Re: [alto] WGLC for draft-ietf-alto-cost-mode-00

Hi Qin, Qiao and all,

I searched for a few documents and it seems that many documents are referring to U+002D as hyphen-minus. It seems to me that we should use hyphen-minus.

https://datatracker.ietf.org/doc/html/rfc3490

https://datatracker.ietf.org/doc/html/rfc5890

https://datatracker.ietf.org/doc/html/rfc8551

https://datatracker.ietf.org/doc/html/rfc8771

Best,

Kai

-----Original Messages-----
From:"Qin Wu" <bill.wu=40huawei.com@dmarc.ietf.org>
Sent Time:2022-04-10 19:21:05 (Sunday)
To: "kaigao@scu.edu.cn" <kaigao@scu.edu.cn>, "Qiao Xiang" <xiangq27@gmail.com>
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WGLC for draft-ietf-alto-cost-mode-00

Hi, Kai and Qiao:

Is there any other RFCs which describe “hyphen” usages besides RFC7285?

Since this work is targeted to update RFC7285, there is a time window to improve RFC7285,

If “hyphen-minus” described in https://www.unicode.org/charts/PDF/U0000.pdf, is current best practice, I have no better reason to reject this request,:-)

The price is we should also update other sections related to cost metric and global endpoint properties with “hyphen” usage.

-Qin

发件人: alto [mailto:alto-bounces@ietf.org] 代表 kaigao@scu.edu.cn
发送时间: 2022年4月10日 15:57
收件人: Qiao Xiang <xiangq27@gmail.com>
抄送:alto@ietf.org
主题: Re: [alto] WGLC for draft-ietf-alto-cost-mode-00

Hi Qiao and all,

Thanks for reviewing the document.

In RFC 7285, "hyphen" is used when defining PID, cost metric, etc. One option is to use the term consistently with existing RFCs.

Best,

Kai

-----Original Messages-----
From:"Qiao Xiang" <xiangq27@gmail.com>
Sent Time:2022-04-09 18:04:36 (Saturday)
To:kaigao@scu.edu.cn
Cc:
Subject: Re: [alto] WGLC for draft-ietf-alto-cost-mode-00

Hi Kai and all,

I have read the document and support the proceeding of its publication with one tiny suggested edit:

Section 3.2: the hyphen ('-', U+002D) -> the hyphen-minus ('-', U+002D)

This is to be consistent with the official name of this character in https://www.unicode.org/charts/PDF/U0000.pdf.

Best

Qiao

On Sat, Apr 9, 2022 at 9:53 AM <kaigao@scu.edu.cn> wrote:

Hi Jordi,

Thanks for reviewing the document!

Best,

Kai

-----Original Messages-----
From:"Jordi Ros Giralt" <jros@qti.qualcomm.com>
Sent Time:2022-04-08 13:03:03 (Friday)
To: "kaigao@scu.edu.cn" <kaigao@scu.edu.cn>, "alto@ietf.org" <alto@ietf.org>
Cc:
Subject: Re: [alto] WGLC for draft-ietf-alto-cost-mode-00

Hi Kai,

I read this document and I support proceeding with its publication.

Thank you,

Jordi 

From: alto <alto-bounces@ietf.org> on behalf of kaigao@scu.edu.cn <kaigao@scu.edu.cn>
Sent: Friday, March 25, 2022 1:46
To:alto@ietf.org <alto@ietf.org>
Subject: [alto] WGLC for draft-ietf-alto-cost-mode-00

WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.

Hi all,

As discussed during the ALTO session in IETF 113, the ALTO cost mode document is now adopted as a working group document. A new WG version (draft-ietf-alto-cost-mode-00) [1] has been submitted to replace the individual draft and address comments from the Call for Adoption.

To move forward, this message starts the WGLC for draft-ietf-alto-cost-mode-00. The WGLC will run till April 8, 2022 (two weeks from now).

As both WG chairs are co-authoring the document, I’m taking care of this call as part of my document shepherding. We would like to have 2-3 reviewers from the working group. Please review and indicate your support or objection to proceed with the publication of this document.

Thanks!

[1] https://datatracker.ietf.org/doc/draft-ietf-alto-cost-mode/.

Best,
Kai
_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

--

Qiao Xiang

Professor, Xiamen University

_________________________________________________________________________________________________________________________

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.