[Int-area] Alissa Cooper's Discuss on draft-ietf-intarea-provisioning-domains-10: (with DISCUSS and COMMENT)
Alissa Cooper via Datatracker <noreply@ietf.org> Tue, 21 January 2020 16:22 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 53928120950; Tue, 21 Jan 2020 08:22:29 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper 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.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <157962374933.28929.2538365268246704614.idtracker@ietfa.amsl.com>
Date: Tue, 21 Jan 2020 08:22:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/ckQFuQHQbKVhUFlmv7AUucp-FkU>
Subject: [Int-area] Alissa Cooper's Discuss on draft-ietf-intarea-provisioning-domains-10: (with DISCUSS and 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: Tue, 21 Jan 2020 16:22:32 -0000
Alissa Cooper has entered the following ballot position for draft-ietf-intarea-provisioning-domains-10: Discuss 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/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- This is a nit that should be easy to resolve but I'm confused by it, so I'm flagging it here. The reference for [URN] in Section 10.2 says '[URN] "URN Namespaces", n.d..,' which seems like an error. Given the way [URN] is used in 4.3, I'm not sure I understand why organizations with formal URN namespaces <https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml#urn-namespaces-1> would be expected to be using PvDs, if that is what the document intends to convey. In any event, at a minimum the reference needs to be fixed. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- = Section 4.1 = "If the HTTP status of the answer is between 200 and 299, inclusive, the host MAY get a file containing a single JSON object." This seems like a misuse of normative MAY, as the behavior is determined by the sending server, not the host. = Section 7 = s/IPv6 Privacy Address/IPv6 temporary address/ (to align with RFC 7721 terminology)
- [Int-area] Alissa Cooper's Discuss on draft-ietf-… Alissa Cooper via Datatracker
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Tommy Pauly
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Alissa Cooper
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Tommy Pauly
- Re: [Int-area] Alissa Cooper's Discuss on draft-i… Alissa Cooper