Skip to main content

Minimal GSTN address format in Internet Mail

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3191.
Author Claudio Allocchio
Last updated 2013-03-02 (Latest revision 2001-06-27)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Draft Standard
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3191 (Draft Standard)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3191

        Title:      Minimal GSTN address format in Internet Mail
        Author(s):  C. Allocchio
        Status:     Standards Track
        Date:       October 2001
        Pages:      13
        Characters: 24235
        Obsoletes:  2303
        Updates:    2846

        I-D Tag:    draft-ietf-fax-minaddr-v2-04.txt


This memo describes a simple method of encoding Global Switched
Telephone Network (GSTN) addresses (commonly called "telephone
numbers") in the local-part of Internet email addresses, along with an
extension mechanism to allow encoding of additional standard
attributes needed for email gateways to GSTN-based services.

This document is a product of the Internet Fax Working Group of the

This is now a Draft 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

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.