[v6ops] Opsdir last call review of draft-ietf-v6ops-conditional-ras-04

Sheng Jiang <jiangsheng@huawei.com> Mon, 21 May 2018 08:23 UTC

Return-Path: <jiangsheng@huawei.com>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 14A1112E87B; Mon, 21 May 2018 01:23:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Sheng Jiang <jiangsheng@huawei.com>
To: ops-dir@ietf.org
Cc: draft-ietf-v6ops-conditional-ras.all@ietf.org, v6ops@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.80.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152689102802.23045.6041887435563645658@ietfa.amsl.com>
Date: Mon, 21 May 2018 01:23:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Vd5yK9mVh6XX3pHrppJKI163WB8>
Subject: [v6ops] Opsdir last call review of draft-ietf-v6ops-conditional-ras-04
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 May 2018 08:23:48 -0000

Reviewer: Sheng Jiang
Review result: Has Issues

Reviewer: Sheng Jiang
Review result: Has Issues

I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG. These comments
were written with the intent of improving the operational aspects of the IETF
drafts. Comments that are not addressed in last call may be included in AD
reviews during the IESG review. Document editors and WG chairs should treat
these comments just like any other last call comments.

This Informational document describes a mechanism that uses the conditional
Router Advertisements for Enterprise Multihoming in which an enterprise network
up-links to multiple ISPs using an address space assigned by an ISP.

Major issue: no.

Minor issue: There are many unused reference. However, they are not simple Nits
and cannot be fixed by deleting them from reference list. Many of these unused
reference are really relevant and should have some content to describe the
relationship with the mechanism or scenario of the document, such as RFC6296
NAT66, etc.

Regards,

Sheng