draft-ietf-ecrit-data-only-ea-09.txt   draft-ietf-ecrit-data-only-ea-10.txt 
ECRIT B. Rosen ECRIT B. Rosen
Internet-Draft NeuStar, Inc. Internet-Draft NeuStar, Inc.
Intended status: Standards Track H. Schulzrinne Intended status: Standards Track H. Schulzrinne
Expires: April 30, 2015 Columbia U. Expires: February 12, 2016 Columbia U.
H. Tschofenig H. Tschofenig
Nokia Siemens Networks August 11, 2015
October 27, 2014
Data-Only Emergency Calls Data-Only Emergency Calls
draft-ietf-ecrit-data-only-ea-09.txt draft-ietf-ecrit-data-only-ea-10.txt
Abstract Abstract
RFC 6443 'Framework for Emergency Calling Using Internet Multimedia' RFC 6443 'Framework for Emergency Calling Using Internet Multimedia'
describes how devices use the Internet to place emergency calls and describes how devices use the Internet to place emergency calls and
how Public Safety Answering Points (PSAPs) can handle Internet how Public Safety Answering Points (PSAPs) can handle Internet
multimedia emergency calls natively. The exchange of multimedia multimedia emergency calls natively. The exchange of multimedia
traffic typically involves a SIP session establishment starting with traffic typically involves a SIP session establishment starting with
a SIP INVITE that negotiates various parameters for that session. a SIP INVITE that negotiates various parameters for that session.
skipping to change at page 1, line 47 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 30, 2015. This Internet-Draft will expire on February 12, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 15, line 40 skipping to change at page 15, line 40
</presence> </presence>
--boundary1-- --boundary1--
Figure 4: Example Message conveying an Alert to a PSAP Figure 4: Example Message conveying an Alert to a PSAP
10. Security Considerations 10. Security Considerations
This section discusses security considerations when SIP user agents This section discusses security considerations when SIP user agents
issue emergency alerts utilizing MESSAGE and CAP. Location specific issue emergency alerts utilizing MESSAGE and CAP. Location specific
threats are not unique to this document and are discussed in threats are not unique to this document and are discussed in
[I-D.ietf-ecrit-trustworthy-location] and [RFC6442]. [RFC7378] and [RFC6442].
The ECRIT emergency services architecture [RFC6443] considers The ECRIT emergency services architecture [RFC6443] considers
classical individual-to-authority emergency calling and the identity classical individual-to-authority emergency calling and the identity
of the emergency caller does not play a role at the time of the call of the emergency caller does not play a role at the time of the call
establishment itself, i.e., a response to the emergency call will not establishment itself, i.e., a response to the emergency call will not
depend on the identity of the caller. In case of emergency alerts depend on the identity of the caller. In case of emergency alerts
generated by devices, like sensors, the processing may be different generated by devices, like sensors, the processing may be different
in order to reduce the number of falsely generated emergency alerts. in order to reduce the number of falsely generated emergency alerts.
Alerts may get triggered based on certain sensor input that may have Alerts may get triggered based on certain sensor input that may have
been caused by other factors than the actual occurrence of an alert been caused by other factors than the actual occurrence of an alert
skipping to change at page 20, line 39 skipping to change at page 20, line 39
13.1. Normative References 13.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", March 1997. Requirement Levels", March 1997.
[cap] Jones, E. and A. Botterell, "Common Alerting Protocol v. [cap] Jones, E. and A. Botterell, "Common Alerting Protocol v.
1.1", October 2005. 1.1", October 2005.
[RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource [RFC2392] Levinson, E., "Content-ID and Message-ID Uniform Resource
Locators", RFC 2392, August 1998. Locators", RFC 2392, DOI 10.17487/RFC2392, August 1998,
<http://www.rfc-editor.org/info/rfc2392>.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. DOI 10.17487/RFC3261, June 2002,
<http://www.rfc-editor.org/info/rfc3261>.
[RFC3428] Campbell, B., Rosenberg, J., Schulzrinne, H., Huitema, C., [RFC3428] Campbell, B., Ed., Rosenberg, J., Schulzrinne, H.,
and D. Gurle, "Session Initiation Protocol (SIP) Extension Huitema, C., and D. Gurle, "Session Initiation Protocol
for Instant Messaging", RFC 3428, December 2002. (SIP) Extension for Instant Messaging", RFC 3428, DOI
10.17487/RFC3428, December 2002,
<http://www.rfc-editor.org/info/rfc3428>.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/
RFC5234, January 2008,
<http://www.rfc-editor.org/info/rfc5234>.
[RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", RFC 3023, January 2001. Types", RFC 3023, DOI 10.17487/RFC3023, January 2001,
<http://www.rfc-editor.org/info/rfc3023>.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003. 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November
2003, <http://www.rfc-editor.org/info/rfc3629>.
[RFC6442] Polk, J., Rosen, B., and J. Peterson, "Location Conveyance [RFC6442] Polk, J., Rosen, B., and J. Peterson, "Location Conveyance
for the Session Initiation Protocol", RFC 6442, December for the Session Initiation Protocol", RFC 6442, DOI
2011. 10.17487/RFC6442, December 2011,
<http://www.rfc-editor.org/info/rfc6442>.
[RFC6881] Rosen, B. and J. Polk, "Best Current Practice for [RFC6881] Rosen, B. and J. Polk, "Best Current Practice for
Communications Services in Support of Emergency Calling", Communications Services in Support of Emergency Calling",
BCP 181, RFC 6881, March 2013. BCP 181, RFC 6881, DOI 10.17487/RFC6881, March 2013,
<http://www.rfc-editor.org/info/rfc6881>.
[I-D.ietf-ecrit-additional-data] [I-D.ietf-ecrit-additional-data]
Randy, R., Rosen, B., Tschofenig, H., Marshall, R., and J. Gellens, R., Rosen, B., Tschofenig, H., Marshall, R., and
Winterbottom, "Additional Data related to an Emergency J. Winterbottom, "Additional Data Related to an Emergency
Call", draft-ietf-ecrit-additional-data-24 (work in Call", draft-ietf-ecrit-additional-data-33 (work in
progress), October 2014. progress), July 2015.
[I-D.rosen-ecrit-addldata-subnot] [I-D.rosen-ecrit-addldata-subnot]
Rosen, B., "Updating Additional Data related to an Rosen, B., "Updating Additional Data related to an
Emergency Call using Subscribe/ Notify", draft-rosen- Emergency Call using Subscribe/ Notify", draft-rosen-
ecrit-addldata-subnot-01 (work in progress), November ecrit-addldata-subnot-01 (work in progress), November
2013. 2013.
13.2. Informative References 13.2. Informative References
[I-D.ietf-ecrit-trustworthy-location] [RFC7378] Tschofenig, H., Schulzrinne, H., and B. Aboba, Ed.,
Tschofenig, H., Schulzrinne, H., and B. Aboba, "Trustworthy Location", RFC 7378, DOI 10.17487/RFC7378,
"Trustworthy Location", draft-ietf-ecrit-trustworthy- December 2014, <http://www.rfc-editor.org/info/rfc7378>.
location-14 (work in progress), July 2014.
[RFC4474] Peterson, J. and C. Jennings, "Enhancements for [RFC4474] Peterson, J. and C. Jennings, "Enhancements for
Authenticated Identity Management in the Session Authenticated Identity Management in the Session
Initiation Protocol (SIP)", RFC 4474, August 2006. Initiation Protocol (SIP)", RFC 4474, DOI 10.17487/
RFC4474, August 2006,
<http://www.rfc-editor.org/info/rfc4474>.
[RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private [RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private
Extensions to the Session Initiation Protocol (SIP) for Extensions to the Session Initiation Protocol (SIP) for
Asserted Identity within Trusted Networks", RFC 3325, Asserted Identity within Trusted Networks", RFC 3325, DOI
November 2002. 10.17487/RFC3325, November 2002,
<http://www.rfc-editor.org/info/rfc3325>.
[RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton, [RFC6443] Rosen, B., Schulzrinne, H., Polk, J., and A. Newton,
"Framework for Emergency Calling Using Internet "Framework for Emergency Calling Using Internet
Multimedia", RFC 6443, December 2011. Multimedia", RFC 6443, DOI 10.17487/RFC6443, December
2011, <http://www.rfc-editor.org/info/rfc6443>.
Authors' Addresses Authors' Addresses
Brian Rosen Brian Rosen
NeuStar, Inc. NeuStar, Inc.
470 Conrad Dr 470 Conrad Dr
Mars, PA 16046 Mars, PA 16046
US US
Email: br@brianrosen.net Email: br@brianrosen.net
skipping to change at page 22, line 27 skipping to change at page 22, line 44
Department of Computer Science Department of Computer Science
450 Computer Science Building 450 Computer Science Building
New York, NY 10027 New York, NY 10027
US US
Phone: +1 212 939 7004 Phone: +1 212 939 7004
Email: hgs+ecrit@cs.columbia.edu Email: hgs+ecrit@cs.columbia.edu
URI: http://www.cs.columbia.edu URI: http://www.cs.columbia.edu
Hannes Tschofenig Hannes Tschofenig
Nokia Siemens Networks Hall in Tirol 6060
Linnoitustie 6 Austria
Espoo 02600
Finland
Phone: +358 (50) 4871445 Email: Hannes.tschofenig@gmx.net
Email: Hannes.Tschofenig@gmx.net
URI: http://www.tschofenig.priv.at URI: http://www.tschofenig.priv.at
 End of changes. 21 change blocks. 
37 lines changed or deleted 46 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/