Re: [netconf] Murray Kucherawy's No Objection on draft-ietf-netconf-http-client-server-17: (with COMMENT)

[Orie Steele <[e-mail]>]

I asked because I was interested in possible differences between server
names defined by this specification, and IDNA2008.

I can imagine possible compatibility issues, between server names supported
by Yang, and ones supported by IDNA2008 or UTS46.

Being unfamiliar with Yang, I wondered if there is a specific document that
addressed international domain names, that might be of use for this
particular field.

It was just a comment.


On Mon, Feb 19, 2024, 7:04 PM Kent Watsen <[e-mail]> wrote:

> Hi Murray (and Orie),
>
> Thank you for your comment.
> Please find my  response below.
>
> Kent
>
>
> On Feb 15, 2024, at 10:18 AM, Murray Kucherawy via Datatracker <
> [e-mail]> wrote:
>
> Murray Kucherawy has entered the following ballot position for
> draft-ietf-netconf-http-client-server-17: 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-netconf-http-client-server/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Feedback from Orie Steele, incoming ART AD:
>
> eaf server-name {
>      nacm:default-deny-write;
>      type string;
>      description
>        "The value of the 'Server' header field.  If not set, then
>         underlying software's default value is used.  Set to the
>         empty string to disable.";
>    }
>
> I'm not a YANG expert, is "type string" shorthand for "UTF-8 string" ?
>
> I don't see any ART review, are there any i18n issues expected with this
> document?
>
>
>
> YANG’s string type si defined here:
> https://datatracker.ietf.org/doc/html/rfc7950#section-9.4
>
> Which says:
>
>    Legal characters are the Unicode and ISO/IEC 10646 [ISO.10646]
>    characters, including tab, carriage return, and line feed but
>    excluding the other C0 control characters, the surrogate blocks, and
>    the noncharacters.
>
> As with all YANG leafs of type “string”, a “pattern” statement may be used
> to reduce its character set.
>
> Is there a particular character set that needs to be supported?
>
> Thanks again,
> Kent
>
>
>
>
>