ecrit B. Rosen
Internet-Draft Neustar, Inc
Intended status: Informational December 16, 2016
Expires: June 19, 2017
A Subregistry for urn:service:sos.police, fire and ambulance
draft-rosen-ecrit-service-urn-subregistries-00
Abstract
In most countries, there are multiple kinds of police forces.
RFC5031 defines a "Service URN" which is used to route emergency
calls. The urn has a sub registry for different kinds of emergency
services that may be reached from different telephone numbers or
service numbers (as opposed to a single number like 112). In many
countries, the "police" service is not a single service, but more
than one service where the service area and/or types of emergencies
they respond to are different. In some countries there are multiple
ambulance services. This document defines sub registries for
urn:service:sos.police, urn:service:sos.ambulance and, for
completeness, urn:service:sos.fire. It also provides an initial set
of entries for these sub registries. These services are in addition
to the base urn:service:sos.police, etc. services.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 19, 2017.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
Rosen Expires June 19, 2017 [Page 1]
Internet-Draft Police/Fire/Ambulance Subregistries December 2016
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2
1.1. Police Force Types . . . . . . . . . . . . . . . . . . . 2
1.2. Ambulance Types . . . . . . . . . . . . . . . . . . . . . 3
1.3. Fire Types . . . . . . . . . . . . . . . . . . . . . . . 4
2. Security Considerations . . . . . . . . . . . . . . . . . . . 4
3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
4. Normative References . . . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
1. IANA Considerations
1.1. Police Force Types
This document extends the urn:service:sos.police to allow the type of
police force. The type of force is a token separated from
urn:service.sos.police by a period. The token names are suggestive
of the names for different kinds of police forces but is not supposed
to be the literal name of the force.
IANA is requested to add a sub registry to the Service URN Labels
under sos Sub-Services entitled sos.police Sub-Services. The
registry should have Service, Description and References as in the
other sub registries for the service urn. The Registration Procedure
is Expert review. The expert shall use the same criteria as the
other urn:service:sos entries. The initial values of the sub
registry are:
Rosen Expires June 19, 2017 [Page 2]
Internet-Draft Police/Fire/Ambulance Subregistries December 2016
+------------+-----------+------------------------------------------+
| Service | Reference | Description |
+------------+-----------+------------------------------------------+
| federal | this | A police force serving an entire nation |
| | document | |
| | | |
| provincial | this | A police force serving a province or |
| | document | state |
| | | |
| county | this | A police force serving a county |
| | document | |
| | | |
| municipal | this | A police force serving a city, town or |
| | document | other incorporated municipality |
+------------+-----------+------------------------------------------+
Table 1: urn:service:sos.police sub registry initial contents
1.2. Ambulance Types
This document extends the urn:service:sos.ambulance to allow the type
of ambulance. The type of service is a token separated from
urn:service.sos.ambulance by a period. The token names are
suggestive of the names for different kinds of ambulance services but
is not supposed to be the literal name of the service.
IANA is requested to add a sub registry to the Service URN Labels
under sos Sub-Services entitled sos.ambulance Sub-Services. The
registry should have Service, Description and References as in the
other sub registries for the service urn. The Registration Procedure
is Expert review. The expert shall use the same criteria as the
other urn:service:sos entries. The initial values of the sub
registry are:
+---------+------------+--------------------------------------------+
| Service | Reference | Description |
+---------+------------+--------------------------------------------+
| public | this | An ambulance service that is operated by a |
| | document | government agency |
| | | |
| private | this | An ambulance service that is operated by a |
| | document | private company |
| | | |
| air | this | An ambulance service that uses a |
| | document | helicopter or airplane |
+---------+------------+--------------------------------------------+
Table 2: urn:service:sos.ambulance sub registry initial contents
Rosen Expires June 19, 2017 [Page 3]
Internet-Draft Police/Fire/Ambulance Subregistries December 2016
1.3. Fire Types
This document extends the urn:service:sos.fire to allow the type of
fire service. The type of service is a token separated from
urn:service.sos.fire by a period. The token names are suggestive of
the names for different kinds of fire services but is not supposed to
be the literal name of the service.
IANA is requested to add a sub registry to the Service URN Labels
under sos Sub-Services entitled sos.fire Sub-Services. The registry
should have Service, Description and References as in the other sub
registries for the service urn. The Registration Procedure is Expert
review. The expert shall use the same criteria as the other
urn:service:sos entries. The initial values of the sub registry are:
+----------+-----------+--------------------------------------------+
| Service | Reference | Description |
+----------+-----------+--------------------------------------------+
| wildfire | this | A fire service that specializes in wild |
| | document | fires, for example, forest fires |
+----------+-----------+--------------------------------------------+
Table 3: urn:service:sos.fire sub registry initial contents
2. Security Considerations
This document has the same security considerations as those in
[RFC5031].
3. Acknowledgements
Ivo Sedlacek described the problem and attempted to register a
service with a specific police force as distinct from
urn:service:sos.police. This work was inspired by his problem.
4. Normative References
[RFC5031] Schulzrinne, H., "A Uniform Resource Name (URN) for
Emergency and Other Well-Known Services", RFC 5031,
DOI 10.17487/RFC5031, January 2008,
<http://www.rfc-editor.org/info/rfc5031>.
Author's Address
Rosen Expires June 19, 2017 [Page 4]
Internet-Draft Police/Fire/Ambulance Subregistries December 2016
Brian Rosen
Neustar, Inc
470 Conrad Dr
Mars, PA 16046
US
Phone: +1 724-382-1051
Email: br@brianrosen.net
Rosen Expires June 19, 2017 [Page 5]