[alto] Moving path-vector-14 ahead

Vijay Gurbani <vijay.gurbani@gmail.com> Fri, 18 June 2021 14:28 UTC

Return-Path: <vijay.gurbani@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 3ED873A44FF; Fri, 18 Jun 2021 07:28:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, URIBL_BLOCKED=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 HJXNOGkdsXMY; Fri, 18 Jun 2021 07:28:53 -0700 (PDT)
Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (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 7AEAA3A4365; Fri, 18 Jun 2021 07:28:53 -0700 (PDT)
Received: by mail-qk1-x72c.google.com with SMTP id bj15so9725188qkb.11; Fri, 18 Jun 2021 07:28:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=J51tY3vU4nOQiiIQqMm6Js+q6HQrUC4f33AQlL3uzEE=; b=STGZfOswvgBMT+DgvVTym/NSvl+X37hLXwRiyOYzyThgh1piMZ1SKGZVmOaKVlAOt2 KACNmh98x+dzXrzK4sGTPZDXX+MmnyjuMXCceJ4q6XHzb4Mto/rBSYv3tj4fPvpiKC9P 161alNgY8x/yUjLWtwV14l8uMyaoqwQXilyOBA+LFxXsoctijtvxgUeLInbvdZcCXzEQ Xf2jf5uiTSlFWsATTm1QkdjUsHp7winGxaXS4Lq7kBVKNS1Q7S3I9nBEzb4SJO+VqKa+ CjquvYuA1iDDgAua4ebfLQT/FggIfnNZWELoEeI7d2j9OIiPlsyFyOT4Npv8IG1jr+MS m2SA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=J51tY3vU4nOQiiIQqMm6Js+q6HQrUC4f33AQlL3uzEE=; b=FBIsPHW7ERSP7MA2HBQpy2w/0ZcC1HSbOguZJq0hzkUhBkx38uqpMirwTMgIS9sOQ1 Dj2Ypm+ZqSL05lI6l7rEVnZNTwmnfFQh81ZzaLg1/HV+bKvWlV7csjRkWWvTRhAEkYM9 WZ74SUeFe6ESxPl/5/fgKiKc+X0V6ke22GhqpYrv3RfAnr4k/TD0UF6Q5FxsK0D+3o/R zRqev75DBu4tTzCwEbRU5w0aKN12+QJzI3TbTkY0zn342Keb2ramgbmgiKGrELoBtXGQ 3B1zSosFyK01GqoAk3zA1OYK6XckwClR+hS+i6G9LH4BvVi+thUgrpt1wFIklzxPvALL VgcQ==
X-Gm-Message-State: AOAM530/SN4g+RdluCNAiE9zEA/6DUdLj85SXbQJPm+k/LaerQJNkBkC 6MN236y56b4RC/6szcdS0VpH0C/QOQvA454naFr3nxmpVhMtaw==
X-Google-Smtp-Source: ABdhPJwHSX/alcAkoY+Tale0O0bRKDWYNJtWr5Tn6DjPGXsYvHaoZiGImlspcy8HsIT6Ngac/3fM1ysRn2alqGHEuxw=
X-Received: by 2002:a25:389:: with SMTP id 131mr13895570ybd.306.1624026527226; Fri, 18 Jun 2021 07:28:47 -0700 (PDT)
MIME-Version: 1.0
From: Vijay Gurbani <vijay.gurbani@gmail.com>
Date: Fri, 18 Jun 2021 09:27:32 -0500
Message-ID: <CAMMTW_+2pxgK3WkUiNriLTV8t7zZoSFjPYX8G2nEEJfr8BBEnw@mail.gmail.com>
To: draft-ietf-alto-path-vector@ietf.org
Cc: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000042ddca05c50b24a8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/YVDZ-QKR8u-eOJGndiP2yhkYAJE>
Subject: [alto] Moving path-vector-14 ahead
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: Fri, 18 Jun 2021 14:28:58 -0000

Dear Authors: I am moving path-vector ahead based on the revised version
(-14) that addresses my comments from the chair reviews [1,2].

Thank you for your time and attention to the draft.

With respect to my comment in S6.4 in my chair review [1]:
> - S6.4: Why have a mini Security Considerations paragraphs in the
subsections
> of S6.4, [...]

You replied:
> [PV] The reason of having mini security consideration paragraphs in
Section
> 6.4 is because the document defines two properties in Section 6.4 and the
> Unified Property document asks for security consideration when defining
> a new property. However, for cost type definition, such a paragraph is
> not formally required so we do not include one.

That is okay, I guess.  Although I think that you could define a subsection
in the normal Security Considerations section and have a forward reference
from S6.4 to that subsection.  You do not need to do this for the draft
to proceed right now, but do be prepared to justify your decision
when the IESG reviews the draft if they bring up this point.

[1] https://mailarchive.ietf.org/arch/msg/alto/0V-LL8dk5LRvO2zQ0F6hUYwYi-g/
[2] https://mailarchive.ietf.org/arch/msg/alto/6oYr0rjU9ZB_gG9muNLGrJknvPM/

- vijay