RFC 3588:Diameter Base Protocol
RFC-Ref

identity


Click on the red underlined text to get to the source

... Authentication The act of verifying the identity of an entity (subject). ...
... NAI], is used in the Diameter protocol to extract a user's identity and realm. The identity is used to identify the user during authentication ...
... Diameter protocol to extract a user's identity and realm. The identity is used to identify the user during authentication and/or authorization ...


... Host identity Following the conventions described for the DiameterIdentity derived AVP ...
... 4. REDIRECT - Diameter messages that fall within this category MUST have the identity of the home Diameter server(s) appended, and returned to the sender ...
... Peer table. When the Local Action is set to RELAY or PROXY, this field contains the identity of the server(s) the message must be routed to. When the Local Action field is set to REDIRECT, this field contains the identity ...
... identity of the server(s) the message must be routed to. When the Local Action field is set to REDIRECT, this field contains the identity of one or more servers the message should be redirected to. ...
... AVP to all requests forwarded. The AVP contains the identity of the peer the request was received from. The home Diameter server ...


... state machine (see Section 5.6). This message allows the discovery of a peer's identity and its capabilities (protocol version number, supported Diameter applications ...
... connection request is received from a Diameter peer, it is not, in the general case, possible to know the identity of that peer until a CER is received from it. This is because host ...
... host and port determine the identity of a Diameter peer; and the source port of an ...
... incoming connection is arbitrary. Upon receipt of CER, the identity of the connecting peer can be uniquely determined from Origin-Host. ...


... agent MUST check for forwarding loops when receiving requests. A loop is detected if the server finds its own identity in a Route-Record AVP ...
... Destination-Host AVP contains the local host's identity, - The Destination-Host ...
... AVP to all requests forwarded. The AVP contains the identity of the peer the request was received from. ...
... - The local host's identity is encoded in the Origin-Host AVP. ...
... AVP (AVP Code 282) is of type DiameterIdentity. The identity added in this AVP MUST be the same as the one received in the Origin-Host ...
... AVP Code 280) is of type DiameterIdentity. This AVP contains the identity of the host that added the Proxy-Info AVP ...


... Result-Code AVP is different from the identity encoded in the Origin-Host AVP. ...
... AVP Code 294) is of type DiameterIdentity. This AVP contains the identity of the Diameter host ...


... The Session-Id MUST begin with the sender's identity encoded in the DiameterIdentity type (see Section 4.4). The remainder of the Session-Id ...


... Diameter connections MUST explicitly carry the Identity Payload fields (IDci and IDcr). The DOI provides for several types of ...



Google
Web
RFC-Ref