[Ietf-not43] example changes

[Andrew Newton]

Based on the point of the MUST/SHOULD language as it relates to protocol 
requirements and service descriptions, I thought I'd throw a few samples 
out just to show what am doing.  If you have objections or suggestions, 
please speak now.


Example 1:

Before:
3.1.1 Mining Prevention

    The protocol MUST have a mechanism to limit the amount of data that
    may be accessed.  The service may have different limits for different
    types of data, as well as for authenticated and non-authenticated
    entities.  The protocol SHOULD be capable of expressing to the client
    these access limitations based on queries per session per unit of
    time, queries per source IP address per unit of time, and total
    queries from all client sessions per unit of time.  The service
    should be able to limit the amount of data based on the above types
    of limitations.

After:
3.1.1 Mining Prevention

3.1.1.1 Protocol Requirement

    The protocol MUST have a mechanism to limit the amount of data that
    may be accessed.  The protocol SHOULD be capable of expressing to the
    client these access limitations based on queries per session per unit
    of time, queries per source IP address per unit of time, and total
    queries from all client sessions per unit of time.

3.1.1.2 Service Description

    The limits placed on differing types of data or applied depending
    upon access status will most likely differ from server to server
    based on policy and need.  Servers should express these limitations
    to the client if policy allows.


Example 2:

Before:
3.1.7 Decentralization

    The service must be decentralized in design and principle and must
    not require the aggregation of data to a central repository, server,
    or entity.  The service may allow for the optional aggregation of
    data indexes or hints.  The protocol MUST NOT require aggregation of
    data indexes or hints.

After:
3.1.7 Decentralization

3.1.7.1 Protocol Requirement

    The protoocl MUST NOT require the aggregation of data to a central
    repository, server, or entity.  The protocol MUST NOT require
    aggregation of data indexes or hints to a central repository, server,
    or entity.

3.1.7.2 Service Description

    Some server operators may have a need to coordinate service in a mesh
    or some other framework with other server operators.  However, the
    ability to operate a CRISP compliant server should not require this.

-andy