Re: [secdir] SecDir review of draft-ietf-calsify-2446bis-09

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 09 October 2009 18:25 UTC

Return-Path: <lunohod.baikonur@googlemail.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 2E43128C228 for <secdir@core3.amsl.com>; Fri, 9 Oct 2009 11:25:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.956
X-Spam-Level:
X-Spam-Status: No, score=-1.956 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 wRuzATqJ+4nf for <secdir@core3.amsl.com>; Fri, 9 Oct 2009 11:25:17 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.26]) by core3.amsl.com (Postfix) with ESMTP id 2CB8228C22B for <secdir@ietf.org>; Fri, 9 Oct 2009 11:25:17 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 5so25347qwi.31 for <secdir@ietf.org>; Fri, 09 Oct 2009 11:26:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=CjT2ddB5829gan/VKIMdmAKZx0nccbvvSirOqMXGMj8=; b=awHpE7ClAkzAhWEo5M7WxEISgc/0oQnPfPQR0YIwS+Y0ZjXw9tRqyNX2LCHmyEitxZ tIYlaoQz2RSQ7bpBaR0pvJ+kTjCyy/a/jO7RlOlcuwH0sHhhdGmA9sC3yqIRtc8B2iYO G7pU1ajpxZf7/8wHWfRZZiRkTwcOsbdqaGQrA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=Wvta991y9lA+tzZoUIsyOYKYhyCuRVovhFo9NFrgnM9wRA31yhrzMoY69HwRFTs3Gk MlTOT88xAF12wFOCjuPDxeWWlUBsHrszxlsB+9RjxZsaz7F76EihIk5cobmDvqm3VO+o TmkxxMIdLh/tJcjT9tCO7sBbOx3NjlaVu412I=
MIME-Version: 1.0
Sender: lunohod.baikonur@googlemail.com
Received: by 10.229.32.82 with SMTP id b18mr1871649qcd.10.1255112818609; Fri, 09 Oct 2009 11:26:58 -0700 (PDT)
In-Reply-To: <7F9A6D26EB51614FBF9F81C0DA4CFEC80190AD3286D2@il-ex01.ad.checkpoint.com>
References: <7F9A6D26EB51614FBF9F81C0DA4CFEC80190AD328370@il-ex01.ad.checkpoint.com> <7236D8B61D923C0A53A03F7E@caldav.corp.apple.com> <7F9A6D26EB51614FBF9F81C0DA4CFEC80190AD3286D2@il-ex01.ad.checkpoint.com>
Date: Fri, 9 Oct 2009 19:26:58 +0100
X-Google-Sender-Auth: 1b3c420c83795b7b
Message-ID: <29d3c4cb0910091126i38b60642vb9ac8ab929a75f9b@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Yaron Sheffer <yaronf@checkpoint.com>, tim.polk@nist.gov
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Cyrus Daboo <cyrus@daboo.name>, Lisa Dusseault <lisa.dusseault@gmail.com>, secdir <secdir@ietf.org>
Subject: Re: [secdir] SecDir review of draft-ietf-calsify-2446bis-09
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: Fri, 09 Oct 2009 18:25:18 -0000

Hi Yaron,

On Tue, Sep 22, 2009 at 10:47 PM, Yaron Sheffer <yaronf@checkpoint.com> wrote:
 [...]
>> Proposal:
>>
>> Section 6.2: remove the sentence:
>>
>>    This may be accomplished using
>>    public key technology, specifically Security Multiparts for MIME
>>    [RFC1847] in the iTIP transport binding.
>>
>> Section 6.2.1: change title to: "Securing iTIP transactions"
>>
>> Change first sentence to:
>>
>>    iTIP transport bindings MUST provide a mechanism to enable
>> authentication of the
>>    sender's identity, and privacy and integrity of the data being
>>    transmitted.
>>
>> The reference to 1847 would be removed entirely.
>
> [YS] If there are still bindings that do use S/MIME, you might want to have
> "if S/MIME is used to provide these assurances..." and the rest of the existing subsection.

This text belongs to iMIP (iTIP binding to SMTP), which is a separate
document that I am editing.

So at this point I think all of your issues were addressed in the
latest version posted by Cyrus.

Regards,
Alexey