Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more ➡
Download
Standard view
Full view
of .
Add note
Save to My Library
Sync to mobile
Look up keyword or section
Like this
31Activity
×

Table Of Contents

0 of .
Results for:
No results containing your search query
P. 1
Diameter Base Protocol

Diameter Base Protocol

Ratings: (0)|Views: 47,865|Likes:
Published by Dino Macchi
This is the IETF specification for the Diameter Base Protocol
This is the IETF specification for the Diameter Base Protocol

More info:

Published by: Dino Macchi on Jun 28, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See More
See less

07/18/2013

pdf

text

original

 
Network Working Group P. CalhounRequest for Comments: 3588 Airespace, Inc.Category: Standards Track J. LoughneyNokiaE. GuttmanSun Microsystems, Inc.G. ZornCisco Systems, Inc.J. ArkkoEricssonSeptember 2003Diameter Base ProtocolStatus of this MemoThis document specifies an Internet standards track protocol for theInternet community, and requests discussion and suggestions forimprovements. Please refer to the current edition of the "InternetOfficial Protocol Standards" (STD 1) for the standardization stateand status of this protocol. Distribution of this memo is unlimited.Copyright NoticeCopyright (C) The Internet Society (2003). All Rights Reserved.AbstractThe Diameter base protocol is intended to provide an Authentication,Authorization and Accounting (AAA) framework for applications such asnetwork access or IP mobility. Diameter is also intended to work inboth local Authentication, Authorization & Accounting and roamingsituations. This document specifies the message format, transport,error reporting, accounting and security services to be used by allDiameter applications. The Diameter base application needs to besupported by all Diameter implementations.Conventions Used In This DocumentThe key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in thisdocument 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 2003Table of Contents1. Introduction................................................. 61.1. Diameter Protocol..................................... 91.1.1. Description of the Document Set.............. 101.2. Approach to Extensibility............................. 111.2.1. Defining New AVP Values...................... 111.2.2. Creating New AVPs............................ 111.2.3. Creating New Authentication Applications..... 111.2.4. Creating New Accounting Applications......... 121.2.5. Application Authentication Procedures........ 141.3. Terminology........................................... 142. Protocol Overview............................................ 182.1. Transport............................................. 202.1.1. SCTP Guidelines.............................. 212.2. Securing Diameter Messages............................ 212.3. Diameter Application Compliance....................... 212.4. Application Identifiers............................... 222.5. Connections vs. Sessions.............................. 222.6. Peer Table............................................ 232.7. Realm-Based Routing Table............................. 242.8. Role of Diameter Agents............................... 252.8.1. Relay Agents................................. 262.8.2. Proxy Agents................................. 272.8.3. Redirect Agents.............................. 282.8.4. Translation Agents........................... 292.9. End-to-End Security Framework......................... 302.10. Diameter Path Authorization........................... 303. Diameter Header.............................................. 323.1. Command Codes......................................... 353.2. Command Code ABNF specification....................... 363.3. Diameter Command Naming Conventions................... 384. Diameter AVPs................................................ 384.1. AVP Header............................................ 394.1.1. Optional Header Elements..................... 414.2. Basic AVP Data Formats................................ 414.3. Derived AVP Data Formats.............................. 424.4. Grouped AVP Values.................................... 494.4.1. Example AVP with a Grouped Data Type......... 504.5. Diameter Base Protocol AVPs........................... 535. Diameter Peers............................................... 565.1. Peer Connections...................................... 565.2. Diameter Peer Discovery............................... 565.3. Capabilities Exchange................................. 595.3.1. Capabilities-Exchange-Request................ 605.3.2. Capabilities-Exchange-Answer................. 605.3.3. Vendor-Id AVP................................ 615.3.4. Firmware-Revision AVP........................ 61Calhoun, et al. Standards Track [Page 2]
 
RFC 3588 Diameter Based Protocol September 20035.3.5. Host-IP-Address AVP.......................... 625.3.6. Supported-Vendor-Id AVP...................... 625.3.7. Product-Name AVP............................. 625.4. Disconnecting Peer Connections........................ 625.4.1. Disconnect-Peer-Request...................... 635.4.2. Disconnect-Peer-Answer....................... 635.4.3. Disconnect-Cause AVP......................... 635.5. Transport Failure Detection........................... 645.5.1. Device-Watchdog-Request...................... 645.5.2. Device-Watchdog-Answer....................... 645.5.3. Transport Failure Algorithm.................. 655.5.4. Failover and Failback Procedures............. 655.6. Peer State Machine.................................... 665.6.1. Incoming connections......................... 685.6.2. Events....................................... 695.6.3. Actions...................................... 705.6.4. The Election Process......................... 716. Diameter Message Processing.................................. 716.1. Diameter Request Routing Overview..................... 716.1.1. Originating a Request........................ 736.1.2. Sending a Request............................ 736.1.3. Receiving Requests........................... 736.1.4. Processing Local Requests.................... 736.1.5. Request Forwarding........................... 746.1.6. Request Routing.............................. 746.1.7. Redirecting Requests......................... 746.1.8. Relaying and Proxying Requests............... 756.2. Diameter Answer Processing............................ 766.2.1. Processing Received Answers.................. 776.2.2. Relaying and Proxying Answers................ 776.3. Origin-Host AVP....................................... 776.4. Origin-Realm AVP...................................... 786.5. Destination-Host AVP.................................. 786.6. Destination-Realm AVP................................. 786.7. Routing AVPs.......................................... 786.7.1. Route-Record AVP............................. 796.7.2. Proxy-Info AVP............................... 796.7.3. Proxy-Host AVP............................... 796.7.4. Proxy-State AVP.............................. 796.8. Auth-Application-Id AVP............................... 796.9. Acct-Application-Id AVP............................... 796.10. Inband-Security-Id AVP................................ 796.11. Vendor-Specific-Application-Id AVP.................... 806.12. Redirect-Host AVP..................................... 806.13. Redirect-Host-Usage AVP............................... 806.14. Redirect-Max-Cache-Time AVP........................... 816.15. E2E-Sequence AVP...................................... 82Calhoun, et al. Standards Track [Page 3]

Activity (31)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Philipp Shilov liked this
Ashish Singh liked this
Varun Sidhu liked this
SOUMIK liked this
Alex_Mallo_1576 liked this
zenios2090 liked this
Henry Cho liked this

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->