RFC 2846 on GSTN Address Extensions in E-mail Services
RFC Editor <rfc-ed@ISI.EDU> Thu, 08 June 2000 18:40 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13784; Thu, 8 Jun 2000 14:40:03 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id OAA13195 for ietf-123-outbound.10@ietf.org; Thu, 8 Jun 2000 14:35:02 -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 OAA13058 for <all-ietf@loki.ietf.org>; Thu, 8 Jun 2000 14:10:36 -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 OAA13290 for <all-ietf@ietf.org>; Thu, 8 Jun 2000 14:10:34 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id LAA19514; Thu, 8 Jun 2000 11:10:30 -0700 (PDT)
Message-Id: <200006081810.LAA19514@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2846 on GSTN Address Extensions in E-mail Services
Cc: rfc-ed@ISI.EDU, ietf-fax@IMC.ORG
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 08 Jun 2000 11:10:30 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2846 Title: GSTN Address Element Extensions in E-mail Services Author(s): C. Allocchio Status: Standards Track Date: June 2000 Mailbox: Claudio.Allocchio@elettra.trieste.it Pages: 35 Characters: 54316 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-fax-fulladdr-06.txt URL: ftp://ftp.isi.edu/in-notes/rfc2846.txt There are numerous applications where there is a need for interaction between the GSTN addressing and Internet addressing. This memo defines a full syntax for one specific case, where there is a need to represent GSTN addresses within Internet e-mail addresses. This full syntax is a superset of a minimal syntax which has been defined in [1]. This document is a product of the Internet Fax Working Group of the IETF. 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.