[dtn] Fwd: LTP CL for BP v7

Keith Scott <keithlscott@gmail.com> Mon, 01 April 2024 19:44 UTC

Return-Path: <keithlscott@gmail.com>
X-Original-To: dtn@ietfa.amsl.com
Delivered-To: dtn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 869E1C151098 for <dtn@ietfa.amsl.com>; Mon, 1 Apr 2024 12:44:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 j01s-knPiYdy for <dtn@ietfa.amsl.com>; Mon, 1 Apr 2024 12:44:34 -0700 (PDT)
Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) (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 D8C65C151061 for <dtn@ietf.org>; Mon, 1 Apr 2024 12:44:34 -0700 (PDT)
Received: by mail-pl1-x634.google.com with SMTP id d9443c01a7336-1e0d8403257so33297615ad.1 for <dtn@ietf.org>; Mon, 01 Apr 2024 12:44:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712000673; x=1712605473; darn=ietf.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=OI/0mQG2G7asNzvab0z0zSGVFKD6eYqlp+rWZ4ATf2U=; b=cOKS1g/w2oW/ofsdsxKxkf9JamCr5kx+t5fLvO0QJG98k688ulGpRrYhBnK12Krtw3 UtpkBbAQ2++9ZM3904D8qRezG20ht0di75X86zIKew9DgQJbv+tO0QPHkpkNCpT04VJY jN9dYsJHP7FeolcZjgJDNKvLlNBBk3v53u5q3t44e2EoOF0kOmK1Kex11xb9RSJcq3wN nIBvsFWS5ekzmfYp6czhUUncC7nfPnp+HW5fKk/fx0QjNartxRrB2PtCJ0NcP5g5icMl 8DC4pZMM6kIB1EewyL4Sy7cQ0iAwxrlWEPefjAr1zqWIsM8+cnWMP39+hunno4qInDmM 6nrg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712000673; x=1712605473; h=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=OI/0mQG2G7asNzvab0z0zSGVFKD6eYqlp+rWZ4ATf2U=; b=mFq6IiqkeYPQJoDCU2JOQF+SFc6XeWlwXniBEnUTpvQOrMhm3SVkdu3zPS7IZJidBb U5E3KGBO8R7LBTm4uYXONruLq9IzW98UARQsoY5+Tp/ryUSza2JHpY+4vAhiOPNlvpH6 cT5X0xJd4Hrlpk9UV2jyiXD7Zm887cLPoaG5NbQZr9Cz+fFQ7MkSvIztlYg8UGaysiQA 3nJDVtfJNf0xMO2I5NfNa7HPK1koeL2wDoL9gspgXAvXKE6KiahL4+KL68FCCuXpyUwC o0KDlHr9alZDGgXf6pUttvAHB+alcGAGNTJly5NVhkQVko2xg/FLPYDD0Uh3rkiIH0a4 SCdw==
X-Gm-Message-State: AOJu0YygCvqT1UOOaPFvXSlGuaeUYTyvPk4UXvyiCmBkLrNvZZV/N/pB kkBZgFgWAVeHQvlLrU9UBXeANPFR2B3IogtmaFZ6TxGi8f9gq9j2w19QQhLO578OW3IDrZU2aib wPreIlTVJGl2oyxFp6V1CZfyBhLDjOUVX5Mg=
X-Google-Smtp-Source: AGHT+IEXxjlz6GkBZRtoiWhFUPlBBFL1/WBfjuJSMazQrMYnKXy2hce/pfZ9vaqcESymu+apv00pWPC1YZRXtNIoBo8=
X-Received: by 2002:a17:902:a616:b0:1db:3a22:1fd6 with SMTP id u22-20020a170902a61600b001db3a221fd6mr9068586plq.66.1712000673469; Mon, 01 Apr 2024 12:44:33 -0700 (PDT)
MIME-Version: 1.0
References: <7AF8662D-FDA3-4C88-95B7-B116825C7023@gmail.com> <036b01da845f$455ea100$d01be300$@gmail.com> <CAHdkBBm-Ct9h7oMZyM=H4=XcSv0+Gboq=CW_F2Orb2hXAyE4Aw@mail.gmail.com>
In-Reply-To: <CAHdkBBm-Ct9h7oMZyM=H4=XcSv0+Gboq=CW_F2Orb2hXAyE4Aw@mail.gmail.com>
From: Keith Scott <keithlscott@gmail.com>
Date: Mon, 01 Apr 2024 21:44:22 +0200
Message-ID: <CAHdkBBmTGhpamcc=aP7jZh7r-Oq4JhNVRoSkMQ=f+3MP9X1i8Q@mail.gmail.com>
To: DTN WG <dtn@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ff5d1306150e37ad"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dtn/CTX7p3B-VsagJV6wnNgiX0QLI-I>
Subject: [dtn] Fwd: LTP CL for BP v7
X-BeenThere: dtn@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Delay Tolerant Networking \(DTN\) discussion list at the IETF." <dtn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtn>, <mailto:dtn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtn/>
List-Post: <mailto:dtn@ietf.org>
List-Help: <mailto:dtn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtn>, <mailto:dtn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2024 19:44:38 -0000

Scott pointed out to me that the CL definition and the CL*A* definition
(how to carry bundles in the CL protocol) are different, so there might
still be a small bit of un-spec'ed work.  And that I forgot to cc: the
dtnwg (thx).... :o

    --keith

---------- Forwarded message ---------
From: Keith Scott <keithlscott@gmail.com>
Date: Mon, Apr 1, 2024 at 8:28 PM
Subject: Re: [dtn] LTP CL for BP v7
To: <sburleig.sb@gmail.com>


Though the CCSDS profile of the RFC5326-based LTP specification *is* a
published spec (https://public.ccsds.org/Pubs/734x1b1.pdf) that should be
suitable for contracting.

I'll also point you at a docker container-based emulation environment here
in case that's useful: https://github.com/keithlscott/opennetem. It comes
with a test scenario that uses LTP convergence layers.

The replacement for LTPCL is very much on CCSDS' todo list.  There's a
draft available to CCSDS dtn working group members but I'm not sure if
that's publicly available.  Let me see if that could be made available....

    --keith



On Mon, Apr 1, 2024 at 8:06 PM <sburleig.sb@gmail.com> wrote:

> Hi, John.  A quick answer that can be discussed further if needed: the LTP
> specification has not changed since RFC 5326, so that expired LTP CL spec
> should still be usable for software development – though it’s not a
> published standard that can be cited in a quote or bid, so you’re out of
> luck if that’s needed.
>
>
>
> The successor to LTP, currently under development in CCSDS DTN WG, will
> not be backward-compatible with LTP, and no CL specification for that
> protocol exists yet anyway, so at this time it’s not an option.
>
>
>
> Scott
>
>
>
> *From:* dtn <dtn-bounces@ietf.org> *On Behalf Of *John Dowdell
> *Sent:* Monday, April 1, 2024 9:34 AM
> *To:* DTN WG <dtn@ietf.org>
> *Subject:* [dtn] LTP CL for BP v7
>
>
>
> Dear all
>
>
>
> I have been looking for a published specification for LTP CL without
> success. The only draft I can find is one from Scott that expired some
> years back. I can see that ION-DTN has a LTP CL function but I’m not quite
> sure how that works.
>
>
>
> I have a need to build a stack that includes at least LTP v1 and BP v7,
> and hence the need for a working LTP CL. If the upcoming LTP v2 works with
> that same CL, all well and good but I get the feeling that it won’t.
>
>
>
> Can someone help me out here please? LTP CL seems to be on nobody’s
> current to-do list, neither IETF nor CCSDS, and I need something for the
> project I’m working on (those of you who know me will know what this is).
>
>
>
> Many thanks
>
>
>
> John
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> dtn mailing list
> dtn@ietf.org
> https://www.ietf.org/mailman/listinfo/dtn
>