[Hipsec] Kathleen Moriarty's No Objection on draft-ietf-hip-rfc6253-bis-08: (with COMMENT)

"Kathleen Moriarty" <Kathleen.Moriarty.ietf@gmail.com> Tue, 05 July 2016 01:08 UTC

Return-Path: <Kathleen.Moriarty.ietf@gmail.com>
X-Original-To: hipsec@ietf.org
Delivered-To: hipsec@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 981A612B024; Mon, 4 Jul 2016 18:08:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160705010848.2630.57374.idtracker@ietfa.amsl.com>
Date: Mon, 04 Jul 2016 18:08:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/hipsec/B2ZwAzVTSGehRPr15Eud5Kqwr5s>
Cc: hipsec@ietf.org, draft-ietf-hip-rfc6253-bis@ietf.org, hip-chairs@ietf.org
Subject: [Hipsec] Kathleen Moriarty's No Objection on draft-ietf-hip-rfc6253-bis-08: (with COMMENT)
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jul 2016 01:08:48 -0000

Kathleen Moriarty has entered the following ballot position for
draft-ietf-hip-rfc6253-bis-08: 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-hip-rfc6253-bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Why is MAY used int he error handling and not MUST or listing these
actions as RECOMMENDED?

Thanks for addressing the SecDir review:
https://www.ietf.org/mail-archive/web/secdir/current/msg06366.html