From nobody Tue Feb 23 03:02:25 2021 Return-Path: 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 B22363A2A55 for ; Tue, 23 Feb 2021 03:02:18 -0800 (PST) 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 9NKu_Ji6bR0l for ; Tue, 23 Feb 2021 03:02:16 -0800 (PST) Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) (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 DBCCA3A2BFC for ; Tue, 23 Feb 2021 03:01:33 -0800 (PST) Received: by mail-ot1-x32b.google.com with SMTP id d9so974582ote.12 for ; Tue, 23 Feb 2021 03:01:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=pEmzTE+T+DCh+APxOVhnxwmcbh9iC3+xo0MCqxpGTXs=; b=kB+LKJ9mhDrZg15+VedyDHUkekzXHiGiNL3v3aMAeLjMdqWuTwsjppG+VeblaTeh3I u27GxeWbWCpZxtIA93OYUEyptzO+pzZk3Ubey5aT2WIsj9KrOTDckHENIb2dWlrB5QHa XD+8n1mSWCw7/EuaiFPSAMHtbedUGZEIZTdHWpF0kdoFdaSBaGqFVnvMOuqBlzJBjYY3 vNkB/SAIUdFra+TqAS43x8yVmH6s8aDvQ217QaUAKQFaXMgHPoXic5btmm6BI7ObxOPP 2peT+ZpT3cRw9TBKMf2cuvKvBd0DuL0DdzHAZw94vEZPTwRjzS9Yrhv+KLCUdG4q013U QC3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=pEmzTE+T+DCh+APxOVhnxwmcbh9iC3+xo0MCqxpGTXs=; b=eUXVfvBLLCn4WhvZgicq7hpXF03I+XQePyXJOgyj9kUVB+r3LN2p/gswnOiwf1CQqo SpGVTLrCCprsQ8aECuD1et1gsgp98vhPpsxR8bQgWp7Oa3d5YeE9Dlf36iZdEiAbagX2 F9QqGceX/lNzhu2if5t1k2u52u+HnQ5WFOKGN+tApfd2szyNijfQA2gnrzlKV7Um0G8M TqyA0+xRuO6jIe8AeK60zMBgI21vm9tLP2Z4Kn1uOpwbiohnDme7fPIyTeqiHs2NkA1F sKUuHNX5eyqiH9RIOiMlHUlWObPT4TD49Lt8/ZAWiErDHMqbv5b1vhXp1FQ1XORd8xem +44Q== X-Gm-Message-State: AOAM533g877bny3FHqXKU0k/6dhdRXW/29wGa3Wx5gMVIfl+PF+0Yyw2 M0F2JymytkA9sfOuTKUjHjh3znHtyaTqVsz86/o= X-Google-Smtp-Source: ABdhPJzsWySpSGyP5wECKAt/SYreHF432nsZ7hiHw6JwpytHqDd6/U1wIKXHNDXpblsjdQD5aBpg9mQKDtR9wj52VXc= X-Received: by 2002:a9d:6742:: with SMTP id w2mr1630211otm.358.1614078093193; Tue, 23 Feb 2021 03:01:33 -0800 (PST) MIME-Version: 1.0 References: <93813531-c32b-5186-a6f2-326646f4870f@j-f-s.de> In-Reply-To: From: Young Lee Date: Tue, 23 Feb 2021 20:01:18 +0900 Message-ID: To: Dhruv Dhody , alto@ietf.org Content-Type: multipart/alternative; boundary="00000000000062775705bbfed7f2" Archived-At: Subject: Re: [alto] IPR Check 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Feb 2021 11:02:24 -0000 --00000000000062775705bbfed7f2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Chairs, I am not aware of any IPR that applies to this draft. Thanks. Young From: Jan Seedorf > Date: Sat, Feb 20, 2021 at 10:30 PM > Subject: IPR Check for draft-ietf-alto-performance-metrics-15 > To: Qin Wu , Y. Richard Yang , < > young.lee@gmail.com>, , Randriamasy, Sabine (Nokia > - FR) , LUIS MIGUEL CONTRERAS > MURILLO > Cc: Vijay Gurbani > > > Dear authors of draft-ietf-alto-performance-metrics, > > I have reviewed draft-ietf-alto-performance-metrics-15 and it is good to > go, I have just one small comment: What does "NBI" stand for in figure 1? > Can you please explain what this means in the text? > > In the meantime, can you please all confirm to me and Vijay that to the > best of your (i.e. the author=E2=80=99s) knowledge, all IPR related to th= is > document has been disclosed? > > Once I have those statements I can upload the shepherd write-up to the > datatracker and move the document status to "submit to IESG". > > Thanks, > > Jan > > > -------- Weitergeleitete Nachricht -------- > Betreff: Re: [alto] I-D Action: draft-ietf-alto-performance-metrics-15.tx= t > Datum: Thu, 4 Feb 2021 18:47:37 -0500 > Von: Y. Richard Yang > An: IETF ALTO > > Hi ALTOers, > > This is the revised version of the document, addressing comments and > issues identified by Danny, Jensen, Kai, authors and some comments from o= ur > wonderful chairs. > > One "interesting" change is > 2001:db8::1:2345:6789:abcd -> 2001:db8::1234:5678 > to make sure that the ipv6 range is within the range of Table 25 of RFC > 6890. > > Cheers, > Richard > > On Thu, Feb 4, 2021 at 6:41 PM wrote: > >> >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> This draft is a work item of the Application-Layer Traffic Optimization >> WG of the IETF. >> >> Title : ALTO Performance Cost Metrics >> Authors : Qin Wu >> Y. Richard Yang >> Young Lee >> Dhruv Dhody >> Sabine Randriamasy >> Luis Miguel Contreras >> Filename : draft-ietf-alto-performance-metrics-15.txt >> Pages : 33 >> Date : 2021-02-04 >> >> Abstract: >> Cost metric is a basic concept in Application-Layer Traffic >> Optimization (ALTO), and different applications may use different >> cost metrics. Since the ALTO base protocol (RFC 7285) defines only a >> single cost metric (i.e., the generic "routingcost" metric), if an >> application wants to issue a cost map or an endpoint cost request to >> determine the resource provider that offers better delay performance, >> the base protocol does not define the cost metric to be used. >> >> This document addresses the issue by introducing network performance >> metrics, including network delay, jitter, packet loss rate, hop >> count, and bandwidth. >> >> There are multiple sources (e.g., estimation based on measurements or >> service-level agreement) to derive a performance metric. This >> document introduces an additional "cost-context" field to the ALTO >> "cost-type" field to convey the source of a performance metric. >> >> >> >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/ >> >> There are also htmlized versions available at: >> https://tools.ietf.org/html/draft-ietf-alto-performance-metrics-15 >> >> https://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metric= s-15 >> >> A diff from the previous version is available at: >> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-alto-performance-metrics-= 15 >> >> >> Please note that it may take a couple of minutes from the time of >> submission >> until the htmlized version and diff are available at tools.ietf.org. >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> >> _______________________________________________ >> alto mailing list >> alto@ietf.org >> https://www.ietf.org/mailman/listinfo/alto >> > > --00000000000062775705bbfed7f2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Chairs,

I= am not aware of any IPR that applies to this draft.

Thanks.
Young


From: Jan Seedorf <ietf@j-f= -s.de>
Date: Sat, Feb 20, 2021 at 10:30 PM
Subject: IPR= Check for draft-ietf-alto-performance-metrics-15
To: Qin Wu <bill.wu= @huawei.com>, Y. Richard Yang <yry@cs.yale.edu>, <young.= lee@gmail.com>, <dhruv.ietf@gmail.com>, Randriamasy, S= abine (Nokia - FR) <sabine.randriamasy@nokia-bell-la= bs.com>, LUIS MIGUEL CONTRERAS MURILLO <l= uismiguel.contrerasmurillo@telefonica.com>
Cc: Vijay Gurbani <= vijay.gurbani@gmail.com>


=20 =20 =20

Dear authors of draft-ietf-alto-performance-metrics,

I have reviewed draft-ietf-alto-performance-metrics-15 and it is good to go, I have just one small comment: What does "NBI" = stand for in figure 1? Can you please explain what this means in the text?

In the meantime, can you please all confirm to me and Vijay that to the best of your (i.e. the author=E2=80=99s) knowledge, all IPR re= lated to this document has been disclosed?

Once I have those statements I can upload the shepherd write-up to the datatracker and move the document status to "submit to IESG".

Thanks,

Jan



-------- Weitergeleitete Nachricht --------
Betreff: Re: [alto] I-D Action: draft-ietf-alto-performance-metrics-15.txt
Datum: Thu, 4 Feb 2021 18:47:37 -0500
Von: Y. Richard Yang <yry@cs.yale.edu>
An: IETF ALTO <alto@ietf.org>


Hi ALTOers,

This is the revised version of the document, addressing comments and issues identified by Danny, Jensen, Kai, authors and some comments from our wonderful chairs.

One "interesting" change is=C2=A0
2001:db8::1:2345:6789:abcd -> 2001:db8::1234:5678
to make sure that the ipv6 range is within the range of Table 25 of RFC 6890.

Cheers,
Richard

On Thu, Feb 4, 2021 at 6:41 PM <internet-drafts@ietf.org> wrote:

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Application-Layer Traffic Optimization WG of the IETF.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0: ALTO Performance Cost Metrics
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0: Qin Wu
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 Y. Richard Yang
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 Young Lee
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 Dhruv Dhody
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 Sabine Randriamasy
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 Luis Miguel Contreras
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0= : draft-ietf-alto-performance-metrics-15.txt
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0: 33
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 : 2021-02-04

Abstract:
=C2=A0 =C2=A0Cost metric is a basic concept in Application-Laye= r Traffic
=C2=A0 =C2=A0Optimization (ALTO), and different applications ma= y use different
=C2=A0 =C2=A0cost metrics.=C2=A0 Since the ALTO base protocol (= RFC 7285) defines only a
=C2=A0 =C2=A0single cost metric (i.e., the generic "routin= gcost" metric), if an
=C2=A0 =C2=A0application wants to issue a cost map or an endpoi= nt cost request to
=C2=A0 =C2=A0determine the resource provider that offers better= delay performance,
=C2=A0 =C2=A0the base protocol does not define the cost metric = to be used.

=C2=A0 =C2=A0This document addresses the issue by introducing n= etwork performance
=C2=A0 =C2=A0metrics, including network delay, jitter, packet l= oss rate, hop
=C2=A0 =C2=A0count, and bandwidth.

=C2=A0 =C2=A0There are multiple sources (e.g., estimation based= on measurements or
=C2=A0 =C2=A0service-level agreement) to derive a performance m= etric.=C2=A0 This
=C2=A0 =C2=A0document introduces an additional "cost-conte= xt" field to the ALTO
=C2=A0 =C2=A0"cost-type" field to convey the source o= f a performance metric.



The IETF datatracker status page for this draft is:
https://= datatracker.ietf.org/doc/draft-ietf-alto-performance-metrics/

There are also htmlized versions available at:
https://too= ls.ietf.org/html/draft-ietf-alto-performance-metrics-15
h= ttps://datatracker.ietf.org/doc/html/draft-ietf-alto-performance-metrics-15=

A diff from the previous version is available at:
htt= ps://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-alto-performance-metrics-15=


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at too= ls.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listin= fo/alto

--00000000000062775705bbfed7f2--