Implementing an Emergency Telecommunications Service (ETS) for Real-Time Services in the Internet Protocol Suite

RFCs 3689 and 3690 detail requirements for an Emergency Telecommunications Service (ETS), of which an Internet Emergency Preparedness Service (IEPS) would be a part. Some of these types of services require call preemption; others require call queuing or other mechanisms. IEPS requires a Call Admission Control (CAC) procedure and a Per Hop Behavior (PHB) for the data that meet the needs of this architecture. Such a CAC procedure and PHB is appropriate to any service that might use H.323 or SIP to set up real-time sessions. The key requirement is to guarantee an elevated probability of call completion to an authorized user in time of crisis. This document primarily discusses supporting ETS in the context of the US Government and NATO, because it focuses on the Multi-Level Precedence and Preemption (MLPP) and Government Emergency Telecommunication Service (GETS) standards. The architectures described here are applicable beyond these organizations. This memo provides information for the Internet community.

[1]  Lixia Zhang,et al.  RSVP Cryptographic Authentication - Updated Message Type Value , 2001, RFC.

[2]  Gonzalo Camarillo,et al.  Integration of Resource Management and Session Initiation Protocol (SIP) , 2002, RFC.

[3]  Scott O. Bradner,et al.  Resource ReSerVation Protocol (RSVP) - Version 1 Applicability Statement Some Guidelines on Deployment , 1997, RFC.

[4]  Shai Herzog,et al.  RSVP Extensions for Policy Control , 2000, RFC.

[5]  Scott Shenker,et al.  Integrated Services in the Internet Architecture : an Overview Status of this Memo , 1994 .

[6]  Shai Herzog Signaled Preemption Priority Policy Element , 2000, RFC.

[7]  Mark Handley,et al.  SDP: Session Description Protocol , 1998, RFC.

[8]  Randall J. Atkinson,et al.  IP Telephony Requirements for Emergency Telecommunication Service (ETS) , 2004, RFC.

[9]  Jean-Yves Le Boudec,et al.  An Expedited Forwarding PHB (Per-Hop Behavior) , 2002, RFC.

[10]  Lixia Zhang,et al.  Resource ReSerVation Protocol (RSVP) - Version 1 Functional Specification , 1997, RFC.

[11]  Andreas Terzis,et al.  RSVP Operation Over IP Tunnels , 2000, RFC.

[12]  David L. Black,et al.  Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers , 1998, RFC.

[13]  Henning Schulzrinne,et al.  Communications Resource Priority for the Session Initiation Protocol (SIP) , 2006, RFC.

[14]  Yoram Bernet,et al.  Format of the RSVP DCLASS Object , 2000, RFC.

[15]  K. K. Ramakrishnan,et al.  Supplemental Information for the New Definition of the EF PHB (Expedited Forwarding Per-Hop Behavior) , 2002, RFC.

[16]  Fred Baker,et al.  Network Working Group Aggregation of Rsvp for Ipv4 and Ipv6 Reservations , 2002 .

[17]  David L. Black,et al.  Differentiated Services and Tunnels , 2000, RFC.

[18]  Zheng Wang,et al.  An Architecture for Differentiated Services , 1998, RFC.

[19]  Randall J. Atkinson,et al.  General Requirements for Emergency Telecommunication Service (ETS) , 2004, RFC.

[20]  Lixia Zhang,et al.  Resource ReSerVation Protocol (RSVP) - Version 1 Message Processing Rules , 1997, RFC.

[21]  Lixia Zhang,et al.  A Framework for Integrated Services Operation over Diffserv Networks , 2000, RFC.

[22]  Roch Guérin,et al.  A Framework for Policy-based Admission Control , 2000, RFC.

[23]  James M. Polk Extending the Session Initiation Protocol (SIP) Reason Header for Preemption Events , 2006, RFC.

[24]  Fred Baker,et al.  RSVP Cryptographic Authentication , 2000, RFC.

[25]  Abhay Parekh,et al.  A generalized processor sharing approach to flow control in integrated services networks: the multiple node case , 1994, TNET.

[26]  Mark Handley,et al.  SIP: Session Initiation Protocol , 1999, RFC.

[27]  Louis Berger,et al.  RSVP Extensions for IPSEC Data Flows , 1997, RFC.

[28]  Abhay Parekh,et al.  A generalized processor sharing approach to flow control in integrated services networks: the single-node case , 1993, TNET.

[29]  Tim Moore,et al.  Identity Representation for RSVP , 2001, RFC.