Human Readable ASPA Notation

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 24 April 2025.¶

Copyright Notice

Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1. Requirements notation

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶

2. Introduction

This informational document defines a human readable ASPA notation for Validated ASPA Payloads (VAPs) [I-D.ietf-sidrops-aspa-profile].¶

The main motivations for providing this notations style are: * This can help to create consistency between RPKI Relying Party software output, making it easier for operators to compare results. * This can be used by RPKI Certificate Authorities (CA) command line interfaces and/or configuration. E.g. allowing a CA to provide a listing of intended VAPs which can be easily compared to RP output. * This can be used for documentation.¶

That said, this definition is informational. Implementations can choose to use their own notation styles instead of, or in addition to this.¶

3. ASPA Notation Definition

This specification uses ABNF syntax specified in [RFC5234].¶

notation            = customer-asid separator providers

customer-asid       = asn
separator           = " => "

providers           = providers-one-line / providers-multiline
providers-one-line  = asn *(*wsp "," *wsp asn)
providers-multiline = "[" *wspml asn *(*wspml "," *wspml asn) *wsp "]"

asn                 = "AS" uint32
uint32              = %d0-4294967295

wsp                 = space / tab

wspml               = space / tab / cr / lf

cr                  = %d13
lf                  = %d10

space               = %d32
tab                 = %d8

4. Example Notations

Some example notations are listed below. The last example is not advised for readability but is technically allowed by this specification.¶

AS65000 => AS65001
65000 => AS65001
65000 => AS65002
AS65000 => AS65001, AS65002,AS65003

AS65000 => [ AS65001, AS65002, AS65003 ]

AS65000 => [
    AS65001,
    AS65002,
    AS65003
]

AS65000 => [AS65001,
                     65002
,AS65003
    ]

5. IANA Considerations

This document has no IANA actions.¶

6. Security Considerations

TBD¶

7. Acknowledgements

Thanks to Randy Bush for suggesting to allow only one possible notation for AS numbers.¶

Authors' Addresses