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
requirement
Click on the red underlined text to get to the source
...
In addition to addressing the above requirements, Diameter also
provides support for the following:
...
... The Diameter base protocol provides the minimum requirements needed
for a AAA protocol, as required by [AAAREQ ...
... Diameter. Therefore, it is imperative that the designers of new
applications understand their requirements before using Diameter.
...
... ABNF] grammar (see
Section 3.2). If the Diameter application has accounting
requirements, it MUST also specify the AVPs that are to be present in
the Diameter Accounting messages ...
... AVPs within an AVP of type Grouped have the
same padding requirements as non-Grouped AVPs, as defined in Section
4.
...
... accounting records in any order and at any time, and does not place
any standards requirement on the processing of these records.
Implementations of Diameter MAY perform checking, ordering,
...
... dependent, they are not standardized by the Diameter specifications.
Applications MAY define requirements on when to accept accounting
records based on the used value of Accounting-Realtime-Required ...
... real-time transfer of accounting records
is a requirement, such as the need to perform credit limit checks and
fraud detection. Note that batch accounting is not a requirement ...
... requirement, such as the need to perform credit limit checks and
fraud detection. Note that batch accounting is not a requirement,
and is therefore not supported by Diameter. Should batched
...
... Diameter accounting server MAY override the interim interval or
the realtime requirements by including the Acct-Interim-Interval or
Accounting-Realtime-Required ...
... Application document requirements ...
... Accounting messages. These
AVP occurrence requirements are guidelines, which may be expanded,
and/or overridden by application-specific requirements ...
... requirements are guidelines, which may be expanded,
and/or overridden by application-specific requirements in the
Diameter applications documents.
...
... Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. ...
... Hiller, T., Walsh, P., Chen, X., Munson, M., Dommety, G., Sivalingham, S., Lim, B., McCann, P., Shiino, H., Hirschman, B.,
Manning, S., Hsu, R., Koo, H., Lipford, M., Calhoun, P., Lo, C., Jaques, E., Campbell, E., Xu, Y., Baba, S., Ayaki, T., Seki,
T. and A. Hameed, "CDMA2000 Wireless Data Requirements for AAA", RFC 3141, June 2001. ...
... Glass, S., Hiller, T., Jacobs, S. and C. Perkins, "Mobile IP Authentication, Authorization, and Accounting Requirements", RFC 2977, October 2000. ...
... Mitton, D. and M. Beadles, "Network Access Server Requirements Next Generation (NASREQNG) NAS Model", RFC 2881, July 2000. ...