Hi all:
While working on the I2RS protocol strawman, some of the design team and early reviewers have disagreed on requirements for the data streams. Therefore, the chairs need input on the requirements for the data streams. Currently the approved requirements have the following types of inbound or outbound streams: 1) Read/writes - simple read/writes or rpc requests, 2) Publication/subscription - via the pub-sub requirements (outbound data stream, inbound control) 3) Actions - via rpc requests (rpc, rpc-response) 4) Some unsecured outbound stream (TBD) As chair, I reviewed the use case requirements and found 11 requirements for I2RS data flow in the (IC) in charter requirements in the I2RS use case requirements document (draft-ietf-i2rs-usecase-reqs-summary <https://datatracker.ietf.org/doc/draft-ietf-i2rs-usecase-reqs-summary> ). These requirements suggest adding: 1) IPFIX as an outbound data stream for traffic monitoring data, and 2) outbound data streams which are data form agnostic (Any of XML, JSON, MTL, protobufs, etc.) over any transport. I've placed the details on these data flow requirements in (draft-hares-i2rs-dataflow-req-01.txt), and I've listed these requirements below. We plan to do I2RS work in phases so we can include a wide scope of outbound protocols (DF-REQ-02/03/09), IPFIX as outbound stream from I2RS ephemeral statistics (DF-REQ-04/05), handling of large data flows outside of pub/sub push (DF-REQ 06). We also have run into request to make sure OAM/ephemeral actions are tailored to work during the network congestion or high resource requirements for routing system (DF-REQ-07/08/09), and that batch uploads of routes work effectively. The only ones I personal (chair hat off) strongly recommend is DF-REQ-01 and DF-REQ-10 so we can vary the level of checking on large batch uploads of routes for certain applications. Jeff and I would like your feedback. To aid this, Sue will present the issues of this topic at the Interim on 10/16/2016 and IETF along with thoughts on the protocol strawman. Sue Hares ================= DF-REQ-01: Support writing to the ephemeral copy of the Local RIB with three different types of checks: minimal data reception checks (TLVs of data valid), all non-referential checks (e.g. do not do leafref, MUST, instance identifiers), and do referential checks via three different rpcs. [Added due to practical consideration with I2RS RIB uploads]. [any form data and transport] DF-REQ-02: The support of large data transfers in a data format agnostic format. This the I2RS protocol should support transport of data in any format including: XML, JSON, MTL (ALias/Waveformat, .mtl), protobufs, and ascii text. DF-REQ-03: Support of any transport [any data form], [/any form data and transport] [IPFIX] DF-REQ-04: Support for the ability to send traffic monitoring information using IPFIX protocol and IPFIX templates, DF-REQ-05: Support of transmitting traffic statistics for filter-based policies (BGP-FS, I2RS FB-RIB, policy routing), IPPM, SFLOW, and others in yang data model format or IPFIX templates formats over XML or JSON. [/IPFIX] [ large data flows outside pub/sub] DF-REQ-06: I2RS should be able to support an action which allocates internal resources for the I2RS agent (memory, processing time, interrupts) and outbound data flow bandwidth. It is expected that an action would be included in a data model in an "rpc"-like format in yang. [/data flows outside of pub-sub - pub-sub already has this restriction] [OAM and outage flows] DF-REQ-07: The I2RS should be able to support an action that interacts with routing OAM functions. DF-REQ-08: The I2RS Agent must be able signals that it will be using different protocol with different constraints (security, priority of data, or transport) or different constraints on the existing protocol (smaller message sizes, different priorities on data carried, or different security levels). (UDP + security vs. TCP + security) [/OAM and outage flows] [yang] DF-REQ-09: Yang MUST have a way to indicate in a data model has actions which allow: different transports, different resource constraints, or different security. DF-REQ-10: Yang MUST have a way to indicate a data model has different levels of checking where: lowest level is message form only, medium level checks message format plus data syntax, and highest level uses the message format, data syntax and referential check netconf configuration does. The default level for I2RS is message format plus data syntax. [/yang]
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
