Re: [Stox] Mapping for media signaling: still about the scope
Peter Saint-Andre <stpeter@stpeter.im> Sun, 28 July 2013 14:48 UTC
Return-Path: <stpeter@stpeter.im>
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 387DE21F9DA1 for <stox@ietfa.amsl.com>; Sun, 28 Jul 2013 07:48:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.729
X-Spam-Level:
X-Spam-Status: No, score=-101.729 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_MLH_Stock1=0.87, USER_IN_WHITELIST=-100]
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 0D8sLWPdzNf3 for <stox@ietfa.amsl.com>; Sun, 28 Jul 2013 07:47:56 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED6121F9DAF for <stox@ietf.org>; Sun, 28 Jul 2013 07:47:56 -0700 (PDT)
Received: from che-vpn-cluster-2-459.cisco.com (unknown [198.135.0.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 5D4314004A; Sun, 28 Jul 2013 08:49:59 -0600 (MDT)
Message-ID: <51F52F17.5040607@stpeter.im>
Date: Sun, 28 Jul 2013 16:47:51 +0200
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Markus.Isomaki@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> <E44893DD4E290745BB608EB23FDDB7620A060F4C@008-AM1MPN1-043.mgdnok.nokia.com>
In-Reply-To: <E44893DD4E290745BB608EB23FDDB7620A060F4C@008-AM1MPN1-043.mgdnok.nokia.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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 14:48:01 -0000
On 7/28/13 4:15 PM, 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?). I think that is a reasonable approach. > 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. I am not fully sure about keeping the WG around, but I leave such decisions up to the chairs and ADs. ;-) > 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. That sounds helpful! Peter -- Peter Saint-Andre https://stpeter.im/
- [Stox] Mapping for media signaling: still about t… Markus.Isomaki
- Re: [Stox] Mapping for media signaling: still abo… Emil Ivov
- Re: [Stox] Mapping for media signaling: still abo… Philipp Hancke
- Re: [Stox] Mapping for media signaling: still abo… Markus.Isomaki
- Re: [Stox] Mapping for media signaling: still abo… Peter Saint-Andre
- Re: [Stox] Mapping for media signaling: still abo… Philipp Hancke
- Re: [Stox] Mapping for media signaling: still abo… Markus.Isomaki
- Re: [Stox] Mapping for media signaling: still abo… Peter Saint-Andre
- Re: [Stox] Mapping for media signaling: still abo… Saúl Ibarra Corretgé