[Stox] sip-xmpp-media: scope, transparency, extensibility?
<Markus.Isomaki@nokia.com> Tue, 04 June 2013 13:31 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 DBEDE21F9CDC for <stox@ietfa.amsl.com>; Tue, 4 Jun 2013 06:31:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.381
X-Spam-Level:
X-Spam-Status: No, score=-6.381 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 NxChADAjZO00 for <stox@ietfa.amsl.com>; Tue, 4 Jun 2013 06:31:42 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id 2B61E21F9A2F for <stox@ietf.org>; Tue, 4 Jun 2013 04:59:30 -0700 (PDT)
Received: from vaebh102.NOE.Nokia.com (in-mx.nokia.com [10.160.244.23]) by mgw-da02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r54BwmHr011089 for <stox@ietf.org>; Tue, 4 Jun 2013 14:59:29 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.60]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 4 Jun 2013 14:59:34 +0300
Received: from 008-AM1MPN1-043.mgdnok.nokia.com ([169.254.3.241]) by 008-AM1MMR1-005.mgdnok.nokia.com ([65.54.30.60]) with mapi id 14.02.0328.011; Tue, 4 Jun 2013 11:59:19 +0000
From: Markus.Isomaki@nokia.com
To: stox@ietf.org
Thread-Topic: sip-xmpp-media: scope, transparency, extensibility?
Thread-Index: Ac5hEd91gMqePBGKTJuHzbQj+2uuXQ==
Date: Tue, 04 Jun 2013 12:00:30 +0000
Message-ID: <E44893DD4E290745BB608EB23FDDB7620A00461C@008-AM1MPN1-043.mgdnok.nokia.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: AUkF7AZ/aooHlqC+qifQh1oZGlMhuIfGbzKxUtD/1r6Bf56b+50Rj1NtJIwAuByN4PL+tbol86DsqiVVK4vJ+CMPJLsujmoJVPCsHXdDsh7iUwffUP8aODGhzhEeXSa68bUKKIS30s7f9/ZqjJHDPYjx3g9mgZ14bH87ZOhYzFFtfLRLGwK5iA662At4xTL5+Ab46gbVLOuzJJ8HHofQDgCshheWime8axOSNlM2JFHlZDka9lahtlUBuxGmZKc6BH9lrRFZQIwrpVHJtKl0XQ==
x-originating-ip: [172.21.82.162]
Content-Type: multipart/alternative; boundary="_000_E44893DD4E290745BB608EB23FDDB7620A00461C008AM1MPN1043mg_"
MIME-Version: 1.0
X-OriginalArrivalTime: 04 Jun 2013 11:59:34.0083 (UTC) FILETIME=[FA8BC130:01CE611A]
X-Nokia-AV: Clean
Subject: [Stox] sip-xmpp-media: scope, transparency, extensibility?
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: Tue, 04 Jun 2013 13:31:57 -0000
Hi,
A high-level comment about sip-xmpp-media [1]:
SDP/Jingle Offer/Answer and ICE are moving targets by themselves. For instance right now MMUSIC WG is working on new features such as "trickle-ICE" (adding new candidates on the fly - I know this is already supported in Jingle) and "bundle" (multiplexing several RTP sessions/streams into a single transport-level packet flow).
We need to ensure that the sip-xmpp-media RFC-to-become is generic enough to stay valid even when such extensions are developed, and we have a story on how and where the SIP-XMPP mappings to various extensions can be developed if needed.
For instance "bundle", AFAIK, is going to be entirely SDP/Jingle level issue, so presumably it will be enough that after the MMUSIC SDP spec is done, a mapping spec to Jingle is written in XSF? On the other hand, trickle-ICE, AFAIK, will require the use of SIP INFO (gasp! ;-) method to carry the new candidates. That seems like something that would require an extension (" a new RFC") to sip-xmpp-media in the IETF, explaining how Jingle's trickle is mapped to SIP's trickle.
Regards,
Markus
[1] http://datatracker.ietf.org/doc/draft-saintandre-sip-xmpp-media/
- [Stox] sip-xmpp-media: scope, transparency, exten… Markus.Isomaki
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Peter Saint-Andre
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Emil Ivov
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Emil Ivov
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Peter Saint-Andre
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Emil Ivov
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Peter Saint-Andre
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Emil Ivov
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Saúl Ibarra Corretgé
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Emil Ivov
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Markus.Isomaki
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Peter Saint-Andre
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Emil Ivov
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Peter Saint-Andre
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Markus.Isomaki
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Saúl Ibarra Corretgé
- Re: [Stox] sip-xmpp-media: scope, transparency, e… Peter Saint-Andre