<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.sriram-sidrops-asra-verification" target="https://datatracker.ietf.org/doc/html/draft-sriram-sidrops-asra-verification-04">
   <front>
      <title>Autonomous System Relationship Authorization (ASRA) as an Extension to ASPA for Enhanced AS Path Verification</title>
      <author initials="K." surname="Sriram" fullname="Kotikalapudi Sriram">
         <organization>NIST</organization>
      </author>
      <author initials="N." surname="Geng" fullname="Nan Geng">
         <organization>Huawei</organization>
      </author>
      <author initials="A." surname="Herzberg" fullname="Amir Herzberg">
         <organization>University of Connecticut</organization>
      </author>
      <date month="May" day="15" year="2026" />
      <abstract>
	 <t>   Autonomous System Provider Authorization (ASPA) record authorizes
   provider ASes of a customer AS (CAS).  While ASPA-based AS_PATH
   verification can correctly detect and mitigate route leaks and some
   forged-origin or forged-path-segment hijacks, it fails to detect some
   malicious path manipulations for routes that are received from
   transit providers.  This document utilizes a new RPKI object called
   Autonomous System Relationship Authorization (ASRA) that
   significantly enhances AS_PATH verification complementing ASPA.  ASRA
   fills in a significant gap in the ASPA method by adding the
   capability to detect fake links in the AS_PATHs in BGP Updates
   propagated from providers to customers.  ASRA achieves this by
   allowing an AS to register additional AS relationships, i.e.,
   customers and lateral peers.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-sriram-sidrops-asra-verification-04" />
   
</reference>
