IETF Logo Mail Archive

Re: [Masque] Erik Kline's Yes on draft-ietf-masque-h3-datagram-10: (with COMMENT)

Erik Kline <ek.ietf@gmail.com> Wed, 15 June 2022 21:00 UTC

Return-Path: <ek.ietf@gmail.com>
X-Original-To: masque@ietfa.amsl.com
Delivered-To: masque@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32E5FC15AAC5; Wed, 15 Jun 2022 14:00:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LFniy6swBF7D; Wed, 15 Jun 2022 13:59:55 -0700 (PDT)
Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com [IPv6:2607:f8b0:4864:20::232]) (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 9AB68C157B5E; Wed, 15 Jun 2022 13:59:55 -0700 (PDT)
Received: by mail-oi1-x232.google.com with SMTP id p8so12662844oip.8; Wed, 15 Jun 2022 13:59:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bI4475OTTWjdbBp5HEybYQ0shrid4dWxBGJJS2oWu9k=; b=VqOfBg88u3k3v2FhYvVyNYJWgqNCADOcjJYiUOsHrO/0FfNPSd7Tt/oFby1KOAVBR5 XlmMoQzrz6NdV78iq1kAlacG2Plc2psvqJHTDqx8a3gZJ8k0RDO7zJ+DSqG4UqpYytvD 1F5BVNO1c4yeJzV4y3RrtYFuCbms2UfbeVdOCxYQbHyRlvc/CukEM6zVNdZvz7hv9BJW pGO28ZnpehFW1q8X8oV1ahTNpHVRc7oBySa7LJ/UecqmNHD0ghDkSHhS6gcMw5a8qv20 ecICCumjwbyJOaYaQx0d13trjxJQGRiwO+yOIyVjbhsxCGV/W6/JnOXlioOQ6Pr+oxzM hGHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bI4475OTTWjdbBp5HEybYQ0shrid4dWxBGJJS2oWu9k=; b=uZ1lcCxxcl64qCabuS8VaCdlvkH3oAqWup7JIlDD665ZJ9UDZHE54rHkIFna3M4LJj UrgFi4KV+7VY7d01wJ9irUCSkABepwnXdAYnd6ZIN1HxpJ305nJuzF8rEUtDL9FphAD/ M89LLNRewNOdyxVbvQ3H6hoY7wEQ2syugfSfVCl6dLdxww5ziugEYpzxalevn2FPLTmS 6gVu9WxrPiIqUU3fLLPyC/N+w89oIFbhmuhW9Gh0qmzWf++kDJcnd8z6VIpgZAknZyn0 9Q7VGEBkZ+I+q6EspbpG9zh5s/rh2hO7KuNHQRiqXEYdie8OVbdJ8L//bon4FhHrkayu PFkA==
X-Gm-Message-State: AOAM53027sp1kLZ5td8gBdRyrMNtzc7sGOAh3caxRuCIn6hVAnsT4Mmj ylySJEg8zJw4tmuLNmTUJU+tCmsr902oD5Kpn/8=
X-Google-Smtp-Source: ABdhPJzm8wvggc+sn1rk1GlUFgWi2cYuGt/7QUGKGIGWkX3CWB2/jG36KtWOn+l+S3x724n31BecgCbQT97xbKfUcY0=
X-Received: by 2002:a05:6808:f92:b0:32f:33af:7234 with SMTP id o18-20020a0568080f9200b0032f33af7234mr6124847oiw.99.1655326794241; Wed, 15 Jun 2022 13:59:54 -0700 (PDT)
MIME-Version: 1.0
References: <165507272176.13413.7473506800933970739@ietfa.amsl.com> <CAPDSy+4fcBSVR0m4SwGfoWvaBAD7ZuwTpSqEZ1-i=CXh=hmzXQ@mail.gmail.com>
In-Reply-To: <CAPDSy+4fcBSVR0m4SwGfoWvaBAD7ZuwTpSqEZ1-i=CXh=hmzXQ@mail.gmail.com>
From: Erik Kline <ek.ietf@gmail.com>
Date: Wed, 15 Jun 2022 13:59:43 -0700
Message-ID: <CAMGpriU+D1=gC_ONFL4UdSxgQUCWOqdczVb9+ZEo8PWLOVmoGg@mail.gmail.com>
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-masque-h3-datagram@ietf.org, masque-chairs@ietf.org, MASQUE <masque@ietf.org>, Christopher Wood <caw@heapingbits.net>
Content-Type: multipart/alternative; boundary="0000000000008ed86105e182cd50"
Archived-At: <https://mailarchive.ietf.org/arch/msg/masque/4JsZtspqfSfhFJQiRmi_n05x0MI>
Subject: Re: [Masque] Erik Kline's Yes on draft-ietf-masque-h3-datagram-10: (with COMMENT)
X-BeenThere: masque@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Multiplexed Application Substrate over QUIC Encryption <masque.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/masque>, <mailto:masque-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/masque/>
List-Post: <mailto:masque@ietf.org>
List-Help: <mailto:masque-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/masque>, <mailto:masque-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2022 21:00:00 -0000

SGTM, thanks!

On Wed, Jun 15, 2022 at 1:58 PM David Schinazi <dschinazi.ietf@gmail.com>
wrote:

> Thanks for your review, Eric!
> Responses inline.
> David
>
> On Sun, Jun 12, 2022 at 3:25 PM Erik Kline via Datatracker <
> noreply@ietf.org> wrote:
>
>>
>> * Possibly the definition of Capsule Type should mention the IANA registry
>>   via a short reference ("; see Section 5.4").
>>
>
> Agreed, added via this commit:
>
> https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/commit/cd550aee6dd871d7396ee97b7a3e42642ee5535c
>
> * If new 2xx codes are defined in the future, are they required to state
>>   what their suitability is in scenarios upgrading to Capsule Protocol
>> use?
>>
>>   If so, is there any additional guidance beyond what one could divine
>>   from a reading of the 2nd to last paragraph?
>>
>>   (New 2xx codes seem extremely unlikely, but is such a thing completely
>>    impossible?)
>>
>
> New 2xx codes have specific semantics that are well-defined in Section 15
> of RFC 9110: clients MUST treat any unknown 2xx error code as 200. Any
> new 2xx code that is defined after this specification is published will
> therefore
> know that existing implementations will by default treat them as 200. If
> they
> want different treatment, they'll have to specify it. Since this is
> guaranteed
> by the semantics of HTTP status codes, I don't think there's anything to
> add to this document.
>

v2.23.0 | Report a Bug | By Email