As per Relevance of the word reference, we have this rfc below:
Network Working Group C.
Request for Comments: 2304 GARR-
Category: Standards Track March 1998
Minimal FAX address format in Internet
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1998). All Rights Reserved
IESG
This memo describes a simple method of encoding PSTN addresses
facsimile devices in the local-part of Internet email addresses
As with all Internet mail addresses, the left-hand-side (local- part
of an address generated according to this specification, is not to
interpreted except by the MTA that is named on the right-hand-
(domain).
1.
Since the very first e-mail to fax gateway objects appeared, a
of different methods to specify a fax address as an e-mail
have been used by implementors. Two major objectives for this
- enable an e-mail user to send faxes from his/her e-
interface
- enable some kind of "fax over e-mail service" transport,
reduce the costs of fax transmissions, and use the
e-mail infrastructure
Allocchio Standards Track [Page 1]
RFC 2304 Minimal FAX address format March 1998
This memo describes the MINIMAL addressing method and
extensions to encode FAX addresses in e-mail addresses, as
in reference [13]. The opposite problem, i.e. to allow a
numeric-only fax device user to access the e-mail transport service
is not discussed here
All implementations supporting this FAX over e-mail address
MUST support as a minimum the specification described in
document. The generic complex case of converting the whole
addressing in e-mail is out of scope in this minimal specification
there is some work in progress in the field, where also a number
standard optional extensions are being defined
In this document the formal definitions are described using
syntax, as defined into [7]. We will also use some of the "
DEFINITIONS" defined in "APPENDIX A - CORE" of that document.
exact meaning of the capitalised
"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "MAY", "OPTIONAL
is defined in reference [6].
2. Minimal Fax
The "service-selector" defined in section 2 of reference [13] for
fax service is
service-selector = "FAX
The minimal addressing for the fax service also requires support
a "qualif-type1" element (see section 2 of reference [13]).
element is an OPTIONAL element of the fax address, but its support
when present, is REQUIRED
qualif-type1 = "/" t33-sep "=" sub-
t33-sep = "T33S
sub-addr = 1*( DIGIT )
Thus, the minimal specification of a fax in e-mail address is
fax-address = fax-mbox [ "/T33S=" sub-addr ]
fax-mbox = "FAX=" global-
Allocchio Standards Track [Page 2]
RFC 2304 Minimal FAX address format March 1998
Note
See section 4.1 in case multiple sub-addr per fax-mbox need to
specified
The Minimal supported syntax for global-phone (as described
section reference [13]) is
global-phone = "+" 1*( DIGIT , written-sep )
written-sep = ( "-" / "." )
The use of other dialling schemas for PSTN numbers (like
numbering plans or local dialling conventions) is also allowed
However, this does not preclude nor remove the minimal
requirement to support the "global-phone" syntax as defined above
Any non "global-phone" dialling schema MUST NOT use the leading "+"
between the "=" sign and the dialling string. The "+" sign
strictly reserved for the standard "global-phone" syntax
Note
The specification of these different dialling schemas is out
scope for this minimal specification
User specification of PSTN e-mail addresses will be facilitated
they can insert these separators between dial elements like
etc. For this reason we allow them in the syntax the written-
element
Implementors' note
Use of the written-sep elements is allowed, but not recommended
Any occurences of written-sep elements in a pstn-mbox MUST
ignored by all conformant implementations. User Agents
remove written-sep elements before submitting messages to
Message Transport System
2.2 Some examples of a minimal "fax-address
FAX=+3940226338
FAX=+12027653000/T33S=1387
FAX=+33-1-88335215
Allocchio Standards Track [Page 3]
RFC 2304 Minimal FAX address format March 1998
3. The e-mail address of the I-fax device: mta-I-
An "I-fax device" has an e-mail address, or to be more exact, a
which enables a mail system to identify it on the e-mail
system
In Internet mail, this is the Right Hand Side (RHS) part of
address, i.e. the part on the right of the "@" sign. We will
this mta-I-
mta-I-fax =
For "domain" strings used in SMTP transmissions, the string
conform to the requirements of that standard's
specifications [1], [3]. For "domain" strings used in
content headers, the string MUST conform to the requirements of
relevant standards [2], [3].
Note: in both cases, the standards permit use of "domain names"
"domain literals" in addresses
4. The fax-
The complete structure used to transfer a minimal FAX address
the Internet e-mail transport system is called "fax-email".
object is an e-mail address which conforms to RFC822 [2] and RFC1123
[3] "addr-spec" syntax, with some extra structure which allows
FAX number to be identified
fax-email = ["/"] fax-address ["/"] "@" mta-I-
Implementors' note
The optional "/" characters can result from other mail
services gateways, where it is also an optional element
Implementations MUST accept the optional slashes but SHOULD
generate them. Gateways are allowed to strip them off
converting to Internet mail addressing
It is essential to remind that "fax-address" element MUST
follow the "quoting rules" spcified in the relevant standards [2],
[3]
4.1 Multiple
In case a particular service requires multiple T.33 subaddresses,
these subaddresses need to be given on the same "fax-mbox",
"fax-email" elements will be used
Allocchio Standards Track [Page 4]
RFC 2304 Minimal FAX address format March 1998
Implementors' note
The UA could accept multiple subaddress elements for the
global-phone, but it must generate multiple "fax-mbox"
when passing the message to the MTA
4.2 Some examples of minimal "fax-email
FAX=+3940226338@faxworld.
FAX=+12027653000/T33S=1387@faxworld.
/FAX=+33-1-88335215/@faxworld.
5.
This proposal creates a minimal standard encoding for FAX
within the global e-mail transport system. The proposal requires
changes to existing e-mail software
6. Security
This document specifies a means by which FAX addresses can be
into e-mail addresses. As routing of e-mail messages is determined
Domain Name System (DNS) information, a successful attack on
service could force the mail path via some particular gateway
message transfer agent where mail security can be affected
compromised software
There are several means by which an attacker might be able to
incorrect mail routing information to a client. These include: (a
compromise of a DNS server, (b) generating a counterfeit response
a client's DNS query, (c) returning incorrect "
information" in response to an unrelated query. Clients SHOULD
that mail routing is based only on authoritative answers. Once
Security mechanisms [5] become more widely deployed, clients
employ those mechanisms to verify the authenticity and integrity
mail routing records
7. Author's
Claudio
Sincrotrone
SS 14 Km 163.5
I 34012
Allocchio Standards Track [Page 5]
RFC 2304 Minimal FAX address format March 1998
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 40 3758523
Fax: +39 40 3758565
8.
[1] Postel, J., "Simple Mail Transfer Protocol", STD 10, RFC 821,
August 1982.
[2] Crocker, D., " Standard for the format of ARPA Internet
messages", STD 11, RFC 822, August 1982.
[3] Braden, R., "Requirements for Internet hosts - application
support", RFC 1123, October 1989.
[4] Malamud, C. and M. Rose, "Principles of Operation for
TPC.INT Subdomain: Remote Printing -- Technical Procedures",
1528, October 1993.
[5] Eastlake, D. and C. Kaufman, "Domain Name System
Extensions", RFC 2065, January 1997.
[6] Bradner, S., "Key words for use in RFCs to Indicate
Levels", RFC 2119, March 1997.
[7] Crocker, D. and P. Overell, "Augmented BNF for
Specifications", RFC 2234, November 1997.
[8] ITU F.401 - Message Handling Services: Naming and Addressing
Public Message Handling Service; recommendation F.401 (
1992)
[9] ITU F.423 - Message Handling Services:
Between the Interpersonal Messaging Service and the
Service; recommendation F.423 (August 1992)
[10] ITU E.164 - Numbering plan for the ISDN era;
E.164/I.331 (August 1991)
[11] ITU T.33 - Facsimile routing utilizing the subaddress
recommendation T.33 (July, 1996)
[12] ETSI I-ETS 300,380 - Universal Personal
(UPT): Access Devices Dual Tone Multi Frequency (DTMF)
for acoustical coupling to the microphone of a handset
(March 1995)
Allocchio Standards Track [Page 6]
RFC 2304 Minimal FAX address format March 1998
[13] Allocchio, C., " Minimal FAX address format in Internet Mail",
RFC 2304, March 1998.
[14] Kille, S., "MIXER (Mime Internet X.400 Enhanced Relay):
between X.400 and RFC 822/MIME", RFC 2156, January 1998.
Allocchio Standards Track [Page 7]
RFC 2304 Minimal FAX address format March 1998
9. Full Copyright
Copyright (C) The Internet Society (1998). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Allocchio Standards Track [Page 8]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
