Re: [rtcweb] Do we still need PRANSWER?

Roman Shpount <roman@telurix.com> Thu, 05 July 2012 17:35 UTC

Return-Path: <roman@telurix.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 C803C21F85AF for <rtcweb@ietfa.amsl.com>; Thu, 5 Jul 2012 10:35:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.946
X-Spam-Level:
X-Spam-Status: No, score=-2.946 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 grMvVv+ULppF for <rtcweb@ietfa.amsl.com>; Thu, 5 Jul 2012 10:35:24 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2EA6F21F85AE for <rtcweb@ietf.org>; Thu, 5 Jul 2012 10:35:24 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so8521336ghb.31 for <rtcweb@ietf.org>; Thu, 05 Jul 2012 10:35:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=GYBR0s/bHIZI0Hkw3RtdWTTy9g599fS6ZJBOkh2ah3g=; b=SU7DLbKn84vLHUbMiwX9L5se8VjCMS/bC/RH0HKk7d6s4NAOGDdYSUh0laARekQ5p+ nsAoRlq14dYJQdtO+QHcriA0uh5fRpEMD//efEjJIH7EpDurhhFyQaEjQRYvvLP31CEw 1G88pOQ97NmWBkWesfQE4sv0/e+PUHJMarIs9QWLanwA85fheE9x1Eb+OsmWaDtbQxWA vg/5tNpHynKBt6SM7ZWIwdTObUm6ESoS0HpXd/uVBGoZuFGALJTX6Ae7Hd+PeKvvYbWr wSVF2VXllVZHj4KHMds/V0AibOCiUbCO0PvBswc+UKVlB1RZPCmV8C95WLEaHW9UmpWi a6SQ==
Received: by 10.236.78.39 with SMTP id f27mr30160472yhe.121.1341509737978; Thu, 05 Jul 2012 10:35:37 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by mx.google.com with ESMTPS id f28sm21889936yhk.2.2012.07.05.10.35.35 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 05 Jul 2012 10:35:37 -0700 (PDT)
Received: by yenq13 with SMTP id q13so8495129yen.31 for <rtcweb@ietf.org>; Thu, 05 Jul 2012 10:35:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.75.162 with SMTP id d2mr38825327paw.59.1341509734841; Thu, 05 Jul 2012 10:35:34 -0700 (PDT)
Received: by 10.68.194.202 with HTTP; Thu, 5 Jul 2012 10:35:34 -0700 (PDT)
In-Reply-To: <CABkgnnUEi9zTCf=LWoKPOTeo47x4Pj=P3_tdM2MhSQtZn1RB6Q@mail.gmail.com>
References: <CAD5OKxui0XeYA8GOnNCkPin_XjOoNvEHeQq1OcmEJ1aYpbF3_A@mail.gmail.com> <CALiegfkJPSj3obFTz0zeF_WZZob1a2eOnMF0ys6QkUxzs6AAEw@mail.gmail.com> <CAD5OKxvqRUuhdfS368_VNS5w6NxChZW=fhYNOHjkJJozXsJ4TA@mail.gmail.com> <CABkgnnUEi9zTCf=LWoKPOTeo47x4Pj=P3_tdM2MhSQtZn1RB6Q@mail.gmail.com>
Date: Thu, 05 Jul 2012 13:35:34 -0400
Message-ID: <CAD5OKxsZRMrgxv=ADvvMvbcth=zDJj9XEcRNP7Y6YyzekZtJig@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary="f46d042dfd71353bbd04c4189391"
X-Gm-Message-State: ALoCoQmpXMV9Y6Hreeu+8eTiy8DvhDTGUsNen8cWl+Sl/1cetLC+5yI+kJpkMuLOUnGFfllc1S7F
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Do we still need PRANSWER?
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, 05 Jul 2012 17:35:24 -0000

On Thu, Jul 5, 2012 at 11:50 AM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 5 July 2012 04:30, Roman Shpount <roman@telurix.com> wrote:
> > This was all written out of frustration mainly by the direction taken by
> > this group on adding things that are not strictly necessary but break
> > interoperability. It is completely incomprehensible to me  why the group
> > decided to add PRANSWER if connection cloning is just as easy to
> implement
> > and would make, on one hand, interop easier, on another hand add
> significant
> > new functionality. When I am saying that connection cloning is easy to
> > implement I mean that I am willing to build a prototype based on chromium
> > code that implements it. Getting the new API through IETF/W3C is above my
> > skill level, since I am fairly bad at writing drafts.
>
> PRANSWER is purely an API construct.  How does that affect
> interoperability other than making it harder to write the browser code
> that achieves it?
>

PRANSWER is an API construct, but it assumes that only serial proxies are
supported. This is an interop issue.
_____________
Roman Shpount