PPP LCP Internationalization Configuration Option
RFC 2484
|
| Document |
Type |
|
RFC - Proposed Standard
(January 1999; No errata)
|
|
Author |
|
Glen Zorn
|
|
Last updated |
|
2013-03-02
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
html
pdf
htmlized
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 2484 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group G. Zorn
Request for Comments: 2484 Microsoft Corporation
Category: Standards Track January 1999
Updates: 2284, 1994, 1570
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.
1. Abstract
The Point-to-Point Protocol (PPP) [1] 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 [2,3,4]. This document defines an
LCP configuration option for the negotiation of character set and
language usage, as required by RFC 2277 [5].
2. Specification of Requirements
In this document, the key words "MAY", "MUST, "MUST NOT", "optional",
"recommended", "SHOULD", and "SHOULD NOT" are to be interpreted as
described in [6].
3. Additional LCP Configuration Option
The Configuration Option format and basic options are already defined
for LCP [1].
Zorn Standards Track [Page 1]
RFC 2484 LCP Internationalization Option January 1999
Up-to-date values of the LCP Option Type field are specified in STD 2
[7]. 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.
4.1. Internationalization
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
Zorn Standards Track [Page 2]
RFC 2484 LCP Internationalization Option January 1999
MIBenum
The MIBenum field is four octets in length. It contains a unique
integer value identifying a charset [5,11].
This value MUST represent one of the set of charsets listed in the
IANA charset registry [7].
The charset registration procedure is described in RFC 2278 [9].
The default charset value is UTF-8 [10]. 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 RFC 1766 [8].
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" [8].
4. References
[1] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51, RFC
1661, July 1994.
[2] Simpson, W., "PPP Challenge Handshake Authentication Protocol
(CHAP)", RFC 1994, August 1996.
[3] Simpson, W., "PPP LCP Extensions", RFC 1570, January 1994.
[4] Blunk, L. and J. Vollbrecht, "PPP Extensible Authentication
Protocol (EAP)", RFC 2284, March 1998.
[5] Alvestrand, H., "IETF Policy on Character Sets and Languages",
BCP 18, RFC 2277, January 1998.
[6] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[7] Reynolds, J. and J. Postel, "Assigned Numbers", STD 2, RFC 1700,
Show full document text