[BLISS] Automatic Handling Survey

Shida Schubert <shida@ntt-at.com> Mon, 29 October 2007 21:22 UTC

Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Imc47-00035o-Pv; Mon, 29 Oct 2007 17:22:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Imc46-000351-U3 for bliss@ietf.org; Mon, 29 Oct 2007 17:22:30 -0400
Received: from agnada.com ([69.36.182.244]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Imc46-0000Kx-FX for bliss@ietf.org; Mon, 29 Oct 2007 17:22:30 -0400
Received: from [192.168.1.101] (S0106001839eceb7a.vc.shawcable.net [24.80.240.54]) (authenticated bits=0) by agnada.com (8.12.11.20060308/8.12.11) with ESMTP id l9TLM4mD020563 for <bliss@ietf.org>; Mon, 29 Oct 2007 15:22:04 -0600
Message-ID: <47264EF1.40201@ntt-at.com>
Date: Mon, 29 Oct 2007 14:21:53 -0700
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: bliss@ietf.org
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Subject: [BLISS] Automatic Handling Survey
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: shida@ntt-at.com
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
Errors-To: bliss-bounces@ietf.org

All;

In Chicago, there was a suggestion to take one of the
milestones and use it as a guinea pig to evaluate the
process described in the problem statement draft for
its effectiveness and functionality.

Problem Statement: 
http://tools.ietf.org/html/draft-ietf-bliss-problem-statement-00.txt

Amongst the chairs and the technical adviser, we decided to
take up the milestone "Automatic Handling" as a guinea pig.

The idea was to conduct a phase 1 (Identify a Feature Group) and
Phase 2 (Submit Feature Flows) in a small group (Authors and chairs)
and contact various vendors to gather information necessary to
identify the problem source.

After some discussion, we realized that contacting individuals
to collect call-flow wasn't as easy as we initially thought it would
be due to the time and effort on the individuals part.

So, to get a reasonable amount of feedback to make any fruitful
conclusions or suggestion(s) that would ultimately solve the
interoperability issues, there was an obvious need to lower the
threshold for providing information.

To do this, we set-up a web form which should take no longer than
5 minutes to complete.

Beside BLISS, we are going to ask SIPForum and participants at
SIPit to participate in the survery(web form), with which we should
get enough feedback to assess the preliminary problem of the space
we are dealing with. If you know somebody that can answer the
questions better than you please forward the link below.

After we have enough information on the statistics of current
implementations in the wild, we can then have a in-depth discussion
on the list. And come up with a clear definition of problem
space(phase 3) as well as recommendation(phase 4).

Below is the link to the web-form, I ask for your feedback and
I thank you for your time and participation.

http://www.bliss-ietf.org/autohandle/?id=27bl01dn22d


 Regards
  Shida

_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www1.ietf.org/mailman/listinfo/bliss