Review of draft-ietf-softwire-multicast-prefix-option-11
Roni Even <roni.even@mail01.huawei.com> Mon, 09 January 2017 06:52 UTC
Return-Path: <roni.even@mail01.huawei.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 97AD7129B1D; Sun, 8 Jan 2017 22:52:22 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roni Even <roni.even@mail01.huawei.com>
To: gen-art@ietf.org
Subject: Review of draft-ietf-softwire-multicast-prefix-option-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.40.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148394474257.769.4965226716760320959.idtracker@ietfa.amsl.com>
Date: Sun, 08 Jan 2017 22:52:22 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/b__xCcjSDkZmniQLtrXlu68BVgY>
Cc: softwires@ietf.org, ietf@ietf.org, draft-ietf-softwire-multicast-prefix-option.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jan 2017 06:52:22 -0000
Reviewer: Roni Even Review result: Almost Ready I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>. Please resolve these comments along with any other Last Call comments you may receive. Document: draft-ietf-softwire-multicast-prefix-option-11 Reviewer: Roni Even Review Date:2017-1-9 IETF LC End Date: 2017–1-12 IESG Telechat date: Summary: This draft is almost ready for publication as a standard track RFC. Major issues: Minor issues: 1. In section 4 first paragraph say “DHCP servers supporting OPTION_V6_PREFIX64 should be configured with U_PREFIX64 and at least one multicast PREFIX64 (i.e., ASM_PREFIX64 and/or SSM_PREFIX64).” From the rest of the section I understand that for SSM deployments both U_PREFIX64 and SSM_PREFIX64 MUST be configured. What is the reason for “should” in the first paragraph? Are there cases where ASM_PREFIX64 or ASM_PREFIX64 and SSM_PREFIX64 are specified and there is no need to specify U_PREFIX64, maybe these cases should be described. Nits/editorial comments: 1. RFC2119 keywords in the document are sometime capitalized and sometime not. I think it will be good to have consistency and if they do not intend to have RFC2119 semantics some other words should be used
- Review of draft-ietf-softwire-multicast-prefix-op… Roni Even
- RE: Review of draft-ietf-softwire-multicast-prefi… mohamed.boucadair
- RE: [Gen-art] Review of draft-ietf-softwire-multi… Roni Even
- RE: [Gen-art] Review of draft-ietf-softwire-multi… mohamed.boucadair
- RE: [Gen-art] Review of draft-ietf-softwire-multi… Roni Even