Re: [alto] Murray Kucherawy's No Objection on draft-ietf-alto-cdni-request-routing-alto-17: (with COMMENT)

Jensen Zhang <jingxuan.n.zhang@gmail.com> Wed, 08 December 2021 11:44 UTC

Return-Path: <jingxuan.n.zhang@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E33743A043E; Wed, 8 Dec 2021 03:44:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 Y_-NzforMGgP; Wed, 8 Dec 2021 03:44:08 -0800 (PST)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (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 E44033A0433; Wed, 8 Dec 2021 03:44:07 -0800 (PST)
Received: by mail-wr1-x436.google.com with SMTP id v11so3547405wrw.10; Wed, 08 Dec 2021 03:44:07 -0800 (PST)
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=BYGxhMAtK8o2ZcBZJDGadslLWb+RwAStazFwJmZaVus=; b=NzJ0JlBrHYMT/eBud49q1WtU8j3+D/v4cdQM3BrDIG/kSoNV2K4p4RqFx/C25zGmS5 M6KV0xfwQwrztJFeY1VJk4MsclRJD2SGvPgqn4xKgQzyO1hf2oh0gvjgsGAI52iZub8R i0nHZJw/oYhrlzvdUntn7OTet+lWzVgwg7Zbtbx+KNzMZMyNsFShYAq/i+9Iq8CJdr8o rZea/1kgKKI1nhqlN88X3D3UrS39xzMm6A5oWtIfy/vg4+DFWsppYCBMzxnuZOcmJJTm bFe4pn2VtjJ/XjOSIi1TMhWqszAG+xIFkWuCtTS1Pp6r7QVdSa1p0+v/nOV5J8uCk3Ot lEiA==
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=BYGxhMAtK8o2ZcBZJDGadslLWb+RwAStazFwJmZaVus=; b=oXwAb1YiVQyy7al60m8RMQ4w6PwThcVmVscfRoxQ8ZQLFglJMG33ZrIkIZNLJ3AyZc tkm/GSQhRqJtVyg8QA+qT/AsP1CI+8LPysZ9OmUhhzThxkJQZXsqIimVdEd8pvWCuiIA spdVkm2Nr9ehkeWoIizHqQhqXtmdyfnc2W+M1SeuODalpSLGX2LlZu0B/+SOYEE8VqfX RyN/G1K698P8CZ56w19ZETpGbaHqvDQ3CBMs0g3zNYVHw1L97TCKbQH7AoeQE2ZNcgQZ qOFs4Hg9fQHCR9v/PfayBq7QlzaU/JghviRcCUZjeIHa62ihIEPRhbjn2Glkf6VNUsJw WECA==
X-Gm-Message-State: AOAM5337CNcYEfl4U88TLIGGrMKD3Kr6LvTwjgxfYjsTJZc1xQHAKuGn ziDStbSG1r+VpUpvkV51VFfNFueFLkBqAuNejcvhGWUh/8k=
X-Google-Smtp-Source: ABdhPJx8bLq823SbtseQKQMgW7wISMdMQ7a/3wHrzC9mbNu+torMBDeSimvyaK5AnTjVyc83L6NZ/wL2uRcvyGe97+Y=
X-Received: by 2002:a05:6000:1889:: with SMTP id a9mr60084366wri.68.1638963845738; Wed, 08 Dec 2021 03:44:05 -0800 (PST)
MIME-Version: 1.0
References: <163877668298.13140.15483213781687203079@ietfa.amsl.com> <CAAbpuyrPOv3D5wZFEYivdwof9yWyOpDCczqNNqnM3Mgkxs2NYw@mail.gmail.com> <CAL0qLwbiiV7hH0-=revXFt5ZJPo0CePqgmhEerk1b0ovxgs4+w@mail.gmail.com>
In-Reply-To: <CAL0qLwbiiV7hH0-=revXFt5ZJPo0CePqgmhEerk1b0ovxgs4+w@mail.gmail.com>
From: Jensen Zhang <jingxuan.n.zhang@gmail.com>
Date: Wed, 08 Dec 2021 19:43:55 +0800
Message-ID: <CAAbpuyoBOTAo7Qo9mzgrPQsSrnrBaxsmVy=Mvd6Bmwm8S_jwcg@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: The IESG <iesg@ietf.org>, alto-chairs <alto-chairs@ietf.org>, IETF ALTO <alto@ietf.org>, draft-ietf-alto-cdni-request-routing-alto@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d332ea05d2a10178"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/qAb01Trajb8qz8kCDQMeqx9-AKA>
Subject: Re: [alto] Murray Kucherawy's No Objection on draft-ietf-alto-cdni-request-routing-alto-17: (with COMMENT)
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Dec 2021 11:44:10 -0000

On Wed, Dec 8, 2021 at 3:02 PM Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Tue, Dec 7, 2021 at 4:03 AM Jensen Zhang <jingxuan.n.zhang@gmail.com>
> wrote:
>
>>
>> The "Interoperability considerations" part of Section 7.1 doesn't seem to
>>> be a
>>> complete answer to the corresponding guidance in Section 6.2 of RFC 6838.
>>>
>>>
>> The authors will be appreciated if you can give any further comments or
>> suggestions on this.
>> For our understanding, the referenced sections in the registration table
>> ("Specification" column) have described the structure and parsing of the
>> corresponding messages. Are they not enough for the "Interoperability
>> considerations"? Could you give any tips about what is missing here? Many
>> thanks.
>>
>
> Sure.  The paragraph I'm citing in RFC 6838 says this about
> Interoperability Considerations:
>
>       Any issues regarding the interoperable use of types employing this
>       structured syntax should be given here.  Examples would include
>       the existence of incompatible versions of the syntax, issues
>       combining certain charsets with the syntax, or incompatibilities
>       with other types or protocols.
>
> Your document has this text:
>
>       This document specifies formats of conforming messages and the
>       interpretation thereof.
>
> What your text tells me is that your document describes what a valid
> instance of this media type's payload looks like.  That's sort of obvious
> though.  What RFC 6838 is asking for goes beyond that, and gives a few
> examples of what you might want to discuss here.
>
> If there were no prior versions of this media type, and it has no known
> incompatibilities with other protocols or character sets, etc., you can
> simply put "None" in this part of the form.  Or if there is something that
> should be considered, this part of the form should include such a
> discussion.
>

Many thanks for your clarification. As far as I know, the new registered
media types do not have any prior versions. They do neither have any known
incompatibility issues. Are you suggesting that we should explicitly put
such statements in the paragraph?

Jensen


>
> -MSK
>