Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix typos, remove redundant paragraphs and adding new figure #2

Open
wants to merge 1 commit into
base: upstream
Choose a base branch
from

Conversation

tanneberger
Copy link
Member

@tanneberger tanneberger commented May 2, 2024

Changes

  • fixed a lot of typos and easy mistakes
  • added figure on the indices
  • added reference to Reference Implementation and RTRlib

@mitradir would you mind taking a look at it?

<t>
An ASPA record is a digitally signed object that binds a set of Provider AS numbers to a Customer AS (CAS) number (in terms of BGP announcements) and is signed by the CAS <xref target="I-D.ietf-sidrops-aspa-profile"/>.
The ASPA attests that the CAS indicated a Set of Provider ASes (SPAS), which applies only to the IPv4 and IPv6 address families (i.e., AFI = 1 and AFI = 2) and only to Network Layer Reachability Information used for unicast forwarding (SAFI = 1).
The definition of Provider AS is given in Section 1 of the ASPA profile object document <xref target="I-D.ietf-sidrops-aspa-profile"/>.
A function of a Provider AS is to propagate a CAS's route announcements onward, i.e., to the Provider's upstream providers, lateral peers, or customers.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-> explains what's the purpose of a provider in a section that is dedicated to the ASPA Record,

A CAS is expected to register a single ASPA listing all its Provider ASes (see <xref target="rec1"/>).
If a CAS has a single ASPA, then the SPAS for the CAS is the set of Provider ASes listed in that ASPA.
In case a CAS has multiple ASPAs, then the SPAS is the union of the Provider ASes listed in all ASPAs of the CAS.
A CAS is expected to register a single ASPA listing all its Provider ASes (see <xref target="rec1"/>), if
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

simplification of the sentence.

@@ -360,20 +343,37 @@ authorized(AS x, AS y) = / Else, "Provider+" if the VAP-SPAS entry
A valid path may have a one horizontal hop that represents peering relation.
</t>
<t>
<strong>Determination of Invalid AS_PATH:</strong>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Renamed this because all cases were explained with the help of the newly introduced indices.

@tanneberger tanneberger requested a review from waehlisch May 2, 2024 19:55
@tanneberger tanneberger self-assigned this May 2, 2024
@tanneberger tanneberger added the enhancement New feature or request label May 2, 2024
@tanneberger tanneberger force-pushed the draft-changes branch 2 times, most recently from da30a23 to 15fcb1f Compare May 2, 2024 20:34
@tanneberger tanneberger changed the title fix typos, remove redudent pharagraphs and adding indice figure fix typos, remove redundant paragraphs and adding new figure May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant