[clue] Fwd: How to exchange metadata about the media streams established with a SIP session
Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Tue, 28 February 2012 11:20 UTC
Return-Path: <gonzalo.camarillo@ericsson.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DEDF21F8601 for <clue@ietfa.amsl.com>; Tue, 28 Feb 2012 03:20:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.247
X-Spam-Level:
X-Spam-Status: No, score=-110.247 tagged_above=-999 required=5 tests=[AWL=0.352, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 SZ9zBmKN91Iw for <clue@ietfa.amsl.com>; Tue, 28 Feb 2012 03:20:40 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id D615221F85A7 for <clue@ietf.org>; Tue, 28 Feb 2012 03:20:39 -0800 (PST)
X-AuditID: c1b4fb3d-b7bb7ae0000007b2-59-4f4cb8869d5d
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 26.7E.01970.688BC4F4; Tue, 28 Feb 2012 12:20:39 +0100 (CET)
Received: from [131.160.36.141] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.213.0; Tue, 28 Feb 2012 12:20:38 +0100
Message-ID: <4F4CB886.3070404@ericsson.com>
Date: Tue, 28 Feb 2012 13:20:38 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: clue@ietf.org
References: <4F4CB861.4090805@ericsson.com>
In-Reply-To: <4F4CB861.4090805@ericsson.com>
X-Enigmail-Version: 1.3.4
X-Forwarded-Message-Id: <4F4CB861.4090805@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Subject: [clue] Fwd: How to exchange metadata about the media streams established with a SIP session
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2012 11:20:40 -0000
FYI. -------- Original Message -------- Subject: How to exchange metadata about the media streams established with a SIP session Date: Tue, 28 Feb 2012 13:20:01 +0200 From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> To: rai@ietf.org Folks, I am sending this email to the RAI list because it is about an architectural issue that affects more than one WG. Both the CLUE and SIPREC WGs have identified the need to exchange metadata about media streams that have been established using SIP. Both groups need to transport such metadata between SIP UAs. In CLUE, they are studying how to transport their metadata, as documented in: http://tools.ietf.org/html/draft-wenger-clue-transport-01 In SIPREC, they are planning to piggyback the metadata in SIP UPDATEs as an XML-encoded body part. When they need to send a request for full state (as opposed to partial state), they use an UPDATE request with a particular body type, as documented in: http://tools.ietf.org/html/draft-ietf-siprec-protocol-02 The best way to exchange metadata within a SIP session depends on the type of metadata and on how the UAs need to interact with each other (e.g., a UA simply pushing information to the other UA or a more complicated protocol). Given that SIPREC and CLUE have different metadata and interactions, it may well be that we decide to use a different mechanism in each group. Nevertheless, I think both groups would benefit from architecturally-inclined RAI people having a look at their work. Please, continue this discussion focusing on their specific requirements on either the CLUE list or the SIPREC list. Somewhat related to this issue, the RTCWeb group discussed the use of SCTP over UDP as a reliable NAT-friendly way to exchange data between endpoints. Cheers, Gonzalo
- [clue] Fwd: How to exchange metadata about the me… Gonzalo Camarillo