[Int-area] Mirja Kühlewind's Yes on draft-ietf-intarea-provisioning-domains-10: (with COMMENT)
Mirja Kühlewind via Datatracker <noreply@ietf.org> Mon, 20 January 2020 17:43 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: int-area@ietf.org
Delivered-To: int-area@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C6EA12097A; Mon, 20 Jan 2020 09:43:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kühlewind via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-intarea-provisioning-domains@ietf.org, Erik Kline <ek@loon.com>, intarea-chairs@ietf.org, ek@loon.com, int-area@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.116.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Mirja Kühlewind <ietf@kuehlewind.net>
Message-ID: <157954218263.1485.1285146620422882411.idtracker@ietfa.amsl.com>
Date: Mon, 20 Jan 2020 09:43:02 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/CgD_2C3b4nuJo_dLAYOD7dW5kJM>
Subject: [Int-area] Mirja Kühlewind's Yes on draft-ietf-intarea-provisioning-domains-10: (with COMMENT)
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2020 17:43:03 -0000
Mirja Kühlewind has entered the following ballot position for draft-ietf-intarea-provisioning-domains-10: 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-intarea-provisioning-domains/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for this well-written document (and thanks Martin for the TSV-ART review)! I have no real issues but two quick questions: 1) In Sec 3.4 (and somewhere earlier as well), you say: "In case multiple PvD Options are found in a given RA, hosts MUST ignore all but the first PvD Option." Why is that restriction actually needed? I mean given you can send multiple RA from the same source address with each an PvD Option with either different of the same ID, would it be so bad to have multiple PvD Option in the same RA? 2) As this document refers to draft-kline-mif-mpvd-api-reqs, is there any plan to update and publish this doc? However, this draft anyway "only" talk about API requirement, but I guess some network signalling would also be needed...? Is there any additional work? P.S.: The shepherd writ-up seems a bit out-dated...
- [Int-area] Mirja Kühlewind's Yes on draft-ietf-in… Mirja Kühlewind via Datatracker
- Re: [Int-area] Mirja Kühlewind's Yes on draft-iet… Tommy Pauly