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

<R.Jesske@telekom.de> Mon, 09 November 2009 23:57 UTC

Return-Path: <R.Jesske@telekom.de>
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 6034A3A67AD for <dispatch@core3.amsl.com>; Mon, 9 Nov 2009 15:57:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.816
X-Spam-Level:
X-Spam-Status: No, score=-2.816 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
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 hVjE-u0BAPPU for <dispatch@core3.amsl.com>; Mon, 9 Nov 2009 15:57:23 -0800 (PST)
Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by core3.amsl.com (Postfix) with ESMTP id 100B53A677E for <dispatch@ietf.org>; Mon, 9 Nov 2009 15:57:22 -0800 (PST)
Received: from s4de8psaans.blf.telekom.de (HELO s4de8psaans.mitte.t-com.de) ([10.151.180.168]) by tcmail71.telekom.de with ESMTP; 10 Nov 2009 00:57:45 +0100
Received: from S4DE8PSAAQB.mitte.t-com.de ([10.151.229.13]) by s4de8psaans.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Tue, 10 Nov 2009 00:57:45 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 Nov 2009 00:57:43 +0100
Message-ID: <9886E5FCA6D76549A3011068483A4BD40537238D@S4DE8PSAAQB.mitte.t-com.de>
In-Reply-To: <4AF7934B.7080902@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dispatch] draft-jesske-sipping-etsi-ngn-reason-04
Thread-Index: Acpg8Nmq5+afqaFTQH+9ByJdXB1RdQAp17eg
References: <9886E5FCA6D76549A3011068483A4BD40498CFB8@S4DE8PSAAQB.mitte.t-com.de> <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> <1247764118.4085.24.camel@victoria-pingtel-com.us.nortel.com><1ECE0EB50388174790F9694F77522CCF1F05050C@zrc2hxm0.corp.nortel.com><4A643B95.3060800@ericsson.com><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>
From: R.Jesske@telekom.de
To: pkyzivat@cisco.com
X-OriginalArrivalTime: 09 Nov 2009 23:57:45.0363 (UTC) FILETIME=[6EB30630:01CA6198]
Cc: audet@nortel.com, dispatch@ietf.org, gonzalo.camarillo@ericsson.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: Mon, 09 Nov 2009 23:57:24 -0000

Hello Paul,
Thanks for that hint. I will change this too. 
Like:

 The appearance of the Reason header is applicable to final responses
       3xx, 4xx, 5xx and 6xx and in addition for 199 Responses as defined within
       ietf-sipcore-199.txt. Also the Reason header is
       applicable to provisional responses18x.

Best Regards

Roland

-----Ursprüngliche Nachricht-----
Von: Paul Kyzivat [mailto:pkyzivat@cisco.com] 
Gesendet: Montag, 9. November 2009 12:58
An: Jesske, Roland
Cc: adam@nostrum.com; audet@nortel.com; dispatch@ietf.org; gonzalo.camarillo@ericsson.com
Betreff: Re: [dispatch] draft-jesske-sipping-etsi-ngn-reason-04



R.Jesske@telekom.de wrote:
> Hi Adam,
> Thank you for your mail. So I propose the following text then:
> 
> The appearance of the Reason header is applicable to final responses
>       3xx, 4xx, 5xx and 6xx and in addition for 199 Responses as defined within
>       ietf-sipcore-199.txt. Also the Reason header is
>       applicable to provisional responses18x which are generated by an
>       interworking gateway from ISUP to SIP.</t>

I think this is ok *except* if you are going to allow one kind of UAS to 
use Reason in a 18x response, then it should be allowed for *any* UAS to 
do so.

For instance, suppose the gateway is replaced by a B2BUA to another sip 
environment, and the request eventually arrives as a gateway. Then a 18x 
response with a Reason header may arrive at the B2BUA and need to be 
replicated on the other side.

	Thanks,
	Paul

> Best Beagards
> 
> Roland 
> 
> -----Ursprüngliche Nachricht-----
> Von: Adam Roach [mailto:adam@nostrum.com] 
> Gesendet: Freitag, 6. November 2009 01:43
> An: Jesske, Roland
> Cc: audet@nortel.com; christer.holmberg@ericsson.com; gonzalo.camarillo@ericsson.com; dispatch@ietf.org
> Betreff: Re: [dispatch] draft-jesske-sipping-etsi-ngn-reason-04
> 
> On 8/6/09 7:28 PM, R.Jesske@telekom.de wrote:
>> Hi Christer and Francois,
>> I have added a sentence under section Overall Applicability:
>>
>>
>> The appearance of the Reason header is applicable to final responses 4xx, 5xx and 6xx and in addition for 199 Responses.
>>
>> Is this proper enough? Or do you have more in mind?
>>    
> 
> Given that RFC 3398 specifies the generation of a 301 in response to a 
> cause code of 22 under certain circumstances, it seems pretty 
> appropriate to allow the inclusion of a Q.850 cause code in 300-class 
> responses also. Or, at least, as appropriate as it would be to include 
> them in 4xx, 5xx, and 6xx responses.
> 
> /a
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>