[Ietf-not43] WG Last call: draft-ietf-crisp-requirements-04.txt

[Andrew Newton]

#@!*%! (now hitting my head against a wall!)

I think you are correct (I blame my cat).  To be clear, this is the 
following text missing?

 >  The protocol MUST provide different error messages to
 >  indicate whether the bag is of unrecognized format
 >  (permanent failure), if it contains unacceptable
 >  data (permanent failure), or if it contains data
 >  that means processing is refused at this time (transient
 >  failure).

Some text talking about:

 > I think it's also important to make  it clear that there
 > will be no more than one bag per referral.  If the referrant
 > server generates another referral itself, it must supply a new
 > bag (and it doesn't matter whether that's the same as
 > the old, cumulative, or entirely new).

To be clear, let's decide on the wording:

   There MUST be only one bag per referral.  If a referent
   server generates another referral, any bag accompanying
   that referral MUST be considered unrelated to the original
   bag.

And:

 >  The client MUST pass the bag as part of any query made  to a referrant
 > server as a result of this referreral.

While we're at it, perhaps a quick blurb at the top of the requirement 
defining "bag".

So section should read as follows (note I merged the last MUST sentence 
at the end of the first requirement paragraph):

3.1.13 Relay Bag

    The term "bag" in this section refers to a flexible container
    of content.

3.1.13.1 Protocol Requirement

    When issuing a referral, the protocol MUST be capable of supplying a
    relay bag from the server to the client, and the protocol MUST be
    capable of allowing the client to submit this relay bag with a query
    to the referred server.  The use of the relay bag MUST be OPTIONAL.
    The protocol MUST NOT make any assumptions regarding the contents of
    the relay bag, but the relay bag MUST be described using the schema
    language of the protocol.  The client MUST pass the bag as part
    of any query made to a referent server as a result of a referral.

    The protocol MUST provide different error messages to
    indicate whether the bag is of unrecognized format
    (permanent failure), if it contains unacceptable
    data (permanent failure), or if it contains data
    that means processing is refused at this time (transient
    failure).

    There MUST be only one bag per referral.  If a referent
    server generates another referral, any bag accompanying
    that referral MUST be considered unrelated to the original
    bag.

3.1.13.2 Service Description

    In some models where service coordination among participating server
    operators is utilized, there might be needs to allow a referring
    server to pass operator-to-operator coordination data along with the
    referral to the referent server.  Such needs might be auditing or
    tracking.  This feature requirement allows a server to pass to the
    client a flexible container of unspecified data ("bag") that the
    client should pass to the referent server.  The bag has no meaning to
    the client.


-andy

Leslie Daigle wrote:
> 
> Hmmm....
> 
> I thought we'd reached agreement on some additional text
> re. relay bags:
> 
> http://lists.verisignlabs.com/pipermail/ietf-not43/2003-February/000477.html 
> 
> 
> which doesn't appear here.
> 
> Leslie.