Re: [alto] Benjamin Kaduk's No Objection on draft-ietf-alto-path-vector-24: (with COMMENT)

kaigao@scu.edu.cn Sun, 20 March 2022 00:46 UTC

Return-Path: <kaigao@scu.edu.cn>
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 615F43A1879; Sat, 19 Mar 2022 17:46:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 f1U2o0T-zX6d; Sat, 19 Mar 2022 17:46:19 -0700 (PDT)
Received: from zg8tmty1ljiyny4xntqumjca.icoremail.net (zg8tmty1ljiyny4xntqumjca.icoremail.net [165.227.154.27]) by ietfa.amsl.com (Postfix) with SMTP id 495D73A1876; Sat, 19 Mar 2022 17:46:16 -0700 (PDT)
Received: by ajax-webmail-app1 (Coremail) ; Sun, 20 Mar 2022 08:46:08 +0800 (GMT+08:00)
X-Originating-IP: [125.70.169.211]
Date: Sun, 20 Mar 2022 08:46:08 +0800
X-CM-HeaderCharset: UTF-8
From: kaigao@scu.edu.cn
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, alto-chairs@ietf.org, draft-ietf-alto-path-vector@ietf.org, alto@ietf.org
X-Priority: 3
X-Mailer: Coremail Webmail Server Version XT5.0.13 build 20210104(ab8c30b6) Copyright (c) 2002-2022 www.mailtech.cn mail
In-Reply-To: <164771169135.16614.10030113436677327902@ietfa.amsl.com>
References: <164771169135.16614.10030113436677327902@ietfa.amsl.com>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Message-ID: <1582519a.1d875.17fa4c9e243.Coremail.kaigao@scu.edu.cn>
X-Coremail-Locale: en_US
X-CM-TRANSID: 4wAACgBXX0NQeTZiUhdcAA--.3073W
X-CM-SenderInfo: 5ndlwt3r6vu3oohg3hdfq/1tbiAQULB138kmLbvQAAs-
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VWxJw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/BFM6fDzbgPuJGa8GyzrdJLWtHWo>
Subject: Re: [alto] Benjamin Kaduk's No Objection on draft-ietf-alto-path-vector-24: (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: Sun, 20 Mar 2022 00:46:23 -0000

Hi Ben,

Thanks for the feedback. Please see inline for the response.

Best,
Kai


&gt; -----Original Messages-----
&gt; From: "Benjamin Kaduk via Datatracker" <noreply@ietf.org>
&gt; Sent Time: 2022-03-20 01:41:31 (Sunday)
&gt; To: "The IESG" <iesg@ietf.org>
&gt; Cc: alto-chairs@ietf.org, draft-ietf-alto-path-vector@ietf.org, alto@ietf.org
&gt; Subject: [alto] Benjamin Kaduk's No Objection on draft-ietf-alto-path-vector-24: (with COMMENT)
&gt; 
&gt; Benjamin Kaduk has entered the following ballot position for
&gt; draft-ietf-alto-path-vector-24: No Objection
&gt; 
&gt; When responding, please keep the subject line intact and reply to all
&gt; email addresses included in the To and CC lines. (Feel free to cut this
&gt; introductory paragraph, however.)
&gt; 
&gt; 
&gt; Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
&gt; for more information about how to handle DISCUSS and COMMENT positions.
&gt; 
&gt; 
&gt; The document, along with other ballot positions, can be found here:
&gt; https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/
&gt; 
&gt; 
&gt; 
&gt; ----------------------------------------------------------------------
&gt; COMMENT:
&gt; ----------------------------------------------------------------------
&gt; 
&gt; -22 to -24 should resolve discuss
&gt; 
&gt; A huge thanks to all involved for the quick turnaround in updating this
&gt; document and getting draft-bw-alto-cost-mode in place to help
&gt; rationalize the IANA registry situation across the ALTO documents!  I'm
&gt; sorry that my turnaround time here was not so quick.
&gt; 
&gt; Fortunately, I can report that the changes address my previous Discuss
&gt; concern and comments, and I have just one additional comment, in Section 6.5.2:
&gt; 
&gt;    The cost mode "array" indicates that every cost value in the response
&gt;    body of a (Filtered) Cost Map or an Endpoint Cost Service MUST be
&gt;    interpreted as a JSON array object.  This cost mode can be applied to
&gt;    all cost metrics.
&gt; 
&gt; Would it be accurate to say that "additional specifications will be
&gt; needed to clarify the semantics of the array cost mode when combined
&gt; with path metrics other than 'ane-path'"?

It is a very good suggestion. We will integrate the proposed text at the end of
the paragraph as follows:

    While this cost mode can be applied to all cost metrics, additional
    specifications will be needed to clarify the semantics of the array cost mode
    when combined with cost metrics other than 'ane-path'.


&gt; That is to say, I do agree that the cost mode should be applicable to
&gt; all cost metrics, but I'm not sure if the current specifications are
&gt; unambiguous about what it means to have an array of ordinal, for
&gt; example.
&gt; 
&gt; 
&gt; 
&gt; _______________________________________________
&gt; alto mailing list
&gt; alto@ietf.org
&gt; https://www.ietf.org/mailman/listinfo/alto
</iesg@ietf.org></noreply@ietf.org>