Re: [Sipping] New draft: Extending the SIP Reason Header with Warning Codes

Jonathan Rosenberg <jdrosen@cisco.com> Sun, 06 November 2005 23:40 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 1EYu88-0007MA-MB; Sun, 06 Nov 2005 18:40:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EYu87-0007M5-Jd for sipping@megatron.ietf.org; Sun, 06 Nov 2005 18:40:55 -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 SAA27274 for <sipping@ietf.org>; Sun, 6 Nov 2005 18:40:30 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EYuNb-0008QB-Hu for sipping@ietf.org; Sun, 06 Nov 2005 18:56:56 -0500
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 06 Nov 2005 15:40:44 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.97,298,1125903600"; d="scan'208"; a="14642391:sNHT21824488"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id jA6Neeci007795; Sun, 6 Nov 2005 18:40:41 -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); Sun, 6 Nov 2005 18:40:30 -0500
Received: from [209.52.109.209] ([10.86.242.55]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Sun, 6 Nov 2005 18:40:29 -0500
Message-ID: <436E946C.8010700@cisco.com>
Date: Sun, 06 Nov 2005 18:40:28 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Jani Hautakorpi (JO/LMF)" <jani.hautakorpi@ericsson.com>
Subject: Re: [Sipping] New draft: Extending the SIP Reason Header with Warning Codes
References: <4354CAA2.1080605@ericsson.com>
In-Reply-To: <4354CAA2.1080605@ericsson.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Nov 2005 23:40:29.0822 (UTC) FILETIME=[78B601E0:01C5E32B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Cc: sipping@ietf.org
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

A comment on the warning extension for anonymous call rejection.

I don't understand why we need a warning value for this. I think we are 
better off just defining a new response code for it (see separate 
discussion on extending reasons for rejection).

-Jonathan R.

Jani Hautakorpi (JO/LMF) wrote:

> Hi all,
> 
> We submitted the following draft couple of days ago:
> http://www.ietf.org/internet-drafts/draft-hautakorpi-reason-header-for-warnings-00.txt
> 
> We would like to welcome all kinds of feedback to our draft, and
> especially comments related to 'open issue' stated in Section 5.
> 
> 

-- 
Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
Director, Service Provider VoIP Architecture   Parsippany, NJ 07054-2711
Cisco Systems
jdrosen@cisco.com                              FAX:   (973) 952-5050
http://www.jdrosen.net                         PHONE: (973) 952-5000
http://www.cisco.com

_______________________________________________
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