I have no opinion in this specific context. That said, I generally
prefer names over numbers in configuration items.
I agree that using a plain YANG string can lead to surprises and
potential security issues if people do not expect that the identifier
can contain almost arbitrary characters. In LM
Hi
I’m fine with instance number. I would not rule out instance name. I’m simply
concerned about
a wide open field.
I would suggest a specific sub-set of characters be allowed if it goes to
“instance name”. The
normal printable characters should be adequate. They generally are handled well
by
Good one. I thought about keeping it, just because :-)
I like the 'IETF 1000 hackathon' typo - this makes it indeed 'best
continuing work' I would say. ;-)
/js
On Wed, Nov 22, 2017 at 04:02:44PM +0100, Benoit Claise wrote:
Forwarding.
I know that some of you are not on the i...@ietf.org mailin
I like the 'IETF 1000 hackathon' typo - this makes it indeed 'best
continuing work' I would say. ;-)
/js
On Wed, Nov 22, 2017 at 04:02:44PM +0100, Benoit Claise wrote:
> Forwarding.
> I know that some of you are not on the i...@ietf.org mailing list.
>
> Regards, Benoit.
>
> Forwarded
Forwarding.
I know that some of you are not on the i...@ietf.org mailing list.
Regards, Benoit.
Forwarded Message
Subject:Blog: YANG Catalog Latest Developments (IETF 100 Hackathon)
Date: Wed, 22 Nov 2017 16:01:49 +0100
From: Benoit Claise
To: IETF-Discussion l
According to RFC 7950, section 9.4, YANG strings are Unicode and
ISO/IEC 10646 characters, including tab, carriage return, and line
feed but excluding the other C0 control characters, the surrogate
blocks, and the noncharacters. Of course, handling Unicode correctly
can still be a lot of fun and sy
Thinking about this some more. I'm not sure what it means for the "ACL
Type" to be "any-acl". It seems that the "match any packet" should be a
type of ACE, e.g. perhaps as the last entry of an ACL, rather than a
type of ACL.
Otherwise if the ACL type is "any-acl" then this only allows two ty
Hi
If you change to “instance name” be very clear on the character set(s) allowed.
I have seen some really bad side
effects when unexpected character sets show up in ID fields. Software tries to
parse it for presentation on a screen
or into a log. The result is a crash or lockup.
Bob
> On N
Mahesh Jethanandani wrote:
> [Taking the discussion to the mailing list]
>
> The summary of the discussion happening on a private thread has to
> do with the ‘any’ container (now leaf) definition in the ACL model
> for something that matches anything, much like a ‘*’ would do in
> regex. The disc
