Internet-Draft submission
Submission status: Cancelled
This submission has been cancelled, modification is no longer possible.
Submission checks
Your Internet-Draft has been verified to pass the submission checks.
Meta-data from the submission
Note: The meta-data shown for a cancelled draft may be incorrect or incomplete.
Document | draft-ietf-ecrit-data-only-ea |
---|---|
Revision | 19 |
Group | Emergency Context Resolution with Internet Technologies (ECRIT) |
Document date | 2020-03-09 |
Submission date | 2020-03-09 |
Title | Non-Interactive Emergency Calls |
Author count | 4 authors |
Author 1 |
Brian Rosen
<br@brianrosen.net>
unknown affiliation US (understood to be United States of America) |
Author 2 |
Henning Schulzrinne
<hgs+ecrit@cs.columbia.edu>
Columbia University US (understood to be United States of America) |
Author 3 |
Hannes Tschofenig
<Hannes.Tschofenig@gmx.net>
ARM Limited Austria |
Author 4 |
Randall Gellens
<rg+ietf@coretechnologyconsulting.com>
Core Technology Consulting unknown country |
Abstract |
Use of the Internet for emergency calling is described in RFC 6443, 'Framework for Emergency Calling Using Internet Multimedia'. In some cases of emergency calls, the transmission of application data is all that is needed and no interactive media channel is established: a situation referred to as 'non-interactive emergency calls', where, unlike most emergency calls, there is no two way interactive media such as voice or video or text. This document describes use of a SIP MESSAGE transaction that includes a container for the data based on the Common Alerting Protocol (CAP). That type of emergency request does not establish a session, distinguishing it from SIP INVITE, which does. Any device that needs to initiate a request for emergency services without an interactive media channel would use the mechanisms in this document. |
Page count | 24 |
File size | 52.1 KB |
Formal languages used | ABNF, XML |
Submission additional resources | None |
Submitter information
Name | Brian Rosen |
---|---|
Email address | br@brianrosen.net |
History
Date | By | Event |
---|---|---|
2020-12-28 | Mostafa Shahdadi | Cancelled submission |
2020-11-26 | Sent full access URL to: Brian Rosen <br@brianrosen.net>, Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, Randall Gellens <rg+ietf@coretechnologyconsulting.com>, Henning Schulzrinne <hgs+ecrit@cs.columbia.edu> | |
2020-09-19 | Sent full access URL to: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, Randall Gellens <rg+ietf@coretechnologyconsulting.com>, Henning Schulzrinne <hgs+ecrit@cs.columbia.edu>, Brian Rosen <br@brianrosen.net> | |
2020-09-19 | Sent full access URL to: Henning Schulzrinne <hgs+ecrit@cs.columbia.edu>, Randall Gellens <rg+ietf@coretechnologyconsulting.com>, Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, Brian Rosen <br@brianrosen.net> | |
2020-09-19 | Sent full access URL to: Henning Schulzrinne <hgs+ecrit@cs.columbia.edu>, Randall Gellens <rg+ietf@coretechnologyconsulting.com>, Brian Rosen <br@brianrosen.net>, Hannes Tschofenig <Hannes.Tschofenig@gmx.net> | |
2020-09-01 | Sent full access URL to: Randall Gellens <rg+ietf@coretechnologyconsulting.com>, Brian Rosen <br@brianrosen.net>, Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, Henning Schulzrinne <hgs+ecrit@cs.columbia.edu> | |
2020-07-25 | Sent full access URL to: Henning Schulzrinne <hgs+ecrit@cs.columbia.edu>, Brian Rosen <br@brianrosen.net>, Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, Randall Gellens <rg+ietf@coretechnologyconsulting.com> | |
2020-07-17 | Sent full access URL to: Henning Schulzrinne <hgs+ecrit@cs.columbia.edu>, Randall Gellens <rg+ietf@coretechnologyconsulting.com>, Brian Rosen <br@brianrosen.net>, Hannes Tschofenig <Hannes.Tschofenig@gmx.net> | |
2020-03-28 | Sent full access URL to: Henning Schulzrinne <hgs+ecrit@cs.columbia.edu>, Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, Brian Rosen <br@brianrosen.net>, Randall Gellens <rg+ietf@coretechnologyconsulting.com> | |
2020-03-09 | Edited rev, abstract, note, submitter, authors and sent request for manual post | |
2020-03-09 | Uploaded submission |
Please send reports about submission tool bugs to the Tools Team using one
of the Bug Report links at the bottom of the page.
If you run into problems submitting an Internet-Draft and need to request manual posting of an Internet-Draft, please send the Internet-Draft and the reason for manual posting to support@ietf.org. Be advised that manual processing always takes additional time.
If you run into problems submitting an Internet-Draft and need to request manual posting of an Internet-Draft, please send the Internet-Draft and the reason for manual posting to support@ietf.org. Be advised that manual processing always takes additional time.