Committed to connecting the world

  •  
ITU GSR 2024

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : Q.3960     
  ITU-T A.5 justification information for referenced document IETF RFC 2681 (1999) in draft Q.3960
1. Clear description of the referenced document:
Name: IETF RFC 2681 (1999)
Title: IETF RFC 2681 (1999), A Round Trip Delay Metric for IPPM
2. Status of approval:
1999
3. Justification for the specific reference:
IETF RFC 2681 (1999) is used as refrence in Q.FW_Int_sp_test
4. Current information, if any, about IPR issues:
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/.
5. Other useful information describing the "Quality" of the document:
RFC - Proposed Standard (September 1999; Errata exhist) Last updated 2013-03-02
6. The degree of stability or maturity of the document:
Last updated 2013-03-02
7. Relationship with other existing or emerging documents:
None
8. Any explicit references within that referenced document should also be listed:
[1] Paxson, D., Almes, G., Mahdavi, J. and M. Mathis, "Framework for/
IP Performance Metrics", RFC 2330, May 1998./
/
[2] Almes, G., Kalidindi,S. and M. Zekauskas, "A One-way Delay/
Metric for IPPM", RFC 2679, September 1999./
/
[3] Mills, D., "Network Time Protocol (v3)", RFC 1305, April 1992./
/
/
/
Almes, et al. Standards Track [Page 18]/
/
/
RFC 2681 Round-trip for Delay Metric for IPPM September 1999/
/
/
[4] Mahdavi, J. and V. Paxson, "IPPM Metrics for Measuring/
Connectivity", RFC 2678, September 1999./
/
[5] Postel, J., "Internet Protocol", STD 5, RFC 791, September 1981./
/
[6] Bradner, S., "Key words for use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
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
Note: This form is based on Recommendation ITU-T A.5