[Sis-dtn] SANA-related question

[Vint Cerf]

has strong parallels with ICANN's IANA and has worked well. As long as SANA
is seen as apolitical and serving of all needs, it can work.

v


On Fri, Sep 10, 2021 at 12:28 PM Dr. Keith L Scott <kscott at mitre.org> wrote:

> Hey,
>
>
>
> So we’re working the revisions to the LTP spec, and one thing we’d like to
> do is to have a ‘field length identifer’ that serves (at least logically)
> as the index into a lookup table that gives the lengths of a number of LTP
> header fields.  So, for example field Length Identifier 1 could mean:
>
>    - The Session ID is 1 byte long
>    - The Session Number is 3 bytes long
>    - The Offset fields in data segments are 4 bytes long
>    - Etc.
>
>
>
> We believe that the ‘lookup table’ should be a SANA registry (we’re
> currently envisioning maybe a couple of ‘profiles’ e.g. for low- medium-
> and high-rate links).
>
>
>
> I THINK we want to write the spec in such a way that we talk about the
> field length identifier and then say something like: “For field lengths
> determined by the field length identifier, implementations MUST use the
> field length values from <insert SANA registry here>”.
>
>
>
>
>
> Does this seem reasonable?  Other thoughts / suggestions?
>
>
>
>
>
>                                 v/r,
>
>
>
>                                 --keith
>
>
> _______________________________________________
> SIS-DTN mailing list
> SIS-DTN at mailman.ccsds.org
> https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn
>


-- 
Please send any postal/overnight deliveries to:
Vint Cerf
1435 Woodhurst Blvd
McLean, VA 22102
703-448-0965

until further notice
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/sis-dtn/attachments/20210910/e0a64c9f/attachment.htm>