RFC 3588:Diameter Base Protocol
RFC-Ref

Session-Id


Click on the red underlined text to get to the source

... sessions. Multi-sessions are tracked by using the Acct-Multi-Session-Id. An example of a multi-session would be a Multi-link ...
... session) or serially. These changes in sessions are tracked with the Accounting-Sub-Session-Id. Transaction ...


... AVP that is included to reference a user's session is the Session-Id. The initial request for authentication ...
... authentication and/or authorization of a user would include the Session-Id. The Session-Id is then used in all subsequent messages to identify the user's session ...
... authorization of a user would include the Session-Id. The Session-Id is then used in all subsequent messages to identify the user's session (see Section 8 for ...
... Session state (associated with a Session-Id) MUST be freed upon receipt of the Session-Termination-Request, Session ...
... concept at the application layer, and is shared between an access device and a server, and is identified via the Session-Id AVP ...


... { Origin-Host } 1*{ Session-Id } *[ AVP ] ...
... Session-Ids must follow. Here there are two: Session-Id = "grump.example.com:33041;23432;893;0AF3B81" ...
... "grump.example.com:33041;23432;893;0AF3B81" Session-Id = "grump.example.com:33054;23561;2358;0AF3B82" ...
... 16 | 'e' | 'x' | 'a' | 'm' | 'p' | 'l' | 'e' | '.' | +-------+-------+-------+-------+-------+-------+-------+-------+ 24 | 'c' | 'o' | 'm' |Padding| Session-Id AVP Header | ...
... 64 | 'A' | 'F' | '3' | 'B' | '8' | '1' |Padding|Padding| +-------+-------+-------+-------+-------+-------+-------+-------+ 72 | Session-Id AVP Header (AVP Code ...
... Realtime-Required | | | | | | Acct- 50 9.8.5 UTF8String | M | P | | V | Y | Multi-Session-Id | | | | | | Accounting- 485 9.8.3 Unsigned32 ...
... Accounting- 44 9.8.4 OctetString| M | P | | V | Y | Session-Id | | | | | | Accounting- 287 9.8.6 Unsigned64 ...
... Accounting- 287 9.8.6 Unsigned64 | M | P | | V | Y | Sub-Session-Id | | | | | | Acct- 259 6.9 Unsigned32 | M | P | | V | N | ...
... Route-Record 282 6.7.1 DiamIdent | M | | | P,V | N | Session-Id 263 8.8 UTF8String | M | P | | V | Y | Session-Timeout 27 8.13 Unsigned32 ...


... failure. - If the Session-Id is present in the request, it MUST be included in the answer. ...
... All messages within the same session, as defined by the same value of the Session-ID AVP MAY be sent to the host specified in the ...


... DIAMETER_UNKNOWN_SESSION_ID 5002 The request contained an unknown Session-Id. DIAMETER ...
... ERR [PXY] > 0*1< Session-Id > { Origin-Host } ...


... Diameter application (e.g., NASREQ). The request contains a Session-Id AVP, which is used in subsequent messages (e.g., subsequent authorization ...
... accounting, etc) relating to the user's session. The Session-Id AVP is a means for the client and servers ...
... Diameter protocol, even in combination with an application, the Session-Id is still used to identify user sessions. However, the session termination ...
... An access device that receives a RAR message with Session-Id equal to a currently active session ...
... Diameter Header: 258, REQ, PXY > < Session-Id > { Origin-Host } ...
... Diameter Header: 258, PXY > < Session-Id > { Result-Code } ...
... resources (e.g., session state) associated with the Session-Id specified in the STR, and return a Session-Termination-Answer ...
... Diameter Header: 275, REQ, PXY > < Session-Id > { Origin-Host } ...
... Diameter Server MUST release all resources for the session indicated by the Session-Id AVP. Any intermediate server in the Proxy ...
... Diameter Header: 275, PXY > < Session-Id > { Result-Code } ...
... An access device that receives an ASR with Session-ID equal to a currently active session ...
... service, to request that the session identified by the Session-Id be stopped. Message Format ...
... Diameter Header: 274, REQ, PXY > < Session-Id > { Origin-Host } ...
... If the session identified by Session-Id in the ASR was successfully terminated, Result-Code ...
... Diameter Header: 274, PXY > < Session-Id > { Result-Code } ...
... Session-Id AVP ...
... The Session-Id AVP (AVP Code 263) is of type UTF8String and is used ...
... session (see Section 8). All messages pertaining to a specific session MUST include only one Session-Id AVP and the same value MUST be used throughout the life of a session ...
... and the same value MUST be used throughout the life of a session. When present, the Session-Id SHOULD appear immediately following the Diameter Header ...
... Header (see Section 3). The Session-Id MUST be globally and eternally unique, as it is meant to uniquely identify a user session without reference to any other ...
... information, and may be needed to correlate historical authentication information with accounting information. The Session-Id includes a mandatory portion and an implementation-defined portion; a ...
... below. The Session-Id MUST begin with the sender's identity encoded in the ...
... identity encoded in the DiameterIdentity type (see Section 4.4). The remainder of the Session-Id is delimited by a ";" character, and MAY be any sequence that the client can guarantee to be eternally unique; however, the ...
... accesspoint7.acme.com;1876543210;523;mobile@200.1.1.88 The Session-Id is created by the Diameter application initiating the ...
... session, which in most cases is done by the client. Note that a Session-Id MAY be used for both the authorization and accounting ...


... in transit. This detection MUST be based on the inspection of the Session-Id and Accounting-Record-Number AVP pairs. Appendix C ...
... In all accounting records, the Session-Id AVP MUST be present; the User-Name ...
... session. A particular value of Accounting-Sub-Session-Id MUST appear only in one sequence of accounting records from a DIAMETER ...
... The Diameter protocol's Session-Id AVP, which is globally unique (see Section 8.8), is used during the authorization ...
... Services that do not require any authorization still use the Session-Id AVP to identify sessions. Accounting ...
... sessions. Accounting messages MAY use a different Session-Id from that sent in authorization messages. Specific applications MAY require different ...
... authorization messages. Specific applications MAY require different a Session-ID for accounting messages. ...
... accounting sub-sessions. Such applications would send messages with a constant Session-Id AVP, but a different Accounting-Sub-Session-Id ...
... a constant Session-Id AVP, but a different Accounting-Sub-Session-Id AVP. In these cases, correlation is performed using the Session-Id ...
... Accounting-Sub-Session-Id AVP. In these cases, correlation is performed using the Session-Id. It is important to note that receiving a STOP_RECORD with no ...
... It is important to note that receiving a STOP_RECORD with no Accounting-Sub-Session-Id AVP when sub-sessions were originally used ...
... service from different access devices (e.g., Mobile IPv4), each with their own unique Session-Id. In such cases, the Acct-Multi-Session- Id AVP ...
... determines that a request is for an existing session SHOULD include the Acct-Multi-Session-Id AVP, which the access device MUST include in all subsequent accounting ...
... accounting messages. The Acct-Multi-Session-Id AVP MAY include the value of the original Session-Id ...
... Acct-Multi-Session-Id AVP MAY include the value of the original Session-Id. It's contents are implementation specific, but MUST be globally unique across other Acct-Multi-Session-Id, and MUST NOT ...
... Session-Id. It's contents are implementation specific, but MUST be globally unique across other Acct-Multi-Session-Id, and MUST NOT change during the life of a session. ...
... Diameter Header: 271, REQ, PXY > < Session-Id > { Origin-Host } ...
... [ User-Name ] [ Accounting-Sub-Session-Id ] [ Acct-Session-Id ] ...
... [ Accounting-Sub-Session-Id ] [ Acct-Session-Id ] [ Acct-Multi-Session-Id ] ...
... [ Acct-Session-Id ] [ Acct-Multi-Session-Id ] [ Acct-Interim-Interval ] ...
... Accounting-Request command. The Accounting-Answer command contains the same Session-Id and includes the usage AVPs only if CMS ...
... Diameter Header: 271, PXY > < Session-Id > { Result-Code } ...
... [ User-Name ] [ Accounting-Sub-Session-Id ] [ Acct-Session-Id ] ...
... [ Accounting-Sub-Session-Id ] [ Acct-Session-Id ] [ Acct-Multi-Session-Id ] ...
... [ Acct-Session-Id ] [ Acct-Multi-Session-Id ] [ Error-Reporting-Host ] ...
... Unsigned32 and identifies this record within one session. As Session-Id AVPs are globally unique, the combination of Session-Id ...
... Session-Id AVPs are globally unique, the combination of Session-Id and Accounting- Record-Number AVPs ...
... Acct-Session-Id AVP ...
... The Acct-Session-Id AVP (AVP Code 44) is of type OctetString ...
... AVP contains the contents of the RADIUS Acct-Session-Id attribute. ...
... Acct-Multi-Session-Id AVP ...
... The Acct-Multi-Session-Id AVP (AVP Code 50) is of type UTF8String, ...
... AVP Code 50) is of type UTF8String, following the format specified in Section 8.8. The Acct-Multi- Session-Id AVP is used to link together multiple related accounting ...
... sessions, where each session would have a unique Session-Id, but the same Acct-Multi-Session-Id AVP ...
... session would have a unique Session-Id, but the same Acct-Multi-Session-Id AVP. This AVP MAY be returned by the ...
... Accounting-Sub-Session-Id AVP ...
... The Accounting-Sub-Session-Id AVP (AVP Code 287) is of type ...
... accounting sub-session identifier. The combination of the Session-Id and this AVP MUST be unique per sub- session ...
... whose Accounting-Record-Type is set to STOP_RECORD. A STOP_RECORD message with no Accounting-Sub-Session-Id AVP present will signal the termination of all sub-sessions ...
... AVP present will signal the termination of all sub-sessions for a given Session-Id. ...


... Session-Binding |0 |0 |0 |0 |0 |0 |0 |0 |0 |0 |0 |0 | Session-Id |0 |0 |0 |0 |0 |0 |1 |1 |1 |1 |1 |1 | Session-Server- |0 |0 |0 |0 |0 |0 |0 |0 |0 |0 |0 |0 | ...
... Acct-Interim-Interval | 0-1 | 0-1 | Acct-Multi-Session-Id | 0-1 | 0-1 | Accounting-Record-Number | 1 | 1 | ...
... Accounting-Record-Type | 1 | 1 | Acct-Session-Id | 0-1 | 0-1 | Accounting-Sub-Session-Id | 0-1 | 0-1 | ...
... Acct-Session-Id | 0-1 | 0-1 | Accounting-Sub-Session-Id | 0-1 | 0-1 | Accounting-Realtime-Required | 0-1 | 0-1 | ...
... Result-Code | 0 | 1 | Session-Id | 1 | 1 | Termination-Cause | 0-1 | 0-1 | ...



Google
Web
RFC-Ref