IETF Logo Mail Archive

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

Mary Barnes <mary.ietf.barnes@gmail.com> Tue, 28 February 2012 15:36 UTC

Return-Path: <mary.ietf.barnes@gmail.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 1C6FC21F86A4 for <rai@ietfa.amsl.com>; Tue, 28 Feb 2012 07:36:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.622
X-Spam-Level:
X-Spam-Status: No, score=-103.622 tagged_above=-999 required=5 tests=[AWL=-0.024, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, 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 sTAdTvjWuItD for <rai@ietfa.amsl.com>; Tue, 28 Feb 2012 07:36:20 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 96DD721F85E1 for <rai@ietf.org>; Tue, 28 Feb 2012 07:36:18 -0800 (PST)
Received: by vcbfk13 with SMTP id fk13so1860060vcb.31 for <rai@ietf.org>; Tue, 28 Feb 2012 07:36:17 -0800 (PST)
Received-SPF: pass (google.com: domain of mary.ietf.barnes@gmail.com designates 10.52.70.165 as permitted sender) client-ip=10.52.70.165;
Authentication-Results: mr.google.com; spf=pass (google.com: domain of mary.ietf.barnes@gmail.com designates 10.52.70.165 as permitted sender) smtp.mail=mary.ietf.barnes@gmail.com; dkim=pass header.i=mary.ietf.barnes@gmail.com
Received: from mr.google.com ([10.52.70.165]) by 10.52.70.165 with SMTP id n5mr13606267vdu.55.1330443377304 (num_hops = 1); Tue, 28 Feb 2012 07:36:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hi7b6Pu78fdA+IBQwUKYwNEMIKakFQ3pE7XGJhCKJzE=; b=LYEwWgJvH/Xt5xcqPhhKJIFm+GAKozLuYdMttwZjs6uSfDb3W6z3F2UQIh4IZ2jUIv P45lO70di8I1Jdkp/TMIMSUTp+O8CgEUG/gSQDGg8TwMERMWQCocBAHy75Yn0tsBBWZw S2s/J32qXDF8e8mlEgQaVF6XYd014CyTK/smg=
MIME-Version: 1.0
Received: by 10.52.70.165 with SMTP id n5mr11208524vdu.55.1330443377252; Tue, 28 Feb 2012 07:36:17 -0800 (PST)
Received: by 10.52.34.138 with HTTP; Tue, 28 Feb 2012 07:36:17 -0800 (PST)
In-Reply-To: <4F4CB861.4090805@ericsson.com>
References: <4F4CB861.4090805@ericsson.com>
Date: Tue, 28 Feb 2012 09:36:17 -0600
Message-ID: <CAHBDyN4r059aczatVqrmJF5iRb5W=-kuSuu3_Tcq3BLy72cqbg@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Content-Type: multipart/alternative; boundary="bcaec5015e53e5193104ba07fc18"
Cc: rai@ietf.org
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 15:36:23 -0000

There is additional detail (and drafts) on the signaling options for CLUE
being discussed in these email threads:
http://www.ietf.org/mail-archive/web/clue/current/msg01076.html
http://www.ietf.org/mail-archive/web/clue/current/msg01089.html
So, if anyone chooses to contribute to the discussion in CLUE, this email
discussion is a good place to start.

I also think the problem spaces are different enough that having a common
mechanism should not be required (or expected).

Mary.
CLUE WG co-chair

On Tue, Feb 28, 2012 at 5:20 AM, Gonzalo Camarillo <
Gonzalo.Camarillo@ericsson.com> wrote:

> 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