1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
|
<pre>Network Working Group K. Toyoda
Request for Comments: 4143 PCC
Category: Standards Track D. Crocker
Brandenburg
November 2005
<span class="h1">Facsimile Using Internet Mail (IFAX) Service of ENUM</span>
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
This document describes the functional specification and definition
of the ENUM Naming Authority Pointer (NAPTR) record for IFax service.
IFax is "facsimile using Internet mail". For this use, the Domain
Name System (DNS) returns the email address of the referenced IFax
system. This mechanism allows email-based fax communication to use
telephone numbers instead of requiring the sender to already know the
recipient email address.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Functional Specification</span>
An IFax client makes a [<a href="#ref-ENUMbis" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">ENUMbis</a>] DNS query, using the target system's
telephone number. The returned NAPTR record specifies an email
address to be used for reaching the target system. The email address
is then used in accordance with Simple Mode of Facsimile using
Internet Mail [<a href="./rfc3965" title=""A Simple Mode of Facsimile Using Internet Mail"">RFC3965</a>], Extended Facsimile using Internet Mail
[<a href="./rfc2532" title="" Extended Facsimile Using Internet Mail"">RFC2532</a>], or Full Mode Fax Profile for Internet Mail [<a href="#ref-FFPIM" title=""Full-mode Fax Profile for Internet Mail (FFPIM)"">FFPIM</a>] is
applied.
The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY"
in this document are to be interpreted as defined in "Key words for
use in RFCs to Indicate Requirement Levels" [<a href="#ref-KEYWORDS" title=""Key words for use in RFCs to Indicate Requirement Levels"">KEYWORDS</a>].
<span class="grey">Toyoda & Crocker Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4143">RFC 4143</a> IFAX service of ENUM November 2005</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. IFax Service Registration</span>
Service Name : "E2U+ifax"
Type: "ifax"
Subtype: "mailto"
URI Scheme: "mailto"
The URI Scheme is "mailto" because facsimile is a profile of standard
Internet mail and uses standard Internet mail addressing.
Functional Specification: See <a href="#section-1">section 1</a>
Security Considerations: See <a href="#section-3">section 3</a>
Intended usage: COMMON
Author: Kiyoshi Toyoda (toyoda.kiyoshi@jp.panasonic.com)
Dave Crocker (dcrocker@bbiw.net)
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
DNS, as used by ENUM, is a globally distributed database. Thus, any
information stored in it is visible to anyone anonymously. Although
this is not qualitatively different from publication in a telephone
directory, it does expose the data subject to automatic data
collection without any indication that this has been done or by whom.
Data harvesting by third parties is often used to generate lists of
targets for unrequested information; in short, the lists are used to
address "spam". The publication of a telephone number in ENUM,
especially when it is an associated Internet fax service, may be used
to send "junk faxes", for example.
In the case of electronic mail, users subscribed to mailing lists can
have "sacrificial" email accounts. These special-purpose addresses
help the user filter out unrequested email. This is not so easy with
published telephone numbers. The PSTN E.164 number assignment
process is much more involved and less flexible; usually a single
E.164 number (or a fixed range of numbers) is associated with each
PSTN access. Thus, it is not possible to use a "sacrificial" phone
number.
Due to the implications of publishing data in a globally accessible
database, as a principle, the data subject MUST give explicit
informed consent to data being published in ENUM.
<span class="grey">Toyoda & Crocker Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4143">RFC 4143</a> IFAX service of ENUM November 2005</span>
Internet Fax is based on existing use of Internet mail. Developers
and users should also consider the Security Consideration sections in
[<a href="./rfc3965" title=""A Simple Mode of Facsimile Using Internet Mail"">RFC3965</a>] and [<a href="./rfc2532" title="" Extended Facsimile Using Internet Mail"">RFC2532</a>].
In addition to the specific security considerations given above, the
Security Considerations section of [<a href="#ref-ENUMbis" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">ENUMbis</a>] applies to this
document.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Example</span>
The following is an example of the use of IFax service in a NAPTR
record.
$ORIGIN 4.3.2.1.6.7.9.8.6.4.e164.arpa
IN NAPTR 10 10 "u" "E2U+ifax:mailto"
"!^.*$!mailto:toyo@example.com!"
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
This specification creates a DNS NAPTR registration, according to the
terms specified in [<a href="#ref-ENUMbis" title=""The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)"">ENUMbis</a>].
The registration details are contained in <a href="#section-2">section 2</a>, Fax Service
Registration.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
[<a id="ref-KEYWORDS">KEYWORDS</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-ENUMbis">ENUMbis</a>] Faltstrom, P. and M. Mealling, "The E.164 to Uniform
Resource Identifiers (URI) Dynamic Delegation Discovery
System (DDDS) Application (ENUM)", <a href="./rfc3761">RFC 3761</a>, April 2004.
[<a id="ref-RFC3965">RFC3965</a>] Toyoda, K., Ohno, H., Murai, J., and D. Wing, "A Simple
Mode of Facsimile Using Internet Mail", <a href="./rfc3965">RFC 3965</a>, December
2004.
[<a id="ref-RFC2532">RFC2532</a>] Masinter, L. and D. Wing, " Extended Facsimile Using
Internet Mail", <a href="./rfc2532">RFC 2532</a>, March 1999.
[<a id="ref-FFPIM">FFPIM</a>] Crocker, D. and G. Klyne, "Full-mode Fax Profile for
Internet Mail (FFPIM)", <a href="./rfc4142">RFC 4142</a>, November 2005.
<span class="grey">Toyoda & Crocker Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4143">RFC 4143</a> IFAX service of ENUM November 2005</span>
Authors' Addresses
Kiyoshi Toyoda
Research and Development Laboratory
Panasonic Communications Co., Ltd.
4-1-62 Minoshima Hakata-ku, Fukuoka 812-8531 Japan
Phone: +81-50-3380-5181
EMail: toyoda.kiyoshi@jp.panasonic.com
Dave Crocker
Brandenburg InternetWorking
675 Spruce Drive
Sunnyvale, CA 94086 USA
Phone: +1.408.246.8253
EMail: dcrocker@bbiw.net
<span class="grey">Toyoda & Crocker Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc4143">RFC 4143</a> IFAX service of ENUM November 2005</span>
Full Copyright Statement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM 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.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Toyoda & Crocker Standards Track [Page 5]
</pre>
|
