Support of fragmentation of RADIUS packets
draft-ietf-radext-radius-fragmentation-11

The information below is for an old version of the document
Document Type Active Internet-Draft (radext WG)
Last updated 2015-01-22 (latest revision 2015-01-20)
Replaces draft-perez-radext-radius-fragmentation
Stream IETF
Intended RFC status Experimental
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Stefan Winter
Shepherd write-up Show (last changed 2014-11-27)
IESG IESG state IESG Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Needs a YES.
Responsible AD BenoƮt Claise
Send notices to radext@ietf.org, draft-ietf-radext-radius-fragmentation.all@tools.ietf.org, radext-chairs@tools.ietf.org, stefan.winter@restena.lu
IANA IANA review state IANA OK - Actions Needed
IANA action state None
RADIUS EXTensions Working Group                          A. Perez-Mendez
Internet-Draft                                            R. Marin-Lopez
Updates: 2865, 6158, 6929                           F. Pereniguez-Garcia
(if approved)                                            G. Lopez-Millan
Intended status: Experimental                       University of Murcia
Expires: July 24, 2015                                          D. Lopez
                                                          Telefonica I+D
                                                                A. DeKok
                                                          Network RADIUS
                                                        January 20, 2015

               Support of fragmentation of RADIUS packets
               draft-ietf-radext-radius-fragmentation-11

Abstract

   The Remote Authentication Dial-In User Service (RADIUS) protocol is
   limited to a total packet size of 4096 octets.  Provisions exist for
   fragmenting large amounts of authentication data across multiple
   packets, via Access-Challenge.  No similar provisions exist for
   fragmenting large amounts of authorization data.  This document
   specifies how existing RADIUS mechanisms can be leveraged to provide
   that functionality.  These mechanisms are largely compatible with
   existing implementations, and are designed to be invisible to
   proxies, and "fail-safe" to legacy RADIUS Clients and Servers.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on July 24, 2015.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Perez-Mendez, et al.      Expires July 24, 2015                 [Page 1]
Internet-Draft       Fragmentation of RADIUS packets        January 2015

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Requirements Language  . . . . . . . . . . . . . . . . . .  6
   2.  Status of this document  . . . . . . . . . . . . . . . . . . .  6
   3.  Scope of this document . . . . . . . . . . . . . . . . . . . .  7
   4.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
   5.  Fragmentation of packets . . . . . . . . . . . . . . . . . . . 12
     5.1.  Pre-authorization  . . . . . . . . . . . . . . . . . . . . 12
     5.2.  Post-authorization . . . . . . . . . . . . . . . . . . . . 17
   6.  Chunk size . . . . . . . . . . . . . . . . . . . . . . . . . . 20
   7.  Allowed large packet size  . . . . . . . . . . . . . . . . . . 21
   8.  Handling special attributes  . . . . . . . . . . . . . . . . . 22
     8.1.  Proxy-State attribute  . . . . . . . . . . . . . . . . . . 22
     8.2.  State attribute  . . . . . . . . . . . . . . . . . . . . . 23
     8.3.  Service-Type attribute . . . . . . . . . . . . . . . . . . 24
     8.4.  Rebuilding the original large packet . . . . . . . . . . . 24
   9.  New flag T field for the Long Extended Type attribute
       definition . . . . . . . . . . . . . . . . . . . . . . . . . . 24
   10. New attribute definition . . . . . . . . . . . . . . . . . . . 25
     10.1. Frag-Status attribute  . . . . . . . . . . . . . . . . . . 25
     10.2. Proxy-State-Length attribute . . . . . . . . . . . . . . . 26
     10.3. Table of attributes  . . . . . . . . . . . . . . . . . . . 27
   11. Operation with proxies . . . . . . . . . . . . . . . . . . . . 27
     11.1. Legacy proxies . . . . . . . . . . . . . . . . . . . . . . 27
     11.2. Updated proxies  . . . . . . . . . . . . . . . . . . . . . 28
   12. General considerations . . . . . . . . . . . . . . . . . . . . 29
     12.1. Flag T . . . . . . . . . . . . . . . . . . . . . . . . . . 29
     12.2. Violation of RFC2865 . . . . . . . . . . . . . . . . . . . 30
Show full document text