[alto] Fwd: Publication has been requested for draft-ietf-alto-performance-metrics-15

Jan Seedorf <ietf@j-f-s.de> Sun, 21 March 2021 22:43 UTC

Return-Path: <ietf@j-f-s.de>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 3119A3A1125 for <alto@ietfa.amsl.com>; Sun, 21 Mar 2021 15:43:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.004
X-Spam-Status: No, score=0.004 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id aaXQgRfADndN for <alto@ietfa.amsl.com>; Sun, 21 Mar 2021 15:43:18 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDFC83A1123 for <alto@ietf.org>; Sun, 21 Mar 2021 15:43:17 -0700 (PDT)
Received: from JANs-MacBook-Pro.local ([]) by mrelayeu.kundenserver.de (mreue011 []) with ESMTPSA (Nemesis) id 1M9nhF-1lILdH2BjJ-005tNj for <alto@ietf.org>; Sun, 21 Mar 2021 23:43:14 +0100
References: <161636623750.17279.11653362689005435027@ietfa.amsl.com>
To: alto@ietf.org
From: Jan Seedorf <ietf@j-f-s.de>
X-Forwarded-Message-Id: <161636623750.17279.11653362689005435027@ietfa.amsl.com>
Message-ID: <c0d315e6-be88-4f14-1ada-93196dcfa6fa@j-f-s.de>
Date: Sun, 21 Mar 2021 23:43:13 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <161636623750.17279.11653362689005435027@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------BE798A8C69949373912C63DD"
X-Provags-ID: V03:K1:V16rdYYPn87qlBVoP6dt8eHZbKQvSjjpPEosZ2wHEO4YDiDgQ9a 8ut3cZwx2PnlUlVjG8QVHuGiSgKj+79H/Pvfi7F62jC/hVJYBLPT0Je0Ti97GfQO3PyCC8K 1rz9KwakleqgRC5oE97pZUbUuY2Tl2Gi7yxLRGZZrETRRvWyLXoirNyXZwU0qk+WyEyKbAX COGd75MIlPClkp/ya1/oQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:mh31eAjTR4M=:Re7MGVmXRIUuixMjAda+8G vdBzAQjcW76BYrDZ1NY3VIs4GxL9lD0tSP36ZPjmF2AneTyE18ZplvjmbW1NAkjHGi8L6TTWx aPh1o49ROehpbAR1V+fZIq1UEdlCIa52JRcCDF6vA0v45fSRr6vO+cKuVmk0LkwOXZss2isEH 83YWDCUFB3QkUsuu6eq/dKzM7smW0oCStnueeo37QpB1Q9rkdo82K59NG5Hs3DsTfU3e3QkN4 LbIxY6r5An2DbPppaQDhzdIrtarjQOYUW/6Xv9EOW7lYfyIGrT7mqCq+czlGrjIKmDSMNUant 7peVZaVzJemS7JaRDktavdc/FxSaCG+bMY6qz64484Lg/MpqqzDeBRqUtb/x5G/2/KhOsLq3H cbyIK1kHtqBTpOPC0zScVICGQvU7l3NvkQOSqaVtqt45Gxq4+t6Uox749ydiv
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/193xZPueDH3cNQl_kYpKUFFDSOU>
Subject: [alto] Fwd: Publication has been requested for draft-ietf-alto-performance-metrics-15
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, 21 Mar 2021 22:43:23 -0000

Dear all,

here is my write-up for the publication request on 

1. Summary

Jan Seedorf is the document shepherd for 
draft-ietf-alto-performance-metrics. Martin Duke is the responsible Area 

The ALTO base protocol (RFC7285) defines only a single cost metric, the 
generic “routing cost” metric. As new ALTO use cases are being 
envisioned (e.g. CDN, 5G, data-intensive science applications, flexible 
inter-domain routing, etc.), the demand for more concrete cost metrics 
to be conveyed via the ALTO protocol arises. This document defines a 
multitude of such concrete ALTO cost metrics, such as one-way delay, hop 
count, residue bandwidth, and several more.

This document is targeted as a Standards Track document (Proposed 
Standard). This designation is appropriate as the document contains 
normative behaviour and specifies several additions to the IANA "ALTO 
Cost Metric Registry" that should be adhered to by the communicating 
entities in order to realize the extension.

2. Review and Consensus
The document was introduced originally in 2013 and has been iterated and 
presented at IEFT meetings many times. It was adopted as WG item in 
2016, showing the general consensus in the ALTO WG for adding more 
concrete costs metrics to the ALTO protocol.

The proposed metrics have been discussed extensively at IETF meetings 
and on the mailing list. Since some of these metrics must to be 
specified in an unambiguous fashion with clear semantics, external help 
from IETF experts was obtained: in 2018 a “Tsvart early review” was 
performed by Brian Trammell. The outcome has been discussed on the 
mailing list and has been addressed in newer versions of the document. 
Also, advice from IETF experts from the IPPM WG on the semantics of the 
proposed metrics was obtained, discussed, and incorporated into the 
document. All of these changes and semantics have been presented to the 
ALTO WG multiple times.

In summary, there is clear consensus for 
draft-ietf-alto-performance-metrics in the ALTO WG, and it provides very 
useful cost metric extensions needed for many of the currently 
envisioned (future) ALTO use cases. A WGLC has successfully been passed 
with no objections, and extensive reviews were provided by various 
members of the WG and have all been addressed.

3. Intellectual Property
The shepherd confirms that each author has stated to him that to the 
best of his/her (i.e. the author’s) knowledge, all IPR related to this 
document has been disclosed.

4. Other Points
Note any downward references (see RFC 3967) and whether they appear in 
the DOWNREF Registry 
(http://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegistry), as 
these need to be announced during Last Call.

All normative references are ok (with respect to RFC 3967) as they are 
all towards documents with standards-level “Proposed Standards”, 
“Internet Standard”, or “BCP”.

  - Jan

-------- Weitergeleitete Nachricht --------
Betreff: 	Publication has been requested for 
Weitersenden-Datum: 	Sun, 21 Mar 2021 15:37:17 -0700 (PDT)
Weitersenden-Von: 	alias-bounces@ietf.org
Weitersenden-An: 	bill.wu@huawei.com, vijay.gurbani@gmail.com, 
Datum: 	Sun, 21 Mar 2021 15:37:17 -0700
Von: 	Jan Seedorf via Datatracker <noreply@ietf.org>
An: 	martin.h.duke@gmail.com
Kopie (CC): 	alto-chairs@ietf.org, alto@ietf.org, 
iesg-secretary@ietf.org, ietf@j-f-s.de, jan@j-f-s.de

Jan Seedorf has requested publication of 
draft-ietf-alto-performance-metrics-15 as Proposed Standard on behalf of 
the ALTO working group.

Please verify the document's state at