[sipcore] Open isues in draft-ietf-sipcore-sip-websocket-09

Iñaki Baz Castillo <ibc@aliax.net> Fri, 14 June 2013 07:59 UTC

Return-Path: <ibc@aliax.net>
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 E20EE21F9C48 for <sipcore@ietfa.amsl.com>; Fri, 14 Jun 2013 00:59:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.578
X-Spam-Level:
X-Spam-Status: No, score=-1.578 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, 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 MXinefRw+u7H for <sipcore@ietfa.amsl.com>; Fri, 14 Jun 2013 00:59:24 -0700 (PDT)
Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 64E2021F9C37 for <sipcore@ietf.org>; Fri, 14 Jun 2013 00:59:24 -0700 (PDT)
Received: by mail-qa0-f48.google.com with SMTP id cm16so6266qab.0 for <sipcore@ietf.org>; Fri, 14 Jun 2013 00:59:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding:x-gm-message-state; bh=Hz2rVT5oEBmHIQ+g6OTEdYY5zdksKiZqpGvkXNGy0S8=; b=QrBSf+RBKGnNMQLrzvhuk0JzQSe1Wu4IYK8E3HMQUwj3QommpNllp5EeV1yd3/Y1lY oby0Y8FsGXfoPiquiOoMqPzsGZdhwsC+Ldy7jVL5PC0EoOOZrgsqGj1VF5erMT0eXws5 orC/WpgsEUg66lZrbCKlPcFzN9Tu9doVv5zb5Rv3NY8dGPThvjZi53NK4tXxkvwMeFLK UHZuZVoDeoadPPxcPLhMn3uTeWbFlQ0lqqVd8v3kiz0u7CKlZbaW4oGoGrhkoMLkREce UL+c+DKyOVogNGzoGQ0A7g51pcsGh3P9lm73G8Q0WRWtquQj733254c1YW5uS87TliL9 4otQ==
X-Received: by 10.49.81.244 with SMTP id d20mr1155628qey.33.1371196763687; Fri, 14 Jun 2013 00:59:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.67.65 with HTTP; Fri, 14 Jun 2013 00:59:03 -0700 (PDT)
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Fri, 14 Jun 2013 09:59:03 +0200
Message-ID: <CALiegfmtohM8Nnf34o2EqMr-jV-LaQBP7mOB5qq+7OcQO9FkSA@mail.gmail.com>
To: "SIPCORE (Session Initiation Protocol Core) WG" <sipcore@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQn3Mu0zH0IgP9uYNE4pZO2BSpfcobfZhfl/jj42X2kDuRNWO+jlkPxO7/6TIi0J7O26v6ve
Subject: [sipcore] Open isues 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: Fri, 14 Jun 2013 07:59:25 -0000

Hi all,

Once  draft-ietf-sipcore-sip-websocket-09 has been submitted, and
after some comments in the WG, I consider that there are still the
following open issues (to be addressed in a new revision):



1) Remove "_This section is non-normative_" text at the top of
non-normative sections.

Those sections don't contain normative keywords (MUST, SHOULD) so they
are indeed non-normative. No need for such an statement.




2 Decide whether the draft updates 3261 or not.

After recent discussion in the WG my opinion is that if somebody wants
to build a SIP UDP and/or TCP device during 2013 year, he does not
need to read draft-ietf-sipcore-sip-websocket, and thus the draft does
not update RFC 3261.

The other point of view is that the draft makes implementation of both
UDP and TCP transports non mandatory if WS is implemented. This opens
the door to two solutions:

a) Stating that in the draft (as currently it does).

b) A new WG item for allowing other transports without requiring UDP/TCP.





In draft-ietf-sipcore-sip-websocket-09 we have tryed to address all
the other open issues reported by members of the WG after 08 was
published. I hope changes and additions in 09 satisfy their concerns.
Otherwise please let us know and we will address them in rev 10.



Thanks a lot to all.



--
Iñaki Baz Castillo
<ibc@aliax.net>