Debian Codegraph @

rfc2303.html

raw
1 <pre>Network Working Group C. Allocchio
2 Request for Comments: 2303 GARR-Italy
3 Category: Standards Track March 1998
4
5
6
7
8 <span class="h1">Minimal PSTN address format in Internet Mail</span>
9
10
11 Status of this Memo
12
13 This document specifies an Internet standards track protocol for the
14 Internet community, and requests discussion and suggestions for
15 improvements. Please refer to the current edition of the "Internet
16 Official Protocol Standards" (STD 1) for the standardization state
17 and status of this protocol. Distribution of this memo is unlimited.
18
19 Copyright Notice
20
21 Copyright (C) The Internet Society (1998). All Rights Reserved.
22
23 IESG NOTE
24
25 This memo describes a simple method of encoding PSTN addresses in the
26 local-part of Internet email addresses, along with an extension
27 mechanism to allow encoding of additional standard attributes needed
28 for email gateways to PSTN-based services.
29
30 As with all Internet mail addresses, the left-hand-side (local- part)
31 of an address generated according to this specification, is not to be
32 interpreted except by the MTA that is named on the right-hand-side
33 (domain).
34
35 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
36
37 Since the very first e-mail to PSTN services gateway appeared, a
38 number of different methods to specify a PSTN address as an e-mail
39 address have been used by implementors. Two major objectives for this
40 were
41
42 - enable an e-mail user to access these services from his/her
43 e-mail interface;
44
45 - enable some kind of "PSTN over e-mail service" transport, to
46 reduce the costs of PSTN long distance transmissions, and use the
47 existing e-mail infrastructure.
48
49
50
51
52 <span class="grey">Allocchio Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2303">RFC 2303</a> Minimal PSTN in Internet Mail March 1998</span>
55
56
57 This memo describes the MINIMAL addressing method to encode PSTN
58 addresses into e-mail addresses and the standard extension mechanism
59 to allow definition of further standard elements. The opposite
60 problem, i.e. to allow a traditional numeric-only PSTN device user to
61 access the e-mail transport service, is not discussed here.
62
63 All implementations supporting this PSTN over e-mail service MUST
64 support as a minimum the specification described in this document.
65 The generic complex case of converting the whole PSTN addressing into
66 e-mail is out of scope in this minimal specification: there is some
67 work in progress in the field, where also a number of standard
68 optional extensions are being defined.
69
70 In this document the formal definitions are described using ABNF
71 syntax, as defined into [<a href="#ref-7" title="&quot;Augmented BNF for Syntax Specifications&quot;">7</a>]. We will also use some of the "CORE
72 DEFINITIONS" defined in "APPENDIX A - CORE" of that document. The
73 exact meaning of the capitalised words
74
75 "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
76 "SHOULD NOT", "RECOMMENDED", "MAY", "OPTIONAL"
77
78 is defined in reference [<a href="#ref-6" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">6</a>].
79
80 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Minimal PSTN address</span>
81
82 The minimal specification of a PSTN address in e-mail address is as
83 follows:
84
85 pstn-address = pstn-mbox [ qualif-type1 ]
86
87 pstn-mbox = service-selector "=" global-phone
88
89 service-selector = 1*( DIGIT / ALPHA / "-" )
90 ; note that SP (space) is not allowed in
91 ; service-selector.
92 ; service-selector MUST be handled as a case
93 ; INSENSITIVE string by implementations.
94
95 Specifications adopting the "pstn-address" definition MUST define a
96 unique case insensitive "service-selector" element to identify the
97 specific messaging service involved.
98
99 These specifications MUST also define which minimal "qualif-type1"
100 extensions, if any, MUST be supported for the specified service.
101
102 Implementations confirming to these minimal requirements
103 specification are allowed to ingnore any other non-minimal extensions
104 address element which can be present in the "pstn-address". However,
105
106
107
108 <span class="grey">Allocchio Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2303">RFC 2303</a> Minimal PSTN in Internet Mail March 1998</span>
111
112
113 conforming implementations MUST preserve all "qualif-type1" address
114 elements they receive.
115
116 The generic "qualif-type1" element is defined as:
117
118 qualif-type1 = "/" keyword "=" string
119
120 keyword = 1*( DIGIT / ALPHA / "-" )
121 ; note that SP (space) is not allowed in keyword
122
123 string = PCHAR
124 ; note that printable characters are %x20-7E
125
126 As such, all "pstn-address" extensions elements MUST be defined in
127 the "qualif-type1" form.
128
129 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> Minimal "global-phone" definition</span>
130
131 We now define the minimal supported syntax for global-phone:
132
133 global-phone = "+" 1*( DIGIT , written-sep )
134
135 written-sep = ( "-" / "." )
136
137 The use of other dialling schemas for PSTN numbers (like private
138 numbering plans or local dialling conventions) is also allowed.
139 However, this does not preclude nor remove the minimal compulsory
140 requirement to support the "global-phone" syntax as defined above.
141
142 Any non "global-phone" dialling schema MUST NOT use the leading "+"
143 between the "=" sign and the dialling string. The "+" sign is
144 strictly reserved for the standard "global-phone" syntax.
145
146 Note:
147 The specification of these different dialling schemas is out of
148 scope for this minimal specification.
149
150 User specification of PSTN e-mail addresses will be facilitated if
151 they can insert these separators between dial elements like digits
152 etc. For this reason we allow them in the syntax the written-sep
153 element.
154
155 Implementors' note:
156 Use of the written-sep elements is allowed, but not recommended.
157 Any occurences of written-sep elements in a pstn-mbox MUST be
158 ignored by all conformant implementations. User Agents SHOULD
159 remove written-sep elements before submitting messages to the
160 Message Transport System.
161
162
163
164 <span class="grey">Allocchio Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2303">RFC 2303</a> Minimal PSTN in Internet Mail March 1998</span>
167
168
169 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> Some examples of a minimal "pstn-address"</span>
170
171 VOICE=+3940226338
172
173 FAX=+12027653000/T33S=6377
174
175 SMS=+33-1-88335215
176
177 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The e-mail address of the I-pstn device: mta-I-pstn</span>
178
179 An "I-pstn device" has an e-mail address, or to be more exact, a name
180 which enables a mail system to identify it on the e-mail global
181 system.
182
183 In Internet mail, this is the Right Hand Side (RHS) part of the
184 address, i.e. the part on the right of the "@" sign. We will call
185 this "mta-I-pstn"
186
187 mta-I-pstn = domain
188
189 For "domain" strings used in SMTP transmissions, the string MUST
190 conform to the requirements of that standard's &lt;domain&gt;
191 specifications [<a href="#ref-1" title="&quot;Simple Mail Transfer Protocol&quot;">1</a>], [<a href="#ref-3" title="&quot;Requirements for Internet hosts - application and support&quot;">3</a>]. For "domain" strings used in message
192 content headers, the string MUST conform to the requirements of the
193 relevant standards [<a href="#ref-2" title="&quot; Standard for the format of ARPA Internet text messages&quot;">2</a>], [<a href="#ref-3" title="&quot;Requirements for Internet hosts - application and support&quot;">3</a>].
194
195 Note: in both cases, the standards permit use of "domain names" or
196 "domain literals" in addresses.
197
198
199 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. The pstn-email</span>
200
201 The complete structure used to transfer a minimal PSTN address over
202 the Internet e-mail transport system is called "pstn-email". This
203 object is a an e-mail address which conforms to <a href="./rfc822">RFC822</a> [<a href="#ref-2" title="&quot; Standard for the format of ARPA Internet text messages&quot;">2</a>] and
204 <a href="./rfc1123">RFC1123</a> [<a href="#ref-3" title="&quot;Requirements for Internet hosts - application and support&quot;">3</a>] "addr-spec" syntax, with some extra structure which
205 allows the PSTN number to be identified.
206
207 pstn-email = ["/"] pstn-address ["/"] "@" mta-I-pstn
208
209 Implementors' note:
210 The optional "/" characters can result from other mail transport
211 services gateways, where it is also an optional element.
212 Implementations MUST accept the optional slashes but SHOULD NOT
213 generate them. Gateways are allowed to strip them off when
214 converting to Internet mail addressing.
215
216
217
218
219
220 <span class="grey">Allocchio Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2303">RFC 2303</a> Minimal PSTN in Internet Mail March 1998</span>
223
224
225 It is essential to remind that "pstn-address" element MUST strictly
226 follow the "quoting rules" spcified in the relevant standards [<a href="#ref-2" title="&quot; Standard for the format of ARPA Internet text messages&quot;">2</a>],
227 [<a href="#ref-3" title="&quot;Requirements for Internet hosts - application and support&quot;">3</a>].
228
229 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> Multiple subaddresses</span>
230
231 In case a particular service requires multiple subaddresses (in any
232 form defined by the specific standard specification for that
233 service), and these subaddresses need to be given on the same "pstn-
234 mbox", multiple "pstn-email" elements will be used.
235
236 Implementors' note:
237 The UA could accept multiple subaddress elements for the same
238 global-phone, but it must generate multiple "pstn-mbox" elements
239 when passing the message to the MTA.
240
241 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> Some examples of "pstn-email"</span>
242
243 [email protected]
244
245 FAX=+1.202.7653000/[email protected]
246
247 /SMS=+33-1-88335215/@telecom.com
248
249 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Conclusions</span>
250
251 This proposal creates a minimal standard encoding for PSTN addresses
252 within the global e-mail transport system and defines the standard
253 extension mechanism to be used to introduce specific new elements.
254
255 The proposal requires no changes to existing e-mail software. Each
256 specific PSTN service using this proposal MUST define its own
257 "service-selector" specification and MUST define the eventual other
258 "qualif-type1" elements to be supported for its minimal addressing
259 specification. An example is in reference [<a href="#ref-13" title="&quot; Minimal FAX address format in Internet Mail&quot;">13</a>].
260
261 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
262
263 This document specifies a means by which PSTN addresses can be
264 encoded into e-mail addresses. As routing of e-mail messages is
265 determined by Domain Name System (DNS) information, a successful
266 attack on this service could force the mail path via some particular
267 gateway or message transfer agent where mail security can be affected
268 by compromised software.
269
270 There are several means by which an attacker might be able to deliver
271 incorrect mail routing information to a client. These include: (a)
272 compromise of a DNS server, (b) generating a counterfeit response to
273
274
275
276 <span class="grey">Allocchio Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2303">RFC 2303</a> Minimal PSTN in Internet Mail March 1998</span>
279
280
281 a client's DNS query, (c) returning incorrect "additional
282 information" in response to an unrelated query. Clients SHOULD ensure
283 that mail routing is based only on authoritative answers. Once DNS
284 Security mechanisms [<a href="#ref-5" title="&quot;Domain Name System Security Extensions&quot;">5</a>] become more widely deployed, clients SHOULD
285 employ those mechanisms to verify the authenticity and integrity of
286 mail routing records.
287
288 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Author's Address</span>
289
290 Claudio Allocchio
291 Sincrotrone Trieste
292 SS 14 Km 163.5 Basovizza
293 I 34012 Trieste
294 Italy
295
296 <a href="./rfc822">RFC822</a>: [email protected]
297 X.400: C=it;A=garr;P=Trieste;O=Elettra;
298 S=Allocchio;G=Claudio;
299 Phone: +39 40 3758523
300 Fax: +39 40 3758565
301
302 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
303
304 [<a id="ref-1">1</a>] Postel, J., "Simple Mail Transfer Protocol", STD 10, <a href="./rfc821">RFC 821</a>,
305 August 1982.
306
307 [<a id="ref-2">2</a>] Crocker, D., " Standard for the format of ARPA Internet text
308 messages", STD 11, <a href="./rfc822">RFC 822</a>, August 1982.
309
310 [<a id="ref-3">3</a>] Braden, R., "Requirements for Internet hosts - application and
311 support", <a href="./rfc1123">RFC 1123</a>, October 1989.
312
313 [<a id="ref-4">4</a>] Malamud, C. and M. Rose, "Principles of Operation for the
314 TPC.INT Subdomain: Remote Printing -- Technical Procedures", <a href="./rfc1528">RFC</a>
315 <a href="./rfc1528">1528</a>, October 1993.
316
317 [<a id="ref-5">5</a>] Eastlake, D. and C. Kaufman, "Domain Name System Security
318 Extensions", <a href="./rfc2065">RFC 2065</a>, January 1997.
319
320 [<a id="ref-6">6</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
321 Levels", <a href="./rfc2119">RFC 2119</a>, March 1997.
322
323 [<a id="ref-7">7</a>] Crocker, D. and P. Overell, "Augmented BNF for Syntax
324 Specifications", <a href="./rfc2234">RFC 2234</a>, November 1997.
325
326 [<a id="ref-8">8</a>] ITU F.401 - Message Handling Services: Naming and Addressing for
327 Public Message Handling Service; recommendation F.401 (August
328 1992)
329
330
331
332 <span class="grey">Allocchio Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2303">RFC 2303</a> Minimal PSTN in Internet Mail March 1998</span>
335
336
337 [<a id="ref-9">9</a>] ITU F.423 - Message Handling Services: Intercommunication
338 Between the Interpersonal Messaging Service and the Telefax
339 Service; recommendation F.423 (August 1992)
340
341 [<a id="ref-10">10</a>] ITU E.164 - Numbering plan for the ISDN era; recommendation
342 E.164/I.331 (August 1991)
343
344 [<a id="ref-11">11</a>] ITU T.33 - Facsimile routing utilizing the subaddress;
345 recommendation T.33 (July, 1996)
346
347 [<a id="ref-12">12</a>] ETSI I-ETS 300,380 - Universal Personal Telecommunication
348 (UPT): Access Devices Dual Tone Multi Frequency (DTMF) sender
349 for acoustical coupling to the microphone of a handset telephone
350 (March 1995)
351
352 [<a id="ref-13">13</a>] Allocchio, C., " Minimal FAX address format in Internet Mail",
353 <a href="./rfc2304">RFC 2304</a>, March 1998.
354
355 [<a id="ref-14">14</a>] Kille, S., "MIXER (Mime Internet X.400 Enhanced Relay): Mapping
356 between X.400 and <a href="./rfc822">RFC 822</a>/MIME", <a href="./rfc2156">RFC 2156</a>, January 1998.
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Allocchio Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2303">RFC 2303</a> Minimal PSTN in Internet Mail March 1998</span>
391
392
393 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Full Copyright Statement</span>
394
395 Copyright (C) The Internet Society (1998). All Rights Reserved.
396
397 This document and translations of it may be copied and furnished to
398 others, and derivative works that comment on or otherwise explain it
399 or assist in its implementation may be prepared, copied, published
400 and distributed, in whole or in part, without restriction of any
401 kind, provided that the above copyright notice and this paragraph are
402 included on all such copies and derivative works. However, this
403 document itself may not be modified in any way, such as by removing
404 the copyright notice or references to the Internet Society or other
405 Internet organizations, except as needed for the purpose of
406 developing Internet standards in which case the procedures for
407 copyrights defined in the Internet Standards process must be
408 followed, or as required to translate it into languages other than
409 English.
410
411 The limited permissions granted above are perpetual and will not be
412 revoked by the Internet Society or its successors or assigns.
413
414 This document and the information contained herein is provided on an
415 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
416 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
417 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
418 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
419 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444 Allocchio Standards Track [Page 8]
445 </pre>