[dhcwg] Erik Kline's Yes on draft-ietf-dhc-dhcpv6-pd-relay-requirements-04: (with COMMENT)
Erik Kline via Datatracker <noreply@ietf.org> Thu, 17 December 2020 01:52 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: dhcwg@ietf.org
Delivered-To: dhcwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 15C133A1371; Wed, 16 Dec 2020 17:52:14 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Erik Kline via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-dhc-dhcpv6-pd-relay-requirements@ietf.org, dhc-chairs@ietf.org, dhcwg@ietf.org, Bernie Volz <volz@cisco.com>, volz@cisco.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.23.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Erik Kline <ek.ietf@gmail.com>
Message-ID: <160816993406.2961.11066542485570806471@ietfa.amsl.com>
Date: Wed, 16 Dec 2020 17:52:14 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/2XmUDU8BjI0hnFC4yFpQb0ydZzI>
Subject: [dhcwg] Erik Kline's Yes on draft-ietf-dhc-dhcpv6-pd-relay-requirements-04: (with COMMENT)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Dec 2020 01:52:14 -0000
Erik Kline has entered the following ballot position for draft-ietf-dhc-dhcpv6-pd-relay-requirements-04: Yes 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-dhc-dhcpv6-pd-relay-requirements/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- [[ questions ]] [ general ] * Should this aim for BCP? [ section 4.2 ] * Seems like the MUST in R-4 is contingent upon implementation of the MAY that precedes it. It might worth sneaking in some condition phrase like, "If such a mechanism is implemented ... MUST ...". * It seems to me that R-5 would prevent a client from monitoring the CMTS/BNG for correctly installed routes by sending it a packet with a destination address in its delegated prefix and checking that it gets reflected back (similar to other checks done for tunnels). (I recognize this is not guaranteed to work in all environments.) What should a client wishing to keep an eye on this stuff do? Just ping a public service with an address in each source prefix of interest? [[ nits ]] [ section 2.1 ] * "This document serves" -> "This document discusses", or "This document is concerned with", or something, perhaps?
- [dhcwg] Erik Kline's Yes on draft-ietf-dhc-dhcpv6… Erik Kline via Datatracker
- Re: [dhcwg] Erik Kline's Yes on draft-ietf-dhc-dh… ianfarrer
- Re: [dhcwg] Erik Kline's Yes on draft-ietf-dhc-dh… Ms. Li HUANG