BGP AS_PATH Verification Based on Autonomous System Provider Authorization (ASPA) Objects
draft-ietf-sidrops-aspa-verification-29
Revision differences
Document history
| Date | Rev. | By | Action |
|---|---|---|---|
|
2026-11-04
|
29 | Mohamed Boucadair | Changed document external resources from: None to: github_repo https://github.com/QratorLabs/ASPA/ |
|
2026-11-04
|
29 | (System) | Changed action holders to Mohamed Boucadair, Alexander Azimov, Eugene Bogomazov, Randy Bush, Keyur Patel, Job Snijders, Kotikalapudi Sriram (IESG state changed) |
|
2026-11-04
|
29 | Mohamed Boucadair | IESG state changed to AD Evaluation::Revised I-D Needed from Publication Requested |
|
2026-11-04
|
29 | Luigi Iannone | # 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: … # 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 |
|
2026-11-04
|
29 | Luigi Iannone | IETF WG state changed to Submitted to IESG for Publication from WG Consensus: Waiting for Write-Up |
|
2026-11-04
|
29 | Luigi Iannone | IESG state changed to Publication Requested from I-D Exists |
|
2026-11-04
|
29 | (System) | Changed action holders to Mohamed Boucadair (IESG state changed) |
|
2026-11-04
|
29 | Luigi Iannone | Responsible AD changed to Mohamed Boucadair |
|
2026-11-04
|
29 | Luigi Iannone | Document is now in IESG state Publication Requested |
|
2026-11-04
|
29 | Luigi Iannone | # 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: … # 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 |
|
2026-11-04
|
29 | Mohamed Boucadair | Med's AD Review: https://mailarchive.ietf.org/arch/msg/sidrops/Msg_rY_kods7O0S3L6hdUs3yE9s/ |
|
2026-10-23
|
29 | Tero Kivinen | Request for Early review by SECDIR is assigned to Prachi Jain |
|
2026-10-22
|
29 | Luigi Iannone | Requested Early review by SECDIR |
|
2026-10-16
|
29 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-29.txt |
|
2026-10-16
|
29 | Alexander Azimov | New version accepted (logged-in submitter: Alexander Azimov) |
|
2026-10-16
|
29 | Alexander Azimov | Uploaded new revision |
|
2026-09-25
|
28 | Luigi Iannone | Notification list changed to housley@vigilsec.com, ggx@gigix.net from housley@vigilsec.com because the document shepherd was set |
|
2026-09-25
|
28 | Luigi Iannone | Document shepherd changed to Luigi Iannone |
|
2026-08-24
|
28 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-28.txt |
|
2026-08-24
|
28 | Alexander Azimov | New version accepted (logged-in submitter: Alexander Azimov) |
|
2026-08-24
|
28 | Alexander Azimov | Uploaded new revision |
|
2026-08-03
|
27 | Luigi Iannone | IETF WG state changed to WG Consensus: Waiting for Write-Up from In WG Last Call |
|
2026-08-03
|
27 | Luigi Iannone | Changed consensus to Yes from Unknown |
|
2026-08-03
|
27 | Luigi Iannone | Intended Status changed to Proposed Standard from None |
|
2026-07-31
|
27 | Ketan Talaulikar | Request for Early review by BGPDIR is assigned to Serge Krier |
|
2026-07-31
|
27 | Ketan Talaulikar | Requested Early review by BGPDIR |
|
2026-07-20
|
27 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-27.txt |
|
2026-07-20
|
27 | Alexander Azimov | New version accepted (logged-in submitter: Alexander Azimov) |
|
2026-07-20
|
27 | Alexander Azimov | Uploaded new revision |
|
2026-07-20
|
26 | Peter Yee | Request for Early review by GENART Completed: Ready with Nits. Reviewer: Peter Yee. Sent review to list. |
|
2026-07-10
|
26 | Luigi Iannone | IETF WG state changed to In WG Last Call from WG Document |
|
2026-07-07
|
26 | Jean Mahoney | Request for Early review by GENART is assigned to Peter Yee |
|
2026-07-07
|
26 | Jean Mahoney | Requested Early review by GENART |
|
2026-07-06
|
26 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-26.txt |
|
2026-07-06
|
26 | Alexander Azimov | New version accepted (logged-in submitter: Alexander Azimov) |
|
2026-07-06
|
26 | Alexander Azimov | Uploaded new revision |
|
2026-04-19
|
25 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-25.txt |
|
2026-04-19
|
25 | Alexander Azimov | New version accepted (logged-in submitter: Alexander Azimov) |
|
2026-04-19
|
25 | Alexander Azimov | Uploaded new revision |
|
2025-10-19
|
24 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-24.txt |
|
2025-10-19
|
24 | Alexander Azimov | New version accepted (logged-in submitter: Alexander Azimov) |
|
2025-10-19
|
24 | Alexander Azimov | Uploaded new revision |
|
2025-09-23
|
23 | Russ Housley | Notification list changed to housley@vigilsec.com from morrowc@ops-netman.net, housley@vigilsec.com |
|
2025-09-23
|
23 | Russ Housley | Notification list changed to morrowc@ops-netman.net, housley@vigilsec.com from morrowc@ops-netman.net because the document shepherd was set |
|
2025-09-23
|
23 | Russ Housley | Document shepherd changed to Russ Housley |
|
2025-09-22
|
23 | Kotikalapudi Sriram | New version available: draft-ietf-sidrops-aspa-verification-23.txt |
|
2025-09-22
|
23 | (System) | New version approved |
|
2025-09-22
|
23 | (System) | Request for posting confirmation emailed to previous authors: Alexander Azimov , Eugene Bogomazov , Job Snijders , Keyur Patel , Kotikalapudi Sriram , Randy Bush |
|
2025-09-22
|
23 | Kotikalapudi Sriram | Uploaded new revision |
|
2025-03-23
|
22 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-22.txt |
|
2025-03-23
|
22 | Alexander Azimov | New version accepted (logged-in submitter: Alexander Azimov) |
|
2025-03-23
|
22 | Alexander Azimov | Uploaded new revision |
|
2025-03-16
|
21 | Kotikalapudi Sriram | New version available: draft-ietf-sidrops-aspa-verification-21.txt |
|
2025-03-16
|
21 | Kotikalapudi Sriram | New version accepted (logged-in submitter: Kotikalapudi Sriram) |
|
2025-03-16
|
21 | Kotikalapudi Sriram | Uploaded new revision |
|
2025-01-04
|
20 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-20.txt |
|
2025-01-04
|
20 | Alexander Azimov | New version accepted (logged-in submitter: Alexander Azimov) |
|
2025-01-04
|
20 | Alexander Azimov | Uploaded new revision |
|
2024-09-27
|
19 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-19.txt |
|
2024-09-27
|
19 | Alexander Azimov | New version accepted (logged-in submitter: Alexander Azimov) |
|
2024-09-27
|
19 | Alexander Azimov | Uploaded new revision |
|
2024-07-08
|
18 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-18.txt |
|
2024-07-08
|
18 | Alexander Azimov | New version accepted (logged-in submitter: Alexander Azimov) |
|
2024-07-08
|
18 | Alexander Azimov | Uploaded new revision |
|
2024-04-05
|
17 | Russ Housley | IETF WG state changed to WG Document from In WG Last Call |
|
2024-02-29
|
17 | Kotikalapudi Sriram | New version available: draft-ietf-sidrops-aspa-verification-17.txt |
|
2024-02-29
|
17 | Kotikalapudi Sriram | New version accepted (logged-in submitter: Kotikalapudi Sriram) |
|
2024-02-29
|
17 | Kotikalapudi Sriram | Uploaded new revision |
|
2023-08-29
|
16 | Kotikalapudi Sriram | New version available: draft-ietf-sidrops-aspa-verification-16.txt |
|
2023-08-29
|
16 | (System) | New version approved |
|
2023-08-29
|
16 | (System) | Request for posting confirmation emailed to previous authors: Alexander Azimov , Eugene Bogomazov , Job Snijders , Keyur Patel , Kotikalapudi Sriram , Randy Bush |
|
2023-08-29
|
16 | Kotikalapudi Sriram | Uploaded new revision |
|
2023-07-10
|
15 | Kotikalapudi Sriram | New version available: draft-ietf-sidrops-aspa-verification-15.txt |
|
2023-07-10
|
15 | (System) | New version approved |
|
2023-07-10
|
15 | (System) | Request for posting confirmation emailed to previous authors: Alexander Azimov , Eugene Bogomazov , Job Snijders , Keyur Patel , Kotikalapudi Sriram , Randy Bush |
|
2023-07-10
|
15 | Kotikalapudi Sriram | Uploaded new revision |
|
2023-04-19
|
14 | Kotikalapudi Sriram | New version available: draft-ietf-sidrops-aspa-verification-14.txt |
|
2023-04-19
|
14 | (System) | New version approved |
|
2023-04-19
|
14 | (System) | Request for posting confirmation emailed to previous authors: Alexander Azimov , Eugene Bogomazov , Job Snijders , Keyur Patel , Kotikalapudi Sriram , Randy Bush |
|
2023-04-19
|
14 | Kotikalapudi Sriram | Uploaded new revision |
|
2023-04-06
|
13 | Chris Morrow | IETF WG state changed to In WG Last Call from WG Document |
|
2023-03-27
|
13 | Kotikalapudi Sriram | New version available: draft-ietf-sidrops-aspa-verification-13.txt |
|
2023-03-27
|
13 | (System) | New version approved |
|
2023-03-27
|
13 | (System) | Request for posting confirmation emailed to previous authors: Alexander Azimov , Eugene Bogomazov , Job Snijders , Keyur Patel , Kotikalapudi Sriram , Randy Bush |
|
2023-03-27
|
13 | Kotikalapudi Sriram | Uploaded new revision |
|
2023-03-09
|
12 | Chris Morrow | Notification list changed to morrowc@ops-netman.net because the document shepherd was set |
|
2023-03-09
|
12 | Chris Morrow | Document shepherd changed to Chris Morrow |
|
2023-03-06
|
12 | Kotikalapudi Sriram | New version available: draft-ietf-sidrops-aspa-verification-12.txt |
|
2023-03-06
|
12 | (System) | New version approved |
|
2023-03-06
|
12 | (System) | Request for posting confirmation emailed to previous authors: Alexander Azimov , Eugene Bogomazov , Job Snijders , Keyur Patel , Kotikalapudi Sriram , Randy Bush |
|
2023-03-06
|
12 | Kotikalapudi Sriram | Uploaded new revision |
|
2022-10-24
|
11 | Job Snijders | New version available: draft-ietf-sidrops-aspa-verification-11.txt |
|
2022-10-24
|
11 | Job Snijders | New version accepted (logged-in submitter: Job Snijders) |
|
2022-10-24
|
11 | Job Snijders | Uploaded new revision |
|
2022-10-24
|
10 | Job Snijders | New version available: draft-ietf-sidrops-aspa-verification-10.txt |
|
2022-10-24
|
10 | Job Snijders | New version accepted (logged-in submitter: Job Snijders) |
|
2022-10-24
|
10 | Job Snijders | Uploaded new revision |
|
2022-07-11
|
09 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-09.txt |
|
2022-07-11
|
09 | Alexander Azimov | New version accepted (logged-in submitter: Alexander Azimov) |
|
2022-07-11
|
09 | Alexander Azimov | Uploaded new revision |
|
2022-02-26
|
08 | (System) | Document has expired |
|
2021-08-25
|
08 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-08.txt |
|
2021-08-25
|
08 | (System) | New version accepted (logged-in submitter: Alexander Azimov) |
|
2021-08-25
|
08 | Alexander Azimov | Uploaded new revision |
|
2021-02-22
|
07 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-07.txt |
|
2021-02-22
|
07 | (System) | New version accepted (logged-in submitter: Alexander Azimov) |
|
2021-02-22
|
07 | Alexander Azimov | Uploaded new revision |
|
2020-11-02
|
06 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-06.txt |
|
2020-11-02
|
06 | (System) | New version approved |
|
2020-11-02
|
06 | (System) | Request for posting confirmation emailed to previous authors: Job Snijders , Randy Bush , Keyur Patel , Alexander Azimov , Eugene Bogomazov |
|
2020-11-02
|
06 | Alexander Azimov | Uploaded new revision |
|
2020-09-10
|
05 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-05.txt |
|
2020-09-10
|
05 | (System) | New version approved |
|
2020-09-10
|
05 | (System) | Request for posting confirmation emailed to previous authors: Randy Bush , Eugene Bogomazov , Job Snijders , Keyur Patel , Alexander Azimov |
|
2020-09-10
|
05 | Alexander Azimov | Uploaded new revision |
|
2020-09-10
|
04 | (System) | Document has expired |
|
2020-03-09
|
04 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-04.txt |
|
2020-03-09
|
04 | (System) | New version approved |
|
2020-03-09
|
04 | (System) | Request for posting confirmation emailed to previous authors: Eugene Bogomazov , Keyur Patel , Alexander Azimov , Randy Bush , Job Snijders |
|
2020-03-09
|
04 | Alexander Azimov | Uploaded new revision |
|
2019-11-04
|
03 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-03.txt |
|
2019-11-04
|
03 | (System) | New version approved |
|
2019-11-04
|
03 | (System) | Request for posting confirmation emailed to previous authors: sidrops-chairs@ietf.org, Job Snijders , Alexander Azimov , Eugene Bogomazov , Keyur Patel |
|
2019-11-04
|
03 | Alexander Azimov | Uploaded new revision |
|
2019-11-04
|
02 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-02.txt |
|
2019-11-04
|
02 | (System) | New version approved |
|
2019-11-04
|
02 | (System) | Request for posting confirmation emailed to previous authors: Job Snijders , Alexander Azimov , Eugene Bogomazov , Keyur Patel |
|
2019-11-04
|
02 | Alexander Azimov | Uploaded new revision |
|
2019-07-08
|
01 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-01.txt |
|
2019-07-08
|
01 | (System) | New version approved |
|
2019-07-08
|
01 | (System) | Request for posting confirmation emailed to previous authors: Job Snijders , Alexander Azimov , Randy Bush , Eugene Bogomazov , Keyur Patel , sidrops-chairs@ietf.org |
|
2019-07-08
|
01 | Alexander Azimov | Uploaded new revision |
|
2019-05-17
|
00 | Chris Morrow | This document now replaces draft-azimov-sidrops-aspa-verification instead of None |
|
2019-05-17
|
00 | Alexander Azimov | New version available: draft-ietf-sidrops-aspa-verification-00.txt |
|
2019-05-17
|
00 | (System) | WG -00 approved |
|
2019-05-17
|
00 | Alexander Azimov | Set submitter to "Alexander Azimov ", replaces to draft-azimov-sidrops-aspa-verification and sent approval email to group chairs: sidrops-chairs@ietf.org |
|
2019-05-17
|
00 | Alexander Azimov | Uploaded new revision |