|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 7799 (2016)
|
|
Title:
|
Active and Passive Metrics and Methods (with Hybrid Types In-Between)
|
|
|
2.
|
Status of approval:
|
|
|
This document is not an Internet Standards Track specification; it is published for informational purposes.
|
|
3.
|
Justification for the specific reference:
|
|
|
Contains the definitions of active and passive methods re-used in this Recommendation.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7799.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
This document is Request for comments approved in May 2016. it is
published for informational purposes.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
This document has relationship with ITU-T Y.1540, [RFC2330], [RFC6390], [RFC2119], etc.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119,/
DOI 10.17487/RFC2119, March 1997,/
http://www.rfc-editor.org/info/rfc2119./
/
[RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis,/
"Framework for IP Performance Metrics", RFC 2330,/
DOI 10.17487/RFC2330, May 1998,/
http://www.rfc-editor.org/info/rfc2330./
/
[RFC3432] Raisanen, V., Grotefeld, G., and A. Morton, "Network/
performance measurement with periodic streams", RFC 3432,/
DOI 10.17487/RFC3432, November 2002,/
http://www.rfc-editor.org/info/rfc3432./
/
[RFC5644] Stephan, E., Liang, L., and A. Morton, "IP Performance/
Metrics (IPPM): Spatial and Multicast", RFC 5644,/
DOI 10.17487/RFC5644, October 2009,/
http://www.rfc-editor.org/info/rfc5644./
/
[RFC5835] Morton, A., Ed. and S. Van den Berghe, Ed., "Framework for/
Metric Composition", RFC 5835, DOI 10.17487/RFC5835, April/
2010, http://www.rfc-editor.org/info/rfc5835./
/
[RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New/
Performance Metric Development", BCP 170, RFC 6390,/
DOI 10.17487/RFC6390, October 2011,/
http://www.rfc-editor.org/info/rfc6390./
[RFC7011] Claise, B., Ed., Trammell, B., Ed., and P. Aitken,/
"Specification of the IP Flow Information Export (IPFIX)/
Protocol for the Exchange of Flow Information", STD 77,/
RFC 7011, DOI 10.17487/RFC7011, September 2013,/
http://www.rfc-editor.org/info/rfc7011./
/
[RFC7312] Fabini, J. and A. Morton, "Advanced Stream and Sampling/
Framework for IP Performance Metrics (IPPM)", RFC 7312,/
DOI 10.17487/RFC7312, August 2014,/
http://www.rfc-editor.org/info/rfc7312./
/
[RFC7594] Eardley, P., Morton, A., Bagnulo, M., Burbridge, T.,/
Aitken, P., and A. Akhter, "A Framework for Large-Scale/
Measurement of Broadband Performance (LMAP)", RFC 7594,/
DOI 10.17487/RFC7594, September 2015,/
http://www.rfc-editor.org/info/rfc7594./
Informative References/
/
[COLORING]/
Chen, M., Ed., Zheng, L., Ed., Mirsky, G., Ed., Fioccola,/
G., Ed., and T. Mizrahi, Ed., "IP Flow Performance/
Measurement Framework", Work in Progress, draft-chen-ippm-/
coloring-based-ipfpm-framework-06, March 2016./
/
[HYBRID] Trammell, B., Zheng, L., Berenguer, S., and M. Bagnulo,/
"Hybrid Measurement using IPPM Metrics", Work in Progress,/
draft-trammell-ippm-hybrid-ps-01, February 2014./
/
[OPSAWG] Capello, A., Cociglio, M., Castaldelli, L., and A. Bonda,/
"A packet based method for passive performance/
monitoring", Work in Progress, draft-tempia-opsawg-p3m-04,/
February 2014./
/
[PASSIVE] Zheng, L., Elkins, N., Lingli, D., Ackermann, M., and G./
Mirsky, "Framework for IP Passive Performance/
Measurements", Work in Progress, draft-zheng-ippm-/
framework-passive-03, February 2015./
/
[PDMOPTION]/
Elkins, N. and M. Ackermann, "IPv6 Performance and/
Diagnostic Metrics (PDM) Destination Option", Work in/
Progress, draft-ietf-ippm-6man-pdm-option-02, April 2016./
[RFC6374] Frost, D. and S. Bryant, "Packet Loss and Delay/
Measurement for MPLS Networks", RFC 6374,/
DOI 10.17487/RFC6374, September 2011,/
http://www.rfc-editor.org/info/rfc6374./
/
[STDFORM] Morton, A., Fabini, J., Elkins, N., Ackermann, M., and V./
Hegde, "Updates for IPPM's Active Metric Framework:/
Packets of Type-P and Standard-Formed Packets", Work in/
Progress, draft-morton-ippm-2330-stdform-typep-02,/
December 2015./
/
[Y.1540] ITU-T, "Internet protocol data communication service - IP/
packet transfer and availability performance parameters",/
March 2011,/
https://www.itu.int/rec/T-REC-Y.1540-201103-I/en./
/
[Y.1731] ITU-T, "Operation, administration and management (OAM)/
functions and mechanisms for Ethernet-based networks",/
August 2015,/
https://www.itu.int/rec/T-REC-G.8013-201508-I/en.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
Author's Address
Al Morton
AT&T Labs
200 Laurel Avenue South
Middletown, NJ
United States
Email: acmorton@att.com
|
|
