requirement
Click on the red underlined text to get to the source
... security and
reliability requirements, it is not possible to devise a single
accounting protocol and set of security services ...
... management is to provide a set of
tools that can be used to meet the requirements of each application.
This document describes the currently available tools as well as the
...
... Requirements language ...
... accounting capabilities (stored or transmitted over the
wire), etc. Legal or financial requirements frequently
mandate archival accounting practices, and may often
...
... data for the purposes of capacity and trend analysis, cost
allocation, auditing, billing. Each of these tasks has different
requirements.
...
... sampling techniques to reduce data collection
requirements while still providing the forecast with the desired
statistical accuracy, it may be possible to tolerate high packet loss
...
... as long as bias is not introduced.
The security requirements for trend analysis and capacity planning
depend on the circumstances of data collection and the sensitivity of
...
...
When accounting data is used for billing purposes, the requirements
depend on whether the billing process is usage-sensitive or not.
...
... packet loss may translate directly to revenue loss. As a result, the
billing process may need to conform to financial reporting and legal
requirements, and therefore an archival accounting approach may be
needed.
...
... revenue, the security and reliability requirements are greater. Due
to financial and legal requirements such systems need to be able to
...
... reliability requirements are greater. Due
to financial and legal requirements such systems need to be able to
survive an audit. Thus security services such as authentication ...
... audit should be at least as stringent as those used in preparation of
the original invoice. Due to financial and legal requirements,
archival accounting practices are frequently required in this
...
... data
collection and security as are billing applications. Due to
financial and legal requirements, archival accounting practices are
frequently required in this application.
...
... either by the network device or by the AAA server. The requirements
for timeliness, security ...
... Requirements summary ...
... cost allocation and auditing, an archival approach to accounting is
frequently mandated, due to financial and legal requirements. Since
in such situations loss of accounting data can translate to revenue
...
... resilience against packet loss is only one aspect of meeting
archival accounting requirements.
As noted in [18 ...
... Implementors should be careful to ensure that
worst-case multiple record processing requirements do not exceed the
capabilities of their systems.
...
... home domain can also control the generation of multiple accounting
records, the estimation of the worst-case processing requirements can
be very difficult.
...
... critical, it has been argued that congestion control is not a
requirement; better to let other less-critical traffic back off in
...
... non-volatile storage. The practical
difference between these approaches is substantial; the former
approach will not satisfy archival accounting requirements while the
latter may. More predictable behavior can be achieved via use of
SCTP ...
... ASCII data representation enables use of highly efficient text
compression algorithms that can minimize storage requirements. Such
compression algorithms are only typically applied to session ...
... CPU requirements ...
... accounting events that have not yet been delivered only until
the timeout interval expires. As a result this model has the
smallest memory requirements. Once the timeout interval has expired,
the accounting event is lost, even if the device has sufficient
...
... accounting data transfer are capable of
satisfying the most demanding security requirements. However, such
systems are not typically capable of providing low processing delay,
although this may be addressed by the enhancements described in [20 ...
... their security and reliability requirements. Some uses such as
capacity planning may only require authentication, integrity ...
... security and
reliability requirements, it is not possible to devise a single
accounting protocol and set of security services ...
... tools that can be used to construct accounting
systems meeting the requirements of an individual application. As a
result, it is important to analyze a given accounting application to
...
... security and reliability
requirements of the application.
Based on an analysis of the requirements ...
... requirements of the application.
Based on an analysis of the requirements, it appears that existing
deployed protocols are capable of meeting the requirements for
...
... Based on an analysis of the requirements, it appears that existing
deployed protocols are capable of meeting the requirements for
intra-domain capacity planning and non-usage sensitive billing. In
...
... critical. Thus, it is possible to use SNMPv3 to satisfy these
requirements, without the NMRG extensions. These include TCP
...
... the security and reliability requirements are greater. As a result,
no existing deployed protocol satisfies the requirements. For
...
... reliability requirements are greater. As a result,
no existing deployed protocol satisfies the requirements. For
example, existing protocols lack data object security ...
... For usage sensitive billing, as well as cost allocation and auditing
applications, the reliability requirement are greater. Here
transport layer reliability ...
... security
scalability improvements such as the KSM can satisfy the requirements
in intra-domain use.
...
... data object security and receipt support are required. No existing
protocol can meet these requirements. A summary is given in the
table on the next page.
...
... Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. ...