Hi Dale,
sorry to be late on this answer, I agree that have a clear understanding
of the capabilities
we want for the mechanism is necessary to clearly write down the
requirement.
In my mind I have an Idea equal on what you expressed in Req A
Req A: It must be possible, when establishing a dialog, to specify that
it be correlated with one or more already existing dialogs, which
dialogs, at the time they were created, did not need to specify that
they might be correlated with in the future.
However, the requirements need to be discussed and agreed by all the wg
and also Req B , that is a little more restrictive could be from my
point of view an acceptable compromise.
/Sal
Dale Worley wrote:
On Fri, 2008-12-19 at 16:45 +0200, salvatore loreto wrote:
Do you think we should be more explicit on this point?
The first question is to come to a clearer understanding in our own
minds what capabilities we want the mechanism to have. After that, we
can write clearly what the requirements are.
In this case, the following two requirements may be quite different in
regard to the solutions that they admit:
Req A: It must be possible, when establishing a dialog, to specify that
it be correlated with one or more already existing dialogs, which
dialogs, at the time they were created, did not need to specify that
they might be correlated with in the future.
Req B: It must be possible, when establishing a dialog, to specify that
it be correlated with one or more already existing dialogs, which
dialogs, at the time they were created, may be required to have
specified that they might be correlated with in the future.
Dale
_______________________________________________
Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP
