IETF Logo Mail Archive

Re: [tsvwg] draft-ietf-udp-options issues from IETF 104

"C. M. Heard" <heard@pobox.com> Thu, 18 July 2019 15:35 UTC

Return-Path: <heard@pobox.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA936120787 for <tsvwg@ietfa.amsl.com>; Thu, 18 Jul 2019 08:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=heard@pobox.com header.d=pobox.com
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 rvBZTxJrop99 for <tsvwg@ietfa.amsl.com>; Thu, 18 Jul 2019 08:35:53 -0700 (PDT)
Received: from pb-smtp2.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29B05120773 for <tsvwg@ietf.org>; Thu, 18 Jul 2019 08:35:52 -0700 (PDT)
Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id AC43F171768 for <tsvwg@ietf.org>; Thu, 18 Jul 2019 11:35:51 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type:content-transfer-encoding; s=sasl; bh=Uhfb3pRdrkXv 74orRRg8OSXZKes=; b=n/O6R2HrCbjMy428Sh9hgFbzl2BfkoYq975JwGbkJUOO 7yWE1z0xxhN66F332JSJM58Hgr+HGAVI63olaDcMxaAXHURy5rpaUT11LXwC+iPW /YMWef5WnhOguJGnwvYepAPWvjKiyHw5TthrMvdSGP8pwOB5N3tFNPaltI9AIbI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type:content-transfer-encoding; q=dns; s=sasl; b=nRGRDl ZFJO/I/l1WPSaRYyDt2gEdHw3DQS/eCSd00ntJxHjy9YKja3PfDdxLq22Lyf6Kq/ Uxyy6ThtYXsYmdD1gTkK5pDhoIr3iKDXZiSKBozxHNQzMeNRbVOxtiw8Dnzr5ZMm Ztx8Wc/hZG3uFoe1yKZXyR2QS4GINCrF11xg0=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 9DD36171765 for <tsvwg@ietf.org>; Thu, 18 Jul 2019 11:35:51 -0400 (EDT)
Received: from mail-io1-f54.google.com (unknown [209.85.166.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 0F3DC171762 for <tsvwg@ietf.org>; Thu, 18 Jul 2019 11:35:51 -0400 (EDT)
Received: by mail-io1-f54.google.com with SMTP id s7so52014913iob.11 for <tsvwg@ietf.org>; Thu, 18 Jul 2019 08:35:51 -0700 (PDT)
X-Gm-Message-State: APjAAAV//rOZG8Fxa/5DFTjA96fSiDvNWuUH++2N7C3MMgfd4A1rS67y lDCOAoteUVAiXdtvc9wNTnAZls7M6m+CVCNQLVY=
X-Google-Smtp-Source: APXvYqyiDhLeyf5RaA/y2GdFMTsZCKnKIQU7KBKKe5AjN8dvTmLVPIXSSbkScn8QweLtAwxNhhybxNcdxyFMJUBTMu4=
X-Received: by 2002:a02:c7c9:: with SMTP id s9mr48106372jao.82.1563464150534; Thu, 18 Jul 2019 08:35:50 -0700 (PDT)
MIME-Version: 1.0
References: <30c17e9c174f6b0da3ecc6b503a8cb17@strayalpha.com> <CACL_3VGs7j+y5vFNT3OL9OKX8ue4rv-Cxi467KR-vbhnMdx86g@mail.gmail.com> <2f71a292f924a9b8de4227c4bbc2f809@strayalpha.com> <CACL_3VGrF5UnbVsSzZZoy1i57WKiQKBX2T3a16UyEVHY=Kr3XA@mail.gmail.com> <CE03DB3D7B45C245BCA0D243277949363061EF7A@MX307CL04.corp.emc.com> <CACL_3VE7+3WD3Uzubf8X9uQX9ZYPnZVhXjheUOuL9EfjT1JkGQ@mail.gmail.com> <CALx6S35V-d3Rn_wjrhbHUHgS=_+dVjR4hbMJ0-JBsG-1BuFuZg@mail.gmail.com> <B5CCEF58-38CE-4973-9CFD-002B404E4EF3@strayalpha.com> <CACL_3VEnJoV9N9i59fJXG1Nyt=mMWT7SuB8B=C-Y9a9QLtqP7Q@mail.gmail.com> <BB3FD9A5-8D30-4600-A7A7-DA3030BD34A3@strayalpha.com> <20190718100109.GA86292@clarinet.employees.org> <718EBD34-5B4A-4458-B9B4-0A94C33E019E@strayalpha.com> <CACL_3VGL2irCkZeEcP+9HLBHqtqaMPZM66youUsatzosUu=Aew@mail.gmail.com> <A07EA390-1A3A-4AE9-AFD7-2F22CD4B0E31@strayalpha.com>
In-Reply-To: <A07EA390-1A3A-4AE9-AFD7-2F22CD4B0E31@strayalpha.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Thu, 18 Jul 2019 08:35:38 -0700
X-Gmail-Original-Message-ID: <CACL_3VF+yt-=vJ3UZW=jh2BtOcGYegOM4+Tx2PGAXiAX8fcLBg@mail.gmail.com>
Message-ID: <CACL_3VF+yt-=vJ3UZW=jh2BtOcGYegOM4+Tx2PGAXiAX8fcLBg@mail.gmail.com>
To: Joe Touch <touch@strayalpha.com>
Cc: "C. M. Heard" <heard@pobox.com>, Derek Fawcus <dfawcus+lists-tsvwg@employees.org>, tsvwg <tsvwg@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Pobox-Relay-ID: B8F2367C-A971-11E9-B238-72EEE64BB12D-06080547!pb-smtp2.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/A12zQDSVipFBfD6H-871cljcqXo>
Subject: Re: [tsvwg] draft-ietf-udp-options issues from IETF 104
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2019 15:35:55 -0000

On Thu, Jul 18, 2019 at 8:26 AM Joe Touch <touch@strayalpha.com> wrote:
> > On Jul 18, 2019, at 8:08 AM, C. M. Heard <heard@pobox.com> wrote:
> >
> > > Also, note that IPv6 included bits to encode whether ICMPs were sent (and
> > > whether the source is multicast).  We haven’t addressed that can of worms
> > > yet either...
> >
> > Nor will we, presumably, since UDP has no analog to ICMP messages.
> >
> > Mike
>
> UDP can cause ICMPs to be issued as per RFC1122.

Correct, it can send Port Unreachable. But that does not
apply for packets discarded because of unknown options,
and I don't see any other ICMP messages listed in Sec 4.1.

Mike

v2.23.0 | Report a Bug | By Email