From mary.ietf.barnes@gmail.com Fri Apr 1 06:17:49 2011 Return-Path: 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 13F123A684A for ; Fri, 1 Apr 2011 06:17:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.866 X-Spam-Level: X-Spam-Status: No, score=-102.866 tagged_above=-999 required=5 tests=[AWL=-0.268, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] 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 Aq4SsK1cP2iB for ; Fri, 1 Apr 2011 06:17:47 -0700 (PDT) Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 889733A6767 for ; Fri, 1 Apr 2011 06:17:47 -0700 (PDT) Received: by vxg33 with SMTP id 33so3158598vxg.31 for ; Fri, 01 Apr 2011 06:19:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=DaFFzLvHx/y+kbmx4LJ1FpxvaZqptnyNr60vvBL0aaY=; b=UzGVDoLSR+soyaJg92YD0fOKwkGrs30+ZS00ubzEEFBNaSNvjFtCWsdAHnuow/aXWO s196jbnSgiLs+m2Uqno4XCKT59I3pBKXdDt5LmwJ6WqKgl4CN/Ho22ZV4afMS4rOWKW9 WzZpyT2UYw19BFfJCnnUa36mD0MRDGFFjgSIk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=As/SgsGIFW+qK0wbOe9xjFe543EYomvhhv4huvZaIIqjhT1UVH9XB1MWe/mR2p5Xqa 4AT1uHVz1fb5O/ZJk46PnApWQXvaRCplDVpm+ZLlpR4vCNwA68NUAIEzaC9Wcz+PkfK1 TucsGLXTpLd0fcF0xIwBq8EI3d40H8ZhmHSKc= MIME-Version: 1.0 Received: by 10.52.65.225 with SMTP id a1mr5352227vdt.183.1301663967514; Fri, 01 Apr 2011 06:19:27 -0700 (PDT) Received: by 10.52.167.137 with HTTP; Fri, 1 Apr 2011 06:19:27 -0700 (PDT) Date: Fri, 1 Apr 2011 08:19:27 -0500 Message-ID: From: Mary Barnes To: DISPATCH Content-Type: multipart/alternative; boundary=20cf307f38ea669192049fdb4255 Subject: [dispatch] Ad-hoc RTCWEB meeting at IETF-80 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2011 13:17:49 -0000 --20cf307f38ea669192049fdb4255 Content-Type: text/plain; charset=ISO-8859-1 FYI... ---------- Forwarded message ---------- From: Mary Barnes Date: Fri, Apr 1, 2011 at 8:18 AM Subject: Re: [RTW] Ad-hoc RTCWEB meeting (Fwd: [dispatch] DISPATCH Ad-HOC meetings about VIPR and RTCWeb at IETF 80) To: "rtc-web@alvestrand.no" The charts from today's meeting are on the meeting materials page under the DISPATCH WG. Regards, Mary. On Wed, Mar 30, 2011 at 2:51 AM, Harald Alvestrand wrote: > Friday 1415-1515 in the Grand Ballroom. > > -------- Original Message -------- Subject: [dispatch] DISPATCH Ad-HOC > meetings about VIPR and RTCWeb at IETF 80 Date: Tue, 15 Mar 2011 11:45:13 > -0600 From: Cullen Jennings To: DISPATCH > list > > The dispatch WG will have two ad-hoc meeting. > > The first is discuss the technical content of the drafts related to the proposed VIPR WG. > > Tentative time: VIPR's is in Tyrolka on Thursday 1300-1400 > > The second is to discuss the technical contents of drafts related to the proposed RTCWeb WG. > > Tentative time: RTCWeb's is Friday 1415-1515 in the Grand Ballroom > > Send Agenda requests for time in either of these to Mary and I. > > Thanks, > Mary & Cullen > > > _______________________________________________ > dispatch mailing listdispatch@ietf.orghttps://www.ietf.org/mailman/listinfo/dispatch > > > _______________________________________________ > RTC-Web mailing list > RTC-Web@alvestrand.no > http://www.alvestrand.no/mailman/listinfo/rtc-web > > --20cf307f38ea669192049fdb4255 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable FYI...

---------- Forwarded message ----= ------
From: Mary Barnes <mary.ietf.barnes@gma= il.com>
Date: Fri, Apr 1, 2011 at 8:18 AM
Subject: Re: [RTW] Ad-hoc RTCWEB meeti= ng (Fwd: [dispatch] DISPATCH Ad-HOC meetings about VIPR and RTCWeb at IETF = 80)
To: "rtc-web@alvestran= d.no" <rtc-web@alvestr= and.no>



The charts from today's meeting are on the meeting material= s page under the DISPATCH WG.

Regards,
Mary.= =A0

On Wed, Mar 30, 2011 at 2:51 AM, Harald Alvestrand <harald@alvestrand.n= o> wrote:
=20 =20 =20
Friday 1415-1515 in the Grand Ballroom.

-------- Original Message --------
Subject: [dispatch] DISPATCH Ad-HOC meetings about VIPR and RTCWeb at IETF 80
Date: Tue, 15 Mar 2011 11:45:13 -0600
From: Cullen Jennings <fluffy@cisco.com>
To: DISPATCH list <dispatch@ietf.org> 


The dispatch WG will have two ad-hoc meeting.=20

The first is discuss the technical content of the drafts related to the pro=
posed VIPR WG.=20

Tentative time: VIPR's is in Tyrolka on Thursday 1300-1400

The second is to discuss the technical contents of drafts related to the pr=
oposed RTCWeb WG.=20

