Review of draft-ietf-6man-rfc4291bis-06

Brian Haberman <> Tue, 10 January 2017 16:32 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id E7E33129D1E; Tue, 10 Jan 2017 08:32:10 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Brian Haberman <>
Subject: Review of draft-ietf-6man-rfc4291bis-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Tue, 10 Jan 2017 08:32:10 -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: Tue, 10 Jan 2017 16:32:11 -0000

Reviewer: Brian Haberman
Review result: Ready with Nits

I just have a few comments/questions on this draft. Overall, it is in
pretty good shape...

1. Section 2.2.3 looks like a complete re-production of RFC 5952, but
I don't see a reference to 5952. Is the intent to deprecate 5952 since
its content is now contained within 4291bis?

2. Section 2.6.1 captures some information about reserved IPv6
multicast addresses, but not all of them. I think it would be
beneficial to point to the IPv6 Multicast Address Allocation registry
maintained by IANA, much like the way Section 2.3 points to the IANA

3. Also in Section 2.6.1, the names of reserved addresses, like "All
Nodes Addresses", were made all lowercase. Was that intentional? Given
that IANA refers to them with capitalization, it would seem that we
need to be consistent. So, I would either retain the capitalization in
this document or ensure that Section 3 directs IANA to update the
names in the registries.