|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 4542 (2006)
|
|
Title:
|
Implementing an Emergency Telecommunications Service (ETS) for Real-Time Services in the Internet Protocol Suite.
|
|
|
2.
|
Status of approval:
|
|
|
Approved as an Informational document.
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Recommendation Y.NGN-ET-Tech refers to IETF RFC 4542 for describing possible solutions for the Internet Emergency Preference Service..
|
|
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=4542
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The status of IETF RFC 4542 is "Informational". Current status of these documents can be found at http://www.ietf.org/iesg/1rfc_index.txt.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The status of IETF RFC 4542 is "Informational". Current status of these documents can be found at http://www.ietf.org/iesg/1rfc_index.txt.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
/
[RFC3689] Carlberg, K. and R. Atkinson, "General Requirements/
for Emergency Telecommunication Service (ETS)", RFC/
3689, February 2004./
/
[RFC3690] Carlberg, K. and R. Atkinson, "IP Telephony/
Requirements for Emergency Telecommunication/
Service (ETS)", RFC 3690, February 2004./
/
[RFC1633] Braden, B., Clark, D., and S. Shenker, "Integrated/
Services in the Internet Architecture: an/
Overview", RFC 1633, June 1994./
/
[RFC2205] Braden, B., Zhang, L., Berson, S., Herzog, S., and/
S. Jamin, "Resource ReSerVation Protocol (RSVP) --/
Version 1 Functional Specification", RFC 2205,/
September 1997./
/
[RFC2207] Berger, L. and T. O'Malley, "RSVP Extensions for/
IPSEC Data Flows", RFC 2207, September 1997./
/
[RFC2208] Mankin, A., Baker, F., Braden, B., Bradner, S.,/
O'Dell, M., Romanow, A., Weinrib, A., and L. Zhang,/
"Resource ReSerVation Protocol (RSVP) Version 1/
Applicability Statement Some Guidelines on/
Deployment", RFC 2208, September 1997./
/
[RFC2209] Braden, B. and L. Zhang, "Resource ReSerVation/
Protocol (RSVP) -- Version 1 Message Processing/
Rules", RFC 2209, September 1997./
/
[RFC2746] Terzis, A., Krawczyk, J., Wroclawski, J., and L./
Zhang, "RSVP Operation Over IP Tunnels", RFC 2746,/
January 2000./
/
[RFC2747] Baker, F., Lindell, B., and M. Talwar, "RSVP/
Cryptographic Authentication", RFC 2747, January/
2000./
/
[RFC2750] Herzog, S., "RSVP Extensions for Policy Control",/
RFC 2750, January 2000./
/
[RFC2753] Yavatkar, R., Pendarakis, D., and R. Guerin, "A/
Framework for Policy-based Admission Control", RFC/
2753, January 2000./
/
[RFC2996] Bernet, Y., "Format of the RSVP DCLASS Object", RFC/
2996, November 2000./
/
[RFC2998] Bernet, Y., Ford, P., Yavatkar, R., Baker, F.,/
Zhang, L., Speer, M., Braden, R., Davie, B.,/
Wroclawski, J., and E. Felstaine, "A Framework for/
Integrated Services Operation over Diffserv/
Networks", RFC 2998, November 2000./
/
[RFC3097] Braden, R. and L. Zhang, "RSVP Cryptographic/
Authentication -- Updated Message Type Value", RFC/
3097, April 2001./
/
[RFC3175] Baker, F., Iturralde, C., Le Faucheur, F., and B./
Davie, "Aggregation of RSVP for IPv4 and IPv6/
Reservations", RFC 3175, September 2001./
/
[RFC3181] Herzog, S., "Signaled Preemption Priority Policy/
Element", RFC 3181, October 2001./
/
[RFC3182] Yadav, S., Yavatkar, R., Pabbati, R., Ford, P.,/
Moore, T., Herzog, S., and R. Hess, "Identity/
Representation for RSVP", RFC 3182, October 2001./
/
[RFC3312] Camarillo, G., Marshall, W., and J. Rosenberg,/
"Integration of Resource Management and Session/
Initiation Protocol (SIP)", RFC 3312, October 2002./
/
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,/
"Definition of the Differentiated Services Field/
(DS Field) in the IPv4 and IPv6 Headers", RFC 2474,/
December 1998./
/
[RFC2475] Blake, S., Black, D., Carlson, M., Davies, E.,/
Wang, Z., and W. Weiss, "An Architecture for/
Differentiated Services", RFC 2475, December 1998./
/
[RFC2983] Black, D., "Differentiated Services and Tunnels",/
RFC 2983, October 2000./
/
[RFC3246] Davie, B., Charny, A., Bennet, J., Benson, K., Le/
Boudec, J., Courtney, W., Davari, S., Firoiu, V.,/
and D. Stiliadis, "An Expedited Forwarding PHB/
(Per-Hop Behavior)", RFC 3246, March 2002./
/
[RFC3247] Charny, A., Bennet, J., Benson, K., Boudec, J.,/
Chiu, A., Courtney, W., Davari, S., Firoiu, V.,/
Kalmanek, C., and K. Ramakrishnan, "Supplemental/
Information for the New Definition of the EF PHB/
(Expedited Forwarding Per-Hop Behavior)", RFC 3247,/
March 2002./
/
[RFC2327] Handley, M. and V. Jacobson, "SDP: Session/
Description Protocol", RFC 2327, April 1998./
/
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G.,/
Johnston, A., Peterson, J., Sparks, R., Handley,/
M., and E. Schooler, "SIP: Session Initiation/
Protocol", RFC 3261, June 2002./
/
[RFC4411] Polk, J., "Extending the Session Initiation/
Protocol (SIP) Reason Header for Preemption/
Events", RFC 4411, February 2006./
/
[RFC4412] Schulzrinne, H. and J. Polk, "Communications/
Resource Priority for the Session Initiation/
Protocol (SIP)", RFC 4412, February 2006./
/
Informative References/
/
[ANSI.MLPP.Spec] American National Standards Institute,/
"Telecommunications - Integrated Services Digital/
Network (ISDN) - Multi-Level Precedence and/
Preemption (MLPP) Service Capability", ANSI/
T1.619-1992 (R1999), 1992./
/
[ANSI.MLPP.Supp] American National Standards Institute, "MLPP/
Service Domain Cause Value Changes", ANSI ANSI/
T1.619a-1994 (R1999), 1990./
/
[G711.1] Viola Networks, "Netally VoIP Evaluator", January/
2003, http://www.brainworks.de/Site/hersteller//
viola_networks/Dokumente/Compr_Report_Sample.pdf./
/
[G711.3] Nortel Networks, "Packet Loss and Packet Loss/
Concealment", 2000, http://www.nortelnetworks.com//
products/01/succession/es/collateral//
tb_pktloss.pdf./
/
[ITU.ETS.E106] International Telecommunications Union,/
"International Emergency Preference Scheme for/
disaster relief operations (IEPS)", ITU-T/
Recommendation E.106, October 2003./
/
[ITU.MLPP.1990] International Telecommunications Union, "Multilevel/
Precedence and Preemption Service (MLPP)", ITU-T/
Recommendation I.255.3, 1990./
/
[Parekh1] Parekh, A. and R. Gallager, "A Generalized/
Processor Sharing Approach to Flow Control in/
Integrated Services Networks: The Multiple Node/
Case", INFOCOM 1993: 521-530, 1993./
/
[Parekh2] Parekh, A. and R. Gallager, "A Generalized/
Processor Sharing Approach to Flow Control in/
Integrated Services Networks: The Single Node/
Case", INFOCOM 1992: 915-924, 1992./
|
|
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):
|
|
|
References should always be made to RFC numbers (and not by other designations such as STD, BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.
|
|
