Received: from mail-ej2-x10.google.com (mail-ej2-x10.google.com [IPv6:2a00:1450:4864:34::10]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 1559D30 for ; Tue, 15 Sep 2026 12:37:45 +0000 (UTC) Authentication-Results: mx.ietf.org; dkim=pass header.d=gmail.com header.s=20251104 header.b=e6cForYL; arc=pass ("google.com:s=arc-20260327:i=1"); dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx.ietf.org: domain of ted.ietf@gmail.com designates 2a00:1450:4864:34::10 as permitted sender) smtp.mailfrom=ted.ietf@gmail.com Received: by mail-ej2-x10.google.com with SMTP id a640c23a62f3a-c2940ef15d3so464440966b.2 for ; Tue, 15 Sep 2026 05:37:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1789475864; cv=none; d=google.com; s=arc-20260327; b=FZLyHWQVEAZIML8LRbLB8wbnim0f66cPNoSZTO0003T+fHqtnQDSVOcINMxYVSyQCo YVlTaAOwg7V4tEJeIrRGlE8YLNjBOuxXzrWO4eg9kJ7wdk3+8pcyYCdBFya6Wyh6nF27 nULT2uBWQ8sTH+mQiyXUsgIYZmuFRT07z3x/U7BU8N7wGoptF0JiQy2PGHz+DAwu6T2W iPrgFVX/EMS2iTVGTpEqUIQuJcJWz5Bq6rXACYCTyA9UmmL+PEd37Cd5YaHKOvVl8Fo8 qFUZ7cuuce1YkZmo3WzNHAxPy8g2L8fNRY1o8s2Hh7t2OxuwY3do3MnHUrtVf4xCCCoX 5s3A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=mYiHy3gLUIhQlka/g+E7oCL2rMCjDOEHHoTSsdOFbsM=; fh=6MDbN/vUBa5vPYIJ/MpiHtlcx167dCXa/lymC63K2eg=; b=pWK7bqGvP85lSuqTTY4r12KOPaST8KWHg5F9I0E5qOKCWYM6+EWefKwpqbH4oKgglb M65ULN/pcJ4+BsM4szvzCsaD+bQWW54xFN00ZIETWENKsoXxBaoLSVZjS8SUW1lil06c RgTu8cHoDDNsofo4/mNXBCquD8iD4W/KDF+Cxo1zi6eX+bSkW6Jxnqw8NBDo22N8GgsT IBkkiNqkPL2vtJq/JySMs1Np0/ex4TMNvQzoXlz/0d0ImNtAlmWnRxlAfopHx4sVeiLx mA0MQqigUkLZi2p8guRYLoAoISHqh7Onx3x3psclIhOyB1sSKR8qsnZS+ZTX2lcYhw4B ZNZA==; darn=ietf.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1789475864; x=1790080664; darn=ietf.org; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to :content-type; bh=mYiHy3gLUIhQlka/g+E7oCL2rMCjDOEHHoTSsdOFbsM=; b=e6cForYLwN6RhK6IOSa1LNnWgiAUBoILks0B90inqGFf1x5S7r+MDjA8N5gKcwAaR4 5HEPQUKrO/2HxvAGNHmniycpzQgGoXa5HdxEXvLVfA5W8o2lG48mOjfSHpf9FLX9LSmO NDlIPmA2+Ih6MFrrj/QB/mIUoEZ0+XCJx92kBGmobH3GYBpf3Na4i9k8ojyhHutncsv7 0AoH3WK7A92m/D759Xy88hCZeb7pRa+P7RTZIfPjWXjQDjh6T3UnqbHUiDd4wxcyg9XK Si25X709DBLPFrr09UDY+X7zkaaRUKl0mzbF0Iix8axGTRkQs2JTTVrhieXX1d/Q1iqI QjZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1789475864; x=1790080664; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to:content-type; bh=mYiHy3gLUIhQlka/g+E7oCL2rMCjDOEHHoTSsdOFbsM=; b=xFlLBR5vot74N6mZEOnhm+SyPnz3YOU4HhlHjuRwjukuOwmIZV1oglxgoRULvxHHkP UK66xkWnaUnGiHjNWPHrgTgrQr/UKmNo81aFiZjizSJjNM4OCmGP6Q+WKXN3TiOpso9z yjUilwmj39zpJ+JneIJzZSAj6Goyj9n2CwjN9qU5yhH1MErUvKSJfTgMqid8riYBBnIK P6a4J7ek3pGpnp5txrKKPiFetHuNpNEW9cotGopNHJJDLWlAa/9pCCbB1WI7haODvlsi TmUs9aXOcko0Gx13CxFw85aA/gKmPLhRvleTNJ8N/NEQnfWi5JzQiPI7A+7tVa5FivoR 6Eug== X-Gm-Message-State: AFuF++kDDje3pe+upaYY7YaiwOJJZiH0NuMN0DBnrEO+rgNJUtB8K9qM 8DAD8XMG5FGgoYnHoOCgQt7bN5hcvSD2IJ9TWPaLnb4YgyeDqNKbq0V5PdF0ge/+Ms+3LWAecbC Keh4AVS1Hmd3aCiw9VOL7/J1uM0C/Igc= X-Gm-Gg: AYBFou08dolipGvtWdh+DnEP2sLN1LYRIiJx0Wj5W+lZ96AbYaj4BR4fwqGj9iGKYwT 9ttWwOo+eMPMos7SlatYwzp8TI1rqxJPFw/o+Tc6hM7T2d5rAEsnqd/+QW3XRGTGQKwlL/r+57z 6PDF9Thb9VtUIloVVVQtGQonbBL/RrTbRCeC+WWtOqVJw+bGcTq4OvKQqkFfb+imEyp5FFK0AO6 8oNUEH71iHLV40lCMKj7dBiJ6KgrXc0/ttJ0ZGNvzu+ErkEZhxczm+9/+LTqn8KO2Z/eDppjGkN 6egcJjgwexFkhTMZ9Lp31C4XAYUfOkY619sRDSchAg2I4h9/Gzxlbuk7d7pFbupHX7meC1Ga0+m T8v4nY0dggUSpBfPeurR1Y2flW6ISq7BJENZ8Lw24pYjZ1HkRFLjYyoMWAoqCzE9MIW5Uq4AodA btkTfg0NpR8AbTocjM6Bx+orL+xqRBeHaXA0ECYeDgYXGb/wJFMU+Mn4/dmOA5A+lsaGYVLwQxo RNRB/4FwbxEf4fE0rMKu4NPssHGcUFeU+KCtkNPIQ0+9a1s1MDLIu+0zrpjIfL6lJnZOfmEDVXE WMrUMh6iDU48Cg== X-Received: by 2002:a17:906:1012:20b0:c29:d522:b4fd with SMTP id a640c23a62f3a-c29d522c5b2mr186601566b.4.1789475863579; Tue, 15 Sep 2026 05:37:43 -0700 (PDT) MIME-Version: 1.0 References: <060abee5-a117-457b-a4d6-021b9be07b17@not4bflu55.de> In-Reply-To: <060abee5-a117-457b-a4d6-021b9be07b17@not4bflu55.de> From: Ted Hardie Date: Tue, 15 Sep 2026 13:37:16 +0100 X-Gm-Features: AcwNN1WmJGzxKSz5FWxoMt8pm2MP9HWJtGt8mxYMp-gQa_8yipl2tNeMf2JWPw0 Message-ID: To: =?UTF-8?Q?Thomas_L=C3=BCchow?= Content-Type: multipart/alternative; boundary="0000000000002ed1bb065b84d1c9" X-Spamd-Bar: -- Message-ID-Hash: 4GJK76ZPP4TNB4WG2U4H7XGHUB7JLKK5 X-Message-ID-Hash: 4GJK76ZPP4TNB4WG2U4H7XGHUB7JLKK5 X-MailFrom: ted.ietf@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-dispatch.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: dispatch@ietf.org X-Mailman-Version: 3.3.10 Precedence: list Subject: [dispatch] Re: Venue guidance for draft-luechow-route86-timestamp-01 List-Id: DISPATCH Working Group Mail List Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --0000000000002ed1bb065b84d1c9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Howdy, The draft mentions constrained environments, but there is no indication of exactly which environments have these constraints and need these particular semantics. Many constrained environments would need more granular semantics than 86.4 second time-of-day slices, for example, and so would not be able to use this. Can you describe the target environments in a bit more detail? Without that, it is difficult to know what venue might be suitable (if any IETF venue turns out to be--this may be work better done elsewhere). best regards, Ted Hardie On Tue, Sep 15, 2026 at 9:41=E2=80=AFAM Thomas L=C3=BCchow wrote: > Hello DISPATCH, > > I am seeking guidance on the appropriate IETF venue for the following > individual Internet-Draft: > > Route86: A Compact Context-Dependent Timestamp Format > https://datatracker.ietf.org/doc/draft-luechow-route86-timestamp/ > > Route86 defines a canonical six-character textual timestamp for constrain= ed > message transports. It combines a three-character Base36 calendar-day > component, interpreted relative to an external reference date, with a > three-digit time-of-day component at 86.4-second resolution. > > The proposal is deliberately narrow: it does not define a transport and i= s > not intended to replace general-purpose Internet date and time formats. T= he > interoperability question is whether independent implementations can > encode, > decode, validate, and order Route86 values consistently when they share t= he > same application profile and reference-date context. > > Would DISPATCH be the appropriate place for initial discussion, or would > CoRE > or another existing group be a better fit? If this subject is outside > DISPATCH's scope, a pointer to the appropriate venue would be appreciated= . > > My aim is an Experimental specification if there is sufficient interest; = I > am > not assuming a particular stream or working group. > > I can provide a short problem statement, implementation notes, and > additional > test vectors if that would be useful. > > Best regards, > > Thomas Luechow > Dorfzwockel > dorfzwockel@not4bflu55.de > _______________________________________________ > dispatch mailing list -- dispatch@ietf.org > To unsubscribe send an email to dispatch-leave@ietf.org > --0000000000002ed1bb065b84d1c9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
How= dy,

