Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Diameter Base Protocol (RFC3588)

IP.com Disclosure Number: IPCOM000019348D
Original Publication Date: 2003-Sep-01
Included in the Prior Art Database: 2003-Sep-12

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

P. Calhoun: AUTHOR [+5]

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. Diameter is also intended to work in both local Authentication, Authorization & Accounting and roaming situations. This document specifies the message format, transport, error reporting, accounting and security services to be used by all Diameter applications. The Diameter base application needs to be supported by all Diameter implementations.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 2% of the total text.

Network Working Group P. Calhoun

Request for Comments: 3588 Airespace, Inc.

Category: Standards Track J. Loughney

Nokia

E. Guttman

Sun Microsystems, Inc.

G. Zorn

Cisco Systems, Inc.

J. Arkko

Ericsson

September 2003

Diameter Base Protocol

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 (2003). All Rights Reserved.

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. Diameter is also intended to work in

both local Authentication, Authorization & Accounting and roaming

situations. This document specifies the message format, transport,

error reporting, accounting and security services to be used by all

Diameter applications. The Diameter base application needs to be

supported by all Diameter implementations.

Conventions Used In This Document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",

"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this

document are to be interpreted as described in BCP 14, RFC 2119

[KEYWORD].

Calhoun, et al. Standards Track [Page 1]

RFC 3588 Diameter Based Protocol September 2003

Table of Contents

1. Introduction................................................. 6

1.1. Diameter Protocol..................................... 9

1.1.1. Description of the Document Set.............. 10

1.2. Approach to Extensibility............................. 11

1.2.1. Defining New AVP Values...................... 11

1.2.2. Creating New AVPs............................ 11

1.2.3. Creating New Authentication Applications..... 11

1.2.4. Creating New Accounting Applications......... 12

1.2.5. Application Authentication Procedures........ 14

1.3. Terminology........................................... 14

2. Protocol Overview............................................ 18

2.1. Transport............................................. 20

2.1.1. SCTP Guidelines.............................. 21

2.2. Securing Diameter Messages............................ 21

2.3. Diameter Application Compliance....................... 21

2.4. Application Identifiers............................... 22

2.5. Connections vs. Sessions.............................. 22

2.6. Peer Table............................................ 23

2.7. Realm-Based Routing Table............................. 24

2.8. Role of Diameter Agents............................... 25

2.8.1. Relay Agents................................. 26

2.8.2. Proxy Agents................................. 27

2.8.3. Redirect Agents.............................. 28

2.8.4. Translation Agents........................... 29

...