The tel URI for Telephone Numbers
RFC 3966

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>, 
    iptel mailing list <iptel@ietf.org>, 
    iptel chair <iptel-chairs@tools.ietf.org>
Subject: Protocol Action: 'The tel URI for Telephone Numbers' to 
         Proposed Standard 

The IESG has approved the following document:

- 'The tel URI for Telephone Numbers '
   <draft-ietf-iptel-rfc2806bis-10.txt> as a Proposed Standard

This document is the product of the IP Telephony Working Group. 

The IESG contact persons are Jon Peterson and Cullen Jennings.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-iptel-rfc2806bis-10.txt

Technical Summary
 
This document defines a "tel" URI scheme for telephone numbers and thereby 
revises the original definition given in RFC2806. This revision eliminates all 
vestiges of "dial string" usage of the tel URI in favor of a model where a tel 
URI is always a globally unique identifier. It also clarifies the use of tel 
URIs as the user portion of SIP URIs.
 
Working Group Summary
 
The IPTEL working group supported this revision to RFC2806.
 
Protocol Quality
 
This document was reviewed for the IESG by Jon Peterson.

RFC Editor Note:
Section 3, 2nd paragraph:

OLD:

   If the reserved characters
   "+", ";", "=", and "?" are used as delimiters between components of
   the "tel" URI, they MUST NOT percent-encoded. 

NEW:

   If the reserved characters
   "+", ";", "=", and "?" are used as delimiters between components of
   the "tel" URI, they MUST NOT be percent-encoded. 
                                ^^