Re: [netmod] Add "node-instance-identifier" to rfc6991-bis?

[Kent Watsen]

 PS: the "token” type add discussion from before never completed (again, 
 modeled after xsd:token)
>> 
>> What about this?
>> 
> 
> What would this type be good for? Any models already using something
> like this?


Not in a standard model, that I’m aware of but, back at Juniper, I had a 
typedef for this that I used as a basis for so many things, but mostly things 
intended to be identifiers of sorts, whereby having whitespace didn’t make 
sense.

Kent // contributor

___
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Re: [netmod] Shepherd review on draft-ietf-netmod-yang-instance-file-format-10

[Kent Watsen]

Hi Balazs,


> P.S. Kent, if further edits are needed, shall I do them via new uploaded 
> versions, or shall I just send the update for checking to you?

I prefer uploaded versions so I (everyone) can easily see the diffs and verify 
the changes made.  Thanks for asking.



> Because it’s a working group document now and so uses the “ietf” prefix.  Try 
> this:
>  
>
> BALAZS2: OK, thanks

Np



> - S5 contains an mix of important and unimportant information.   I think that 
> the most important thing to state that the module defines an offline format 
> that MAY contain security sensitive information, and thus safe handling is 
> advised.  Maybe also say something about because the YANG module only defines 
> a “structure”,  the Security Considerations doesn’t follow the template 
> specified in https://tools.ietf.org/html/rfc8407#section-3.7.1 
> ).  For instance: s/is 
> designed as a wrapper specifying a format and a metadata header for YANG 
> instance data defined by the content-schema/specifies an offline format/
> BALAZS: Most of text was required to be put there by earlier reviewers 
> (Mostly Juergen and Acee Lindem) and sent to the mailing list.
> I added that we do not follow the security template for YANG models.
>  
> Please add the reference to https://tools.ietf.org/html/rfc8407#section-3.7.1 
>  per above.
> BALAZS2: OK

Thx


>  - S8.1: agreed that RFC8525 is Normative, but the only place it it 
> referenced is in a non-normative section…please add a ref to it from a 
> normative section.
> BALAZS: It is referenced from the YANG module which is normative.
>  
> You just added that reference, but not correctly:
>   1) the “reference” doesn’t follow the standard format
>   2) the paragraph at the top of 3.2 doesn’t also list RFC 8525
> BALAZS2: OK, corrected

Getting there…

A)
  OLD:
 The first item is either ietf-yang-library
  NEW:
The first module listed MUST either 'ietf-yang-library’, from RFC 8525,

B) 
  OLD:
This YANG module imports typedefs from [RFC6991], identities from
[RFC8342] and the "structure" extension from
[I-D.ietf-netmod-yang-data-ext].  It also references [RFC8525].

  NEW:
This YANG module imports typedefs from [RFC6991], identities from
[RFC8342], and the "structure" extension from
[I-D.ietf-netmod-yang-data-ext].  It also references [RFC8525]
in a “description” statement..



>  - Appendix B:
> - s/For instance data/Instance data/
> BALAZS: Sorry, that would make the sentence incorrect.
>  
> Do you mean it to be “For instance, data” then?   If “instance data” is 
> supposed to be read together, maybe use a hyphen or quotes?
> BALAZS2: OK, added quotes

Thank you!  (I hope you see now how confusing that was to read before…)


> - the syntax grammar used in S3, P8 doesn’t make sense - use ABNF?
> BALAZS: 
>  
> Please fix the grammar.
>  
> BALAZS2: OK, Updated grammar.

That grammar excludes the possibility of using CBOR, which is indicated as 
possible in S2, P3...


Also, isn’t this now the case?
   OLD: The name of the instance data file SHOULD be of the form:
   NEW: The name of the instance data file MUST be of the form, defined using 
ABNF [RFC5234]:

- and be sure to add a Normative reference to RFC 5234




