|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 6038 (2010)
|
|
Title:
|
Two-Way Active Measurement Protocol (TWAMP) Reflect Octets and Symmetrical Size Features
|
|
|
2.
|
Status of approval:
|
|
|
All are approved IETF documents
|
|
3.
|
Justification for the specific reference:
|
|
|
IETF RFC 6038 is an extension to IETF RFC 5357 applying asymmetric IP traffic.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=6038
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
This RFC was approved in October 2010.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Informational IETF Stream document approved October 2010.
.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
This document extends the usage of RFC 5357.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[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./
/
[RFC5618] Morton, A. and K. Hedayat, "Mixed Security Mode for the/
Two-Way Active Measurement Protocol (TWAMP)", RFC 5618,/
August 2009.
|
|
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):
|
|
|
None
|