<= div class=3D"gmail_default" style=3D"font-size:small">The draft mentions co= nstrained environments, but there is no indication of exactly which environ= ments have these constraints and need these particular semantics.=C2=A0 Man= y constrained environments would need more granular semantics than 86.4 sec= ond time-of-day slices, for example, and so would not be able to use this.= =C2=A0 Can you describe the target environments in a bit more detail?=C2=A0= Without that, it is difficult to know what venue might be suitable (if any= IETF venue turns out to be--this may be work better done elsewhere).
=

best regards,

Ted Hardie

On= Tue, Sep 15, 2026 at 9:41=E2=80=AFAM Thomas L=C3=BCchow <dorfzwockel=3D= 40not4bflu55.de@dmarc.iet= f.org> wrote:
=20 =20 =20
Hello DISPAT= CH,

I am seeking= guidance on the appropriate IETF venue for the following
individual I= nternet-Draft:

Route86: A C= ompact Context-Dependent Timestamp Format
https://datatracker.ietf.org/doc/draft-luechow-route86-timestamp/<= /a>

Route86 defi= nes a canonical six-character textual timestamp for constrained
message tran= sports. It combines a three-character Base36 calendar-day
component, i= nterpreted relative to an external reference date, with a
three-digit = time-of-day component at 86.4-second resolution.

The proposal= is deliberately narrow: it does not define a transport and is
not intended= to replace general-purpose Internet date and time formats. The
interoperabi= lity question is whether independent implementations can encode,
decode, vali= date, and order Route86 values consistently when they share the
same applica= tion profile and reference-date context.

Would DISPAT= CH be the appropriate place for initial discussion, or would CoRE
or another e= xisting group be a better fit? If this subject is outside
DISPATCH'= ;s scope, a pointer to the appropriate venue would be appreciated.

My aim is an= Experimental specification if there is sufficient interest; I am
not assuming= a particular stream or working group.

I can provid= e a short problem statement, implementation notes, and additional
test vectors= if that would be useful.

Best regards= ,

Thomas Luech= ow
Dorfzwockel<= /span>
dorfzwockel@not4bflu55.d= e
_______________________________________________
dispatch mailing list -- dispatch@ietf.org
To unsubscribe send an email to dispatch-leave@ietf.org
--0000000000002ed1bb065b84d1c9--