Re: [alto] Shepherd writeup for path-vector (draft) Tue, 12 January 2021 11:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3B3773A1165 for <>; Tue, 12 Jan 2021 03:39:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UwEWAOsCiYzl for <>; Tue, 12 Jan 2021 03:39:12 -0800 (PST)
Received: from ( []) by (Postfix) with SMTP id 135013A1164 for <>; Tue, 12 Jan 2021 03:39:11 -0800 (PST)
Received: by ajax-webmail-app1 (Coremail) ; Tue, 12 Jan 2021 19:39:06 +0800 (GMT+08:00)
X-Originating-IP: []
Date: Tue, 12 Jan 2021 19:39:06 +0800 (GMT+08:00)
X-CM-HeaderCharset: UTF-8
To: "Vijay Gurbani" <>
Cc: "IETF ALTO" <>, "Qin Wu" <>
X-Priority: 3
X-Mailer: Coremail Webmail Server Version XT5.0.13 build 20200820(b2b8cba1) Copyright (c) 2002-2021 mail
In-Reply-To: <>
References: <> <>
Content-Type: multipart/alternative; boundary="----=_Part_195021_1743707763.1610451546131"
MIME-Version: 1.0
Message-ID: <>
X-Coremail-Locale: en_US
X-CM-TRANSID: 4wAACgDXOYxaiv1fRI8cAA--.2720W
X-CM-SenderInfo: 5ndlwt3r6vu3oohg3hdfq/1tbiAQQTB138kknmPwAAsy
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VWxJw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <>
Subject: Re: [alto] Shepherd writeup for path-vector (draft)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 12 Jan 2021 11:39:16 -0000

Hi Vijay,

How do you do? We have fixed most of the IDNits errors/warnings with a new revision -14. The remaining warnings are:

1. IDNits identifes [TBD] as references but we are using them in examples as placeholders for content length values.

2. IDNits thinks the version of [I-D.yang-alto-deliver-functions-over-networks] is -00 but the latest version as we used in the draft is -01.

How do you suggest we proceed here? Do you think we can submit -14 right now? Or we should wait for your review on -13?




-----Original Messages-----
Sent Time:2021-01-12 17:46:53 (Tuesday)
To: "Qin Wu" <>
Cc: "IETF ALTO" <>
Subject: Re: [alto] Shepherd writeup for path-vector (draft)

Hi Qin,

Thanks for the notification! I will fix the IDNits errors as soon as possible.


2021-01-12 09:45:08"Qin Wu" <>wrote;wrote:

Hi, authors of path-vector:

I haven’t seen you addressed IDnits errors raised by Vijay below:

Please reply to Vijay and confirm whether there are anything missing or open issues which haven’t been closed.


-Qin (With chair hat on)

发件人: alto [] 代表 Vijay Gurbani
发送时间: 2020年12月2日 1:36
收件人: IETF ALTO <>
主题: [alto] Shepherd writeup for path-vector (draft)


All: I have started the shepherd review of path-vector  The review is below.

The token is with me to do a chair/shepherd review of the draft.  With the semester coming to a close and grading to do, etc., I have reserved the week starting Dec-16 to do the shepherd review of the draft.


In the meantime, please go through the draft shepherd writeup and let me know if I have erred anywhere.




- vijay


Shepherd writeup for draft-ietf-alto-path-vector-13

1. Summary.

The document shepherd is Vijay K. Gurbani, and the responsible area director is Martin Duke.

The document is a Standards Track document, targeted as a Proposed Standard.  The WG has chosen the requested publication type since this draft extends the base ALTO protocol in a normative manner.  Specifically, the document seeks to extend the base ALTO protocol (RFC 7285) to provide the concept of "Abstract Network Elements" (ANE).  ANEs are an abstraction of physical network components --- routers, etc. --- that handle (switch) packets.  An application whose performance may be impacted by a particular traversal path in the network may wish to consult the ANEs to determine an optimized path to the destination.

This draft is a major conceptual advance in the abstractions provided by the base ALTO protocol.

2. Review and consensus.
This work is mature.  It started off as an individual submission in March 2015, and was adopted as a WG deliverable in May 2017.  A detailed review of this draft was provided early on by Sabine Randriamasy [1,2,3] shortly after it was adopted.  Version -04 was further reviewed by Danny Perez [4] and Qiao Xiang [5] in 2018, and the work progressed appreciably between 2018 and 2019, resulting in the release of -09 in November 2019.

A WGLC was initiated on Sep-28-2020, and a review was provided by Qiao Xiang [6] and Luis Contreras [7] on version -11.  Version -12 included the comments from Qiao and Luis, with version -13 following with some minor revisions.

Earlier versions of path-vector have been implemented (without the integration of unified-props); the implementation was used in a super computing conference demonstration for OpenFlow-based networks [8].  The latest version of path-vector is being implemented and will be open-sourced on GitHub [9].

The shepherd has an action item to review version -13.

3. Intellectual property
All of the authors have confirmed with the shephered that they are not aware of any IPR filed with respect to the draft.

4. Other points
IDNits reports 1 error, 7 warnings, and 2 comments.