Below is the minutes from a few weeks ago for Call-Completion
design team meeting.
Meeting Date/Time:
--------------------
2008.03.27 09:00PST-10:00PST
Attendees:
--------------------
Dale Worley
Denis Alexitsev
Dennis Lubbers
Enrico Marocco
Shida Schubert
* Please send me an e-mail, if I've missed anybody..
Agenda:
--------------------
1. Recapturing the discussions from the IETF 71.
2. Meeting Frequency.
3. Action Items
Discussion:
--------------------
1. Recapturing the discussions from the IETF71
- Denis explained the presentation and the outcome of the meeting.
Topic 1: Call-Correlation
- Debate over the use of cookie in the call-info or R-URI.
- R-URI parameter has issues with B2BUA stripping it.
- If call-info is used, it better be noted somewhere
that it survives B2BUA etc.
- Debate over the use of term cookie for the information
which is going to be used to correlate the dialogs.
- Will call it a cookie for now.
*After some debate it was suggested to call it token.
Topic 2: Use of PUBLISH for suspend/resume
- Denis explained how PUBLISH may be used to control
suspend/resume. It's sent to the monitor but the
To header would contain the AoR of the A party (caller)
so it's indeed modifying the its own state which doesn't
violate the semantics of PUBLISH..
- Some debate on how this is done, time runs out so Dennis
will provide text.
2. Meeting Frequency
- Design team will meet up every 2 weeks.
- Will arrange a meeting as necessary.
3. Action Items
Denis.A
- Submit the overall idea of call correlation, and how
the information is conveyed to the design team ML based
on the outcome from the meeting.
- Submit the mechanism on how PUBLISH is going to address
the problem of suspend/resume even when the PUBLISH request
is indeed sent to the monitor without violating the semantics
of PUBLISH.
Dale
- Provide comments/nits on the draft.
- Submit e-mail to BLISS list regarding the issues surrounding
call-correlation.
- Send out the questions on some of the details about the mechanism
to the design team list.
Rest of the design team
- Read the drafts and provide comments for refinement of the draft.
Regards
Shida
_______________________________________________
BLISS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bliss
