Hi Tony and Eliot, Thank you for your replies. We have updated the document accordingly.
Tony - We have two followup questions: A) Regarding: >> 8) <!--[rfced] Please clarify "into the global Internet" in this >> sentence. Do gateways advertise prefixes to cover all of their >> local user stations perhaps "across the global Internet" or >> "including those in global Internet"? >> >> Original: >> Gateways and their supporting terrestrial networks advertise >> prefixes covering all its local user stations into the >> global Internet. >> >> Perhaps: >> Gateways and their supporting terrestrial networks advertise >> prefixes to cover all its local user stations across the >> global Internet. >> --> > > Specifically, gateways would be using BGP to advertise the prefixes for the > local user stations. As usual, BGP would propagate the information throughout > all of the autonomous systems of the entire Internet. I view this as > injection “into” the Internet as the information necessarily ends up residing > in all transit operators. The word “across” would imply to me that transit > systems are not involved, which is not the case. These directional prepositions are quite difficult when it's conceptual and not physical directions. With your explanation above in mind, would "throughout" instead of "covering" be a more accurate word choice for conveying the intended meaning? Perhaps: Gateways and their supporting terrestrial networks advertise prefixes throughout all its local user stations and into the global Internet. B) Regarding: >> 9) <!-- [rfced] Please clarify what "this" in "this architecture" refers >> to. Is it the "forwarding plane" or "on-stripe" architecture? >> >> Original: >> 6. Traffic Forwarding and Traffic Engineering >> >> Forwarding in this architecture is straightforward. >> >> Perhaps: >> 6. Traffic Forwarding and Traffic Engineering >> >> Forwarding in the forwarding plane architecture is straightforward. >> --> > > The whole document presents a single architecture: routing, addressing, and > forwarding are all coupled. Since "this" appears to be referring to the entire document, may we then update to the following? Perhaps: 6. Traffic Forwarding and Traffic Engineering This document's forwarding architecture is straightforward. The updated files have been posted here (please refresh): https://www.rfc-editor.org/authors/rfc9717.txt https://www.rfc-editor.org/authors/rfc9717.pdf https://www.rfc-editor.org/authors/rfc9717.html https://www.rfc-editor.org/authors/rfc9717.xml The relevant diff files have been posted here (please refresh): https://www.rfc-editor.org/authors/rfc9717-diff.html (comprehensive diff) https://www.rfc-editor.org/authors/rfc9717-auth48diff.html (AUTH48 changes only) Note that it may be necessary for you to refresh your browser to view the most recent version. For the AUTH48 status of this document, please see: https://www.rfc-editor.org/auth48/rfc9717 Thank you, RFC Editor/st > On Jan 21, 2025, at 4:03 PM, Independent Submissions Editor (Eliot Lear) > <rfc-...@rfc-editor.org> wrote: > > I like it. > > On 21.01.2025 22:17, Tony Li wrote: >> >> >>> On Jan 21, 2025, at 1:00 PM, Independent Submissions Editor (Eliot Lear) - >>> rfc-ise at rfc-editor.org <mailforwa...@cloudmails.net> wrote: >>> >>> Hi! >>> All good with what Tony wrote, but perhaps here... >>> On 21.01.2025 21:37, Tony Li wrote: >>>> The goal of the routing architecture is to provide an organizational >>>> structure to protocols running on the satellite network such that >>>> topology information is conveyed through relevant portions of the >>>> network, paths are computed across the network, data >>>> can be delivered along those paths, and the structure can scale >>>> without any changes to the organizational structure. >>>> >>> That sentence is a mouthful and there's a very minor tense problem. I >>> think you're being just a bit too terse, but I won't stand on my head on >>> this. Do you want to take another swing? >>> Eliot >> >> Ok, less terse: >> >> The goal of the routing architecture is to provide an organizational >> structure to protocols running >> on the satellite network. This architecture must convey topology information >> to relevant portions >> of the network. This enables path computation that is used for data >> forwarding. The architecture >> must also scale without global changes to the organizational structure. >> >> Please feel to massage as you see fit. >> >> Thanks, >> T >> -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
