Internet DRAFT - draft-chowdhury-rohc-radius-attributes
draft-chowdhury-rohc-radius-attributes
Network Working Group K. Chowdhury
Internet-Draft A. Seshadri
Expires: April 13, 2006 Starent Networks
October 10, 2005
RADIUS Support for New Header Compression Schemes
draft-chowdhury-rohc-radius-attributes-00.xml
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 13, 2006.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
The definition of RADIUS attribute "Framed-Compression" in RFC 2865
does not include values for new Header Compression schemes like ROHC,
ROHC-TCP. This document defines the new values to the "Framed-
Compression" attribute.
Chowdhury & Seshadri Expires April 13, 2006 [Page 1]
Internet-Draft October 2005
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4
3. New values for the Framed-Compression . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . 8
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
7. Normative References . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 9
Intellectual Property and Copyright Statements . . . . . . . 11
Chowdhury & Seshadri Expires April 13, 2006 [Page 2]
Internet-Draft October 2005
1. Introduction
RFC 2865 defines the Framed-Compression attribute. This attribute is
used today to indicate compression protocol to be used for the radio
link. The NAS (also wireless access gateway) also uses this
attribute to convey its capability to the AAA server.
The values defined for Framed-Compression attribute are as follows:
0 None
1 VJ TCP/IP header compression
2 IPX header compression
3 Stac-LZS compression
There are newer header compression schemes defined by IETF e.g.
ROHC. ROHC is being deployed worldwide and it is especially gaining
immense popularity in 3G wireless networks.
This document defines the additional Framed-Compression attribute
values required for ROHC support.
Chowdhury & Seshadri Expires April 13, 2006 [Page 3]
Internet-Draft October 2005
2. Terminology
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC 2119.
Chowdhury & Seshadri Expires April 13, 2006 [Page 4]
Internet-Draft October 2005
3. New values for the Framed-Compression
Proposed revision in RFC 2865 for Framed-Compression attribute:
Description
This Attribute indicates a compression protocol to be used for the
link. It MAY be used in Access-Accept packets. It MAY be used in an
Access-Request packet as a hint to the server that the NAS would
prefer to supports the use that a compression scheme, but the RADIUS
server is not required to honor the hint.
More than one compression protocol Attribute MAY be sent in the same
RADIUS message. It is the responsibility of the NAS to apply the
proper compression protocol to appropriate link traffic.
A summary of the Framed-Compression Attribute 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 | Value
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Value (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 13 for Framed-Compression.
Length: 6.
Value:
The Value field is four octets.
0 None
1 VJ TCP/IP header compression
2 IPX header compression
3 Stac-LZS compression
TBD-1 RObust Header Compression [RFC3095].
Chowdhury & Seshadri Expires April 13, 2006 [Page 5]
Internet-Draft October 2005
TBD-2 VJ TCP/IP header compression and RObust Header Compression
[ROHC-VJ]. When this value is negotiated, VJ compression
is used for all TCP/IP traffic and ROHC compression is used
for remaining traffic (UDP/IP, RTP/IP, ESP/IP).
TBD-3 Link Layer Assisted RObust Header Compression [RFC3242].
Chowdhury & Seshadri Expires April 13, 2006 [Page 6]
Internet-Draft October 2005
4. Security Considerations
This document does not introduce any new security concerns beyond
those specified in the basic DHCP [RFC2865].
Chowdhury & Seshadri Expires April 13, 2006 [Page 7]
Internet-Draft October 2005
5. IANA Considerations
The following values for Framed-Compression attribute MUST be
assigned by IANA:
TBD-1 RObust Header Compression [RFC3095].
TBD-2 VJ TCP/IP header compression and RObust Header Compression
[ROHC-VJ].
TBD-3 Link Layer Assisted RObust Header Compression [RFC3242].
Chowdhury & Seshadri Expires April 13, 2006 [Page 8]
Internet-Draft October 2005
6. Acknowledgements
TBD.
7. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)",
RFC 2865, June 2000.
[RFC3095] Bormann, C., Burmeister, C., Degermark, M., Fukushima, H.,
Hannu, H., Jonsson, L-E., Hakenberg, R., Koren, T., Le,
K., Liu, Z., Martensson, A., Miyazaki, A., Svanbro, K.,
Wiebke, T., Yoshimura, T., and H. Zheng, "RObust Header
Compression (ROHC): Framework and four profiles: RTP, UDP,
ESP, and uncompressed", RFC 3095, July 2001.
[RFC3242] Jonsson, L-E. and G. Pelletier, "RObust Header Compression
(ROHC): A Link-Layer Assisted Profile for IP/UDP/RTP",
RFC 3242, April 2002.
[ROHC-VJ] Pelletier et. al., G., "RObust Header Compression (ROHC):A
Profile for TCP/IP (ROHC-TCP).",
draft-ietf-rohc-tcp-10.txt (work in progress), July 2005.
Authors' Addresses
Kuntal Chowdhury
Starent Networks
30 International Place
Tewksbury, MA 01876
US
Phone: +1 214-550-1416
Email: kchowdhury@starentnetworks.com
Chowdhury & Seshadri Expires April 13, 2006 [Page 9]
Internet-Draft October 2005
Arun Seshadri
Starent Networks
201, 2nd Floor, Carlton Tower
Airport Road, KodiHalli
Bangalore, 560 008
India
Phone: +91 80-5125-6100
Email: aruns@starentnetworks.com
Chowdhury & Seshadri Expires April 13, 2006 [Page 10]
Internet-Draft October 2005
Intellectual Property Statement
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 BCP 78 and BCP 79.
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
http://www.ietf.org/ipr.
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.
Disclaimer of Validity
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.
Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Chowdhury & Seshadri Expires April 13, 2006 [Page 11]
