IETF Logo Mail Archive

Re: [clue] IETF#89: CLUE Data Channel - Next Step

Mary Barnes <mary.ietf.barnes@gmail.com> Thu, 06 March 2014 09:50 UTC

Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 560471A019A for <clue@ietfa.amsl.com>; Thu, 6 Mar 2014 01:50:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qx0tmejJOu1I for <clue@ietfa.amsl.com>; Thu, 6 Mar 2014 01:50:23 -0800 (PST)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id D1EE51A0194 for <clue@ietf.org>; Thu, 6 Mar 2014 01:50:22 -0800 (PST)
Received: by mail-we0-f179.google.com with SMTP id x48so2751732wes.38 for <clue@ietf.org>; Thu, 06 Mar 2014 01:50:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oPUXtJTExlvuoxSfTqOQMpo/DWopBp/XAPcuNDb+sAk=; b=vrSe2Vkuc8ZLRzc9w4Jh5Ej14pFXlsYmBGzAzj29ZlYyRA+QpnKg3Xnh5K/Qt1/isL B2JYZwC0V3uQG7ovUa+EYVaEcEzKtabBF7wqfBzEBQaioZb4f3yVwzf7escWIgmTb1h4 gdf1WcVDOxBwKRog7+V4J7o46PN1VpayiuAyfEC4UUZq0SrM520rTCDBH11mQKc6DPYJ ndUUUdjiPwoZT5GM5f4FmABoUH63AOzazMud5RClmCmeUvvJqoJS0LL6UMpraCIZS2NC eGzkNFikII5/Ufd0VXpvz3fHTnjO+Z58SptqJjuFM9IVbAZdfuzWoqjl0lPdKisFYT5t qFvg==
MIME-Version: 1.0
X-Received: by 10.194.82.69 with SMTP id g5mr8154639wjy.85.1394099410888; Thu, 06 Mar 2014 01:50:10 -0800 (PST)
Received: by 10.217.96.195 with HTTP; Thu, 6 Mar 2014 01:50:10 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1CFD69@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1CFD69@ESESSMB209.ericsson.se>
Date: Thu, 06 Mar 2014 03:50:10 -0600
Message-ID: <CAHBDyN7n+evosjX-jNuzJa1DoGGNMuBqLkoPccZbMUnx+a5u9g@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="047d7bb047942aefa804f3ed108e"
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/nBF7sPRt92E7dzWuKCj7IfxT_2w
Cc: "clue@ietf.org" <clue@ietf.org>
Subject: Re: [clue] IETF#89: CLUE Data Channel - Next Step
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 06 Mar 2014 09:50:26 -0000

Just for clarification, the reference to the "eyzak" draft is:
http://datatracker.ietf.org/doc/draft-ejzak-mmusic-data-channel-sdpneg/

Note, it's NOT the version that shows up for DISPATCH.

Mary.


On Wed, Mar 5, 2014 at 2:38 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>  Hi data channel lovers,
>
>  Today we agreed to adopt DECP for the CLUE Data Channel (CDC).
>
>  (Note that we did NOT prevent usage of draft-eyzak, if the mechanism
> gets done in MMUSIC).
>
>  (We also agreed that there needs to be A way to identity that a call can
> use CLUE, but that is NOT the topic of this e-mail - please start a
> separate thread if you want to discuss that).
>
>  As time has been allocated for the CDC also on Friday, I intend to use
> that time to discuss the issue regarding who is responsible for sending
> DATA_CHANNEL_OPEN.
>
>
>  First we need to decide if we want to specify who is responsible, or
> whether we'll specify procedures when both endpoints send DCO.
>
>  My suggestion is that we do specify that one of the endpoints is
> responsible.
>
>  Second, if we agree to the suggestion above, we need to decide which
> endpoint is responsible for sending DCO. Alternatives are e.g. offerer,
> answerer, DTLS client and DTLS server. Note that this is separate from
> which endpoint establishes the SCTP association, and how the DTLS roles are
> determined - those procedures are defined in the sctp-sdp draft.
>
>  Also, we do need to describe what happens if both endpoint still sends
> DCO. It would be considered an error case, and we could e.g. say that the
> endpoint responsible for sending DCO would have to reset the stream/channel
> created by the other endpoint.
>
>  Regards,
>
>  Christer
>  Sent from Windows Mail
>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>
>

v2.23.0 | Report a Bug | By Email