Tentative time:  RTCWeb's is  Friday 1415-1515 in the Grand Ballroom

Send Agenda requests for time in either of these to Mary and I.=20

Thanks,
Mary & Cullen


_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch

_______________________________________________
RTC-Web mailing list
RTC-Web@alvestra= nd.no
http://www.alvestrand.no/mailman/listinfo/rtc-web



--20cf307f38ea669192049fdb4255-- From gonzalo.camarillo@ericsson.com Tue Apr 5 00:55:48 2011 Return-Path: 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 E1C803A68EA for ; Tue, 5 Apr 2011 00:55:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.668 X-Spam-Level: X-Spam-Status: No, score=-106.668 tagged_above=-999 required=5 tests=[AWL=-0.069, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] 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 tUVrFtVNPHKj for ; Tue, 5 Apr 2011 00:55:27 -0700 (PDT) Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 172F63A67EF for ; Tue, 5 Apr 2011 00:55:25 -0700 (PDT) X-AuditID: c1b4fb39-b7c6dae0000023f2-67-4d9acb534f2b Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 3D.B8.09202.35BCA9D4; Tue, 5 Apr 2011 09:57:08 +0200 (CEST) Received: from [131.160.37.44] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.137.0; Tue, 5 Apr 2011 09:57:07 +0200 Message-ID: <4D9ACB53.40004@ericsson.com> Date: Tue, 5 Apr 2011 10:57:07 +0300 From: Gonzalo Camarillo User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: DISPATCH X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: AAAAAA== Subject: [dispatch] RTCWeb mailing list X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2011 07:55:48 -0000 Hi, FYI: as part of the chartering process, we have created the following mailing list: http://www.ietf.org/mail-archive/web/rtcweb/current/msg00001.html This mailing list is intended to be the mailing list of the RTCWeb WG-to-be. From now on, RTCWeb-related discussions should happen on the newly-created list. Note that the RTCWeb charter is still under IESG/IAB review. Cheers, Gonzalo From gonzalo.camarillo@ericsson.com Tue Apr 5 05:01:09 2011 Return-Path: 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 624AB3A693E for ; Tue, 5 Apr 2011 05:01:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.665 X-Spam-Level: X-Spam-Status: No, score=-106.665 tagged_above=-999 required=5 tests=[AWL=-0.066, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] 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 mvHgTZSTzj8g for ; Tue, 5 Apr 2011 05:01:02 -0700 (PDT) Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 2EC0E3A6937 for ; Tue, 5 Apr 2011 05:01:01 -0700 (PDT) X-AuditID: c1b4fb3d-b7bd5ae000002ba3-96-4d9b04e47a3e Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id B0.2F.11171.4E40B9D4; Tue, 5 Apr 2011 14:02:44 +0200 (CEST) Received: from [131.160.37.44] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.137.0; Tue, 5 Apr 2011 14:02:44 +0200 Message-ID: <4D9B04E3.2090301@ericsson.com> Date: Tue, 5 Apr 2011 15:02:43 +0300 From: Gonzalo Camarillo User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: DISPATCH X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: AAAAAA== Subject: [dispatch] SIP responses carrying Q.850 cause values in Reason header fields X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2011 12:01:09 -0000 Hi, last week in the DISPATCH session, there was consensus to allow SIP responses to carry Reason header fields with Q.850 cause values. As I said some time ago, I am willing to AD sponsor this draft if/when the DISPATCH chairs confirm such consensus on the list. In the mean time, I have some comments on how to document this decision. The following (fairly short) draft updates a couple of paragraphs in RFC 3326 in order to achieve the desired outcome: http://www.ietf.org/id/draft-jesske-dispatch-update3326-reason-responses-02.txt I think this is not a particularly elegant way to define what we want. For example, if we wanted to define a solution to HERFP in the future based on the Reason header, we would need to update those paragraphs again, making them longer every time we added a new use case. Instead, I would prefer to explicitly define what we want to do and be done with it. Such a (also fairly short) draft would say something along the following lines: "RFC 3326 allows the presence of the Reason header field in any response whose status code explicitly allows its presence. This document explicitly allows any SIP response to carry a Reason header field with a Q.850 cause value. SIP responses with Reason header fields carrying values other than Q.850 cause values are outside of the scope of this document." I would like to know the opinion of the WG on this matter (i.e., how to document the WG's consensus). Note that reaching consensus was the difficult part. Agreeing on how to document it should be easy. Thanks, Gonzalo From R.Jesske@telekom.de Wed Apr 6 02:22:35 2011 Return-Path: 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 1D5C23A68EE for ; Wed, 6 Apr 2011 02:22:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[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 2GyvfJ3NFG9p for ; Wed, 6 Apr 2011 02:22:34 -0700 (PDT) Received: from tcmail53.telekom.de (tcmail53.telekom.de [217.5.214.110]) by core3.amsl.com (Postfix) with ESMTP id 621DC3A68E6 for ; Wed, 6 Apr 2011 02:22:32 -0700 (PDT) Received: from he111630.emea1.cds.t-internal.com ([10.134.93.22]) by tcmail51.telekom.de with ESMTP/TLS/AES128-SHA; 06 Apr 2011 11:24:12 +0200 Received: from HE111648.emea1.cds.t-internal.com ([169.254.5.34]) by HE111630.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 6 Apr 2011 11:24:12 +0200 From: To: , Date: Wed, 6 Apr 2011 11:24:10 +0200 Thread-Topic: [dispatch] SIP responses carrying Q.850 cause values in Reason header fields Thread-Index: AcvziW99TxTdvSF2RWSq4ugDLe6iZgAsg++A Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D01859CA8D4@HE111648.emea1.cds.t-internal.com> References: <4D9B04E3.2090301@ericsson.com> In-Reply-To: <4D9B04E3.2090301@ericsson.com> Accept-Language: en-US, de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dispatch] SIP responses carrying Q.850 cause values in Reason header fields X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2011 09:22:35 -0000 Hi Gonzalo, I'm OK with your proposal so I could change it if people would like it. It makes it shorter. The only I would propose to have in is the explicit mentioning of the Respo= nse values due to the fact that a 100OK or 200OK should not include a Reaso= n header with a Q.850 Cause Value. Best Regards Roland Jesske > -----Urspr=FCngliche Nachricht----- > Von: dispatch-bounces@ietf.org > [mailto:dispatch-bounces@ietf.org] Im Auftrag von Gonzalo Camarillo > Gesendet: Dienstag, 5. April 2011 14:03 > An: DISPATCH > Betreff: [dispatch] SIP responses carrying Q.850 cause values > in Reason header fields > > Hi, > > last week in the DISPATCH session, there was consensus to allow SIP > responses to carry Reason header fields with Q.850 cause values. As I > said some time ago, I am willing to AD sponsor this draft if/when the > DISPATCH chairs confirm such consensus on the list. > > In the mean time, I have some comments on how to document > this decision. > The following (fairly short) draft updates a couple of > paragraphs in RFC > 3326 in order to achieve the desired outcome: > > http://www.ietf.org/id/draft-jesske-dispatch-update3326-reason > -responses-02.txt > > I think this is not a particularly elegant way to define what we want. > For example, if we wanted to define a solution to HERFP in the future > based on the Reason header, we would need to update those paragraphs > again, making them longer every time we added a new use case. > > Instead, I would prefer to explicitly define what we want to do and be > done with it. Such a (also fairly short) draft would say > something along > the following lines: > > "RFC 3326 allows the presence of the Reason header field in > any response > whose status code explicitly allows its presence. This document > explicitly allows any SIP response to carry a Reason header > field with a > Q.850 cause value. SIP responses with Reason header fields carrying > values other than Q.850 cause values are outside of the scope of this > document." > > I would like to know the opinion of the WG on this matter > (i.e., how to > document the WG's consensus). Note that reaching consensus was the > difficult part. Agreeing on how to document it should be easy. > > Thanks, > > Gonzalo > > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch > From James.Rafferty@dialogic.com Wed Apr 6 11:04:09 2011 Return-Path: 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 653CE28C106 for ; Wed, 6 Apr 2011 11:04:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.402 X-Spam-Level: X-Spam-Status: No, score=0.402 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, HOST_MISMATCH_NET=0.311] 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 XfanxRipxIkV for ; Wed, 6 Apr 2011 11:04:08 -0700 (PDT) Received: from outbound.dialogic.com (static-173-210-122-27.ngn.onecommunications.net [173.210.122.27]) by core3.amsl.com (Postfix) with ESMTP id 5DF4E28C0D6 for ; Wed, 6 Apr 2011 11:04:08 -0700 (PDT) Received: from MBX.dialogic.com ([fe80::bd56:b76c:8d2c:437b]) by pysxht01.dialogic.com ([::1]) with mapi; Wed, 6 Apr 2011 14:05:52 -0400 From: James Rafferty To: "R.Jesske@telekom.de" , "Gonzalo.Camarillo@ericsson.com" , "dispatch@ietf.org" Date: Wed, 6 Apr 2011 14:05:49 -0400 Thread-Topic: [dispatch] SIP responses carrying Q.850 cause values in Reason header fields Thread-Index: AcvziW99TxTdvSF2RWSq4ugDLe6iZgAsg++AABJM9IA= Message-ID: <54633A5E61DC84429CB9FE3D9143C72103D739BF@MBX.dialogic.com> References: <4D9B04E3.2090301@ericsson.com> <580BEA5E3B99744AB1F5BFF5E9A3C67D01859CA8D4@HE111648.emea1.cds.t-internal.com> In-Reply-To: <580BEA5E3B99744AB1F5BFF5E9A3C67D01859CA8D4@HE111648.emea1.cds.t-internal.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dispatch] SIP responses carrying Q.850 cause values in Reason header fields X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2011 18:04:09 -0000 Hi, =20 I ran this proposal by one of our architects and got the following feedback= and questions for clarification:=20 The change actually makes sense and we do support the majority of the chan= ge already. The main part that we do not support is the use of the Reason = header in 18x or 199 provisional responses as it is not defined how you wan= t to interwork that overall message.=20 =09 For example, if you get IAM send Invite, then 100 Trying, then you get 180= Ringing that has a Reason header with Q.850 of cause code 31, do you rele= ase the call after that and send REL with cause code 31 to the PSTN or do y= ou send ACM back to the PSTN? James -----Original Message----- From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On Behal= f Of R.Jesske@telekom.de Sent: Wednesday, April 06, 2011 5:24 AM To: Gonzalo.Camarillo@ericsson.com; dispatch@ietf.org Subject: Re: [dispatch] SIP responses carrying Q.850 cause values in Reason= header fields Hi Gonzalo, I'm OK with your proposal so I could change it if people would like it. It makes it shorter. The only I would propose to have in is the explicit mentioning of the Respo= nse values due to the fact that a 100OK or 200OK should not include a Reaso= n header with a Q.850 Cause Value. Best Regards Roland Jesske > -----Urspr=FCngliche Nachricht----- > Von: dispatch-bounces@ietf.org > [mailto:dispatch-bounces@ietf.org] Im Auftrag von Gonzalo Camarillo > Gesendet: Dienstag, 5. April 2011 14:03 > An: DISPATCH > Betreff: [dispatch] SIP responses carrying Q.850 cause values > in Reason header fields > > Hi, > > last week in the DISPATCH session, there was consensus to allow SIP > responses to carry Reason header fields with Q.850 cause values. As I > said some time ago, I am willing to AD sponsor this draft if/when the > DISPATCH chairs confirm such consensus on the list. > > In the mean time, I have some comments on how to document > this decision. > The following (fairly short) draft updates a couple of > paragraphs in RFC > 3326 in order to achieve the desired outcome: > > http://www.ietf.org/id/draft-jesske-dispatch-update3326-reason > -responses-02.txt > > I think this is not a particularly elegant way to define what we want. > For example, if we wanted to define a solution to HERFP in the future > based on the Reason header, we would need to update those paragraphs > again, making them longer every time we added a new use case. > > Instead, I would prefer to explicitly define what we want to do and be > done with it. Such a (also fairly short) draft would say > something along > the following lines: > > "RFC 3326 allows the presence of the Reason header field in > any response > whose status code explicitly allows its presence. This document > explicitly allows any SIP response to carry a Reason header > field with a > Q.850 cause value. SIP responses with Reason header fields carrying > values other than Q.850 cause values are outside of the scope of this > document." > > I would like to know the opinion of the WG on this matter > (i.e., how to > document the WG's consensus). Note that reaching consensus was the > difficult part. Agreeing on how to document it should be easy. > > Thanks, > > Gonzalo > > _______________________________________________ > 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 From R.Jesske@telekom.de Fri Apr 8 04:15:32 2011 Return-Path: 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 331473A68EF for ; Fri, 8 Apr 2011 04:15:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[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 fCghMg9wSzKR for ; Fri, 8 Apr 2011 04:15:31 -0700 (PDT) Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by core3.amsl.com (Postfix) with ESMTP id A7BC33A6A49 for ; Fri, 8 Apr 2011 04:15:29 -0700 (PDT) Received: from he111630.emea1.cds.t-internal.com ([10.134.93.22]) by tcmail71.telekom.de with ESMTP/TLS/AES128-SHA; 08 Apr 2011 13:17:12 +0200 Received: from HE111648.emea1.cds.t-internal.com ([169.254.5.34]) by HE111630.emea1.cds.t-internal.com ([::1]) with mapi; Fri, 8 Apr 2011 13:17:12 +0200 From: To: , , Date: Fri, 8 Apr 2011 13:17:11 +0200 Thread-Topic: [dispatch] SIP responses carrying Q.850 cause values in Reason header fields Thread-Index: AcvziW99TxTdvSF2RWSq4ugDLe6iZgAsg++AABJM9IAAHXVkMA== Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D0185AD43B8@HE111648.emea1.cds.t-internal.com> References: <4D9B04E3.2090301@ericsson.com> <580BEA5E3B99744AB1F5BFF5E9A3C67D01859CA8D4@HE111648.emea1.cds.t-internal.com> <54633A5E61DC84429CB9FE3D9143C72103D739BF@MBX.dialogic.com> In-Reply-To: <54633A5E61DC84429CB9FE3D9143C72103D739BF@MBX.dialogic.com> Accept-Language: en-US, de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dispatch] SIP responses carrying Q.850 cause values in Reason header fields X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2011 11:15:32 -0000 Hi James, we have discussed 199 please see mail from Paul: ----Start Pauls Mail I've realized via discussions with Christer that the changes here are introducing a conflict with the 199 draft. That draft is explicitly calling for use of a Reason header with sip cause code to indicate the final sip response that caused a 199 response to be sent. Because 199 is being defined to explicitly allow this usage, it is in compliance with 3326. If we were to revise 3326 as we are discussing, then the 199 usage would be in conflict with the revision. So, I think we have to craft the wording very carefully here, to allow the use of Q.850 codes in a range of responses, while leaving the use of sip reason codes up to per-response-code specifications, as it was. And I'll restate that it probably doesn't make good sense to use any/all Q.850 response codes in an arbitrary sip response either. Thanks, Paul ---- End Pauls Mail With regard to 18x. Within ISUP a cause value could be also sent within an = ACM to progress "early media" for specific announcements. Earlier the reaso= n within 18x were discussed, and it was agreed to include these within this= scope. Best Regards Roland Jesske > -----Urspr=FCngliche Nachricht----- > Von: James Rafferty [mailto:James.Rafferty@dialogic.com] > Gesendet: Mittwoch, 6. April 2011 20:06 > An: Jesske, Roland; Gonzalo.Camarillo@ericsson.com; dispatch@ietf.org > Betreff: RE: [dispatch] SIP responses carrying Q.850 cause > values in Reason header fields > > Hi, > > I ran this proposal by one of our architects and got the > following feedback and questions for clarification: > > The change actually makes sense and we do support the > majority of the change already. The main part that we do not > support is the use of the Reason header in 18x or 199 > provisional responses as it is not defined how you want to > interwork that overall message. > > For example, if you get IAM send Invite, then 100 > Trying, then you get 180 Ringing that has a Reason header > with Q.850 of cause code 31, do you release the call after > that and send REL with cause code 31 to the PSTN or do you > send ACM back to the PSTN? > > James > > -----Original Message----- > From: dispatch-bounces@ietf.org > [mailto:dispatch-bounces@ietf.org] On Behalf Of R.Jesske@telekom.de > Sent: Wednesday, April 06, 2011 5:24 AM > To: Gonzalo.Camarillo@ericsson.com; dispatch@ietf.org > Subject: Re: [dispatch] SIP responses carrying Q.850 cause > values in Reason header fields > > Hi Gonzalo, > I'm OK with your proposal so I could change it if people > would like it. > It makes it shorter. > The only I would propose to have in is the explicit > mentioning of the Response values due to the fact that a > 100OK or 200OK should not include a Reason header with a > Q.850 Cause Value. > > Best Regards > Roland Jesske > > > > > -----Urspr=FCngliche Nachricht----- > > Von: dispatch-bounces@ietf.org > > [mailto:dispatch-bounces@ietf.org] Im Auftrag von Gonzalo Camarillo > > Gesendet: Dienstag, 5. April 2011 14:03 > > An: DISPATCH > > Betreff: [dispatch] SIP responses carrying Q.850 cause values > > in Reason header fields > > > > Hi, > > > > last week in the DISPATCH session, there was consensus to allow SIP > > responses to carry Reason header fields with Q.850 cause > values. As I > > said some time ago, I am willing to AD sponsor this draft > if/when the > > DISPATCH chairs confirm such consensus on the list. > > > > In the mean time, I have some comments on how to document > > this decision. > > The following (fairly short) draft updates a couple of > > paragraphs in RFC > > 3326 in order to achieve the desired outcome: > > > > http://www.ietf.org/id/draft-jesske-dispatch-update3326-reason > > -responses-02.txt > > > > I think this is not a particularly elegant way to define > what we want. > > For example, if we wanted to define a solution to HERFP in > the future > > based on the Reason header, we would need to update those paragraphs > > again, making them longer every time we added a new use case. > > > > Instead, I would prefer to explicitly define what we want > to do and be > > done with it. Such a (also fairly short) draft would say > > something along > > the following lines: > > > > "RFC 3326 allows the presence of the Reason header field in > > any response > > whose status code explicitly allows its presence. This document > > explicitly allows any SIP response to carry a Reason header > > field with a > > Q.850 cause value. SIP responses with Reason header fields carrying > > values other than Q.850 cause values are outside of the > scope of this > > document." > > > > I would like to know the opinion of the WG on this matter > > (i.e., how to > > document the WG's consensus). Note that reaching consensus was the > > difficult part. Agreeing on how to document it should be easy. > > > > Thanks, > > > > Gonzalo > > > > _______________________________________________ > > 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 > From mary.ietf.barnes@gmail.com Wed Apr 20 14:20:34 2011 Return-Path: X-Original-To: dispatch@ietfc.amsl.com Delivered-To: dispatch@ietfc.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 12C92E0728 for ; Wed, 20 Apr 2011 14:20:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.225 X-Spam-Level: X-Spam-Status: No, score=-104.225 tagged_above=-999 required=5 tests=[AWL=1.373, BAYES_00=-2.599, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aCTCrFND1N78 for ; Wed, 20 Apr 2011 14:20:32 -0700 (PDT) Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfc.amsl.com (Postfix) with ESMTP id 946C2E074C for ; Wed, 20 Apr 2011 14:20:32 -0700 (PDT) Received: by vws12 with SMTP id 12so1107039vws.31 for ; Wed, 20 Apr 2011 14:20:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=frz5JLi0800+M9qmVRpx2QQrDrl4W8UsAQVW/lZhIs8=; b=jHNsWv7ATXgrCsZn7MQs25LVFX7saHV5pqUe4Ms+VYuSebgWbGCHbPR9M/B81ypghB slTaMJVa+9FocFzcf85evweDD92rzF2+GSGNLDI/Q+ui+zoEftKAs8GY3QAMG0hUbaL1 xvv2mcFUW0xXooZgC/K3gGtx1/uvUaTZJPozk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=vpccQ8fqr98g4sPiS7AVcHdgPmZ/TRxXbyu3KwfgyKfE894ZwTw32uzq4OH3Lh5w5f YNcbBd97b/klxAL0JWZruh6kW8D7L2pNNOl5felO9eH4HVrugwgzzA3G9YlhXejmEAEW ZAnT98HjtMXqq0oP64yNFYcePG6JjLZwXsXyI= MIME-Version: 1.0 Received: by 10.52.0.236 with SMTP id 12mr11656302vdh.223.1303334432036; Wed, 20 Apr 2011 14:20:32 -0700 (PDT) Received: by 10.52.167.137 with HTTP; Wed, 20 Apr 2011 14:20:31 -0700 (PDT) In-Reply-To: <4483E11778CA964F9644B68621E1CA464A55F513@CRPMBOXPRD02.polycom.com> References: <4483E11778CA964F9644B68621E1CA464A55F513@CRPMBOXPRD02.polycom.com> Date: Wed, 20 Apr 2011 16:20:31 -0500 Message-ID: From: Mary Barnes To: DISPATCH Content-Type: multipart/mixed; boundary=20cf30434702d8589704a1603181 Cc: allessandro.forcina@telecomitalia.it Subject: [dispatch] FW: Invitation i3 Forum Workshop - Washington D.C., May 26th 2011 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2011 21:20:34 -0000 --20cf30434702d8589704a1603181 Content-Type: multipart/alternative; boundary=20cf30434702d8588504a160317f --20cf30434702d8588504a160317f Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable This workshop might be of interest, noting that they specifically would lik= e participation of folks from IETF. Regards, Mary DISPATCH WG co-chair *From:* Forcina Alessandro [mailto:alessandro.forcina@telecomitalia.it] *Subject:* I: Invitation i3 Forum Workshop - Washington D.C., May 26th 2011 Dear Friends, On behalf i3 Forum, it is a pleasure for me to invite Sip Forum and IETF officials to attend the 2nd edition of the i3 Forum Workshop that will take place on May 26th in Washington D.C., USA after the ITW 2011 conference. The conference (see attachment) will focus on the strategic implications, marketing value and technical aspects of: - Streamlining IP Interoperability Processes: Signalling and ISUP Releas= e Cause Mapping - Ensuring an Optimum End-user Experience: QoS Control and Monitoring fo= r IP Voice - Maximizing Voice Service Flexibility: Routing and Addressing Challenge= s and Opportunities - IPX in the Real World - Why IP Interconnection Matters to the Business of Voice More specifically, in addition to initial keynotes and final panel session on the carriers=92 industry, four sessions are scheduled on the following topics: [1] IPX; [2] QoS control and monitoring [3] Signalling (ISUP Release cause Mapping) [4] Routing & Addressing (Enum) We will be honoured if Sip Forum representative like to participate to the panel on QoS Control and monitoring or to have a speech on the issue of ISUP Release Cause Mapping. On this specific issue I can inform you that in late =9210 / early =9211 we jointly worked with 3GPP CT and we finalised th= e new version of TS 29.163 Version 7.22 which we fully support for the SIP interconnections. The view of Sip Forum / IETF on this issue is welcome. In case you or other Sip Forum / IETF representative are interested to participate to the panels feel free to contact me. In any case I thank you for distributing this message within your companies and within SiP Forum an= d IETF. For registration go to www.i3forum.org My best regards, Alessandro Forcina (acting as i3 Forum WS =93Technical Aspects=94 Chairman) Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. *This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intende= d recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.* *[image: rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non =E8 necessario.* Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. *This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intende= d recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.* *[image: rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non =E8 necessario.* --20cf30434702d8588504a160317f Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable This workshop might be of interest, noting that they specifically would lik= e participation of folks from IETF. =A0

