RFC 3588:Diameter Base Protocol
RFC-Ref

Proxies


Click on the red underlined text to get to the source

... RADIUS] does not provide for explicit support for agents, including Proxies, Redirects and Relays. Since the expected behavior is not defined, it varies between implementations. Diameter ...
... RADIUS does not define data-object security mechanisms, and as a result, untrusted proxies may modify attributes or even packet headers without being detected. Combined with lack of support for capabilities negotiation ...
... roaming between providers. However, since RADIUS does not provide explicit support for proxies, and lacks auditability and transmission-level security features, RADIUS ...
... authenticate and/or authorize messages locally; agents include proxies, redirects and relay agents. A Diameter server ...
... Agent or Proxy In addition to forwarding requests and responses, proxies make policy decisions relating to resource usage and provisioning. This is typically accomplished by tracking the state ...
... state of NAS devices. While proxies typically do not respond to client Requests prior to receiving a Response from the server, they may ...
... receiving a Response from the server, they may originate Reject messages in cases where policies are violated. As a result, proxies need to understand the semantics of the messages passing through them, and may not support all Diameter applications ...
... integrity and confidentially, even in the presence of relays and/or proxies. Session ...


... Diameter proxies MUST support the base protocol, which includes accounting ...
... Relay agents MUST NOT reorder AVPs, and proxies MUST NOT reorder AVPs. ...
... Diameter Routing Table. However, they differ since they modify messages to implement policy enforcement. This requires that proxies maintain the state of their downstream ...
... provisioning. It is important to note that although proxies MAY provide a value-add function for NASes, they do not allow access devices to use end-to- ...
... authentication. Proxies MAY be used in call control centers or access ISPs that provide outsourced connections ...
... according to their configuration. Proxies that wish to limit resources MUST maintain session state. ...
... session state. All proxies MUST maintain transaction state. ...
... Since enforcing policies requires an understanding of the service being provided, Proxies MUST only advertise the Diameter applications they support. ...


... Diameter agents (proxies, redirects or relays) MUST also contain an Acct- Application-Id AVP, an Auth-Application-Id ...
... Diameter agents (proxies, redirects or relays) MUST not include the Destination-Realm in its ABNF ...
... Diameter message that may be forwarded by Diameter agents (proxies, redirects or relays) MUST include the target realm in the ...


... on a per-hop basis, and Diameter proxies MAY attempt to correct the error, if it is possible. Note that these and only these errors MUST only be used in answer messages ...


... connected with the access device will not discover that the access device has been restarted unless and until it receives a new request from the access device. Thus, use of this mechanism across proxies is opportunistic rather than reliable, but useful nonetheless. ...



Google
Web
RFC-Ref