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

<Markus.Isomaki@nokia.com> Sun, 28 July 2013 14:15 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 1DB7F21F9CAD for <stox@ietfa.amsl.com>; Sun, 28 Jul 2013 07:15:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.729
X-Spam-Level:
X-Spam-Status: No, score=-5.729 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 HXJHn4m0DLAd for <stox@ietfa.amsl.com>; Sun, 28 Jul 2013 07:15:29 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id BE1A021F9CAC for <stox@ietf.org>; Sun, 28 Jul 2013 07:15:29 -0700 (PDT)
Received: from vaebh101.NOE.Nokia.com (in-mx.nokia.com [10.160.244.22]) by mgw-da02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r6SEFJew015016; Sun, 28 Jul 2013 17:15:20 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.23]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Sun, 28 Jul 2013 17:15:19 +0300
Received: from 008-AM1MPN1-043.mgdnok.nokia.com ([169.254.3.18]) by 008-AM1MMR1-007.mgdnok.nokia.com ([65.54.30.23]) with mapi id 14.03.0136.001; Sun, 28 Jul 2013 14:15:18 +0000
From: Markus.Isomaki@nokia.com
To: fippo@goodadvice.pages.de, stox@ietf.org
Thread-Topic: [Stox] Mapping for media signaling: still about the scope
Thread-Index: Ac5s3MA7fW54rEx1RRO+pgL1gkj4zQAOhceAACMblMAHdi+XAAABRzsAAAZD1WA=
Date: Sun, 28 Jul 2013 14:15:17 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620A060F4C@008-AM1MPN1-043.mgdnok.nokia.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>
In-Reply-To: <51F4F8E4.2070105@goodadvice.pages.de>
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+/nZJb9Kg7Iv/YdXDG3jsbgoPRJrYyGPl+RLUy5o34pe1STuA2RpMSi077FMJtsQYCEodI7KBWg9ffclhoduPnayiFhwzReIw/VnMKcsz//oIBJDXVwpuXFGRIJZxiYjmuaNKS9a3pbBGCq5tU95fJcY5rB307tGcWSGlGkQ4tCxi2vH+3ZcePW5GHk1IeGyJogUs0wTjBSPiIeXeQaIpUBFFcmTWmh/ngZQRJKyH4cNW+CFlzU2cBE2iQQHlNE0jhpOByZKSJVg==
x-originating-ip: [91.152.96.196]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 28 Jul 2013 14:15:19.0367 (UTC) FILETIME=[E3D1F570:01CE8B9C]
X-Nokia-AV: Clean
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 14:15:35 -0000

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.

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. 

Markus