Re: [bfcpbis] Spencer Dawkins' Yes on draft-ietf-bfcpbis-bfcp-websocket-13: (with COMMENT)
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 02 February 2017 14:28 UTC
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57667129470; Thu, 2 Feb 2017 06:28:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TWyU8hn9dB2n; Thu, 2 Feb 2017 06:28:20 -0800 (PST)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC07F129430; Thu, 2 Feb 2017 06:28:19 -0800 (PST)
Received: by mail-yw0-x231.google.com with SMTP id v200so11359540ywc.3; Thu, 02 Feb 2017 06:28:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=FeReLYHQH/m+QXqan9BHHtsuYXa2VYfAkDIlqF7hxbo=; b=By3JrtL5+7XqetUm5Gdfeqf/aSXIAITlwAAerKtHTlJdzbR0hOGh6tU2VdmVVTPlUa nmfwSF1W/uX6Sa/i/CbJzGLcdRivQgnoyDkB5zZNBBXWLq37byC55FAYk3Kx/aqRn4KH rmsVFsPkHAX0g5MdKdSNsUzj8aGqU2kIkNu0K7ql7X4lGXLELs5ru4A6DJ4tmVfyTvSV 1jgl8ouQfOg5madXD0RVlWe/MbUOfn7R+9ZpaCV/pXLJaq5dnsnrVRbo3r2TDipuPNHq 06SrV4/SVI7jz67yOx8gzptbNqHkhVRRPh7O3rw7kjhreNbC8c/RfEiIgcKUU4EIsyRg y0mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=FeReLYHQH/m+QXqan9BHHtsuYXa2VYfAkDIlqF7hxbo=; b=pLI0bt2H2Vk0HOWQoO8lUbfDpXhIoBZdrd9Xnn6Y5djMXaypsI2mXoZdnCvz73EQ+h 2hrurC/kKoRHvU8d+ybQ9dy0Vri/ZJknkWxS006HfDldUhE0M3tUsrJiKzjM1ip17PyM lE/sf84vsfXeyH8Sge649yC5PNdOaTiWVZvE9gy2s0B59fFrqe6GTQCYAQi2ZrlDhTyb ZJT254r1U9r01MFVM/KdEKWobYqk6r3joYCNZTXBr/x/h25UXDcu6RdP4dW/mkY0H5M0 YF++fs8C6bZtmoSBbSc1vWMlwYFyFao+oRvT/t+qUgnrO5dcLfC4zEPFMaMPog4+d7wL p8WQ==
X-Gm-Message-State: AIkVDXIlFH1f2hcFHhAVoGVpA5P/hpcEELruHi7i2LGJSloa7ivOQd2qFeZDCbRNh9B4Mm8/lj8GXj5HIgkeag==
X-Received: by 10.129.137.6 with SMTP id z6mr5638991ywf.19.1486045698939; Thu, 02 Feb 2017 06:28:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.221.132 with HTTP; Thu, 2 Feb 2017 06:28:18 -0800 (PST)
In-Reply-To: <616B68FF-11A7-49D4-BB60-121A2A5C786A@cisco.com>
References: <148466803770.32051.5938243863646069856.idtracker@ietfa.amsl.com> <616B68FF-11A7-49D4-BB60-121A2A5C786A@cisco.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 02 Feb 2017 23:28:18 +0900
Message-ID: <CAKKJt-dSFzv_DWJ83wa0e=hV06rVxVsqgwEZZsX=8hot_w5NjQ@mail.gmail.com>
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
Content-Type: multipart/alternative; boundary="94eb2c06a7ae01633905478cfae2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/E-E758JZETtPF-iBNet2ITosF_k>
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>, "bfcpbis-chairs@ietf.org" <bfcpbis-chairs@ietf.org>, "draft-ietf-bfcpbis-bfcp-websocket@ietf.org" <draft-ietf-bfcpbis-bfcp-websocket@ietf.org>, The IESG <iesg@ietf.org>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
Subject: Re: [bfcpbis] Spencer Dawkins' Yes on draft-ietf-bfcpbis-bfcp-websocket-13: (with COMMENT)
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bfcpbis/>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 14:28:22 -0000
Hi, Ram, On Mon, Jan 30, 2017 at 8:24 PM, Ram Mohan R (rmohanr) <rmohanr@cisco.com> wrote: > Hi Spencer, > > Thanks for your feedback. Please see inline <Ram> > > -----Original Message----- > From: Spencer Dawkins <spencerdawkins.ietf@gmail.com> > Date: Tuesday, 17 January 2017 at 9:17 PM > To: The IESG <iesg@ietf.org> > Cc: "draft-ietf-bfcpbis-bfcp-websocket@ietf.org" <draft-ietf-bfcpbis-bfcp- > websocket@ietf.org>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, " > bfcpbis-chairs@ietf.org" <bfcpbis-chairs@ietf.org>, "Charles Eckel > (eckelcu)" <eckelcu@cisco.com>, "bfcpbis@ietf.org" <bfcpbis@ietf.org> > Subject: Spencer Dawkins' Yes on draft-ietf-bfcpbis-bfcp-websocket-13: > (with COMMENT) > Resent-From: <alias-bounces@ietf.org> > Resent-To: <anton.roman@quobis.com>, <stephane.cazeaux@orange.com>, < > gsalguei@cisco.com>, <sergio.garcia.murillo@gmail.com>, <rmohanr@cisco.com>, > <victor.pascual.avila@oracle.com> > Resent-Date: Tuesday, 17 January 2017 at 9:17 PM > > Spencer Dawkins has entered the following ballot position for > draft-ietf-bfcpbis-bfcp-websocket-13: Yes > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria. > html > for more information about IESG DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-bfcpbis-bfcp-websocket/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > I have a couple of questions on authentication in this draft. > > Does this text, > > Since the WebSocket API does not distinguish between certificate > errors and other kinds of failure to establish a connection, it > is > expected that browser vendors will warn end users directly of any > kind of problem with the server certificate. > > apply to any WebSocket-based application? > > <Ram> Yes. This is nothing specific to BFCP over webSocket. I think > perhaps this text is not a right fit for this document. I do see RFC6455 > (like in section 7.1.7) already talk about webSocket API and at certain > places on indicating failures to users. I will remove this text from this > spec. > > In this text, > > A floor control server that receives a message over TCP/WS can > request the use of TCP/WSS by generating an Error message, as > described in Section 13.8 of [I-D.ietf-bfcpbis-rfc4582bis], with an > Error code with a value of 9 (use TLS). > > is "request" the right word? Or is "require" more accurate, if the > server > isn't going to establish a TCP/WS connection? > > <Ram> I think requires is appropriate here. I will re-word the text to: > > NEW: > A floor control server that receives a message over TCP/WS can > mandate the use of TCP/WSS by generating an Error message, as > described in Section 13.8 of [I-D.ietf-bfcpbis-rfc4582bis], with an > Error code with a value of 9 (use TLS). > > Is the above ok ? Both resolutions work for me (but do the right thing!). Spencer
- [bfcpbis] Spencer Dawkins' Yes on draft-ietf-bfcp… Spencer Dawkins
- Re: [bfcpbis] Spencer Dawkins' Yes on draft-ietf-… Ram Mohan R (rmohanr)
- Re: [bfcpbis] Spencer Dawkins' Yes on draft-ietf-… Spencer Dawkins at IETF