IETF Logo Mail Archive

Re: [bfcpbis] Spencer Dawkins' Yes on draft-ietf-bfcpbis-bfcp-websocket-13: (with COMMENT)

"Ram Mohan R (rmohanr)" <rmohanr@cisco.com> Mon, 30 January 2017 11:24 UTC

Return-Path: <rmohanr@cisco.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 B2326129450; Mon, 30 Jan 2017 03:24:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.72
X-Spam-Level:
X-Spam-Status: No, score=-17.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 5HjRS0CYmBX4; Mon, 30 Jan 2017 03:24:51 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0830312944A; Mon, 30 Jan 2017 03:24:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4460; q=dns/txt; s=iport; t=1485775491; x=1486985091; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=cr7kXSr+3xcSxT30nC8lGX6wsdQJkBK9fe/NHpz6arI=; b=JGiT2xpVIg3DC05U1c2YGx256uq1z0Ws4HYThLSj3zYafNxXtuJRajpk ScQpTbFIHdxTLbPuP9dHfFWVXKSa1FN+3tLAkS44xcTJI/e71tSDQXU6u yQ+juO0NPqKmb2qmaZttySxr8kB3jxoh32XK+gGV3dC2WsdjuaYTlhKr4 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BQAQBqIY9Y/5RdJa1dGQEBAQEBAQEBAQEBBwEBAQEBg1NhgQkHg06KCZIBiAmLGoIPggwqhXgCGoF2PxgBAgEBAQEBAQFiKIRpAQEBBCMREzIMBAIBCBEDAQIDAiYCAgIfERUICAIEAQ0FiUkDGA6rFIIlgz6Daw2DOgEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgQuHRYJqglGBShEBBhYHMQKCTC6CMQWJApIaOAGGZocDhBGBeYUViWmKJ4hXAR84dlUVSwGEYIFIdQGGBIEhgQwBAQE
X-IronPort-AV: E=Sophos;i="5.33,311,1477958400"; d="scan'208";a="379028910"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Jan 2017 11:24:50 +0000
Received: from XCH-RTP-020.cisco.com (xch-rtp-020.cisco.com [64.101.220.160]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v0UBOn3k006492 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 30 Jan 2017 11:24:50 GMT
Received: from xch-rtp-017.cisco.com (64.101.220.157) by XCH-RTP-020.cisco.com (64.101.220.160) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 30 Jan 2017 06:24:48 -0500
Received: from xch-rtp-017.cisco.com ([64.101.220.157]) by XCH-RTP-017.cisco.com ([64.101.220.157]) with mapi id 15.00.1210.000; Mon, 30 Jan 2017 06:24:49 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>, The IESG <iesg@ietf.org>
Thread-Topic: Spencer Dawkins' Yes on draft-ietf-bfcpbis-bfcp-websocket-13: (with COMMENT)
Thread-Index: AQHScNkACrTHzuLnYUCVszFqszkAeaFRpT4A
Date: Mon, 30 Jan 2017 11:24:48 +0000
Message-ID: <616B68FF-11A7-49D4-BB60-121A2A5C786A@cisco.com>
References: <148466803770.32051.5938243863646069856.idtracker@ietfa.amsl.com>
In-Reply-To: <148466803770.32051.5938243863646069856.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1a.0.160910
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.143.30.47]
Content-Type: text/plain; charset="utf-8"
Content-ID: <D41E15ED01E46D40812B90C1FB21DC74@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/_8_ATNQpt5NKdG722_s_aV_EB8k>
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>, "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>
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: Mon, 30 Jan 2017 11:24:53 -0000

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 ?

Regards,
Ram

v2.23.0 | Report a Bug | By Email