Re: [Sipping] draft-rosenberg-sipping-acr-code-00.txt
Dean Willis <dean.willis@softarmor.com> Tue, 10 January 2006 17:35 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 1EwNOj-0003Tu-ND; Tue, 10 Jan 2006 12:35:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EwNOh-0003Sr-TB for sipping@megatron.ietf.org; Tue, 10 Jan 2006 12:35:04 -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 MAA23558 for <sipping@ietf.org>; Tue, 10 Jan 2006 12:33:43 -0500 (EST)
Received: from nylon.softarmor.com ([66.135.38.164]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EwNVQ-0001lh-LM for sipping@ietf.org; Tue, 10 Jan 2006 12:42:02 -0500
Received: from [192.168.2.105] ([128.107.236.177]) (authenticated bits=0) by nylon.softarmor.com (8.13.1/8.13.1) with ESMTP id k0AHetMw007258 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Tue, 10 Jan 2006 11:40:57 -0600
In-Reply-To: <475FF955A05DD411980D00508B6D5FB00C290701@en0033exch001u.uk.lucent.com>
References: <475FF955A05DD411980D00508B6D5FB00C290701@en0033exch001u.uk.lucent.com>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <B9A01F73-5955-46CE-B8B1-81734CCD8F24@softarmor.com>
Content-Transfer-Encoding: 7bit
From: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] draft-rosenberg-sipping-acr-code-00.txt
Date: Tue, 10 Jan 2006 11:34:48 -0600
To: "Drage, Keith (Keith)" <drage@lucent.com>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit
Cc: "'rohan@ekabal.com'" <rohan@ekabal.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
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] draft-rosenberg-sipping-acr-code-00.txt Drage, Keith (Keith)
- Re: [Sipping] draft-rosenberg-sipping-acr-code-00… Dean Willis
- Re: [Sipping] draft-rosenberg-sipping-acr-code-00… Paul Kyzivat
- Re: [Sipping] draft-rosenberg-sipping-acr-code-00… Jonathan Rosenberg
- Re: [Sipping] draft-rosenberg-sipping-acr-code-00… Gonzalo Camarillo
- Re: [Sipping] draft-rosenberg-sipping-acr-code-00… Jonathan Rosenberg
- Re: [Sipping] draft-rosenberg-sipping-acr-code-00… Dean Willis
- Re: [Sipping] draft-rosenberg-sipping-acr-code-00… Dean Willis