IETF Logo Mail Archive

Re: [RAI] How to exchange metadata about the media streams established with a SIP session

"Ravindran, Parthasarathi" <pravindran@sonusnet.com> Tue, 28 February 2012 11:49 UTC

Return-Path: <pravindran@sonusnet.com>
X-Original-To: rai@ietfa.amsl.com
Delivered-To: rai@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A89221F8619 for <rai@ietfa.amsl.com>; Tue, 28 Feb 2012 03:49:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.522
X-Spam-Level:
X-Spam-Status: No, score=-2.522 tagged_above=-999 required=5 tests=[AWL=0.077, BAYES_00=-2.599]
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 zD+aoJu50NAK for <rai@ietfa.amsl.com>; Tue, 28 Feb 2012 03:49:17 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 282A921F8613 for <rai@ietf.org>; Tue, 28 Feb 2012 03:49:17 -0800 (PST)
Received: from sonusmail05.sonusnet.com (sonusmail05.sonusnet.com [10.128.32.155]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id q1SBo2iH022578; Tue, 28 Feb 2012 06:50:02 -0500
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail05.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 28 Feb 2012 06:49:13 -0500
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 28 Feb 2012 17:19:10 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub01.sonusnet.com ([fe80::5cbc:2823:f6cc:9ce7%11]) with mapi id 14.01.0355.002; Tue, 28 Feb 2012 17:19:09 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "rai@ietf.org" <rai@ietf.org>
Thread-Topic: [RAI] How to exchange metadata about the media streams established with a SIP session
Thread-Index: AQHM9grzSsDTVY7e0UuDtFmiVKlxPZZSLCVw
Date: Tue, 28 Feb 2012 11:49:10 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C0E05106E@inba-mail01.sonusnet.com>
References: <4F4CB861.4090805@ericsson.com>
In-Reply-To: <4F4CB861.4090805@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.54.67]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 28 Feb 2012 11:49:10.0427 (UTC) FILETIME=[FBF8E6B0:01CCF60E]
Subject: Re: [RAI] How to exchange metadata about the media streams established with a SIP session
X-BeenThere: rai@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Real-time Applications and Infrastructure \(RAI\)" <rai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rai>, <mailto:rai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rai>
List-Post: <mailto:rai@ietf.org>
List-Help: <mailto:rai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rai>, <mailto:rai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2012 11:49:18 -0000

Hi all,

Just adding more information about SIPREC protocol, "SIPREC Metadata is transported in the body of INVITE or UPDATE or RE-INVITE or any SIP message with SDP from Session recording client (SRC) to Session Recording Server(SRS). Metadata request from SRS is a separate UPDATE transaction and SRC replies metadata in the subsequent transaction using RE-INVITE or UPDATE."

Thanks
Partha

>-----Original Message-----
>From: rai-bounces@ietf.org [mailto:rai-bounces@ietf.org] On Behalf Of
>Gonzalo Camarillo
>Sent: Tuesday, February 28, 2012 4:50 PM
>To: rai@ietf.org
>Subject: [RAI] How to exchange metadata about the media streams
>established with a SIP session
>
>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
>
>_______________________________________________
>RAI mailing list
>RAI@ietf.org
>https://www.ietf.org/mailman/listinfo/rai

v2.23.0 | Report a Bug | By Email