Committed to connecting the world

  •  
wtisd

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : H.810     
  ITU-T A.5 justification information for referenced document IETF RFC 2988 (2000) in draft H.810
1. Clear description of the referenced document:
Name: IETF RFC 2988 (2000)
Title: Computing TCP's Retransmission Timer
2. Status of approval:
Standards track RFC approved November 2000. Obsoleted by RFC 6298.
3. Justification for the specific reference:
H.810 requires the use of this RFC, Computing TCP's Retransmission Timer, for the codification of the algorithm used for setting the Retransmission Timeout (RTO) over the WAN Interface. The RTO ensures data delivery in the absence of any feedback from the remote data WAN receiver utilized within Continua's architecture. There is also dependency on the use of this spec across other IHE and HL7 that also use this specification. Additionally, many H.810 certified devices exist that use this version of the RFC.
4. Current information, if any, about IPR issues:
N/A.
5. Other useful information describing the "Quality" of the document:
Specification approved November 2000. Obsoleted by RFC 6298. Errata exist.
6. The degree of stability or maturity of the document:
Specification approved November, 2000 and has been widely used.
7. Relationship with other existing or emerging documents:
It expands on the discussion in section 4.2.3.1 of RFC 1122 and upgrades the requirement of supporting the algorithm from a SHOULD to a MUST.
8. Any explicit references within that referenced document should also be listed:
[AP99] Allman, M. and V. Paxson, "On Estimating End-to-End Network Path Properties", SIGCOMM 99./
/
[APS99] Allman, Paxson V. and W. Stevens, "TCP Congestion Control", RFC 2581, April 1999./
/
[Bra89] Braden, R., "Requirements for Internet Hosts -- Communication Layers", STD 3, RFC 1122, October 1989./
/
[Bra97] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[Jac88] Jacobson, V., "Congestion Avoidance and Control", Computer Communication Review, vol. 18, no. 4, pp. 314-329, Aug. 1988./
/
[JK88] Jacobson, V. and M. Karels, "Congestion Avoidance and Control", ftp://ftp.ee.lbl.gov/papers/congavoid.ps.Z./
/
[KP87] Karn, P. and C. Partridge, "Improving Round-Trip Time Estimates in Reliable Transport Protocols", SIGCOMM 87./
/
[Pos81] Postel, J., "Transmission Control Protocol", STD 7, RFC 793, September 1981.
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):
N/A.
Note: This form is based on Recommendation ITU-T A.5