IETF Logo Mail Archive

Re: [DNSOP] "flagday" again, was Re: Wrapping up draft-ietf-dnsop-dns-tcp-requirements

Joe Abley <jabley@hopcount.ca> Mon, 01 July 2019 18:29 UTC

Return-Path: <jabley@hopcount.ca>
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 F0C8F1206AE for <dnsop@ietfa.amsl.com>; Mon, 1 Jul 2019 11:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 TOz5sqi8gRAm for <dnsop@ietfa.amsl.com>; Mon, 1 Jul 2019 11:29:32 -0700 (PDT)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61CC012023F for <dnsop@ietf.org>; Mon, 1 Jul 2019 11:29:32 -0700 (PDT)
Received: by mail-lj1-x230.google.com with SMTP id t28so14222157lje.9 for <dnsop@ietf.org>; Mon, 01 Jul 2019 11:29:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:mime-version:references:in-reply-to:date:message-id:subject:to :cc:content-transfer-encoding; bh=Nr0mRn8zorJz9UEEB1jFGGWILwUEWWdCV1fLMWwc7sM=; b=CSJ36ID1fnALP5A20QToQb74n3AvpVjOqtEUFniCA48jqGtacebdLMO9pghU4dh3Zr atjlLUWwM7MFuCX7vPdDDgTRRgYN9O9n5EM5VhenAKaD+1rpALFJHzILXXpfcU58S8Ve 4PsAfqpaXXGeXxIW/AoPGJpD+nu14OU29s+sI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:references:in-reply-to:date :message-id:subject:to:cc:content-transfer-encoding; bh=Nr0mRn8zorJz9UEEB1jFGGWILwUEWWdCV1fLMWwc7sM=; b=bky4rjBAA3M8l1o4FJ14IbCurmTOMEXLxbRfYIeRv55Eizg+qtDwNfDdlc1dt8halr +4BlUuqDNtDBDiw38l2kx6uuwS/qnsXtX8dN3TxQmzTBCPW9JpLTnVIab5B+8JCk3aKS TXt9JMg5RRIYFxrfT7595xsZiGkucttJj9ny85zTXfPo9UxiEh7pYjLmhL54gWzahwCY 2vN43aiR+KgMvHZWnwqkCdUqjNr3pivM0TWCMqqHSA28aCiU7pGSLbaYbWN+A6i5dG9Z MNhP07UdAfCCrUeaWE8DCeeCK+5cq2yyNF04NgemUKgFX+/1agF6SyfU7omFe7bvkVKl gCHA==
X-Gm-Message-State: APjAAAX9rocybjvzdPwqxwrm57QC+AAwKS2q1zmlND2CDpNFZ2ikK06G NCkiuTglg/JddHA8uLaCPo9J/wxgl0D7utRkTHVp0Q==
X-Google-Smtp-Source: APXvYqwEqRuxhNTtnDtNELZlu0efR/dTCloH9snyFBeiS2YdKpt7Zcuggv1sM4CLCNFoWnwmk3t+RKxkrZFhUcrbfz0=
X-Received: by 2002:a2e:8082:: with SMTP id i2mr15145709ljg.121.1562005770490; Mon, 01 Jul 2019 11:29:30 -0700 (PDT)
Received: from unknown named unknown by gmailapi.google.com with HTTPREST; Mon, 1 Jul 2019 14:29:29 -0400
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
References: <20190625101020.3c601691@p50.localdomain> <cdb97d93-4480-08eb-436b-574fe22c4981@nic.cz> <alpine.LRH.2.21.1907011349190.28830@bofh.nohats.ca>
In-Reply-To: <alpine.LRH.2.21.1907011349190.28830@bofh.nohats.ca>
Date: Mon, 01 Jul 2019 14:29:29 -0400
Message-ID: <CAJhMdTPDekPrv4z8u1zxAi2m4SONbKx_cX461SwLfpLakmNZ8g@mail.gmail.com>
To: Paul Wouters <paul@nohats.ca>
Cc: Petr Špaček <petr.spacek@nic.cz>, dnsop@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/i3UnvRXw14qc1ief6Vq7Y4jUigY>
Subject: Re: [DNSOP] "flagday" again, was Re: Wrapping up draft-ietf-dnsop-dns-tcp-requirements
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 01 Jul 2019 18:29:34 -0000

Hi Paul,

> On Jul 1, 2019, at 14:00, Paul Wouters <paul@nohats.ca> wrote:
>
> On Mon, 1 Jul 2019, Petr Špaček wrote:
>
> [broken record on]
>
>> I would only add reference to
>> https://datatracker.ietf.org/doc/draft-ietf-intarea-frag-fragile/
>> + DNS Flag Day 2020, which is going to effectivelly kill UDP
>> fragmentation in DNS and thus require TCP for perfect operation.
>
> The internet does not do "flag days". Please stop calling it flag days.

The IETF might or might not do flag days, but the Internet
demonstrably has done, at least in the instance of the transition from
NCP to TCP/IP which gave rise to the meaning of the very phrase that
we are discussing. (Maybe the MULTICS ASCII transition was first, but
NCP -> TCP/IP certainly used the phrase.)

Whether or not the last so-called DNS flag day or the next one are
flag days according to anybody's personal definition, I think the
point was well made (in Bangkok the other month and in DC more
recently) that the use of the phrase seems have given the respective
exercises a greater sense of operational urgency, which, if true,
seems useful, necessary even.

We are in the realms of marketing, here, not niche philology. If you
want to raise awareness of something, marketing is necessary.

I don't see the benefit to anybody in complaining about it unless you
think the end goal is undesirable.


Joe

v2.23.0 | Report a Bug | By Email