Regards,
Mary
DISPATCH WG co-chair
<= br>


From:= Forcina Alessandro [mailto:alessandro.forci= na@telecomitalia.it]=A0

Subject: I: Invitation i3 Forum Workshop - Washington D.C.,= May 26th 2011

=A0

Dear Fr= iends,

=A0

On behalf i3 Forum, it is a pleasure for me to invite Sip Forum and = IETF officials to attend the 2nd edition of the i3 Forum Workshop that will= take place on May 26th in Washington D.C., USA after the ITW 2011 conferen= ce.

=A0

The conference (see at= tachment) will focus on the strategic implications, marketing value and tec= hnical aspects of:

  • Streamlining IP Interoperability Proc= esses: Signalling and ISUP Release Cause Mapping <= /span>
  • Ensuring an Optimum End-user Experience: QoS Control and = Monitoring for IP Voice
  • Maximizing Voice Service Fl= exibility: Routing and Addressing Challenges and Opportunities
  • IPX in the Real World
  • Why IP Interconnection Matters to the Business of Voice <= /span>

More specifically, in addi= tion to initial keynotes and final panel session on the carriers=92 industr= y, four sessions are scheduled on the following topics:

[= 1]=A0=A0 IPX;

[= 2]=A0=A0 QoS co= ntrol and monitoring

