I think we have two options:
1. Report as a new Errata, not necessarily incorporated into
draft-ietf-alto-cost-mode-00
2. Fix this altogether in draft-ietf-alto-cost-mode-00
Let’s hear what other say about this.
-Qin
发件人: Qiao Xiang [mailto:xiang...@gmail.com]
发送时间: 2022年4月11日 9:17
Cool. Then it seems we should update RFC7285 to be consistent with
unicode.org and other RFCs. What do you think, Qin?
Best
Qiao
On Mon, Apr 11, 2022 at 8:19 AM wrote:
> Hi Qin, Qiao and all,
>
>
> I searched for a few documents and it seems that many documents are
> referring to U+002D as
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
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/U.pdf, is
current best practice, I have no
Thanks Jordi for bringing this up on the list for further discussion.
I am wondering whether building Bottleneck structure can be seen as modeling
technology and require AI and machine learning technologies to be involved? If
the answer is yes, it might be worth exploring this in NMRG mailing
Cool. I'm ok with it. Was being extra careful. :-)
Best
Qiao
On Sun, Apr 10, 2022 at 3:57 PM wrote:
> 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
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"
Sent Time:2022-04-09 18:04:36 (Saturday)
