IETF Logo Mail Archive

Re: [IPsec] draft-ietf-ipsecme-ikev2-null-auth-05.txt

Stephen Kent <kent@bbn.com> Thu, 02 April 2015 14:21 UTC

Return-Path: <kent@bbn.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B82291B2B70 for <ipsec@ietfa.amsl.com>; Thu, 2 Apr 2015 07:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 p33VQ2qXeEFh for <ipsec@ietfa.amsl.com>; Thu, 2 Apr 2015 07:21:13 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B3051A90F2 for <ipsec@ietf.org>; Thu, 2 Apr 2015 07:21:02 -0700 (PDT)
Received: from ssh.bbn.com ([192.1.122.15]:33062 helo=COMSEC.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1YdfzQ-000LWj-Mt for ipsec@ietf.org; Thu, 02 Apr 2015 10:21:00 -0400
Message-ID: <551D504C.7040601@bbn.com>
Date: Thu, 02 Apr 2015 10:21:00 -0400
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: ipsec@ietf.org
References: <21780.37200.119692.51021@fireball.kivinen.iki.fi> <C5AE72F035554A3F9F02F7C283C536C4@buildpc> <CAHbuEH7KX6x9rQHTN4M5QB4dZ6vsZ8oAjQYuZooKsqxdgf6xnQ@mail.gmail.com> <A4CA1B96-3AF6-4D5F-9EFE-6794CBC31FBD@vpnc.org> <CAHbuEH5GV7wKv7PO++wgA_b3K_=dKESAx6xf0JOZTmU1REMbpQ@mail.gmail.com> <CAHbuEH4tT=pTa+bE8W2Xix99djfDjq7Fkpuj10-Pp=GAKDtgwA@mail.gmail.com> <8CB67699-1986-417D-B270-678EBCBA7C29@vpnc.org>
In-Reply-To: <8CB67699-1986-417D-B270-678EBCBA7C29@vpnc.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipsec/Q-UFA82kShYklI-G1K0HzR2O-4A>
Subject: Re: [IPsec] draft-ietf-ipsecme-ikev2-null-auth-05.txt
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 14:21:14 -0000

As the primary author of 4301, and the creator of the PAD, I believe 
this work
does update that section of 4301. I agree with Kathleen that this doc 
needs to
say precisely what parts of 4301 are being updated, perhaps using a 
before/after
approach.

Steve

> On Apr 1, 2015, at 6:57 PM, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> wrote:
>> I went back to the email thread as I wanted to look at the consensus and don't see it the way Paul does.
>> Here is the end of the thread:
>> http://www.ietf.org/mail-archive/web/ipsec/current/msg09668.html
>>
>> It reads as confusion with the term updates and most being ok with going in either direction, Paul against and Yaron more in favor.
> Yes, exactly. So, it sounds like you see the consensus (and confusion) the way I do.
>
>> Updates can update very specific text in a draft.  Since this just applies in this special case, the updates text needs to be clearly worded to reflect that or you copy in all the text that applies from the other draft.
> Sounds fine. Who do you want to make that decision?
>
> --Paul Hoffman
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec
>

v2.23.0 | Report a Bug | By Email