Debian Codegraph @

rfc1664.html

raw
1 <pre>Network Working Group C. Allocchio
2 Request for Comments: 1664 A. Bonito
3 Category: Experimental GARR-Italy
4 B. Cole
5 Cisco Systems Inc.
6 S. Giordano
7 Centro Svizzero Calcolo Scientifico
8 R. Hagens
9 Advanced Network &amp; Services
10 August 1994
11
12
13 <span class="h1">Using the Internet DNS to Distribute</span>
14 <span class="h1">RFC1327 Mail Address Mapping Tables</span>
15
16 Status of this Memo
17
18 This memo defines an Experimental Protocol for the Internet
19 community. This memo does not specify an Internet standard of any
20 kind. Distribution of this memo is unlimited.
21
22 Abstract
23
24 This memo defines how to store in the Internet Domain Name System the
25 mapping information needed by e-mail gateways and other tools to map
26 <a href="./rfc822">RFC822</a> domain names into X.400 O/R names and vice versa. Mapping
27 information can be managed in a distributed rather than a centralised
28 way. Gateways located on Internet hosts can retrieve the mapping
29 information querying the DNS instead of having fixed tables which
30 need to be centrally updated and distributed. This memo is a joint
31 effort of X400 operation working group (x400ops) and RARE Mail and
32 Messaging working group (WG-MSG).
33
34 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
35
36 The connectivity between the Internet SMTP mail and other mail
37 services, including the Internet X.400 mail and the commercial X.400
38 service providers, is assured by the Mail eXchanger (MX) record
39 information distributed via the Internet Domain Name System (DNS). A
40 number of documents then specify in details how to convert or encode
41 addresses from/to <a href="./rfc822">RFC822</a> style to the other mail system syntax.
42 However, only conversion methods provide, via some algorithm or a set
43 of mapping rules, a smooth translation, resulting in addresses
44 indistinguishable from the native ones in both <a href="./rfc822">RFC822</a> and foreign
45 world.
46
47 <a href="./rfc1327">RFC1327</a> describes a set of mappings which will enable interworking
48 between systems operating the CCITT X.400 (1984/88) Recommendations
49
50
51
52 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
55
56
57 and systems using the <a href="./rfc822">RFC822</a> mail protocol, or protocols derived from
58 <a href="./rfc822">RFC822</a>. That document addresses conversion of services, addresses,
59 message envelopes, and message bodies between the two mail systems.
60 This document is concerned with one aspect of <a href="./rfc1327">RFC1327</a>: the mechanism
61 for mapping between X.400 O/R addresses and <a href="./rfc822">RFC822</a> domain names. As
62 described in <a href="./rfc1327#appendix-F">Appendix&nbsp;F of RFC1327</a>, implementation of the mappings
63 requires a database which maps between X.400 O/R addresses and domain
64 names, and this database is statically defined.
65
66 This approach requires many efforts to maintain the correct mapping:
67 all the gateways need to get coherent tables to apply the same
68 mappings, the conversion tables must be distributed among all the
69 operational gateways, and also every update needs to be distributed.
70 This static mechanism requires quite a long time to be spent
71 modifying and distributing the information, putting heavy constraints
72 on the time schedule of every update. In fact it does not appear
73 efficient compared to the Internet Domain Name Service (DNS). More
74 over it does not look feasible to distribute the database to a large
75 number of other useful applications, like local address converters,
76 e-mail User Agents or any other tool requiring the mapping rules to
77 produce correct results.
78
79 A first proposal to use the Internet DNS to store, retrieve and
80 maintain those mappings was introduced by two of the authors (B. Cole
81 and R. Hagens) adopting two new DNS resource record (RR) types: TO-
82 X400 and TO-822. This new proposal adopts a more complete strategy,
83 and requires one new RR only. The distribution of the <a href="./rfc1327">RFC1327</a> mapping
84 rules via DNS is in fact an important service for the whole Internet
85 community: it completes the information given by MX resource record
86 and it allows to produce clean addresses when messages are exchanged
87 among the Internet <a href="./rfc822">RFC822</a> world and the X.400 one (both Internet and
88 Public X.400 service providers).
89
90 A first experiment in using the DNS without expanding the current set
91 of RR and using available ones was in the mean time deployed by some
92 of the authors. The existing PTR resource records were used to store
93 the mapping rules, and a new DNS tree was created under the ".it" top
94 level domain. The result of the experiment was positive, and a few
95 test applications ran under this provisional set up. This test was
96 also very useful in order to define a possible migration strategy
97 during the deployment of the new DNS containing the new RR. The
98 Internet DNS nameservers wishing to provide this mapping information
99 need in fact to be modified to support the new RR type, and in the
100 real Internet, due to the large number of different implementations,
101 this takes some time.
102
103 The basic idea is to adopt a new DNS RR to store the mapping
104 information. The <a href="./rfc822">RFC822</a> to X.400 mapping rules (including the so
105
106
107
108 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
111
112
113 called 'gate' rules) will be stored in the ordinary DNS tree, while
114 the definition of a new branch of the name space defined under each
115 national top level domain is envisaged in order to contain the X.400
116 to <a href="./rfc822">RFC822</a> mappings. A "two-way" mapping resolution schema is thus
117 fully implemented.
118
119 The creation of the new domain name space representing the X.400 O/R
120 names structure also provides the chance to use the DNS to distribute
121 dynamically other X.400 related information, thus solving other
122 efficiency problems currently affecting the X.400 MHS service.
123
124 In this paper we will adopt the <a href="./rfc1327">RFC1327</a> mapping rules syntax, showing
125 how it can be stored into the Internet DNS.
126
127 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a> Definitions syntax</span>
128
129 The definitions in this document is given in BNF-like syntax, using
130 the following conventions:
131
132 | means choice
133 \ is used for continuation of a definition over several lines
134 [] means optional
135 {} means repeated one or more times
136
137 The definitions, however, are detailed only until a certain level,
138 and below it self-explaining character text strings will be used.
139
140 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Motivation</span>
141
142 Implementations of <a href="./rfc1327">RFC1327</a> gateways require that a database store
143 address mapping information for X.400 and <a href="./rfc822">RFC822</a>. This information
144 must be disseminated to all <a href="./rfc1327">RFC1327</a> gateways. In the Internet
145 community, the DNS has proven to be a practical mean for providing a
146 distributed name service. Advantages of using a DNS based system over
147 a table based approach for mapping between O/R addresses and domain
148 names are:
149
150 - It avoids fetching and storing of entire mapping tables by every
151 host that wishes to implement <a href="./rfc1327">RFC1327</a> gateways and/or tools
152
153 - Modifications to the DNS based mapping information can be made
154 available in a more timely manner than with a table driven
155 approach.
156
157 - It allows full authority delegation, in agreement with the
158 Internet regionalization process.
159
160
161
162
163
164 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
167
168
169 - Table management is not necessarily required for DNS-based
170 <a href="./rfc1327">RFC1327</a> gateways.
171
172 - One can determine the mappings in use by a remote gateway by
173 querying the DNS (remote debugging).
174
175 Also many other tools, like address converters and User Agents can
176 take advantage of the real-time availability of <a href="./rfc1327">RFC1327</a> tables,
177 allowing a much easier maintenance of the information.
178
179 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. The domain space for X.400 O/R name addresses</span>
180
181 Usual domain names (the ones normally used as the global part of an
182 <a href="./rfc822">RFC822</a> e-mail address) and their associated information, i.e., host
183 IP addresses, mail exchanger names, etc., are stored in the DNS as a
184 distributed database under a number of top-level domains. Some top-
185 level domains are used for traditional categories or international
186 organisations (EDU, COM, NET, ORG, INT, MIL...). On the other hand
187 any country has its own two letter ISO country code as top-level
188 domain (FR, DE, GB, IT, RU, ...), including "US" for USA. The
189 special top-level/second-level couple IN-ADDR.ARPA is used to store
190 the IP address to domain name relationship. Our proposal defines in
191 the above structure the appropriate way to locate the X.400 O/R name
192 space, thus enabling us to store in DNS the <a href="./rfc1327">RFC1327</a> mapping data.
193
194 The <a href="./rfc1327">RFC1327</a> mapping information is composed by three tables: 'table1'
195 gives the translation from X.400 to <a href="./rfc822">RFC822</a> while 'table2' and 'gate'
196 tables map <a href="./rfc822">RFC822</a> into X.400. Each mapping table is composed by
197 mapping rules, and a single mapping rule is composed by a keyword
198 (the argument of the mapping function derived from the address to be
199 translated) and a translator (the mapping function parameter):
200
201 keyword#translator#
202
203 the '#' sign is a delimiter enclosing the translator. An example:
204
205 foo.bar.us#PRMD$foo\.bar.ADMD$intx.C$us#
206
207 Local mappings are not intended for use outside their restricted
208 environment, thus they should not be included in DNS. If local
209 mappings are used, they should be stored using static local tables,
210 exactly as local static host tables can be used with DNS.
211
212 The keyword of a 'table2' and 'gate' table entry is a valid <a href="./rfc822">RFC822</a>
213 domain; thus the usual domain name space can be used without problems
214 to store these entries.
215
216
217
218
219
220 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
223
224
225 On the other hand, the keyword of a 'table1' entry belongs to the
226 X.400 O/R name space. The X.400 O/R name space does not usually fit
227 into the usual domain name space, although there are a number of
228 similarities; a new name structure is thus needed to represent it.
229 This new name structure contains the X.400 mail domains.
230
231 To ensure the correct functioning of the DNS system, the new X.400
232 name structure must be hooked to the existing domain name space in a
233 way which respects the existing name hierarchy.
234
235 A possible solution was to create another special branch, starting
236 from the root of the DNS tree, somehow similar to the in-addr.arpa
237 tree. This idea would have required to establish a central authority
238 to coordinate at international level the management of each national
239 X.400 name tree, including the X.400 public service providers. This
240 coordination problem is a heavy burden if approached globally. More
241 over the X.400 name structure is very 'country oriented': thus while
242 it requires a coordination at national level, it does not have
243 concepts like the international root. In fact the X.400 international
244 service is based on a large number of bilateral agreements, and only
245 within some communities an international coordination service exists.
246
247 The X.400 two letter ISO country codes, however, are the same used
248 for the <a href="./rfc822">RFC822</a> country top-level domains and this gives us an
249 appropriate hook to insert the new branches. Our proposal is, in
250 fact, to create under each national top level ISO country code a new
251 branch in the name space. This branch represents exactly the X.400
252 O/R name structure as defined in each single country, following the
253 ADMD, PRMD, O, OU hierarchy. A unique reserved label 'X42D' is placed
254 under each country top-level domain, and hence the national X.400
255 name space derives its own structure:
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
279
280
281 . (root)
282 |
283 +-----------------+-----------+--------+-----------------+...
284 | | | |
285 edu it us fr
286 | | | |
287 +---+---+... +-----+-----+... +-----+-----+... +--+---+...
288 | | | | | | | | | |
289 ... ... cnr X42D infn va ca X42D X42D inria
290 | | | |
291 +------------+------------+... ... ... +----+-------+...
292 | | | | |
293 ADMD-PtPostel ADMD-garr ADMD-Master400 ADMD-atlas ADMD-red
294 | | | |
295 +----------+----+... ... +-------+------+... ...
296 | | | |
297 PRMD-infn PRMD-STET PRMD-Telecom PRMD-Renault
298 | | | |
299 ... ... ... ...
300
301
302 The creation of the X.400 new name tree at national level solves the
303 problem of the international coordination. Actually the coordination
304 problem is just moved at national level, but it thus becomes easier
305 to solve. The coordination at national level between the X.400
306 communities and the Internet world is already a requirement for the
307 creation of the national static <a href="./rfc1327">RFC1327</a> mapping tables; the use of
308 the Internet DNS gives further motivations for this coordination.
309
310 The coordination at national level also fits in the ongoing proposal
311 intended to define exactly the <a href="./rfc1327">RFC1327</a> Mapping Authorities. The DNS
312 in fact allows a step by step authority distribution, up to a final
313 complete delegation, which can be easily controlled at national level
314 accordingly with national needs and situations. A further advantage
315 of the national based solution is to allow each country to set up its
316 own X.400 name structure in DNS and to deploy its own authority
317 delegation according to its local time scale and requirements, with
318 no loss of global service in the mean time. And last, placing the new
319 X.400 name tree and coordination process at national level fits into
320 the Internet regionalization and internationalisation process, as it
321 requires local bodies to take care of local coordination problems.
322
323 The DNS name space thus contains completely the information required
324 by an e-mail gateway or tool to perform the X.400-RFC822 mapping: a
325 simple query to the nearest nameserver provides it. Moreover there is
326 no more any need to store, maintain and distribute manually any
327 mapping table. The new X.400 name space can also contain further
328 information about the X.400 community, as DNS allows for it a
329
330
331
332 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
335
336
337 complete set of resource records, and thus it allows further
338 developments. This set of RRs in the new X.400 name space must be
339 considered 'reserved' and thus not used until further specifications.
340
341 The construction of the new domain space trees will follow the same
342 procedures used when organising at first the already existing DNS
343 space: at first the information will be stored in a quite centralised
344 way, and distribution of authority will be gradually achieved. A
345 separate document will describe the implementation phase and the
346 methods to assure a smooth introduction of the new service.
347
348 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. The new DNS resource record for <a href="./rfc1327">RFC1327</a> mapping rules: PX</span>
349
350 The specification of the Internet DNS (<a href="./rfc1035">RFC1035</a>) provides a number of
351 specific resource records (RRs) to contain specific pieces of
352 information. In particular they contain the Mail eXchanger (MX) RR
353 and the host Address (A) records which are used by the Internet SMTP
354 mailers. As we will store the <a href="./rfc822">RFC822</a> to X.400 mapping information in
355 the already existing DNS name tree, we need to define a new DNS RR in
356 order to avoid any possible clash or misuse of already existing data
357 structures. The same new RR will also be used to store the mappings
358 from X.400 to <a href="./rfc822">RFC822</a>. More over the mapping information, i.e., the
359 <a href="./rfc1327">RFC1327</a> mapping rules, has a specific format and syntax which require
360 an appropriate data structure and processing. A further advantage of
361 defining a new RR is the ability to include flexibility for some
362 eventual future development.
363
364 The definition of the new 'PX' DNS resource record is:
365
366 class: IN (Internet)
367
368 name: PX (pointer to X.400/RFC822 mapping information)
369
370 value: 26
371
372 The PX RDATA format is:
373
374 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
375 | PREFERENCE |
376 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
377 / MAP822 /
378 / /
379 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
380 / MAPX400 /
381 / /
382 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
383
384 where:
385
386
387
388 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
391
392
393 PREFERENCE A 16 bit integer which specifies the preference given to
394 this RR among others at the same owner. Lower values
395 are preferred;
396
397 MAP822 A &lt;domain-name&gt; element containing &lt;<a href="./rfc822">rfc822</a>-domain&gt;, the
398 <a href="./rfc822">RFC822</a> part of the <a href="./rfc1327">RFC1327</a> mapping information;
399
400 MAPX400 A &lt;domain-name&gt; element containing the value of
401 &lt;x400-in-domain-syntax&gt; derived from the X.400 part of
402 the <a href="./rfc1327">RFC1327</a> mapping information (see sect. 4.2);
403
404 PX records cause no additional section processing. The PX RR format
405 is the usual one:
406
407 &lt;name&gt; [&lt;class&gt;] [&lt;TTL&gt;] &lt;type&gt; &lt;RDATA&gt;
408
409 When we store in DNS a 'table1' entry, then &lt;name&gt; will be an X.400
410 mail domain name in DNS syntax (see sect. 4.2). When we store a
411 'table2' or a 'gate' table entry, &lt;name&gt; will be an <a href="./rfc822">RFC822</a> mail
412 domain name, including both fully qualified DNS domains and mail only
413 domains (MX-only domains). All normal DNS conventions, like default
414 values, wildcards, abbreviations and message compression, apply also
415 for all the components of the PX RR. In particular &lt;name&gt;, MAP822 and
416 MAPX400, as &lt;domain-name&gt; elements, must have the final "." (root)
417 when they are fully qualified.
418
419 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> Additional features of the PX resource record</span>
420
421 The definition of the RDATA for the PX resource record, and the fact
422 that DNS allows a distinction between an exact value and a wildcard
423 match for the &lt;name&gt; parameter, represent an extension of the <a href="./rfc1327">RFC1327</a>
424 specification for mapping rules. In fact, any <a href="./rfc1327">RFC1327</a> mapping table
425 entry is an implicit wildcard entry, i.e., the rule
426
427 net2.it#PRMD$net2.ADMD$p400.C$it#
428
429 covers any <a href="./rfc822">RFC822</a> domain ending with 'net2.it', unless more detailed
430 rules for some subdomain in 'net2.it' are present. Thus there is no
431 possibility to specify explicitly an <a href="./rfc1327">RFC1327</a> entry as an exact match
432 only rule. In DNS an entry like
433
434 *.net2.it. IN PX 10 net2.it. PRMD-net2.ADMD-p400.C-it.
435
436 specify the usual wildcard match as for <a href="./rfc1327">RFC1327</a> tables. However an
437 entry like
438
439 ab.net2.it. IN PX 10 ab.net2.it. O-ab.PRMD-net2.ADMDb.C-it.
440
441
442
443
444 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
447
448
449 is valid only for an exact match of 'ab.net2.it' <a href="./rfc822">RFC822</a> domain.
450
451 Note also that in DNS syntax there is no '#' delimiter around MAP822
452 and MAPX400 fields: the syntax defined in sect. 4.2 in fact does not
453 allow the &lt;blank&gt; (ASCII decimal 32) character within these fields,
454 making unneeded the use of an explicit delimiter as required in the
455 <a href="./rfc1327">RFC1327</a> original syntax.
456
457 Another extension to the <a href="./rfc1327">RFC1327</a> specifications is the PREFERENCE
458 value defined as part of the PX RDATA section. This numeric value has
459 exactly the same meaning than the similar one used for the MX RR. It
460 is thus possible to specify more than one single mapping for a domain
461 (both from <a href="./rfc822">RFC822</a> to X.400 and vice versa), giving as the preference
462 order. In <a href="./rfc1327">RFC1327</a> static tables, however, you cannot specify more
463 than one mapping per each <a href="./rfc822">RFC822</a> domain, and the same restriction
464 apply for any X.400 domain mapping to an <a href="./rfc822">RFC822</a> one.
465
466 More over, in the X.400 recommendations a note suggests than an
467 ADMD=&lt;blank&gt; should be reserved for some special cases. Various
468 national functional profile specifications for an X.400 MHS states
469 that if an X.400 PRMD is reachable via any of its national ADMDs,
470 independently of its actual single or multiple connectivity with
471 them, it should use ADMD=&lt;blank&gt; to advertise this fact. Again, if a
472 PRMD has no connections to any ADMD it should use ADMD=0 to notify
473 its status, etc. However, in most of the current real situations, the
474 ADMD service providers do not accept messages coming from their
475 subscribers if they have a blank ADMD, forcing them to have their own
476 ADMD value. In such a situation there are problems in indicating
477 properly the actually working mappings for domains with multiple
478 connectivity. The PX RDATA 'PREFERENCE' extension was introduced to
479 take in consideration these problems.
480
481 However, as these extensions are not available with <a href="./rfc1327">RFC1327</a> static
482 tables, it is strongly discouraged to use them when interworking with
483 any table based gateway or application. The extensions were in fact
484 introduced just to add more flexibility, like the PREFERENCE value,
485 or they were already implicit in the DNS mechanism, like the wildcard
486 specification. They should be used very carefully or just considered
487 'reserved for future use'. In particular, for current use, the
488 PREFERENCE value in the PX record specification should be fixed to a
489 value of 50, and only wildcard specifications should be used when
490 specifying &lt;name&gt; values.
491
492 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> The DNS syntax for an X.400 'domain'</span>
493
494 The syntax definition of the <a href="./rfc1327">RFC1327</a> mapping rules is defined in
495 <a href="#appendix-F">appendix F</a> of that document. However that syntax is not very human
496 oriented and contains a number of characters which have a special
497
498
499
500 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
503
504
505 meaning in other fields of the Internet DNS. Thus in order to avoid
506 any possible problem, especially due to some old DNS implementations
507 still being used in the Internet, we define a syntax for the X.400
508 part of any <a href="./rfc1327">RFC1327</a> mapping rules (and hence for any X.400 O/R name)
509 which makes it compatible with a &lt;domain-name&gt; element, i.e.,
510
511 &lt;domain-name&gt; ::= &lt;subdomain&gt; | " "
512 &lt;subdomain&gt; ::= &lt;label&gt; | &lt;label&gt; "." &lt;subdomain&gt;
513 &lt;label&gt; ::= &lt;alphanum&gt;|
514 &lt;alphanum&gt; {&lt;alphanumhyphen&gt;} &lt;alphanum&gt;
515 &lt;alphanum&gt; ::= "0".."9" | "A".."Z" | "a".."z"
516 &lt;alphanumhyphen&gt; ::= "0".."9" | "A".."Z" | "a".."z" | "-"
517
518 (see <a href="./rfc1035#section-2.3.1">RFC1035, section&nbsp;2.3.1</a>, page 8). The legal character set for
519 &lt;label&gt; does not correspond to the IA5 Printablestring one used in
520 <a href="./rfc1327">RFC1327</a> to define mapping rules. However a very simple "escape
521 mechanism" can be applied in order to bypass the problem. We can in
522 fact simply describe the X.400 part of an <a href="./rfc1327">RFC1327</a> mapping rule format
523 as:
524
525 &lt;map-rule&gt; ::= &lt;map-elem&gt; | &lt;map-elem&gt; { "." &lt;map-elem&gt; }
526 &lt;map-elem&gt; ::= &lt;attr-label&gt; "$" &lt;attr-value&gt;
527 &lt;attr-label&gt; ::= "C" | "ADMD" | "PRMD" | "O" | "OU"
528 &lt;attr-value&gt; ::= " " | "@" | IA5-Printablestring
529
530 As you can notice &lt;domain-name&gt; and &lt;map-rule&gt; look similar, and also
531 &lt;label&gt; and &lt;map-elem&gt; look the same. If we define the correct method
532 to transform a &lt;map-elem&gt; into a &lt;label&gt; and vice versa the problem
533 to write an <a href="./rfc1327">RFC1327</a> mapping rule in &lt;domain-name&gt; syntax is solved.
534
535 The <a href="./rfc822">RFC822</a> domain part of any <a href="./rfc1327">RFC1327</a> mapping rule is of course
536 already in &lt;domain-name&gt; syntax, and thus remains unchanged.
537
538 In particular, in a 'table1' mapping rule the 'keyword' value must be
539 converted into &lt;x400-in-domain-syntax&gt; (X.400 mail DNS mail domain),
540 while the 'translator' value is already a valid <a href="./rfc822">RFC822</a> domain. Vice
541 versa in a 'table2' or 'gate' mapping rule, the 'translator' must be
542 converted into &lt;x400-in-domain-syntax&gt;, while the 'keyword' is
543 already a valid <a href="./rfc822">RFC822</a> domain.
544
545 <span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a> IA5-Printablestring to &lt;alphanumhyphen&gt; mappings</span>
546
547 The problem of unmatching IA5-Printablestring and &lt;label&gt; character
548 set definition is solved by a simple character mapping rule: whenever
549 an IA5 character does not belong to &lt;alphanumhyphen&gt;, then it is
550 mapped using its 3 digit decimal ASCII code, enclosed in hyphens. A
551 small set of special rules is also defined for the most frequent
552 cases. Moreover some frequent characters combinations used in <a href="./rfc1327">RFC1327</a>
553
554
555
556 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
559
560
561 rules are also mapped as special cases.
562
563 Let's then define the following simple rules:
564
565 <a href="./rfc1327">RFC1327</a> rule DNS store translation conditions
566 -----------------------------------------------------------------
567 &lt;attr-label&gt;$@ &lt;attr-label&gt; missing attribute
568 &lt;attr-label&gt;$&lt;blank&gt; &lt;attr-label&gt;"b" blank attribute
569 &lt;attr-label&gt;$xxx &lt;attr-label&gt;-xxx elsewhere
570
571 Non &lt;alphanumhyphen&gt; characters in &lt;attr-value&gt;:
572
573 <a href="./rfc1327">RFC1327</a> rule DNS store translation conditions
574 -----------------------------------------------------------------
575 - -h- hyphen
576 \. -d- quoted dot
577 &lt;blank&gt; -b- blank
578 &lt;non A/N character&gt; -&lt;3digit-decimal&gt;- elsewhere
579
580 If the DNS store translation of &lt;attr-value&gt; happens to end with an
581 hyphen, then this last hyphen is omitted.
582
583 Let's now have some examples:
584
585 <a href="./rfc1327">RFC1327</a> rule DNS store translation conditions
586 -----------------------------------------------------------------
587 PRMD$@ PRMD missing attribute
588 ADMD$&lt;blank&gt; ADMDb blank attribute
589 ADMD$400-net ADMD-400-h-net hyphen mapping
590 PRMD$UK\.BD PRMD-UK-d-BD quoted dot mapping
591 O$ACME Inc\. O-ACME-b-Inc-d blank &amp; final hyphen
592 PRMD$main-400-a PRMD-main-h-400-h-a hyphen mapping
593 O$-123-b O--h-123-h-b hyphen mapping
594 OU$123-x OU-123-h-x hyphen mapping
595 PRMD$Adis+co PRMD-Adis-043-co 3digit mapping
596
597 Thus, an X.400 part from an <a href="./rfc1327">RFC1327</a> mapping rule like
598
599 [email protected]$ppp\.rrr.ADMD$aaa ddd-mmm.C$cc
600
601 translates to
602
603 OU-uuu.O.PRMD-ppp-d-rrr.ADMD-aaa-b-ddd-h-mmm.C-cc
604
605 Another example:
606
607 OU$sales dept\[email protected]$ACME.ADMD$ .C$GB
608
609
610
611
612 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
615
616
617 translates to
618
619 OU-sales-b-dept-d.O.PRMD-ACME.ADMDb.C-GB
620
621 <span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a> Flow chart</span>
622
623 In order to achieve the proper DNS store translations of the X.400
624 part of an <a href="./rfc1327">RFC1327</a> mapping rules or any other X.400 O/R name, some
625 software tools will be used. It is in fact evident that the above
626 rules for converting mapping table from <a href="./rfc1327">RFC1327</a> to DNS format (and
627 vice versa) are not user friendly enough to think of a human made
628 conversion.
629
630 To help in designing such tools, we describe hereunder a small flow
631 chart. The fundamental rule to be applied during translation is,
632 however, the following:
633
634 "A string must be parsed from left to right, moving appropriately
635 the pointer in order not to consider again the already translated
636 left section of the string in subsequent analysis."
637
638 Flow chart 1 - Translation from <a href="./rfc1327">RFC1327</a> to DNS format:
639
640
641 parse single attribute
642 (enclosed in "." separators)
643 |
644 (yes) --- &lt;label&gt;$@ ? --- (no)
645 | |
646 map to &lt;label&gt; (no) &lt;label&gt;$&lt;blank&gt; ? (yes)
647 | | |
648 | map to &lt;label&gt;- map to &lt;label&gt;"b"
649 | | |
650 | map "\." to -d- |
651 | | |
652 | map "-" to -h- |
653 | | |
654 | map non A/N char to -&lt;3digit&gt;- |
655 restart | | |
656 ^ | remove (if any) last "-" |
657 | | | |
658 | \-------&gt; add a "." &lt;--------------/
659 | |
660 \---------- take next attribute (if any)
661
662
663
664
665
666
667
668 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
671
672
673 Flow chart 2 - Translation from DNS to <a href="./rfc1327">RFC1327</a> format:
674
675
676 parse single attribute
677 (enclosed in "." separators)
678 |
679 (yes) ---- &lt;label&gt; ? ---- (no)
680 | |
681 map to &lt;label&gt;$@ (no) &lt;label&gt;"b" ? (yes)
682 | | |
683 | map to &lt;label&gt;$ map to &lt;label&gt;$&lt;blank&gt;
684 | | |
685 | map -d- to "\." |
686 | | |
687 | map -h- to "-" |
688 | | |
689 | map -b- to " " |
690 restart | | |
691 ^ | map -&lt;3digit&gt;- to non A/N char |
692 | | | |
693 | \--------&gt; add a "." &lt;----------/
694 | |
695 \------------- take next attribute (if any)
696
697
698 Note that the above flow charts deal with the translation of the
699 attributes syntax, only.
700
701 <span class="h4"><a class="selflink" id="section-4.2.3" href="#section-4.2.3">4.2.3</a> The Country Code convention in the &lt;name&gt; value.</span>
702
703 The <a href="./rfc822">RFC822</a> domain space and the X.400 O/R address space, as said in
704 <a href="#section-3">section 3</a>, have one specific common feature: the X.400 ISO country
705 codes are the same as the <a href="./rfc822">RFC822</a> ISO top level domains for countries.
706 In the previous sections we have also defined a method to write in
707 &lt;domain-name&gt; syntax any X.400 domain, while in <a href="#section-3">section 3</a> we
708 described the new name space starting at each country top level
709 domain under the X42D.cc (where 'cc' is then two letter ISO country
710 code).
711
712 The &lt;name&gt; value for a 'table1' entry in DNS should thus be derived
713 from the X.400 domain value, translated to &lt;domain-name&gt; syntax,
714 adding the 'X42D.cc.' post-fix to it, i.e.,
715
716 ADMD$acme.C$fr
717
718 produces in &lt;domain-name&gt; syntax the key:
719
720 ADMD-acme.C-fr
721
722
723
724 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
727
728
729 which is post-fixed by 'X42D.fr.' resulting in:
730
731 ADMD-acme.C-fr.X42D.fr.
732
733 However, due to the identical encoding for X.400 country codes and
734 <a href="./rfc822">RFC822</a> country top level domains, the string 'C-fr.X42D.fr.' is
735 clearly redundant.
736
737 We thus define the 'Country Code convention' for the &lt;name&gt; key,
738 i.e.,
739
740 "The C-cc section of an X.400 domain in &lt;domain-name&gt; syntax must
741 be omitted when creating a &lt;name&gt; key, as it is identical to the
742 top level country code used to identify the DNS zone where the
743 information is stored".
744
745 Thus we obtain the following &lt;name&gt; key examples:
746
747 X.400 domain DNS &lt;name&gt; key
748 --------------------------------------------------------------------
749 ADMD$acme.C$fr ADMD-acme.X42D.fr.
750 PRMD$ux\.av.ADMD$ .C$gb PRMD-ux-d-av.ADMDb.X42D.gb.
751 PRMD$ppb.ADMD$Dat 400.C$de PRMD-ppb.ADMD-Dat-b-400.X42D.de.
752
753 <span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a> Creating the appropriate DNS files</span>
754
755 Using <a href="./rfc1327">RFC1327</a>'s assumption of an asymmetric mapping between X.400 and
756 <a href="./rfc822">RFC822</a> addresses, two separate relations are required to store the
757 mapping database: <a href="./rfc1327">RFC1327</a> 'table1' and <a href="./rfc1327">RFC1327</a> 'table2'; thus also in
758 DNS we will maintain the two different sections, even if they will
759 both use the PX resource record. More over <a href="./rfc1327">RFC1327</a> also specify a
760 third table: <a href="./rfc1327">RFC1327</a> 'gate' Table. This additional table, however,
761 has the same syntax rules than <a href="./rfc1327">RFC1327</a> 'table2' and thus the same
762 translation procedure as 'table2' will be applied; some details about
763 the <a href="./rfc1327">RFC1327</a> 'gate' table are discussed in <a href="#section-4.4">section 4.4</a>.
764
765 Let's now check how to create, from an <a href="./rfc1327">RFC1327</a> mapping rule entry,
766 the appropriate DNS entry in a DNS data file. We can again define an
767 <a href="./rfc1327">RFC1327</a> mapping rule entry as defined in <a href="#appendix-F">appendix F</a> of that document
768 as:
769
770 &lt;x400-domain&gt;#&lt;<a href="./rfc822">rfc822</a>-domain&gt;# (case A: 'table1' entry)
771
772 and
773
774 &lt;<a href="./rfc822">rfc822</a>-domain&gt;#&lt;x400-domain&gt;# (case B: 'table2' and 'gate' entry)
775
776 The two cases must be considered separately. Let's consider case A.
777
778
779
780 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
783
784
785 - take &lt;x400-domain&gt; and translate it into &lt;domain-name&gt; syntax,
786 obtaining &lt;x400-in-domain-syntax&gt;;
787 - create the &lt;name&gt; key from &lt;x400-in-domain-syntax&gt; i.e., apply
788 the Country Code convention described in sect. 4.2.3;
789 - construct the DNS PX record as:
790
791 *.&lt;name&gt; IN PX 50 &lt;<a href="./rfc822">rfc822</a>-domain&gt; &lt;x400-in-domain-syntax&gt;
792
793 Please note that within PX RDATA the &lt;<a href="./rfc822">rfc822</a>-domain&gt; precedes the
794 &lt;x400-in-domain-syntax&gt; also for a 'table1' entry.
795
796 an example: from the rule
797
798 PRMD$ab.ADMD$ac.C$fr#ab.fr#
799
800 we obtain
801
802 *.PRMD-ab.ADMD-ac.X42D.fr. IN PX 50 ab.fr. PRMD-ab.ADMD-ac.C-fr.
803
804 Note that &lt;name&gt;, &lt;<a href="./rfc822">rfc822</a>-domain&gt; and &lt;x400-in-domain-syntax&gt; are
805 fully qualified &lt;domain-name&gt; elements, thus ending with a ".".
806
807 Let's now consider case B.
808
809 - take &lt;<a href="./rfc822">rfc822</a>-domain&gt; as &lt;name&gt; key;
810 - translate &lt;x400-domain&gt; into &lt;x400-in-domain-syntax&gt;;
811 - construct the DNS PX record as:
812
813 *.&lt;name&gt; IN PX 50 &lt;<a href="./rfc822">rfc822</a>-domain&gt; &lt;x400-in-domain-syntax&gt;
814
815 an example: from the rule
816
817 ab.fr#PRMD$ab.ADMD$ac.C$fr#
818
819 we obtain
820
821 *.ab.fr. IN PX 50 ab.fr. PRMD-ab.ADMD-ac.C-fr.
822
823 Again note the fully qualified &lt;domain-name&gt; elements.
824
825
826
827
828
829
830
831
832
833
834
835
836 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
839
840
841 A file containing the <a href="./rfc1327">RFC1327</a> mapping rules and <a href="./rfc1327">RFC1327</a> 'gate' table
842 written in DNS format will look like the following fictious example:
843
844 !
845 ! <a href="./rfc1327">RFC1327</a> table 1: X.400 --&gt; <a href="./rfc822">RFC822</a>
846 !
847 *.ADMD-acme.X42D.it. IN PX 50 it. ADMD-acme.C-it.
848 *.PRMD-accred.ADMD-tx400.X42D.it. IN PX 50 \
849 accred.it. PRMD-accred.ADMD-tx400.C-it.
850 *.O-u-h-newcity.PRMD-x4net.ADMDb.X42D.it. IN PX 50 \
851 cs.ncty.it. O-u-h-newcity.PRMD-x4net.ADMDb.C-it.
852 !
853 ! <a href="./rfc1327">RFC1327</a> table 2: <a href="./rfc822">RFC822</a> --&gt; X.400
854 !
855 *.nrc.it. IN PX 50 nrc.it. PRMD-nrc.ADMD-acme.C-it.
856 *.ninp.it. IN PX 50 ninp.it. O.PRMD-ninp.ADMD-acme.C-it.
857 *.bd.it. IN PX 50 bd.it. PRMD-uk-d-bd.ADMDb.C-it.
858 !
859 ! <a href="./rfc1327">RFC1327</a> Gate Table
860 !
861 my.it. IN PX 50 my.it. OU-int-h-gw.O.PRMD-ninp.ADMD-acme.C-it.G.
862 co.it. IN PX 50 co.it. O-mhs-h-relay.PRMD-x4net.ADMDb.C-it.G.
863
864 (here the "\" indicates continuation on the same line, as wrapping is
865 done only due to typographical reasons).
866
867 Note the special suffix ".G." on the right side of the 'gate' Table
868 section whose aim is described in <a href="#section-4.4">section 4.4</a>. The corresponding
869 <a href="./rfc1327">RFC1327</a> tables are:
870
871
872 #
873 # <a href="./rfc1327">RFC1327</a> table 1: X.400 --&gt; <a href="./rfc822">RFC822</a>
874 #
875 ADMD$acme.C$it#it#
876 PRMD$accred.ADMD$tx400.C$it#accred.it#
877 O$u-newcity.PRMD$x4net.ADMD$ .C$it#cs.ncty.it#
878 #
879 # <a href="./rfc1327">RFC1327</a> table 2: <a href="./rfc822">RFC822</a> --&gt; X.400
880 #
881 nrc.it#PRMD$nrc.ADMD$acme.C$it#
882 ninp.it#O.PRMD$ninp.ADMD$acme.C$it#
883 bd.it#PRMD$uk\.bd.ADMD$ .C$it#
884 #
885 # <a href="./rfc1327">RFC1327</a> Gate Table
886 #
887 my.it#[email protected]$ninp.ADMD$acme.C$it#
888 co.it#O$mhs-relay.PRMD$x4net.ADMD$ .C$t#
889
890
891
892 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
895
896
897 <span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a> Storing the <a href="./rfc1327">RFC1327</a> Gate table</span>
898
899 <a href="./rfc1327#section-4.3.4">Section&nbsp;4.3.4 of RFC1327</a> also specify how an address should be
900 converted between <a href="./rfc822">RFC822</a> and X.400 in case a complete mapping is
901 impossible. To allow the use of DDAs for non mappable domains, the
902 <a href="./rfc1327">RFC1327</a> 'gate' table is thus introduced. DNS must store and
903 distribute also these data.
904
905 One of the major features of the DNS is the ability to distribute the
906 authority: a certain site runs the "primary" nameserver for one
907 determined sub-tree and thus it is also the only place allowed to
908 update information regarding that sub-tree. This fact allows, in our
909 case, a further additional feature to the table based approach. In
910 fact we can avoid one possible ambiguity about the use of the 'gate'
911 table (and thus of DDAs encoding).
912
913 The authority maintaining a DNS entry in the usual <a href="./rfc822">RFC822</a> domain
914 space is the only one allowed to decide if its domain should be
915 mapped using Standard Attributes (SA) syntax or Domain Defined
916 Attributes (DDA) one. If the authority decides that its <a href="./rfc822">RFC822</a> domain
917 should be mapped using SA, then the PX RDATA will be a 'table2'
918 entry, otherwise it will be a 'gate' table entry. Thus for an <a href="./rfc822">RFC822</a>
919 domain we cannot have any more two possible entries, one from 'table2
920 and another one from 'gate' table, and the action for a gateway
921 results clearly stated.
922
923 The <a href="./rfc1327">RFC1327</a> 'gate' table syntax is actually identical to <a href="./rfc1327">RFC1327</a>
924 'table2'. Thus the same syntax translation rules from <a href="./rfc1327">RFC1327</a> to DNS
925 format can be applied. However a gateway or any other application
926 must know if the answer it got from DNS contains some 'table2' or
927 some 'gate' table information. This is easily obtained flagging with
928 an additional ".G." post-fix the PX RDATA value when it contains a
929 'gate' table entry. The example in <a href="#section-4.3">section 4.3</a> shows clearly the
930 result. As any X.400 O/R domain must end with a country code ("C-xx"
931 in our DNS syntax) the additional ".G." creates no conflicts or
932 ambiguities at all. This postfix must obviously be removed before
933 using the <a href="./rfc1327">RFC1327</a> 'gate' table data.
934
935 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Finding <a href="./rfc1327">RFC1327</a> mapping information from DNS</span>
936
937 The <a href="./rfc1327">RFC1327</a> mapping information is stored in DNS both in the normal
938 <a href="./rfc822">RFC822</a> domain name space, and in the newly defined X.400 name space.
939 The information, stored in PX resource records, does not represent a
940 full <a href="./rfc822">RFC822</a> or X.400 O/R address: it is a template which specifies
941 the fields of the domain that are used by the mapping algorithm.
942
943 When mapping information is stored in the DNS, queries to the DNS are
944 issued whenever an iterative search through the mapping table would
945
946
947
948 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
951
952
953 be performed (<a href="./rfc1327">RFC1327</a>: <a href="#section-4.3.4">section 4.3.4</a>, State I; <a href="#section-4.3.5">section 4.3.5</a>, mapping
954 B). Due to the DNS search mechanism, DNS by itself returns the
955 longest possible match in the stored mapping rule with a single
956 query, thus no iteration and/or multiple queries are needed. As
957 specified in <a href="./rfc1327">RFC1327</a>, a search of the mapping table will result in
958 either success (mapping found) or failure (query failed, mapping not
959 found).
960
961 When a DNS query is issued, a third possible result is timeout. If
962 the result is timeout, the gateway operation is delayed and then
963 retried at a later time. A result of success or failure is processed
964 according to the algorithms specified in <a href="./rfc1327">RFC1327</a>. If a DNS error code
965 is returned, an error message should be logged and the gateway
966 operation is delayed as for timeout. These pathological situations,
967 however, should be avoided with a careful duplication and chaching
968 mechanism which DNS itself provides.
969
970 Searching the nameserver which can authoritatively solve the query is
971 automatically performed by the DNS distributed name service.
972
973 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a> A DNS query example</span>
974
975 An <a href="./rfc1327">RFC1327</a> mail-gateway located in the Internet, when translating
976 addresses from <a href="./rfc822">RFC822</a> to X.400, can get information about the <a href="./rfc1327">RFC1327</a>
977 mapping rule asking the DNS. As an example, when translating the
978 address SUN.CCE.NRC.IT, the gateway will just query DNS for the
979 associated PX resource record. The DNS should contain a PX record
980 like this:
981
982 *.cce.nrc.it. IN PX 50 cce.nrc.it. O-cce.PRMD-nrc.ADMD-acme.C-it.
983
984 The first query will return immediately the appropriate mapping rule
985 in DNS store format.
986
987 There is no ".G." at the end of the obtained PX RDATA value, thus
988 applying the syntax translation specified in paragraph 4.2 the
989 <a href="./rfc1327">RFC1327</a> Table 2 mapping rule will be obtained.
990
991 Let's now take another example where a 'gate' table rule is returned.
992 If we are looking for an <a href="./rfc822">RFC822</a> domain ending with top level domain
993 "MW", and the DNS contains a PX record like this,
994
995 *.mw. IN PX 50 mw. O-cce.PRMD-nrc.ADMD-acme.C-it.G.
996
997 DNS will return 'mw.' and 'O-cce.PRMD-nrc.ADMD-acme.C-it.G.', i.e., a
998 'gate' table entry in DNS store format. Dropping the final ".G." and
999 applying the syntax translation specified in paragraph 4.2 the
1000 original rule will be available. More over, the ".G." flag also tells
1001
1002
1003
1004 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
1007
1008
1009 the gateway to use DDA encoding for the inquired <a href="./rfc822">RFC822</a> domain.
1010
1011 On the other hand, translating from X.400 to <a href="./rfc822">RFC822</a> the address
1012
1013 C=de; ADMD=pkz; PRMD=nfc; O=top;
1014
1015 the mail gateway should convert the syntax according to paragraph
1016 4.2, apply the 'Country code convention' described in 4.2.3 to derive
1017 the appropriate DNS translation of the X.400 O/R name and then query
1018 DNS for the corresponding PX resource record. The obtained record for
1019 which the PX record must be queried is thus:
1020
1021 O-top.PRMD-nfc.ADMD-pkz.X42D.de.
1022
1023 The DNS could contain:
1024
1025 *.ADMD-pkz.X42D.de. IN PX 50 pkz.de. ADMD-pkz.C-de.
1026
1027 Assuming that there are not more specific records in DNS, the
1028 wildcard mechanism will return the <a href="./rfc1327">RFC1327</a> 'table1' rule in encoded
1029 format.
1030
1031 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Administration of mapping information</span>
1032
1033 The DNS, using the PX RR, will be able to distribute the mapping
1034 information to all <a href="./rfc1327">RFC1327</a> gateways located on the Internet. However,
1035 not all <a href="./rfc1327">RFC1327</a> gateways will be able to use the Internet DNS. It is
1036 expected that some gateways in a particular management domain will
1037 conform to one of the following models:
1038
1039 (a) Table-based, (b) DNS-based, (c) X.500-based
1040
1041 Table-based management domains will continue to submit and retrieve
1042 their mapping tables from the International Mapping Table coordinator
1043 manually or via some automated procedures. Their mapping information
1044 should be made available in DNS by the appropriate DNS authority
1045 using the same mechanism already in place for MX records: if a branch
1046 has not yet in place its own DNS server, some higher authority in the
1047 DNS tree will provide the service for it. A transition procedure
1048 similar to the one used to migrate from the 'hosts.txt' tables to DNS
1049 can be applied also to the deployment phase of this proposal. An
1050 informational document describing the implementation phase and the
1051 detailed coordination procedures is expected. The deployment phase
1052 must also follow the directives produced by the current work on
1053 <a href="./rfc1327">RFC1327</a> mapping authorities, in order to insure consistency in the
1054 mapping information itself.
1055
1056
1057
1058
1059
1060 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
1063
1064
1065 Another distributed directory service which can distribute the
1066 <a href="./rfc1327">RFC1327</a> mapping information is X.500. The coordination, alignment and
1067 uniqueness of mapping information between DNS and X.500 is an
1068 essential fact if it happens to have both systems in place. The ideal
1069 solution is a dynamic alignment mechanism which transparently makes
1070 the DNS mapping information available in X.500 and vice versa. Some
1071 work in this specific field is already being done [see Costa] which
1072 can result in a global transparent directory service, where the
1073 information is stored in DNS or in X.500, but is visible completely
1074 by any of the two systems.
1075
1076 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Conclusion</span>
1077
1078 The introduction of the new PX resource record and the definition of
1079 the X.400 O/R name space in the DNS structure provide a good
1080 repository for mapping information. The mapping information is stored
1081 in the DNS tree structure so that it can be easily obtained using the
1082 DNS distributed name service. At the same time the definition of the
1083 appropriate DNS space for X.400 O/R names provide a repository where
1084 to store and distribute some other X.400 MHS information. The use of
1085 the DNS has many known advantages in storing, managing and updating
1086 the information. A successful number of tests have been performed
1087 under the provisional top level domain "X400.IT", and their results
1088 confirmed the advantages of the method.
1089
1090 Software to query the DNS and then to convert between the textual
1091 representation of DNS resource records and the address format defined
1092 in <a href="./rfc1327">RFC1327</a> needs to be developed. This software must also allow a
1093 smooth implementation and deployment period, eventually taking care
1094 of the transition phase. A further informational document describing
1095 operational and implementation of the service is expected.
1096
1097 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span>
1098
1099 We wish to thanks all those who contributed to the discussion and
1100 revision of this document: many of their ideas and suggestions
1101 constitute essential parts of this work. In particular thanks to Jon
1102 Postel, Paul Mockapetris, Rob Austin and the whole IETF x400ops, RARE
1103 wg-msg and IETF namedroppers groups. A special mention to Christian
1104 Huitema for his fundamental contribution to this work.
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
1119
1120
1121 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
1122
1123 [<a id="ref-CCITT">CCITT</a>] CCITT SG 5/VII, "Recommendation X.400, Message Handling
1124 Systems: System Model - Service Elements", October 1988.
1125
1126 [<a id="ref-RFC 1327">RFC 1327</a>] Kille, S., "Mapping between X.400(1988)/ISO 10021 and <a href="./rfc822">RFC</a>
1127 <a href="./rfc822">822</a>", <a href="./rfc1327">RFC 1327</a>, March 1992.
1128
1129 [<a id="ref-RFC 1034">RFC 1034</a>] Mockapetris, P., "Domain Names - Concepts and Facilities",
1130 STD 13, <a href="./rfc1034">RFC 1034</a>, USC/Information Sciences Institute, November
1131 1987.
1132
1133 [<a id="ref-RFC 1035">RFC 1035</a>] Mockapetris, P., "Domain names - Implementation and
1134 Specification", STD 13, <a href="./rfc1035">RFC 1035</a>, USC/Information Sciences
1135 Institute, November 1987.
1136
1137 [<a id="ref-RFC 1033">RFC 1033</a>] Lottor, M., "Domain Administrators Operation Guide", <a href="./rfc1033">RFC</a>
1138 <a href="./rfc1033">1033</a>, SRI International, November 1987.
1139
1140 [<a id="ref-Costa">Costa</a>] Costa, A., Macedo, J., and V. Freitas, "Accessing and
1141 Managing DNS Information in the X.500 Directory", Proceeding of
1142 the 4th Joint European Networking Conference, Trondheim, NO, May
1143 1993.
1144
1145 [<a id="ref-Houttin">Houttin</a>] Houttin, J., Hansen, K., and S. Aumont, "Address Mapping
1146 Functions and Authorities", Internet-DRAFT, May 1993.
1147
1148 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Security Considerations</span>
1149
1150 Security issues are not discussed in this memo.
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
1175
1176
1177 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Authors' Addresses</span>
1178
1179 Claudio Allocchio
1180 Sincrotrone Trieste
1181 Padriciano 99
1182 I 34012 Trieste
1183 Italy
1184
1185 <a href="./rfc822">RFC822</a>: [email protected]
1186 X.400: C=it;A=garr;P=Trieste;O=Elettra;
1187 S=Allocchio;G=Claudio;
1188 Phone: +39 40 3758523
1189 Fax: +39 40 226338
1190
1191
1192 Antonio Blasco Bonito
1193 CNUCE - CNR
1194 Reparto infr. reti
1195 Viale S. Maria 36
1196 I 56126 Pisa
1197 Italy
1198
1199 <a href="./rfc822">RFC822</a>: [email protected]
1200 X.400: C=it;A=garr;P=cnr;O=cnuce;S=bonito;
1201 Phone: +39 50 593246
1202 Fax: +39 50 589354
1203
1204
1205 Bruce Cole
1206 Cisco Systems Inc.
1207 P.O. Box 3075
1208 1525 O'Brien Drive
1209 Menlo Park, CA 94026
1210 U.S.A.
1211
1212 <a href="./rfc822">RFC822</a>: [email protected]
1213 X.400: C=us;A= ;P=Internet;
1214 DD.<a href="./rfc822">rfc-822</a>=bcole(a)cisco.com;
1215 Phone: +1 415 6888245
1216 Fax: +1 415 6884575
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc1664">RFC 1664</a> Internet DNS for Mail Mapping Tables August 1994</span>
1231
1232
1233 Silvia Giordano
1234 Centro Svizzero di
1235 Calcolo Scientifico
1236 Via Cantonale
1237 CH 6928 Manno
1238 Switzerland
1239
1240 <a href="./rfc822">RFC822</a>: [email protected]
1241 X.400: C=ch;A=arcom;P=switch;O=cscs;
1242 S=giordano;
1243 Phone: +41 91 508213
1244 Fax: +41 91 506711
1245
1246
1247 Robert Hagens
1248 Advanced Network and Services
1249 1875 Campus Commons Drive
1250 Reston, VA 22091
1251 U.S.A.
1252
1253 <a href="./rfc822">RFC822</a>: [email protected]
1254 X.400: C=us;A= ;P=Internet;
1255 DD.<a href="./rfc822">rfc-822</a>=hagens(a)ans.net;
1256 Phone: +1 703 7587700
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284 Allocchio, Bonito, Cole, Giordano &amp; Hagens [Page 23]
1285 </pre>