[deepspace] Re: Fwd: New Version Notification for draft-acosta-deepspace-celestial-bodies-registry-01.txt

[Alejandro Acosta <[e-mail]>]

Hi Erik,

   You're totally right, and I actually agree.

   IANA shouldn't be carrying that weight when the IAU already does the 
job. The draft is definitely too long and over-engineered right now (I 
wanted to do a good job and I overworked it). My main goal was just to 
flag that Deepspace/TIPTOP will eventually need an "ISO 3166 equivalent" 
for celestial objects and neither IANA nor the IETF need to do it.

   Deferring to the IAU is definitely the right way to go. If some 
discussion happen I’ll trim down the draft big time for the next version 
and remove the unnecessary IANA overhead.

   Thanks for the catch!


Best,

Alejandro Acosta,



On 5/9/26 11:20 PM, Erik Kline wrote:
> Does IANA really need to be doing this?
>
> For RFC 9179 S2.1 
> (https://datatracker.ietf.org/doc/html/rfc9179#section-2.1) they just 
> defer to the IAU:
>
> 2.1.  Frame of Reference
>
>    The frame of reference ('reference-frame') defines what the location
>    values refer to and their meaning.  The referred-to object can be any
>    astronomical body.  It could be a planet such as Earth or Mars, a
>    moon such as Enceladus, an asteroid such as Ceres, or even a comet
>    such as 1P/Halley.  This value is specified in 'astronomical-body'
>    and is defined by the International Astronomical Union
>    <http://www.iau.org>. The default 'astronomical-body' value is
>    'earth'.
>
>
>
> On Thu, Aug 27, 2026 at 11:47 PM Alejandro Acosta 
> <[e-mail]> wrote:
>
>     Hello group,
>       I just submitted my first draft (yes, 01, sorry, I screwed it up
>     with the 00 version).
>       Any comments, feedback, or suggestions  are highly welcome.
>
>     Thanks,
>
>     Alejandro
>
>
>
>     -------- Forwarded Message --------
>     Subject: 	New Version Notification for
>     draft-acosta-deepspace-celestial-bodies-registry-01.txt
>     Date: 	Thu, 27 Aug 2026 23:24:38 -0700
>     From: 	[e-mail]
>     To: 	Alejandro Acosra <[e-mail]>
>     <mailto:[e-mail]>, Alejandro Acosta
>     <[e-mail]> <mailto:[e-mail]>
>
>
>
>     A new version of Internet-Draft
>     draft-acosta-deepspace-celestial-bodies-registry-01.txt has been
>     successfully
>     submitted by Alejandro Acosta and posted to the
>     IETF repository.
>
>     Name: draft-acosta-deepspace-celestial-bodies-registry
>     Revision: 01
>     Title: Defining a Celestial Bodies Registry for Deep Space
>     Internet Addressing
>     Date: 2026-08-27
>     Group: Individual Submission
>     Pages: 5
>     URL:
>     https://www.ietf.org/archive/id/draft-acosta-deepspace-celestial-bodies-registry-01.txt
>     Status:
>     https://datatracker.ietf.org/doc/draft-acosta-deepspace-celestial-bodies-registry/
>     HTML:
>     https://www.ietf.org/archive/id/draft-acosta-deepspace-celestial-bodies-registry-01.html
>     HTMLized:
>     https://datatracker.ietf.org/doc/html/draft-acosta-deepspace-celestial-bodies-registry
>     Diff:
>     https://author-tools.ietf.org/iddiff?url2=draft-acosta-deepspace-celestial-bodies-registry-01
>
>     Abstract:
>
>     This document proposes the creation of a formalized registry for
>     celestial bodies within the Internet Assigned Numbers Authority
>     (IANA) to support routing and address allocation in deep space
>     networks. As internet architecture expands to interplanetary scales,
>     routing protocols rely on hierarchical aggregation based on planetary
>     and celestial entities. However, the IETF currently lacks a
>     standardized taxonomical framework or mapping mechanism to uniquely
>     identify these entities. This document outlines the requirements for
>     establishing such a registry, suggests leveraging definitions from
>     the International Astronomical Union (IAU), and discusses the
>     integration of these identifiers into the deep space routing
>     architecture.
>
>
>
>     The IETF Secretariat
>
>     -- 
>     deepspace mailing list -- [e-mail]
>     To unsubscribe send an email to [e-mail]
>