IETF Logo Mail Archive

Re: [rtcweb] SDP Offer/Answer draft-jennings-rtcweb-signaling - Scope

Cullen Jennings <fluffy@cisco.com> Tue, 18 October 2011 19:02 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 8D21D21F8C9C for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 12:02:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.539
X-Spam-Level:
X-Spam-Status: No, score=-106.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 qHJG5GPamKs8 for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 12:02:24 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id E0EA321F8C9A for <rtcweb@ietf.org>; Tue, 18 Oct 2011 12:02:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=566; q=dns/txt; s=iport; t=1318964544; x=1320174144; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=AxzQC77kmdcnPbDFsK4iouHPpLJBD8wN1jIeZSK4PrU=; b=Miwdy6hfqDsFLvdzj5+rzUo8/bscIk1eBsoSuqpEx4PZsl593unTW3te x+XK7KbJ1h1pT3FW01T9bzpPrgI8dkaPlfyt+leMvpuPuCrc9LHPNOV3A NtkRPMaF1Lc5Rf62oRYWPzgxqQP5TYxfoXp/MT8mAjKk/KiBGwSJP/bOP U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAMjLnU6rRDoG/2dsb2JhbABEqG6BBYFuAQEBAwESASc/EAtGVwY1h16XdwGeYoc6YQSIAot7kXY
X-IronPort-AV: E=Sophos;i="4.69,366,1315180800"; d="scan'208";a="8678893"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 18 Oct 2011 19:02:23 +0000
Received: from dhcp-171-70-217-213.cisco.com (dhcp-171-70-217-213.cisco.com [171.70.217.213]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p9IJ2NOC016965; Tue, 18 Oct 2011 19:02:23 GMT
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset="us-ascii"
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A058522341F416A@ESESSCMS0356.eemea.ericsson.se>
Date: Tue, 18 Oct 2011 12:02:21 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <10704DBF-9400-42BA-B9C5-209C338F042E@cisco.com>
References: <15B0E3AD-3086-499A-8E79-7AE58B3376C4@cisco.com> <2E239D6FCD033C4BAF15F386A979BF51159957@sonusinmail02.sonusnet.com> <CALiegfnGfpWooceicAbLQ35oVDUZC6+d=903qSKkxW952i-8pw@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A058522341F416A@ESESSCMS0356.eemea.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: Jonathan Rosenberg <jonathan.rosenberg@skype.net>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: [rtcweb] SDP Offer/Answer draft-jennings-rtcweb-signaling - Scope
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: Tue, 18 Oct 2011 19:02:25 -0000

On Oct 18, 2011, at 3:18 , Christer Holmberg wrote:

> 
> So, while I support and offer/answer based approach, I think we need to get a clearer understanding of the scope.

My view is this is draft is a set of semantics and syntax that operates over an abstract transport protocol. In most cases the transport with be web sockets or HTTP based. If this looks like a reasonable protocol, it would be likely to influence the W3C API. I'm not really sure how to clear up the scope. I'm just not sure what the scope is I need to clear up.

v2.23.0 | Report a Bug | By Email