Re: [manet] Kathleen Moriarty's No Objection on draft-ietf-manet-rfc6779bis-06: (with COMMENT)

kathleen.moriarty.ietf@gmail.com Thu, 02 June 2016 13:34 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: manet@ietfa.amsl.com
Delivered-To: manet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BC4512D184; Thu, 2 Jun 2016 06:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, 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 evO0kg04TMD6; Thu, 2 Jun 2016 06:34:51 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 A3FC912D194; Thu, 2 Jun 2016 06:34:40 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id n63so36447540qkf.0; Thu, 02 Jun 2016 06:34:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/lagJSoD3nqpLAdg5+v3hp/dQtrZKXPfaq++0oE7JGc=; b=VDSvihAawaz0/4H24/sXOt3dJ+JOk/O3LXVl7a60ndjhtRQ0OUS2dLNLfa6UCpSVsv 9zXXNjWYJuPBuzdtFYMD58VHo8AKXJycG0HyT/w3GXveSxvMAcWhcJlbS+vRO8m8+HLz mSTJyU7YGaKlo0y3yMSQEymONY1SF5dR+1WdETjCcbhw6ejF+/lfhJkpviIIY8QG13dl Wyu2ADEGqnHxnAQJ9QhfybAat29B11/Mnz8SdDyvQmQ5MFDbNgmYWvMTreaBM8lWPVQG rGzBs9EpeTrwPWXSNdpvJzvK3aHk2b8nHDiLk8W5hFFDpaZQeisPkV06HfImCLEIxSgP /r1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/lagJSoD3nqpLAdg5+v3hp/dQtrZKXPfaq++0oE7JGc=; b=HJd6pWQ9ldx/6chi0b94U/7RQSJFZTaDkgYCtU37FCBL9RdI87Yl8ghYTTXFg+KCmN 3mGT6LDl6cUGQ7uBhExCkX+tTvntrfk1EwKaSg0a9PMi430qxRHQDQSWZFPR9fukJmyG +wkhdV078oPJ8hMpJ76B9y5qeUo/KHGPxiQl0L4Ls9XGond0w5YHPPZ/1r/TWFt6ApuI 1OywQz7pa2YtMKqknRfO1RHjYcwMfL2zREByDK2ges0DKgLmHxke3Hl0lLp70tOyDdX6 NKl7uDOKsF6FiHh8pbcMqyzjHtsOw2d0odMX5Nis7Z7iH+avjvxQq/IYQtQEK9vIrxuo AxxQ==
X-Gm-Message-State: ALyK8tKKwfVcjuGxu70NmA0tbFkc8H/QllVglX5qTd45EE8WGtwUUVMfH2jEBgb7eG9uvw==
X-Received: by 10.55.87.197 with SMTP id l188mr42181226qkb.13.1464874479796; Thu, 02 Jun 2016 06:34:39 -0700 (PDT)
Received: from [192.168.1.6] (209-6-124-204.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.124.204]) by smtp.gmail.com with ESMTPSA id b188sm1685788qkg.8.2016.06.02.06.34.39 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 02 Jun 2016 06:34:39 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: kathleen.moriarty.ietf@gmail.com
X-Mailer: iPhone Mail (12H143)
In-Reply-To: <CAK=bVC9j5m8_F8LpO-iEPNu1jL3_ttgtQ2GcBz5vihahM1GPuw@mail.gmail.com>
Date: Thu, 02 Jun 2016 09:34:38 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <074A9E01-07E5-4AE1-8447-7A9ABB883E89@gmail.com>
References: <20160601191400.16077.83083.idtracker@ietfa.amsl.com> <CAK=bVC9j5m8_F8LpO-iEPNu1jL3_ttgtQ2GcBz5vihahM1GPuw@mail.gmail.com>
To: Ulrich Herberg <ulrich@herberg.name>
Archived-At: <http://mailarchive.ietf.org/arch/msg/manet/4hmldYiI_SYpv6d36ooERqph4kM>
Cc: "manet-chairs@ietf.org" <manet-chairs@ietf.org>, Christopher Dearlove <chris.dearlove@baesystems.com>, "manet@ietf.org" <manet@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-manet-rfc6779bis@ietf.org" <draft-ietf-manet-rfc6779bis@ietf.org>
Subject: Re: [manet] Kathleen Moriarty's No Objection on draft-ietf-manet-rfc6779bis-06: (with COMMENT)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mobile Ad-hoc Networks <manet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/manet>, <mailto:manet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/manet/>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/manet>, <mailto:manet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2016 13:34:53 -0000


Sent from my iPhone

> On Jun 2, 2016, at 1:25 AM, Ulrich Herberg <ulrich@herberg.name> wrote:
> 
> Kathleen,
> 
> I wouldn't go as far as saying that "the boilerplate wasn't used";
> there was only a minor difference to the boilerplate. I am not sure
> where it came from. We copied that section from RFC6779, so my only
> guess is that the boilerplate has changed since then (but I haven't
> verified). Either way, I have prepared a new revision that uses the
> same text as in the boilerplate.

Thanks for using the updated boilerplate.

Best regards,
Kathleen 

> 
> Best regards
> Ulrich
> 
> On Wed, Jun 1, 2016 at 12:14 PM, Kathleen Moriarty
> <Kathleen.Moriarty.ietf@gmail.com> wrote:
>> Kathleen Moriarty has entered the following ballot position for
>> draft-ietf-manet-rfc6779bis-06: No Objection
>> 
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>> 
>> 
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>> 
>> 
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-manet-rfc6779bis/
>> 
>> 
>> 
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>> 
>> I'll wait for the response to Stephen's question as I also noticed the
>> boilerplate wasn't used (SecDir review did too, kinda).
>> 
>> I do appreciate the descriptions provided for the threats associated with
>> the read/write read/create objects.  Thanks for that.
>> 
>>