IETF Logo Mail Archive

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

"Dale Worley" <dworley@nortel.com> Fri, 17 July 2009 18:50 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 AF72A3A6CCA for <dispatch@core3.amsl.com>; Fri, 17 Jul 2009 11:50:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.689
X-Spam-Level:
X-Spam-Status: No, score=-6.689 tagged_above=-999 required=5 tests=[AWL=-0.090, 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 NqtDLSYSkneb for <dispatch@core3.amsl.com>; Fri, 17 Jul 2009 11:50:58 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id ACB553A69A3 for <dispatch@ietf.org>; Fri, 17 Jul 2009 11:50:58 -0700 (PDT)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id n6HHwus06509; Fri, 17 Jul 2009 17:58:56 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 17 Jul 2009 14:00:38 -0400
From: Dale Worley <dworley@nortel.com>
To: R.Jesske@telekom.de
In-Reply-To: <9886E5FCA6D76549A3011068483A4BD404A9B6D7@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> <1247763684.4085.21.camel@victoria-pingtel-com.us.nortel.com> <9886E5FCA6D76549A3011068483A4BD404A9B6D7@S4DE8PSAAQB.mitte.t-com.de>
Content-Type: text/plain
Organization: Nortel Networks
Date: Fri, 17 Jul 2009 14:00:37 -0400
Message-Id: <1247853637.3780.25.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: 17 Jul 2009 18:00:38.0185 (UTC) FILETIME=[7D99E190:01CA0708]
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: Fri, 17 Jul 2009 18:50:59 -0000

Thinking about this discussion, I would add a sentence to the abstract
telling the reader that the Reason header in responses is widely used,
even though it is not officially specified.  Something along these
lines:

        Although the use of the Reason header field in responses is
        considered in RFC 3326, doing so is not specified for any
        existing response code.  Nonetheless, the Reason header field
        has been widely used in responses to carry Q.850 reason codes
        for failure responses to INVITEs that have been gatewayed to
        PSTN systems.  This document specifies and formally permits the
        use of the Reason header field in SIP responses to carry Q.850
        reason codes for this and other purposes.

I think that makes the current situation clear to the uninformed reader
(e.g., me), and it only requires 3 sentences.

Dale

v2.26.15 | Report a Bug | By Email | System Status