Internet DRAFT - draft-blanchet-regext-rdap-space
draft-blanchet-regext-rdap-space
Internet Engineering Task Force MB. Blanchet
Internet-Draft 24 October 2022
Intended status: Standards Track
Expires: 27 April 2023
RDAP Query and Response for Space Objects and Networks
draft-blanchet-regext-rdap-space-00
Abstract
Objects and networks in space are owned by entities, have locations
and have identity or network address. This document describes
Registration Data Access Protocol(RDAP) queries and response for
these space objects and networks.
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 27 April 2023.
Copyright Notice
Copyright (c) 2022 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.
Blanchet Expires 27 April 2023 [Page 1]
Internet-Draft Abbreviated Title October 2022
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. OID Path Segment . . . . . . . . . . . . . . . . . . . . 3
2.2. CBHE Node Numbers Path Segment . . . . . . . . . . . . . 3
2.3. Others TBD: assets, service sites, ... . . . . . . . . . 4
3. JSON Responses . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. ObjectClassName: entity . . . . . . . . . . . . . . . . . 4
3.2. Node Id . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.3. ObjectClassName: serviceSite . . . . . . . . . . . . . . 4
3.4. Aperture . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Transport . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. Finding Authoritative Servers . . . . . . . . . . . . . . . . 6
5.1. OID Bootstrap Registry . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7
8.2. Informative References . . . . . . . . . . . . . . . . . 7
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
Objects and networks in space are owned by entities, have locations
and have identity or network address. The space community through
the Consultative Committee for Space Data Systems[ccsds] has setup
registres[sana] and its related policies. These registries are
managed by the Space Assigned Numbers Authority (SANA) that documents
those properties for space objects and networks. Instead of
reinventing another access protocol for registration data access,
this document extends the Internet Registration Data Access
Protocol(RDAP) (STD95) used for domain names, IP addresses and AS
numbers by defining new queries and responses for the space objects
and networks.
Except if explicitly specified or not relevant, all considerations of
[RFC9082], [RFC9083] are herein inherited.
1.1. Requirements Language
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.
Blanchet Expires 27 April 2023 [Page 2]
Internet-Draft Abbreviated Title October 2022
2. Queries
This section is inspired and somewhat supplements [RFC9082] by adding
new queries.
In order to avoid any future name collision when an RDAP server may
be answering both Internet domain names and IP addresses queries as
well as this specification queries, the "space" keyword is prefixed
in the path for the queries in this specification.
Examples in this section use "https://examplespacerdapserver.org/
rdap" as the URL prefix before the specified query path segment.
2.1. OID Path Segment
Syntax: space/oid/<oid>
Space objects, assets, organizations and networks are managed using
unique identifiers based on the ISO Object Identifier hierarchy
(OID). Therefore, any object may be queried using its OID. The OID
must be provided from the ISO root. The OID is specified in its
native form, which is number.number.number.number ... Response
format for each kind of object is specified in the Response section
in this document.
Examples:
* https://examplespacerdapserver.org/rdap/space/oid/1.3.112.4.7.84
returns the data for the NASA Mars Reconnaissance Orbiter
spacecraft.
* https://examplespacerdapserver.org/rdap/space/oid/1.3.112.4.34.1
returns the data for a range of Bundle Protocol Node numbers
belonging to NASA Goddard.
2.2. CBHE Node Numbers Path Segment
Syntax: space/cbhe/<number-range>
Bundle protocol CBHE node numbers[RFC5050] are specified by a range
of two unsigned integers separated by '-'. In case of a single node
number, only the number is specified.
Examples:
* https://examplespacerdapserver.org/rdap/space/cbhe/100-256 returns
the data for this range.
Blanchet Expires 27 April 2023 [Page 3]
Internet-Draft Abbreviated Title October 2022
* https://examplespacerdapserver.org/rdap/space/cbhe/45623 returns
the data for this specific node.
2.3. Others TBD: assets, service sites, ...
TBD
3. JSON Responses
As JSON is liberal for adding new properties that receivers should
ignore when they are unknown, it is forseen that some space RDAP
registries may add more properties in their response than those
specified in this document.
This section inherits all considerations of [RFC9083] except noted.
3.1. ObjectClassName: entity
Use JSContact instead of jCard as in RFC9083
3.2. Node Id
3.3. ObjectClassName: serviceSite
Blanchet Expires 27 April 2023 [Page 4]
Internet-Draft Abbreviated Title October 2022
{
"objectClassName": "serviceSite",
"OID": "1.3.112.4.9.76",
"Name": "Svalbard",
"Abbreviation": "SVLBRD",
"Aliases": [],
"Location Type": "Surface",
"Planetary Body": "Earth",
"Country": "Norway",
"City": "Svalbard",
"Latitude": "-02.996090",
"Longitude": "+040.194663",
"Elevation": 456.01,
"Trajectory": null,
"Orbit": null,
"Spacecraft": null,
"Requestor": "1.3.112.4.2.222",
"Affiliation": "1.3.112.4.1.37",
"Apertures": [
"1.3.112.4.9.76.1",
"1.3.112.4.9.76.2",
"1.3.112.4.9.76.3"
],
"Owner": "1.3.112.4.1.37",
"CreatedBy": "1.3.112.4.2.2",
"Creation date": "2018-11-01T14:21:19.891375+00:00",
"UpdatedBy": "1.3.112.4.2.2",
"Update date": "2018-11-01T15:00:00.255626+00:00"
}
TBD: explain the syntax of all properties
3.4. Aperture
Blanchet Expires 27 April 2023 [Page 5]
Internet-Draft Abbreviated Title October 2022
{
"OID": "1.3.112.4.9.76.3",
"Name": "SDA5",
"Aliases": [],
"Forward Links": [],
"Return Links": [
"1.3.112.4.9.76.3.1"
],
"Location Type": "Surface",
"Planetary Body": "Earth",
"Latitude": "+781339.72",
"Longitude": "+0152531.8",
"Elevation": 460.68,
"Diameter": null,
"Aperture Type": null,
"Pointing Constraints": [],
"Available Services": [],
"Created By": "1.3.112.4.2.2",
"Creation date": "2018-11-01T14:58:33+00:00",
"Updated By": "1.3.112.4.2.2",
"Update date": "2018-11-01T17:54:58.889530+00:00"
}
TBD: explain the syntax of all properties
4. Transport
This document assumes that queries about space objects and networks
are done on the regular Internet to servers located on Earth,
therefore the transport of such queries would use the same transport
as specified by standard RDAP queries for domain names or IP
addresses. It should be possible to carry those queries in space
over an appropriate transport, such as DTN. However, this
specification does not describe such transport.
5. Finding Authoritative Servers
The space community runs a service similar (and in fact inspired by)
to IANA, named Space Assigned Numbers Authority (SANA) [sana].
Similar to [RFC9224], this document specifies the bootstrap registry
located at IANA with initial values.
5.1. OID Bootstrap Registry
IANA will setup a new bootstrap registry for OIDs. The keys are the
root of the OID subtree delegated to a specific RDAP server. The
registry will be initially populated with a single entry:
["1.3.112.4"], ["https://rdap.sanaregistry.org/"]
Blanchet Expires 27 April 2023 [Page 6]
Internet-Draft Abbreviated Title October 2022
6. IANA Considerations
TBD
7. Security Considerations
All security considerations of STD95 are herein inherited. While
space assets and objects may have higher security risks than Earth
equivalents, nothing in this specification add more security risks as
the information of such assets is public. As with Internet RDAP,
some information may be redacted (see TODO: internet draft redacted)
when confidentiality is required. Moreover, authentication and
authorization mechanisms such as TODO: openid-draft may be used to
access more confidential data.
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC9082] Hollenbeck, S. and A. Newton, "Registration Data Access
Protocol (RDAP) Query Format", STD 95, RFC 9082,
DOI 10.17487/RFC9082, June 2021,
<https://www.rfc-editor.org/info/rfc9082>.
[RFC9083] Hollenbeck, S. and A. Newton, "JSON Responses for the
Registration Data Access Protocol (RDAP)", STD 95,
RFC 9083, DOI 10.17487/RFC9083, June 2021,
<https://www.rfc-editor.org/info/rfc9083>.
[RFC9224] Blanchet, M., "Finding the Authoritative Registration Data
Access Protocol (RDAP) Service", STD 95, RFC 9224,
DOI 10.17487/RFC9224, March 2022,
<https://www.rfc-editor.org/info/rfc9224>.
[RFC5050] Scott, K. and S. Burleigh, "Bundle Protocol
Specification", RFC 5050, DOI 10.17487/RFC5050, November
2007, <https://www.rfc-editor.org/info/rfc5050>.
8.2. Informative References
Blanchet Expires 27 April 2023 [Page 7]
Internet-Draft Abbreviated Title October 2022
[sana] SANA, "Space Assigned Numbers Authority (SANA)",
<https://sanaregistry.org>.
[ccsds] CCSDS, "Consultative Committee on Space Data Systems
(CCSDS)", <https://ccsds.org>.
Acknowledgements
This work is based on a discussion with Peter Shames of Jet
Propulsion Laboratory on how to provide information of space objects
and networks.
Author's Address
Marc Blanchet
Email: Marc.Blanchet@viagenie.ca
Blanchet Expires 27 April 2023 [Page 8]
