Subject: [BLISS] Minutes from Call-Completion Meeting:08.02.14

From: Shida Schubert <[email-masked]>
Date: Tue, 19 Feb 2008 10:38:49 -0800

I have attached the minutes from the Call-Completion design
team meeting we had last Thursday.

Date/Time:
--------------------
2008.02.14 09:00PST-10:00PST

Attendees:
--------------------
- Dale Worley
- Dennis Alexeitsev
- Dennis Lubber
- Enrico Marocco
- Martin Huelsemann
- Shida Schubert
- Eric Sasaki

Agenda:
----------------------------------
1. Revisit the remaining issues.
 >> Call Retention (Suspend/Resume)
 >> Dialog Correlation
 >> Draft Consolidation
2. Action Plans
3. Next Meeting

Discussion:
-----------------------------------
1. Revisit the remaining issues.
- Suspend/Resume
  >> Question, can this be done via SUBSCRIBE?
   > Problem, can't diffirentiate the activation and resume.
    > Problem is how to reach the same GW.
    >> Enrico will send out the text regarding the use of
       route-set.

- Chair asked that design team focuses on solving the call-completion
  in the context of pure SIP environment first.

- Correlating the original call with call-completion activation.
  >> Call-id can be used in pure SIP scenario.
  >> Because there may be multiple PSTN-GW involved may not work
     in PSTN-interop scenario.
     >> Suggestions
       - Call-id usage will be the basic approach.
       - In case a paricular id which distinguish call-id is present,
         value within this would be used. >> Ambiguous as to whether
         we are going to add a text on this or not.
       - Suggestions to make a note that in some deployment, caller/callee
         identity may be sufficient to correlate the
         original call/activation/completion call.(Closed Garden)
  >> Agreed that call-info etc. are still used to indicate the mode etc.

- Merging of the draft.
  >> Martin and Dale will send the text/xml to Shida, Shida will merge the
     two and submit.
  >> Design team will read the abstract/introduction of the two drafts and
     send recommended text to the list.

2. Action Plan
-----------------------------------------------------
 1. Dale will send XML/text of his draft to Shida.
 2. Martin will send text for poetzl draft to Shida.
 3. Shida will look after the submission of the 00 draft.
 4. Dale will post the list of remaining issues that are preventing the
    call-completion to work in pure SIP environment, if any.
 5. Design Team will read the abstract/introduction of the two drafts and
    send some recommended text for abstract/introduction used for the 
merged draft.
 6. Design Team, if hasn't read the thread will read the thread and 
continue
    the discussion.

3. Next Meeting:
-----------------------------------------------------
Feb 21st 09:00PST-10:00PST

_______________________________________________
BLISS mailing list
[email-masked]
http://www.ietf.org/mailman/listinfo/bliss