Changeset 325:5133b45e3305 in freeDiameter for README

Timestamp:

May 20, 2010, 2:23:11 PM (14 years ago)

Author:

Sebastien Decugis <sdecugis@nict.go.jp>

Branch:

default

Phase:

public

Message:

Updated documentation

File:

• README (modified) (2 diffs)

README

@@ -1 @@
-The freeDiameter daemon implements the Diameter base protocol.
-Loadable extensions add the logic of Diameter applications and advanced use of the daemon.
+freeDiameter is an implementation of Diameter.
+
+Diameter is a protocol designed to carry Authentication, Authorization and
+Accounting (AAA) payload. It is an evolution of the RADIUS protocol (as the 
+name suggests).
+
+Diameter is an extensible protocol. RFC3588 (currently under revision) defines the
+Base Protocol that all Diameter nodes must support, while other documents define
+the additional protocol support for specific applications. Such applications include 
+for example Network Access Servers (RFC4005), EAP (RFC4072), ...
+
+
+The implementation consists in several components:
+ - libfreeDiameter : the shared library provides the functions to manipulate Diameter
+      messages and dictionary. This library is meant to be re-used for other projects
+      that would require parsing or manipulating Diameter messages.
+      
+ - freeDiameterd : the daemon establishes the network connections with other Diameter
+      peers and performs the tasks described in Diameter Base Protocol, such as
+      watchdogs, basic routing, ...
+      
+ - extensions : the extensions provide the mean to augment the features of the
+      freeDiameterd daemon. Extensions can provide the handling of a Diameter 
+      application, but also advanced routing features, peer management, etc.
+
+
 See http://aaa.koganei.wide.ad.jp/ for more information on the project.
+
 freeDiameter was previously known as the "waaad" project (WIDE AAA Daemon)
 
@@ -11 +36 @@
 
 See INSTALL for information on building and using this software.
-
---------------
-Known possible bugs:
- - management of the Host-IP-Address values in CER/CEA may be strange (for TCP and SCTP)
-