Hi Dhruv, And I added Hari to the to: line, as shepherd.
> On Sep 28, 2022, at 2:48 AM, Dhruv Dhody <[email protected]> wrote: > > +jgs: Is there an established practice in PCE of using US-ASCII as the > +character set for human-readable strings? This would seem to be a > +practice that's discouraged by BCP 18, BCP 166. Was this discussed in > +the WG and a decision taken to not use internationalized strings? > +-- > > Dhruv: Yes. Currently all strings in PCEP are ASCII. See > https://notes.ietf.org/strings-in-pcep?view > > This was discussed briefly in the WG. The authors decided to keep ASCII with > the idea that all string processing would be better to be handled together. Thanks. I think it would be helpful to capture this somehow in the shepherd writeup. I don’t see a perfect place to list it, but it fits sort-of under 10. Several IETF Areas have assembled [lists of common issues that their reviewers encounter][6]. Do any such issues remain that would merit specific attention from subsequent reviews? because the ART checklist includes • Internationalization and Localization: Unicode, UTF-8, UTF-16, Usernames and/or Passwords, anything to be displayed to a user or otherwise involving a phrase like "human-readable” Or it could be covered under questions (1) or (2), though again there isn’t a perfect fit — maybe we should revise the shepherd template again to (re?)introduce an optional question for “describe anything you think interesting or relevant in the WG discussion”. Anyway, I don’t think anyone will be upset if you just fit the information in somewhere... Regards, —John _______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