> - In S3, P8: “the semicolons and the decimal point, if present, shall be 
> replaced by underscores” - why are they not escaped?
> BALAZS: This is a file name. Escaping in file names does not always work 
> (depending on the filesystem and tools used). This is more simple and 
> understandable
>  
> No, this is a special case CLR and we never do this.  I see this idea has 
> been in the document since -03, so it must’ve bee discussed, can you point me 
> to the discussion? 
>  
> FWIW, my OS doesn’t even require escaping colons.  BTW, they’re “colons” (not 
> semicolons).
> BALAZS2: Windows doesn’t allow colons in the filename. Although it’s not 
> everyone’s favorite OS, it is pretty widespread. 

Understood, but that doesn’t explain why escapes can’t work.  Please explain.


> For Ubuntu Linux and a bash shell the colon is allowed, but tab extension 
> does not work properly.

On Bash:
  $ touch a:b
  $ ls a ---> replaces “a” with "a\:b” 
  a:b

Seems regular to me…what’s the problem?


> Sorry, I don’t remember any discussion on this. Timestamps were discussed, 
> but I don’t find any arguments about this substitution.
> Changed semicolon->colon

Excellent.


> - It is unclear how the "inline-content-schema” feature could ever be used.  
> I.e., there are no protocol-accessible nodes in the module…
> BALAZS: The system can declare in supported/not-supported in design 
> documentation. E.g. in UC2, Preloading Default Configuration the designer 
> preparing instance data, can decide to use or not use the 
> inline-content-schema based on this.
>  
> When I make statements like this, please see it 

Re: [netmod] YANG Versioning weekly meeting (not a VI!)

[Kent Watsen]

Updated ICS file attached...now the 15-minute start alarm should be set.

Kent // as co-chair


BEGIN:VCALENDAR
CALSCALE:GREGORIAN
VERSION:2.0
X-WR-CALNAME:YANG Versioning
METHOD:PUBLISH
PRODID:-//Apple Inc.//Mac OS X 10.14.6//EN
BEGIN:VTIMEZONE
TZID:America/Scoresbysund
BEGIN:DAYLIGHT
TZOFFSETFROM:-0100
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
DTSTART:19820328T00
TZNAME:GMT
TZOFFSETTO:+
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
DTSTART:19961027T01
TZNAME:GMT-1
TZOFFSETTO:-0100
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
ATTENDEE;CN="NETMOD Working Group";CUTYPE=INDIVIDUAL;EMAIL="netmod-chair
 s...@ietf.org";ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:netmod-cha...@ietf.org
DTEND;TZID=America/Scoresbysund:20200414T14
TRANSP:OPAQUE
ORGANIZER;CN="Cisco Webex";SCHEDULE-AGENT=CLIENT:MAILTO:messenger@webex.
 com
UID:7be01da1-3f37-458e-ba86-6f8014452267
DTSTAMP:20200421T13Z
LOCATION:https://ietf.webex.com/ietf
X-APPLE-TRAVEL-ADVISORY-BEHAVIOR:AUTOMATIC
DESCRIPTION:\n\nJOIN WEBEX MEETING\nhttps://ietf.webex.com/ietf/j.php?MT
 ID=m2c561452450cf19d54e91c84b70c14cc\nMeeting number (access code): 617 
 633 719\n\nHost key: 504671\n\nMeeting password: Pm2SJHakZ23\n\n\n\nJOIN
  BY PHONE\n1-650-479-3208 Call-in toll number (US/Canada) \nTap here to 
 call (mobile phones only\, hosts not supported): tel:%2B1-650-479-3208\,
 \,*01*617633719%23%23*01*\n\n1-877-668-4493 Call-in toll free number (US
 /Canada) \nTap here to call (mobile phones only\, hosts not supported): 
 tel:1-877-668-4493\,\,*01*617633719%23%23*01*\n\nGlobal call-in numbers:
 \nhttps://ietf.webex.com/ietf/globalcallin.php?MTID=m760b4453ad872ad0c59
 799278e28ae64\n\nToll-free dialing restrictions: \nhttps://www.webex.com
 /pdf/tollfree_restrictions.pdf\n\n\nJOIN FROM A VIDEO SYSTEM OR APPLICAT
 ION\nDial sip:617633...@ietf.webex.com\nYou can also dial 173.243.2.68 a
 nd enter your meeting number.\n\n\nJoin using Microsoft Lync or Microsof
 t Skype for Business\nDial sip:617633719.i...@lync.webex.com\n\n\n\nCan'
 t join the meeting? Contact support here:\nhttps://ietf.webex.com/ietf/m
 c\n\n\nIMPORTANT NOTICE: Please note that this Webex service allows audi
 o and other information sent during the session to be recorded\, which m
 ay be discoverable in a legal matter. You should inform all meeting atte
 ndees prior to recording if you intend to record the meeting.\n
