On Mon, Apr 21, 2014 at 03:02:18PM -0400, Jeffrey Haas wrote: > > The binary encoding of FORCES may help with speed. > It was asserted elsewhere (copied below) that this may only be 3-5% of a > speed improvement. (I had thought I recalled a discussion in netmod(?) at > one point of a BER format for YANG, but my google-fu is failing me.) >
As long as you do crypto in software, the outcome of the binary vs. textual data encoding discussion likely does not matter much. Note that for NC all standards-track transports do authentication and encryption above the transport layer (via SSH or optionally TLS). For RC it is likely going to be TLS. For ForCES, it seems RFC 5811 (ForCES over SCTP) requires IPsec in transport mode plus IKE. Perhaps all boxes that are targets for I2RS can be assumed to have hardware crypto and hence this is a non-issue. But I think it is important to keep the bigger picture in mind when we talk about performance (and I assume I2RS will not pass through the IESG with a plaintext transport mode). /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 <http://www.jacobs-university.de/> _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
