Diameter Base Protocol
draft-ietf-dime-rfc3588bis-29

The information below is for an old version of the document
Document Type Active Internet-Draft (dime WG)
Last updated 2011-09-22 (latest revision 2011-08-30)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Unknown
Document shepherd Jouni Korhonen
IESG IESG state IESG Evaluation::Revised I-D Needed
Telechat date
Needs 7 more YES or NO OBJECTION positions to pass.
Responsible AD Dan Romascanu
IESG note Jouni Korhonen (jouni.korhonen@nsn.com, jouni.nospam@gmail.com) is the Document Shepherd
Send notices to dime-chairs@tools.ietf.org, draft-ietf-dime-rfc3588bis@tools.ietf.org
DIME                                                     V. Fajardo, Ed.
Internet-Draft                                    Telcordia Technologies
Obsoletes: 3588 (if approved)                                   J. Arkko
Intended status: Standards Track                       Ericsson Research
Expires: March 2, 2012                                       J. Loughney
                                                   Nokia Research Center
                                                                 G. Zorn
                                                             Network Zen
                                                         August 30, 2011

                         Diameter Base Protocol
                   draft-ietf-dime-rfc3588bis-29.txt

Abstract

   The Diameter base protocol is intended to provide an Authentication,
   Authorization and Accounting (AAA) framework for applications such as
   network access or IP mobility in both local and roaming situations.
   This document specifies the message format, transport, error
   reporting, accounting and security services used by all Diameter
   applications.  The Diameter base protocol as defined in this document
   obsoletes RFC 3588 and must be supported by all new Diameter
   implementations.

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 March 2, 2012.

Copyright Notice

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

   This document is subject to BCP 78 and the IETF Trust's Legal

Fajardo, et al.           Expires March 2, 2012                 [Page 1]
Internet-Draft           Diameter Base Protocol              August 2011

   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  . . . . . . . . . . . . . . . . . . . . . . . .   7
     1.1.  Diameter Protocol . . . . . . . . . . . . . . . . . . . .   9
       1.1.1.   Description of the Document Set  . . . . . . . . . .  10
       1.1.2.   Conventions Used in This Document  . . . . . . . . .  11
       1.1.3.   Changes from RFC3588 . . . . . . . . . . . . . . . .  11
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .  13
     1.3.  Approach to Extensibility . . . . . . . . . . . . . . . .  18
       1.3.1.   Defining New AVP Values  . . . . . . . . . . . . . .  19
       1.3.2.   Creating New AVPs  . . . . . . . . . . . . . . . . .  19
       1.3.3.   Creating New Commands  . . . . . . . . . . . . . . .  19
       1.3.4.   Creating New Diameter Applications . . . . . . . . .  20
   2.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .  21
     2.1.  Transport . . . . . . . . . . . . . . . . . . . . . . . .  22
       2.1.1.   SCTP Guidelines  . . . . . . . . . . . . . . . . . .  23
     2.2.  Securing Diameter Messages  . . . . . . . . . . . . . . .  24
     2.3.  Diameter Application Compliance . . . . . . . . . . . . .  25
     2.4.  Application Identifiers . . . . . . . . . . . . . . . . .  25
     2.5.  Connections vs. Sessions  . . . . . . . . . . . . . . . .  25
     2.6.  Peer Table  . . . . . . . . . . . . . . . . . . . . . . .  26
     2.7.  Routing Table . . . . . . . . . . . . . . . . . . . . . .  27
     2.8.  Role of Diameter Agents . . . . . . . . . . . . . . . . .  29
       2.8.1.   Relay Agents . . . . . . . . . . . . . . . . . . . .  30
       2.8.2.   Proxy Agents . . . . . . . . . . . . . . . . . . . .  31
       2.8.3.   Redirect Agents  . . . . . . . . . . . . . . . . . .  31
       2.8.4.   Translation Agents . . . . . . . . . . . . . . . . .  32
     2.9.  Diameter Path Authorization . . . . . . . . . . . . . . .  33
   3.  Diameter Header . . . . . . . . . . . . . . . . . . . . . . .  34
     3.1.  Command Codes . . . . . . . . . . . . . . . . . . . . . .  37
Show full document text