DNS Resource Records for DTN Overlays
draft-johnson-dns-ipn-cla-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
|
|
|---|---|---|---|
| Author | Scott M. Johnson | ||
| Last updated | 2024-06-23 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-johnson-dns-ipn-cla-00
Internet Engineering Task Force S. Johnson, Ed.
Internet-Draft Spacely Packets, LLC
Intended status: Informational 23 June 2024
Expires: 25 December 2024
DNS Resource Records for DTN Overlays
draft-johnson-dns-ipn-cla-00
Abstract
Delay Tolerant Networks (DTNs) are typically characterized by high
latency and lack of constant end to end connectivity, consistent with
their use in deep space communications. This, however, is not the
limit of application of Bundle Protocol (BP) and related DTN enabling
technologies. Through a collection of Convergance Layer Adapters
(CLAs), deployment overlaying the terrestrial Internet is a core
component of DTN implementations. IPN is a integer based naming
scheme for DTN networks. Nothwithstanding cryptographic
considerations, three basic components are necessary to make a BP
overlay network connection, the IP address of the node, the CBHE Node
Number (IPN component), and the CLA which providing IP connectivity.
This document describes additions to DNS to enable terrestrial BP
resource look up.
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 25 December 2024.
Copyright Notice
Copyright (c) 2024 IETF Trust and the persons identified as the
document authors. All rights reserved.
Johnson Expires 25 December 2024 [Page 1]
Internet-Draft DNS Resource Records for DTN Overlays June 2024
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. RRTYPES for Delay Tolerant Networks . . . . . . . . . . . . . 2
2.1. IPN . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.2. CLA . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Convergence Layer Adapters . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
Terrestrial use of DTNs across reliable, low latency paths introduces
the opportunity to leverage the existing DNS infrastructure to
distribute connectivity related data. While is it not technically
feasible to ensure delivery of non-stale data to spaceborne DTN nodes
in response to a DNS lookup request, there is no such barrier to
deploying DNS records which describe those core datasets necessary to
enable connection of DTN nodes overlaying IPv4 or IPv6 networks.
2. RRTYPES for Delay Tolerant Networks
2.1. IPN
A popular naming scheme for BP nodes is the IPN naming scheme,
defined in [RFC7116]. The fundamental unit of this scheme is the
Endpoint Identifier (EID) which is comprised of two 64 bit unsigned
integers delineated by . as described in section 4.2.5.1.2 of
[RFC9171]. Of the components of an EID, only the (node-nbr)
component identifies the node, while the (service-nbr) component
generally is analagous to the port number bound to an IP socket.
Therefore, a DNS RRTYPE is requested to represent the (node-nbr)
component of an EID as a character array of no more than 21
characters, encoded in US-ASCII. Wire and presentation formats are
identical and interchangable. Suitable syntax, encoded as character
arrays, for these resource records are either a 64 bit unsigned
Johnson Expires 25 December 2024 [Page 2]
Internet-Draft DNS Resource Records for DTN Overlays June 2024
integer, or two 32 bit unsigned integers delimited by a period.
2.2. CLA
BP supports a wide range of CLAs; some IP based and others
interfacing at different layers or via different network layer
protocols . Those treated here represent the subset designed to
operate overlaying IP networks, and hence have DNS services generally
constantly available in a low latency environment. Primary among
these are TCP, UDP and LTP over UDP CLAs operating over both IPv4 and
IPv6 links. Table 1 describes an initial list of of valid values for
a CLA RRTYPE, to be encoded as US-ASCII character arrays for both
presentation and wire formats.
3. Convergence Layer Adapters
+=========================+
| Valid CLA RRTYPE Values |
+=========================+
| TCP-v4 |
+-------------------------+
| TCP-v6 |
+-------------------------+
| UDP-v4 |
+-------------------------+
| UDP-v6 |
+-------------------------+
| LTP-v4 |
+-------------------------+
| LTP--v6 |
+-------------------------+
| STCP-v4 |
+-------------------------+
| STCP-v6 |
+-------------------------+
| BSSP-v4 |
+-------------------------+
| BSSP-v6 |
+-------------------------+
| IPND-v4 |
+-------------------------+
| IPND-v6 |
+-------------------------+
Table 1
Johnson Expires 25 December 2024 [Page 3]
Internet-Draft DNS Resource Records for DTN Overlays June 2024
4. IANA Considerations
IANA is requested to create CLA and IPN RRTYPES in the Domain Name
System (DNS) Resource Record (RR) TYPEs registry.
5. Security Considerations
This document should not affect the security of the Internet.
6. References
6.1. Normative References
[RFC7116] Scott, K. and M. Blanchet, "Licklider Transmission
Protocol (LTP), Compressed Bundle Header Encoding (CBHE),
and Bundle Protocol IANA Registries", RFC 7116,
DOI 10.17487/RFC7116, February 2014,
<https://www.rfc-editor.org/info/rfc7116>.
[RFC9171] Burleigh, S., Fall, K., and E. Birrane, III, "Bundle
Protocol Version 7", RFC 9171, DOI 10.17487/RFC9171,
January 2022, <https://www.rfc-editor.org/info/rfc9171>.
Author's Address
Scott M. Johnson (editor)
Spacely Packets, LLC
46 High Ridge Road
Daytona Beach, FL 32117
United States of America
Phone: 386-888-7311
Email: scott@spacelypackets.com
Johnson Expires 25 December 2024 [Page 4]