[= 3]=A0=A0 Signal= ling (ISUP Release cause Mapping)

[= 4]=A0=A0 Routin= g & Addressing (Enum)

=A0

We will be honoured if= Sip Forum representative like to participate to the panel on QoS Control a= nd monitoring =A0or to have a speech on the issue of ISUP Release Cause Map= ping. On this specific issue I can inform you that in late =9210 / early = =9211 we jointly worked with 3GPP CT and we finalised the new version of TS= 29.163 Version 7.22 which we fully support for the SIP interconnections. T= he view of Sip Forum / IETF on this issue is welcome.

=A0

In case you or other S= ip Forum / IETF representative are interested to participate to the panels = feel free to contact me. In any case I thank you for distributing this mess= age within your companies and within SiP Forum and IETF.

=A0

For registration go to= www.i3forum.org<= /span>

=A0

My best regards,

Alessandro Forcina

(acting = as i3 Forum WS =93Technical Aspects=94 Chairman)

=A0

<= td width=3D"468" style=3D"width:351.0pt;padding:.75pt .75pt .75pt .75pt">

Questo messaggio e i suoi allegati sono in= dirizzati esclusivamente alle persone indicate. La diffusione, copia o qual= siasi altra azione derivante dalla conoscenza di queste informazioni sono r= igorosamente vietate. Qualora abbiate ricevuto questo documento per errore = siete cortesemente pregati di darne immediata comunicazione al mittente e d= i provvedere alla sua distruzione, Grazie.

