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

Paul Kyzivat <pkyzivat@cisco.com> Tue, 10 November 2009 00:05 UTC

Return-Path: <pkyzivat@cisco.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 CDDDB3A6945 for <dispatch@core3.amsl.com>; Mon, 9 Nov 2009 16:05:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.595
X-Spam-Level:
X-Spam-Status: No, score=-6.595 tagged_above=-999 required=5 tests=[AWL=0.004, 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 iy7Mn7d45NQQ for <dispatch@core3.amsl.com>; Mon, 9 Nov 2009 16:05:59 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id BC2C63A691A for <dispatch@ietf.org>; Mon, 9 Nov 2009 16:05:58 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEALQ9+EqtJV2d/2dsb2JhbADGMZdFhD4E
X-IronPort-AV: E=Sophos;i="4.44,711,1249257600"; d="scan'208";a="67135877"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rtp-iport-1.cisco.com with ESMTP; 10 Nov 2009 00:06:12 +0000
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id nAA06C62014581; Tue, 10 Nov 2009 00:06:12 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Nov 2009 19:06:12 -0500
Received: from [161.44.174.156] ([161.44.174.156]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 9 Nov 2009 19:06:11 -0500
Message-ID: <4AF8AE73.4050405@cisco.com>
Date: Mon, 09 Nov 2009 19:06:11 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: R.Jesske@telekom.de
References: <9886E5FCA6D76549A3011068483A4BD40498CFB8@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> <9886E5FCA6D76549A3011068483A4BD40537238D@S4DE8PSAAQB.mitte.t-com.de>
In-Reply-To: <9886E5FCA6D76549A3011068483A4BD40537238D@S4DE8PSAAQB.mitte.t-com.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 10 Nov 2009 00:06:11.0728 (UTC) FILETIME=[9C843100:01CA6199]
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: Tue, 10 Nov 2009 00:05:59 -0000

Roland,

Thanks! That addresses my concern.

	Thanks,
	Paul

R.Jesske@telekom.de wrote:
> 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
>>
>