[DNSOP] Re: [IPNSIG PWG] Re: [dtn] Re: An Interplanetary DNS Model

Sivasubramanian M <6.internet@gmail.com> Wed, 24 July 2024 05:52 UTC

Return-Path: <6.internet@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4005EC1CAF2C; Tue, 23 Jul 2024 22:52:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jU0Ec_QPhAiy; Tue, 23 Jul 2024 22:52:10 -0700 (PDT)
Received: from mail-oi1-x229.google.com (mail-oi1-x229.google.com [IPv6:2607:f8b0:4864:20::229]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62703C1D52ED; Tue, 23 Jul 2024 22:52:10 -0700 (PDT)
Received: by mail-oi1-x229.google.com with SMTP id 5614622812f47-3d9306100b5so3833287b6e.1; Tue, 23 Jul 2024 22:52:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721800329; x=1722405129; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=OwHZX1vR/AN121q3rptE9GfviWMkUwGSkWP4UMkqntw=; b=H30AqDj1DKyjwiDk8sYtcCyt2Pb/0B0oYM+lwZXSAUEY2KbxzAt6AGoI8FJllT76X+ QRsEyHq6x9CO0AnrXcl534Tkc3hOPaNB24RbPSBT3/RjzSLFMOEyl+WZx+SYVEL2vaP8 Vjy1PhIX8hf4pDeMnYr5M9Nc4/IEl7fSP1mIQ6aFwppB3q6n8uHciaRulEJkJv/2AxiD ahilfPY1bf3kMV9kOJSRQIg8ym3c9BGzQq++7HnVsplqDpKHxy5cll4jvzyCHBKCS4pp gP3yeSt2nk2f00+9LMBU94WWvGXtWfkFyLL2eg0LnHnUyZJubgb41Sn6hujKHxhXFRmo kDzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721800329; x=1722405129; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=OwHZX1vR/AN121q3rptE9GfviWMkUwGSkWP4UMkqntw=; b=L4ZJMBTd+nbHrsQ4QYlXnjinCEnHpWUPwrPyQPk6pJs2SOcU+uUjwGP4u1Qu37rSKA 0jBayVnkfpDUEmMCGaz9F/nS43sR2e+1PhNijX8hdRMYA8ZD3uBsE/mVDHQIrE6iSUg3 22BSnIhIj+7dJj/q5abbtAjq0EmpZuU7y0x3rnB2lpZOXVgg0YMD7qEB+KHtg3CzekM4 0+RxyRwyqvI0tysMl+o5PkP9KI1Lw/yfgmjRGUytfVDfpgsUaCX1cYb8s4eZT1m5zmiJ X50vY2f7tOP/MER/oSgxq+N5xP5wVfglTyGI7ZMfeeUOXHG0HCYjoreDNQpDNc8DDdui aX1g==
X-Forwarded-Encrypted: i=1; AJvYcCXvcovyYFG9layApKqVE1pgOK4RsRwa8YRuSLQZvaNTbbpcGjWTH3kspe9RO9EOyK1Y3JQaXM8QGDfwFKFvV927sYg6yV95dBAsCWau
X-Gm-Message-State: AOJu0YxzDiNl7SlBtCcVyFbMH/GS5QQZ15CU/rhMinostuhtJwJHAiCB JrwiR9JBCpv49l1VaIXxECIfrAM+3jGDmKmWnvJCQzVuFmb6T6VPqS2JiScOYD3aaNs5NWyjBQw hWlEjOtTsfBzrJNF1chzavl0gFSY=
X-Google-Smtp-Source: AGHT+IEMs67P9fv9Tam/KYCrk2bxieY4rLQH4B/vn7QfsRccrCwqg9ZpOwMJDaK8WYeUmVnK6jtUz5INIEIX/UGv+10=
X-Received: by 2002:a05:6808:1918:b0:3d9:2373:e75d with SMTP id 5614622812f47-3db06e06c62mr1983332b6e.35.1721800329102; Tue, 23 Jul 2024 22:52:09 -0700 (PDT)
MIME-Version: 1.0
References: <65daf988-f696-4f35-5a72-5b11ef4893b8@spacelypackets.com> <CO6PR09MB76060FCD3142903330D99F73A3A82@CO6PR09MB7606.namprd09.prod.outlook.com> <SA1PR15MB43706F599108E4CE1EFE68C6B3A82@SA1PR15MB4370.namprd15.prod.outlook.com> <0298f830-ea89-e151-1837-5e5ccb3ae710@spacelypackets.com> <CAKsgsGznEhcavkvpbBk1rusLJpAx8ZtBqptMw-WTwUXiGvtpmw@mail.gmail.com>
In-Reply-To: <CAKsgsGznEhcavkvpbBk1rusLJpAx8ZtBqptMw-WTwUXiGvtpmw@mail.gmail.com>
From: Sivasubramanian M <6.internet@gmail.com>
Date: Wed, 24 Jul 2024 11:21:59 +0530
Message-ID: <CAKsgsGwBB8bks4xeQ1kc9mqHhBVXtne4MrT=6kS4S-8W9VCGFQ@mail.gmail.com>
To: ipnsigpwg@googlegroups.com
Content-Type: multipart/alternative; boundary="000000000000fd8e26061df7e09b"
Message-ID-Hash: GTXDYLKMEG2XFOTQFYVBVCCPP4VN7RS7
X-Message-ID-Hash: GTXDYLKMEG2XFOTQFYVBVCCPP4VN7RS7
X-MailFrom: 6.internet@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Ben Schwartz <bemasc=40meta.com@dmarc.ietf.org>, "Nordgren, Bryce - FS, MT" <bryce.l.nordgren=40usda.gov@dmarc.ietf.org>, dtn@ietf.org, dnsop <dnsop@ietf.org>, awg-ipnsig@googlegroups.com
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [DNSOP] Re: [IPNSIG PWG] Re: [dtn] Re: An Interplanetary DNS Model
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/AouhesuoYryGxjdHNJspvgp6prQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>

On Wed, 24 Jul, 2024, 11:07 Sivasubramanian M, <6.internet@gmail.com> wrote:

>
>
> On Tue, 23 Jul, 2024, 02:50 Scott Johnson, <scott@spacelypackets.com>
> wrote:
>
>> Hi Ben,
>>
>> On Mon, 22 Jul 2024, Ben Schwartz wrote:
>>
>> > This document seems to propose that "https" URLs will route through
>>
>> "route through" is exactly what is not happening here.  https will be
>> secure to the edge of the IP network, which is the limit of the local IP
>> transaction.
>>
>> > gateways that terminate end-to-end security, destroying the "https"
>> > scheme's confidentiality and integrity properties.
>>
>> BPSEC picks up the slack here, as soon as the request details are placed
>> in a bundle for transit of the space network segments.
>> A new https request is created on the remote end from the data in the
>> bundle.
>>
>> End to end IP, particularly to anywhere more remote than the Moon, is a
>> practical impossibility; hence, security measures must be limited in
>> scope
>> to the networks they traverse.
>>
>> > That's a red flag
>> > for me.
>>
>> It would be for me too if what I am proposing were the same as what you
>> are describing.
>>
>> > Rather than trying to retrofit compatibility with existing terrestrial
>> > protocols into this (hypothetical and quite distant) scenario, I think
>> > we would be better served by developing protocols that serve real
>> > demands today, and delaying other technical solutions until real demand
>> > appears.
>>
>> Thanks for your feedback on that.  The truth is, we have most of what we
>> need already for mostly robotic missions.  You may find the 100 year
>> vision of the Interplanetary Chapter of ISOC interesting:
>> https://www.ipnsig.org
>>
>> As to real demand, an intimate knowledge of the players and their
>> capabilities, as well as those proposed specifications for Lunar
>> networks,
>> leads me to conclude that it will be difficult to get this finished and
>> shiny to a stage where it is viable for flight use before it is necessary.
>> True, the demands of Lunar colonization are different than near term
>> needs, but the need for IP networking there had thusfar not been
>> challenged, nor has the need for BP based DTN in some instances, and
>> definitely between terrestrial and Lunar IP networks.
>
>
> Why not ship the A route server
>

(... Root server. Apologies)

to the skies, ask the rest of the alphabets on the ground to mirror it on
> weekends to provide all week DNS route service on the ground, updated, with
> two digit latency? A small part of the A on the sky could also serially
> serve the IPNs, especially those on the sky that don't have an everyday
> need to bounce signals back and forth with the computers on the ground? The
> sky is above ground !
>

>
> We can't have
>> little Timmy in the basement taking over construction machines on the
>> Moon, can we?  If Timmy has no route to the Lunar IP network, this is not
>> an issue.  Meanwhile, we wish to enable a IP native services on the Moon,
>> while allowing viably delay tolerant IP applications best-effort
>> interoperability with terrestrial services.  Given the Adopt, Adapt,
>> Author order of preference in engineering solutions promoted by LOGIC
>> (https://logic.jhuapl.edu) it seems assmebling the lego blocks we
>> already
>> have into a solution, where possible, is the preferred path.
>>
>> Don't get me wrong; If someone offers me a big enough check, I _may_ find
>> something else to do with my time, but for now, I manage to feed my kids
>> with pure research and development like this, so I think I am going to
>> keep at it ;)
>>
>> Thanks,
>> ScottJ
>>
>>
>> >
>> > --Ben
>> >
>> > _______________________________________________________________________
>> > From: Nordgren, Bryce - FS, MT
>> > <bryce.l.nordgren=40usda.gov@dmarc.ietf.org>
>> > Sent: Monday, July 22, 2024 3:42 PM
>> > To: Scott Johnson <scott@spacelypackets.com>; dtn@ietf.org
>> > <dtn@ietf.org>; dnsop@ietf.org <dnsop@ietf.org>
>> > Cc: ipnsigpwg@googlegroups.com <ipnsigpwg@googlegroups.com>;
>> > awg-ipnsig@googlegroups.com <awg-ipnsig@googlegroups.com>
>> > Subject: [DNSOP] Re: [dtn] An Interplanetary DNS Model
>> > Just spitballing, but instead of a new TLD, what about
>> > "{earth,moon,mars}. sol. arpa" as your suffix? This seems like it's
>> > right in the wheelhouse of the "Address Resolution Parameter Area". . .
>> > https: //en. wikipedia. org/wiki/. arpa
>> > Just spitballing, but instead of a new TLD, what about
>> > "{earth,moon,mars}.sol.arpa" as your suffix?
>> >
>> > This seems like it's right in the wheelhouse of the "Address Resolution
>> > Parameter Area"...
>> >
>> > https://en.wikipedia.org/wiki/.arpa
>> >
>> >
>> >
>> > Forest Service Shield
>> >
>> > Bryce Nordgren, FRIT
>> > Physical Scientist
>> >
>> > Forest Service
>> >
>> > Missoula Fire Science Lab
>> >
>> > p: 406-829-6955
>> > c: 406-396-4147
>> > bryce.l.nordgren@usda.gov
>> >
>> > 5775 Hwy 10 W
>> > Missoula, MT 59808
>> > www.fs.fed.us
>> > USDA Logo Forest Service Twitter USDA Facebook
>> >
>> > Caring for the land and serving people
>> >
>> >
>> >
>> >
>> >
>> > _______________________________________________________________________
>> > From: Scott Johnson <scott@spacelypackets.com>
>> > Sent: Monday, July 22, 2024 3:00 AM
>> > To: dtn@ietf.org <dtn@ietf.org>; dnsop@ietf.org <dnsop@ietf.org>
>> > Cc: ipnsigpwg@googlegroups.com <ipnsigpwg@googlegroups.com>;
>> > awg-ipnsig@googlegroups.com <awg-ipnsig@googlegroups.com>
>> > Subject: [dtn] An Interplanetary DNS Model
>> > Hi Everyone,
>> >
>> > Sorry for the 4-way cross posting, but I wanted to reach all of those
>> > parties who may have interest.
>> >
>> > I have published an internet-draft version of a document I have been
>> > privately publishing, in order that the community may understand, pick
>> > apart, improve, and fill in the blanks.  This is in response to
>> > community
>> > interest and related efforts, in order that we best arrive at a
>> > standardized practice and architecture for Interplanetary Internet
>> > communications.  I welcome and look forward to comments which could
>> > help
>> > us reach this laudable goal.  I am not sure of the exact venue for WG
>> > adoption, given the scope of the concepts.  As such will I refrain from
>> > asking for WG adoption at this time, pending discussion from the DTN
>> > and
>> > DNS communities.
>> >
>> > Please find the draft here:
>> > https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata
>> > tracker.ietf.org%2Fdoc%2Fdraft-johnson-interplanetary-dns%2F&data=05%
>> > 7C02%7Cbryce.l.nordgren%40usda.gov%7Ca6aa16d3a3434c34031208dcaa2d44ba
>> > %7Ced5b36e701ee4ebc867ee03cfa0d4697%7C1%7C0%7C638572358631001081%7CUn
>> > known%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1ha
>> > WwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=BTPmN%2B7FDxrLZPRDDZZoD6YNKHG1d5
>> > ROtFlDjqZg1Vs%3D&reserved=0
>> >
>> > I would also be interested in revisiting Marc Blanchet's smtp and http
>> > over BP related drafts in the light of the above document, to see if
>> > adaptation can be made to make these efforts dovetail together.
>> >
>> > Thanks to all,
>> > Scott Johnson
>> > Spacely Packets, LCC
>> >
>> > _______________________________________________
>> > dtn mailing list -- dtn@ietf.org
>> > To unsubscribe send an email to dtn-leave@ietf.org
>> >
>> >
>> >
>> >
>> > This electronic message contains information generated by the USDA
>> > solely for the intended recipients. Any unauthorized interception of
>> > this message or the use or disclosure of the information it contains
>> > may violate the law and subject the violator to civil or criminal
>> > penalties. If you believe you have received this message in error,
>> > please notify the sender and delete the email immediately.
>> >
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "IPNSIGPWG" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ipnsigpwg+unsubscribe@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/ipnsigpwg/0298f830-ea89-e151-1837-5e5ccb3ae710%40spacelypackets.com
>> .
>>
>