Re: [Stox] current status

<Markus.Isomaki@nokia.com> Wed, 18 September 2013 11:17 UTC

Return-Path: <Markus.Isomaki@nokia.com>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C635811E8212 for <stox@ietfa.amsl.com>; Wed, 18 Sep 2013 04:17:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.728
X-Spam-Level:
X-Spam-Status: No, score=-5.728 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_MLH_Stock1=0.87]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TiXg1+tX-A-W for <stox@ietfa.amsl.com>; Wed, 18 Sep 2013 04:17:33 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id 48E6011E8200 for <stox@ietf.org>; Wed, 18 Sep 2013 04:17:29 -0700 (PDT)
Received: from smtp.mgd.nokia.com ([65.54.30.56]) by mgw-da02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r8IBG83B025087 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 18 Sep 2013 14:16:14 +0300
Received: from 008-AM1MPN1-043.mgdnok.nokia.com ([169.254.3.213]) by 008-AM1MMR1-001.mgdnok.nokia.com ([65.54.30.56]) with mapi id 14.03.0136.001; Wed, 18 Sep 2013 11:16:13 +0000
From: <Markus.Isomaki@nokia.com>
To: <mary.ietf.barnes@gmail.com>, <stpeter@stpeter.im>
Thread-Topic: [Stox] current status
Thread-Index: AQHOqq0qg9qblya/s0KWirTx3JDOFJm4rF8AgAA3LwCAAAVnAIAAAduAgBJ+KvA=
Date: Wed, 18 Sep 2013 11:16:12 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620A0B3F90@008-AM1MPN1-043.mgdnok.nokia.com>
References: <52294513.8080407@stpeter.im> <E44893DD4E290745BB608EB23FDDB7620A099FB8@008-AM1MPN1-041.mgdnok.nokia.com> <8EFEDB10-B1D2-4D58-80A1-BDC24BF1EA8E@ag-projects.com> <522A046A.3050105@stpeter.im> <CAHBDyN55w9Woj671-5_6ba=M25RE5FmiRU_G_1O1W8FbAJX1Sg@mail.gmail.com>
In-Reply-To: <CAHBDyN55w9Woj671-5_6ba=M25RE5FmiRU_G_1O1W8FbAJX1Sg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tituslabs-classifications-30: TLPropertyRoot=Nokia; Confidentiality=Nokia Internal Use Only; Project=None;
x-titus-version: 3.5.9.3
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7IulO1qCvm8En2VRIW+V9LtEkfnB+JBrLOQY7L/WBao7EFVKiEZvHemEz9atb8MiVcW8Gr5JjRlyAqXorWrEneXHHfMRItKJPBcYwZEUQgRv9PZZQGLxGwTo4m4InXalbdXDPk8g+PwDLCopuuJpQTZ6iWrr1+3IGFdgrh7nbKoLHo7LHFk3DQgyLyyTanLNATk5btvRRq4ZCcYLSHAtWgv4=
x-originating-ip: [10.236.6.11]
Content-Type: multipart/alternative; boundary="_000_E44893DD4E290745BB608EB23FDDB7620A0B3F90008AM1MPN1043mg_"
MIME-Version: 1.0
X-Nokia-AV: Clean
Cc: stox@ietf.org, saul@ag-projects.com
Subject: Re: [Stox] current status
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <stox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stox>, <mailto:stox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stox>
List-Post: <mailto:stox@ietf.org>
List-Help: <mailto:stox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stox>, <mailto:stox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2013 11:17:44 -0000

Hi,

There have been no further comments on this, so I think we can declare it decided that we won't expand the scope of -core with topics like forking, but leave that to the -media to handle.

My proposed plan for the next steps of the WG is:

-          Before Vancouver: Issue WG Last Calls on -core, -im, and -presence and see if they indeed are mature enough to be delivered forward.

-          For Vancouver: Get updated versions of especially -media, and possibly -chat and -groupchat, and collect the open issues about them.

-          In Vancouver: Discuss the open issues about -media, and if needed -chat and -groupchat.

-          After Vancouver: Depending on the maturity and issues raised, schedule WG Last Calls for the remaining deliverables.

