IETF Logo Mail Archive

Re: [Tools-discuss] Asynchronous submission

Jennifer Richards <jennifer@staff.ietf.org> Tue, 30 May 2023 13:50 UTC

Return-Path: <jennifer@staff.ietf.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03BAEC15153F for <tools-discuss@ietfa.amsl.com>; Tue, 30 May 2023 06:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, 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=staff-ietf-org.20221208.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id azTBzO8WQcNZ for <tools-discuss@ietfa.amsl.com>; Tue, 30 May 2023 06:50:39 -0700 (PDT)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3503EC14E515 for <tools-discuss@ietf.org>; Tue, 30 May 2023 06:50:39 -0700 (PDT)
Received: by mail-qt1-x834.google.com with SMTP id d75a77b69052e-3f7f864525fso49882121cf.1 for <tools-discuss@ietf.org>; Tue, 30 May 2023 06:50:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20221208.gappssmtp.com; s=20221208; t=1685454638; x=1688046638; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=rou6nxaUnBTpapKUwBQ/pqpiEgBgmXeOMUHKKl34/Es=; b=JEcvgpn06LR0h4GBFdTYH5KLOPHUc2K8cq1lN6+LEvfxmg9YCcqrHfxiOOd6+pH7HM CDOQomc/hW+w/DGGB1x/XLzIfjhvjUMts47XqauJsLedXAJEb/SUmg0mCZIBXSKhlmh2 4xl58+i/7/CRB+WRU7KF8w+vT9PiigHUpKRVPMjaWke5KExfejD09pLOGF1dnq1izwpn cEKPatBjBfJUMKmHxRKjT87sC2YtPFMJZx+b5/ik/k/QTAv0WKzQeKW2TEP4J159dFu1 0T4HOWqFSSZPFxwtOMIkodQ40lD7UAYEcR27Wo8VgHk7C82vHC5uEluXy4Hg2Qgmra+i FeTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685454638; x=1688046638; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=rou6nxaUnBTpapKUwBQ/pqpiEgBgmXeOMUHKKl34/Es=; b=hB69JUiIBU27kkomojpwRO3HyBiAwLN9+1VENa1TzgaTCoPrVimw30GVgzmwRQCBg7 VlX/LeLJPJOp59sfB5b7/LreCasoSbhaMGC5kHAGtlAQbGAEUW75Qeu5RNhXuO/H+xUe 7WLPceBTPwZW2dgwt2rlj37FUy+rcli4a6/BPEZtw/EAk5mbgjWVYaToAlVbRaxsyYFV u6vm/n7hY2WR2bKZeIcfamZuZUTNRsyHlMiDt6GEpIkCpLBoGaT1yg94EFT0VXpSLfId tJPc6jRYNvHYIIB2E0NXzOCwPRZk/5e8d+9Eb662qcfuw5WNRp0hCqL/GhEwx2gYOio+ 7Z4g==
X-Gm-Message-State: AC+VfDweXlP/jtARBDCwYuiIycY0KDkAkNfJkHrYbjdprGZLxbWXFtUd QlQv+bWd7iojPpq+9SxvXTZJV2NE1W096wNUQ+cPDFB3
X-Google-Smtp-Source: ACHHUZ4lFK7IeMF1KsDw/HJB3QK8E2us7xgLmkE/vwiJZkuBn1VCY3t8H01ftOQb2rDuosiwsJY/vA==
X-Received: by 2002:ad4:4ea4:0:b0:626:e55:dfaa with SMTP id ed4-20020ad44ea4000000b006260e55dfaamr2411053qvb.48.1685454637966; Tue, 30 May 2023 06:50:37 -0700 (PDT)
Received: from [192.168.50.101] (hlfxns018gw-134-41-156-209.dhcp-dynamic.fibreop.ns.bellaliant.net. [134.41.156.209]) by smtp.gmail.com with ESMTPSA id z7-20020a0cfec7000000b0061fb6cc2051sm1663039qvs.15.2023.05.30.06.50.37 for <tools-discuss@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 30 May 2023 06:50:37 -0700 (PDT)
Message-ID: <b375b834-33d2-bd23-53f4-1054d2f5758e@staff.ietf.org>
Date: Tue, 30 May 2023 10:50:36 -0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.11.2
To: tools-discuss@ietf.org
References: <E5FE4F29-B372-4191-8BC9-DDF8545DEC0D@tzi.org>
Content-Language: en-CA
From: Jennifer Richards <jennifer@staff.ietf.org>
In-Reply-To: <E5FE4F29-B372-4191-8BC9-DDF8545DEC0D@tzi.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/2LHLlR4scHgqM5BfMw5Y72IQr14>
Subject: Re: [Tools-discuss] Asynchronous submission
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 May 2023 13:50:40 -0000

On 2023-05-27 5:43 a.m., Carsten Bormann wrote:
> The user experience is jarring.
> The refresh interval is way too long(*) for something that usually took about a second in the previous version.
> Of course, I now know that I can simply CMD-R (F5), but that behavior becoming ingrained may be counterproductive.
> 
> So maybe some adaptive refresh interval (with binary exponential backoff?) would be a useful enhancement.
> 

It's 30 seconds, and you're right it's often too long. What's there now 
was a quick and dirty implementation to support the switch to 
asynchronous validation.

There's an existing API endpoint for checking the draft status that we 
should use to improve the update strategy.

https://github.com/ietf-tools/datatracker/issues/5714

jennifer

v2.23.0 | Report a Bug | By Email