# Document Shepherd Write-Up for Working Group Documents
Document: https://datatracker.ietf.org/doc/draft-ietf-sidrops-aspa-verification/
Title: BGP AS_PATH Verification Based on Autonomous System Provider
Authorization (ASPA) Objects
Revision: draft-ietf-sidrops-aspa-verification-29
Shepherd: Luigi Iannone (ggx@gigix.net)
## Document History & Implementations
1. Have the Chairs confirmed Working Group (WG) consensus for this document?
Did they indicate any issues to be called out with regard to that rough
consensus? If so, what were they?
This document passed Working Group Last Call, confirmed by the Chairs,
showing a broad support for this document. No issues were raised.
2. Indicate any significant disagreement in the WG about whether or not this
document falls within the current charter.
THis document falls in whithin the current charter.
3. If anyone threatened an appeal or otherwise indicated extreme discontent,
please summarize the areas of conflict in separate email messages to the
responsible Area Director.
No controversy. The document had some delay waiting for related two
related documents, namely [draft-ietf-sidrops-aspa-profile] and
[draft-ietf-sidrops-8210bis].
4. For protocol documents, indicate whether the document adheres to the WG
implementation policy (if any). Also, indicate whether there are existing
(or planned) implementations and, if so, where they are listed.
([RFC 7942][3] recommends they be reported in the document itself).
The document adheres to the WG implementation policy. As section 10 of
the document describes in details, there are several existing
implementations.
## Additional Reviews
5. Have reviews for the document happened in other IETF WGs or external
organizations that you are aware of? If so, please provide references to
those reviews (if any).
N/A
6. Describe the results of formal expert reviews (e.g., media type, URI) that
the document has undergone. Also, indicate whether any of the required
reviews are missing.
N/A
7. If the document contains a YANG module, does the document’s Datatracker page
indicate that it has no errors and warnings?
N/A
Has a YANGDOCTOR review been done on a recent version, indicating that it is
ready for publication?
N/A
Does the document use the various templates in [RFC 9907][4] (mainly, YANG
module, Security, and IANA templates)?
N/A
8. Describe all reviews and automated checks performed to validate sections of
the document written in a formal language, such as XML, JSON code,
ABNF/RBNF/BNF rules, ASN.1, CBOR CDDL, etc.
N/A
9. Does the document describe any protocol elements that are intended for human
interpretation and understanding? If so, does the document contain an
Internationalization Considerations section that describes how those
protocol elements are suitable for international use?
N/A
## Document Shepherd Checks
10. Confirm that (in your opinion) this document is clearly written, complete,
technically accurate, correctly designed, and ready to be handed off to the
responsible Area Director.
The document is clearly written, needed, and ready to be handed off to
the responsible AD.
11. Several IETF Areas have assembled
[lists of common issues that their reviewers encounter][5]. Have such
issues been identified and addressed? For which areas are subsequent
reviews believed particularly important to happen?
The document does not touch any ops issue.
12. What type of RFC publication is being requested
([Best Current Practice][6], [Proposed Standard, Internet Standard][7],
[Informational, Experimental, or Historic][8])?
The document requests to be published as Proposed Standard.
Why is this the appropriate type of RFC?
It is the right publication type as it is intended to be part of the
RPKI to Router protocol version 2 [draft-ietf-sidrops-8210bis] and
[draft-ietf-sidrops-aspa-profile] which are also Proposed Standard.
13. Will publication of this document change the status of any existing
RFC(s)? If so, does the Datatracker status page for this document correctly
list those RFCs on the Title page, in the Abstract, and in the Introduction
of the document?
This document does not change the status of any existing RFC.
14. If the document uses [BCP 14][9] key words, does the document follow the
guidance in the
[IESG Statement on Clarifying the Use of BCP 14 Key Words][10]?
Is there any use of the BCP 14 key words that could be considered unclear
or inappropriate? Please flag those.
Nothing to flag.
15. Confirm that reasonable efforts have been made to remind the WG (including
the document authors, editors, and contributors) about the intellectual
property rights (IPR) disclosure obligations described in [BCP 79][11].
IPR disclosure obligations have been reminded to authors at various
occasions, including during WGLC:
https://mailarchive.ietf.org/arch/msg/sidrops/m21U8hZPigPYV_TKnU4ZwsHtuus/.
Also, the chairs reached out to authors
https://mailarchive.ietf.org/arch/msg/sidrops/v1AYBOiIos5Yua_A0rH_s-6x2Kw/
All the co-authors, did state explicitly that they are not aware of any
IPR related to this document. No one else did any IPR disclosure.
16. Confirm that each author, editor, and contributor has shown their
willingness to be listed as such. If the total number of authors and
editors on the front page is greater than five, please provide a
justification.
Each co-author is clearly willing to be listed as such.
All listed authors have significantly contributed to the specification.
17. Please list any remaining I-D nits in the version of the document you
reviewed that you feel are actual errors. Simply running the
[idnits tool][12] is not enough; please review the
["Content Guidelines" on authors.ietf.org][13]. Idnits may display false
positives; please flag those and please briefly explain as needed.
(NOTE: No need to provide explanation for common false positives that are
self-explanatory such as the existence of a newer version of referenced
I-D)
No error to be listed.
### Document References
18. List any informative references that should be normative or vice-versa?
If so, please list those.
No reference should change type.
19. List any normative references that are not freely available to anyone.
Does the community have sufficient access to review these references?
There is no reference with restricted access.
20. List any normative downward references (see [RFC 3967][15] and
[BCP 97][16]) that are not already listed in the [DOWNREF registry][17].
IDNITS indicates two DOWNREF, namely RFC6480 and RFC 7908. RFC6480 is
already listed in the DOWNREF registry. RFC7908, should be added as
ASPA specifically protects against some form of BGP Route Leaks, hence
the knowledge on the different kind of BGP Route Leaks as described in
that RFC is paramount to understand the level of protection.
21. List any normative references to documents that are not ready to be
submitted to the IESG for publication or are otherwise in an unclear
state. For each, indicate the plan for their completion, if known.
[I-D.ietf-sidrops-aspa-profile] is normative, however, the document has
already passed WGLC and will advance in parallel. Other than that, no
references are in unclear state or not ready.
### IANA Considerations
22. Describe your review of the IANA considerations section, especially its
consistency with the body of the document.
N/A
Confirm that all IANA requested actions are associated with the
appropriate reservations in IANA registries.
N/A
Confirm that any referenced IANA registries have been clearly identified.
N/A
Confirm that each newly created IANA registry specifies its initial
contents, allocation procedures, and a reasonable name (see
[RFC 8126][18]).
N/A
23. List any new IANA registries that require Designated Expert Review for
future allocations (Expert Review, Specification Required). If any, please
confirm that the document includes guidelines for Designated Experts. Are
these instructions to the Designated Expert clear?
N/A