[babel] Opsdir last call review of draft-ietf-babel-hmac-08
Dan Romascanu via Datatracker <noreply@ietf.org> Mon, 05 August 2019 14:42 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: babel@ietf.org
Delivered-To: babel@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A1FF8120234; Mon, 5 Aug 2019 07:42:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dan Romascanu via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-babel-hmac.all@ietf.org, ietf@ietf.org, babel@ietf.org, dromasca@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.99.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Dan Romascanu <dromasca@gmail.com>
Message-ID: <156501615060.24541.14266875792954906382@ietfa.amsl.com>
Date: Mon, 05 Aug 2019 07:42:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/qmoIqRsO0GLvhTIKFSvWGqIjGWY>
Subject: [babel] Opsdir last call review of draft-ietf-babel-hmac-08
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2019 14:42:31 -0000
Reviewer: Dan Romascanu Review result: Ready This document describes a cryptographic authentication mechanism for the Babel routing protocol that has provisions for replay avoidance. As this is not a new protocol but rather an extension of the existing Babel routing protocol allowing for both unicast and multicast datagrams to be used, a full RFC 5706 review does not apply. The document is Ready from and operational and manageability point of view. It is clearly written and provides all needed information to operators. It states that the deployment can be made incrementally in existing networks where current implementations of Babel are already present. It is important for operators to pay attention at the restrictions of applicability defined in section 1.1. There are also a number of recommendations in the text related to configuration parameters that are of interests not only for implementers but also for operators deploying these extensions - for example in sections 4.3.1.1, and 4.4. I would have preferred these to be included in a separate 'Operational Considerations' section.
- [babel] Opsdir last call review of draft-ietf-bab… Dan Romascanu via Datatracker