From nobody Wed May 31 01:33:57 2023
Return-Path: <libor.peltan@nic.cz>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 813CCC151544
 for <dnsop@ietfa.amsl.com>; Wed, 31 May 2023 01:33:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001,
 RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001,
 URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 KdCI0Di-kf3i for <dnsop@ietfa.amsl.com>;
 Wed, 31 May 2023 01:33:54 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 17F35C151094
 for <dnsop@ietf.org>; Wed, 31 May 2023 01:33:53 -0700 (PDT)
Received: from [192.168.88.252] (ip-217-030-074-194.aim-net.cz [217.30.74.194])
 by mail.nic.cz (Postfix) with ESMTPSA id 1EC4A1C1531
 for <dnsop@ietf.org>; Wed, 31 May 2023 10:33:50 +0200 (CEST)
Authentication-Results: mail.nic.cz;
 auth=pass smtp.auth=libor.peltan@nic.cz smtp.mailfrom=libor.peltan@nic.cz
Content-Type: multipart/alternative;
 boundary="------------veP4id0V849OfmO0Sfw04pCC"
Message-ID: <9e878214-4def-ab48-c882-54e29ba764b5@nic.cz>
Date: Wed, 31 May 2023 10:33:49 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.11.0
References: <168552183341.64553.1115658743324539974@ietfa.amsl.com>
Content-Language: en-US
To: dnsop <dnsop@ietf.org>
From: "libor.peltan" <libor.peltan@nic.cz>
In-Reply-To: <168552183341.64553.1115658743324539974@ietfa.amsl.com>
X-Forwarded-Message-Id: <168552183341.64553.1115658743324539974@ietfa.amsl.com>
X-Virus-Scanned: clamav-milter 0.103.7 at mail
X-Virus-Status: Clean
X-Rspamd-Queue-Id: 1EC4A1C1531
X-Spamd-Bar: -----
X-Spamd-Result: default: False [-5.10 / 20.00]; BAYES_HAM(-5.00)[100.00%];
 MIME_GOOD(-0.10)[multipart/alternative,text/plain];
 MIME_TRACE(0.00)[0:+,1:+,2:~];
 ASN(0.00)[asn:48574, ipnet:217.30.64.0/20, country:CZ];
 FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ZERO(0.00)[0];
 ARC_NA(0.00)[]; NEURAL_HAM(-0.00)[-0.798];
 RCPT_COUNT_ONE(0.00)[1]; TO_DN_ALL(0.00)[];
 FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[];
 MID_RHS_MATCH_FROM(0.00)[]
X-Rspamd-Server: mail
X-Rspamd-Action: no action
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ukBywrDUaRgTSzu4-55mHf4vaTM>
Subject: [DNSOP] Fwd: New Version Notification for
 draft-peltan-edns-presentation-format-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>,
 <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>,
 <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 May 2023 08:33:56 -0000

This is a multi-part message in MIME format.
--------------veP4id0V849OfmO0Sfw04pCC
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi dsnop,

we'd like to turn your attention again to our draft 
https://www.ietf.org/archive/id/draft-peltan-edns-presentation-format-01.html

We believe this document shall fill a missing gap in specifications, and 
help interoperability of DNS tools. Therefore, we think it'd make sense 
if this document once becomes a dnsop-homed RFC.

We'd appreciate your feedback and comments.

Update from -00: added Guidelines for Future EDNS(0) Options (thanks to 
Pieter Lexis); nitpicks.

Thank you!

Libor and Tom



-------- Přeposlaná zpráva --------
Předmět: 	New Version Notification for 
draft-peltan-edns-presentation-format-01.txt
Datum: 	Wed, 31 May 2023 01:30:33 -0700
Od: 	internet-drafts@ietf.org
Komu: 	Libor Peltan <libor.peltan@nic.cz>, Tom Carpay <tomcarpay@gmail.com>




A new version of I-D, draft-peltan-edns-presentation-format-01.txt
has been successfully submitted by Libor Peltan and posted to the
IETF repository.

