RFC 9717: A Routing Architecture for Satellite Networks
In plain English — editorial summary, not part of the RFC
Satellite networks present some interesting challenges for packet networking. The entire topology is continually in motion, with links far less reliable than what is common in terrestrial networks. Some changes to link connectivity can be anticipated due to orbital dynamics. This document proposes a scalable routing architecture for satellite networks based on existing routing protocols and mechanisms that is enhanced with scheduled link connectivity change information. This document proposes no protocol changes. This document presents the author's view and is neither the product of the IETF nor a consensus view of the community.
Document record
- Document ID
- RFC9717
- Published
- January 2025
- Authors
- T. Li
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9085Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment RoutingUpdated
August 2021
- RFC 8667IS-IS Extensions for Segment RoutingCurrent
December 2019
- RFC 9351Border Gateway Protocol - Link State (BGP-LS) Extensions for Flexible Algorithm AdvertisementCurrent
February 2023
- RFC 9294Application-Specific Link Attributes Advertisement Using the Border Gateway Protocol - Link State (BGP-LS)Current
August 2022
- RFC 8666OSPFv3 Extensions for Segment RoutingCurrent
December 2019
- RFC 8665OSPF Extensions for Segment RoutingCurrent
December 2019
- RFC 8287Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data PlanesUpdated
December 2017
- RFC 9666Area Proxy for IS-ISCurrent
October 2024
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?