Re: [tram] Alexey Melnikov's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
"Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com> Thu, 01 September 2016 03:48 UTC
Return-Path: <tireddy@cisco.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5E5D12D08F; Wed, 31 Aug 2016 20:48:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.069
X-Spam-Level:
X-Spam-Status: No, score=-15.069 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=-0.548, 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 mAHDVUEfgLrt; Wed, 31 Aug 2016 20:48:33 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C308128B44; Wed, 31 Aug 2016 20:48:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3038; q=dns/txt; s=iport; t=1472701713; x=1473911313; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=tf9pOA3al1fT2LyUCGgPn5DZpxYxbwdgt/pnGIVZhBs=; b=U5axNuJV0lXzoB6oJ6LjxXRJUzCo0UxlgdJxrFN73howL8mNi5dNAQjt GYUAVbGKlPyLSMlvk6DcZzWbh7lXo0f9Dlg0/+CENLWQpCbKMFQeq6Lkc Izkfl5c/wIAm7dTSR+Xo4wZvDKsOHXlyMXRISTGmS8+hvfchm40phiT8n A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AHAgDvo8dX/4sNJK1UCYNQAQEBAQEeV3wHthKCD4IBJIV4AhyBMjgUAQIBAQEBAQEBXieEYQEBBSMRRQwEAgEIDgMEAQEDAiMDAgICMBQBCAgCBAENBQiIQA6uGYxtAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwWBBYUqhE2EEgcKAQaDGIJaBYgthXeLLAGGH4kKgXSEXYkNjEiDeAEeNoJ8gTVwAYQ/DRcHgQJ/AQEB
X-IronPort-AV: E=Sophos;i="5.30,265,1470700800"; d="scan'208";a="317330597"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Sep 2016 03:48:32 +0000
Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u813mWio027782 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 1 Sep 2016 03:48:32 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 31 Aug 2016 22:48:31 -0500
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1210.000; Wed, 31 Aug 2016 22:48:31 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>, The IESG <iesg@ietf.org>
Thread-Topic: Alexey Melnikov's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
Thread-Index: AQHSA54fDJMoqK9Hq0C6sHCN+3QJCaBj/4Yw
Date: Thu, 01 Sep 2016 03:48:31 +0000
Message-ID: <21b2559f2a234c64b47595eb4615c661@XCH-RCD-017.cisco.com>
References: <147265807396.13320.16720268350417791956.idtracker@ietfa.amsl.com>
In-Reply-To: <147265807396.13320.16720268350417791956.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.43.3]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/SqoiDX4xI6Nk3q3ZoGpUgVh__G8>
Cc: "sperreault@jive.com" <sperreault@jive.com>, "draft-ietf-tram-turn-server-discovery@ietf.org" <draft-ietf-tram-turn-server-discovery@ietf.org>, "tram@ietf.org" <tram@ietf.org>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>
Subject: Re: [tram] Alexey Melnikov's Discuss on draft-ietf-tram-turn-server-discovery-09: (with DISCUSS)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Sep 2016 03:48:36 -0000
> -----Original Message----- > From: Alexey Melnikov [mailto:aamelnikov@fastmail.fm] > Sent: Wednesday, August 31, 2016 9:11 PM > To: The IESG <iesg@ietf.org> > Cc: draft-ietf-tram-turn-server-discovery@ietf.org; Simon Perreault > <sperreault@jive.com>; tram-chairs@ietf.org; sperreault@jive.com; > tram@ietf.org > Subject: Alexey Melnikov's Discuss on draft-ietf-tram-turn-server-discovery- > 09: (with DISCUSS) > > Alexey Melnikov has entered the following ballot position for > draft-ietf-tram-turn-server-discovery-09: Discuss > > 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-tram-turn-server-discovery/ > > > > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- > > In Section 9: > > o For certificate-based authentication, a pre-populated trust anchor > store [RFC6024] allows a TURN client to perform path validation > for the server certificate obtained during the (D)TLS handshake. > > If the client used a domain name to discover the TURN server, that > domain name also provides a mechanism for validation of the TURN > server. The client MUST use the rules and guidelines given in > section 6 of [RFC6125] to validate the TURN server identity. > > I am glad that you are referencing RFC 6125, but unfortunately you don't > provide enough details. Please add details as specified in Section 3 of RFC > 6125 to your document. Sure, will add the following lines: Certification authorities that issue TURN server certificates SHOULD support the DNS-ID and SRV-ID identifier types. TURN service providers SHOULD include the DNS-ID and SRV-ID identifier types in certificate requests. -Tiru > > >
- [tram] Alexey Melnikov's Discuss on draft-ietf-tr… Alexey Melnikov
- Re: [tram] Alexey Melnikov's Discuss on draft-iet… Tirumaleswar Reddy (tireddy)
- Re: [tram] Alexey Melnikov's Discuss on draft-iet… Alexey Melnikov
- Re: [tram] Alexey Melnikov's Discuss on draft-iet… Tirumaleswar Reddy (tireddy)
- Re: [tram] Alexey Melnikov's Discuss on draft-iet… Alexey Melnikov
- Re: [tram] Alexey Melnikov's Discuss on draft-iet… Tirumaleswar Reddy (tireddy)
- Re: [tram] Alexey Melnikov's Discuss on draft-iet… Spencer Dawkins at IETF
- [tram] Need to be fixed! Discuss on draft-ietf-tr… Karl Stahl
- Re: [tram] Need to be fixed! Discuss on draft-iet… Karl Stahl
- Re: [tram] Need to be fixed! Discuss on draft-iet… Spencer Dawkins at IETF