IETF Logo Mail Archive

Re: [bfcpbis] Alexey Melnikov's Discuss on draft-ietf-bfcpbis-sdp-ws-uri-08: (with DISCUSS and COMMENT)

"Ram Mohan R (rmohanr)" <rmohanr@cisco.com> Thu, 19 January 2017 14:18 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 EC0F21295F7; Thu, 19 Jan 2017 06:18:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.721
X-Spam-Level:
X-Spam-Status: No, score=-17.721 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, 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 vK5dFCyeYIUh; Thu, 19 Jan 2017 06:18:41 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3806C1295F5; Thu, 19 Jan 2017 06:18:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2468; q=dns/txt; s=iport; t=1484835521; x=1486045121; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=WoxdfedQpzGsyLbz8blcqAAHODvcbSImjuRYDTdDTfs=; b=PwPVVkiJkdc47892O5n42+Cd97YacJveZOOoTLccpKepCyUn9Uw9kFb3 lyth76U0PcY3IMI/XhFp9x3KdOPcCcwx4vlgVuBSl6GgsThszo5mYcXI0 PyiZ1p7nzKvDu5DB+2Mh9W9PnlZdS7BA8dLWvTRYsEcv49Zs171pv2rDQ o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CXAQCyyYBY/5JdJa1VCRkBAQEBAQEBAQEBAQcBAQEBAYM/AQEBAQEfgWkHg0qKCJFkH5Mdgg+CDIYiAhqBZD8YAQIBAQEBAQEBYyiEaQEBAQMBIxFFDAQCAQgOAwMBAgECAh8HAgICMBUICAIEAQ0FiHsIr2yCJYo/AQEBAQEBAQEBAQEBAQEBAQEBAQEBHYELh0UIgmGEIhEWBzOCTC2CMQEEm0QBkWQKgW2FD4lokm8BHziBRhVKAYRegUhziFeBDQEBAQ
X-IronPort-AV: E=Sophos;i="5.33,254,1477958400"; d="scan'208";a="197089096"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Jan 2017 14:18:40 +0000
Received: from XCH-RTP-016.cisco.com (xch-rtp-016.cisco.com [64.101.220.156]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v0JEIe20004296 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 19 Jan 2017 14:18:40 GMT
Received: from xch-rtp-017.cisco.com (64.101.220.157) by XCH-RTP-016.cisco.com (64.101.220.156) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 19 Jan 2017 09:18:39 -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; Thu, 19 Jan 2017 09:18:39 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>, The IESG <iesg@ietf.org>
Thread-Topic: [bfcpbis] Alexey Melnikov's Discuss on draft-ietf-bfcpbis-sdp-ws-uri-08: (with DISCUSS and COMMENT)
Thread-Index: AQHSbeseZdw0JJoDs02EXfYysuX0qaE7UlwAgATeqwCAAGECAA==
Date: Thu, 19 Jan 2017 14:18:38 +0000
Message-ID: <E847AE5D-18C9-4979-B308-D493EFD5A453@cisco.com>
References: <148434596441.9752.6696571117558965561.idtracker@ietfa.amsl.com> <CC88E0DB-1B9A-4565-BC9B-724ADFC94B75@cisco.com> <1484834486.429378.852857416.0FD086B0@webmail.messagingengine.com>
In-Reply-To: <1484834486.429378.852857416.0FD086B0@webmail.messagingengine.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.65.37.142]
Content-Type: text/plain; charset="utf-8"
Content-ID: <41AE2CDFFF3AFA4684B1E3E1B330DBA9@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/0CLyodlA0GLgvekw_a-fRXPcKNI>
Cc: "draft-ietf-bfcpbis-sdp-ws-uri@ietf.org" <draft-ietf-bfcpbis-sdp-ws-uri@ietf.org>, "bfcpbis@ietf.org" <bfcpbis@ietf.org>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "bfcpbis-chairs@ietf.org" <bfcpbis-chairs@ietf.org>
Subject: Re: [bfcpbis] Alexey Melnikov's Discuss on draft-ietf-bfcpbis-sdp-ws-uri-08: (with DISCUSS and 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, 19 Jan 2017 14:18:43 -0000

Hi Alexy,

I will incorporate the below suggestion from you. 

Thanks,
Ram

-----Original Message-----
From: Alexey Melnikov <aamelnikov@fastmail.fm>
Date: Thursday, 19 January 2017 at 7:31 PM
To: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>, The IESG <iesg@ietf.org>
Cc: "draft-ietf-bfcpbis-sdp-ws-uri@ietf.org" <draft-ietf-bfcpbis-sdp-ws-uri@ietf.org>, "bfcpbis@ietf.org" <bfcpbis@ietf.org>, "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "bfcpbis-chairs@ietf.org" <bfcpbis-chairs@ietf.org>
Subject: Re: [bfcpbis] Alexey Melnikov's Discuss on draft-ietf-bfcpbis-sdp-ws-uri-08: (with DISCUSS and COMMENT)

    Hi Ram,
    
    On Mon, Jan 16, 2017, at 06:09 AM, Ram Mohan R (rmohanr) wrote:
    > Hi Alexey,
    > 
    > Thanks for your feedback. Please see inline <Ram>
    
    >     2) In Section 6: how is Websocket TLS server identity verified?
    >     
    >  [rfc7525] which is referred in this draft has some text (in Section 6)
    >  on how server certs can be verified. Do you see a need to anything
    >  specific in this draft?
    
    As hostname verification is often omitted in naive implementations, I
    would rather this was called out explicitly. For example:
    
    6.  Security Considerations
    
       The WebSocket clients have to initiate the TCP connection to the
       WebSocket server identified by the FQDN in a=ws/a=wss-uri.  Further
       as with any other web connection, the clients will verify the servers
       certificate.  The WebSocket client MUST follow the procedures in
       [RFC7525] while setting up TLS connection with webSocket server.
    
    I would insert "(including hostname verification as per section 6.1 in
    [RFC7525])" after "[RFC7525]" above.
    
    Best Regards,
    Alexey

v2.23.0 | Report a Bug | By Email