This e-mail and any attachments=A0is=A0confidential an= d may contain privileged information intended for the addressee(s) only. Di= ssemination, copying, printing or use by anybody else is unauthorised. If y= ou are not the intended recipient, please delete this message and any attac= hments and advise the sender by return e-mail, Thanks.

3D"rispettaRispett= a l'ambiente. Non stampare questa mail se non =E8 necessario.

=A0

Questo messaggio e i suoi allegati sono in= dirizzati esclusivamente alle persone indicate. La diffusione, copia o qual= siasi altra azione derivante dalla conoscenza di queste informazioni sono r= igorosamente vietate. Qualora abbiate ricevuto questo documento per errore = siete cortesemente pregati di darne immediata comunicazione al mittente e d= i provvedere alla sua distruzione, Grazie.

This e-mail and any attachments=A0is=A0confidential an= d may contain privileged information intended for the addressee(s) only. Di= ssemination, copying, printing or use by anybody else is unauthorised. If y= ou are not the intended recipient, please delete this message and any attac= hments and advise the sender by return e-mail, Thanks.

3D"rispettaRispett= a l'ambiente. Non stampare questa mail se non =E8 necessario.

=A0

<= br>
--20cf30434702d8588504a160317f-- --20cf30434702d8589704a1603181 Content-Type: text/plain; charset=US-ASCII; name="ATT00001..txt" Content-Disposition: attachment; filename="ATT00001..txt" Content-Transfer-Encoding: base64 X-Attachment-Id: 386fcc775505cfdf_0.1 X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCmRpcmVjdG9y cyBtYWlsaW5nIGxpc3QNCmRpcmVjdG9yc0BzaXBmb3J1bS5vcmcNCmh0dHA6Ly9zaXBmb3J1bS5v cmcvbWFpbG1hbi9saXN0aW5mby9kaXJlY3RvcnMNCg== --20cf30434702d8589704a1603181-- From tme@americafree.tv Wed Apr 20 16:01:09 2011 Return-Path: X-Original-To: dispatch@ietfc.amsl.com Delivered-To: dispatch@ietfc.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 5741FE0751 for ; Wed, 20 Apr 2011 16:01:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.195 X-Spam-Level: X-Spam-Status: No, score=-105.195 tagged_above=-999 required=5 tests=[AWL=3.404, BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QOUDsNhfTgyj for ; Wed, 20 Apr 2011 16:01:08 -0700 (PDT) Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by ietfc.amsl.com (Postfix) with ESMTP id 5F3E5E0721 for ; Wed, 20 Apr 2011 16:01:08 -0700 (PDT) Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 217E3A885618; Wed, 20 Apr 2011 19:01:08 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=windows-1252 From: Marshall Eubanks In-Reply-To: Date: Wed, 20 Apr 2011 19:01:05 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <694C8C05-64C0-453E-A122-4890F91077F5@americafree.tv> References: <4483E11778CA964F9644B68621E1CA464A55F513@CRPMBOXPRD02.polycom.com> To: Mary Barnes X-Mailer: Apple Mail (2.1081) Cc: DISPATCH , allessandro.forcina@telecomitalia.it Subject: Re: [dispatch] FW: Invitation i3 Forum Workshop - Washington D.C., May 26th 2011 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2011 23:01:09 -0000 On Apr 20, 2011, at 5:20 PM, Mary Barnes wrote: > This workshop might be of interest, noting that they specifically = would like participation of folks from IETF. =20 >=20 The ITW they refer to is this http://www.internationaltelecomsweek.com/ 23-25 May, 2011 in DC, which is also something of interest. Regards Marshall > Regards, > Mary > DISPATCH WG co-chair >=20 >=20 >=20 > From: Forcina Alessandro [mailto:alessandro.forcina@telecomitalia.it]=20= >=20 > Subject: I: Invitation i3 Forum Workshop - Washington D.C., May 26th = 2011 >=20 >=20 > =20 > Dear Friends, >=20 > =20 > On behalf i3 Forum, it is a pleasure for me to invite Sip Forum and = IETF officials to attend the 2nd edition of the i3 Forum Workshop that = will take place on May 26th in Washington D.C., USA after the ITW 2011 = conference. >=20 > =20 > The conference (see attachment) will focus on the strategic = implications, marketing value and technical aspects of: >=20 > =95 Streamlining IP Interoperability Processes: Signalling and = ISUP Release Cause Mapping > =95 Ensuring an Optimum End-user Experience: QoS Control and = Monitoring for IP Voice > =95 Maximizing Voice Service Flexibility: Routing and Addressing = Challenges and Opportunities > =95 IPX in the Real World > =95 Why IP Interconnection Matters to the Business of Voice > More specifically, in addition to initial keynotes and final panel = session on the carriers=92 industry, four sessions are scheduled on the = following topics: >=20 > [1] IPX; >=20 > [2] QoS control and monitoring >=20 > [3] Signalling (ISUP Release cause Mapping) >=20 > [4] Routing & Addressing (Enum) >=20 > =20 > We will be honoured if Sip Forum representative like to participate to = the panel on QoS Control and monitoring or to have a speech on the = issue of ISUP Release Cause Mapping. On this specific issue I can inform = you that in late =9210 / early =9211 we jointly worked with 3GPP CT and = we finalised the new version of TS 29.163 Version 7.22 which we fully = support for the SIP interconnections. The view of Sip Forum / IETF on = this issue is welcome. >=20 > =20 > In case you or other Sip Forum / IETF representative are interested to = participate to the panels feel free to contact me. In any case I thank = you for distributing this message within your companies and within SiP = Forum and IETF. >=20 > =20 > For registration go to www.i3forum.org >=20 > =20 > My best regards, >=20 > Alessandro Forcina >=20 > (acting as i3 Forum WS =93Technical Aspects=94 Chairman) >=20 > =20 > Questo messaggio e i suoi allegati sono indirizzati esclusivamente = alle persone indicate. La diffusione, copia o qualsiasi altra azione = derivante dalla conoscenza di queste informazioni sono rigorosamente = vietate. Qualora abbiate ricevuto questo documento per errore siete = cortesemente pregati di darne immediata comunicazione al mittente e di = provvedere alla sua distruzione, Grazie. >=20 > This e-mail and any attachments is confidential and may contain = privileged information intended for the addressee(s) only. = Dissemination, copying, printing or use by anybody else is unauthorised. = If you are not the intended recipient, please delete this message and = any attachments and advise the sender by return e-mail, Thanks. >=20 > Rispetta l'ambiente. Non stampare questa mail se non =E8 necessario. >=20 > =20 > Questo messaggio e i suoi allegati sono indirizzati esclusivamente = alle persone indicate. La diffusione, copia o qualsiasi altra azione = derivante dalla conoscenza di queste informazioni sono rigorosamente = vietate. Qualora abbiate ricevuto questo documento per errore siete = cortesemente pregati di darne immediata comunicazione al mittente e di = provvedere alla sua distruzione, Grazie. >=20 > This e-mail and any attachments is confidential and may contain = privileged information intended for the addressee(s) only. = Dissemination, copying, printing or use by anybody else is unauthorised. = If you are not the intended recipient, please delete this message and = any attachments and advise the sender by return e-mail, Thanks. >=20 > Rispetta l'ambiente. Non stampare questa mail se non =E8 necessario. >=20 > =20 >=20 > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch From mary.ietf.barnes@gmail.com Fri Apr 29 11:44:48 2011 Return-Path: X-Original-To: dispatch@ietfa.amsl.com Delivered-To: dispatch@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFA95E0710 for ; Fri, 29 Apr 2011 11:44:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.592 X-Spam-Level: X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dj+QHotxAhnQ for ; Fri, 29 Apr 2011 11:44:48 -0700 (PDT) Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2A055E06D6 for ; Fri, 29 Apr 2011 11:44:48 -0700 (PDT) Received: by vxg33 with SMTP id 33so3495546vxg.31 for ; Fri, 29 Apr 2011 11:44:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=a6Is8IgQgJU0CiqmvbBtx0DFcFKh3ANH8/uvwb4A7Zs=; b=lmnkip7LDd3wKpXw3lZRudL0N9Ii3Bx7Cwe6UmXCsvvIfHqPeJ0L1LvXn+wkKL58EU t43nGM9nHLbESpgqMmOIGPX77/Ya5Y3d/2/bxWS3012Bzq9Nia9LryAqlxGJwbpDjPlf ph4EnqtKQNmBbjnrSZw1XhNETgMSM+CyCv020= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=VVH2FsrHCSKdOM+IECLf8VSa64NhFSD+LrLijscvoHyBRMYqJF0zz7whNBQPK7NiKK qb/zh3WfkpK2LmG+YnvyFkB0ROUz+5HJ3is7qCW6cVJ0Jli2a2tVDGpLNvL7g0pXGJOX ETvMmlKlQ3ndb3eHXDQ7hE7jRuAqjodgkKpQA= MIME-Version: 1.0 Received: by 10.52.113.193 with SMTP id ja1mr3925255vdb.183.1304102687605; Fri, 29 Apr 2011 11:44:47 -0700 (PDT) Received: by 10.52.160.132 with HTTP; Fri, 29 Apr 2011 11:44:47 -0700 (PDT) Date: Fri, 29 Apr 2011 13:44:47 -0500 Message-ID: From: Mary Barnes To: DISPATCH Content-Type: multipart/alternative; boundary=bcaec548a6f97201d604a213119b Subject: [dispatch] Deadlines for IETF-81 X-BeenThere: dispatch@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: DISPATCH Working Group Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2011 18:44:49 -0000 --bcaec548a6f97201d604a213119b Content-Type: text/plain; charset=ISO-8859-1 Hi folks, As you should be aware, registration and planning are underway for IETF-81: http://www.ietf.org/meeting/81/index.html Here's a reminder of the deadlines for the DISPATCH WG for the upcoming meeting, the first of which is about 2 weeks away: http://trac.tools.ietf.org/wg/dispatch/trac/wiki * *May 16, 2011*. Cutoff date to notify the chairs/DISPATCH WG of plans to submit a proposal. [Two weeks prior to BoF proposal deadline, 7 weeks before -00 deadline] * *May 23, 2011*. Cutoff for charter proposals for topics. [One week prior to BoF proposal deadline*, two weeks before announcement of topics] * *June 6, 2011*. Topics that are to be the focus of IETF-81 are announced. [Typically one week before AD BoF approval and deadline to request WG slot, 4 weeks before -00 deadline] * *July 4, 2011*. -00 draft deadline. * *July 11, 2011*. Draft deadline. Regards, Mary DISPATCH WG co-chair --bcaec548a6f97201d604a213119b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi folks,
=A0
As you should be aware, registration and planning are underway for IET= F-81:
=A0
Here's a reminder of the deadlines for the DISPATCH WG for the upc= oming meeting, the first of which is about 2 weeks away:
=A0

* May 16, 2011.=A0Cutoff date to notify the chairs/DISP= ATCH WG of plans to submit a proposal. [Two weeks prior to BoF proposal dea= dline, 7 weeks before -00 deadline]

* May 23, 2011.=A0Cutoff for charter proposals for topi= cs. [One week prior to BoF proposal deadline*, two weeks before announcemen= t of topics]

* June 6, 2011.=A0Topics that are to be the focus of IE= TF-81 are announced. [Typically one week before AD BoF approval and deadlin= e to request WG slot, 4 weeks before -00 deadline]

* July 4, 2011.=A0-00 draft deadline.

* July 11, 2011.=A0Draft deadline.

Regards,
Mary
DISPATCH WG co-chair
--bcaec548a6f97201d604a213119b--