IETF Logo Mail Archive

Re: [sipcore] Open issues in draft-ietf-sipcore-sip-websocket-09

Michael Procter <michael@voip.co.uk> Thu, 27 June 2013 13:57 UTC

Return-Path: <michael@voip.co.uk>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEE6621F9997 for <sipcore@ietfa.amsl.com>; Thu, 27 Jun 2013 06:57:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.977
X-Spam-Level:
X-Spam-Status: No, score=-5.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
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 G1nRxLcJTc8g for <sipcore@ietfa.amsl.com>; Thu, 27 Jun 2013 06:57:10 -0700 (PDT)
Received: from na3sys009aog120.obsmtp.com (na3sys009aog120.obsmtp.com [74.125.149.140]) by ietfa.amsl.com (Postfix) with SMTP id B272021F9D89 for <sipcore@ietf.org>; Thu, 27 Jun 2013 06:57:09 -0700 (PDT)
Received: from mail-wi0-f182.google.com ([209.85.212.182]) (using TLSv1) by na3sys009aob120.postini.com ([74.125.148.12]) with SMTP ID DSNKUcxEtT2STMTdcYG9LTMqggCaE4idbAH7@postini.com; Thu, 27 Jun 2013 06:57:09 PDT
Received: by mail-wi0-f182.google.com with SMTP id m6so652525wiv.15 for <sipcore@ietf.org>; Thu, 27 Jun 2013 06:57:08 -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:content-transfer-encoding:x-gm-message-state; bh=5T8byCQc/S3sjltiz1ei9POXZg1YkW2ilAGAqpZDZOc=; b=brIz9o6EkG8S5qIc4hB67ibUOxdFrROLTg/EBKUC86M3oG1ZBUHlt4iUzTeFSI4UfT c8H7o0/zQsVJRkbuIObFySqkJJL2v4UotJeCEcEOgbx0joVWOJsSe9AIUiu2AsQo9BD9 2sCSKOnhg1eH3H1yS70FlXw26hWUZjDGELRI1l5Lyin6oSI2ffCHClqI5FcXsVCWQ8Tb TjnJ8HT0uQaCI6NaS2NEtgmNSpxpjUvDUCHUmy/6QipPPmh3sxHKkAGSNXW+R100lJSi bPCc94+AXqtYCeApafM/QDG1Kszhv2ilHrVjqS36j1WQDrWUsbU8ihIsmJS7WURYAF+Q MqJw==
X-Received: by 10.194.240.201 with SMTP id wc9mr6569111wjc.1.1372341428030; Thu, 27 Jun 2013 06:57:08 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.240.201 with SMTP id wc9mr6569108wjc.1.1372341427961; Thu, 27 Jun 2013 06:57:07 -0700 (PDT)
Received: by 10.194.164.234 with HTTP; Thu, 27 Jun 2013 06:57:07 -0700 (PDT)
In-Reply-To: <51CB0532.3020107@alum.mit.edu>
References: <CALiegfmtohM8Nnf34o2EqMr-jV-LaQBP7mOB5qq+7OcQO9FkSA@mail.gmail.com> <003f01ce6aaf$aabda760$0038f620$@co.in> <CALiegfn=KrEsOT+HGkCpfkS3C7Tc0Jko6kautCHk3sP8zHrzVw@mail.gmail.com> <011e01ce6c44$3c70e290$b552a7b0$@co.in> <CALiegfnPeFf751QHLoeT_jO0u1LROtvkqseE7QcAZvLgSiqVZQ@mail.gmail.com> <E54AEADE791D51469F45E7FBB964391505C964@SGSIMBX001.nsn-intra.net> <019a01ce6d24$8ee95670$acbc0350$@co.in> <CALiegfkFVJgNNLJat+3v4JqXz_=OwLPTDtR6J55dRLmiH8OgFg@mail.gmail.com> <51C3267F.8040709@alum.mit.edu> <002301ce713c$c2672880$47357980$@co.in> <51CB0532.3020107@alum.mit.edu>
Date: Thu, 27 Jun 2013 14:57:07 +0100
Message-ID: <CAPms+wSKhMf9XEnNJpSnQ+w-pbTPE7oQtkESrUpvrcvHTZ_OOw@mail.gmail.com>
From: Michael Procter <michael@voip.co.uk>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnATHs6MBas1hyowwNJMXWra80JLJZ1+Pv1VHPWVsq+TkPTeMYxlXflrh3uMRP6EaxWcdS7usHy21Ny581RaQsXNFgxi4IMPajwTPDEnp3LT1p0Uh6xwaGgkIg5q4Dau9hTImhNnWkIntb9QLnmqom5LVQrHQ==
Cc: sipcore@ietf.org
Subject: Re: [sipcore] Open issues in draft-ietf-sipcore-sip-websocket-09
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2013 13:57:16 -0000

On 26 June 2013 16:13, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> The real issue is: how can a websocket server ever decide that it *doesn't*
> need to R-R?

The websocket server shouldn't R-R a request if it is a non-dialog-establishing
request (e.g. REGISTER, PUBLISH) or an in-dialog non-target-refresh request
(e.g. INFO).  It is probably fair to say that INVITEs should be, but
that specific
case is already covered by RFC5626, as Iñaki has pointed out.

Regards,

Michael

v2.23.0 | Report a Bug | By Email