Re: [Netconf] draft-ietf-netconf-monitoring-09 last call comments from js
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Netconf] draft-ietf-netconf-monitoring-09 last call comments from js
Juergen Schoenwaelder writes:
>Tell me how this works (AVPs are the things RADIUS sends around in the
>payload) - or better tell me not, since this would impact ISMS badly.
Look for "JUNOS Configuration" in:
http://www.cymru.com/gillsr/documents/junos-radius-authentication.htm
>You won't expect TCP objects to document how TCP works, right. The
>same logic applies to RFC 3412 and all the other SNMP RFCs.
No, but I would expect the tcp.yang to fully describe how the tcp
objects work, not just that this leaf has a range of such and the
leaf is a boolean. Given that we can say:
description "
Lots of very detailed text.
More detailed text.
";
and:
/*
Some detailed text that needn't be in the description statement.
*/
And given the number of mib implementors that seem to not read the
rfc, just the mib, I'd vote to have all real text live within the
yang module.
Thanks,
Phil
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.