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

2021-03-21 Thread Jan Seedorf

Dear all,

here is my write-up for the publication request on 
draft-ietf-alto-performance-metrics:


1. Summary

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


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 
draft-ietf-alto-performance-metrics-15

Weitersenden-Datum: Sun, 21 Mar 2021 15:37:17 -0700 (PDT)
Weitersenden-Von:   alias-boun...@ietf.org
Weitersenden-An: 	bill...@huawei.com, vijay.gurb...@gmail.com, 
i...@j-f-s.de

Datum:  Sun, 21 Mar 2021 15:37:17 -0700
Von:Jan Seedorf via Datatracker 
An: martin.h.d...@gmail.com
Kopie (CC): 	alto-cha...@ietf.org, alto@ietf.org, 
iesg-secret...@ietf.org, i...@j-f-s.de, j...@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 
https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/



___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto


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

2021-03-21 Thread Jan Seedorf via Datatracker
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 
https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/


___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto


[alto] Shepherd write up for cdni-request-routing-alto

2021-03-21 Thread Vijay Gurbani
All: The shepherd writeup for CDNI is below.  Jan and I will be moving the
CNDI draft, path-vector, and unified-props as a cluster.  Please let me
know if you have any questions on the shepherd writeup.  Thanks.

1. Summary

Vijay K. Gurbani is the document shepherd for
draft-ietf-alto-cdni-request-routing-alto. Martin Duke is the responsible
Area Director.

RFC 8008 defines the semantics for the CDNI Footprint & Capabilities
Advertisement Interface (FCI). This document specifies a concrete protocol
for the CDNI FCI using the ALTO protocol. A new ALTO service called the
"CDNI Advertisement Service" which conveys JSON objects of media type
"application/alto-cdni+json" is defined. This service can convey CDNI FCI
Base Advertisement Objects as defined in RFC8008 to ALTO clients via the
ALTO protocol.

This document is targeted as a Standards Track document (Proposed
Standard). This designation is appropriate as the document contains
normative behaviour and message formats that should be adhered to by the
communicating entities in order to realize the extension.

2. Review and Consensus
The “ALTO Service for CDNI FCI” had been added as a new ALTO WG milestone
in 2017, following an agreement between the CDNI WG and the ALTO WG to
finalise the ALTO service for conveying (i.e. transporting) CDNI FCI
objects in the ALTO WG. draft-ietf-alto-cdni-request-routing-alto has a
long history and had been iterated and presented multiple times in the CDNI
WG prior to 2017 (see draft-seedorf-cdni-request-routing-alto).

The document is well-known in the ALTO working group and has been presented
many times. The approach is agreed upon and no objections have been raised
during the WGLC on draft-ietf-alto-cdni-request-routing-alto-09 in February
2020. All comments from the individual reviews during the WGLC have since
been addressed and the document has been polished further multiple times
since the WGLC (now in draft-ietf-alto-cdni-request-routing-alto-13).

In summary, there is clear consensus for
draft-ietf-alto-cdni-request-routing-alto in the ALTO WG, and it provides a
very useful extension needed also by the CDNI WG to convey CDNI FCI objects
defined in RFC8008. A WGLC has successfully been passed, 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”.
___
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto