[v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-conditional-ras-06: (with COMMENT)
Benjamin Kaduk <kaduk@mit.edu> Thu, 02 August 2018 02:26 UTC
Return-Path: <kaduk@mit.edu>
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 CB377129C6A; Wed, 1 Aug 2018 19:26:56 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk <kaduk@mit.edu>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-v6ops-conditional-ras@ietf.org, Russ White <russ@riw.us>, v6ops-chairs@ietf.org, russ@riw.us, v6ops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.83.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153317681682.21918.12970450956130307676.idtracker@ietfa.amsl.com>
Date: Wed, 01 Aug 2018 19:26:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/xoJoDEqGiJiZztGnQ9Dlv8vkFZI>
Subject: [v6ops] Benjamin Kaduk's No Objection on draft-ietf-v6ops-conditional-ras-06: (with COMMENT)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.27
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: Thu, 02 Aug 2018 02:26:57 -0000
Benjamin Kaduk has entered the following ballot position for draft-ietf-v6ops-conditional-ras-06: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-v6ops-conditional-ras/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I'll echo Mirja and Spencer's question about the "empty" security considerations. (I actually don't much care for the "This memo introduces no new security considerations" formulation in general, unless it's literally the only content of the section -- it's either followed by new security considerations, in which it's just wrong, or followed by calling out specific portions of the referenced security considerations that are particularly relevant. In the latter case, it seems useful to provide more of a lead-in like "The general security considerations of [X] and[Y] apply, and in particular [...]".) Unfortunately, I don't seem to be in a good position to comment on actual additions to the security considerations section, since I don't have a clear picture of what the proposal in this document actually changes when compared to current/normal practices. This is presumably just a matter of my lacking the appropriate background knowledge for the routing bits, but in a scenario like Figure 3, with distinct edge and first-hop routers, what kind of RAs would the first-hop routers normally be sending? Would they be announcing the routes in question here just without the PIO markings, or not advertising anything at all, or something else? Other than that, thanks for the well-written document!
- [v6ops] Benjamin Kaduk's No Objection on draft-ie… Benjamin Kaduk
- Re: [v6ops] Benjamin Kaduk's No Objection on draf… Jen Linkova
- Re: [v6ops] Benjamin Kaduk's No Objection on draf… Benjamin Kaduk