<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.39 (Ruby 2.6.10) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-sastry-spacerg-space-research-infra-typology-00" category="info" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.34.0 -->
  <front>
    <title abbrev="SpaceRG-Infra">A typology of Space Research Infrastructures</title>
    <seriesInfo name="Internet-Draft" value="draft-sastry-spacerg-space-research-infra-typology-00"/>
    <author fullname="Nishanth Sastry">
      <organization>University of Surrey</organization>
      <address>
        <email>n.sastry@surrey.ac.uk</email>
      </address>
    </author>
    <author fullname="Juan A. Fraire">
      <organization>Inria</organization>
      <address>
        <email>juan.fraire@inria.fr</email>
      </address>
    </author>
    <date year="2026" month="July" day="20"/>
    <keyword>simulators</keyword>
    <keyword>emulators</keyword>
    <keyword>testbeds</keyword>
    <keyword>in-orbit platforms</keyword>
    <keyword>datasets</keyword>
    <keyword>measurement tools</keyword>
    <keyword>implementations</keyword>
    <keyword>libraries</keyword>
    <keyword>visualizers</keyword>
    <keyword>research platforms</keyword>
    <abstract>
      <?line 55?>

<t>Space networking research increasingly relies on a heterogeneous ecosystem of software, datasets, experimental platforms, reference implementations, and operational research assets. These resources have historically been developed independently by different research groups, agencies, and projects, making discovery, comparison, interoperability, and reuse difficult. Existing registries typically catalogue tools individually but provide limited guidance on their functional role within the research lifecycle.</t>
      <t>This document proposes a typology for research infrastructures relevant to the Space Research Group (SPACERG). Rather than classifying resources according to implementation technology or project origin, the proposed taxonomy groups resources according to their research function. The typology provides a common vocabulary for describing software and non-software research assets, supports the organization of community registries, and facilitates interoperability, reproducibility, and long-term maintenance of research infrastructures. The classification is intended to evolve as new classes of research resources emerge. The typology is implemented by a machine-readable registry of research resources maintained by the research group.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="https://irtf-spacerg.github.io/id-leo-tools/draft-sastry-spacerg-space-research-infra-typology.html"/>.
        Status information for this document may be found at <eref target="https://datatracker.ietf.org/doc/draft-sastry-spacerg-space-research-infra-typology/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/irtf-spacerg/id-leo-tools"/>.</t>
    </note>
  </front>
  <middle>
    <?line 61?>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Research in space networking depends upon a broad collection of complementary research infrastructures. These include simulation environments, network emulators, protocol implementations, datasets, browser-based experimentation environments, visualization tools, experimental testbeds, satellite constellations, and software supporting data collection and analysis. While many of these resources have become widely adopted within individual research communities, they are often documented independently, use inconsistent terminology, and overlap in functionality.</t>
      <t>As the Space Research Group (SPACERG) develops a shared registry of research infrastructures, it has become apparent that simply maintaining a list of available tools is insufficient. Users require a consistent method of understanding <em>what role</em> a resource plays within the research ecosystem, how it complements other resources, and where it fits within an experimental workflow. A common typology also improves discoverability, assists researchers in selecting appropriate infrastructures, and enables more consistent metadata across independently maintained registries.</t>
      <t>The typology described in this document was developed through an analysis of the more than 110 verified research resources collected from the community and curated in the SPACERG registry. Rather than deriving categories from software architecture or implementation language, the classification emerged from the primary research purpose served by each resource. This functional approach accommodates both software and non-software research assets and remains applicable as new technologies are introduced.</t>
      <t>The initial categories identified include, under the names used by the registry:</t>
      <ul spacing="normal">
        <li>
          <t><strong>Simulator</strong>, modelling network behaviour using abstract representations (flow-level, packet-level, or discrete-event) to support scalable experimentation without executing real protocol stacks.</t>
        </li>
        <li>
          <t><strong>Emulator</strong>, reproducing the timing and topology of target systems while executing real protocol implementations and operating-system network stacks.</t>
        </li>
        <li>
          <t><strong>Testbed</strong>, offering physical, virtual, or hybrid environments with real links, such as terminal deployments and ground stations, for integrated experimental evaluation.</t>
        </li>
        <li>
          <t><strong>In-orbit platform</strong>, representing operational or experimental space assets (research satellites, constellations, and hosted payloads) that provide real-world experimentation opportunities.</t>
        </li>
        <li>
          <t><strong>Dataset / data</strong>, including curated measurement datasets and live data services such as orbital-element feeds.</t>
        </li>
        <li>
          <t><strong>Measurement</strong>, providing tools and methodologies that produce new measurements, including browser-integrated extensions, terminal-telemetry collectors, Internet-scanning methodologies, and benchmarking frameworks.</t>
        </li>
        <li>
          <t><strong>Implementation</strong>, providing runnable protocol stacks, proxies, and flight software deployed in experiments, such as Bundle Protocol implementations, non-terrestrial-network radio access stacks, and performance-enhancing proxies.</t>
        </li>
        <li>
          <t><strong>Library</strong>, providing reusable building blocks embedded by other resources, such as orbit propagators, contact-plan generators, and routing libraries.</t>
        </li>
        <li>
          <t><strong>Visualizer</strong>, supporting analysis, interpretation, and presentation of orbital and network state.</t>
        </li>
        <li>
          <t><strong>Research platform</strong>, offering orchestration and service environments for experimentation, such as satellite edge-computing and serverless frameworks.</t>
        </li>
      </ul>
      <t>The registry vocabulary additionally reserves a small set of auxiliary labels (Meta-resource, Commercial / service, Unresolved, Other) for resources that fall outside these research categories or that await classification.</t>
      <t>Although these categories provide broad coverage of the current SPACERG registry, they are not intended to be exhaustive. New categories may emerge as the community develops additional research infrastructures, including digital twins, AI-assisted experimentation platforms, workflow management systems, and cloud-based experimentation environments.</t>
      <t>The purpose of this document is therefore not to prescribe a fixed ontology, but rather to establish a common vocabulary that enables researchers to consistently classify and discover research infrastructures relevant to space networking. The taxonomy is intended to support the SPACERG registry, facilitate interoperability with other research infrastructure catalogues, and provide a foundation for future standardization efforts within the IRTF and IETF research communities.</t>
    </section>
    <section anchor="the-spacerg-registry">
      <name>The SPACERG Registry</name>
      <t>The typology in this document is implemented by a community registry maintained by SPACERG in the repository that also hosts this document, and published as a searchable page with JSON and CSV exports <xref target="REGISTRY"/>. Each resource is described by one machine-readable record carrying its class under this typology, functional metadata (how orbital dynamics are defined, which layers are covered, whether real protocol stacks are exercised, the largest scale demonstrated in a publication, and input and output formats), and provenance metadata (license, a named contact, how the entry was collected, and when it was last verified).</t>
      <t>Additions and corrections are made by pull request, one file per resource, and are validated automatically against the registry schema. To be included, a resource should be specific to space or satellite networking, usable by others through a public artifact or a documented access program, and verifiable through a working URL and, where claims matter, a publication.</t>
      <t>Registry entries are point-in-time observations: tools are abandoned, URLs move, and maintenance states go stale. Each record therefore carries a last-verified date and entries are re-verified periodically. Entries that fail verification are marked as historic rather than deleted, because unmaintained resources remain relevant as baselines against which published results were obtained.</t>
    </section>
    <section anchor="conventions-and-definitions">
      <name>Conventions and Definitions</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
      <?line -18?>

