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

"Dale Worley" <dworley@nortel.com> Mon, 06 July 2009 15:37 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 E794A3A6D0F for <dispatch@core3.amsl.com>; Mon, 6 Jul 2009 08:37:38 -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 UrhCScSWhvfz for <dispatch@core3.amsl.com>; Mon, 6 Jul 2009 08:37:37 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 2FC293A6A15 for <dispatch@ietf.org>; Mon, 6 Jul 2009 08:37:37 -0700 (PDT)
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 n66Fare08385; Mon, 6 Jul 2009 15:36:53 GMT
Received: from [47.16.90.165] ([47.16.90.165]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 6 Jul 2009 11:36:52 -0400
From: Dale Worley <dworley@nortel.com>
To: R.Jesske@telekom.de
In-Reply-To: <9886E5FCA6D76549A3011068483A4BD40498CFB8@S4DE8PSAAQB.mitte.t-com.de>
References: <9886E5FCA6D76549A3011068483A4BD40498CFB8@S4DE8PSAAQB.mitte.t-com.de>
Content-Type: text/plain
Organization: Nortel Networks
Date: Mon, 06 Jul 2009 11:36:52 -0400
Message-Id: <1246894612.3747.17.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: 06 Jul 2009 15:36:52.0995 (UTC) FILETIME=[960B1530:01C9FE4F]
Cc: DISPATCH <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: Mon, 06 Jul 2009 15:37:39 -0000

On Mon, 2009-07-06 at 13:50 +0200, R.Jesske@telekom.de wrote:
> Dear all, 
> After getting no response to my question from the dispatch. I assume
> that there is no interest on this draft within dispatch.
> 
> So now I would like to ask the people from SIPCORE and BILSS where do
> they see the work.
> 
> The below mentioned draft describes the use of the Reason Header
> within Resoponses for interoperability with the existing PSTN/ISDN
> networks.

Is the Abstract right?  As far as I can tell (by reading section 2), the
Abstract doesn't describe the draft at all.  That might be a reason that
you haven't gotten any response -- the Abstract "proposes the use of the
Reason header field in SIP responses", but that is something that is
already defined and allowed.

Dale