Re: [IPsec] AD review of draft-ietf-ipsecme-rfc4307bis

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Mon, 09 January 2017 14:43 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B1B3129CFF for <ipsec@ietfa.amsl.com>; Mon, 9 Jan 2017 06:43:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 1kTBM9erY3Ge for <ipsec@ietfa.amsl.com>; Mon, 9 Jan 2017 06:43:25 -0800 (PST)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (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 B4E64129CF1 for <ipsec@ietf.org>; Mon, 9 Jan 2017 06:43:24 -0800 (PST)
Received: by mail-qt0-x236.google.com with SMTP id l7so88266745qtd.1 for <ipsec@ietf.org>; Mon, 09 Jan 2017 06:43:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=A+1+TzYEOr9LbR1ac+mpJblJS72HyrXvSnTu4sWXj1w=; b=k+agk1m9TtJq1kRNYxuHFQvWB5X8XEuWk21G31r4v1yv/gFTsyNnonY8xv0eaBEB4x nbL4ijJ2rX2XeqiRHJSgbMXwwn4+0U4xTl9LvRDEtUays9zq2nvkZ8JhN+n7L5HR8n38 dmvxaSLYLBbcDWdZPH6jJeM29+ARvAHs1MA4cX4MjPmhnppH9We8AXfpRRR+PrtpE1eP ScE+1Qp37IBTaUcw2yIDme+dGMuTmBe42PgSMUMGBy6RMLgerhwH9s+TsRpU6ugWUBWB NEAIxUntjCR09tA2fm5cJsiEIj8dayhLBFGojCs2kQZn1qqIUl/Pz+b20qfPqysLDSy+ QLOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=A+1+TzYEOr9LbR1ac+mpJblJS72HyrXvSnTu4sWXj1w=; b=iPxRT27YmO1PCwrpTO8ZvwXgwlaH3bXYKTlQnk4p6hSNT4tKPYcG02zMgMnjuyu1nM G0eCJ4S1NXh3v16zKWZDEDZxnXqd4eFjs+rxmZnBWyPD5lvdkEgncVuVuOlBmHQy7oT0 qutJi+Wob2wuaKZKY547PHeIncxVdY2KbOjxQe5HKGQbH9vfobYtnh7otnERy1ZYg0n4 myKZ1496fkt87M7QTl9muW593S6OAy46tODFRa+MznpQbJFessKa4fTjjKHYbJpiDXku DKaRJ42uREdqbuSVCt95EiIZyhjOj7xyDEsX4Ly8Nt524J1SeffOMY+TeZNIRlsq/tvp NICA==
X-Gm-Message-State: AIkVDXLFYTJ3BLOkLdNegWfoWjYjKwiBKlVai2hWJaDJrBTWLV1hgntCevqMvToy6LlweKLEcDs9NkGHs8zvpg==
X-Received: by 10.237.41.36 with SMTP id s33mr7678741qtd.139.1483973003892; Mon, 09 Jan 2017 06:43:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.161.101 with HTTP; Mon, 9 Jan 2017 06:43:23 -0800 (PST)
In-Reply-To: <BN6PR09MB1427FEFE4970F7DDB412AAD9F0640@BN6PR09MB1427.namprd09.prod.outlook.com>
References: <CAHbuEH4pqTK-kc65FVh98X-t+YsVe+9=J7_PjB8hESsY+5=-PQ@mail.gmail.com> <alpine.LRH.2.20.1612121254150.14930@bofh.nohats.ca> <CAHbuEH4MgqDpWR_yc21Z8-HNU1Pvy8Hyz0NvW9qntwtxFuZmmw@mail.gmail.com> <CAHbuEH7RROEheNbAJ9RpE+V8TiP1DYa92CbXEMQcas7wDUoYKg@mail.gmail.com> <alpine.LRH.2.20.1701061555210.2069@bofh.nohats.ca> <CAHbuEH46LQ=rk4aTqcbCa+=De5HPwbGBRQQOCzdV0tB0pz1wfw@mail.gmail.com> <BN6PR09MB1427FEFE4970F7DDB412AAD9F0640@BN6PR09MB1427.namprd09.prod.outlook.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Mon, 09 Jan 2017 09:43:23 -0500
Message-ID: <CAHbuEH6pYvWk79KgjdW=L7cnxm5vQZOhRcFu4mPUOE2+Ndu_TQ@mail.gmail.com>
To: "Waltermire, David A. (Fed)" <david.waltermire@nist.gov>
Content-Type: multipart/alternative; boundary="001a114d3f9ec0dce40545aa6365"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/0347m5DrKiVSsyRwXluYtxrkWsE>
Cc: "ipsec@ietf.org" <ipsec@ietf.org>, "paul@nohats.ca" <paul@nohats.ca>
Subject: Re: [IPsec] AD review of draft-ietf-ipsecme-rfc4307bis
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 09 Jan 2017 14:43:26 -0000

Hi Dave,

Yes, I can remove the telechat date and reset it when the WG os ready.
With that, it seems it would be fine to add time to the IETF last call
(restart).

Thank you,
Kathleen

On Mon, Jan 9, 2017 at 9:31 AM, Waltermire, David A. (Fed) <
david.waltermire@nist.gov> wrote:

> Kathleen,
>
>
>
> I am just getting back after taking a long holiday. Sorry I was AFK on
> this one.
>
>
>
> We want to advance rfc7321bis to go through the remainder of IESG review
> with 4307bis as a pair. Unfortunately, I wasn’t able to get this done
> before leaving on holiday. I need to do a WGLC on rfc7321bis starting ASAP
> this week. Can you hold 4307bis for a bit to have the two run concurrently?
>
>
>
> Thanks,
>
> Dave
>
>
>
> *From:* IPsec [mailto:ipsec-bounces@ietf.org] *On Behalf Of *Kathleen
> Moriarty
> *Sent:* Friday, January 06, 2017 4:01 PM
> *To:* paul@nohats.ca
> *Cc:* ipsec@ietf.org
> *Subject:* Re: [IPsec] AD review of draft-ietf-ipsecme-rfc4307bis
>
>
>
>
>
>
>
> On Fri, Jan 6, 2017 at 3:56 PM, Paul Wouters <paul@nohats.ca> wrote:
>
> On Fri, 6 Jan 2017, Kathleen Moriarty wrote:
>
> I never got an answer as to whether or not I should wait on the last call,
> so I pushed it through.  No comments
> came in during the holiday period.  Should last call be extended?  Or does
> the WG feel the reason was because the
> document is ready?  If the latter then I'll get it ready for an IESG
> telechat.  I'd prefer to put it on 2/2/2017
> as there are already a fair number of documents on the telechat in 2 weeks.
>
>
> If you schedule it for 2/2 then I guess we can give people another two
> weeks for comments? Although I'm not sure if that means we will get
> more comments :)
>
> I'm not sure we'll get more either.  Is 2/2 okay or is there any rush for
> this draft?
>
>
>
> Thanks!
>
>
>
> Paul
>
>
>
>
>
> --
>
>
>
> Best regards,
>
> Kathleen
>



-- 

Best regards,
Kathleen