RFC 2806 on URLs for Telephone Calls

RFC Editor <rfc-ed@ISI.EDU> Fri, 28 April 2000 22:17 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13046; Fri, 28 Apr 2000 18:17:10 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id SAA08577 for ietf-123-outbound.10@ietf.org; Fri, 28 Apr 2000 18:15:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA08553 for <all-ietf@loki.ietf.org>; Fri, 28 Apr 2000 18:10:40 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13002 for <all-ietf@ietf.org>; Fri, 28 Apr 2000 18:10:38 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id PAA14033; Fri, 28 Apr 2000 15:10:39 -0700 (PDT)
Message-Id: <200004282210.PAA14033@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2806 on URLs for Telephone Calls
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 28 Apr 2000 15:10:39 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2806

        Title:	    URLs for Telephone Calls
        Author(s):  A. Vaha-Sipila
        Status:     Standards Track
	Date:       April 2000
        Mailbox:    avs@iki.fi, antti.vaha-sipila@nokia.com
        Pages:      21
        Characters: 50647
        Updates/Obsoletes/SeeAlso: None    

        I-D Tag:    draft-antti-telephony-url-12.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2806.txt


This document specifies URL (Uniform Resource Locator) schemes
"tel", "fax" and "modem" for specifying the location of a
terminal in the phone network and the connection types (modes of
operation) that can be used to connect to that entity. This
specification covers voice calls (normal phone calls, answering
machines and voice messaging systems), facsimile (telefax) calls and
data calls, both for POTS and digital/mobile subscribers.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc2806.txt"><ftp://ftp.isi.edu/in-notes/rfc2806.txt>