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

Cullen Jennings <fluffy@cisco.com> Thu, 20 October 2011 02:07 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 02DC01F0C5B for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 19:07:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.982
X-Spam-Level:
X-Spam-Status: No, score=-105.982 tagged_above=-999 required=5 tests=[AWL=0.617, 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 RECIJ6DDpdJu for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 19:07:26 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 914FE1F0C44 for <rtcweb@ietf.org>; Wed, 19 Oct 2011 19:07:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=490; q=dns/txt; s=iport; t=1319076446; x=1320286046; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=n1mZrIuQKYSR0rCzckEFRLoFQ+Cij0VLpqaZq4hsaGU=; b=HIHPhIKtRf6vBQHyzN7ctbO+1qehEW56jocZD/beILH5eHNMYelSvR37 s0hianJ/7rqm0jMDXy7TDjGksdVwtlnbfY4tZyoISafFwL3OfZsZI76Mv 6mP2lgQdABczxc/JCyVH3MKPbNNsYhT6bZd6NZsuENf6Qc1Ml6FEkBBut w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAJiBn06rRDoH/2dsb2JhbABEqQOBBYFuAQEBAQMSASc/EAtGVwY1h2aXWAGeToc6YQSIAot8hSqMTA
X-IronPort-AV: E=Sophos;i="4.69,375,1315180800"; d="scan'208";a="9014609"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 20 Oct 2011 02:07:25 +0000
Received: from [192.168.4.100] (sjc-fluffy-8914.cisco.com [10.20.249.165]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p9K27OAL005483; Thu, 20 Oct 2011 02:07:24 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4E9F7182.5000207@acm.org>
Date: Wed, 19 Oct 2011 20:07:24 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <E109D366-3B55-40DA-B8DB-86C17F8D0FAD@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> <10704DBF-9400-42BA-B9C5-209C338F042E@cisco.com> <7F2072F1E0DE894DA4B517B93C6A058522341F4A36@ESESSCMS0356.eemea.ericsson.se> <2F4D4B67-7AE0-4C8F-B390-B043FBA82B76@cisco.com> <4E9F7182.5000207@acm.org>
To: Marc Petit-Huguenin <petithug@acm.org>
X-Mailer: Apple Mail (2.1084)
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: Thu, 20 Oct 2011 02:07:27 -0000

On Oct 19, 2011, at 6:55 PM, Marc Petit-Huguenin wrote:

>> 
>> This whole "is this an API or Protocol discussion" leaves me sort of saying
>> "Yes" but I'm not sure it matters much. Any API can be turned into a protocol
>> using a RPC approach. 
> 
> I disagree here.
> 
> http://labs.oracle.com/techrep/1994/abstract-29.html

Good point and nice paper. Perhaps I should have said an API can be turned into a really bad protocol using an RPC approach :-)