IETF Logo Mail Archive

Re: [rtcweb] Agenda requests for Atlanta meeting

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 09 October 2012 06:28 UTC

Return-Path: <christer.holmberg@ericsson.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 4626B21F84F9 for <rtcweb@ietfa.amsl.com>; Mon, 8 Oct 2012 23:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.126
X-Spam-Level:
X-Spam-Status: No, score=-6.126 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T6xTQ+rrL1jB for <rtcweb@ietfa.amsl.com>; Mon, 8 Oct 2012 23:28:42 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 11C5721F849A for <rtcweb@ietf.org>; Mon, 8 Oct 2012 23:28:41 -0700 (PDT)
X-AuditID: c1b4fb2d-b7fea6d000002ccb-ca-5073c418dbf0
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 90.1B.11467.814C3705; Tue, 9 Oct 2012 08:28:41 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.243]) by esessmw0184.eemea.ericsson.se ([10.2.3.53]) with mapi; Tue, 9 Oct 2012 08:28:40 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Date: Tue, 09 Oct 2012 08:28:39 +0200
Thread-Topic: [rtcweb] Agenda requests for Atlanta meeting
Thread-Index: Ac2lqN/V0WBQ/IXCSdqzySCpE8ZrOgAPjxBA
Message-ID: <7F2072F1E0DE894DA4B517B93C6A0585340BAD0867@ESESSCMS0356.eemea.ericsson.se>
References: <506B0367.4000103@ericsson.com> <C5E08FE080ACFD4DAE31E4BDBF944EB111867718@xmb-aln-x02.cisco.com> <7F2072F1E0DE894DA4B517B93C6A0585340BAD03A6@ESESSCMS0356.eemea.ericsson.se> <C5E08FE080ACFD4DAE31E4BDBF944EB11187F8F1@xmb-aln-x02.cisco.com> <CABcZeBP0Ura+QgtzfAyydMMb+aopOYu-xoGoVB0Gt5M0adMvvg@mail.gmail.com>
In-Reply-To: <CABcZeBP0Ura+QgtzfAyydMMb+aopOYu-xoGoVB0Gt5M0adMvvg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrALMWRmVeSWpSXmKPExsUyM+Jvra7kkeIAg7t1Fiten2O36JjMZrH2 Xzu7A7PHlN8bWT2WLPnJ5DH5cRtzAHMUl01Kak5mWWqRvl0CV8bvNX/ZC6awVXzZsYu5gfEt SxcjJ4eEgInEoemfmSFsMYkL99azdTFycQgJnGKU+PBqLQuEM4dRoq1nF2sXIwcHm4CFRPc/ bZAGEYFAiakTJoMNYhZQl7iz+Bw7iM0ioCLx8d1sMFtYwFJi0eb9bBD1VhJrbl1nhrCNJKZO eQoW5xUIl7iw8TgTxK5jTBKXP08E28UJtODFPCaQGkag476fWsMEsUtc4taT+UwQRwtILNlz HuoBUYmXj/+xQtSLStxpX88IUa8jsWD3JzYIW1ti2cLXzBB7BSVOznzCMoFRbBaSsbOQtMxC 0jILScsCRpZVjMK5iZk56eWGeqlFmcnFxfl5esWpmxiBsXRwy2/dHYynzokcYpTmYFES5+VK 2u8vJJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgVFm9fqZ+e2O7ecy+MJim7Z4CD+ynOTY3829 r4jvxYE7i/sfKxk7zdPdJ2v5Mf1M9Z8fEziPSUv+/mPecOfvkflv5l7Y7mSs8MAhKIXJ5GNB I4vyc8m/IaKbVga37om+YF/Syvv+sSPDLet7HVMN5ufe096leypI43a+7JkLf58rHmQXKxOV /qPEUpyRaKjFXFScCAB7bGzAcwIAAA==
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Agenda requests for Atlanta meeting
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, 09 Oct 2012 06:28:43 -0000

Hi Ekr,

>I would attend such a phone call if it were held.
>
>My immediate reaction is that from an implementor's perspective. PRANSWER is a lot easier to address than cloning. I feel like cloning pulls in a lot of difficult lifetime and ownership semantics. By contrast, supporting PRANSWER is very easy. Before >deciding that cloning is the answer I'd like to see two
>things:
>
>1. A clear set of use cases that shows what cloning does well that PRANSWER does not.
>2. A fairly complete defn of the clone semantics.
>
>Otherwise I worry that we'll detour to cloning and then only after 6 months discover it doesn't work.

Please note that JSEP-02 already supports cloning (the details on how it's done are missing, though).

Regards,

Christer

v2.23.0 | Report a Bug | By Email