Re: [Netconf] WGLC on netconf-event-notifications-13

> From: Tianran Zhou, October 9, 2018 10:07 PM
> 
> Hi,
> 
> I have reviewed this document, and think it's OK to move forward.
> 
> Only one thing, I am a little lost in the following paragraph.
> "  Each error identity will be inserted as the "error-app-tag" using
>    JSON encoding following the form <modulename>:<identityname>.  An
>    example of such as valid encoding would be "ietf-subscribed-
>    notifications:no-such-subscription". "
> 
> I do not know why "JSON encoding" is mentioned here.
> <modulename>:<identityname> is not JSON like.

Thanks for the comment Tianran.   In that paragraph we are saying that a way of encoding is needed to uniquely identify a specific identity within the module.  As you point out, It is true that there are not quotes around the "<modulename>" and  "<identityname>".  So you are right that it is not exactly JSON like (although there is some similarity).   

To remove the confusion, I just eliminated the text "using JSON encoding".  Is that sufficient for you?

Eric

> Regards,
> Tianran
> 
> > -----Original Message-----
> > From: Netconf [mailto:netconf-bounces@ietf.org] On Behalf Of Kent
> > Watsen
> > Sent: Friday, October 05, 2018 6:11 AM
> > To: netconf@ietf.org
> > Subject: [Netconf] WGLC on netconf-event-notifications-13
> >
> > This message starts a Last Call on
> > draft-ietf-netconf-netconf-event-notifications-13 (a.k.a.
> > "netconf-notif"):
> >
> >
> > https://tools.ietf.org/html/draft-ietf-netconf-netconf-event-notificat
> > io
> > ns-13
> >
> > This, along with the restconf-notif Last Call, started in a separate
> > message, marks the last of the last calls on the yang push suite of
> > drafts. As explained before, given the size and number of documents,
> > the chairs decided to break the reviews up into pieces so as to get
> > focus on each in turn.  We chose to go top-down, starting with
> > yang-push and ending with the "notif" drafts.  We plan to submit the drafts
> for publication when they are ready as a collective.
> > The goal is to do all this prior to IETF 103.
> >
> > While it's always nice to receive messages of support, at this time,
> > the question isn't so much if the working group supports the work than
> > if the document is ready to progress.  The chairs need to see reviews
> > that indicate thorough end-to-end reading of the text.  Of course, if
> > there are any objections, these should be brought forward now as well.
> >
> > The current version (-13) of this draft was published on Oct 4th (today).
> > The datatracker page for the draft is here:
> >
> >
> > https://datatracker.ietf.org/doc/draft-ietf-netconf-netconf-event-noti
> > fi
> > cations.
> >
> >
> > Thanks,
> > Kent (and Mahesh)
> >
> >
> >
> > _______________________________________________
> > Netconf mailing list
> > Netconf@ietf.org
> > https://www.ietf.org/mailman/listinfo/netconf
> 
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf