Review of draft-ietf-dhc-dhcpv6-failover-protocol-03

Carlos Bernardos <> Sat, 24 December 2016 07:55 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 971CE129613; Fri, 23 Dec 2016 23:55:14 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Carlos Bernardos <>
To: <>
Subject: Review of draft-ietf-dhc-dhcpv6-failover-protocol-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Fri, 23 Dec 2016 23:55:14 -0800
Archived-At: <>
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 24 Dec 2016 07:55:14 -0000

Reviewer: Carlos Bernardos
Review result: Ready

I am an assigned INT directorate reviewer for
draft-ietf-dhc-dhcpv6-failover-protocol-03. These comments were
written primarily for the benefit of the Internet Area Directors.
Document editors and shepherd(s) should treat these comments just like
they would treat comments from any other IETF contributors and resolve
them along with any other Last Call comments that have been received.
For more details on the INT Directorate, see

I'm not an expert in DHCPv6, so please consider this review as a light
one. Keeping this in mind, please find my review below.

Overall, I have not found any issue. I think the document is quite
complete and deep. Actually, my main overall comment is that it is
sometimes a bit hard to follow, due to its length and level of
complexity. Since a protocol specification has to be precise, my only
recommendation to address this would be to consider adding some
figures in Section 4, for the reader to get a first overall idea.

Question: is there any implementation available, so some experience
gained from it can be reported (maybe as an annex)?