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

"Dale Worley" <dworley@nortel.com> Wed, 09 December 2009 21:40 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 54CBC3A690C for <dispatch@core3.amsl.com>; Wed, 9 Dec 2009 13:40:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level:
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050, 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 X0PK2SnkaoXi for <dispatch@core3.amsl.com>; Wed, 9 Dec 2009 13:40:32 -0800 (PST)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 595B63A680F for <dispatch@ietf.org>; Wed, 9 Dec 2009 13:40:32 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id nB9LeC429643; Wed, 9 Dec 2009 21:40:12 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 9 Dec 2009 16:39:57 -0500
From: Dale Worley <dworley@nortel.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <4AFADAD9.7040402@cisco.com>
References: <9886E5FCA6D76549A3011068483A4BD40498CFB8@S4DE8PSAAQB.mitte.t-com.de> <9886E5FCA6D76549A3011068483A4BD404A9C2B7@S4DE8PSAAQB.mitte.t-com.de> <1ECE0EB50388174790F9694F77522CCF1F155AC5@zrc2hxm0.corp.nortel.com> <CA9998CD4A020D418654FCDEF4E707DF0B1683CC@esealmw113.eemea.ericsson.se> <1ECE0EB50388174790F9694F77522CCF1F556A65@zrc2hxm0.corp.nortel.com> <9886E5FCA6D76549A3011068483A4BD404BFFC37@S4DE8PSAAQB.mitte.t-com.de> <4AF37113.8030908@nostrum.com> <9886E5FCA6D76549A3011068483A4BD405319E68@S4DE8PSAAQB.mitte.t-com.de> <4AF7934B.7080902@cisco.com> <9886E5FCA6D76549A3011068483A4BD40537238D@S4DE8PSAAQB.mitte.t-com.de> <4AF! 8AE73.4050405@cisco.com> <CA9998CD4A020D418654FCDEF4E707DF0B16864C@esealmw113.eemea.ericsson.se> <744A66DF31B5B34EA8B08BBD8187A722C6423E@DEMUEXC014.nsn-intra.net> <4AFAC2DF.3090001@cisco.com> <9886E5FCA6D76549A3011068483A4BD405372C90@S4DE8PSAAQB.mitte.t-com.de> <4AFAD1 50.9070900@cisco.com> <9886E5FCA6D76549A3011068483A4BD405372CDE@S4DE8PSAAQB.mitte.t-com.d e> <4AFADAD9.7040402@cisco.com>
Content-Type: text/plain
Organization: Nortel Networks
Date: Wed, 09 Dec 2009 16:39:57 -0500
Message-Id: <1260394797.4277.39.camel@khone.us.nortel.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-5.fc8)
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Dec 2009 21:39:57.0442 (UTC) FILETIME=[2706E620:01CA7918]
Cc: paul.while@ericsson.com, dispatch@ietf.org, R.Jesske@telekom.de, calme@alcatel-lucent.com
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: Wed, 09 Dec 2009 21:40:33 -0000

On Wed, 2009-11-11 at 10:40 -0500, Paul Kyzivat wrote:
> 
> R.Jesske@telekom.de wrote:
> > Hi Paul,
> > Sorry. I was to fast with my writing an sending. 
> > What I meant to write was the 100. But I dont know any other 1xx beyond 18x and 199 that would fit. Or did I forgot one.
> > 
> > Or is it more the general avalibility for 1xx for future.
> 
> Enumerating which ones are meaningful isn't future proof.
> Maybe this is a special case since there is a requirement to explicitly 
> document which responses this header may appear in (why?),
> but IMO it would be better not to second guess, and just allow them all.

Yes, we should generically allow Reason in any 101-199 or final
response.  The proper use of "Reason: Q.850;cause=..." is "to describe
the cause for the generation of the response by a datum that is to be
interpreted based on the Q.850 standard".  The usual reason for this is
that the ultimate cause of the generation of the response was an SS7
protocol operation that contained the specified cause code, but even
that need not be true.  The goal is to specify how the receiver should
interpret the header; based on that, the restrictions on the sender are
implied.

Dale