An LMAP application for IPFIX
draft-bagnulo-lmap-ipfix-00
The information below is for an old version of the document.
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
|
|
---|---|---|---|
Authors | Marcelo Bagnulo , Brian Trammell | ||
Last updated | 2013-02-08 | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | I-D Exists | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
draft-bagnulo-lmap-ipfix-00
sourceTransportPort = 23677 destinationTransportPort = 34567 flowStartMilliseconds = the timestamp corresponding to 10:00 CET flowEndMilliseconds = the timestamp corresponding to 10:00 CET plus 1 millisecond (Assuming 1 ms of delay) --------------------------- metricIdentifier = UDP_Latency as per [I-D.bagnulo-ippm-new-registry-independent] testSchedule = Periodic as per [I-D.bagnulo-ippm-new-registry-independent] scheduleRate = 1 outputType = Raw as per [I-D.bagnulo-ippm-new-registry-independent] testEnvironment = No-cross-traffic as per [I-D.bagnulo-ippm-new-registry-independent] sourceIPv4Address = 192.0.2.1 destinationIPv4Address = 203.0.113.1 sourceTransportPort = 23677 destinationTransportPort = 34567 flowStartMilliseconds = the timestamp corresponding to 10:00 CET plus one second flowEndMilliseconds = the timestamp corresponding to 10:00 CET plus one second plus 2 millisecond (Assuming 2 ms of delay) --------------------------- metricIdentifier = UDP_Latency as per [I-D.bagnulo-ippm-new-registry-independent] testSchedule = Periodic as per [I-D.bagnulo-ippm-new-registry-independent] scheduleRate = 1 outputType = Raw as per [I-D.bagnulo-ippm-new-registry-independent] testEnvironment = No-cross-traffic as per [I-D.bagnulo-ippm-new-registry-independent] sourceIPv4Address = 192.0.2.1 destinationIPv4Address = 203.0.113.1 sourceTransportPort = 23677 destinationTransportPort = 34567 flowStartMilliseconds = the timestamp corresponding to 10:00 CET plus two seconds flowEndMilliseconds = the timestamp corresponding to 10:00 CET plus two seconds plus 1 millisecond (Assuming 1 ms of delay) --------------------------- 4. Discussion Overhead. As noted in the previous example, all the data describing the test itself is repeated in every Data set resulting in increased Bagnulo & Trammell Expires August 11, 2013 [Page 7] Internet-Draft LMAP-IPFIX February 2013 overhead. Since the data describing the test can be considered metadata about the test results, it would be possible to explore the possibility of encoding it in Options Templates. 5. What standardization is needed for this? So, in order to enable the use of IPFIX for LMP, the following pieces of standardization would be required. o The definition of the metric registry. This is not specific for IPFIX as any other Report protocol is likely to require this, but having an independent registry enables multiple report protocols. o The definition of new IEs. Some of them are identified above, some other are likely to be needed as well. o The definition of the Templates sets for each of the tests to be performed. This is necessary to have a defined Template that different vendors can implement and can use the IPFIX format in the wire, but they don't need to fully implement IPFIX parsing to read arbitrary Template sets, just the ones associated with the relevant metrics. 6. Security considerations TBD 7. IANA Considerations TBD 8. Acknowledgements We would like to thank Sam Crawford and Al Morton for input on early discussions for this draft. 9. References 9.1. Normative References [RFC5101] Claise, B., "Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of IP Traffic Flow Information", RFC 5101, January 2008. [RFC5470] Sadasivan, G., Brownlee, N., Claise, B., and J. Quittek, "Architecture for IP Flow Information Export", RFC 5470, Bagnulo & Trammell Expires August 11, 2013 [Page 8] Internet-Draft LMAP-IPFIX February 2013 March 2009. [I-D.bagnulo-ippm-new-registry-independent] Bagnulo, M., Burbridge, T., Crawford, S., Eardley, P., and A. Morton, "A registry for commonly used metrics. Independent registries", draft-bagnulo-ippm-new-registry-independent-00 (work in progress), January 2013. 9.2. Informative References [I-D.ietf-ipfix-ie-doctors] Trammell, B. and B. Claise, "Guidelines for Authors and Reviewers of IPFIX Information Elements", draft-ietf-ipfix-ie-doctors-07 (work in progress), October 2012. Authors' Addresses Marcelo Bagnulo Universidad Carlos III de Madrid Av. Universidad 30 Leganes, Madrid 28911 SPAIN Phone: 34 91 6249500 Email: marcelo@it.uc3m.es URI: http://www.it.uc3m.es Brian Trammell Swiss Federal Institute of Technology Zurich Gloriastrasse 35 8092 Zurich Switzerland Email: trammell@tik.ee.ethz.ch Bagnulo & Trammell Expires August 11, 2013 [Page 9]