> On Nov 7, 2024, at 8:38 PM, Stefan Ubbink
> wrote:
>
> On 7 Nov 2024 18:36:34 +
> "John Levine" wrote:
>
>> It appears that Shane Kerr said:
>> Since I noticed the ZONEVERSION RFC 9660, I was thinking that
>> this could be extended to include a version at the database.
Hi Petr,
I am unable to meet in person about this, but I were thinking about
providing some way of forwarder specification. My usage would be a
common way to discover where and how are responses forwarded. The
primary task for be would be discovering, how is the next hop protected,
if at all.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I just joined the list, so apologize if I am repeating a comment that has
already been made. Something that just jumped out at me is that in section 3.5
on timestamps, the draft references RFC4034 without also mentioning that these
timestamps
Hi Jens,
Thanks for your comment. See below.
On Fri, Nov 8, 2024 at 7:56 AM Jens Finkhäuser wrote:
>
> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>
> Hi,
>
> I just joined the list, so apologize if I am repeating a comment that has
> already been made. Something that just jumped out at me i
Hi,
> > Small changes that make it easier to digest.
>
> 🙂 You mean as in MD5 (Message Digest (algorithm) 5)? 🙂
>
That is deprecated in favour of the beer you owe me for that joke 😃
Jens
BEGIN:VCARD
VERSION:3.0
ADR;TYPE=work,pref:;;Theodor-Stern-Kai 1;Frankfurt am Main;;60596;DE - Germ
any
B
