RFC 3601 on Text String Notation for Dial Sequences and Global Switched Telephone Network (GSTN) / E.164 Addresses (fwd)

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to [email protected] for more info.

--NextPart
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.OSX.4.56.0309111011502.449@mac-allocchio3.elettra.trieste.it>


FYI,

------------------------------------------------------------------------------
Claudio Allocchio             G   A   R   R          [email protected]
                        Project Technical Officer
tel: +39 040 3758523      Italian Academic and       G=Claudio; S=Allocchio;
fax: +39 040 3758565        Research Network         P=garr; A=garr; C=it;

           PGP Key: http://www.cert.garr.it/PGP/keys.php3#ca

---------- Forwarded message ----------
Date: Wed, 10 Sep 2003 10:15:00 -0700
From: [email protected]
To: IETF-Announce:  ;
Cc: [email protected]
Subject: RFC 3601 on Text String Notation for Dial Sequences and Global
    Switched Telephone Network (GSTN) / E.164 Addresses


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


        RFC 3601

        Title:      Text String Notation for Dial Sequences and
                    Global Switched Telephone Network (GSTN) /
                    E.164 Addresses
        Author(s):  C. Allocchio
        Status:     Standards Track
        Date:       September 2003
        Mailbox:    [email protected]
        Pages:      10
        Characters: 18572
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-allocchio-gstn-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3601.txt


This memo describes the full set of notations needed to represent
a text string in a Dial Sequence.  A Dial Sequence is normally
composed of Dual Tone Multi Frequency (DTMF) elements, plus
separators and additional "actions" (such as "wait for
dialtone", "pause for N secs", etc.) which could be needed to
successfully establish the connection with the target service:
this includes the cases where subaddresses or DTMF menu navigation
apply.

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 [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body
help: ways_to_get_rfcs.  For example:

        To: [email protected]
        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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
[email protected].  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.
--NextPart
Content-Type: MULTIPART/ALTERNATIVE; BOUNDARY=OtherAccess
Content-ID: <Pine.OSX.4.56.0309111011503.449@mac-allocchio3.elettra.trieste.it>
Content-Description: 

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to [email protected] for more info.

--OtherAccess
Content-Type: MESSAGE/EXTERNAL-BODY; ACCESS-TYPE=mail-server; SERVER="[email protected]"
Content-ID: <Pine.OSX.4.56.0309111011504.449@mac-allocchio3.elettra.trieste.it>

--OtherAccess
Content-Type: MESSAGE/EXTERNAL-BODY; NAME="rfc3601.txt"; SITE="ftp.isi.edu"; ACCESS-TYPE=anon-ftp; DIRECTORY=in-notes
Content-ID: <Pine.OSX.4.56.0309111011505.449@mac-allocchio3.elettra.trieste.it>

--OtherAccess--
--NextPart--