RFC 2846
GSTN Address Element Extensions in E-mail Services
GSTN Address Element Extensions in E-mail Services 💌
(part 1 of 5)
okay bestie, let's start with the title block 🎀 This is RFC 2846, from the Network Working Group. C. Allocchio at GARR-Italy wrote it, it's a Standards Track doc, and it's dated June 2000. The header doesn't list anything it obsoletes or updates.
Status of this Memo 📋
This document is an Internet standards track protocol for the Internet community, and it's asking for discussion and suggestions for improvements 🫶 For the standardization state and status of this protocol, check the current edition of "Internet Official Protocol Standards" (STD 1). Distribution of this memo is unlimited.
Copyright Notice ©️
Copyright (C) The Internet Society (2000). All Rights Reserved.
Abstract ✨
There are tons of apps where the phone network (GSTN addressing) and Internet addressing need to talk to each other 📞💻 This memo defines a full syntax for one specific case: putting GSTN addresses inside Internet e-mail addresses 💌 That full syntax is a superset of a minimal syntax already defined in [1].
1. Introduction 🌸
GSTN addresses in e-mail (also known as the Public Switched Telephone Network, or PSTN) can range from a tiny number of elements to a really big, complicated collection 😭 The minimal format and general address syntax were defined in [1], along with the mechanism for defining more address elements. This memo uses that extension mechanism to finish the syntax for representing GSTN addresses in e-mail addresses, and it includes the IANA registrations for all the newly defined elements 🧚
Specifically, the following additional address elements shall be defined:
- the detailed definition of GSTN number formats, so we can cover the different standard GSTN numbering schemes (i.e. gstn-phone, sub-addr-spec and post-dial)
- the message originator and/or recipient specification (pstn-recipient)
GSTN addresses in e-mail MAY contain extra elements that are defined and registered in other specifications (see for example the "T33S" element in [2]). BUT they MUST use the definitions in this memo for the elements specified here 🙅♀️
Also, "service-selector" names and "qualif-type1" elements MUST be registered with IANA and published in the "ASSIGNED NUMBERS" document. This gives us a standard way to extend the element sets and should avoid unnecessary duplication 🔁 The IANA registration form templates for registering new elements are in Appendix B, and the IANA considerations section of this document spells out the procedures for new registrations 📝
There's also a collection of forms for the "service-selector" and "qualif-type1" elements that are already defined. Those are in Appendix C and Appendix D respectively 💅
We worked hard to keep things compatible with elements from existing e-mail gateway services and standard specs 🫶 For example, compatibility with the MIXER [3] gateway specifications has been kept wherever possible. ✨
1.1 Relationship with Internet addressing other than e-mail 🦋
Even though this memo focuses on e-mail addresses, a bunch of the elements defined here can also be used by other specs that embed GSTN addresses into other kinds of addresses. For example, there's some work in progress on a URL spec that adopts similar definitions, with small changes to the global syntax because of the specific URL format 🌈
1.2 Terminology and Syntax conventions 🧠
Here the formal definitions are written in ABNF syntax, as defined in [4]. We also use some of the "CORE DEFINITIONS" from "APPENDIX A - CORE" of that document. The exact meaning of the capitalised words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" is defined in reference [5] 🎓
2. GSTN extended number and pstn-mbox extended format 📱
In reference [1], section 2, the minimal definition of pstn-mbox includes the global-phone element, and more details are defined in [1] section 2.1 ✨
But non-global-phone numbering schemes are also possible 🌍 So the minimal set syntax defined in [1] shall be extended to support local-phone elements. That means the gstn-phone format is defined like this:
gstn-phone = ( global-phone / local-phone )The GSTN system also has optional subaddresses and post dialling sequences, which makes things even more complex 🙈 Because of that, the definition of pstn-mbox per [1] needs to be extended to cover both the minimal set definition and the extended syntax. The expanded definition of pstn-mbox looks like this:
pstn-mbox = service-selector "=" global-phone
pstn-mbox =/ service-selector "=" gstn-phone
[ sub-addr-spec ] [post-sep post-dial]NOTE: see section 4 if multiple "sub-addr-spec" elements per pstn-mbox need to be specified 👀
2.1 The local-phone syntax 📞
The local-phone element is meant to cover the cases where the global-phone numbering scheme doesn't apply. The GSTN world has lots of different and complex conventions, so the local-phone definition supports a large number of elements 💖
Here's the detailed syntax for local-phone elements:
local-phone = [ exit-code ] [ dial-number ]
exit-code = phone-string
; this will include elements such as the digit to
; access outside line, the long distance carrier
; access code, the access password to the service,
; etc...
dial-number = phone-string
; this is in many cases composed of different elements
; such as the local phone number, the area code
; (if needed), the international country code
; (if needed), etc...Note: the "+" character is reserved for use in global-phone addresses per [7], so it MUST NOT be used as the starting character in a local-phone string. Don't be that person 🙅♀️
Here's the phone-string and DTMF stuff:
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 for
; alphabetic strings used in DTMF operations.
; They are NOT applicable for the alphabetic
; characters that are mapped to digits on phone
; keypads in some countries.
pause = "p"
tonewait = "w"The written-sep element is defined in [1], section 2.1 📖
Note: how "pause" and "tonewait" get interpreted in local-phone numbers depends on the specific MTA implementation, so their exact meaning isn't defined here 🤷♀️ Both "pause" and "tonewait" are case insensitive 💜
Important Note: a local-phone specification is a sequence that should only be used by the destination MTA specified by mta-I-pstn (see [1], section 3). Per [12], other MTAs should transfer the message without modifying the LHS 🚨
2.2 The sub-addr-spec element 🎀
In GSTN service there are cases where a sub-addr-spec is needed to specify the final destination 🎯 In particular, there are ISDN subaddresses [7], which apply to various services, while other subaddress types may be service specific (see the fax service T.33 subaddress [8], [2]).
Inside real telephone operations, you might see different types of subaddresses used as part of one complete address. So the sub-addr-spec syntax below defines the subaddress element for 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 INSENSITIVE
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 elements 🌈
Sometimes, once the connection with the destination GSTN device is up, you need another dialling sequence to get into further services 📲 A typical example is an automated menu-driven service that uses DTMF sequences. These cases can be handled with the "post-sep" and "post-dial" elements, defined below:
post-sep = "/POSTD="
; note that "/POSTD=" is case INSENSITIVE
post-dial = phone-stringThe IANA registration forms for post-sep and post-dial are given in Appendix D.3 🫧
3. The pstn-recipient 💌
Some applications find it really valuable to add extra details to the pstn-mbox element 💁♀️ Common examples include originator and/or recipient names and physical addresses, especially with onramp and/or offramp gateways.
The optional pstn-recipient element gives you a way to include those details ✨
For example, when an offramp fax gateway is involved, the pstn-recipient element could be used to name the intended recipient on a fax cover page, and the fax cover page headers could be qualified using the originator's pstn-recipient info 📠
To keep the syntax compact, the pstn-recipient element may be used for both originator and recipient addresses. In every ABNF definition that follows, any element labelled "recipient" may also be used for originator information 🧃
The pstn-recipient is a sequence of qualif-type1 elements, defined like this:
pstn-recipient = [ recipient-name ]
[ 1*( recipient-qualifier ) ]So 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 in [1] section 2 🔍
3.1 The recipient-name 👑
The recipient-name specifies the personal name of the originator and/or recipient 🥰
recipient-name = "/ATTN=" pers-name
pers-name = [ givenname "." ]
[ initials "." ]
surnameThe following definitions come directly from the MIXER specification [3]:
surname = printablestring
givenname = 1*( DIGIT / ALPHA / SP / "'" / "+" /
"," / "-" / "/" / ":" / "=" / "?" )
initials = 1*ALPHANote: the "initials" element can specify the middle initial that's common in some countries 🌏 It can also support multiple initials, which are commonly used in other countries. That lets you cover every possible combination of the givenname initials. See the examples in section 5.2 ✨
It's essential to remember that the "pstn-address" element (in all its components and extensions) MUST strictly follow the "quoting rules" specified in the relevant e-mail standards [11], [12] 🚨
The IANA registration form for recipient-name is given in Appendix D.4 📝
3.2. The extensible recipient-qualifier ✨
okay so sometimes the recipient-name just isn't enough to say exactly who the originator and/or recipient is 💅 so there's an extra set of optional elements for that. what they mean is mostly up to whatever application is using them 🎀
recipient-qualifier = ( qualif-type1 / qualif-type2 )the recipient-qualifier is a qualif-type1 element, and it contains a qualif-type1 element again in a recursive definition, which is what keeps the format extensible 🦋 the whole point of qualif-type2 is to leave room for extra stuff that goes beyond what qualif-type1 covers 🌈
here are the qualif-type2 elements that get defined:
qualif-type2 = "/" qual2-label "=" string
qual2-label = "ORG" / "OFNO" / "OFNA" / "STR" / "ADDR"
"ADDU" / "ADDL" / "POB" / "ZIP" / "CO"
string = PCHAR
; note that printable characters are %x20-7E
printablestring = 1*( DIGIT / ALPHA / SP /
"'" / "(" / ")" / "+" / "," / "-" /
"." / "/" / ":" / "=" / "?" )
; this definition comes from ITU F.401 [9]
; and MIXER [3]here's Table 1, which gives a quick rundown of each qual2-label 🍓
Table 1 - qual2-label
qual2-label Description
-----------------------------------------------------------------
"ORG" Organization Name for Physical Delivery (example: ACME
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 delivery
(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 delivery
"ZIP" Postal ZIP code for physical delivery
"CO" Country Name for physical delivery
-----------------------------------------------------------------usually one of these elements, or a combo of a few, is enough to pin down the originator and/or recipient 🫶 but if you stack a ton of them you get a super long recipient-qualifier, which is giving chaos 😭 so only the strictly needed elements SHOULD be used. and the maximum total length of the pstn-email MUST in fact not exceed the limits specified in the relevant e-mail standards [11] [12] 💀
IMPORTANT NOTE: the meaning of the elements above comes straight from the F.401 specification [9], but the naming convention in this document is deliberately different 🙈 that way we avoid a clash with related X.400 addressing rules. any other specification that uses this document's extension mechanism to define new qualif-type1 elements that overlap with F.401 is cautioned to come up with labels that are different from the ones used in F.401.
the IANA registration form for these elements is given in appendix D.5 to D.14 📋
4. Multiple sub-addr-spec cases
there are some GSTN applications that use multiple subaddresses, and T.33 subaddresses in fax service are one of those cases 📠 but e-mail doesn't really do it that way: every recipient always gets their own unique e-mail address. so if multiple subaddresses are present, using multiple "pstn-email" elements [1] is REQUIRED 🎀
Implementors' note: The UA MAY accept multiple subaddress elements for the same global-phone, but it MUST generate multiple "pstn-mbox" elements when submitting the message to the MTA. 🌸
5. Examples ✨
to make the spec make sense, here's a limited set of examples 🧚 lots of them are about the fax service, but a few other possible services sneak in too. you can also peek at the examples in [1] and [2] for extra info. and just to be clear, all of these examples are for illustration purposes only 💖
5.1. pstn-mbox examples
a pstn-mbox address in Italy for the fax service, dialled from U.S.A., using local-phone, without sub-addr-spec and without written-sep:
FAX=0103940226338a pstn-mbox address in Germany for a hypothetical XYZ service, using global-phone, with ISDN sub-addr-spec 1234 and written-sep ".":
XYZ=+49.81.7856345/ISUB=1234a 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-dial sequence p1w7005393w373:
FAX=+1-202-455-7622/T33S=8745/PostD=p1w7005393w373a pstn-mbox address in Italy for fax service, using local-phone, dialed from an MTA in Germany (international access code "00", with ISDN subaddress 9823, with T.33 subaddress "4312" and without pause or written-sep:
FAX=003940226338/Isub=9823/T33S=4312the same pstn-mbox address in Italy, using local-phone dialed from an MTA in Italy (long distance call), with long distant access "0", with exit-code "9", T.33 subaddress "4312", pause "p" and written-sep ".":
FAX=9p040p22.63.38/t33s=4312a pstn-mbox address in North America for hypothetical service XYZ, using global-phone, without sub-addr-spec and written-sep "-" and ".":
XYZ=+1.202.344-5723a pstn-mbox address for fax service in France, using local-phone dialed from an MTA in France (long distance call), with exit-code "0", T.33 subaddress "3345" and pause "p":
FAX=0p0134782289/T33s=3345a 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 is the sequence to access the local short-dial number:
FAX=/postd=w6743w99p515.2. pstn-recipient examples
here's a bunch of pstn-recipient examples 💅 just remember that pstn-recipient is only an optional element, so a pstn-mbox element is also required in a pstn-address.
a pstn-recipient using only recipient-name, with givenname initials and surname:
/ATTN=Tom.J.Smithsa pstn-recipient using only recipient-name, with givenname, a complete set of initials (including the first name initial "C") and surname (where the "real life" givennames are "Carlo Maria Luis Santo" and the surname is "Nascimento"):
/ATTN=Carlo.CMLS.Nascimentoa pstn-recipient using only recipient-name, with givenname and surname:
/ATTN=Mark.Collinsa pstn-recipient using only recipient-name, with surname only:
/ATTN=Smithsa pstn-recipient using recipient-name, and one recipient-qualifier element:
/ATTN=J.Smiths/OFNA=Quaility-controla pstn-recipient using two recipient-qualifier extension, only:
/OFNO=T2-33A/OFNA=Quality-Ccontrola fax-recipient using some recipient-qualifier for physical delivery:
/STR=45, Main.Street/OFNA=Sales.dept5.3. pstn-address examples
these are some pstn-address examples, made by mixing and matching the pieces from the earlier examples 🧩 each one is a complete address that can be used as the "local part" (LHS) element of an e-mail address.
without optional pstn-recipient (fax service):
FAX=+12023445723with pstn-recipient (XYZ service):
XYZ=+3940226338/ATTN=Mark.Collinswith pstn-recipient made of two recipient-qualifier extensions (fax service):
FAX=9p040p22.63.38/t33s=4312/ofno=T2-33A/OFNA=Q-C5.4. pstn-email examples
here are the same addresses as before, where "faxgw" is the mta-I-pstn field for the fax service 📬
FAX=+12023445723@faxgw
FAX=+39-40-226338/ATTN=Mark.Collins@faxgw
FAX=9p040p226338/T33S=4312/OFNO=T2-33A/OFNA=Q-C@faxgw
FAX=+39040226338/ATTN=Mark.Collins/@faxgwNOTE: the optional "/" in front for the "@" sign can be generated by gateways to other services, like MIXER [3]. 🔥
5.5. A complete SMTP transaction example:
and finally, a full SMTP transaction so you can see the whole thing in action 🎬
S: <listening on SMTP port>
C: <opens connection to SMTP port>
S: 220 foo.domain.com ESMTP service ready
C: EHLO pc.mailfax.com
S: 250 foo.domain.com says hello
C: MAIL FROM:<tom@mailfax.com>
S: 250 <tom@mailfax.com> Sender ok
C: RCPT TO:<FAX=+3940226338@foo.mailfax.com>
S: 250 <FAX=+3940226338> recipient ok
C: DATA
S: 354 Enter your data
C: From: Thomas Blake <tom@mailfax.com>
C: To: Jim Burton <FAX=+3940226338@foo.mailfax.com>
C: Subject: Hello there
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 a
C: TIFF fax bodypart
C:
C: --16820115-1435684603#2306
C: Content-Type: image/TIFF
C: Content-Transfer-Encoding: BASE64
C: Content-Description: FAX
C:
C: ABAA745HDKLSW932ALSDL3ANCVSASDFLALSDFA
C: 87AASS2999499ASDANASDF0000ASDFASDFNANN
C: 87BBHDXBADS00288SADFNAZBZNNDNNSNNA11A0
C: H8V73KS0C8JS6BFJEH78CDWWDUJEDF7JKES8==
C: --16820115-1435684603#2306--
C: .
S: 250 Okay
C: QUIT
S: 221 Goodbye6. Conclusion 🌟
this proposal sets up a standard set of extensions for GSTN addresses, which builds on the minimal spec in [1] and makes it way more detailed 🦋 it stays consistent with existing e-mail standards, but lets you describe GSTN addresses more precisely, including element-specific stuff for each originator and/or recipient. it also gives us an IANA registration mechanism so new services and qualifiers can be added to GSTN addresses 👑
7. Security Considerations 🚨
okay bestie, this one is SERIOUS, so read it carefully 🫶 this document describes a way to encode GSTN addresses and more into e-mail addresses. and since e-mail routing is determined by Domain Name System (DNS) data, a successful attack on DNS could spread tampered information, which would cause e-mail messages to get diverted through some MTA or Gateway whose software security has been compromised 😭
there are a few ways an attacker might deliver wrong mail routing info to a client, including: (a) compromising a DNS server, (b) generating a counterfeit response to a client's DNS query, and (c) returning incorrect "additional information" in response to an unrelated query. clients SHOULD ensure that mail routing are based only on authoritative answers. and once DNS Security mechanisms [7] become more widely deployed, clients SHOULD employ those mechanisms to verify the authenticity and integrity of mail routing records 🔐
some GSTN services need you to dial private codes, like Personal Identification Numbers, to reach a G3 fax recipient or to access special services 🙈 since e-mail addresses are sent without encoding over the MTAs transport service, this could let unauthorized people get their hands on those codes when they're used inside local-phone. even worse, these codes might show up in some cases in the originator and/or recipient addresses on cover pages delivered via offramp gateways to G3 fax recipients 💀 so senders SHOULD be provided methods to prevent this disclosure, like code encryption or masquerading techniques. out-of-band communication of authorization information or use of encrypted data in special fields are the available non-standard techniques. protect those codes like they're your diary 🔒💖
8. Appendix A: Collected ABNF Syntax ✨
okay bestie, this is the grammar cheat sheet 🧚 it pulls the minimal [1] and extended elements of pstn-address into one place so you can see how everything fits together 💅
pstn-email = ["/"] pstn-address ["/"] "@" mta-I-pstn
mta-I-pstn = domain
pstn-address = pstn-mbox [ qualif-type1 ]
pstn-address =/ pstn-mbox [ pstn-recipient ] [ qualif-type1 ]
pstn-mbox = service-selector "=" global-phone
pstn-mbox =/ service-selector "=" gstn-phone
[ sub-addr-spec ] [post-sep post-dial]
service-selector = 1*( DIGIT / ALPHA / "-" )
qualif-type1 = "/" keyword "=" string
keyword = 1*( DIGIT / ALPHA / "-" )
string = PCHAR
gstn-phone = ( global-phone / local-phone )
global-phone = "+" 1*( DIGIT , written-sep )
local-phone = [ exit-code ] [ dial-number ]
exit-code = phone-string
dial-number = phone-string
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 ]
isdn-sep = "/ISUB="
isub-addr = 1*( DIGIT )
isub-addr =/ 1*( DIGIT / written-sep )
post-sep = "/POSTD="
post-dial = phone-string
pstn-recipient = [ recipient-name ]
[ 1*( recipient-qualifier ) ]
recipient-name = "/ATTN=" pers-name
pers-name = [ givenname "." ]
[ initials "." ]
surname
surname = printablestring
givenname = 1*( DIGIT / ALPHA / SP / "'" / "+" /
"," / "-" / "/" / ":" / "=" / "?" )
initials = 1*ALPHA
recipient-qualifier = ( qualif-type1 / qualif-type2 )
qualif-type2 = "/" qual2-label "=" string
qual2-label = "ORG" / "OFNO" / "OFNA" / "STR" / "ADDR"
"ADDU" / "ADDL" / "POB" / "ZIP" / "CO"
printablestring = 1*( DIGIT / ALPHA / SP /
"'" / "(" / ")" / "+" / "," / "-" /
"." / "/" / ":" / "=" / "?" )10. Appendix B: IANA Considerations 🎀
so the service-selector and qualif-type1 values are extensible, which means they're basically open for new members 🦋 they MUST be registered with IANA, no exceptions bestie.
to register a service-selector or a qualif-type1 element, the registration form templates in B.1 and B.2 MUST be used. any new registration MUST fulfill the "Specification Required" criterion, as defined in RFC 2434, section 2 [13]:
"Specification Required - Values and their meaning MUST be documented in an RFC or other permanent and readily available reference, in sufficient detail so that interoperability between independent implementations is possible."
IANA MUST NOT accept registrations which are not supplemented by a Specification as defined above and which are not fully specified according to the template forms given in B.1 and B.2. if IANA needs to consult about accepting a new registration, IANA SHOULD refer to the Application Area Director, who'll point them to the appropriate "expert" individual or IETF Working Group 🫶
after a successful registration, IANA should publish the registered new element on the appropriate online IANA WEB site, and include it in the updates of the "Assigned Numbers" RFC series 🌈
B.1: IANA Registration form template for new values of GSTN address service-selector
here's the template, copied exactly so nothing gets lost 📝
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
service-selector specifier "foo"
service-selector name:
foo
Description of Use:
foo - ("foo" is a fictional new service-selector used in this
template as an example, it is to be replaced with the new value
being registered. Include a short description of the use of the
new value here. This MUST include reference to Standard Track RFCs
and eventually to other Standard Bodies documents for the complete
description; the use of the value must be defined completely
enough for independent implementation).
Security Considerations:
(Any additional security considerations that may be introduced by
use of the new service-selector parameter should be defined here
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 freely
distributable.B.2: IANA Registration form template for new values of GSTN address qualif-type1 keyword and value
and here's the second template for qualif-type1 keyword and value, also verbatim 🍓
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
qualif-type1 element "bar"
qualif-type1 "keyword" name:
bar
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 basic
elements the tokens given in specification [4]. To avoid any
duplication (when appropriate), it MUST also use as building
non-basic tokens any already registered non-basic token from other
qualif-type1 elements, i.e. it MUST use the same non-basic token
name and then repeat its identical ABNF definition from basic
tokens; see appendix E for examples).
Description of Use:
bar - ("bar" is a fictional description for a new qualif-type1
element used in this template as an example. It is to be replaced
by the real description of qualif-type1 element being registered.
Include a short description of the use of the new qualif-type1
here. This MUST include reference to Standards Track RFCs and
eventually to other Standard Bodies documents for the complete
description; the use of the value MUST be defined completely
enough for independent implementation.)
Use Restriction:
(If the new qualif-type1 elements is meaningful only for a
specific set of service-element, you MUST specify here the list of
allowed service-element types. If there is no restriction, then
specify the keyword "none")
Security Considerations:
(Any additional security considerations that may be introduced by
use of the new service-selector parameter should be defined here
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 freely
distributable.11. Appendix C: IANA Registration form for new value of GSTN address service-selector "FAX" 📠
this one's a real, filled-in registration for the FAX service-selector 🎉
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
service-selector specifier "FAX"
service-selector name:
FAX
Description of Use:
FAX - specify that the GSTN address refers either to an
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 Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 375856512. Appendix D: IANA Registration forms for new values of GSTN address qualit-type1 keyword and value 🌸
four filled-in registrations are coming up, one for each new qualif-type1 keyword 💖
D.1 - T33S
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
qualif-type1 element "T33S"
qualif-type1 "keyword" name:
T33S
qualif-type1 "value" ABNF definition:
sub-addr = 1*( DIGIT )
Description of Use:
T33S is used to specify the numeric only optional fax sub-address
element described in "ITU T.33 - Facsimile routing utilizing the
subaddress; recommendation T.33 (July, 1996)". Further detailed
description is available in RFC 2304.
Use Restriction:
The use of "T33S" is restricted to "FAX" service-selector, is it
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 Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 3758565D.2 - ISUB
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
qualif-type1 element "ISUB"
qualif-type1 "keyword" name:
ISUB
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 used
in ISDN service to reach specific objects on the ISDN service. It can
eventually embed written separator elements for the only scope to
enhance human readability. See RFC 2846 for further details.
Use Restriction:
none.
Security Considerations:
See the Security Consideration section of RFC 2846.
Person & email address to contact for further information:
Claudio Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 3758565D.3 - POSTD
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
qualif-type1 element "POSTD"
qualif-type1 "keyword" name:
POSTD
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 access
additional services (for example a menu' driven interface)
available after the service site has been accessed using
gstn-phone. See RFC 2846 for further details.
Use Restriction:
none.
Security Considerations:
See the Security Consideration section of RFC 2846.
Person & email address to contact for further information:
Claudio Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 3758565D.4 - ATTN
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
qualif-type1 element "ATTN"
qualif-type1 "keyword" name:
ATTN
qualif-type1 "value" ABNF definition:
pers-name = [ givenname "." ] [ initials "." ] surname
surname = printablestring
givenname = 1*( DIGIT / ALPHA / SP / "'" / "+" /
"," / "-" / "/" / ":" / "=" / "?" )
initials = 1*ALPHAOkay so the personal name bit is basically this little grammar 🎀
printablestring = 1*( DIGIT / ALPHA / SP /
"'" / "(" / ")" / "+" / "," / "-" /
"." / "/" / ":" / "=" / "?" )Description of Use: This is for the personal name of whoever's the originator or the recipient of the message 💖 See RFC 2846 for further details.
Use Restriction: none. No restrictions, bestie ✨
Security Considerations: See the Security Consideration section of RFC 2846 🔒
Person & email address to contact for further information:
Claudio Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 3758565D.5 - ORG 💅
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
qualif-type1 element "ORG"qualif-type1 "keyword" name:
ORG
qualif-type1 "value" ABNF definition:
string = PCHARDescription of Use: This one's for the Organization Name, like ACME Inc.! 🏢 See RFC 2846 for further details.
Use Restriction: none. Zero limits here 🌈
Security Considerations: See the Security Consideration section of RFC 2846 🔒
Person & email address to contact for further information:
Claudio Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 3758565D.6 - OFNO 🧚
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
qualif-type1 element "OFNO"qualif-type1 "keyword" name:
OFNO
qualif-type1 "value" ABNF definition:
string = PCHARDescription of Use: Here's where the Office Number goes, like BLD2-44 🚪 See RFC 2846 for further details.
Use Restriction: none. Totally open, no cap 🍓
Security Considerations: See the Security Consideration section of RFC 2846 🔒
Person & email address to contact for further information:
Claudio Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 3758565D.7 - OFNA 🌸
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
qualif-type1 element "OFNA"qualif-type1 "keyword" name:
OFNA
qualif-type1 "value" ABNF definition:
string = PCHARDescription of Use: This is the Office Name, like Sales 💼 See RFC 2846 for further details.
Use Restriction: none. Nothing to worry about 💅
Security Considerations: See the Security Consideration section of RFC 2846 🔒
Person & email address to contact for further information:
Claudio Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 3758565D.8 - STR 🦋
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
qualif-type1 element "STR"qualif-type1 "keyword" name:
STR
qualif-type1 "value" ABNF definition:
string = PCHARDescription of Use: This is the Street Address, like 45, Main Street 🛣️ See RFC 2846 for further details.
Use Restriction: none. Free and clear 🫶
Security Considerations: See the Security Consideration section of RFC 2846 🔒
Person & email address to contact for further information:
Claudio Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 3758565D.9 - ADDR 💌
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
qualif-type1 element "ADDR"qualif-type1 "keyword" name:
ADDR
qualif-type1 "value" ABNF definition:
string = PCHARDescription of Use: This is the Unformatted Postal Address, like HWY 14, Km 94.5 - Loc. Redhill 📮 See RFC 2846 for further details.
Use Restriction: none. Go wild 🌈
Security Considerations: See the Security Consideration section of RFC 2846 🔒
Person & email address to contact for further information:
Claudio Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 3758565D.10 - ADDU 👑
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
qualif-type1 element "ADDU"qualif-type1 "keyword" name:
ADDU
qualif-type1 "value" ABNF definition:
string = PCHARDescription of Use: This is the Unique Postal Name, like ACMETELEX 📠 See RFC 2846 for further details.
Use Restriction: none. Easy peasy 💖
Security Considerations: See the Security Consideration section of RFC 2846 🔒
Person & email address to contact for further information:
Claudio Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 3758565D.11 - ADDL 🏢
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
qualif-type1 element "ADDL"qualif-type1 "keyword" name:
ADDL
qualif-type1 "value" ABNF definition:
string = PCHARDescription of Use: These are the Local Postal Attributes, like Entrance 3, 3rd floor, Suite 296 🪄 See RFC 2846 for further details.
Use Restriction: none. No limits, periodt 💅
Security Considerations: See the Security Consideration section of RFC 2846 🔒
Person & email address to contact for further information:
Claudio Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 3758565D.12 - POB 📫
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
qualif-type1 element "POB"qualif-type1 "keyword" name:
POB
qualif-type1 "value" ABNF definition:
string = PCHARDescription of Use: This is the Post Office Box, like CP 1374 📦 See RFC 2846 for further details.
Use Restriction: none. Totally fine 🎀
Security Considerations: See the Security Consideration section of RFC 2846 🔒
Person & email address to contact for further information:
Claudio Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 3758565D.13 - ZIP 🌟
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
qualif-type1 element "ZIP"qualif-type1 "keyword" name:
ZIP
qualif-type1 "value" ABNF definition:
string = PCHARDescription of Use: This is the Postal ZIP code, like I 34012 🗺️ See RFC 2846 for further details.
Use Restriction: none. Zero restrictions, bestie ✨
Security Considerations: See the Security Consideration section of RFC 2846 🔒
Person & email address to contact for further information:
Claudio Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 3758565D.14 - CO 🌍
To: IANA@isi.edu
Subject: Registration of new values for the GSTN address
qualif-type1 element "CO"qualif-type1 "keyword" name:
CO
qualif-type1 "value" ABNF definition:
string = PCHARDescription of Use: This is the Country Name, like Belgium 🇧🇪 See RFC 2846 for further details.
Use Restriction: none. Open to all 💜
Security Considerations: See the Security Consideration section of RFC 2846 🔒
Person & email address to contact for further information:
Claudio Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 375856513. Author's Address 🦋
Claudio Allocchio
INFN-GARR
c/o Sincrotrone Trieste
SS 14 Km 163.5 Basovizza
I 34012 Trieste
Italy
RFC822: Claudio.Allocchio@elettra.trieste.it
X.400: C=it;A=garr;P=Trieste;O=Elettra;
S=Allocchio;G=Claudio;
Phone: +39 040 3758523
Fax: +39 040 375856514. References 📚
- [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): Mapping between X.400 and RFC 822/MIME", RFC 2156, January 1998.
- [4] Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications", RFC 2234, November 1997.
- [5] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
- [6] ETSI I-ETS 300,380 - Universal Personal Telecommunication (UPT): Access Devices Dual Tone Multi Frequency (DTMF) sender for acoustical coupling to the microphone of a handset telephone (March 1995)
- [7] ITU E.164 - The International Public Telecommunication Numbering 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 for Public Massage Handling Service; recommendation F.401 (August 1992)
- [10] ITU F.423 - Message Handling Services: Intercommunication Between the Interpersonal Messaging Service and the Telefax Service; recommendation F.423 (August 1992)
- [11] Crocker, D., "Standard for the format of ARPA Internet text messages", STD 11, RFC 822, August 1982.
- [12] Braden, R., "Requirements for Internet hosts - application and support", STD 3, RFC 1123, October 1989.
- [13] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
15. Full Copyright Statement ✨
okay bestie, this part is the legal bit, but it's still important so let's go 💅 The Internet Society owns the copyright here, © 2000, all rights reserved 🎀
You're allowed to copy this document and share it with others 🦋 You can also make derivative works that comment on it, explain it, or help people implement it, and publish and distribute those too, in whole or in part, with no restrictions at all 🌈 The one catch is that the copyright notice and this paragraph have to stay on every copy and every derivative work 🫶
What you can't do is change the document itself 🙈 That means no removing the copyright notice, and no removing references to the Internet Society or other Internet organizations. There are two exceptions. The first is developing Internet standards, where the copyright procedures in the Internet Standards process have to be followed. The second is translating it into languages other than English 🌸
The permissions in this section are perpetual, so they will never be revoked by the Internet Society or its successors or assigns 💜
Now the disclaimer, which is a bit dramatic but totally real 😭 This document and the information in it is provided on an "AS IS" basis, and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS, OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE 💀
Acknowledgement
Funding for the RFC Editor function is currently provided by the Internet Society 🍓👑
📦 where this page comes from
- ietf: rfc2846 2000-06
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms