Service URN Labels

Created

• 2007-08-22

Last Updated

• 2017-05-15

Note

The policy for adding top-level service labels is 'Standards Action'. The policy for assigning labels to sub-services may differ for each top-level service designation and MUST be defined by the document describing the top-level service.

To allow use within the constraints of S-NAPTR [ref], all top-level service names MUST NOT exceed 27 characters.

Available Formats

• XML
• HTML
• TXT

URN Service Labels

Registration Procedure(s)

• Standards Action

Reference

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

Available Formats

• CSV

'sos' Sub-Services

Registration Procedure(s)

• Expert Review

Expert(s)

• ECRIT working group, its successor, or, in their absence, the IESG.

Reference

• RFC 7163: URN for Country-Specific Emergency Services

Available Formats

• CSV

'counseling' Sub-Services

Registration Procedure(s)

• Expert Review

Expert(s)

• ECRIT working group, its successor, or, in their absence, the IESG.

Reference

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

Available Formats

• CSV

'test' Sub-Services

Registration Procedure(s)

• Expert Review

Expert(s)

• Brian Rosen

Reference

• RFC 6881: Best Current Practice for Communications Services in Support of Emergency Calling

Available Formats

• CSV