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

[Juergen Schoenwaelder <[e-mail]>]

On Thu, Dec 12, 2013 at 08:52:09AM +0100, Martin Bjorklund wrote:
> Randy Presuhn <[e-mail]> wrote:
> > Hi -
> > 
> > >From: Juergen Schoenwaelder <[e-mail]>
> > >Sent: Dec 11, 2013 12:38 AM
> > >To: Randy Presuhn <[e-mail]>
> > >Cc: [e-mail]
> > >Subject: Re: [netmod] AD review of draft-ietf-netmod-system-mgmt
> > >
> > >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.
> > 
> > Not if the data definition restricts the values to an ASCII
> > subset, as has been proposed.  What's in the draft at the
> > moment will bring its own interoperability problems, but
> > at least it's a baby step forward.
> 
> So it seems we have a chance to fix this now.  But I need to
> understand what exactly you and/or Juergen propose.  Preferrably
> concrete text.  I *think* that the proposal is something like this:
> 
>    o  An implementation MUST allow any legal "string" (YANG string).

I do not think we need to state this since this is the default anyway
for an object using the string type.
 
>    o  An implementation that maps this value to the corresponding MIB
>       object, which has size and character set limitations, MUST use
>       some mechanism out of the scope for this document to ensure that
>       the MIB object syntax is still valid.

Yes.

> Also, just to make sure, we are talking about:
> 
>    system/location        -- sysLocation
>    system/contact         -- sysContact
>    interface/description  -- ifAlias

It might also apply to interface/name (ifName).

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1, 28759 Bremen, Germany
Fax:   [phone]         <http://www.jacobs-university.de/>