</section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>TODO Security</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
            <abstract>
              <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="REGISTRY" target="https://irtf-spacerg.github.io/id-leo-tools/registry/">
          <front>
            <title>SPACERG Space Networking Tools Registry</title>
            <author>
              <organization>IRTF Space Research Group</organization>
            </author>
            <date/>
          </front>
        </reference>
      </references>
    </references>
    <?line 132?>

<section numbered="false" anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>TODO acknowledge.</t>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAIijXWoAA5Va7XIbtxX9v0+BMn9sD5eK2sw05aRJGFl2lLElV5KTyXQ6
GXAXJBHtLlgAS4rJ+F36LH2ynnsB7AdFZ9wfibggFrif55576TzPM699peZi
shD+sDWVWR+EWYm7rSyUuFVOSVtsxFWzstJ52xa+tcpNMrlcWrXDa7zx9nXO
OyZZIb1aG3uYC92sTJaVpmhkjfNLK1c+d3TIIXf0kl2Hv7mNt+SazsiTGPnn
n2euXdbaOW0arOKUq8v7V0J8JmTlDC7XTam2Cv9r/GQqJqrU3lgtK3q4WnyH
P8bi0+39q0nWtPVS2XlWQsJ5VpjGqca1bi6glcqgyl8ynGuVnIvF7eUCD3tj
H9bWtNu5+Om1+AlPulmL17SSPagDvi7nmciF03VbSdzs6EkNH7xyfqlK/qyb
3Nil9mKL71fG1rwKcaRTnj/XSjqYt4Y6whtThdfqbcVL0sMMvFTppZVWK37Y
adfKSv+mwo3JmINbdqppofJnQnTa0EOw6FgtLNdSV3PBnvlWW7+aGbumdTp0
Ljbeb9387Ew9SpJrVpj6DMfhaO037ZJ8gneSg890mVfK5KzMBLsgEyyCXemc
4e5ZOGOmzei9s/8/dGYbX1eTLJOt3xhLTsLdQqzaqgrReK3dRjZ+I+74VP4W
espG/8Zmnov3jd7BpNqHdGitVWGbCgZqZkGgbx1/NZPFrH14etEPrWzEYiZe
WamtOnHPVYOAHR78K96YrXj7t5q+xEOWNfAk3tjBjxllVvckxO3l66u7+9uf
53xKTOe7d4uLy9vXMY+vld9HP9+TSZHYa90p7qVdK9/79lN8YuMBZ3xCZ2cR
FYReSLpjFAkxRls4CcUKaayybDabZVme50IucaQsfJaFF5te7C6sdVMgRx3W
qgNWK2SBMI2QYqO8smatGmVaJ1Rh3MF5VZP3nFn5PVJ72mXbVKjHrbKa86rq
c2WKI1fKqga3HyXeVMimFAZv8TPe6mSSjs6cifsNVmjZtLaAXBu5U2IDOwGU
CllB4KVSjSjVTlU4qBQD/KIvD6LUK77e94dzztLtUK2AtkGOrTW/qoIUqSUb
qNSuMIjYw1QgJ7eAB2eaKW4gq5DQS10hmMPbVrUQlC7TRVv5mbh8hJTBzuxX
siqSKUoNUJdIq1YFVCKx9U6XbVCp9SQNnhWAqdYeeq1bXUqyITzjN0pbZERT
JLOZSok9wkrzl72mlV6p4lAAVbLsHmYTKB4tgyHO3xoHmWRfpOCvYVSM6hMF
htpJhlG+41QgimcxSZ7PxK3ELoutyNaigj/16hDDLvpSFgXwntZw5Dg0gPLF
poml0ybX4KNea7iA7o8KlMi1R9OY+hDd+rELgtE69ZL1OMR6E0Szk1ng8xqS
7Ewhl6g/NtgH3xVWL+nQlAPs/8Y0ebdwFMZT4drt1ljvWPIhWlEu0UVtQ7DY
h0oIqpUsKMQI4U+EnVWQtmwLPYzDyjTrHDtrqjp4pQlBs/qoY4MBoocQnSyV
DvchjUqyndqZCnknHfBjH/YSRgwO7Y0OJwL7jsxK5yUH40ikpYR8BeKVCo4s
5bJSSfvDRw5mffBfeH8U5uz5iHi1LssKEPgZ6oBn+5BGWZbd9gYItXgIhgE0
nGi3jHxLa2QJx1SVKgZuSiFqD39sTiABQLVqkb+RydAZqtlpaxo6Af6Nl/fk
ZkrB5w0ufYqTPchCsr1TNl9Kiv0B5J64IvGYmFIENEconcgUIhRBViGMEAq4
kT4PMbqL7BjIbDLINDQR7ZNAo4PTsMJPGw2X1rJhd/pTML5ERakJt0oF0JOl
2VJsRBjrAbE3dUoUzg8ceSByieM9VYAIbMclYCra4A3oguhiHojs0AFcYgUC
yFdyS4HRgyoyChG1cJ8Adqn8EGqABFlVno7lo1BBKfGwhEuGkFvUGBZwIz0F
zhZmSVFPFpfAc+fpSLkDseGkieWD8tW1VHw0TpiJ94gRgsJ/t5oASgzUrxWY
RUmntLCRdR4moNN/2dO1VEp+wQvJV1TID+5kcekIwVRszJ6U6VME6MDw37k8
WHqPNUU7V9p3h6JAjIKS0mJVmf1MLBIId0BCXQqlB2AaYZQqdF+JHWnpOhnJ
CJTuioOUTLilugEK6NVTd5CEAEyYFWhjrDqymuSIl4U1zh3xjAE29RjONXcA
grF0cITCksNqvEcU9BzGbxBf6w0ZJiVUTKIgFtfU8/PPBVQHZvOlT+AyZia+
XFlT88t9oSFNixa0KwmjOnqbIndcwREoSEcYMHajxGb43L4I4nrAB9uSavZR
Qa9ks25BuELxPio3oWYMJIWH6hHKbltL1R6etLtQAJQcqEuoCyMNKBE7mrYQ
CUAMlVxEl4jKT6/bkdiRcx0dWEFeyrlYBzuOQsag13UsOKqMrtcEVhBmYDRN
EROcFkvENOQh600djiPEGtS44A40KTlY/osXd6k1fvECTNWUhNrwSyonSwVs
1TAKTuGAjw0AswWol2qKeEYphvYDQYfKI4sH5dMT0RxklgX9z7HS+OdEAiL0
CwcGy2Y4Lj6UzgbUVT2qoo3UlzqBVNWANMUDsiLocTlQo2MyRNUoZUB6SfaG
2Ec/QQldlQigA/jgEvOx245q6LDVAEOKnUyy2li0+1AVSTJDzQMdvt0gDaE5
VVXrWxnMtDksrS5HZZfNEGSBYx6Y/HFExbqDdSBHZQ5hN4lF9IWKbFfuiWgS
/1qHDB2hI0h41fLGJO7V8RQkmZTdTcIPWywcPTovUKEY8M+6DOj4gJueZAQb
40i0rTxUoErueShaqWsh9XNYtnpKUQxHUSzjSYWXgd+IM2YVJH9IDkaciFPD
UU7iQ4HyomsPbITQQRP4JZOzXSCKCqEgVgpkJ136tj+Qbgyyh26BaiodHWpl
yvGkIqU4I8BAJDcUOZG0kQ9RRlywXwoE8HSSi2hCRGumgVfE9BGZOTKt4cI/
EiPYf4nWdQOMZPaKOlYrCuROt6tR9I/Vs23DRe44M3nPY998VHq98T1ahqgN
BaN36iC+v0MQ49R3H2WxhLVQDTHmaaSYp+yzstSGgFqhsCZZuCVXlucyaGFy
1aAOMUJEKZOqb3h0dzjSEe0467hsdRV8Uhmci1KDzC4Dvj6hKKOw4Q5TriM3
Rw5AMJ8jxxpBIxEbv+AaYQICdVPEJNuP3SSRxBuQ51TX4zgBuRqslEYRPVIT
8MUwDgWrhyyv0j23xyPKEXYZYkJUBjqeHhNlDFyrMTQEcZJJ+v5AlWuVE9Nr
fQJprsq2IvcNQ5FrYMeEB420LEsd4KgKNd7uuOV2NVYEAQFx3PYRrI62o9wo
JOSztzBSntw1FReo68oWVGDPkkZT8b6hHWhXy6m4IQc/T3ONSIw4i1d0Ebzm
CK267iS2GX21NjZsl3tJ9HbEWqg7qKjigamFEwYvJiBMjSSR1LVKLK6gASfg
6JhzDbqaxvhRC76kSreRraMZ5UxcUx/eX1fLQyRRXGhGXK9vTjqr/1FL0oFY
qdccdH6vKXkXV3lg1yfazsGwL5F3av2gMaNuLNghtovKtOUntK8xfBLxY8sN
KbNmPa1amWgtGInyhik2YmmlH3EDsjY2ejRUs5HRGoF0ADxotzk56GGfp05g
2Evgzb4noDFeHGyxZqkb+bQZ2vEIIk5M0jDraAKTyNcppj4dzImejIkCHemQ
7pRc/TCyn4Ry8MKIREyCbyiJVi3v55ZR2jJNFtRqxcOtQZPIs2o6i39eOtXB
z2hEcz9Qpxugj7umJ73SqVnSkxHa4WhclC7pelgEFf2yFX3NbSVRGje+LNqj
5VDBSZJRinUJFZSSmi38w93NNW++uPuR4poN8vvv6ZeEDx9m4nLYsZAafUNI
xahRp0ZiNMGEg6zl4Sl1zRxzXc+gXWeq6bD/6frVZ9SbpwJSHtBh6CK0K6Va
kXmmRKRpViwPFOKS+16EcfhGxch5SuR5J9g3ENjRXrJrRQzdhR6BLqiJOXZt
pgyWLAaVTjcoI4Gbt54+ht9h3PM+EuMIs1cIJ4BKAeol90tlqs1hDEFiwHPw
LDXVXRfczR8aGj/QVzCj7zro54TmER8D9YPhbZhsBU1rSXB+gApVxYMV6Dll
r62oDdkOmES4i14CV9clqy9bb+gHpjD+B60AqPpRhwejbdBrAgcY7WN3SIL3
QeNQbioif4APVVAp6qEE+dkX6R5XaAAWmFAkPK6fL0R/QFS0pJIH7FgcjNIi
J4MbQGProFcwWRg+dQelOer72ze0aRonPYhVXVN58kCl6TgAZjSSjaqTw1IX
vTVIXFDnHF0gtFpSZQ8Mcp6YOfXuS1xjOHxxJ81rdtHuw7m3C7PztaFPlepy
kLOqLx+UX3w9B0XejVXIdXEq1MtnVb+Bypcpg1NxeNwVGYauoq3ilCNEkX0I
OJJ+xOqKUhizVIqDdakKSYPLthmNlhKHCUOJvp7QEBEVFQ0nCRmDK6R1D154
va0IpskzZhkOZRi+MA21+V3svyRkCLkQ0PgBrIR+nHdi8vb93T39YwD6K65v
+PPt5T/eX91evqTPd98v3rzpPmRxx933N+/fvOw/9W9e3Lx9e3n9MryMVTFa
yiZvFz9PgmMnN+/ur26uF28mT4sC2dbHvIl8ms2cjYZu3128++9/zr8ALv/p
9tXFn8/P//bhQ3z48vyvX+CBACIOhRvkaXgkUpbJ7Ra4zzBW0URnS4BKBdNR
Vu4bQdEEa774J1nmX3Px1bLYnn/xdVwghUeLyWajRbbZ05UnLwcjnlg6cU1n
zdH6kaXH8i5+Hj0nuw8Wv/qGYk3k519+83WWUQzdKbBaqsAXRJDKOHCg+Ll5
edN9y1uvFteLp9tG/qSxeGPCThlQGLblH3iWKD50yqJ4aMy+QjvCfDH7fR7+
PYoq/z7hn8EnH+LlstsJB/0Psn1asqEjAAA=

-->

</rfc>
