Re: [IPsec] Barry Leiba's Discuss on draft-ietf-ipsecme-ikev2-null-auth-06: (with DISCUSS and COMMENT)

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Thu, 21 May 2015 20:24 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.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 D8BF01A8992; Thu, 21 May 2015 13:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 MiU3KseVlIcZ; Thu, 21 May 2015 13:24:35 -0700 (PDT)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB18E1A8A48; Thu, 21 May 2015 13:24:34 -0700 (PDT)
Received: by laat2 with SMTP id t2so110913004laa.1; Thu, 21 May 2015 13:24:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wZK5K0AzpyM9xc5P0RICa4tA6+RjcyO9RUH2+OOFysw=; b=ep4G5sO+YLakOhENkmSOpPVebzhnZ3PsRHZ9gmKvIwK4q5LfAQz+TuL11CvNI9M05Q wGKdYOzhxjJa4XZTHehkn6kcHR58rWIC5lMrUK7YH3aTaa06kmOky01+jTp2xpbaUZ0X SydJGDO2dw1RVFxHSYUGR2fzwFV8b47uWjcCbVq+vlddsb9HZZbMi9tf4gMu3kdfx6NO XUyavZa6qI7gV1IRKSZV2PE5wJ/6kDjWx3rClcNgSdG+pCYfvyJriJj964uKrxDVn0jG JBUJr+5tggt5BzMW5OrRc3oVTqwG51Ut+PCq25UMhmPcBFhcmN+4nV5SPfC29cnamvCb vYlQ==
MIME-Version: 1.0
X-Received: by 10.152.4.72 with SMTP id i8mr3770091lai.32.1432239873259; Thu, 21 May 2015 13:24:33 -0700 (PDT)
Received: by 10.112.11.199 with HTTP; Thu, 21 May 2015 13:24:33 -0700 (PDT)
In-Reply-To: <CALaySJLrp-+NZZBbePGKpdLM75hZ_Y6x_MXZ38DazGRZxOiN1g@mail.gmail.com>
References: <20150521183527.2369.7540.idtracker@ietfa.amsl.com> <760AAAD4-BF1A-4202-BFA1-537C4B3DD9D5@vpnc.org> <CALaySJLrp-+NZZBbePGKpdLM75hZ_Y6x_MXZ38DazGRZxOiN1g@mail.gmail.com>
Date: Thu, 21 May 2015 16:24:33 -0400
Message-ID: <CAHbuEH7zeuo=otowWVEY+Ovx1rRS=_fCu3wYX_zugSrYmkn_YA@mail.gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary="089e01494248e0ff1a05169d54e0"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipsec/CBcXpU7d-WGddtQeq2jVf8Ekef0>
Cc: ipsecme-chairs@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>, "ipsec@ietf.org" <ipsec@ietf.org>, draft-ietf-ipsecme-ikev2-null-auth.ad@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-ipsecme-ikev2-null-auth.shepherd@ietf.org, draft-ietf-ipsecme-ikev2-null-auth@ietf.org
Subject: Re: [IPsec] Barry Leiba's Discuss on draft-ietf-ipsecme-ikev2-null-auth-06: (with DISCUSS and COMMENT)
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, 21 May 2015 20:24:37 -0000

If it's decided to put this draft back into last call, I can do this in the
next couple of hours, but then will be on an overnight flight and will be
without much access until tomorrow afternoon US eastern time.

Thanks,
Kathleen

On Thu, May 21, 2015 at 2:58 PM, Barry Leiba <barryleiba@computer.org>
wrote:

> >> I have no problem with the reference to Experimental RFC 5739, but I do
> >> have a problem with the downref not having been noted in the last call
> >> announcement, as required by RFC 3967 (BCP 97).  And I think the MUST in
> >> the last paragraph of Section 2.5 requires 5739 to be normative.  I hate
> >> to say this, but I think this requires a second last call on this
> >> document, which will really serve no one.  We really do need to do an
> >> update to BCP 97 to fix this, because it comes up all the time.
> >
> > If the IESG wants to fix BCP 97, that's grand. Do note in the "very
> > informative and useful shepherd writeup", it says:
> >
> > If this becomes too much of an issue for the
> > purists, the reference can be moved to the Informative References
> section, but it is more
> > appropriate as a normative reference.
> >
> > I really meant that. Instead of wasting everyone's time with another
> > IETF LC, please strongly consider changing the DISCUSS to "yes, you
> > need to move that reference to the Informational References" section.
>
> The problem is that Section 2.5 says that you MUST do what's in 5739,
> so I think 5739 has to be normative.  And, while I do think a second
> last call is silly, it doesn't really waste must of anyone's time, and
> only delays the document by a week or two, depending upon when
> Kathleen is able to start the second last call.
>
> I think the best thing is just to start a second last call tout de
> suite, which notes the downref and asks for comments only on that
> point.  And then we've done the right thing with respect to BCP 97.
> (And meanwhile, I'll scare up an author for an update to BCP 97,
> because I, too, am tired of this silliness.)
>
> Barry
>
>
> Barry
>



-- 

Best regards,
Kathleen