IETF Logo Mail Archive

Re: [secdir] Secdir review of draft-hollenbeck-rfc4930bis-02

Alexey Melnikov <alexey.melnikov@isode.com> Wed, 15 July 2009 15:57 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5AF443A69B3; Wed, 15 Jul 2009 08:57:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.502
X-Spam-Level:
X-Spam-Status: No, score=-2.502 tagged_above=-999 required=5 tests=[AWL=0.097, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bisrEAVE5gCQ; Wed, 15 Jul 2009 08:57:58 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 61D6C3A6947; Wed, 15 Jul 2009 08:57:58 -0700 (PDT)
Received: from [172.16.2.160] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <Sl359QAe-R7F@rufus.isode.com>; Wed, 15 Jul 2009 16:47:03 +0100
Message-ID: <4A5DF9CA.9060304@isode.com>
Date: Wed, 15 Jul 2009 16:46:18 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Sandra Murphy <sandy@sparta.com>
References: <046F43A8D79C794FA4733814869CDF07025CD275@dul1wnexmb01.vcorp.ad.vrsn.com> <Pine.WNT.4.64.0907151127100.4872@SANDYM-LT.columbia.ads.sparta.com>
In-Reply-To: <Pine.WNT.4.64.0907151127100.4872@SANDYM-LT.columbia.ads.sparta.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "Hollenbeck, Scott" <shollenbeck@verisign.com>, iesg@ietf.org, secdir@ietf.org
Subject: Re: [secdir] Secdir review of draft-hollenbeck-rfc4930bis-02
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jul 2009 15:57:59 -0000

Sandra Murphy wrote:

> On Tue, 14 Jul 2009, Hollenbeck, Scott wrote:
>
>> Doesn't TLS provide protections for this issue?
>>
>> -Scott-
>
> (a) rfc4930 does not mandate use of TLS as a tranport connection, by 
> design (so I don't know why you mention it):

rfc4934 (binding to TLS over TCP) mandates use of TLS.

>    EPP is intended for use in diverse operating environments where
>    transport and security requirements vary greatly.  It is unlikely
>    that a single transport or security specification will meet the needs
>    of all anticipated operators, so EPP was designed for use in a
>    layered protocol environment.  Bindings to specific transport and
>    security protocols are outside the scope of this specification.

v2.23.0 | Report a Bug | By Email