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 G. Zorn
Request for Comments: 2484 Microsoft Corporation
Category: Standards Track January 1999
Updates: <a href="./rfc2284">2284</a>, <a href="./rfc1994">1994</a>, <a href="./rfc1570">1570</a>
PPP LCP Internationalization Configuration Option
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 (1999). All Rights Reserved.
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Abstract</span>
The Point-to-Point Protocol (PPP) [<a href="#ref-1" title=""The Point-to-Point Protocol (PPP)"">1</a>] provides a standard method for
transporting multi-protocol datagrams over point-to-point links. PPP
also defines an extensible Link Control Protocol (LCP), which allows
negotiation of an Authentication Protocol for authenticating its peer
before allowing Network Layer protocols to transmit over the link.
Both LCP and Authentication Protocol packets may contain text which
is intended to be human-readable [<a href="#ref-2" title=""PPP Challenge Handshake Authentication Protocol (CHAP)"">2</a>,<a href="#ref-3" title=""PPP LCP Extensions"">3</a>,<a href="#ref-4" title=""PPP Extensible Authentication Protocol (EAP)"">4</a>]. This document defines an
LCP configuration option for the negotiation of character set and
language usage, as required by <a href="./rfc2277">RFC 2277</a> [<a href="#ref-5" title=""IETF Policy on Character Sets and Languages"">5</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Specification of Requirements</span>
In this document, the key words "MAY", "MUST, "MUST NOT", "optional",
"recommended", "SHOULD", and "SHOULD NOT" are to be interpreted as
described in [<a href="#ref-6" title=""Key words for use in RFCs to Indicate Requirement Levels"">6</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Additional LCP Configuration Option</span>
The Configuration Option format and basic options are already defined
for LCP [<a href="#ref-1" title=""The Point-to-Point Protocol (PPP)"">1</a>].
<span class="grey">Zorn Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc2484">RFC 2484</a> LCP Internationalization Option January 1999</span>
Up-to-date values of the LCP Option Type field are specified in STD 2
[<a href="#ref-7" title=""Assigned Numbers"">7</a>]. This document concerns the following value:
28 Internationalization
The Internationalization option described here MAY be negotiated
independently in each direction.
Only one instance of this option SHOULD be sent by an implementation,
representing its preferred language and charset.
If Internationalization option is rejected by the peer, the default
language and charset MUST be used to construct all human-readable
messages sent to the peer.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Internationalization</span>
Description
This Configuration Option provides a method for an implementation
to indicate to the peer both the language in which human-readable
messages it sends should be composed and the charset in which that
language should be represented.
A summary of the Internationalization option format is shown below.
The fields are transmitted from left to right.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | MIBenum
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
MIBenum (cont) | Language-Tag...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
28
Length
>= 7
<span class="grey">Zorn Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc2484">RFC 2484</a> LCP Internationalization Option January 1999</span>
MIBenum
The MIBenum field is four octets in length. It contains a unique
integer value identifying a charset [<a href="#ref-5" title=""IETF Policy on Character Sets and Languages"">5</a>,<a href="#ref-11" title=""Printer MIB"">11</a>].
This value MUST represent one of the set of charsets listed in the
IANA charset registry [<a href="#ref-7" title=""Assigned Numbers"">7</a>].
The charset registration procedure is described in <a href="./rfc2278">RFC 2278</a> [<a href="#ref-9" title=""IANA Charset Registration Procedures"">9</a>].
The default charset value is UTF-8 [<a href="#ref-10" title=""UTF-8, a transformation format of ISO 10646"">10</a>]. The MIBenum value for
the UTF-8 charset is 106.
Language-Tag
The Language-Tag field is an ASCII string which contains a
language tag, as defined in <a href="./rfc1766">RFC 1766</a> [<a href="#ref-8" title=""Tags for the Identification of Languages"">8</a>].
Language tags are in principle case-insensitive; however, since
the capitalization of a tag does not carry any meaning,
implementations SHOULD send only lower-case Tag fields.
The default Tag value is "i-default" [<a href="#ref-8" title=""Tags for the Identification of Languages"">8</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. References</span>
[<a id="ref-1">1</a>] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51, <a href="./rfc1661">RFC</a>
<a href="./rfc1661">1661</a>, July 1994.
[<a id="ref-2">2</a>] Simpson, W., "PPP Challenge Handshake Authentication Protocol
(CHAP)", <a href="./rfc1994">RFC 1994</a>, August 1996.
[<a id="ref-3">3</a>] Simpson, W., "PPP LCP Extensions", <a href="./rfc1570">RFC 1570</a>, January 1994.
[<a id="ref-4">4</a>] Blunk, L. and J. Vollbrecht, "PPP Extensible Authentication
Protocol (EAP)", <a href="./rfc2284">RFC 2284</a>, March 1998.
[<a id="ref-5">5</a>] Alvestrand, H., "IETF Policy on Character Sets and Languages",
<a href="https://www.rfc-editor.org/bcp/bcp18">BCP 18</a>, <a href="./rfc2277">RFC 2277</a>, January 1998.
[<a id="ref-6">6</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-7">7</a>] Reynolds, J. and J. Postel, "Assigned Numbers", STD 2, <a href="./rfc1700">RFC 1700</a>,
October 1994. See also: <a href="http://www.iana.org/numbers.html">http://www.iana.org/numbers.html</a>
[<a id="ref-8">8</a>] Alvestrand, H., "Tags for the Identification of Languages", <a href="./rfc1766">RFC</a>
<a href="./rfc1766">1766</a>, March 1995.
<span class="grey">Zorn Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc2484">RFC 2484</a> LCP Internationalization Option January 1999</span>
[<a id="ref-9">9</a>] Freed, N. and J. Postel, "IANA Charset Registration Procedures",
<a href="https://www.rfc-editor.org/bcp/bcp19">BCP 19</a>, <a href="./rfc2278">RFC 2278</a>, January 1998.
[<a id="ref-10">10</a>] Yergeau, F., "UTF-8, a transformation format of ISO 10646", <a href="./rfc2279">RFC</a>
<a href="./rfc2279">2279</a>, January 1998.
[<a id="ref-11">11</a>] Smith, R., Wright, F., Hastings, T., Zilles, S. and J.
Gyllenskog, "Printer MIB", <a href="./rfc1759">RFC 1759</a>, March 1995.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
It is possible that an attacker might manipulate the option in such a
way that displayable messages would be unintelligible to the reader.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
Thanks to Craig Fox (fox@cisco.com), James Carlson
(carlson@ironbridgenetworks.com), Harald Alvestrand
(Harald.Alvestrand@maxware.no), Kevin Smith (kevin@ascend.com), Karl
Fox (karl@ascend.com), Thomas Narten (narten@raleigh.ibm.com) and
Narendra Gidwani (nareng@microsoft.com) for helpful suggestions and
feedback.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Chair's Address</span>
Karl Fox
Ascend Communications
3518 Riverside Drive
Suite 101
Columbus, OH 43221
Phone: +1 614 326 6841
EMail: karl@ascend.com
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Author's Address</span>
Glen Zorn
Microsoft Corporation
One Microsoft Way
Redmond, Washington 98052
Phone: +1 425 703 1559
Fax: +1 425 936 7329
EMail: glennz@microsoft.com
<span class="grey">Zorn Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc2484">RFC 2484</a> LCP Internationalization Option January 1999</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Full Copyright Statement</span>
Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Zorn Standards Track [Page 5]
</pre>
|
