UpdatedPROPOSED STANDARDIETF stream

RFC 5031: A Uniform Resource Name (URN) for Emergency and Other Well-Known Services

Still current, but amended. Parts of this document are changed or extended by RFC 7163. Read both.

In plain English — editorial summary, not part of the RFC

The content of many communication services depends on the context, such as the user's location. We describe a 'service' URN that allows well-known context-dependent services that can be resolved in a distributed manner to be identified. Examples include emergency services, directory assistance, and call-before-you-dig hot lines. [STANDARDS-TRACK]

Document record

Document ID
RFC5031
Published
January 2008
Authors
H. Schulzrinne
Status
PROPOSED STANDARD
Stream
IETF
Area
art
Pages
14
Also known as
Updated by:
RFC 7163

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/5031-a-uniform-resource-name-urn-for-emergency-and-other-well-known-services