Re: Protocol Action: 'IKEv2 Fragmentation' to Proposed Standard (draft-ietf-ipsecme-ikev2-fragmentation-10.txt)

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Wed, 03 September 2014 20:54 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D57AE1A6FE5 for <ietf@ietfa.amsl.com>; Wed, 3 Sep 2014 13:54:12 -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 kLVAev66Hr5h for <ietf@ietfa.amsl.com>; Wed, 3 Sep 2014 13:54:11 -0700 (PDT)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 156F51A6FE6 for <ietf@ietf.org>; Wed, 3 Sep 2014 13:53:31 -0700 (PDT)
Received: by mail-la0-f45.google.com with SMTP id pn19so10596955lab.32 for <ietf@ietf.org>; Wed, 03 Sep 2014 13:53:30 -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=RYe8km5fWK+AH/tvqMsMiW2qWSmGYZhPXb1hz74VWAU=; b=xAPNk25tjAtQP0aXsaBVg6janfEzS6Sg/NB6yhF3C8mIQjllgRSoisoWddrBh3ZaF9 vOjIYm/1f4D7f6Gsx7DMPZ+m4/9VyYzZcr156xDlfJ4J87ZGkOj5wXmcs/Zgi54OC8wI zoacLzpXsDYEpof/wznXnhTMA3pDUuHu25ReAFyUCvtYm/oi7fPSz2Q1koq0mPL0JSrp e9edHjc3eXzY51AaNXcA2RREZ2EGKSRVAv8MBw2+sIS8MOWsJ20MN2r6d/wcPrScIpcL g/WkwfFtXEsC5ed9kkahQ1AjqiHJ5QV2gWl2XzvIxgt5WKuJTWQ9aACzEri9bxVUG7RP aUEA==
MIME-Version: 1.0
X-Received: by 10.112.118.68 with SMTP id kk4mr39108lbb.4.1409777610428; Wed, 03 Sep 2014 13:53:30 -0700 (PDT)
Received: by 10.112.64.170 with HTTP; Wed, 3 Sep 2014 13:53:30 -0700 (PDT)
In-Reply-To: <10593890.1409771163918.JavaMail.root@elwamui-mouette.atl.sa.earthlink.net>
References: <10593890.1409771163918.JavaMail.root@elwamui-mouette.atl.sa.earthlink.net>
Date: Wed, 03 Sep 2014 16:53:30 -0400
Message-ID: <CAHbuEH4RQCr9-WfuEEnKSWcW8mBe6OUbgd=39-UcWYSucSzUtA@mail.gmail.com>
Subject: Re: Protocol Action: 'IKEv2 Fragmentation' to Proposed Standard (draft-ietf-ipsecme-ikev2-fragmentation-10.txt)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>
Content-Type: multipart/alternative; boundary="047d7bb03ee2ae94d705022f6d77"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PtHlIoZUH3-2fgO0dgKieycCk4U
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Sep 2014 20:54:13 -0000

Hi Randy,

Sorry, this was my fault.  I have a question into the secretariat to see if
I can fix this as it was part of the ballot text.  I was checking on the
number of implementations and forgot to go back and update with the answer,
none.

If I can add text, it will note that the working group reached consensus
and that there are no implementations yet.  That would be followed with the
text from the shepherd report:

The WG discussion of the document was fairly good, with about average
participation (which
for the IPsecME WG means "the chairs had to beg a bit for more
participants, but we then got
them"). We also got a "TSVDIR-ish review" of the draft, which got good
discussion on the
list. There was a reasonable amount of give-and-take, and the WG Last Call
was uncontentious.
A significant point was brought up during IETF Last Call, and was added to
the Security
Considerations.

Best regards,
Kathleen


On Wed, Sep 3, 2014 at 3:06 PM, Randy Presuhn <randy_presuhn@mindspring.com>
wrote:

> Hi -
> >From: The IESG <iesg-secretary@ietf.org>
> >Sent: Sep 2, 2014 3:04 PM
> >To: IETF-Announce <ietf-announce@ietf.org>
> >Cc: ipsecme mailing list <ipsec@ietf.org>, ipsecme chair <
> ipsecme-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
> >Subject: Protocol Action: 'IKEv2 Fragmentation' to Proposed Standard
> (draft-ietf-ipsecme-ikev2-fragmentation-10.txt)
> ...
> >Document Quality
> >
> >   Are there existing implementations of the protocol?  Have a
> >   significant number of vendors indicated their plan to
> >   implement the specification?  Are there any reviewers that
> >   merit special mention as having done a thorough review,
> >   e.g., one that resulted in important changes or a
> >   conclusion that the document had no substantive issues?  If
> >   there was a MIB Doctor, Media Type, or other Expert Review,
> >   what was its course (briefly)?  In the case of a Media Type
> >   Review, on what date was the request posted?
>
> It would have been nice if the announcement had included
> answers to these questions.
>
> Randy
>
>


-- 

Best regards,
Kathleen