Subject: [AAA-WG]: Issue 102: clarification on difference between session and peer c onnection

From: Yiwen Jiang <[email-masked]>
Date: Fri, 27 Jul 2001 15:57:01 -0400

Submitter name: Jacques Caron, Yiwen Jiang
Submitter email address: [email-masked]
Date first submitted: July 27th, 2001
Reference: N/A
Document: base
Comment type: E
Priority: 1
Section: 
Rationale/Explanation of issue: 

The relationship between peer-to-peer connection vs. user session was not
specified in the base protocol. 

Requested change:
(Below is my first attempt at modifying the initial email that Pat sent out
to clairfy such. Maybe we can added in section 8.0.)

While peer-to-peer connections is a transport level connection, a user
session is a logical concept at the application level. It exists over one or
many peer-to-peer connections. 

 +--------+            +-------+           +--------+
 | Client |            | Relay |           | Server |
 +--------+            +-------+           +--------+
           <---------->        <---------->
           peer connection A    peer connection B

           <------------------------------>
                       User session x

In the above example, peer connection A is established between the Client
and its local Relay. Peer connection B is established between the Relay and
the Server. User session x spans from the Client via the Relay to the
Server. Each "user" of a service causes an auth request to be sent, with a
unique session identifier. Once accepted by the server, both the client and
the server are aware of the session. Because of this behaviour, all Diameter
clients will need to first initiate a peer-to-peer connection before it can
issue user requests to its immediate Diameter peer. All user sessions are
"multiplexed" through a single connection.

Cheers,
Yiwen
---
Yiwen Jiang
Mobile IP Networking
Email: [email-masked]
Phone: (613)271-7710

Telecom Innovation Centre
505 March Road
Kanata, Ontario, Canada
K2K 2M5