Re: [Stox] Mapping for media signaling: still about the scope

Saúl Ibarra Corretgé <saul@ag-projects.com> Sun, 28 July 2013 21:38 UTC

Return-Path: <saul@ag-projects.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 B0A9021F89C3 for <stox@ietfa.amsl.com>; Sun, 28 Jul 2013 14:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.024
X-Spam-Level:
X-Spam-Status: No, score=-0.024 tagged_above=-999 required=5 tests=[AWL=0.195, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, J_CHICKENPOX_43=0.6, MIME_8BIT_HEADER=0.3, 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 xt6gswq8dakY for <stox@ietfa.amsl.com>; Sun, 28 Jul 2013 14:38:16 -0700 (PDT)
Received: from mail.sipthor.net (node06.dns-hosting.info [85.17.186.6]) by ietfa.amsl.com (Postfix) with ESMTP id CA77E21F9635 for <stox@ietf.org>; Sun, 28 Jul 2013 14:38:14 -0700 (PDT)
Received: by mail.sipthor.net (Postfix, from userid 5001) id 711FFB35DE; Sun, 28 Jul 2013 23:38:13 +0200 (CEST)
Received: from imac.saghul.lan (ip3e830637.speed.planet.nl [62.131.6.55]) by mail.sipthor.net (Postfix) with ESMTPSA id 2D9E9B017A; Sun, 28 Jul 2013 23:38:12 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="iso-8859-1"
From: Saúl Ibarra Corretgé <saul@ag-projects.com>
In-Reply-To: <E44893DD4E290745BB608EB23FDDB7620A060F4C@008-AM1MPN1-043.mgdnok.nokia.com>
Date: Sun, 28 Jul 2013 23:38:11 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <15FFF4CE-4860-4796-8F7E-F0523FFDE486@ag-projects.com>
References: <E44893DD4E290745BB608EB23FDDB7620A01C877@008-AM1MPN1-042.mgdnok.nokia.com> <51C1F1AB.1040701@jitsi.org> <E44893DD4E290745BB608EB23FDDB7620A01DBE9@008-AM1MPN1-042.mgdnok.nokia.com> <51F4F050.2040309@stpeter.im> <51F4F8E4.2070105@goodadvice.pages.de> <E44893DD4E290745BB608EB23FDDB7620A060F4C@008-AM1MPN1-043.mgdnok.nokia.com>
To: Markus.Isomaki@nokia.com
X-Mailer: Apple Mail (2.1085)
Cc: stox@ietf.org, fippo@goodadvice.pages.de
Subject: Re: [Stox] Mapping for media signaling: still about the scope
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: Sun, 28 Jul 2013 21:38:21 -0000

On Jul 28, 2013, at 4:15 PM, <Markus.Isomaki@nokia.com> <Markus.Isomaki@nokia.com> wrote:

> Hi Peter, Philipp,
> 
> Philipp Hancke wrote,
>> 
>> Am 28.07.2013 12:20, schrieb Peter Saint-Andre:
>> [...]
>>> I like that approach. The Jingle XEPs already define SDP mappings for
>>> the base use cases, and that content could be moved to the stox-media
>>> I-D. If additional features are defined in SIP, SDP, or Jingle
>>> (trickle-ICE, BUNDLE, multistream, etc.) then we can specify those in
>>> incremental extensions.
>> 
>> Right. The problem on the XSF side is that this mapping is currently spread
>> over (from the top of my head) XEPs 0166, 0167, 0176, (0177 doesn't bother
>> mapping), 0293, 0294 and 0320. This is something that needs to be more
>> centralized anyway and the stox-media draft might be the normative place to
>> do this.
>> 
> 
> It sounds to me then that the STOX WG should:
> - Consolidate the mappings for all stable specs and features into the current -media document and aim to publish it as an RFC according to the current charter, i.e. deliver it to the IESG (hopefully) already before IETF 88. The value of stabilizing and publishing that document would be that the mappings would be found in one place.
> - Start, first as individual (non-WG) drafts, incremental extensions for the relevant new features (mentioned above). Perhaps one draft is enough for all of the listed ones if their timeline is roughly identical and there is interest to cover all of them. That draft would evolve as the actual extensions in IETF and XSF develop, and would get published as an RFC around the same time as them (next year?). If things progress well, we could adopt that draft as a STOX WG item around IETF 88. I believe it does fit content-wise ("mapping for media signaling") to our charter, we just need to create an additional milestone for it. I don't know if we should keep the WG active for just one document, but given the overhead of creating new WGs etc., I think that would make sense.
> 

That sounds good to me!

> Saul's slides for next Thursday (https://dl.dropboxusercontent.com/u/2243619/stox-ietf87.pdf) seem to assume that approach. The chairs can perhaps create one-slider to be more explicit about the plan and scope. 
> 

Yeah, I somewhat assumed that,but it's definitely up for discussion. Since I'm not all that familiar with all the process, please do let me know if you rather have some extra items added to the slides and I'll gladly do so.


Cheers,

--
Saúl Ibarra Corretgé
AG Projects