Kathleen Moriarty's No Objection on draft-ietf-bfd-seamless-base-09: (with COMMENT)

"Kathleen Moriarty" <Kathleen.Moriarty.ietf@gmail.com> Tue, 03 May 2016 21:04 UTC

Return-Path: <Kathleen.Moriarty.ietf@gmail.com>
X-Original-To: rtg-bfd@ietf.org
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E4C6912D8FE; Tue, 3 May 2016 14:04:05 -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>
Subject: Kathleen Moriarty's No Objection on draft-ietf-bfd-seamless-base-09: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160503210405.8301.12183.idtracker@ietfa.amsl.com>
Date: Tue, 03 May 2016 14:04:05 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-bfd/sw41YEjBmKvtGBVue2JPbT6HWJw>
Cc: rtg-bfd@ietf.org, draft-ietf-bfd-seamless-base@ietf.org, bfd-chairs@ietf.org
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.17
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 May 2016 21:04:06 -0000

Kathleen Moriarty has entered the following ballot position for
draft-ietf-bfd-seamless-base-09: 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-bfd-seamless-base/



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

Thanks for addressing my prior discuss comments in the updated draft,
noting them here to check before approval.

This should be pretty easy to address.  In the security consideration
section, the following recommendation appears:

 o  SBFDReflector MUST NOT look at the crypto sequence number before
      accepting the packet.

Could you please add text to say what happens (what attacks are possible)
if this is looked at?  There is nothing to stop the crypt sequence number
from being looked at, right?  Is there a way to actually prevent that?