Re: [sipcore] Some comments on draft-barnes-sipcore-rfc4244bis-03

Shida Schubert <shida@ntt-at.com> Wed, 02 December 2009 05:28 UTC

Return-Path: <shida@ntt-at.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5DF2E3A6765 for <sipcore@core3.amsl.com>; Tue, 1 Dec 2009 21:28:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.19
X-Spam-Level:
X-Spam-Status: No, score=-2.19 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 j6eZeXsjloaf for <sipcore@core3.amsl.com>; Tue, 1 Dec 2009 21:28:33 -0800 (PST)
Received: from gateway13.websitewelcome.com (gateway13.websitewelcome.com [67.18.82.4]) by core3.amsl.com (Postfix) with SMTP id 7602E3A67AB for <sipcore@ietf.org>; Tue, 1 Dec 2009 21:28:33 -0800 (PST)
Received: (qmail 17148 invoked from network); 2 Dec 2009 05:42:18 -0000
Received: from gator465.hostgator.com (69.56.174.130) by gateway13.websitewelcome.com with SMTP; 2 Dec 2009 05:42:18 -0000
Received: from fl1-118-109-66-179.tky.mesh.ad.jp ([118.109.66.179]:63098 helo=[192.168.1.5]) by gator465.hostgator.com with esmtpa (Exim 4.69) (envelope-from <shida@ntt-at.com>) id 1NFhl3-00028c-Vj; Tue, 01 Dec 2009 23:28:10 -0600
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
From: Shida Schubert <shida@ntt-at.com>
In-Reply-To: <10A79C23-41FB-4FF8-AD55-2F83D7017EFC@gmail.com>
Date: Wed, 02 Dec 2009 14:28:22 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <057B55FD-2B09-4296-AB60-6FA7E47EDD37@ntt-at.com>
References: <4B13C4FC.5050907@sipstation.com> <98E67934-70CE-49E4-A2C3-05C3EB42573F@skype.net> <C25ED9E1-DA40-4D79-92FA-148958AE2154@ntt-at.com> <10A79C23-41FB-4FF8-AD55-2F83D7017EFC@gmail.com>
To: Francois Audet <audet.francois@gmail.com>
X-Mailer: Apple Mail (2.1077)
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
Cc: sipcore@ietf.org
Subject: Re: [sipcore] Some comments on draft-barnes-sipcore-rfc4244bis-03
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Dec 2009 05:28:34 -0000

 I don't think we need normative text, the whole examples are 
in appendix anyways, but I think what people want is to have 
explicit text on how one can determine the first versus the 
last redirecting target. I am not the one asking for them so 
I can't speak for them though.. 

 Regards
  Shida

On Dec 2, 2009, at 12:55 PM, Francois Audet wrote:

> That seems pretty reasonable to me. But...
> 
> Perhaps we can clarify a bit more in explaining why a voicemail system would choose the first versus the last redirecting target.  This is typically not a "configuration" as described in your example below (although, it is certainly possible).
> 
> Typically, a voicemail system will choose the first one IF it is responsible for the mailbox of that target. Obviously, it would be impossible otherwise. In this latter case, the voicemail system would then use the last redirecting number.
> 
> This is why I don't think we can put "normative" text, but instead "use case examples" as described above. A implementation could decide to always use the last redirecting number.
> 
> On Nov 30, 2009, at 17:39 , Shida Schubert wrote:
> 
>> 
>> Francois;
>> 
>> This was something Cullen asked we add to the draft too.
>> 
>> I am assuming what we need is to add an explicit text that aids
>> voicemail server to identify the target of the voicemail box.
>> 
>> If a call was initially received at Alice then diverted
>> to Carol,  then to Bob which then diverts to voicemail,
>> the question is for which AoR should the voicemail server
>> leave a voicemail?
>> 
>> I think the answer depends on the configuration
>> of the voicemail server. But with the "mp" tag and
>> "mp" index we can identify when the mapping
>> (diversion) took place making it much more
>> deterministic to identify the target of the voicemail box.
>> 
>> Looking at the example from the draft below;
>> 
>> History-Info: <sip:bob@example.com>;index=1
>> History-Info: <sip:bob@192.0.2.3?Reason=SIP;cause=302>;\
>>                  index=1.1;rc
>>    History-Info: <sip:carol@example.com>;index=1.2;mp=1
>>    History-Info: <sip:carol@192.0.2.4>;index=1.2.1;rc
>>    History-Info: <sip:vm@example.com>;index=1.3;mp=1.2
>>    History-Info: <sip:vm@192.0.2.5>;index=1.3.1
>> 
>> If the voicemail server is configured to use the voicemail box
>> of the initial target it can look for the first mp tag and look
>> at the hi-entry that mp index references (bob@example.com)
>> 
>> If the voicemail server is configured to use the voicemail box
>> of the last target then it can look for the last mp tag and look
>> at the hi-entry that mp index references (carol@example.com) etc.
>> 
>> Regards
>> Shida
>> 
>> On Dec 1, 2009, at 7:56 AM, Francois AUDET wrote:
>> 
>>> 
>>> On Nov 30, 2009, at 5:13 , Alan Johnston wrote:
>>> 
>>>> 
>>>> Does this document have a good voicemail example?  This is the application I am most interested in, so it would be nice to have a very clear example of this.
>>>> 
>>> 
>>> That was the intent of section B.2 (in the appendix).
>>> 
>>> Are you saying you'd want a better voicemail example? Or that we add more voicemail examples? What do you have in mind?
>>> _______________________________________________
>>> sipcore mailing list
>>> sipcore@ietf.org
>>> https://www.ietf.org/mailman/listinfo/sipcore
>> 
>