draft-ietf-ecrit-data-only-ea-12.txt   draft-ietf-ecrit-data-only-ea-13.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: January 19, 2017 Columbia U. Expires: January 20, 2017 Columbia U.
H. Tschofenig H. Tschofenig
ARM Limited ARM Limited
R. Gellens R. Gellens
July 18, 2016 July 19, 2016
Data-Only Emergency Calls Data-Only Emergency Calls
draft-ietf-ecrit-data-only-ea-12.txt draft-ietf-ecrit-data-only-ea-13.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) handle Internet multimedia how Public Safety Answering Points (PSAPs) handle Internet multimedia
emergency calls natively. The exchange of multimedia traffic for emergency calls natively. The exchange of multimedia traffic for
emergency services involves a SIP session establishment starting with emergency services 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 48 skipping to change at page 1, line 48
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 January 19, 2017. This Internet-Draft will expire on January 20, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
skipping to change at page 16, line 43 skipping to change at page 16, line 43
An entity that has already received a CAP message within the An entity that has already received a CAP message within the
indicated timeframe is able to detect a replayed message and, if the indicated timeframe is able to detect a replayed message and, if the
content of that message is unchanged, then no additional security content of that message is unchanged, then no additional security
vulnerability is created. Additionally, it is RECOMMENDED to make vulnerability is created. Additionally, it is RECOMMENDED to make
use of SIP security mechanisms, such as SIP Identity [RFC4474], to use of SIP security mechanisms, such as SIP Identity [RFC4474], to
tie the CAP message to the SIP message. To provide protection of the tie the CAP message to the SIP message. To provide protection of the
entire SIP message exchange between neighboring SIP entities, the entire SIP message exchange between neighboring SIP entities, the
usage of TLS is MANDATORY. usage of TLS is MANDATORY.
Note that none of the security mechanism in this document protect Note that none of the security mechanism in this document protect
against a compromised sensor sending crafted alerts. against a compromised sensor sending crafted alerts. Privacy
provided for any emergency calls, including data-only messages, is
subject to local regulations.
10. IANA Considerations 10. IANA Considerations
10.1. Registration of the 'application/EmergencyCallData.cap+xml' MIME 10.1. Registration of the 'application/EmergencyCallData.cap+xml' MIME
type type
To: ietf-types@iana.org To: ietf-types@iana.org
Subject: Registration of MIME media type application/ Subject: Registration of MIME media type application/
EmergencyCallData.cap+xml EmergencyCallData.cap+xml
 End of changes. 5 change blocks. 
5 lines changed or deleted 7 lines changed or added

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