As per Relevance of the word services, we have this rfc below:
Network Working Group C.
Request for Comments: 2846 GARR-
Category: Standards Track June 2000
GSTN Address Element Extensions in E-mail
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 (2000). All Rights Reserved
There are numerous applications where there is a need for
between the GSTN addressing and Internet addressing. This
defines a full syntax for one specific case, where there is a need
represent GSTN addresses within Internet e-mail addresses. This
syntax is a superset of a minimal syntax which has been defined
[1].
1.
The possible elements composing a "Global Switched Telephone
(GSTN) address in e-mail" (also known as the Public
Telephone Network - PSTN) can vary from a minimum number up to
really large and complex collection. As noted the minimal format
general address syntax have been defined in [1], along with
mechanism needed to define additional address elements. This
uses this extension mechanism to complete the syntax for
GSTN addresses within e-mail addresses and contains the
registrations for all newly defined elements
In particular, the following additional address elements shall
defined
- the detailed definition of GSTN number formats, in order to
various alternative standard GSTN numbering schemes, (i.e. gstn
phone, sub-addr-spec and post-dial
Allocchio Standards Track [Page 1]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
- the message originator and/or recipient specification (pstn
recipient
GSTN addresses in e-mail MAY contain additional elements defined
registered in other specifications (see for example "T33S" element
[2]), but they MUST use definitions contained in this memo for
elements specified here
In particular, "service-selector" names and "qualif-type1"
MUST be registered with IANA, and published within the "
NUMBERS" document. This provides a standard mechanism for
the element sets and should avoid unnecessary duplication.
Registration form templates for the purpouse of registering
elements are provided in Appendix B. In addition the
consideration section of this document defines the
required to proceed with new registrations
A collection of forms for already defined "service-selector"
"qualif-type1" elements is listed in appendix C and appendix
respectively
In particular, efforts have been made to maintain compatibility
elements defined in existing e-mail gateway services and
specifications. For example, to the extent possible,
has been maintained with the MIXER [3] gateways specifications
1.1 Relationship with Internet addressing other than e-
Even if in this memo we focus on e-mail addresses, a number
elements defined in this specification can also be used for
specifications dealing with embedding GSTN addresses into
addresses: for example there is some work in progress about
specification which adopts similar definitions, with slight
in the global syntax due to specific URL format
1.2 Terminology and Syntax
In this document the formal definitions are described using
syntax, as defined into [4]. 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 [5].
Allocchio Standards Track [Page 2]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
2. GSTN extended number and pstn-mbox extended
In reference [1], section 2, the minimal definition of pstn-
includes the global-phone element, and further details are defined
[1] section 2.1.
However other non global-phone numbering schemes are also possible
Thus, the minimal set syntax defined in [1] shall be extended
enable support for local-phone elements. Therefore, the gstn-
format is defined as follows
gstn-phone = ( global-phone / local-phone )
The complexity of the GSTN system includes also the optional use
subaddresses and post dialling sequences. As a consequence, there
a need to extend the definition of pstn-mbox per [1] to
support for both the minimal set definition and an extended syntax
The expanded definition of pstn-mbox is as follows
pstn-mbox = service-selector "=" global-
pstn-mbox =/ service-selector "=" gstn-
[ sub-addr-spec ] [post-sep post-dial
NOTE: see section 4 in the event multiple "sub-addr-spec"
per pstn-mbox need to be specified
2.1 The local-phone
The local-phone element is intended to represent the set of
cases where the global-phone numbering schema does not apply.
the different and complex conventions currently being used in
GSTN system, the local-phone definition supports a large number
elements
The detailed syntax for local-phone elements follows
local-phone = [ exit-code ] [ dial-number ]
exit-code = phone-
; this will include elements such as the digit
; access outside line, the long distance
; access code, the access password to the service
; etc...
Allocchio Standards Track [Page 3]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
dial-number = phone-
; this is in many cases composed of different
; such as the local phone number, the area
; (if needed), the international country
; (if needed), etc...
Note
the "+" character is reserved for use in global-phone
per [7] and MUST NOT be used as the starting character in
local-phone string
phone-string = 1*( DTMF / pause / tonewait / written-sep )
DTMF = ( DIGIT / "#" / "*" / "A" / "B" / "C" / "D" )
; special DTMF codes like "*", "#", "A", "B",
; "C", "D" are defined in [6]
; Important Note: these elements only apply
; alphabetic strings used in DTMF operations
; They are NOT applicable for the
; characters that are mapped to digits on
; keypads in some countries
pause = "p
tonewait = "w
The written-sep element is defined in [1], section 2.1.
Note
"pause" and "tonewait" character interpretation in local-
numbers depends on the specific MTA implementation. Thus its
meaning is not defined here. Both "pause" and "tonewait" are
insensitive
Important Note
A local-phone specification is a sequence which should be
only by the destination MTA specified by mta-I-pstn (see [1],
section 3). Per [12], other MTAs should transfer the
without modifying the LHS
2.2 The sub-addr-spec
In GSTN service there are cases where a sub-addr-spec is required
specify the final destination. In particular there are
subaddresses [7], which apply for various services, whereas
subaddress types may be service specific (see the fax service T.33
subaddress [8], [2]).
Allocchio Standards Track [Page 4]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Within actual telephone operations there may be cases where
types of subaddresses are used as part of a single complete address
Therefore, the sub-addr-spec syntax definition which follows
the subaddress element for the context of ISDN use; the T.33
subaddress element is defined in [2], section 2.
The definition of sub-addr-spec is
sub-addr-spec = [ isdn-sep isub-addr ]
In detail
isdn-sep = "/ISUB="
; note that "/ISUB=" is case
isub-addr = 1*( DIGIT )
isub-addr =/ 1*( DIGIT / written-sep )
The IANA registration form for sub-addr-spec is given in appendix D.2
2.3 The post-sep and post-dial
In some cases, after the connection with the destination GSTN
has been established, a further dialling sequence is required
access further services. A typical example is an automated menu
driven service using DTMF sequences. These cases may be handled
"post-sep" and "post-dial" elements as defined below
post-sep = "/POSTD="
; note that "/POSTD=" is case
post-dial = phone-
The IANA registration form for post-sep and post-dial are given
appendix D.3
3. The pstn-
There are some application where it is valuable to supplement
pstn-mbox element with additional details. Common examples
the use of originator and/or recipient names and physical addresses
particularly in the context of onramp and/or offramp gateways
The optional pstn-recipient element provides support for
details
Allocchio Standards Track [Page 5]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
As an example, when an offramp fax gateway is involved,
pstn-recipient element could be used to specify the
recipient on a fax cover page, and the fax cover page headers
be qualified using the originator pstn-recipient information
In the interest of a compact syntax, the pstn-recipient element
be used to support both originator and recipient addresses. For
cases within the ABNF definitions to follow, the elements
with "recipient" may also be used for originator information
The pstn-recipient is a sequence of qualif-type1 elements as
below
pstn-recipient = [ recipient-name ]
[ 1*( recipient-qualifier ) ]
As a consequence, the extended definition of pstn-address becomes
pstn-address = pstn-mbox [ qualif-type1 ]
pstn-address =/ pstn-mbox [ pstn-recipient ] [ qualif-type1 ]
The definition for qualif-type1 elements is contained in [1]
2.
3.1 The recipient-
The recipient-name specifies the personal name of the
and/or recipient
recipient-name = "/ATTN=" pers-
pers-name = [ givenname "." ]
[ initials "." ]
The following definitions come directly from the MIXER
[3]:
surname =
givenname = 1*( DIGIT / ALPHA / SP / "'" / "+" /
"," / "-" / "/" / ":" / "=" / "?" )
initials = 1*
Allocchio Standards Track [Page 6]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Note
the "initials" element can specify the middle initial which
common in some countries; however it is also possible to
multiple initials, which may be commonly used in other countries
This allows the complete set of givennames initials in
possible combination. See examples at section 5.2
It is essential to remember that the "pstn-address" element (in
its components and extensions) MUST strictly follow the "
rules" specified in the relevant e-mail standards [11], [12].
The IANA registration form for recipient-name is given in
D.4.
3.2 The extensible recipient-
The recipient-name is sometimes not enough to specify completely
originator and/or recipient. An additional set of optional elements
whose specific definition is in most cases application dependent,
thus defined
recipient-qualifier = ( qualif-type1 / qualif-type2 )
The recipient-qualifier is a qualif-type1 element, and contains
qualif-type1 element in a recursive definition which allows
extensible format. The purpouse of qualif-type2 element is to
additional extensibility for items which go beyond the scope of
defined for use with the qualif-type1 element
A series of qualif-type2 elements are defined below
qualif-type2 = "/" qual2-label "="
qual2-label = "ORG" / "OFNO" / "OFNA" / "STR" / "ADDR
"ADDU" / "ADDL" / "POB" / "ZIP" / "CO
string =
; note that printable characters are %x20-7
printablestring = 1*( DIGIT / ALPHA / SP /
"'" / "(" / ")" / "+" / "," / "-" /
"." / "/" / ":" / "=" / "?" )
; this definition comes from ITU F.401 [9]
; and MIXER [3]
Allocchio Standards Track [Page 7]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Table 1 includes short definition of qual2-label fields
Table 1 - qual2-
qual2-label
-----------------------------------------------------------------
"ORG" Organization Name for Physical Delivery (example:
Inc
"OFNO" Office Number for physical delivery (example: BLD2-44)
"OFNA" Office Name for physical delivery (example: Sales
"STR" Street address for physical delivery (example
45, Main Street
"ADDR" Unformatted postal address for physical
(example: HWY 14, Km 94.5 - Loc. Redhill
"ADDU" Unique postal name for physical delivery (example
ACMETELEX
"ADDL" Local postal attributes for physical delivery (example
Entrance 3, 3rd floor, Suite 296)
"POB" Post Office Box for physical
"ZIP" Postal ZIP code for physical
"CO" Country Name for physical
-----------------------------------------------------------------
One or a combination of some of the above elements is usually
to exactly specify the originator and/or recipient of the message
The use of a large number of these elements could in fact create
very long recipient-qualifier. Thus, only the strictly
elements SHOULD be used. The maximum total length of the pstn-
MUST in fact not exceed the limits specified in the relevant e-
standards [11] [12].
IMPORTANT NOTE: Although the meaning of the above elements is
directly from similar elements available in F.401 specification [9],
the naming convention used in this document is explicitly different
In this way a conflict is avoided with related X.400
rules. Other specification which use the extension mechanism of
document to define new qualif-type1 elements which overlap with F.401
are cautioned to create new labels which are different than
used in F.401.
Allocchio Standards Track [Page 8]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
The IANA registration form for these elements is given in
D.5 to D.14.
4. Multiple sub-addr-spec
There are some instances in GSTN applications where
subaddresses are used: T.33 subaddresses in fax service are one
these cases. In e-mail practice a separate and unique e-mail
is always used for each recipient; as such, if multiple
are present, the use of multiple "pstn-email" elements [1]
REQUIRED
Implementors' note
The UA MAY accept multiple subaddress elements for the
global-phone, but it MUST generate multiple "pstn-mbox"
when submitting the message to the MTA
5.
In order to clarify the specification we present here a limited
of examples. Many of the examples refer to the fax service, but
additional possible services are included. Check also the examples
[1] and [2] for additional information. Please note that all
examples are for illustration purpouses, only
5.1 pstn-mbox
A pstn-mbox address in Italy for the fax service, dialled
U.S.A., using local-phone, without sub-addr-spec and
written-sep
FAX=0103940226338
A pstn-mbox address in Germany for an hypothetical XYZ service,
global-phone, with ISDN sub-addr-spec 1234 and written-sep ".":
XYZ=+49.81.7856345/ISUB=1234
A pstn-mbox address in U.S.A. for fax service, using global-phone
with T.33 sub-addr-spec 8745, with written-sep "-" and post-
sequence p1w7005393w373
FAX=+1-202-455-7622/T33S=8745/PostD=p1w7005393w373
A pstn-mbox address in Italy for fax service, using local-phone
dialed from an MTA in Germany, (international access code "00",
ISDN subaddress 9823, with T.33 subaddress "4312" and without
or written-sep
Allocchio Standards Track [Page 9]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
FAX=003940226338/Isub=9823/T33S=4312
The same pstn-mbox address in Italy, using local-phone dialed from
MTA in Italy (long distance call), with long distant access "0",
exit-code "9", T.33 subaddress "4312", pause "p" and written-sep ".":
FAX=9p040p22.63.38/t33s=4312
A pstn-mbox address in North America for hypothetical service XYZ
using global-phone, without sub-addr-spec and written-sep "-"
".":
XYZ=+1.202.344-5723
A pstn-mbox address for fax service in France, using local-
dialed from an MTA in France (long distance call), with exit-
"0", T.33 subaddress "3345" and pause "p":
FAX=0p0134782289/T33s=3345
A pstn-mbox address for fax service in North America, using local
phone, without sub-addr-spec, without local-number, using only post
dial sequences to reach numbers stored in a locally defined short
dial numbers database, where 6743 is an access password, and 99p51
the sequence to access the local short-dial number
FAX=/postd=w6743w99p51
5.2 pstn-recipient
Here are a number of pstn-recipient examples. Please note that pstn
recipient is just an optional element, and thus a pstn-mbox
also is required in a pstn-address
A pstn-recipient using only recipient-name, with givenname
and surname
/ATTN=Tom.J.
A pstn-recipient using only recipient-name, with givenname,
complete set of initials (including the first name initial "C")
surname (where the "real life" givennames are "Carlo Maria
Santo" and the surname is "Nascimento"):
/ATTN=Carlo.CMLS.
A pstn-recipient using only recipient-name, with givenname
surname
Allocchio Standards Track [Page 10]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
/ATTN=Mark.
A pstn-recipient using only recipient-name, with surname only
/ATTN=
A pstn-recipient using recipient-name, and one recipient-
element
/ATTN=J.Smiths/OFNA=Quaility-
A pstn-recipient using two recipient-qualifier extension, only
/OFNO=T2-33A/OFNA=Quality-
A fax-recipient using some recipient-qualifier for physical delivery
/STR=45, Main.Street/OFNA=Sales.
5.3 pstn-address
Some pstn-address examples, obtained combining elements from
examples. There are complete addresses which can be used as "
part" (LHS) element of an e-mail address
Without optional pstn-recipient (fax service):
FAX=+12023445723
With pstn-recipient (XYZ service):
XYZ=+3940226338/ATTN=Mark.
With pstn-recipient made of two recipient-qualifier extensions (
service):
FAX=9p040p22.63.38/t33s=4312/ofno=T2-33A/OFNA=Q-
5.4 pstn-email
Here are the same addresses as before, where "faxgw" is
mta-I-pstn field for the fax service
FAX=+12023445723@
FAX=+39-40-226338/ATTN=Mark.Collins@
FAX=9p040p226338/T33S=4312/OFNO=T2-33A/OFNA=Q-C@
Allocchio Standards Track [Page 11]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
FAX=+39040226338/ATTN=Mark.Collins/@
NOTE: the optional "/" in front for the "@" sign can be generated
gateways to other services, like MIXER [3].
5.5 A complete SMTP transaction example
Here is an example of complete SMTP transaction
S: <listening on SMTP port
C: connection to SMTP port
S: 220 foo.domain.com ESMTP service
C: EHLO pc.mailfax.
S: 250 foo.domain.com says
C: MAIL FROM:
S: 250 Sender
C: RCPT TO:
S: 250 recipient
C:
S: 354 Enter your
C: From: Thomas Blake
C: To: Jim Burton
C: Subject: Hello
C: MIME-version: 1.0
C: Date: Mon, 01 Sep 1997 18:14:23 -0700
C: Content-Type: multipart/mixed; boundary=16820115-1435684603#2306
C
C: This is a MIME message. It contains
C: TIFF fax
C
C: --16820115-1435684603#2306
C: Content-Type: image/
C: Content-Transfer-Encoding: BASE64
C: Content-Description:
C
C: ABAA745HDKLSW932ALSDL3
C: 87AASS2999499ASDANASDF0000
C: 87BBHDXBADS00288SADFNAZBZNNDNNSNNA11A
C: H8V73KS0C8JS6BFJEH78CDWWDUJEDF7JKES8==
C: --16820115-1435684603#2306--
C: .
S: 250
C:
S: 221
Allocchio Standards Track [Page 12]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
6.
This proposal creates a standard set of extensions for
addresses, enriching the existing minimal specification [1].
proposal is consistent with existing e-mail standards, but allows
more detailed GSTN address specification, including per
and/or recipient specific elements. The IANA registration
to permit the addition of new services and qualifiers using the
addresses is also provided
7. Security
This document specifies a means by which GSTN addresses and more
be encoded into e-mail addresses. Since e-mail routing is
by Domain Name System (DNS) data, a successful attack to DNS
disseminate tampered information, which causes e-mail messages to
diverted via some MTA or Gateway where the security of the
has been compromised
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 are based only on authoritative answers. Once
Security mechanisms [7] become more widely deployed, clients
employ those mechanisms to verify the authenticity and integrity
mail routing records
Some GSTN service require dialing of private codes, like
Identification Numbers, to dial a G3 fax recipient or to
special services. As e-mail addresses are transmitted
encoding over the MTAs transport service, this could
unauthorized people to gain access to these codes when used
local-phone. More over these codes might appear in some cases in
originator and/or recipient addresses on cover pages delivered
offramp gateways to G3 fax recipients. Senders SHOULD be
methods to prevent this disclosure, like code encryption,
masquerading techniques: out-of-band communication of
information or use of encrypted data in special fields are
available non-standard techniques
Allocchio Standards Track [Page 13]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
8. Appendix A: Collected ABNF
In this section we provide a summary of ABNF specifications
both the minimal [1] and the extended elements of pstn-address
pstn-email = ["/"] pstn-address ["/"] "@" mta-I-
mta-I-pstn =
pstn-address = pstn-mbox [ qualif-type1 ]
pstn-address =/ pstn-mbox [ pstn-recipient ] [ qualif-type1 ]
pstn-mbox = service-selector "=" global-
pstn-mbox =/ service-selector "=" gstn-
[ sub-addr-spec ] [post-sep post-dial
service-selector = 1*( DIGIT / ALPHA / "-" )
qualif-type1 = "/" keyword "="
keyword = 1*( DIGIT / ALPHA / "-" )
string =
gstn-phone = ( global-phone / local-phone )
global-phone = "+" 1*( DIGIT , written-sep )
local-phone = [ exit-code ] [ dial-number ]
exit-code = phone-
dial-number = phone-
phone-string = 1*( DTMF / pause / tonewait / written-sep )
DTMF = ( DIGIT / "#" / "*" / "A" / "B" / "C" / "D" )
written-sep = ( "-" / "." )
pause = "p
tonewait = "w
sub-addr-spec = [ isdn-sep isub-addr ]
Allocchio Standards Track [Page 14]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
isdn-sep = "/ISUB="
isub-addr = 1*( DIGIT )
isub-addr =/ 1*( DIGIT / written-sep )
post-sep = "/POSTD="
post-dial = phone-
pstn-recipient = [ recipient-name ]
[ 1*( recipient-qualifier ) ]
recipient-name = "/ATTN=" pers-
pers-name = [ givenname "." ]
[ initials "." ]
surname =
givenname = 1*( DIGIT / ALPHA / SP / "'" / "+" /
"," / "-" / "/" / ":" / "=" / "?" )
initials = 1*
recipient-qualifier = ( qualif-type1 / qualif-type2 )
qualif-type2 = "/" qual2-label "="
qual2-label = "ORG" / "OFNO" / "OFNA" / "STR" / "ADDR
"ADDU" / "ADDL" / "POB" / "ZIP" / "CO
printablestring = 1*( DIGIT / ALPHA / SP /
"'" / "(" / ")" / "+" / "," / "-" /
"." / "/" / ":" / "=" / "?" )
10. Appendix B: IANA
As the service-selector and qualif-type1 elements values
extensible ones, they MUST be registered with IANA
To register a service-selector or a qualif-type1 element,
registration form templates given in B.1 and B.2 MUST be used.
new registration MUST fulfill the "Specification Required" criterion
as defined in RFC 2434, section 2 [13]:
Allocchio Standards Track [Page 15]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
"Specification Required - Values and their meaning MUST
documented in an RFC or other permanent and readily
reference, in sufficient detail so that
between independent implementations is possible."
IANA MUST NOT accept registrations which are not supplemented by
Specification as defined above and which are not fully
according to the template forms given in B.1 and B.2. In case of
for further consultation about accepting a new registration,
SHOULD refer to the Application Area Director to be directed to
appropriate "expert" individual or IETF Working Group
After successful registration, IANA should publish the registered
element in the appropriate on-line IANA WEB site, and include it
the updates of the "Assigned Numbers" RFC series
B.1: IANA Registration form template for new values of GSTN
service-
To: IANA@isi.
Subject: Registration of new values for the GSTN
service-selector specifier "foo
service-selector name
Description of Use
foo - ("foo" is a fictional new service-selector used in
template as an example, it is to be replaced with the new
being registered. Include a short description of the use of
new value here. This MUST include reference to Standard Track
and eventually to other Standard Bodies documents for the
description; the use of the value must be defined
enough for independent implementation).
Security Considerations
(Any additional security considerations that may be introduced
use of the new service-selector parameter should be defined
or in the reference Standards Track RFCs
Person & email address to contact for further information
(fill in contact information
Allocchio Standards Track [Page 16]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
INFORMATION TO THE SUBMITTER
The accepted registrations will be listed in the "Assigned Numbers
series of RFCs. The information in the registration form is
distributable
B.2: IANA Registration form template for new values of
address qualif-type1 keyword and
To: IANA@isi.
Subject: Registration of new values for the GSTN
qualif-type1 element "bar
qualif-type1 "keyword" name
qualif-type1 "value" ABNF definition
abnf - ("abnf" MUST define the ABNF form of the qualif-type1 value
The ABNF specification MUST be self-contained, using as
elements the tokens given in specification [4]. To avoid
duplication (when appropriate), it MUST also use as
non-basic tokens any already registered non-basic token from
qualif-type1 elements, i.e. it MUST use the same non-basic
name and then repeat its identical ABNF definition from
tokens; see appendix E for examples).
Description of Use
bar - ("bar" is a fictional description for a new qualif-type
element used in this template as an example. It is to be
by the real description of qualif-type1 element being registered
Include a short description of the use of the new qualif-type
here. This MUST include reference to Standards Track RFCs
eventually to other Standard Bodies documents for the
description; the use of the value MUST be defined
enough for independent implementation.)
Use Restriction
(If the new qualif-type1 elements is meaningful only for
specific set of service-element, you MUST specify here the list
allowed service-element types. If there is no restriction,
specify the keyword "none")
Allocchio Standards Track [Page 17]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Security Considerations
(Any additional security considerations that may be introduced
use of the new service-selector parameter should be defined
or in the reference Standards Track RFCs
Person & email address to contact for further information
(fill in contact information
INFORMATION TO THE SUBMITTER
The accepted registrations will be listed in the "Assigned Numbers
series of RFCs. The information in the registration form is
distributable
11. Appendix C: IANA Registration form for new value of
address service-selector "FAX
To: IANA@isi.
Subject: Registration of new values for the GSTN
service-selector specifier "FAX
service-selector name
Description of Use
FAX - specify that the GSTN address refers either to
Internet Fax device, or an onramp/offramp Fax gateway
For a complete description refer to RFC 2304 and RFC 2303
Security Considerations
See the Security Consideration section of RFC 2304.
Person & email address to contact for further information
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
Allocchio Standards Track [Page 18]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
12. Appendix D: IANA Registration forms for new values of
address qualit-type1 keyword and
D.1 - T33
To: IANA@isi.
Subject: Registration of new values for the GSTN
qualif-type1 element "T33S
qualif-type1 "keyword" name
T33
qualif-type1 "value" ABNF definition
sub-addr = 1*( DIGIT )
Description of Use
T33S is used to specify the numeric only optional fax sub-
element described in "ITU T.33 - Facsimile routing utilizing
subaddress; recommendation T.33 (July, 1996)". Further
description is available in RFC 2304.
Use Restriction
The use of "T33S" is restricted to "FAX" service-selector, is
has no meaning outside the fax service
Security Considerations
See the Security Consideration section of RFC 2304.
Person & email address to contact for further information
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
Allocchio Standards Track [Page 19]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
D.2 -
To: IANA@isi.
Subject: Registration of new values for the GSTN
qualif-type1 element "ISUB
qualif-type1 "keyword" name
qualif-type1 "value" ABNF definition
isub-addr = 1*( DIGIT )
isub-addr =/ 1*( DIGIT / written-sep )
written-sep = ( "-" / "." )
Description of Use
"ISUB" is used to specify the optional ISDN sub-address elements
in ISDN service to reach specific objects on the ISDN service. It
eventually embed written separator elements for the only scope
enhance human readability. See RFC 2846 for further details
Use Restriction
none
Security Considerations
See the Security Consideration section of RFC 2846.
Allocchio Standards Track [Page 20]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Person & email address to contact for further information
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
D.3 -
To: IANA@isi.
Subject: Registration of new values for the GSTN
qualif-type1 element "POSTD
qualif-type1 "keyword" name
qualif-type1 "value" ABNF definition
phone-string = 1*( DTMF / pause / tonewait / written-sep )
DTMF = ( DIGIT / "#" / "*" / "A" / "B" / "C" / "D" )
pause = "p
tonewait = "w
written-sep = ( "-" / "." )
Description of Use
POSTD is the optional further dialling sequence needed to
additional services (for example a menu' driven interface
available after the service site has been accessed
gstn-phone. See RFC 2846 for further details
Allocchio Standards Track [Page 21]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Use Restriction
none
Security Considerations
See the Security Consideration section of RFC 2846.
Person & email address to contact for further information
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
D.4 -
To: IANA@isi.
Subject: Registration of new values for the GSTN
qualif-type1 element "ATTN
qualif-type1 "keyword" name
qualif-type1 "value" ABNF definition
pers-name = [ givenname "." ] [ initials "." ]
surname =
givenname = 1*( DIGIT / ALPHA / SP / "'" / "+" /
"," / "-" / "/" / ":" / "=" / "?" )
initials = 1*
printablestring = 1*( DIGIT / ALPHA / SP /
"'" / "(" / ")" / "+" / "," / "-" /
"." / "/" / ":" / "=" / "?" )
Allocchio Standards Track [Page 22]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Description of Use
To specify the personal name of the individual intended as
originator or the recipient of the message. See RFC 2846
further details
Use Restriction
none
Security Considerations
See the Security Consideration section of RFC 2846.
Person & email address to contact for further information
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
D.5 -
To: IANA@isi.
Subject: Registration of new values for the GSTN
qualif-type1 element "ORG
qualif-type1 "keyword" name
qualif-type1 "value" ABNF definition
string =
Description of Use
To specify the Organization Name (example: ACME Inc.) See RFC 2846
for further details
Allocchio Standards Track [Page 23]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Use Restriction
none
Security Considerations
See the Security Consideration section of RFC 2846.
Person & email address to contact for further information
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
D.6 -
To: IANA@isi.
Subject: Registration of new values for the GSTN
qualif-type1 element "OFNO
qualif-type1 "keyword" name
qualif-type1 "value" ABNF definition
string =
Description of Use
To specify the Office Number (example: BLD2-44) See RFC 2846
for further details
Use Restriction
none
Allocchio Standards Track [Page 24]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Security Considerations
See the Security Consideration section of RFC 2846.
Person & email address to contact for further information
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
D.7 -
To: IANA@isi.
Subject: Registration of new values for the GSTN
qualif-type1 element "OFNA
qualif-type1 "keyword" name
qualif-type1 "value" ABNF definition
string =
Description of Use
To specify the Office Name (example: Sales) See RFC 2846
for further details
Use Restriction
none
Security Considerations
See the Security Consideration section of RFC 2846.
Allocchio Standards Track [Page 25]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Person & email address to contact for further information
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
D.8 -
To: IANA@isi.
Subject: Registration of new values for the GSTN
qualif-type1 element "STR
qualif-type1 "keyword" name
qualif-type1 "value" ABNF definition
string =
Description of Use
To specify the Street Address (example: 45, Main Street).
See RFC 2846 for further details
Use Restriction
none
Security Considerations
See the Security Consideration section of RFC 2846.
Allocchio Standards Track [Page 26]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Person & email address to contact for further information
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
D.9 -
To: IANA@isi.
Subject: Registration of new values for the GSTN
qualif-type1 element "ADDR
qualif-type1 "keyword" name
qualif-type1 "value" ABNF definition
string =
Description of Use
To specify the Unformatted Postal Address (example: HWY 14,
Km 94.5 - Loc. Redhill). See RFC 2846 for further details
Use Restriction
none
Security Considerations
See the Security Consideration section of RFC 2846.
Allocchio Standards Track [Page 27]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Person & email address to contact for further information
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
D.10 -
To: IANA@isi.
Subject: Registration of new values for the GSTN
qualif-type1 element "ADDU
qualif-type1 "keyword" name
qualif-type1 "value" ABNF definition
string =
Description of Use
To specify the Unique Postal Name (example: ACMETELEX).
RFC 2846 for further details
Use Restriction
none
Security Considerations
See the Security Consideration section of RFC 2846.
Allocchio Standards Track [Page 28]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Person & email address to contact for further information
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
D.11 -
To: IANA@isi.
Subject: Registration of new values for the GSTN
qualif-type1 element "ADDL
qualif-type1 "keyword" name
qualif-type1 "value" ABNF definition
string =
Description of Use
To specify the Local Postal Attributes (example: Entrance 3,
3rd floor, Suite 296). See RFC 2846 for further details
Use Restriction
none
Security Considerations
See the Security Consideration section of RFC 2846.
Allocchio Standards Track [Page 29]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Person & email address to contact for further information
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
D.12 -
To: IANA@isi.
Subject: Registration of new values for the GSTN
qualif-type1 element "POB
qualif-type1 "keyword" name
qualif-type1 "value" ABNF definition
string =
Description of Use
To specify the Post Office Box (example: CP 1374). See RFC 2846
for further details
Use Restriction
none
Security Considerations
See the Security Consideration section of RFC 2846.
Allocchio Standards Track [Page 30]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Person & email address to contact for further information
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
D.13 -
To: IANA@isi.
Subject: Registration of new values for the GSTN
qualif-type1 element "ZIP
qualif-type1 "keyword" name
qualif-type1 "value" ABNF definition
string =
Description of Use
To specify Postal ZIP code (example: I 34012). See RFC 2846
for further details
Use Restriction
none
Security Considerations
See the Security Consideration section of RFC 2846.
Allocchio Standards Track [Page 31]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Person & email address to contact for further information
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
D.14 -
To: IANA@isi.
Subject: Registration of new values for the GSTN
qualif-type1 element "CO
qualif-type1 "keyword" name
qualif-type1 "value" ABNF definition
string =
Description of Use
To specify the Country Name (example: Belgium) See RFC 2846
for further details
Use Restriction
none
Security Considerations
See the Security Consideration section of RFC 2846.
Allocchio Standards Track [Page 32]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
Person & email address to contact for further information
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
13. Author's
Claudio
INFN-
c/o Sincrotrone
SS 14 Km 163.5
I 34012
RFC822: Claudio.Allocchio@elettra.trieste.
X.400: C=it;A=garr;P=Trieste;O=Elettra
S=Allocchio;G=Claudio
Phone: +39 040 3758523
Fax: +39 040 3758565
14.
[1] Allocchio, C., "Minimal PSTN address format in Internet Mail",
RFC 2303, March 1998.
[2] Allocchio, C., "Minimal FAX address format in Internet Mail",
RFC 2304, March 1998.
[3] Kille, S., "MIXER (Mime Internet X.400 Enhanced Relay):
between X.400 and RFC 822/MIME", RFC 2156, January 1998.
[4] Crocker, D. and P. Overell, "Augmented BNF for
Specifications", RFC 2234, November 1997.
[5] Bradner, S., "Key words for use in RFCs to Indicate
Levels", BCP 14, RFC 2119, March 1997.
Allocchio Standards Track [Page 33]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
[6] ETSI I-ETS 300,380 - Universal Personal Telecommunication (UPT):
Access Devices Dual Tone Multi Frequency (DTMF) sender
acoustical coupling to the microphone of a handset
(March 1995)
[7] ITU E.164 - The International Public Telecommunication
Plan E.164/I.331 (May 1997)
[8] ITU T.33 - Facsimile routing utilizing the subaddress
recommendation T.33 (July, 1996)
[9] ITU F.401 - Message Handling Services: Naming and Addressing
Public Massage Handling Service; recommendation F.401 (
1992)
[10] ITU F.423 - Message Handling Services:
Between the Interpersonal Messaging Service and the
Service; recommendation F.423 (August 1992)
[11] Crocker, D., "Standard for the format of ARPA Internet
messages", STD 11, RFC 822, August 1982.
[12] Braden, R., "Requirements for Internet hosts - application
support", STD 3, RFC 1123, October 1989.
[13] Narten, T. and H. Alvestrand, "Guidelines for Writing an
Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
Allocchio Standards Track [Page 34]
RFC 2846 GSTN Address Extensions in E-mail Services June 2000
15. Full Copyright
Copyright (C) The Internet Society (2000). 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
Funding for the RFC Editor function is currently provided by
Internet Society
Allocchio Standards Track [Page 35]
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
