Re: [Sipping] draft-rosenberg-sipping-acr-code-00.txt

Paul Kyzivat <pkyzivat@cisco.com> Tue, 10 January 2006 19:25 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EwP7r-0003GR-3V; Tue, 10 Jan 2006 14:25:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EwP7p-0003GM-8W for sipping@megatron.ietf.org; Tue, 10 Jan 2006 14:25:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01342 for <sipping@ietf.org>; Tue, 10 Jan 2006 14:24:25 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwPEa-00058N-ID for sipping@ietf.org; Tue, 10 Jan 2006 14:32:44 -0500
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 10 Jan 2006 11:25:36 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.99,351,1131350400"; d="scan'208"; a="19423374:sNHT24124472"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k0AJPE6X000844; Tue, 10 Jan 2006 14:25:33 -0500 (EST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 10 Jan 2006 14:25:33 -0500
Received: from [161.44.79.59] ([161.44.79.59]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 10 Jan 2006 14:25:28 -0500
Message-ID: <43C40A28.7060403@cisco.com>
Date: Tue, 10 Jan 2006 14:25:28 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] draft-rosenberg-sipping-acr-code-00.txt
References: <475FF955A05DD411980D00508B6D5FB00C290701@en0033exch001u.uk.lucent.com> <B9A01F73-5955-46CE-B8B1-81734CCD8F24@softarmor.com>
In-Reply-To: <B9A01F73-5955-46CE-B8B1-81734CCD8F24@softarmor.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Jan 2006 19:25:28.0446 (UTC) FILETIME=[9D3B11E0:01C6161B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: 7bit
Cc: "'rohan@ekabal.com'" <rohan@ekabal.com>, "Drage, Keith (Keith)" <drage@lucent.com>, "'sipping@ietf.org'" <sipping@ietf.org>, "'gonzalo.camarillo@ericsson.com'" <gonzalo.camarillo@ericsson.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

I vote YES.

Dean Willis wrote:
> 
> Since the draft defines a new SIP response code, I believe it would  
> need to be progressed through the SIP working group as a standards- 
> track document.
> 
> Do we have a consensus in SIPPING on the fundamental requirements and  
> the general approach? If so, we can forward this work to SIP for  
> completion.
> 
> -- 
> Dean
> 
> 
> On Jan 5, 2006, at 5:24 AM, Drage, Keith (Keith) wrote:
> 
>> At the ad-hoc SIPPING meeting in Vancouver to discuss ETSI TISPAN  
>> issues, http://www.ietf.org/internet-drafts/draft-rosenberg-sipping- 
>> acr-code-00.txt was presented as the appropriate solution to the  
>> TISPAN issue of how to reject anonymous calls. Note that an  anonymous 
>> call (where the identity has been explicitly withheld),  and a call 
>> where the identity has failed to be transferred by the  intervening 
>> signalling, are different things and the new proposed  new status-code 
>> only applies to the former.
>>
>> The need for users to be able to reject such calls, and the need to  
>> explicitly indicate the reason for rejection, are part of European  
>> regulatory requirements for voice calls.
>>
>> The alternative approach identified by TISPAN was to include the  
>> existing PSTN/ISDN cause value in a Reason header in a response,  but 
>> SIPPING people concluded that this was not a good idea.
>>
>> ETSI TISPAN has agreed to use the proposed new status-code to solve  
>> this problem. The draft looks to be uncontentious and complete. Can  I 
>> ask the WG chairs how they intend to progress the draft?
>>
>> regards
>>
>> Keith
>>
>> Keith Drage
>> Lucent Technologies
>> drage@lucent.com
>> tel: +44 1793 776249
>>
>> _______________________________________________
>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the application of SIP
>> Use sip-implementors@cs.columbia.edu for questions on current sip
>> Use sip@ietf.org for new developments of core SIP
>>
> 
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP