IETF Logo Mail Archive

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

"Dale Worley" <dworley@nortel.com> Thu, 16 July 2009 17:02 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 1A76A28C134 for <dispatch@core3.amsl.com>; Thu, 16 Jul 2009 10:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.71
X-Spam-Level:
X-Spam-Status: No, score=-6.71 tagged_above=-999 required=5 tests=[AWL=-0.111, 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 1vnuNrMdPE+g for <dispatch@core3.amsl.com>; Thu, 16 Jul 2009 10:02:08 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id 1CD003A69F7 for <dispatch@ietf.org>; Thu, 16 Jul 2009 10:02:08 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (casmtp.ca.nortel.com [47.140.202.46]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id n6GGxiD16175; Thu, 16 Jul 2009 16:59:44 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:01:25 -0400
From: Dale Worley <dworley@nortel.com>
To: R.Jesske@telekom.de
In-Reply-To: <9886E5FCA6D76549A3011068483A4BD404A14E83@S4DE8PSAAQB.mitte.t-com.de>
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>
Content-Type: text/plain
Organization: Nortel Networks
Date: Thu, 16 Jul 2009 13:01:24 -0400
Message-Id: <1247763684.4085.21.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:01:25.0461 (UTC) FILETIME=[0D997850:01CA0637]
Cc: dispatch@ietf.org
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:02:09 -0000

On Mon, 2009-07-13 at 08:16 +0200, R.Jesske@telekom.de wrote:

> The main probblem is that reasons are currently not allowed in
> responses. Neither conditionally nor allowed
> 
> Please see: http://www.ietf.org/mail-archive/web/sipping/current/msg09682.html

That clarifies things.

Let me rephrase my complaint:  Although the text of the RFC states "The
Reason header field MAY appear in [...] any response whose status code
explicitly allows the presence of this header field.", that text is
stunningly unclear that the consequence is that the Reason header is not
allowed in *any* defined response, and a casual reader might not realize
that Reason is thus effectively forbidden in all responses.

Expanding the Abstract along these lines would make the significance and
importance of the draft much clearer:

        Although the use of the Reason header in responses is considered
        in RFC 3326, doing so is not specified for any existing response
        code.  This document specifies the use of the Reason header
        field in SIP responses to carry Q.850 reason codes for the
        failure of an INVITE.
        
Dale

v2.23.0 | Report a Bug | By Email