|
1.
|
Clear description of the referenced document:
|
|
|
|
|
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:
|
|
|
Required for sub-path definition.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Copyright (c) 2010 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.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
|
|
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.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Last updated April 2010
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
This document has relationship with [RFC2330], [Y.1540], [RFC2330], 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, March 1997./
/
[RFC2330] Paxson, V., Almes, G., Mahdavi, J., and M. Mathis,/
"Framework for IP Performance Metrics", RFC 2330,/
May 1998./
/
[RFC3979] Bradner, S., Ed., "Intellectual Property Rights in IETF/
Technology", BCP 79, RFC 3979, March 2005./
/
[RFC4656] Shalunov, S., Teitelbaum, B., Karp, A., Boote, J., and/
M. Zekauskas, "A One-way Active Measurement Protocol/
(OWAMP)", RFC 4656, September 2006./
[RFC5357] Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and/
J. Babiarz, "A Two-Way Active Measurement Protocol/
(TWAMP)", RFC 5357, October 2008./
/
Informative References/
/
[RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way/
Delay Metric for IPPM", RFC 2679, September 1999./
/
[RFC2680] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way/
Packet Loss Metric for IPPM", RFC 2680, September 1999./
/
[RFC2681] Almes, G., Kalidindi, S., and M. Zekauskas, "A Round-trip/
Delay Metric for IPPM", RFC 2681, September 1999./
/
[RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay/
Variation Metric for IP Performance Metrics (IPPM)",/
RFC 3393, November 2002./
/
[RFC4737] Morton, A., Ciavattone, L., Ramachandran, G., Shalunov,/
S., and J. Perser, "Packet Reordering Metrics", RFC 4737,/
November 2006./
/
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation/
Applicability Statement", RFC 5481, March 2009./
/
[RFC5560] Uijterwaal, H., "A One-Way Packet Duplication Metric",/
RFC 5560, May 2009./
/
[RFC5644] Stephan, E., Liang, L., and A. Morton, "IP Performance/
Metrics (IPPM): Spatial and Multicast", RFC 5644,/
October 2009./
/
[Y.1540] ITU-T Recommendation Y.1540, "Internet protocol data/
communication service - IP packet transfer and/
availability performance parameters", November 2007./
|
|
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):
|
|
|
Authors' Addresses
Al Morton (editor)
AT&T Labs
200 Laurel Avenue South
Middletown, NJ 07748
USA
Phone: +1 732 420 1571
Fax: +1 732 368 1192
EMail: acmorton@att.com
URI: http://home.comcast.net/~acmacm/
Steven Van den Berghe (editor)
Alcatel-Lucent
Copernicuslaan 50
Antwerp 2018
Belgium
Phone: +32 3 240 3983
EMail: steven.van_den_berghe@alcatel-lucent.com
|
|
