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
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
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
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
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
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
|
<pre>Network Working Group X. Lee
Request for Comments: 4713 W. Mao
Category: Informational CNNIC
E. Chen
N. Hsu
TWNIC
J. Klensin
October 2006
Registration and Administration Recommendations for Chinese Domain Names
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2006).
IESG Note
This RFC is not a candidate for any level of Internet Standard. The
IETF disclaims any knowledge of the fitness of this RFC for any
purpose and in particular notes that the decision to publish is not
based on IETF review for such things as security, congestion control,
or inappropriate interaction with deployed protocols. The RFC Editor
has chosen to publish this document at its discretion. Readers of
this document should exercise caution in evaluating its value for
implementation and deployment. See <a href="./rfc3932">RFC 3932</a> for more information.
Abstract
Many Chinese characters in common use have variants, which makes most
of the Chinese Domain Names (CDNs) have at least two different forms.
The equivalence between Simplified Chinese (SC) and Traditional
Chinese (TC) characters is very important for CDN registration. This
memo builds on the basic concepts, general guidelines, and framework
of <a href="./rfc3743">RFC 3743</a> to specify proposed registration and administration
procedures for Chinese domain names. The document provides the
information needed for understanding and using the tables defined in
the IANA table registrations for Simplified and Traditional Chinese.
<span class="grey">Lee, et al. Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4713">RFC 4713</a> Recommendations for Chinese Domain Names October 2006</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. Chinese Characters .........................................<a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. Chinese Domain Name Label (CDNL) ...........................<a href="#page-3">3</a>
<a href="#section-2.3">2.3</a>. Simplified Chinese Variant Table (SCVT) ....................<a href="#page-4">4</a>
<a href="#section-2.4">2.4</a>. Traditional Chinese Variant Table (TCVT) ...................<a href="#page-4">4</a>
<a href="#section-2.5">2.5</a>. Original Chinese Domain Name Label (OCDNL) .................<a href="#page-4">4</a>
<a href="#section-3">3</a>. Procedure for Registration of Chinese Domain Name Labels ........<a href="#page-4">4</a>
<a href="#section-3.1">3.1</a>. Terminology and Context ....................................<a href="#page-4">4</a>
<a href="#section-3.2">3.2</a>. Procedure in Terms of the <a href="./rfc3743">RFC 3743</a> Model ...................<a href="#page-4">4</a>
<a href="#section-3.3">3.3</a>. <a href="./rfc3743">RFC 3743</a> Optional Registry Processing ......................<a href="#page-5">5</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-5">5</a>
<a href="#section-5">5</a>. Acknowledgements ................................................<a href="#page-6">6</a>
<a href="#section-6">6</a>. References ......................................................<a href="#page-6">6</a>
<a href="#section-6.1">6.1</a>. Normative References .......................................<a href="#page-6">6</a>
<a href="#section-6.2">6.2</a>. Informative References .....................................<a href="#page-7">7</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
With the standardization of Internationalized Domain Names for
Application (IDNA, described in [<a href="./rfc3490" title=""Internationalizing Domain Names in Applications (IDNA)"">RFC3490</a>], [<a href="./rfc3491" title=""Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)"">RFC3491</a>], and [<a href="./rfc3492" title=""Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA)"">RFC3492</a>]),
internationalized domain names (IDNs), i.e., those that contain non-
ASCII characters, are included in the DNS, and users can access the
Internet with their native languages, most of which are not English.
However, many languages have special requirements, which are not
addressed in the IDNA RFCs. One way to deal with some of the
remaining issues involves grouping characters that could be confused
together as "variants". The variant approach is discussed in <a href="./rfc4290">RFC</a>
<a href="./rfc4290">4290</a> [<a href="./rfc4290" title=""Suggested Practices for Registration of Internationalized Domain Names (IDN)"">RFC4290</a>] and specifically for documents written in Chinese,
Japanese, or Korean (CJK documents), in the so-called "JET
Guidelines" <a href="./rfc3743">RFC 3743</a> [<a href="./rfc3743" title=""Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean"">RFC3743</a>]. Readers of this document are assumed
to be familiar with the concepts and terminology of the latter. The
guidelines specified in this document provide a set of specific
tables and methods required to apply the JET Guidelines to Chinese
characters. For example, changes were made in the forms of a large
number of Chinese characters during the last century to simplify
writing and reading. These "Simplified" characters have been adopted
in some Chinese-speaking communities, while others continue to use
the "Traditional" forms. On the global Internet, if IDNA were used
alone, there would be considerable potential for confusion if the two
forms were not considered together. Consequently, effective use of
Chinese Domain Names (CDNs) requires variant equivalence, as
described in <a href="./rfc3743">RFC 3743</a>, to handle character differences between
Simplified and Traditional Chinese forms.
<span class="grey">Lee, et al. Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4713">RFC 4713</a> Recommendations for Chinese Domain Names October 2006</span>
Chinese variant equivalence itself is very complicated in principle
(please read [<a href="#ref-C2C" title=""Pitfalls and Complexities of Chinese to Chinese Conversion"">C2C</a>] for further information). When it comes to the
usage of Chinese domain names, the basic requirement is to match the
user perception of Chinese characters between Simplified Chinese (SC)
and Traditional Chinese (TC) forms. When users register SC or TC
domain names, they will wish to obtain the other forms (Traditional
or Simplified, respectively) as well, and expect others to be able to
access the website or other resources in both forms.
This document specifies a solution for Chinese domain name
registration and administration that has been adopted and deployed by
CNNIC (the top-level domain registry for "CN") and TWNIC (the top-
level domain registry for "TW") to manage Simplified Chinese and
Traditional Chinese domain name equivalence. In the terminology of
<a href="./rfc3743">RFC 3743</a>, this solution is based on Internationalized Domain Labels
(IDLs).
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
This document adopts the terminologies that are defined in <a href="./rfc3743">RFC 3743</a>.
It is not possible to understand this document without first
understanding the concepts and terminology or <a href="./rfc3743">RFC 3743</a>, including
terminology introduced in its examples. Additional terminology is
defined later in this document.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Chinese Characters</span>
This document suggests permitting only a subset of Chinese characters
in Chinese Domain Names (CDNs) and hence in the DNS. When this
document discusses Chinese characters, it only refers to the subset
of the characters in the first column of the current IANA
registration tables for Chinese as discussed in <a href="#section-2.3">Section 2.3</a> and
<a href="#section-2.4">Section 2.4</a>. These are defined, in detail, in [<a href="#ref-LVT-SC" title="".CN Chinese Character Table"">LVT-SC</a>] and [<a href="#ref-LVT-TC" title="".TW Traditional Chinese Character Table"">LVT-TC</a>].
Of course, characters excluded from these tables are still valid
Chinese characters. However, this document strongly suggests that
registries do not permit any registration of Chinese characters that
are not listed in the tables. The tables themselves will be updated
in the future if necessary.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Chinese Domain Name Label (CDNL)</span>
If an IDN label includes at least one Chinese character, it is called
a Chinese Domain Name (CDN) Label. CDN labels may contain characters
from the traditional letter-digit-hyphen (LDH) set as well as Chinese
characters.
<span class="grey">Lee, et al. Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4713">RFC 4713</a> Recommendations for Chinese Domain Names October 2006</span>
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Simplified Chinese Variant Table (SCVT)</span>
Based on <a href="./rfc3743">RFC 3743</a> [<a href="./rfc3743" title=""Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean"">RFC3743</a>], a language table for Simplified Chinese
has been defined [<a href="#ref-LVT-SC" title="".CN Chinese Character Table"">LVT-SC</a>]. It can be used for the registration of
Simplified Chinese domain names. The key feature of this table is
that the preferred variant is the SC character, which is used by
Chinese mainland users or defined in Chinese-related standards.
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Traditional Chinese Variant Table (TCVT)</span>
Similarly, a language table has been defined for Traditional Chinese
[<a href="#ref-LVT-TC" title="".TW Traditional Chinese Character Table"">LVT-TC</a>]. It is also based on the rules of <a href="./rfc3743">RFC 3743</a>. It can be used
for registration of Traditional Chinese domain names. The preferred
variant is the TC character, which is used by Taiwan users or defined
in related standards.
<span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Original Chinese Domain Name Label (OCDNL)</span>
The Chinese Domain Name Label that users submit for registration.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Procedure for Registration of Chinese Domain Name Labels</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Terminology and Context</span>
This document adopts the same procedure for Chinese Domain Name Label
(CDNL) registration as the one defined for more general IDN labels in
<a href="./rfc3743#section-3.2.3">section 3.2.3 of RFC 3743</a> [<a href="./rfc3743" title=""Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean"">RFC3743</a>]. The terminology and notation
used below, and the steps that are mentioned, derive from that
document. In particular, "CV" is the character variant associated
with an input character ("IN") and a language table. The language
tables used here are those for Chinese as spoken and written in the
Chinese mainland (ZH-CN) and on Taiwan (ZH-TW). "PV" is the selected
Preferred Variant.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Procedure in Terms of the <a href="./rfc3743">RFC 3743</a> Model</span>
The first column of the Simplified Chinese Variant Table (SCVT) is
the same as the first column of the corresponding Traditional Chinese
Variant Table (TCVT) and so are the third columns of both tables.
Consequently, the CV(IN, ZH-CN) will be same as the CV(IN, ZH-TW)
after Step 3; the PV(IN, ZH-CN) is in SC form, and the PV(IN, ZH-TW)
is in TC form. As a result, there will not be more than three
records (i.e., for the original label (OCDNL), the Simplified Chinese
(SC) form, and the Traditional Chinese (TC) form) to be added into
the zone file after applying this procedure. In other words, the
procedure does not generate labels that contain a mixture of
Simplified and Traditional Chinese as variants.
<span class="grey">Lee, et al. Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc4713">RFC 4713</a> Recommendations for Chinese Domain Names October 2006</span>
The set of languages associated with the input (IN) is both ZH-CN and
ZH-TW by default. The procedure for CDNL registration uses the
optional registry-defined rules provided in <a href="./rfc3743">RFC 3743</a> for optional
processing, with the understanding that the rules may vary for
different registries supporting CDNs. The motivation for such rules
is described below.
The preferred variant(s) is/are TC in TCVT, and SC in SCVT. There
may be more than one preferred variant for a given valid character.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. <a href="./rfc3743">RFC 3743</a> Optional Registry Processing</span>
In actuality, while IDNA, and hence <a href="./rfc3743">RFC 3743</a>, process characters one
at a time, the actual relationship between the valid code point and
the preferred variant is contextual: whether one character can be
substituted for another depends on the characters with which it is
associated in a label or, more generally, in a phrase. In
particular, some of the preferred variants make no sense in
combination with other characters; therefore, those combinations
should not be added into the Zone file (described as "ZV" or zone
variants in <a href="./rfc3743">RFC 3743</a>). If desired, it should be possible to define
and implement rules to reduce the preferred variant labels to only
plausible ones. This could be done, for example, with some
artificial intelligence tools, or with feedback from the registrant,
or with selection based on frequency of occurrence in other texts.
To illustrate one possibility, the OCDNL could be required to be TC-
only or SC-only, and if there is more than one preferred variant, the
OCDNL will be used as the PV, instead of the PV produced by the
algorithm.
To reemphasize, the tables in [<a href="#ref-LVT-SC" title="".CN Chinese Character Table"">LVT-SC</a>] and [<a href="#ref-LVT-TC" title="".TW Traditional Chinese Character Table"">LVT-TC</a>] follow the table
format and terminologies defined in [<a href="./rfc3743" title=""Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean"">RFC3743</a>]. If one intends to
implement Chinese domain name registrations based on these two tables
or ones similar to them, a complete understanding of <a href="./rfc3743">RFC 3743</a> is
needed for the proper use of those tables.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
This document is subject to the same security considerations as <a href="./rfc3743">RFC</a>
<a href="./rfc3743">3743</a>, which defines the table formats and operations. As with that
base document, part of its intent is to reduce the security problems
that might be caused by confusion among characters with similar
appearances or meanings. While it will not introduce any additional
security issues, additional registration restrictions such as those
outlined in <a href="#section-3">Section 3</a> may further reduce potential problems.
<span class="grey">Lee, et al. Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc4713">RFC 4713</a> Recommendations for Chinese Domain Names October 2006</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
Thanks to these people for their suggestions and for their efforts to
bring this tough work to conclusion and to promote the results: WANG
YanFeng, Ai-Chin LU, Shian-Shyong TSENG, QIAN HuaLin, and Li-Ming
TSENG.
The authors especially thank Joe ZHANG and XiaoMing WANG for their
outstanding contributions on SCVT in [<a href="#ref-LVT-SC" title="".CN Chinese Character Table"">LVT-SC</a>]. Also, thanks to Kenny
HUANG, Zheng-Wei LIN, Shi-Xiong TSENG, Lie-Neng WU, Cheng-Wu PAN,
Lin-Mei WEI, and Qi-Qing HSU for their efforts and contributions on
editing the TCVT in [<a href="#ref-LVT-TC" title="".TW Traditional Chinese Character Table"">LVT-TC</a>]. These experts provided basic materials
or gave very crucial suggestions and principles to accomplish these
two variant tables.
The authors also gratefully acknowledge the contributions of those
who commented and made suggestions on this document, including James
SENG, and other JET members.
<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-LVT-SC">LVT-SC</a>] QIAN, H. and X. LEE, ".CN Chinese Character Table", IANA
IDN Languages Tables, March 2005.
[<a id="ref-LVT-TC">LVT-TC</a>] LU, A., ".TW Traditional Chinese Character Table", IANA
IDN Languages Tables, March 2005.
[<a id="ref-RFC3490">RFC3490</a>] Faltstrom, P., Hoffman, P., and A. Costello,
"Internationalizing Domain Names in Applications (IDNA)",
<a href="./rfc3490">RFC 3490</a>, March 2003.
[<a id="ref-RFC3491">RFC3491</a>] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep
Profile for Internationalized Domain Names (IDN)", <a href="./rfc3491">RFC</a>
<a href="./rfc3491">3491</a>, March 2003.
[<a id="ref-RFC3492">RFC3492</a>] Costello, A., "Punycode: A Bootstring encoding of Unicode
for Internationalized Domain Names in Applications
(IDNA)", <a href="./rfc3492">RFC 3492</a>, March 2003.
[<a id="ref-RFC3743">RFC3743</a>] Konishi, K., Huang, K., Qian, H., and Y. Ko, "Joint
Engineering Team (JET) Guidelines for Internationalized
Domain Names (IDN) Registration and Administration for
Chinese, Japanese, and Korean", <a href="./rfc3743">RFC 3743</a>, April 2004.
<span class="grey">Lee, et al. Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc4713">RFC 4713</a> Recommendations for Chinese Domain Names October 2006</span>
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
[<a id="ref-C2C">C2C</a>] Halpern, J. and J. Kerman, "Pitfalls and Complexities of
Chinese to Chinese Conversion", International Unicode
Conference (14th) in Boston, March 1999.
[<a id="ref-RFC4290">RFC4290</a>] Klensin, J., "Suggested Practices for Registration of
Internationalized Domain Names (IDN)", <a href="./rfc4290">RFC 4290</a>, December
2005.
<span class="grey">Lee, et al. Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc4713">RFC 4713</a> Recommendations for Chinese Domain Names October 2006</span>
Authors' Addresses
LEE Xiaodong
CNNIC, No.4 South 4th Street, Zhongguancun
Beijing 100080
Phone: +86 10 58813020
EMail: lee@cnnic.cn
URI: <a href="http://www.cnnic.cn">http://www.cnnic.cn</a>
MAO Wei
CNNIC, No.4 South 4th Street, Zhongguancun
Beijing 100080
Phone: +86 10 58813055
EMail: mao@cnnic.cn
URI: <a href="http://www.cnnic.cn">http://www.cnnic.cn</a>
Erin CHEN
TWNIC, 4F-2, No. 9, Sec. 2, Roosevelt Rd.
Taipei 100
Phone: +886 2 23411313
EMail: erin@twnic.net.tw
URI: <a href="http://www.twnic.net.tw">http://www.twnic.net.tw</a>
Nai-Wen HSU
TWNIC, 4F-2, No. 9, Sec. 2, Roosevelt Rd.
Taipei 100
Phone: +886 2 23411313
EMail: snw@twnic.net.tw
URI: <a href="http://www.twnic.net.tw">http://www.twnic.net.tw</a>
John C KLENSIN
1770 Massachusetts Ave, #322
Cambridge, MA 02140
USA
Phone: +1 617 491 5735
EMail: john+ietf@jck.com
<span class="grey">Lee, et al. Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc4713">RFC 4713</a> Recommendations for Chinese Domain Names October 2006</span>
Full Copyright Statement
Copyright (C) The Internet Society (2006).
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 at www.rfc-editor.org/copyright.html, 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 provided by the IETF
Administrative Support Activity (IASA).
Lee, et al. Informational [Page 9]
</pre>
|