Name: draft-peltan-edns-presentation-format
Revision: 01
Title: EDNS Presentation and JSON Format
Document date: 2023-05-31
Group: Individual Submission
Pages: 20
URL: 
https://www.ietf.org/archive/id/draft-peltan-edns-presentation-format-01.txt
Status: 
https://datatracker.ietf.org/doc/draft-peltan-edns-presentation-format/
Htmlized: 
https://datatracker.ietf.org/doc/html/draft-peltan-edns-presentation-format
Diff: 
https://author-tools.ietf.org/iddiff?url2=draft-peltan-edns-presentation-format-01

Abstract:
This document describes textual and JSON representation format of
EDNS option. It also modifies the escaping rules of JSON
representation of DNS messages, previously defined in RFC8427.



The IETF Secretariat


--------------veP4id0V849OfmO0Sfw04pCC
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi dsnop,<br>
      <br>
      we'd like to turn your attention again to our draft
<a class="moz-txt-link-freetext" href="https://www.ietf.org/archive/id/draft-peltan-edns-presentation-format-01.html">https://www.ietf.org/archive/id/draft-peltan-edns-presentation-format-01.html</a><br>
      <br>
      We believe this document shall fill a missing gap in
      specifications, and help interoperability of DNS tools. Therefore,
      we think it'd make sense if this document once becomes a
      dnsop-homed RFC.<br>
      <br>
      We'd appreciate your feedback and comments.<br>
      <br>
      Update from -00: added Guidelines for Future EDNS(0) Options
      (thanks to Pieter Lexis); nitpicks.<br>
      <br>
      Thank you!<br>
      <br>
      Libor and Tom <br>
    </p>
    <div class="moz-forward-container"><br>
      <br>
      -------- Přeposlaná zpráva --------
      <table class="moz-email-headers-table" cellspacing="0"
        cellpadding="0" border="0">
        <tbody>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Předmět:
            </th>
            <td>New Version Notification for
              draft-peltan-edns-presentation-format-01.txt</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Datum: </th>
            <td>Wed, 31 May 2023 01:30:33 -0700</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Od: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Komu: </th>
            <td>Libor Peltan <a class="moz-txt-link-rfc2396E" href="mailto:libor.peltan@nic.cz">&lt;libor.peltan@nic.cz&gt;</a>, Tom Carpay
              <a class="moz-txt-link-rfc2396E" href="mailto:tomcarpay@gmail.com">&lt;tomcarpay@gmail.com&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <br>
      A new version of I-D, draft-peltan-edns-presentation-format-01.txt<br>
      has been successfully submitted by Libor Peltan and posted to the<br>
      IETF repository.<br>
      <br>
      Name: draft-peltan-edns-presentation-format<br>
      Revision: 01<br>
      Title: EDNS Presentation and JSON Format<br>
      Document date: 2023-05-31<br>
      Group: Individual Submission<br>
      Pages: 20<br>
      URL:
<a class="moz-txt-link-freetext" href="https://www.ietf.org/archive/id/draft-peltan-edns-presentation-format-01.txt">https://www.ietf.org/archive/id/draft-peltan-edns-presentation-format-01.txt</a><br>
      Status:
      <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-peltan-edns-presentation-format/">https://datatracker.ietf.org/doc/draft-peltan-edns-presentation-format/</a><br>
      Htmlized:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-peltan-edns-presentation-format">https://datatracker.ietf.org/doc/html/draft-peltan-edns-presentation-format</a><br>
      Diff:
<a class="moz-txt-link-freetext" href="https://author-tools.ietf.org/iddiff?url2=draft-peltan-edns-presentation-format-01">https://author-tools.ietf.org/iddiff?url2=draft-peltan-edns-presentation-format-01</a><br>
      <br>
      Abstract:<br>
      This document describes textual and JSON representation format of<br>
      EDNS option. It also modifies the escaping rules of JSON<br>
      representation of DNS messages, previously defined in RFC8427.<br>
      <br>
      <br>
      <br>
      The IETF Secretariat<br>
      <br>
      <br>
    </div>
  </body>
</html>

--------------veP4id0V849OfmO0Sfw04pCC--

