Re: [rtcweb] #13: Transport of DATA_CHANNEL_OPEN

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Thu, 25 April 2013 21:10 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3FD21F96CC for <rtcweb@ietfa.amsl.com>; Thu, 25 Apr 2013 14:10:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108
X-Spam-Level:
X-Spam-Status: No, score=-108 tagged_above=-999 required=5 tests=[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 cKZYhsFHrwCQ for <rtcweb@ietfa.amsl.com>; Thu, 25 Apr 2013 14:10:05 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 7E12F21F96CA for <rtcweb@ietf.org>; Thu, 25 Apr 2013 14:10:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=563; q=dns/txt; s=iport; t=1366924205; x=1368133805; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=8lSjkPcmDkbhxj2e5QuVDTWjEU5y0V4xBgS7ePYbkWQ=; b=We4aYREsuYK1GjRWdgz0vpvC/Bmotz3pGrl+OBg9gCtNcZp+u6q3HWMI 0esWI9pOMXcfD3RHBys/EV3QTaJOFDl0gVwfyyFCNHy5tWQegYI4yctU2 RbdfM7a/bcllPMwqQBuSn1XxzayBPo1zMpgZeaGTC7Jz5xzEZU9PpmgG4 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AosGAFCaeVGtJXG//2dsb2JhbABRgwaDJrtBgQQWbQeCHwEBAQMBeQULAgEIIiQyJQIEDgUIE4dzBr5TjwICMQeCbWEDoSGHHYMOgig
X-IronPort-AV: E=Sophos;i="4.87,553,1363132800"; d="scan'208";a="203263818"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-4.cisco.com with ESMTP; 25 Apr 2013 21:10:05 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r3PLA5XT022308 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 25 Apr 2013 21:10:05 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.192]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0318.004; Thu, 25 Apr 2013 16:10:04 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] #13: Transport of DATA_CHANNEL_OPEN
Thread-Index: AQHOQflBi1erDoB5e0Kx1cZ1sYRwVA==
Date: Thu, 25 Apr 2013 21:10:04 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB11349F9B5@xmb-aln-x02.cisco.com>
References: <066.3120a55540cacaa74ee5fda0b5273a48@trac.tools.ietf.org> <5174C8D2.40504@matthew.at> <5177F7EE.1010909@matthew.at> <CAJrXDUGa1=Nqq9WPL57=OkUU9mG7yHz0uzG1KncS8yVzbSAM0A@mail.gmail.com> <AE1A6B5FD507DC4FB3C5166F3A05A484162816C1@tk5ex14mbxc272.redmond.corp.microsoft.com>
In-Reply-To: <AE1A6B5FD507DC4FB3C5166F3A05A484162816C1@tk5ex14mbxc272.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <FB72F63AB6AC6D499405137C45B6482C@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [rtcweb] #13: Transport of DATA_CHANNEL_OPEN
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 25 Apr 2013 21:10:06 -0000

So with my co-chair hat on here… 

It seems we have been around the need for OPEN several times and have come to consensus on it in the past. Can someone please:

1) summarize the arguments that in the past that lead us to think we need OPEN 

2) sketch out the range of possible solutions to deal with unexpected data before the OPEN 

Cullen 



On Apr 24, 2013, at 11:28 PM, Matthew Kaufman (SKYPE) <matthew.kaufman@skype.net> wrote:

> I’d still love to hear why it is “needed” though.
>  
> Matthew Kaufman