Re: [rtcweb] Notes from Data discussion today - DCEP MTI?

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 04 March 2014 15:58 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FAA51A0117 for <rtcweb@ietfa.amsl.com>; Tue, 4 Mar 2014 07:58:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
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 cgXMqEDN3wJj for <rtcweb@ietfa.amsl.com>; Tue, 4 Mar 2014 07:58:17 -0800 (PST)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id 506911A0141 for <rtcweb@ietf.org>; Tue, 4 Mar 2014 07:58:17 -0800 (PST)
Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta05.westchester.pa.mail.comcast.net with comcast id ZQ4h1n0020mv7h055TyEkc; Tue, 04 Mar 2014 15:58:14 +0000
Received: from dhcp-a663.meeting.ietf.org ([31.133.166.99]) by omta11.westchester.pa.mail.comcast.net with comcast id ZTw51n00s2904qf3XTw8Cb; Tue, 04 Mar 2014 15:56:12 +0000
Message-ID: <5315F795.7090304@alum.mit.edu>
Date: Tue, 04 Mar 2014 15:56:05 +0000
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <A44844EB-07A4-488F-9D2D-9BEDFF9512AC@iii.ca>
In-Reply-To: <A44844EB-07A4-488F-9D2D-9BEDFF9512AC@iii.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393948694; bh=8KLyW7oHHNiiCBFysysRxQ9pKqtOhvfhNjDL3pXKMKA=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=smkSykVXV8ZByjNT/eGFSl5pjmev+M+d0fOmbSXYN1d5BkBXYGOwvYwYgredC7iY7 niigbZHtrQmDXiHnVfZv+Tb1FT13hzUJZ9wugLHil8t06CPHMV8IS+7ZE5YQPtne6D GMYanFtUv2z25PJ/9VDr8DRY/ERx7C5aqKsar7C3X1+GBfq03M8VtQTKv+cR2oTzm5 E+WXuaJYQngoL2cS8Ne4oD8nSnKSCYJAXnC82Cru4OtHH8mUEHmu26a/DVtvkqPMGt oaWNWNhK1f98iyQ1yh0ZEUfb1UGxBtPpLPBKdry8v0xH1WtpYrzXtNMRCcgXeLzas4 B8yD9JeeFX0NA==
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/9Jep3wE3N7l_7yvF2PuThBxbtkU
Subject: Re: [rtcweb] Notes from Data discussion today - DCEP MTI?
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Mar 2014 15:58:18 -0000

On 3/4/14 11:32 AM, Cullen Jennings wrote:

> Issue #8
> - The transports documents should make the DCEP  be MTI
> - The data channel draft will not require implementation of DCEP

It isn't hugely important to me which document the MTI is in.
(I do care for clarity, but not as far as substance.)

What *is* important to me is what the definition of "webrtc-datachannel" 
is, in the registry defined by draft-ietf-mmusic-sctp-sdp-06. (I can't 
find anything that does the definition.)

If it says DCEP is MTI then I'm ok. If it doesn't then I think there is 
a problem.

	Thanks,
	Paul