On Tue, 2009-03-03 at 14:45 +0000, Hutton, Andrew wrote: > [AndyH] - The text in what is now in section 5.2. of -03 when it states > various things that the callers agent "can" do but if I understand the > text correctly these are all outside the scope of the document. However > whether the agent can do these things or not depends on the architecture > of the solution (i.e. where the caller's agent is located) so I think it > is best just not to mention the things that the agent "can" do but are > outside the scope of the document as it just complicates the draft.
It's out of scope *how* the agent does these things, but it is a requirement on the agent that it *can* do them. My goal for that section is to notify implementors as to what the agent must be able to do. Conversely, having enumerated the necessary capabilities of the agent, the reader can verify that the defined procedures later in the document do not require any further capabilities. Otherwise, the implementor will have to comb through the procedures to develop his own list of agent<-->UAC facilities. Dale _______________________________________________ BLISS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bliss
