IETF Logo Mail Archive

Re: Adding ECN to Transport and Recovery

Jana Iyengar <jri.ietf@gmail.com> Sun, 10 June 2018 17:14 UTC

Return-Path: <jri.ietf@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 26A32130E94 for <quic@ietfa.amsl.com>; Sun, 10 Jun 2018 10:14:43 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 lhK7ZV7HwfZ3 for <quic@ietfa.amsl.com>; Sun, 10 Jun 2018 10:14:41 -0700 (PDT)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 982E3130E7C for <quic@ietf.org>; Sun, 10 Jun 2018 10:14:41 -0700 (PDT)
Received: by mail-io0-x235.google.com with SMTP id g7-v6so21276690ioh.11 for <quic@ietf.org>; Sun, 10 Jun 2018 10:14:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Wq3feLZWLz22iPckhhgVTPmkQ0uLDkwAyVuPpiMFX7M=; b=SlQYr+1f8IhP/m6zs6zg7ZRX0yTmIFCBz1ntN1SxNIzZlTTz1hgSQMQUaeOrjdMDUW 2zK9vA9Z3iUVNsHgdccZyEB7D4Iqgr+yb9Bvt8yjsCYmdBK3LYfsp3x0arOQcx0oSBQo tTaJXZwqFLqF8+SQxh4MyNWIeDfPmq6MKp30o+zgh34SP71z9EfMWW9zTOu3kownVVIX TQhsZikF0Q/Y1bIuA8tBw32bKsCTWOTLZjIFoYR94Ckmbyx1pRIrMjxQyRIQX9TFWb/i fAbaHcwANPtIVi6shfxTZrbYaG2EQJ0fsOtB7g6VCy22H7dYsEcrr/wfF5YM6PTh9BUf Smbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Wq3feLZWLz22iPckhhgVTPmkQ0uLDkwAyVuPpiMFX7M=; b=dVPrqU8DqHREkgZHM1p6RNP5oBMcH5Lu2MbaZ/P82HvepD3mEAN/0SZDHb7uXcdbQO Ebq1dVkYDOMlD0omYg3Vk4Bcy6mE01u5X1u2TNIJaxLJNuqLrNw2h2iv4kK3Cvb6DbG7 wMl5IC2lpBmVsvRYdfR/TWtP1KqCR+oL0YA+KqjfpI2tvOOG/sy5nFMaGsNpnK86E0dr uUAb1Ryx2L6MZ05B4wkV/K7npdmpzCnWHzarrsPr9yNDHxku23RM9Pb7PFiR+rHjB8PN T0faZSihUJueoU4B0qpc4WkLb1yrhUP5pd/dgFd/dwS6xcJhEbpZefY8jsP2jsRm979E r5Ew==
X-Gm-Message-State: APt69E2Stz0FaC4obOpyGYE5KEzNpYrxNMUajWZvEp5SRzc0kGTt+PRA R34wv5E5PAapQoBJe3qyiKKCjCLs0X3jZq1Izzg=
X-Google-Smtp-Source: ADUXVKJO0f3VzponGSbASvrG25Zr16/VYVQRr7uNFvVA5ewE4a8/3NP9ikZKpVIz6GwKDMDXapoDe0Rn85wcvxp1+BY=
X-Received: by 2002:a6b:8d05:: with SMTP id p5-v6mr4913929iod.59.1528650880947; Sun, 10 Jun 2018 10:14:40 -0700 (PDT)
MIME-Version: 1.0
References: <26584f2a-230b-c55e-db16-d32225c8ee4d@ericsson.com> <5a82e9ef-971f-6510-866c-9886e73796a9@ericsson.com> <20180608150833.GB13418@ubuntu-dmitri> <CAKcm_gM_OHgWcJ+ktAg9BCQx1rtHc9GFg2bZG40-NcO2MoVG9w@mail.gmail.com> <CANatvzySuzK9EO13m_UQxb4wZkYW=+6By3QMU5gKXhq69gaUag@mail.gmail.com> <790ec098-9ec9-5eff-4785-d71d9ac92059@huitema.net> <73B82E99-EFEE-4DBC-A2CA-8FA381F33C5E@trammell.ch> <CAKcm_gN-s0XVsGL2LLusvcm5_hp-Z5_9OFMkwph5m_bGMDbAtQ@mail.gmail.com> <55DA3F1D-2B09-4D25-9630-6BC85B68A3AF@huitema.net>
In-Reply-To: <55DA3F1D-2B09-4D25-9630-6BC85B68A3AF@huitema.net>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Sun, 10 Jun 2018 10:14:30 -0700
Message-ID: <CACpbDcdTtQBLNhhiX_+wWCo-OzVvBKBpS-8RsYRcZ30xhefQZQ@mail.gmail.com>
Subject: Re: Adding ECN to Transport and Recovery
To: Christian Huitema <huitema@huitema.net>
Cc: Ian Swett <ianswett@google.com>, "Brian Trammell (IETF)" <ietf@trammell.ch>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000be98f6056e4cc4fb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fR2rjN0iC5oMOPNdghPPzQjKJtg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.26
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: Sun, 10 Jun 2018 17:14:43 -0000

Sounds like there's general agreement that modifying the varint to contain
a flag bit will add unnecessary complexity.
Let's try to get the PR in as it is now, and if anyone really wants to go
merge this and the ACK frame or rename things, let's paint that bikeshed
separately.



On Sat, Jun 9, 2018 at 8:39 AM Christian Huitema <huitema@huitema.net>
wrote:

>
>
> > On Jun 9, 2018, at 8:27 AM, Ian Swett <ianswett@google.com> wrote:
> >
> > QUIC is complex enough, I think we should just call them ACK and
> ACK_ECN.  A few implementations sending at least one ACK_ECN frame per
> connection will dispel any belief that ACK_ECN is optional.  A small amount
> of use will be a lot more valuable than clever naming.
>
> Also, ECN is just one of the extensions that could be planned for ACK.
> Timestamps would be nice too, for those who want one-way-delay based
> congestion control.
>
> -- Christian Huitema
>

v2.23.0 | Report a Bug | By Email