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

Hi,

A small editorial change proposal:

"The appearance of the Reason header is applicable to 3xx, 4xx, 5xx and 6xx final responses
and 18x and 199 <reference> provisional responsess."

Regards,

Christer

-----Original Message-----
From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On Behalf Of Paul Kyzivat
Sent: 10. marraskuuta 2009 3:06
To: R.Jesske@telekom.de
Cc: audet@nortel.com; dispatch@ietf.org; Gonzalo Camarillo
Subject: Re: [dispatch] draft-jesske-sipping-etsi-ngn-reason-04

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
>>
> 
_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch