Re: [rtcweb] Fwd: New Version Notification for draft-uberti-rtcweb-turn-rest-00.txt

Martin Thomson <martin.thomson@gmail.com> Mon, 08 July 2013 22:30 UTC

Return-Path: <martin.thomson@gmail.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 042BF21F9AAE for <rtcweb@ietfa.amsl.com>; Mon, 8 Jul 2013 15:30:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.433
X-Spam-Level:
X-Spam-Status: No, score=-2.433 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 svZUSfjxk5f3 for <rtcweb@ietfa.amsl.com>; Mon, 8 Jul 2013 15:30:33 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 3382321F9A3C for <rtcweb@ietf.org>; Mon, 8 Jul 2013 15:30:33 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id l18so4215395wgh.14 for <rtcweb@ietf.org>; Mon, 08 Jul 2013 15:30:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=A8eH8/aK3T4xvnbLeHff86CAZ8r0aON9ICVf2uHKH3M=; b=w4Ei3sT8kVm4Mm5GWF/A9ATyzqN+EYwNPPtMoN3gP/+Zcgo9WFHOjIm4BpUpmiUNe+ Jhjt8JyWxnADZgdbmmGTKOPuWOkJePoNGlrz0Kijt4P/cqXpNinEEJ1St0/vHnJf/NfQ rkL4XUsrcfOnn4T5jzDBrnjQjBxK0a6pVo/bE/hfkevanosTAxLB2BZ5E5TR9jw3clkp cLtLDOXfLpUBvdjVWMWHkfITuMFqHK5FVdNoazSQucJfMaidigEizAa227ZnOr1tzyfe hBEMYkOZyw3SXLsiwTncahPz+a39Iz23eF/QF/+OT+H+Y3bwjgsarR4aAGIvEfKn2wvL 1rBA==
MIME-Version: 1.0
X-Received: by 10.194.77.99 with SMTP id r3mr13478131wjw.5.1373322632376; Mon, 08 Jul 2013 15:30:32 -0700 (PDT)
Received: by 10.194.60.46 with HTTP; Mon, 8 Jul 2013 15:30:32 -0700 (PDT)
In-Reply-To: <51DB37C5.3060701@nostrum.com>
References: <20130708041540.7930.93762.idtracker@ietfa.amsl.com> <CALe60zAs-NCJgiiHuFHi1ZEOdp2SB4v2-0AYrxBQ2R_gJ=nLcA@mail.gmail.com> <CAOJ7v-0Vxkf-4j-ZHCisKuORob_cL3ogXoexTFMDMJDEttRbaQ@mail.gmail.com> <51DB3443.6070301@nostrum.com> <CABkgnnUqpUp7bBjZw9nGi-zJJF4AC61LFmOvKKjZO=qH_1QzrA@mail.gmail.com> <51DB37C5.3060701@nostrum.com>
Date: Mon, 8 Jul 2013 15:30:32 -0700
Message-ID: <CABkgnnU044uSZM5A-fVdAN2KatndPzb_cS9gwrjH520msOY+JQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Adam Roach <adam@nostrum.com>
Content-Type: text/plain; charset=UTF-8
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Fwd: New Version Notification for draft-uberti-rtcweb-turn-rest-00.txt
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: Mon, 08 Jul 2013 22:30:34 -0000

On 8 July 2013 15:05, Adam Roach <adam@nostrum.com> wrote:
>> But it's equally valid to try to pretend otherwise and use GET.  After
>> all, most servers won't actually be allocating any state for these
>> things.
>
> I hope none of them do. It's kind of the main point of the whole draft.

I expect all of them to do so, but not hold clients responsible for
that, so GET is still OK.

>> p.s., I was going to let this slide, but this design is not RESTful,
>> no sense in pretending like it is.
>
> I'm not sure I agree with your assessment. Which of these six constraints do
> you believe are violated?
>
> http://en.wikipedia.org/wiki/Representational_state_transfer#Constraints

Will you think worse of me if I avoid opening this particular can of
worms?  I regret even mentioning it.

I've learned not to use the term RESTful, I should have known better.