IETF Logo Mail Archive

Re: [dispatch] draft-jesske-sipping-etsi-ngn-reason-04

"Dale Worley" <dworley@nortel.com> Thu, 16 July 2009 17:08 UTC

Return-Path: <dworley@nortel.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2D6463A6938 for <dispatch@core3.amsl.com>; Thu, 16 Jul 2009 10:08:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.706
X-Spam-Level:
X-Spam-Status: No, score=-6.706 tagged_above=-999 required=5 tests=[AWL=-0.107, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 KiWc4MWBdnjC for <dispatch@core3.amsl.com>; Thu, 16 Jul 2009 10:08:13 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 39EC53A68CC for <dispatch@ietf.org>; Thu, 16 Jul 2009 10:08:13 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n6GH8cw19936; Thu, 16 Jul 2009 17:08:39 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 16 Jul 2009 13:08:38 -0400
From: Dale Worley <dworley@nortel.com>
To: Francois Audet <audet@nortel.com>
In-Reply-To: <1ECE0EB50388174790F9694F77522CCF1F050471@zrc2hxm0.corp.nortel.com>
References: <9886E5FCA6D76549A3011068483A4BD40498CFB8@S4DE8PSAAQB.mitte.t-com.de> <1246894612.3747.17.camel@victoria-pingtel-com.us.nortel.com> <9886E5FCA6D76549A3011068483A4BD40498D2CA@S4DE8PSAAQB.mitte.t-com.de> <1247255492.3757.40.camel@victoria-pingtel-com.us.nortel.com> <9886E5FCA6D76549A3011068483A4BD404A14E83@S4DE8PSAAQB.mitte.t-com.de> <1ECE0EB50388174790F9694F77522CCF1F050471@zrc2hxm0.corp.nortel.com>
Content-Type: text/plain
Organization: Nortel Networks
Date: Thu, 16 Jul 2009 13:08:38 -0400
Message-Id: <1247764118.4085.24.camel@victoria-pingtel-com.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8)
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Jul 2009 17:08:38.0894 (UTC) FILETIME=[0FF218E0:01CA0638]
Cc: dispatch@ietf.org, R.Jesske@telekom.de
Subject: Re: [dispatch] draft-jesske-sipping-etsi-ngn-reason-04
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2009 17:08:14 -0000

On Thu, 2009-07-16 at 12:48 -0400, Audet, Francois (SC100:3055) wrote:
> Hi Roland,
> 
> You use case is very common.  
> 
> I believe you are incorrect in saying that "reasons are currently 
> not allowed in responses. Neither conditionally nor allowed".
> 
> RFC 3326 says in 1.0:
>   "[...] it can appear in any request
>    within a dialog, in any CANCEL request and in any response whose
>    status code explicitly allows the presence of this header field."
> 
> To be honest, I believe Q.850 codes are much more common in 
> Responses than in requests.

Googling

     "sip/2.0" reason "q.850"

turns up numerous examples of SIP responses using the Reason header in
the forbidden manner.

I'd say that your draft formally allows what people are already doing.

Dale

v2.23.0 | Report a Bug | By Email