[BLISS] Minutes from Call-Completion Meeting: 08.06.05
Shida Schubert <shida@ntt-at.com> Thu, 12 June 2008 16:18 UTC
Return-Path: <bliss-bounces@ietf.org>
X-Original-To: bliss-archive@optimus.ietf.org
Delivered-To: ietfarch-bliss-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C570E3A695A; Thu, 12 Jun 2008 09:18:22 -0700 (PDT)
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB50A3A695A for <bliss@core3.amsl.com>; Thu, 12 Jun 2008 09:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GpFtSx3E5oq9 for <bliss@core3.amsl.com>; Thu, 12 Jun 2008 09:18:21 -0700 (PDT)
Received: from gateway16.websitewelcome.com (gateway16.websitewelcome.com [70.85.130.5]) by core3.amsl.com (Postfix) with SMTP id DFA3B3A6823 for <bliss@ietf.org>; Thu, 12 Jun 2008 09:18:20 -0700 (PDT)
Received: (qmail 32190 invoked from network); 12 Jun 2008 16:22:18 -0000
Received: from gator465.hostgator.com (69.56.174.130) by gateway16.websitewelcome.com with SMTP; 12 Jun 2008 16:22:18 -0000
Received: from [66.37.169.174] (port=53546 helo=[192.168.10.8]) by gator465.hostgator.com with esmtp (Exim 4.68) (envelope-from <shida@ntt-at.com>) id 1K6pVb-0001OO-KQ for bliss@ietf.org; Thu, 12 Jun 2008 11:18:43 -0500
Message-Id: <35C052D9-F512-44C5-BDEF-F53EDC53E409@ntt-at.com>
From: Shida Schubert <shida@ntt-at.com>
To: bliss@ietf.org
Mime-Version: 1.0 (Apple Message framework v924)
Date: Thu, 12 Jun 2008 06:18:45 -1000
X-Mailer: Apple Mail (2.924)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator465.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ntt-at.com
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: [BLISS] Minutes from Call-Completion Meeting: 08.06.05
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: bliss-bounces@ietf.org
Errors-To: bliss-bounces@ietf.org
Below is the minutes from Call-Completion design team meeting
last week.
Meeting Date/Time:
--------------------
2008.06.05 09:00PST-10:00PST
Attendees:
--------------------
Denis Alexitsev
Martin Huelsemann
Dennis Lubbers
Enrico Marocco
Shida Schubert
* Please send me an e-mail, if I've missed anybody..
Agenda:
--------------------
1. Discuss the ongoing issues regarding SUS/RES.
2. Potential use of context-id for the dialog-correlation
3. Meeting Frequency.
4. Action Items
Discussion:
--------------------
1. Recapturing the issues about SUS/RES.
- Martin explained when considering the interworking explicit SUS/RES
is needed.
- Dennis.L asks if some indication can be added on the SUBSCRIBE.
- Rest of the team explained how SUBSCRIBE can't change the state,
and that
this has been discussed in the past before at the meeting.
- Dennis.L will write up a text that will illustrate how UNSUB/RESUB
(implicit method) will not work.
- Dennis.L suggested the use of SUBSCRIBE to monitor the caller's
agent to modify the
SUS/RES status (If caller is busy simply put the state to RESUME).
- Denis.A explained that this was suggested before and it was declined
as an overkill.
- Design team asked if Paul can join the teleconference.
>> Chair will take this up.
2. Potential use of context-id for the dialog-correlation
- Martin explained the draft that writes about context-id:
- It may be useful for the dialog-correlation.
- Denis summarized the gist of draft.
- Discuss with the authors/Gonzalo about the use of this
document to accomplish dialog correlation. Design team agreed that
if there is a
common mechanism that can be used to correlate the dialog, there is
no need to
invent something else.
3. Scheduling the next meeting
- Will try to invite Paul and hold it on June 12th 9:00PST-10:00PST
4. Action Items
- Chair
Invite Paul to the teleconference.
- Dennis.L
Illustrate why implicit SUS/RES will not work in case of
interworking.
- Rest of the design team
Read the revised draft.
Regards
Shida
_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www.ietf.org/mailman/listinfo/bliss
- [BLISS] Minutes from Call-Completion Meeting: 08.… Shida Schubert