1 - 2 - 3 - 6 - 7 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W
create
Click on the red underlined text to get to the source
... corresponding shared secrets. This results in a large
administrative burden, and creates the temptation to reuse the
RADIUS shared secret ...
... interoperability issues. It is
expected that command codes are reused; new command codes can only be
created by IETF Consensus (see Section 11.2.1).
...
... When no existing AVP can be used, a new AVP should be created. The
new AVP being defined MUST use one of the data types listed in
...
... AVP be used (see Section 4.4).
In order to create a new AVP, a request MUST be sent to IANA, with a
...
... Diameter usage scenario find itself unable to fit within
an existing application without requiring major changes to the
specification, it may be desirable to create a new Diameter
application. Major changes to an application include:
...
... A dynamically discovered peer causes an entry in the Peer Table (see
Section 2.6) to be created. Note that entries created via DNS MUST
...
... Peer Table (see
Section 2.6) to be created. Note that entries created via DNS MUST
expire (or be refreshed) within the DNS TTL ...
... outside of the local realm, a routing table entry (see Section 2.7)
for the peer's realm is created. The routing table entry's
expiration MUST match the peer's expiration value.
...
... no transport connection exists with the new agent, one is created,
and the request is sent directly to it.
...
...
When a request is locally processed, the following procedures MUST be
applied to create the associated answer, in addition to any
additional procedures that MAY be discussed in the Diameter
application defining the command:
...
... This AVP contains the maximum number of seconds the peer and route
table entries, created as a result of the Redirect-Host, will be
cached. Note that once a host ...
... Redirect-Host, will be
cached. Note that once a host created due to a redirect indication
is no longer reachable, any associated peer and routing table entries
...
... AVP Code and other fields set as expected
in the missing AVP. The created AVP is then added to the Failed-
AVP ...
... Lifetime value is determined, since a low, non-zero, value could
create significant Diameter traffic, which could congest both the
...
... Diameter entity issuing this AVP MUST create a higher value for
this AVP each time its state ...
... accounting be required in the future, a new Diameter application will
need to be created, or it could be handled using another protocol.
Note, however, that even if at the Diameter layer ...
... client SHOULD store new accounting records there as soon as the
records are created and until a positive acknowledgement of their
reception from the Diameter Server has been received. Upon a reboot,
...
... are randomized so that large accounting message storms are not
created either among records or around a common service start
...
... created; an IPsec SA is automatically created based on a simple
static policy. Since IPsec extensions are typically not available to
...
... # . Additional applications may be defined in the future.
# An updated service template will be created at that time.
#
...
... # . Additional applications may be defined in the future.
# An updated service template will be created at that time.
#
NASREQ ...