Re: [netmod] AD review of draft-ietf-netmod-system-mgmt

[Benoit Claise <[e-mail]>]

Dear all,
> On Tue, Dec 10, 2013 at 01:18:10PM -0800, Randy Presuhn wrote:
>   
>>> Anyway, for a standardized approach, someone would have to write a
>>> document that defines how unicode code points are represented as
>>> escaped charater sequences in DisplayStrings. I do not think that this
>>> document is in charge of doing this. Hence, until such a standard is
>>> written, I think things need to be implementation specific.
>> Perhaps, though that is the route to being stuck with ASCII until the
>> successor to Netconf rolls along.
> Not necessarily. If you configure via NETCONF (or most CLIs these
> days), you can use unicode characters. The code that maps names to
> legacy non-unicode interfaces then needs to do suitable translations
> to fit whatever constraint there is.
If the WG is fine with this proposal, fine with me.  You should adapt 
the proposal then.
For consistency reasons, that principle should be applied to 
description/ifAlias in draft-ietf-netmod-interfaces-cfg.
This could be considered as IETF LC comment, I guess.

>
> If someone configures via legacy non-unicode interfaces, well then
> there is no unicode in the configured names. I do not think we can fix
> that problem. This requires to change the legacy non-unicode
> interfaces, which I think is not the task of this WG.
Agreed.

Regards, Benoit
>
> /js
>