Paul: The current I2RS RIB Data model is a yang model which can be access via netconf and restconf with the restrictions in the network management datastore architecture. Are you looking for us to specify the netconf/restconf suite protocols, and the CBOR for binary in this section. If you are looking for more than that, are you looking for what is in https://datatracker.ietf.org/doc/draft-ietf-i2rs-security-environment-reqs/ Thank you, Sue Hares WG co-chair -----Original Message----- From: i2rs [mailto:i2rs-bounces@xxxxxxxx] On Behalf Of Paul Wouters Sent: Sunday, February 25, 2018 1:59 PM To: secdir@xxxxxxxx Cc: i2rs@xxxxxxxx; ietf@xxxxxxxx; draft-ietf-i2rs-rib-info-model.all@xxxxxxxx Subject: [i2rs] Secdir last call review of draft-ietf-i2rs-rib-info-model-14 Reviewer: Paul Wouters Review result: Has Issues I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. The summary of the review is Has Issues. This Informational draft specifies an information model for routing information bases (RIBs) , and hints at how a read/write API would look like. I think the document should be improved to clarify this API beyond a simple mention of SSH and TLS in its own section, outside of the Security Consideration section. For example, if this is TLS, what is used? Something restful? xml? json? What would the URI be? And for ssh, what kind of access would be given? How is this restricted to the RIB API ? _______________________________________________ i2rs mailing list i2rs@xxxxxxxx https://www.ietf.org/mailman/listinfo/i2rs