PRIORITY:5
SEQUENCE:1586881774
CLASS:PUBLIC
X-ALT-DESC;FMTTYPE=text/html:* {padding: 0\; 
margin: 0\;}table {	border-collapse: separate\; width =100%\;	border:
  0\;	border-spacing: 0\;}tr {	line-height: 18px\;}a, td {	font-size: 14p
 x\;	font-family: Arial\;	color: #333\;	word-wrap: break-word\;	word-brea
 k: normal\;	padding: 0\;}.title {	font-size: 28px\;}.image {	width: auto
 \;	max-width: auto\;}.footer {	width: 604px\;}.main {}@media screen and 
 (max-device-width: 800px) {	.title {		font-size: 22px !important\;	}	.im
 age {		width: auto !important\;		max-width: 100% !important\;	}	.footer 
 {		width: 100% !important\;		max-width: 604px !important	}	.main {		widt
 h: 100% !important\;		max-width: 604px !important	}}	\;When it's ti
 me, join the Webex meeting here.	\;	
 		Meeting number
  (access code): 617 633 719		Hos
 t key: 504671			Meeting password:Pm2SJHakZ23	\;		
 			Join meetin
 g \;\;Join by phone\; Tap to call in from a mobile device (attendees only)\; 1-650-479-3208\;Call-in toll number (US/C
 anada)\; 1-877-668-4493\;Call-in toll free nu
 mber (US/Canada)\; https://ietf.webex.com/ietf/
 globalcallin.php?MTID=m760b4453ad872ad0c59799278e28ae64">Global call-in numbers\;\;|\;\;https://www.webex
 ..com/pdf/tollfree_restrictions.pdf">Toll-free calling restrictions \; \;Join from a video system or applicationDial 617633...@ietf.we
 bex.com\; You can also dial 173.243.2.68 and enter your meeting number. 
 bsp\; \; \; Join using Microsoft Lync or Microsoft Skype for Busi
 nessDial 617633719.i...@lync.webex.com			\;	Need help? Go to http://help.webex.com; style="color:#04
 9FD9\; text-decoration:none\;">http://help.webex.com	\;		
SUMMARY:YANG Versioning
LAST-MODIFIED:20200416T174539Z
DTSTART;TZID=America/Scoresbysund:20200414T13
CREATED:20200414T163150Z
RRULE:FREQ=WEEKLY;INTERVAL=1;UNTIL=20200811T14Z;BYDAY=TU
BEGIN:VALARM
X-WR-ALARMUID:55A190FE-533F-48CC-9563-CD24226D8FF6
UID:55A190FE-533F-48CC-9563-CD24226D8FF6
TRIGGER:-PT15M
ATTACH;VALUE=URI:Chord
ACTION:AUDIO
END:VALARM
END:VEVENT
END:VCALENDAR




> On Apr 14, 2020, at 2:25 PM, Kent Watsen  wrote:
> 
> 
> For those interested in participating in discussions on the YANG Versioning 
> set of drafts, the following weekly 1-hour meeting has been created by 
> request of the authors for that purpose.
> 
> ICS file attached (includes a 15-minute alarm)
> 
> PS: this is NOT a