Some late comments on draft-ietf-quic-load-balancers
Watson Ladd <watsonbladd@gmail.com> Thu, 11 March 2021 22:48 UTC
Return-Path: <watsonbladd@gmail.com>
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 9CC723A105D for <quic@ietfa.amsl.com>; Thu, 11 Mar 2021 14:48:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 AsSwzBpnwi0z for <quic@ietfa.amsl.com>; Thu, 11 Mar 2021 14:48:19 -0800 (PST)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 5B7433A105B for <quic@ietf.org>; Thu, 11 Mar 2021 14:48:19 -0800 (PST)
Received: by mail-ed1-x52a.google.com with SMTP id x21so5252848eds.4 for <quic@ietf.org>; Thu, 11 Mar 2021 14:48:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=2Ri43mwL6rQPU5QqYbTGCIkzmjz+SbTfAqmWBTBrV5M=; b=iUe7kJJIxslKz5wtbzbdXMWXb1Pd3tJ7Q2GZP2jXetGQ1ToQllva5NYE/YPzuQavKu jprpKBy/Jft2u3N7C/hBNKXP4CD2XU+/dHo6HCMh0727m5IoG+uDjo4ftXHpPv+KOdWC OwZYp4EiZ0Rd1q11B71DpR8yt5nTPX+kqGfUYbUeBSDvhXZIkR0NqF79559p/xVJSQrt EBeyWfdHyMi7duoGwEv/h8TuiEEEsNvBvKdcXEHHVTiFqF3tfnLEVUfRo8bSh3SRiIRs p9uEqGKxMjuekx+RuQAX0zOUJSSdWGqEp+JKwE/djBYp1V2FmphyuxZcHkrgWc2CeK43 rIMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=2Ri43mwL6rQPU5QqYbTGCIkzmjz+SbTfAqmWBTBrV5M=; b=SRC8GV4+LfeQY5Os0Mi3czAXnzoY3g1v+Yos3QmpAfUkRJphPUleeQZV0trTZm7s5R Ulg7SZ6w0BkYGtxKThWsvv2UvwjO7AOCg/DIPMQm/mCEQ0ySd3d14P8UwQWV37ppgRzi fTj+5DnVB0B/hVvWx4V+iYrnm6CI8KnTGcuTxsBSUmr71Ffx0eIXMcEr6E6gS5yqyHPj XTWE4uCQ8PcAN/Xityk9OWB3gTWJokFbmD2rAOFfABUfzWAPAplQU4m3o2o2g/gog8iA qOTCSc0g7/A2NW/GvUAOrNIVSeVerZezC115qEFt3OKFJg5IAJeShZl8uWufynyxRD/O 9l7g==
X-Gm-Message-State: AOAM531ZXggTtU9MAAJHyrdvDlCWGmGGf0sOqApxU1CLr+AvY9ay9dqv cl3TJvGh39KEOmJtVXIqJoKkG2FNYpe7Yccdms10mA61xxY=
X-Google-Smtp-Source: ABdhPJz1ygyLUaQC4OH0yYbEPYOtpdH3mSk7cxoAMQ3f2ArZ1NNK7XaFQBnqPeo7HhSVM8vOokjooE8RWj3mTAlT9Jo=
X-Received: by 2002:aa7:d4cb:: with SMTP id t11mr10768258edr.202.1615502897008; Thu, 11 Mar 2021 14:48:17 -0800 (PST)
MIME-Version: 1.0
From: Watson Ladd <watsonbladd@gmail.com>
Date: Thu, 11 Mar 2021 14:48:05 -0800
Message-ID: <CACsn0cn70MK699XyWmYp7i3nw7TSwPS4q94A4BFf4FFVy9MNrg@mail.gmail.com>
Subject: Some late comments on draft-ietf-quic-load-balancers
To: IETF QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/xcP0cwxpu1GcUnl4_XSBN70hF8E>
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: Thu, 11 Mar 2021 22:48:21 -0000
Dear QUIC WG, First a moment of unforgivable pedantry. Universal time is unfortunately not the right name for UTC, which is slightly different. It could also mean UT1 or some other variations It's also not clear what the future of computer timekeeping is and I know several places don't synchronize to UTC internally. I think the best way to handle this is to say something like "synchronized" and leave open as to exactly how that is done. I agree with the comments that there are too many options and should be fewer. Other then that I didn't see any problems but I'm probably too sleepy right now to spot them. Sincerely, Watson Ladd -- Astra mortemque praestare gradatim
- Some late comments on draft-ietf-quic-load-balanc… Watson Ladd
- Re: Some late comments on draft-ietf-quic-load-ba… James
- Re: Some late comments on draft-ietf-quic-load-ba… Mikkel Fahnøe Jørgensen
- Re: Some late comments on draft-ietf-quic-load-ba… Martin Duke