Let the chairs (Yana and me) know if you have issues with this plan or even better, suggestions how to improve it.

Markus


From: ext Mary Barnes [mailto:mary.ietf.barnes@gmail.com]
Sent: 06 September, 2013 19:43
To: Peter Saint-Andre
Cc: Saúl Ibarra Corretgé; stox@ietf.org; Isomaki Markus (Nokia-CIC/Espoo)
Subject: Re: [Stox] current status



On Fri, Sep 6, 2013 at 11:35 AM, Peter Saint-Andre <stpeter@stpeter.im<mailto:stpeter@stpeter.im>> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 9/6/13 10:16 AM, Saúl Ibarra Corretgé wrote:
>
> On Sep 6, 2013, at 3:25 PM, <Markus.Isomaki@nokia.com<mailto:Markus.Isomaki@nokia.com>>
> <Markus.Isomaki@nokia.com<mailto:Markus.Isomaki@nokia.com>> wrote:
>
>> Hi,
>>
>> There have been a fair number of comments on -core, -im and
>> -presence since the Berlin IETF. Please take a look at the new
>> versions http://tools.ietf.org/id/draft-ietf-stox-core-04.txt
>> http://tools.ietf.org/id/draft-ietf-stox-im-02.txt
>> http://tools.ietf.org/id/draft-ietf-stox-presence-04.txt and see
>> if your issues have been properly addressed, and/or whether you
>> want to still raise any new issues.
>>
>> If nothing specific comes up, the chairs will consider starting
>> WG LC on these documents in the near future.
>>
>> One thing that I wonder about -core is whether it is a good idea
>> to stabilize or last call it yet at this point, since there have
>> been some issues raised about -media that might have impact to
>> -core, such as dealing with SIP side forking or loop detection.
>> So is it better to wait with -core until -media is more stable?
>>
>
> At some point we agreed that those issues would be handled in
> -media, because in other cases (chat, presence, im) the gateway is
> itself the endpoint and handles all the "media", so those didn't
> seem to apply.
That is my recollection, too.
 [MB] That was also what I thought when I reviewed -core. [/MB]

Thus I'd be in favor of stabilizing the -core spec, and hanlding the
forking issues in the -media spec.
[MB] I agree. [/MB]

Peter

- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSKgRqAAoJEOoGpJErxa2p4GUP/2bzG8+WbRPcn0JpREhws+T5
m3WBrq0OoJryDzxaA2HmBq15TBawWzsVce5dp4oOY73G9HsPxCyDHrPYiN/SBxhK
VTSrIid3GCd9s0uTNEgPIwcQ6DFJy5f3nxdo2YWgmm+ncJ7hvuSXSGoDCammAyX0
nGci5VPoesbj+LZaebSPgFDHX7jtVElqloR2wpHYxmTh+P34sXGuKneQH43wYdM7
seOMpsD8yyfwRUqvhglUf4H46maQvYENTDCFsk5XjbcWoJLK52+N+Pwkw9ofr6DZ
no/j5xPLY1mr3FTE0MTgMn0Nq3YSCD4M3jLrsjjdudvlQvLcItWIK4x9OO8JaaFx
5+AWtrCjn6yu/NKLgY8M5zhju51T8/srn1sBzxCQNkj5dNykbhp2W/Qo2Y+eahF1
cZEOhmTTALEpbqvtGxZBg/p9kSugwk3q4oAlP875JlBS+VLiiFXc6MIeXqWHS9yf
X2KXJj3xNrh1Esp/Z2FG/W5+uz+e9tT2IlevhKcNozFs+gyJHeD/KwZZ3Oc3/Hqj
4RkFcLW+8iXFqH1EozpYFcr7WOhNRlh2KtbBON/w9o7481i35HRG8cR0TtFZ//By
pqTdVWZhwYH3PR9B4+6cY53Lk5aWoL5RGX5DYMPluHuJGcPW99VORRE8RRo4eepC
nTGO/i5/5W8SC+EE3hO7
=6RTC
-----END PGP SIGNATURE-----
_______________________________________________
stox mailing list
stox@ietf.org<mailto:stox@ietf.org>
https://www.ietf.org/mailman/listinfo/stox