[Gen-art] draft-ietf-sidrops-aspa-profile-27 early Genart review
Peter Yee via Datatracker <noreply@ietf.org> Sun, 19 July 2026 11:27 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@mail2.ietf.org
Received: from [10.244.21.25] (gaia.k8s.ietf.org [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id A309711970951; Sun, 19 Jul 2026 04:27:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784460432; bh=8g5Cx+tF4ZL/FGEw3qziurcNasThwZi/xmugdZ6CSIE=; h=From:To:Cc:Subject:Reply-To:Date; b=C7vlIorYw6dN/dSKYDiMR3kkTalLeaJoTsQx/hz8v/ruya/eY3Jq9kUl65+R9ACI8 9FRJsOFPmhCizrh81CDkB8OQbd161wF6Lmg3/2lNO3UIEJm/weBOuVglyk7pNShUN8 cTtUz03rycgIt2+npsUfLcRi9KtTcgo7RDEZEXF0=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Peter Yee via Datatracker <noreply@ietf.org>
To: gen-art@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.69.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178446043256.588.17184129397541003804@dt-datatracker-d4d6ff9d9-fsx7d>
Date: Sun, 19 Jul 2026 04:27:12 -0700
Message-ID-Hash: XXD6ZJVPMPTF7VT4QYYKEW66OPWW6Q2V
X-Message-ID-Hash: XXD6ZJVPMPTF7VT4QYYKEW66OPWW6Q2V
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-gen-art.ietf.org-0; header-match-gen-art.ietf.org-1; header-match-gen-art.ietf.org-2; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-sidrops-aspa-profile.all@ietf.org, sidrops@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Peter Yee <peter@akayla.com>
Subject: [Gen-art] draft-ietf-sidrops-aspa-profile-27 early Genart review
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/JB6TfIaIiiN50H3ppyotgMB2VNs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Owner: <mailto:gen-art-owner@ietf.org>
List-Post: <mailto:gen-art@ietf.org>
List-Subscribe: <mailto:gen-art-join@ietf.org>
List-Unsubscribe: <mailto:gen-art-leave@ietf.org>
Document: draft-ietf-sidrops-aspa-profile Title: A Profile for Autonomous System Provider Authorization Reviewer: Peter Yee Review result: Ready with Nits Document: draft-ietf-sidrops-aspa-profile Title: A Profile for Autonomous System Provider Authorization Reviewer: Peter Yee Review result: Ready with Nits I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at <https://wiki.ietf.org/en/group/gen/GenArtFAQ>. Document: draft-ietf-sidrops-aspa-profile-27 Reviewer: Peter Yee Review Date: 2026-07-19 IETF LC End Date: IESG Telechat date: Not scheduled for a telechat Summary: This draft specifies an Autonomous System Provider Authorization object that is protected by CMS. The object allows a customer Autonomous System to specify its Provider Autonomous System(s). Major issues: None Minor issues: Page 3, 1st paragraph after lettered items, 1st sentence: I’m having troubles understanding how this specification constitutes a profile. A profile of what? As far as I can see, it specifies an object, its semantics, and related procedures. Admittedly, that object ends up inside of a CMS wrapper, but I don’t really think of that as making it a profile of a CMS-protected object. To be clear, this is a really minor issue, and I could be wrong about what constitutes a profile. Nits/editorial comments: Page 3, 4th paragraph after lettered items, 1st sentence: change “CMS [RFC5652] protected” to “CMS-protected [RFC 5652]”. Change “content type” to “content-type”. Page 6, section 3.3, 1st bullet item: change “CustomerASID” to “customerASID”. Page 6, section 3.3, 4th bullet item: change “An” to “A”. Page 7, section 5.2, 1st sentence: Should “CAs” be “CAS”? I’m unclear which entity does the signing, but if it is the customer AS, then it should be “CAS”. Page 8, 1st paragraph, 3rd sentence: insert “as” between “CAS” and “invalid”. Append a comma after “e.g.”
- [Gen-art] draft-ietf-sidrops-aspa-profile-27 earl… Peter Yee via Datatracker
- [Gen-art] Re: draft-ietf-sidrops-aspa-profile-27 … Job Snijders