From nobody Fri Sep  4 10:38:33 2020
Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 4E71E3A0C54
 for <quic@ietfa.amsl.com>; Fri,  4 Sep 2020 10:38:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.846
X-Spam-Level: 
X-Spam-Status: No, score=-2.846 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.948,
 SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
 autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id uAGzSsZmHmdS for <quic@ietfa.amsl.com>;
 Fri,  4 Sep 2020 10:38:30 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com
 [138.201.61.189])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id C6AD23A0C50
 for <quic@ietf.org>; Fri,  4 Sep 2020 10:38:29 -0700 (PDT)
Received: from xse459.mail2web.com ([66.113.197.205] helo=xse.mail2web.com)
 by mx14.antispamcloud.com with esmtp (Exim 4.92)
 (envelope-from <huitema@huitema.net>) id 1kEFfI-0005f1-JK
 for quic@ietf.org; Fri, 04 Sep 2020 19:38:26 +0200
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60])
 by xse.mail2web.com (Postfix) with ESMTPS id 4BjlDZ0TWlzDMp
 for <quic@ietf.org>; Fri,  4 Sep 2020 10:34:54 -0700 (PDT)
Received: from [10.5.2.16] (helo=xmail06.myhosting.com)
 by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256)
 (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1kEFbx-000681-UZ
 for quic@ietf.org; Fri, 04 Sep 2020 10:34:53 -0700
Received: (qmail 28745 invoked from network); 4 Sep 2020 17:34:53 -0000
Received: from unknown (HELO [192.168.1.107])
 (Authenticated-user:_huitema@huitema.net@[172.58.38.240])
 (envelope-sender <huitema@huitema.net>)
 by xmail06.myhosting.com (qmail-ldap-1.03) with ESMTPA
 for <quic@ietf.org>; 4 Sep 2020 17:34:53 -0000
Subject: Re: UDP, checksum, ports (was: Re: Should the specifications
 hard-refer to UDP?)
To: sarikaya@ieee.org, Lars Eggert <lars@eggert.org>
Cc: "quic@ietf.org" <quic@ietf.org>
References: <1ce1b329-78c0-42c4-aec7-db19b74742eb@www.fastmail.com>
 <2bac14c6-a543-454f-a0f3-d77258c2428b@www.fastmail.com>
 <CALGR9oa1y59huKSx+AY3OnMveN1Bm2xChZ=cbgaw+7jxvxQG5A@mail.gmail.com>
 <02060b294609539c1be54e89b1510ceb64ce87b2.camel@ericsson.com>
 <CAC8QAcfYtS0wDv3nr5Q6rC_ROx2tmTk09WEJ5sU9KYS+3M+4sA@mail.gmail.com>
 <A9D1260B-EC0F-4F48-9B13-D528FEB12562@eggert.org>
 <CAC8QAcf9AoDEaBgzGej3_9gBzirDJnPYHyBywywDPLHWJaZ=ig@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata=
 mDMEXtavGxYJKwYBBAHaRw8BAQdA1ou9A5MHTP9N3jfsWzlDZ+jPnQkusmc7sfLmWVz1Rmu0
 J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PoiWBBMWCAA+FiEEw3G4
 Nwi4QEpAAXUUELAmqKBYtJQFAl7WrxsCGwMFCQlmAYAFCwkIBwIGFQoJCAsCBBYCAwECHgEC
 F4AACgkQELAmqKBYtJQbMwD/ebj/qnSbthC/5kD5DxZ/Ip0CGJw5QBz/+fJp3R8iAlsBAMjK
 r2tmyWyJz0CUkVG24WaR5EAJDvgwDv8h22U6QVkAuDgEXtavGxIKKwYBBAGXVQEFAQEHQJoM
 6MUAIqpoqdCIiACiEynZf7nlJg2Eu0pXIhbUGONdAwEIB4h+BBgWCAAmFiEEw3G4Nwi4QEpA
 AXUUELAmqKBYtJQFAl7WrxsCGwwFCQlmAYAACgkQELAmqKBYtJRm2wD7BzeK5gEXSmBcBf0j
 BYdSaJcXNzx4yPLbP4GnUMAyl2cBAJzcsR4RkwO4dCRqM9CHpVJCwHtbUDJaa55//E0kp+gH
Message-ID: <eae30e77-e317-864a-d9d7-1c563bff17de@huitema.net>
Date: Fri, 4 Sep 2020 10:34:53 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <CAC8QAcf9AoDEaBgzGej3_9gBzirDJnPYHyBywywDPLHWJaZ=ig@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------2D46EDDB5E24F0FC8002ECFE"
Content-Language: en-US
X-Originating-IP: 66.113.197.205
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.197.0/24
Authentication-Results: antispamcloud.com; auth=pass
 smtp.auth=66.113.197.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: ham
X-Spampanel-Outgoing-Evidence: Combined (0.08)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0VKALJWqpbz84ezJUOplsTqpSDasLI4SayDByyq9LIhVbJBh0A1d+9W2
 UFX3UaX8T0TNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDcnqpk5VeF3xR4kF6iVwRtbgN
 zB/4Jkrw1eDLcif59fvmkNUFzqgK71j290HiPyeFU7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq
 8GSPg+5hmwN8D4LrepG7AX8WNwY81aOsarGPChhedL2Py5oHk46jSvfpO+1kZkomjtjB6X7/nuj3
 koRhn2BlE7dXoT0pGVmhMAaQ/AfCRwRe7yHm5oY+NYmsSGn+svMubxnbgm1cr18FZBEPC2/c16Xd
 7sC9aC4xteE1WLqGS9YoqrsZ2DyteN0e+ECCv9/f+GPymkgDVo7QBKA4MctKq4ifYPcXFRL2K3LA
 EfDXVOdt7wDbusYnuEVWSxKMHbU0zkNM3EElFDaoLuOPKc8gc82pKfhB7T02ZXdoQxMs//iOE4Fl
 hiCv9TR+UxzLZWL8hwGBjhoI3W+YcuHfP5PkZb5A+wE5qGdpH54Oa3V8I76VOEvlwLCanpZsarZa
 LIRpEqA8mZEwWcPoaRBqQ28Cyw5TTd3T7ZcA6yPx7zZCWNjJ/TI6yZf0AxY+BTyUpv5ZZ7Pszxf2
 ie80q3LAG2MiIaIREzT1xNjuO97khcUFBr/guEWv1bdCp3Zd9clP8wSiJZWbJCj+xRrjVmRxpGtS
 cvUmgj1LCHKe1PH/6K0TmoP6lY3JlF2jZAOanSBpz6Rja2u/0jI5Drb/uCdxrn0R1dKOr9zm50cb
 k66JCEX8hyQ7ijXfifysta6u1iHEyuS7GD1uvcojqec+j6EReqEF8xOyo0wFJOYIJd4MvQ0Nf4Ec
 bvHO1diDanHV9KirFAIIecsyj+YNTo81GR+jDXFsz/ZQnbbTizvwlZsrbltGiZoUh+c+5pFVgpT1
 b21uZVckGp0ccOa2XhkGbmsUNPNkere1WheNsVXmhO8BzADiszcWR9bz/SDtF09JpSbuuCeiIDK0
 C/0=
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/46zwTVZ8uU1h_p7zy3t6XFemdx8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>,
 <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>,
 <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Sep 2020 17:38:31 -0000

This is a multi-part message in MIME format.
--------------2D46EDDB5E24F0FC8002ECFE
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit


On 9/4/2020 9:07 AM, Behcet Sarikaya wrote:
>
>
> On Fri, Sep 4, 2020 at 10:56 AM Lars Eggert <lars@eggert.org
> <mailto:lars@eggert.org>> wrote:
>
>     Hi,
>
>     On 2020-9-4, at 18:36, Behcet Sarikaya <sarikaya2012@gmail.com
>     <mailto:sarikaya2012@gmail.com>> wrote:
>     > QUIC draft mentions UDP in many places, it says QUIC is
>     UDP-based but in the draft RFC 768 is not listed as a reference
>     informative/normative.
>
>     I opened https://github.com/quicwg/base-drafts/pull/4073 to fix
>     that - thank you for noticing.
>
>     > Second, probably more importantly, UDP header has the fields
>     source/destination port and checksum. These are not mentioned in
>     the draft.
>     > I wonder why?
>
>     What would you expect the drafts to say about checksums and ports?
>
>
> Yes, I realize that the draft mentions ports. 
> What I think should be mentioned is if these header fields are
> required then what are the requirements on implementations, or just
> refer to RFC 768?


Let's just refer to RFC 768. In particular, let's not have a protracted
discussion about UDP versus UDP-lite...

-- Christian Huitema


--------------2D46EDDB5E24F0FC8002ECFE
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><br>
    </p>
    <div class="moz-cite-prefix">On 9/4/2020 9:07 AM, Behcet Sarikaya
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAC8QAcf9AoDEaBgzGej3_9gBzirDJnPYHyBywywDPLHWJaZ=ig@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr"><br>
        </div>
        <br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Fri, Sep 4, 2020 at 10:56
            AM Lars Eggert &lt;<a href="mailto:lars@eggert.org"
              moz-do-not-send="true">lars@eggert.org</a>&gt; wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hi,<br>
            <br>
            On 2020-9-4, at 18:36, Behcet Sarikaya &lt;<a
              href="mailto:sarikaya2012@gmail.com" target="_blank"
              moz-do-not-send="true">sarikaya2012@gmail.com</a>&gt;
            wrote:<br>
            &gt; QUIC draft mentions UDP in many places, it says QUIC is
            UDP-based but in the draft RFC 768 is not listed as a
            reference informative/normative.<br>
            <br>
            I opened <a
              href="https://github.com/quicwg/base-drafts/pull/4073"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/quicwg/base-drafts/pull/4073</a>
            to fix that - thank you for noticing.<br>
            <br>
            &gt; Second, probably more importantly, UDP header has the
            fields source/destination port and checksum. These are not
            mentioned in the draft.<br>
            &gt; I wonder why?<br>
            <br>
            What would you expect the drafts to say about checksums and
            ports?<br>
            <br>
          </blockquote>
          <div><br>
          </div>
          <div>Yes, I realize that the draft mentions ports. </div>
          <div>What I think should be mentioned is if these header
            fields are required then what are the requirements on
            implementations, or just refer to RFC 768?</div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <p>Let's just refer to RFC 768. In particular, let's not have a
      protracted discussion about UDP versus UDP-lite...</p>
    <p>-- Christian Huitema<br>
    </p>
  </body>
</html>

--------------2D46EDDB5E24F0FC8002ECFE--

