----- Original Message ----- From: "Joe Clarke (jclarke)" <[email protected]> Sent: Thursday, May 09, 2019 3:28 PM
> > > On May 8, 2019, at 07:31, tom petch <[email protected]> wrote: > > > > ----- Original Message ----- > > From: "Joe Clarke (jclarke)" <[email protected]> > > Sent: Monday, May 06, 2019 4:11 PM > >> > >> On May 6, 2019, at 08:06, Qin Wu > > <[email protected]<mailto:[email protected]>> wrote: > >> > >> Hi, Chairs: > >> Sorry for late follow up, thanks Jurgen, Andy,Joe, Joel and all others > > for good comments, here is the update based on discussion and suggestion > > on the mailing list > >> The diff is: > >> https://www.ietf.org/rfcdiff?url2=draft-wu-netmod-factory-default-03 > >> > >> Hey, Qin. I read through the changes, and I have a couple of > > additional comments. > >> > >> First, the term “YANG server” sounds odd to me. I know what you mean, > > but I haven’t seen this defined before. Maybe just saying a device or > > host is sufficient? > > > > Joe > > > > If you look at the various RFC - YANG, Netconf, NMDA - they all define > > the terms 'client' and 'server'; in the context, 'YANG server' seems > > appropriate. > > It was the combination of the two words as “YANG server” which throws me. You’re serving data modeled using YANG. Anyway, it sounds like there’s a good referential solution to this from Jürgen and Martin, so that should sort this out. Joe, yes, I can see what you mean. I was objecting to the use of 'host', 'device' or such like having just read draft-dai-quic-netconf-00.txt which wants to reserve client and server for the transport and go to manager and agent for netconf. We have been down this road before, with SNMP and NETCONF, and the confusion it creates is considerable. If authors cannot cope with well-established terminology, then they should not be writing I-Ds - if that I-D comes up for adoption in its present form, I will resolutely oppose, all the way to IETF Last Call. </rant> Tom Petch > Joe > > _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
