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

"Christer Holmberg" <christer.holmberg@ericsson.com> Thu, 06 August 2009 17:52 UTC

Return-Path: <christer.holmberg@ericsson.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 A4A673A6B16 for <dispatch@core3.amsl.com>; Thu, 6 Aug 2009 10:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.486
X-Spam-Level:
X-Spam-Status: No, score=-5.486 tagged_above=-999 required=5 tests=[AWL=0.763, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 BQmLhdpLndI2 for <dispatch@core3.amsl.com>; Thu, 6 Aug 2009 10:52:55 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 023DB3A697F for <dispatch@ietf.org>; Thu, 6 Aug 2009 10:52:54 -0700 (PDT)
X-AuditID: c1b4fb3e-b7b53ae000004f0b-f3-4a7b18788079
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 47.44.20235.8781B7A4; Thu, 6 Aug 2009 19:52:56 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Thu, 6 Aug 2009 19:52:56 +0200
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: Thu, 06 Aug 2009 19:50:08 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF083CD245@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dispatch] draft-jesske-sipping-etsi-ngn-reason-04
Thread-Index: AcoJHi+ROLPVUN7URFqcaM3kAonJJAAoLukwABqf5HAC2pAeYAAUVgtgAB0UM7AAGUCS2g==
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> <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>
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: R.Jesske@telekom.de, audet@nortel.com, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
X-OriginalArrivalTime: 06 Aug 2009 17:52:56.0426 (UTC) FILETIME=[BAA20CA0:01CA16BE]
X-Brightmail-Tracker: AAAAAA==
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: Thu, 06 Aug 2009 17:52:56 -0000

Hi,
 
>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?

I am ok with the proposed with the text. Maybe you should say "for provisional 199 responses". 

I guess it would be good to add a reference to the 199 spec also.

Regards,

Christer 


-----Ursprüngliche Nachricht-----
Von: Francois Audet [mailto:audet@nortel.com]
Gesendet: Mittwoch, 5. August 2009 17:55
An: Christer Holmberg; Jesske, Roland; Gonzalo Camarillo
Cc: dispatch@ietf.org
Betreff: RE: [dispatch] draft-jesske-sipping-etsi-ngn-reason-04

Yes, I think so.

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> Sent: Tuesday, August 04, 2009 23:16
> To: Audet, Francois (SC100:3055); R.Jesske@telekom.de;
> Gonzalo Camarillo
> Cc: dispatch@ietf.org
> Subject: RE: [dispatch] draft-jesske-sipping-etsi-ngn-reason-04
>
>
> Hi Francois,
>
> As you mentioned earlier, it could make sense to allow it in 199.
>
> Regards,
>
> Christer
>
> -----Original Message-----
> From: dispatch-bounces@ietf.org
> [mailto:dispatch-bounces@ietf.org] On Behalf Of Francois Audet
> Sent: Tuesday, July 21, 2009 8:34 PM
> To: R.Jesske@telekom.de; Gonzalo Camarillo
> Cc: dispatch@ietf.org
> Subject: Re: [dispatch] draft-jesske-sipping-etsi-ngn-reason-04
>
> and explain why 3XX, 2XX and 1XX don't make sense.
>
> > -----Original Message-----
> > From: R.Jesske@telekom.de [mailto:R.Jesske@telekom.de]
> > Sent: Monday, July 20, 2009 22:03
> > To: Gonzalo.Camarillo@ericsson.com; Audet, Francois (SC100:3055)
> > Cc: Worley, Dale (BL60:9D30); dispatch@ietf.org
> > Subject: AW: [dispatch] draft-jesske-sipping-etsi-ngn-reason-04
> >
> > Hi Gonzalo,
> > Thank you for your comments.
> > You are correct. The used cases within the document shows
> where ISUP
> > causes will be included.
> > I think in such cases we should clearly state that SIP
> Reason should
> > be excluded within SIP responses, to avoid contradictions.
> >
> > Then I will include that only within 4xx/5xx/6xx Responses
> the Reason
> > header with an Q.850 Cause makes sense.
> >
> > There are requirements and three used cases described
> within the draft
> > so I hope that fits.
> >
> > Best Regards
> >
> > Roland
> > -----Ursprüngliche Nachricht-----
> > Von: Gonzalo Camarillo [mailto:Gonzalo.Camarillo@ericsson.com]
> > Gesendet: Montag, 20. Juli 2009 11:41
> > An: Francois Audet
> > Cc: Dale Worley; dispatch@ietf.org; Jesske, Roland
> > Betreff: Re: [dispatch] draft-jesske-sipping-etsi-ngn-reason-04
> >
> > Hi,
> >
> > as Francois suggests, a document specifying the use of
> Reason header
> > fields in responses needs to specify those things (see
> Francois' list
> > below). Additionally, you should think of whether or not
> Reason header
> > fields in responses can carry SIP status codes and what happens if
> > they are different to the status code of the response.
> >
> > In short, the document cannot simply say that now it is OK to use
> > Reason in responses. It needs to address the different situations a
> > typical implementation may face.
> >
> > Cheers,
> >
> > Gonzalo
> >
> >
> > Francois Audet wrote:
> > > Again, the spec is very clear that it IS allowed.
> > >
> > > I believe the wishy-washy text about "status code
> > explicitly allowing
> > > it" was meant to exclude responses that were not appropriate, and
> > > restricing it to effectively error responses.
> > >
> > > At the time this was written, I believe we were not clear
> on which
> > > codes were supposed to be appropriate or not.
> > >
> > > Seems to me:
> > > - Any Error response code should be allowed.
> > > - I don't think 2XX makes sense.
> > > - 3XX is controversial (as per the email quoted by Roland):
> > seems to me it
> > >   would be quite useful
> > > - Provisional is interesting... Sounds like 199 error
> > response to me...
> > >
> > >> -----Original Message-----
> > >> From: Worley, Dale (BL60:9D30)
> > >> Sent: Thursday, July 16, 2009 10:09
> > >> To: Audet, Francois (SC100:3055)
> > >> Cc: R.Jesske@telekom.de; dispatch@ietf.org
> > >> Subject: RE: [dispatch] draft-jesske-sipping-etsi-ngn-reason-04
> > >>
> > >> On Thu, 2009-07-16 at 12:48 -0400, Audet, Francois
> > (SC100:3055) wrote:
> > >>> Hi Roland,
> > >>>
> > >>> You use case is very common. 
> > >>>
> > >>> I believe you are incorrect in saying that "reasons are
> > >> currently not
> > >>> allowed in responses. Neither conditionally nor allowed".
> > >>>
> > >>> RFC 3326 says in 1.0:
> > >>>   "[...] it can appear in any request
> > >>>    within a dialog, in any CANCEL request and in any
> > response whose
> > >>>    status code explicitly allows the presence of this
> > header field."
> > >>>
> > >>> To be honest, I believe Q.850 codes are much more common in
> > >> Responses
> > >>> than in requests.
> > >> Googling
> > >>
> > >>      "sip/2.0" reason "q.850"
> > >>
> > >> turns up numerous examples of SIP responses using the
> > Reason header
> > >> in the forbidden manner.
> > >>
> > >> I'd say that your draft formally allows what people are
> > already doing.
> > >>
> > >> Dale
> > >>
> > >>
> > >>
> > > _______________________________________________
> > > 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
>