
From vkg@bell-labs.com  Wed May  2 12:04:49 2012
Return-Path: <vkg@bell-labs.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 F2BFD11E808E for <alto@ietfa.amsl.com>; Wed,  2 May 2012 12:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.862
X-Spam-Level: 
X-Spam-Status: No, score=-107.862 tagged_above=-999 required=5 tests=[AWL=-1.263, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d+7Ot0NRXLU7 for <alto@ietfa.amsl.com>; Wed,  2 May 2012 12:04:48 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 5D11011E8074 for <alto@ietf.org>; Wed,  2 May 2012 12:04:48 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id q42J4jBC022141 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 2 May 2012 14:04:45 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q42J4iRN017220 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 2 May 2012 14:04:45 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q42J4iYU003570; Wed, 2 May 2012 14:04:44 -0500 (CDT)
Message-ID: <4FA18682.9040808@bell-labs.com>
Date: Wed, 02 May 2012 14:09:54 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: alto <alto@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Cc: Ted Hardie <ted.ietf@gmail.com>
Subject: [alto] WGLC review of draft-ietf-alto-protocol-11
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 02 May 2012 19:04:49 -0000

Folks: Enrico and I had requested Ted to perform a joint review of
the ALTO protocol that will serve as a WGLC review as well as an
APPSDIR review.

The detailed review Ted posted is available at
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg05406.html
(Thanks, Ted).

We will request the authors to post further followups and comments on
the review to the ALTO mailing list as well as the APPSIDR mailing list.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From ben@niven-jenkins.co.uk  Wed May  2 12:29:44 2012
Return-Path: <ben@niven-jenkins.co.uk>
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 E724921E80B7; Wed,  2 May 2012 12:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.885
X-Spam-Level: 
X-Spam-Status: No, score=-104.885 tagged_above=-999 required=5 tests=[AWL=-2.286, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id leLKUg2Doo+T; Wed,  2 May 2012 12:29:44 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id 17E4A21E80B6; Wed,  2 May 2012 12:29:44 -0700 (PDT)
Received: from cpc4-cmbg17-2-0-cust814.5-4.cable.virginmedia.com ([86.14.227.47] helo=[192.168.0.3]) by mail10.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1SPfF8-0007Js-Vh; Wed, 02 May 2012 20:29:43 +0100
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <30166A91-3C02-48F7-8C3B-179DA770138C@niven-jenkins.co.uk>
Date: Wed, 2 May 2012 20:29:42 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4DC76AEC-2DCE-4DE4-B92C-C37F160DA7FF@niven-jenkins.co.uk>
References: <CA+9kkMB4nUayYO3q8ydj477jh9NM8oZyXAQ5k-NsRN=KHjb3cA@mail.gmail.com> <2DE7DDDA-6621-4E56-BD3D-1173833E672B@niven-jenkins.co.uk> <CA+9kkMApj1dPNn+0Uiz9iRPBhk3Px9kj-nP+Z+UGsjxoqY82eg@mail.gmail.com> <98BA299A-18E0-412C-A005-754F336E1620@niven-jenkins.co.uk> <CADOmCZXkF=Qc46x7+00KmB+y2q4Rm6xku2Q40YBQtsp4QeuqQQ@mail.gmail.com> <30166A91-3C02-48F7-8C3B-179DA770138C@niven-jenkins.co.uk>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
X-Mailer: Apple Mail (2.1084)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: Richard Alimi <ralimi@google.com>, draft-ietf-alto-protocol.all@tools.ietf.org, alto <alto@ietf.org>, apps-discuss@ietf.org
Subject: Re: [alto] [apps-discuss] Review of draft-ietf-alto-protocol-11.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 02 May 2012 19:29:45 -0000

cc'ing ALTO as Vijay suggested. Ben

On 2 May 2012, at 20:24, Ben Niven-Jenkins wrote:

> Rich, Ted,
>=20
> On 2 May 2012, at 18:49, Richard Alimi wrote:
>=20
>> On Wed, May 2, 2012 at 10:39 AM, Ben Niven-Jenkins
>> <ben@niven-jenkins.co.uk> wrote:
>>>=20
>>> On 2 May 2012, at 17:28, Ted Hardie wrote:
>>>>=20
>>>> It is not the cacheability of the results of post request that I =
was
>>>> referring to, but
>>>> the cacheability of the results of a 303.
>>>=20
>>> Ah, I see. Yes I see your issue with the text now.
>>>=20
>>> I believe there is an implicit assumption on the part of the authors =
that in this model (receive a POST and return a 303) that the ALTO =
server could be doing some level of "ALTO-application level caching" to =
avoid repeating expensive queries by determining that a given POST would =
execute the same query as a previous POST and therefore rather than run =
the query again, just return a 303 to a resource on the ALTO server that =
contains the results of the previous (identical) query.
>>>=20
>>=20
>> The word 'caching' was meant to apply to the response the ALTO Client
>> that actually contained the data it was looking for (that is, the
>> following GET).  An ALTO Server could also internally cache the
>> results to avoid repeated computation, but that was meant to be
>> implicit since this text was referring to the protocol messaging.
>>=20
>> I understand Ted's point about the ambiguity in the text 'employ
>> caching for the response to a POST request'.  We can clean that up to
>> indicate that the caching is for the ALTO-level response (as returned
>> by the following GET) and not the response to the POST itself.
>>=20
>>> But as I'm not an author I'll crawl back under my rock now.
>>=20
>> No - come back! :)
>=20
> As you asked so nicely, I wonder if the following (slightly wordy) =
change would address Ted's comment:
>=20
> OLD:
>   Note that it is possible for an ALTO Server to employ caching for =
the
>   response to a POST request.  This can be accomplished by returning =
an
>   HTTP 303 status code ("See Other") indicating to the ALTO Client =
that
>   the resulting Cost Map is available via a GET request to an =
alternate
>   URL (which may be cached).
> NEW:
> Note that it is possible for an ALTO Server to leverage caching HTTP =
intermediaries for responses to both GET and POST requests by including =
explicit freshness information (see Section 2.3.1 of [HTTPBIS Part6]).
>=20
> Caching of POST requests is not widely implemented by HTTP =
intermediaries, however an alternative approach is for an ALTO Server, =
in response to POST requests, to return an HTTP 303 status code ("See =
Other") indicating to the ALTO Client that the resulting Cost Map is =
available via a GET request to an alternate URL. HTTP intermediaries =
that do not support caching of POST requests could then cache the =
response to the GET request from the ALTO Client following the alternate =
URL in the 303 response (if the response to the subsequent GET request =
contains explicit freshness information).
> END
>=20
> Ted went on to say:
>> Since cachability
>> is a major reason cited for the re-use of HTTP, some additional text
>> on the use cache control directives ("public" and "Max-age" seem
>> particularly important in this context) might also be useful.
>=20
> I wonder whether a reference to Section 3.2 of HTTPBIS Part6 would =
suffice?
>=20
> Ben
>=20
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss


From richard.alimi@gmail.com  Wed May  2 22:23:05 2012
Return-Path: <richard.alimi@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 76CA821F84CD; Wed,  2 May 2012 22:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.377
X-Spam-Level: 
X-Spam-Status: No, score=-2.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n8V9H3imZNNt; Wed,  2 May 2012 22:23:04 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7CCB721F84C4; Wed,  2 May 2012 22:23:04 -0700 (PDT)
Received: by ggmi1 with SMTP id i1so187592ggm.31 for <multiple recipients>; Wed, 02 May 2012 22:23:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=2bZ5O9dWMzE76JSWHbFTJK69UlfwOO2GLKpJnthNWW8=; b=BFAOYPW/Zb+ojCCOisI6sCqMgHtwmozRj8gDGJ9YRZuVlLT3feKPKrQhaulIu4RfN4 mOFeBrOCpvvadvd+ciDYE0gSQ64s0eoyfm3rXJh8mceeufOu9ZB4+fA0iYsCUs4i3o3Q sV1JU+TbXlopsOwBLJdyYHv2+hNCYEfD/Wt0wocwaxrpkAeugfJkAyxAKYypuFmfaOs6 EgYAR5iiXXJnDMHDCAhB4zSTURpU5eVQ25efdidNZVfw3GQxMYKsWSIsGJ0Mo2O4BEOy 1+vdugCvF8u/2GVH6fPG81zsHpHYl2dG05PW1xtanFFgzJccChvt4VFmsmCcDRtL22iv lgJw==
Received: by 10.50.45.197 with SMTP id p5mr461296igm.20.1336022583866; Wed, 02 May 2012 22:23:03 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.231.206.146 with HTTP; Wed, 2 May 2012 22:22:43 -0700 (PDT)
In-Reply-To: <4DC76AEC-2DCE-4DE4-B92C-C37F160DA7FF@niven-jenkins.co.uk>
References: <CA+9kkMB4nUayYO3q8ydj477jh9NM8oZyXAQ5k-NsRN=KHjb3cA@mail.gmail.com> <2DE7DDDA-6621-4E56-BD3D-1173833E672B@niven-jenkins.co.uk> <CA+9kkMApj1dPNn+0Uiz9iRPBhk3Px9kj-nP+Z+UGsjxoqY82eg@mail.gmail.com> <98BA299A-18E0-412C-A005-754F336E1620@niven-jenkins.co.uk> <CADOmCZXkF=Qc46x7+00KmB+y2q4Rm6xku2Q40YBQtsp4QeuqQQ@mail.gmail.com> <30166A91-3C02-48F7-8C3B-179DA770138C@niven-jenkins.co.uk> <4DC76AEC-2DCE-4DE4-B92C-C37F160DA7FF@niven-jenkins.co.uk>
From: Richard Alimi <rich@velvetsea.net>
Date: Wed, 2 May 2012 22:22:43 -0700
X-Google-Sender-Auth: 15k_gtreUUrW-7CkbEFf6vGG6Ck
Message-ID: <CA+cvDaYUt+T2mpk5ijSvR3onyoeYPbjUnyZhXhUC_3J45QJQmw@mail.gmail.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Richard Alimi <ralimi@google.com>, draft-ietf-alto-protocol.all@tools.ietf.org, alto <alto@ietf.org>, apps-discuss@ietf.org
Subject: Re: [alto] [apps-discuss] Review of draft-ietf-alto-protocol-11.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 03 May 2012 05:23:05 -0000

On Wed, May 2, 2012 at 12:29 PM, Ben Niven-Jenkins
<ben@niven-jenkins.co.uk> wrote:
> cc'ing ALTO as Vijay suggested. Ben
>
> On 2 May 2012, at 20:24, Ben Niven-Jenkins wrote:
>
>> Rich, Ted,
>>
>> On 2 May 2012, at 18:49, Richard Alimi wrote:
>>
>>> On Wed, May 2, 2012 at 10:39 AM, Ben Niven-Jenkins
>>> <ben@niven-jenkins.co.uk> wrote:
>>>>
>>>> On 2 May 2012, at 17:28, Ted Hardie wrote:
>>>>>
>>>>> It is not the cacheability of the results of post request that I was
>>>>> referring to, but
>>>>> the cacheability of the results of a 303.
>>>>
>>>> Ah, I see. Yes I see your issue with the text now.
>>>>
>>>> I believe there is an implicit assumption on the part of the authors t=
hat in this model (receive a POST and return a 303) that the ALTO server co=
uld be doing some level of "ALTO-application level caching" to avoid repeat=
ing expensive queries by determining that a given POST would execute the sa=
me query as a previous POST and therefore rather than run the query again, =
just return a 303 to a resource on the ALTO server that contains the result=
s of the previous (identical) query.
>>>>
>>>
>>> The word 'caching' was meant to apply to the response the ALTO Client
>>> that actually contained the data it was looking for (that is, the
>>> following GET). =A0An ALTO Server could also internally cache the
>>> results to avoid repeated computation, but that was meant to be
>>> implicit since this text was referring to the protocol messaging.
>>>
>>> I understand Ted's point about the ambiguity in the text 'employ
>>> caching for the response to a POST request'. =A0We can clean that up to
>>> indicate that the caching is for the ALTO-level response (as returned
>>> by the following GET) and not the response to the POST itself.
>>>
>>>> But as I'm not an author I'll crawl back under my rock now.
>>>
>>> No - come back! :)
>>
>> As you asked so nicely, I wonder if the following (slightly wordy) chang=
e would address Ted's comment:
>>
>> OLD:
>> =A0 Note that it is possible for an ALTO Server to employ caching for th=
e
>> =A0 response to a POST request. =A0This can be accomplished by returning=
 an
>> =A0 HTTP 303 status code ("See Other") indicating to the ALTO Client tha=
t
>> =A0 the resulting Cost Map is available via a GET request to an alternat=
e
>> =A0 URL (which may be cached).
>> NEW:
>> Note that it is possible for an ALTO Server to leverage caching HTTP int=
ermediaries for responses to both GET and POST requests by including explic=
it freshness information (see Section 2.3.1 of [HTTPBIS Part6]).
>>
>> Caching of POST requests is not widely implemented by HTTP intermediarie=
s, however an alternative approach is for an ALTO Server, in response to PO=
ST requests, to return an HTTP 303 status code ("See Other") indicating to =
the ALTO Client that the resulting Cost Map is available via a GET request =
to an alternate URL. HTTP intermediaries that do not support caching of POS=
T requests could then cache the response to the GET request from the ALTO C=
lient following the alternate URL in the 303 response (if the response to t=
he subsequent GET request contains explicit freshness information).
>> END

This seems reasonable to me, except would it be appropriate to have
this kind of document dependency?  Would it be more appropriate to
just reference RFC2616?

>>
>> Ted went on to say:
>>> Since cachability
>>> is a major reason cited for the re-use of HTTP, some additional text
>>> on the use cache control directives ("public" and "Max-age" seem
>>> particularly important in this context) might also be useful.
>>
>> I wonder whether a reference to Section 3.2 of HTTPBIS Part6 would suffi=
ce?

Once upon a time, we used to have more detail about how to use HTTP
(caching in particular) in the ALTO Protocol draft itself. The
recommendation at that point was to strip out the large majority of it
and rely on the reference to the HTTP specs being sufficient.

That said, any pointers to help out implementers are fine with me as
long as we don't to back to where we were before :)  A concise hint or
direct reference pointing to the cache control directives seems
reasonable to me unless there are objections.

Thanks for the feedback,
Rich

>>
>> Ben
>>
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto

From ben@niven-jenkins.co.uk  Wed May  2 23:59:33 2012
Return-Path: <ben@niven-jenkins.co.uk>
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 B141221F8601; Wed,  2 May 2012 23:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2JnybRZW3fik; Wed,  2 May 2012 23:59:32 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id 6BF6621F85F8; Wed,  2 May 2012 23:59:32 -0700 (PDT)
Received: from cpc4-cmbg17-2-0-cust814.5-4.cable.virginmedia.com ([86.14.227.47] helo=[192.168.0.3]) by mail4.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1SPq02-0003n0-OA; Thu, 03 May 2012 07:58:51 +0100
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <CA+cvDaYUt+T2mpk5ijSvR3onyoeYPbjUnyZhXhUC_3J45QJQmw@mail.gmail.com>
Date: Thu, 3 May 2012 07:59:28 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A05467E6-0C38-40E3-B0C0-2207F05A882C@niven-jenkins.co.uk>
References: <CA+9kkMB4nUayYO3q8ydj477jh9NM8oZyXAQ5k-NsRN=KHjb3cA@mail.gmail.com> <2DE7DDDA-6621-4E56-BD3D-1173833E672B@niven-jenkins.co.uk> <CA+9kkMApj1dPNn+0Uiz9iRPBhk3Px9kj-nP+Z+UGsjxoqY82eg@mail.gmail.com> <98BA299A-18E0-412C-A005-754F336E1620@niven-jenkins.co.uk> <CADOmCZXkF=Qc46x7+00KmB+y2q4Rm6xku2Q40YBQtsp4QeuqQQ@mail.gmail.com> <30166A91-3C02-48F7-8C3B-179DA770138C@niven-jenkins.co.uk> <4DC76AEC-2DCE-4DE4-B92C-C37F160DA7FF@niven-jenkins.co.uk> <CA+cvDaYUt+T2mpk5ijSvR3onyoeYPbjUnyZhXhUC_3J45QJQmw@mail.gmail.com>
To: Richard Alimi <rich@velvetsea.net>
X-Mailer: Apple Mail (2.1084)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: Richard Alimi <ralimi@google.com>, draft-ietf-alto-protocol.all@tools.ietf.org, alto <alto@ietf.org>, apps-discuss@ietf.org
Subject: Re: [alto] [apps-discuss] Review of draft-ietf-alto-protocol-11.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 03 May 2012 06:59:33 -0000

Rich,

On 3 May 2012, at 06:22, Richard Alimi wrote:

> On Wed, May 2, 2012 at 12:29 PM, Ben Niven-Jenkins
> <ben@niven-jenkins.co.uk> wrote:
>>=20
>>> As you asked so nicely, I wonder if the following (slightly wordy) =
change would address Ted's comment:
>>>=20
>>> OLD:
>>>   Note that it is possible for an ALTO Server to employ caching for =
the
>>>   response to a POST request.  This can be accomplished by returning =
an
>>>   HTTP 303 status code ("See Other") indicating to the ALTO Client =
that
>>>   the resulting Cost Map is available via a GET request to an =
alternate
>>>   URL (which may be cached).
>>> NEW:
>>> Note that it is possible for an ALTO Server to leverage caching HTTP =
intermediaries for responses to both GET and POST requests by including =
explicit freshness information (see Section 2.3.1 of [HTTPBIS Part6]).
>>>=20
>>> Caching of POST requests is not widely implemented by HTTP =
intermediaries, however an alternative approach is for an ALTO Server, =
in response to POST requests, to return an HTTP 303 status code ("See =
Other") indicating to the ALTO Client that the resulting Cost Map is =
available via a GET request to an alternate URL. HTTP intermediaries =
that do not support caching of POST requests could then cache the =
response to the GET request from the ALTO Client following the alternate =
URL in the 303 response (if the response to the subsequent GET request =
contains explicit freshness information).
>>> END
>=20
> This seems reasonable to me, except would it be appropriate to have
> this kind of document dependency?  Would it be more appropriate to
> just reference RFC2616?

Up to you. HTTPBIS is in the process of putting the HTTPBIS specs =
through WG LC so there is light at the end of the tunnel for them =
popping out as RFCs. I referred to the HTTPBIS document because it's =
easier to find an appropriate reference but similar material is in 2616.

>>> Ted went on to say:
>>>> Since cachability
>>>> is a major reason cited for the re-use of HTTP, some additional =
text
>>>> on the use cache control directives ("public" and "Max-age" seem
>>>> particularly important in this context) might also be useful.
>>>=20
>>> I wonder whether a reference to Section 3.2 of HTTPBIS Part6 would =
suffice?
>=20
> Once upon a time, we used to have more detail about how to use HTTP
> (caching in particular) in the ALTO Protocol draft itself. The
> recommendation at that point was to strip out the large majority of it
> and rely on the reference to the HTTP specs being sufficient.

I seem to remember being one of the people saying to strip it out and =
just provide a reference :-)

Ben

>=20
> That said, any pointers to help out implementers are fine with me as
> long as we don't to back to where we were before :)  A concise hint or
> direct reference pointing to the cache control directives seems
> reasonable to me unless there are objections.
>=20
> Thanks for the feedback,
> Rich
>=20
>>>=20
>>> Ben
>>>=20
>>> _______________________________________________
>>> apps-discuss mailing list
>>> apps-discuss@ietf.org
>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>=20
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto


From vkg@bell-labs.com  Thu May  3 06:33:35 2012
Return-Path: <vkg@bell-labs.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 5722B21F85A7; Thu,  3 May 2012 06:33:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.742
X-Spam-Level: 
X-Spam-Status: No, score=-107.742 tagged_above=-999 required=5 tests=[AWL=-1.143, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xP9AVZ40-ymG; Thu,  3 May 2012 06:33:34 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 981AA21F848F; Thu,  3 May 2012 06:33:34 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id q43DXTZA028702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 3 May 2012 08:33:29 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q43DXRF3019614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 May 2012 08:33:28 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.238.235]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q43DXQHC019257; Thu, 3 May 2012 08:33:27 -0500 (CDT)
Message-ID: <4FA28A5D.4050904@bell-labs.com>
Date: Thu, 03 May 2012 08:38:37 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120329 Thunderbird/11.0.1
MIME-Version: 1.0
To: Richard Alimi <rich@velvetsea.net>
References: <CA+9kkMB4nUayYO3q8ydj477jh9NM8oZyXAQ5k-NsRN=KHjb3cA@mail.gmail.com> <2DE7DDDA-6621-4E56-BD3D-1173833E672B@niven-jenkins.co.uk> <CA+9kkMApj1dPNn+0Uiz9iRPBhk3Px9kj-nP+Z+UGsjxoqY82eg@mail.gmail.com> <98BA299A-18E0-412C-A005-754F336E1620@niven-jenkins.co.uk> <CADOmCZXkF=Qc46x7+00KmB+y2q4Rm6xku2Q40YBQtsp4QeuqQQ@mail.gmail.com> <30166A91-3C02-48F7-8C3B-179DA770138C@niven-jenkins.co.uk> <4DC76AEC-2DCE-4DE4-B92C-C37F160DA7FF@niven-jenkins.co.uk> <CA+cvDaYUt+T2mpk5ijSvR3onyoeYPbjUnyZhXhUC_3J45QJQmw@mail.gmail.com> <A05467E6-0C38-40E3-B0C0-2207F05A882C@niven-jenkins.co.uk>
In-Reply-To: <A05467E6-0C38-40E3-B0C0-2207F05A882C@niven-jenkins.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: draft-ietf-alto-protocol.all@tools.ietf.org, alto <alto@ietf.org>, apps-discuss@ietf.org, Richard Alimi <ralimi@google.com>
Subject: Re: [alto] [apps-discuss] Review of draft-ietf-alto-protocol-11.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 03 May 2012 13:33:35 -0000

On 05/03/2012 01:59 AM, Ben Niven-Jenkins wrote:
>> This seems reasonable to me, except would it be appropriate to
>> have this kind of document dependency?  Would it be more
>> appropriate to just reference RFC2616?
>
> Up to you. HTTPBIS is in the process of putting the HTTPBIS specs
> through WG LC so there is light at the end of the tunnel for them
> popping out as RFCs. I referred to the HTTPBIS document because it's
> easier to find an appropriate reference but similar material is in
> 2616.

If the reference to HTTPBIS is informative, then we are not gated
by HTTPBIS reaching the terminal state of RFC assignment.

So the question to Rich A. would be whether he thinks that the
reference we put in fits better as Informative or Normative.
If the former, then we can move ahead without any delays.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From ietfdbh@comcast.net  Thu May  3 09:27:28 2012
Return-Path: <ietfdbh@comcast.net>
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 68EB321F85EA for <alto@ietfa.amsl.com>; Thu,  3 May 2012 09:27:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hj6rYyL0aoOM for <alto@ietfa.amsl.com>; Thu,  3 May 2012 09:27:27 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by ietfa.amsl.com (Postfix) with ESMTP id 8498821F85D6 for <alto@ietf.org>; Thu,  3 May 2012 09:27:27 -0700 (PDT)
Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by qmta05.westchester.pa.mail.comcast.net with comcast id 5USF1j0060xGWP855UTMsq; Thu, 03 May 2012 16:27:21 +0000
Received: from [192.168.1.120] ([68.98.94.120]) by omta12.westchester.pa.mail.comcast.net with comcast id 5USU1j00W2bpJkL3YUSc7z; Thu, 03 May 2012 16:27:22 +0000
User-Agent: Microsoft-MacOutlook/14.2.0.120402
Date: Thu, 03 May 2012 09:26:28 -0700
From: David Harrington <ietfdbh@comcast.net>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>, Richard Alimi <rich@velvetsea.net>
Message-ID: <CBC7FF71.21AD8%ietfdbh@comcast.net>
Thread-Topic: [alto] [apps-discuss] Review of draft-ietf-alto-protocol-11.txt
In-Reply-To: <A05467E6-0C38-40E3-B0C0-2207F05A882C@niven-jenkins.co.uk>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: Richard Alimi <ralimi@google.com>, draft-ietf-alto-protocol.all@tools.ietf.org, alto <alto@ietf.org>, apps-discuss@ietf.org
Subject: Re: [alto] [apps-discuss] Review of draft-ietf-alto-protocol-11.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 03 May 2012 16:27:28 -0000

I would also recommend providing a reference rather than duplicating
specification, so there is no possibility of conflict between this and the
normative spec.
--
David Harrington
Internet Engineering Task Force (IETF)
Ietfdbh@comcast.net
+1-603-828-1401





On 5/2/12 11:59 PM, "Ben Niven-Jenkins" <ben@niven-jenkins.co.uk> wrote:

>Rich,
>
>On 3 May 2012, at 06:22, Richard Alimi wrote:
>
>> On Wed, May 2, 2012 at 12:29 PM, Ben Niven-Jenkins
>> <ben@niven-jenkins.co.uk> wrote:
>>> 
>>>> As you asked so nicely, I wonder if the following (slightly wordy)
>>>>change would address Ted's comment:
>>>> 
>>>> OLD:
>>>>   Note that it is possible for an ALTO Server to employ caching for
>>>>the
>>>>   response to a POST request.  This can be accomplished by returning
>>>>an
>>>>   HTTP 303 status code ("See Other") indicating to the ALTO Client
>>>>that
>>>>   the resulting Cost Map is available via a GET request to an
>>>>alternate
>>>>   URL (which may be cached).
>>>> NEW:
>>>> Note that it is possible for an ALTO Server to leverage caching HTTP
>>>>intermediaries for responses to both GET and POST requests by
>>>>including explicit freshness information (see Section 2.3.1 of
>>>>[HTTPBIS Part6]).
>>>> 
>>>> Caching of POST requests is not widely implemented by HTTP
>>>>intermediaries, however an alternative approach is for an ALTO Server,
>>>>in response to POST requests, to return an HTTP 303 status code ("See
>>>>Other") indicating to the ALTO Client that the resulting Cost Map is
>>>>available via a GET request to an alternate URL. HTTP intermediaries
>>>>that do not support caching of POST requests could then cache the
>>>>response to the GET request from the ALTO Client following the
>>>>alternate URL in the 303 response (if the response to the subsequent
>>>>GET request contains explicit freshness information).
>>>> END
>> 
>> This seems reasonable to me, except would it be appropriate to have
>> this kind of document dependency?  Would it be more appropriate to
>> just reference RFC2616?
>
>Up to you. HTTPBIS is in the process of putting the HTTPBIS specs through
>WG LC so there is light at the end of the tunnel for them popping out as
>RFCs. I referred to the HTTPBIS document because it's easier to find an
>appropriate reference but similar material is in 2616.
>
>>>> Ted went on to say:
>>>>> Since cachability
>>>>> is a major reason cited for the re-use of HTTP, some additional text
>>>>> on the use cache control directives ("public" and "Max-age" seem
>>>>> particularly important in this context) might also be useful.
>>>> 
>>>> I wonder whether a reference to Section 3.2 of HTTPBIS Part6 would
>>>>suffice?
>> 
>> Once upon a time, we used to have more detail about how to use HTTP
>> (caching in particular) in the ALTO Protocol draft itself. The
>> recommendation at that point was to strip out the large majority of it
>> and rely on the reference to the HTTP specs being sufficient.
>
>I seem to remember being one of the people saying to strip it out and
>just provide a reference :-)
>
>Ben
>
>> 
>> That said, any pointers to help out implementers are fine with me as
>> long as we don't to back to where we were before :)  A concise hint or
>> direct reference pointing to the cache control directives seems
>> reasonable to me unless there are objections.
>> 
>> Thanks for the feedback,
>> Rich
>> 
>>>> 
>>>> Ben
>>>> 
>>>> _______________________________________________
>>>> apps-discuss mailing list
>>>> apps-discuss@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>> 
>>> _______________________________________________
>>> alto mailing list
>>> alto@ietf.org
>>> https://www.ietf.org/mailman/listinfo/alto
>
>_______________________________________________
>alto mailing list
>alto@ietf.org
>https://www.ietf.org/mailman/listinfo/alto



From ralimi@google.com  Fri May  4 17:35:03 2012
Return-Path: <ralimi@google.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 2526821E8024 for <alto@ietfa.amsl.com>; Fri,  4 May 2012 17:35:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RN60uFiVZoj0 for <alto@ietfa.amsl.com>; Fri,  4 May 2012 17:34:58 -0700 (PDT)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8240421E8018 for <alto@ietf.org>; Fri,  4 May 2012 17:34:58 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so2745929lbb.31 for <alto@ietf.org>; Fri, 04 May 2012 17:34:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-system-of-record; bh=ZHPLbmFiU2qKb0eI9DK87D6IJu1Zc+Uo+Q6mhhg3JRE=; b=VfDgiSY/2nsJZ1fUE9R5YR8+rFNDRdZ9veUe6r5ksugCT73PQyHlLREjziTII2f6pZ ka7cPgisF5ytN9N/QQRF/o/q5mvNdHUOeYFaLoTBnZetB9shCoWeQClJl5EqTL1VymX+ ir3v/Cb3D/ekyZGqw7RzGjxPHgvMntgtQOJc4PqQ3EvT5D3NJFzAXpsn0hfKwJLYO5UM NMwE83eYES/MqSEqcyP8mwxJOw9LzPYIHJkaEJS93WI8j074K07CBGMnH/HOX13EXkT1 RryojU3zT/paE6VnmmaMX3eO8I4goQkz1ue0VD3r0X+JCz4AdAmFD9Td1zo4x45tkaBh 5Pcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-system-of-record :x-gm-message-state; bh=ZHPLbmFiU2qKb0eI9DK87D6IJu1Zc+Uo+Q6mhhg3JRE=; b=DcxsMrkg2JS1bceA2ZmYL3XUKk5ZA1dMJTJmrPwYeu01uFLOgD3bn8/Ni+it/424wz YHiw5SPW4fi9CqBC0wsvGetbHlFpJLG2YlUQ2b2YhbbuZ3zloeShqkyWY7HegbE+kD67 wBytTbmpzdc2IO2562g72Abzk7/m9WIUnlY0HG67M96PLi2846roi+V7GWCIdizUfYb8 jlz4BYDRw8kmwe2Kp29l9nwMjC26QyZe4RwYQLWpn1B0Y0IQfDYMGJhdw8wn2p1YCql5 +z0/yYLfnH2g7Oc9ut4nYWZBlt7glEFPrP7+On/lSTnnAYsnzuhKlBSrantmCodd/Irx 1XzQ==
Received: by 10.152.112.161 with SMTP id ir1mr7575467lab.13.1336178097335; Fri, 04 May 2012 17:34:57 -0700 (PDT)
Received: by 10.152.112.161 with SMTP id ir1mr7575448lab.13.1336178097191; Fri, 04 May 2012 17:34:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.134.97 with HTTP; Fri, 4 May 2012 17:34:26 -0700 (PDT)
In-Reply-To: <4FA28A5D.4050904@bell-labs.com>
References: <CA+9kkMB4nUayYO3q8ydj477jh9NM8oZyXAQ5k-NsRN=KHjb3cA@mail.gmail.com> <2DE7DDDA-6621-4E56-BD3D-1173833E672B@niven-jenkins.co.uk> <CA+9kkMApj1dPNn+0Uiz9iRPBhk3Px9kj-nP+Z+UGsjxoqY82eg@mail.gmail.com> <98BA299A-18E0-412C-A005-754F336E1620@niven-jenkins.co.uk> <CADOmCZXkF=Qc46x7+00KmB+y2q4Rm6xku2Q40YBQtsp4QeuqQQ@mail.gmail.com> <30166A91-3C02-48F7-8C3B-179DA770138C@niven-jenkins.co.uk> <4DC76AEC-2DCE-4DE4-B92C-C37F160DA7FF@niven-jenkins.co.uk> <CA+cvDaYUt+T2mpk5ijSvR3onyoeYPbjUnyZhXhUC_3J45QJQmw@mail.gmail.com> <A05467E6-0C38-40E3-B0C0-2207F05A882C@niven-jenkins.co.uk> <4FA28A5D.4050904@bell-labs.com>
From: Richard Alimi <ralimi@google.com>
Date: Fri, 4 May 2012 17:34:26 -0700
Message-ID: <CADOmCZV8V0LJK5h=NdB3GvhcB8qT01aR-oSe7H+MOxROeK8Syw@mail.gmail.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQmqe96k3neEGbuWGjGd4/v3vN178jdu6Q1AZwTfSLC18N7X/OkDXYnACCdKZpD/lSbhyPvLWvyOeqvY0bSfM09OZ2GtE4ua32RXuxBUEm6YVxSQ5nsY1M5KVzQDcVCzKCYliU6p
X-Mailman-Approved-At: Sat, 05 May 2012 03:20:38 -0700
Cc: draft-ietf-alto-protocol.all@tools.ietf.org, alto <alto@ietf.org>, apps-discuss@ietf.org
Subject: Re: [alto] [apps-discuss] Review of draft-ietf-alto-protocol-11.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sat, 05 May 2012 00:35:03 -0000

On Thu, May 3, 2012 at 6:38 AM, Vijay K. Gurbani <vkg@bell-labs.com> wrote:
> On 05/03/2012 01:59 AM, Ben Niven-Jenkins wrote:
>>>
>>> This seems reasonable to me, except would it be appropriate to
>>> have this kind of document dependency? =A0Would it be more
>>> appropriate to just reference RFC2616?
>>
>>
>> Up to you. HTTPBIS is in the process of putting the HTTPBIS specs
>> through WG LC so there is light at the end of the tunnel for them
>> popping out as RFCs. I referred to the HTTPBIS document because it's
>> easier to find an appropriate reference but similar material is in
>> 2616.
>
>
> If the reference to HTTPBIS is informative, then we are not gated
> by HTTPBIS reaching the terminal state of RFC assignment.
>
> So the question to Rich A. would be whether he thinks that the
> reference we put in fits better as Informative or Normative.
> If the former, then we can move ahead without any delays.

Based on my understanding, this seems like a normative reference.  If
someone thinks otherwise, please say so and I'll be happy to add a
reference to HTTPbis instead :)

Rich

>
> Thanks,
>
>
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web: =A0 http://ect.bell-labs.com/who/vkg/

From Martin.Stiemerling@neclab.eu  Fri May 11 00:30:57 2012
Return-Path: <Martin.Stiemerling@neclab.eu>
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 BE62921F8609 for <alto@ietfa.amsl.com>; Fri, 11 May 2012 00:30:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Level: 
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bKLqqyJXVPXJ for <alto@ietfa.amsl.com>; Fri, 11 May 2012 00:30:57 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 2778521F85D7 for <alto@ietf.org>; Fri, 11 May 2012 00:30:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id D2D19101010 for <alto@ietf.org>; Fri, 11 May 2012 09:26:27 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id busED4TJLqWW for <alto@ietf.org>; Fri, 11 May 2012 09:26:27 +0200 (CEST)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id B6871101000 for <alto@ietf.org>; Fri, 11 May 2012 09:26:22 +0200 (CEST)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 11 May 2012 09:30:51 +0200
Message-ID: <4FACC02A.5040000@neclab.eu>
Date: Fri, 11 May 2012 09:30:50 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: <alto@ietf.org>
References: <4F8BE443.9050903@telecomitalia.it>
In-Reply-To: <4F8BE443.9050903@telecomitalia.it>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 11 May 2012 07:30:57 -0000

Hi there,

An important note on the ALTO protocol as part of the WGLC:

The ALTO requirements have been discussed in the 2012-05-10 IESG 
telechat and one point raised which is actually of importance for the 
ALTO protocol is this:

There is/was a DISCUSS on the ALTO requirements about operations and 
management (OAM) of the ALTO protocol.
RFC 5706 (http://tools.ietf.org/html/rfc5706) gives an overview of 
points to be checked for new protocols.

However, we have not considered RFC 5706 (at least to my knowledge) in 
the ALTO protocol that discusses operations and management of the ALTO 
protocol.

The outcome of the IESG discussion is that the ALTO protocol must cover 
the aspect of OAM and discuss what is potentially needed and what is 
potentially not needed.

For instance:
- the support of logging at the server for failure detection is a 
potentially a good idea, though it might become touchy in the p2p use case.
- discussion of what clients are supposed to do when a server fails for 
various reasons. This is probably already covered in the current ALTO 
protocol draft.

Regards,

   Martin

-- 
IETF Transport Area Director

martin.stiemerling@neclab.eu

NEC Laboratories Europe - Network Research Division NEC Europe Limited
Registered Office: NEC House, 1 Victoria Road, London W3 6BL
Registered in England 283

From bclaise@cisco.com  Thu May 10 17:15:36 2012
Return-Path: <bclaise@cisco.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 3D5C421F859E for <alto@ietfa.amsl.com>; Thu, 10 May 2012 17:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.298
X-Spam-Level: 
X-Spam-Status: No, score=-7.298 tagged_above=-999 required=5 tests=[AWL=2.700,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LGsGRfsvswAj for <alto@ietfa.amsl.com>; Thu, 10 May 2012 17:15:34 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 9E60F21F856A for <alto@ietf.org>; Thu, 10 May 2012 17:15:34 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q4AHbnS0025658; Thu, 10 May 2012 19:37:49 +0200 (CEST)
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q4AHbmiF006456; Thu, 10 May 2012 19:37:48 +0200 (CEST)
Message-ID: <4FABFCEC.5070701@cisco.com>
Date: Thu, 10 May 2012 19:37:48 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: alto@ietf.org
Content-Type: multipart/alternative; boundary="------------050705090805090607000605"
X-Mailman-Approved-At: Fri, 11 May 2012 08:09:00 -0700
Subject: [alto] IPFIX Information Element in the ALTO protocol
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 11 May 2012 00:15:36 -0000

This is a multi-part message in MIME format.
--------------050705090805090607000605
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

I've been reviewing draft-ietf-alto-reqs-14 and the following requirement got me thinking:

  REQ.  ARv14-5: An ALTO client protocol MUST be extensible to enable
    support of other host group descriptor types in future.  An ALTO
    client protocol specification MUST define an appropriate procedure
    for adding new host group descriptor types, e.g., by establishing an
    IANA registry.

Why don't you reuse an existing registry, in which you will have all the
Information Elements already defined instead of defining a new one?
WhatI have in mind:the IPFIX I.E. IANA registry  <http://www.iana.org/assignments/ipfix/ipfix.xml>.
The piece of information I see in draft-ietf-alto-reqs-14 are IP address, prefix, BGP AS: they're in IANA.
And many other IEs are already present, for future ALTO extensions, if required.

This would not only save one registry (ALTO Endpoint Property in draft-ietf-alto-protocol-10), but offers a bigger advantage.
Let me explain.... When you will control your applications with ALTO, you will anyway want to apply a flow measurement to monitor your changes, and to serve as a feedback loop for more optimizations.
And the chances are high that you will using a NetFlow/IPFIX based mechanism. Both NetFlow and IPFIX usethe IPFIX I.E. IANA registry  <http://www.iana.org/assignments/ipfix/ipfix.xml>.

Therefore, it would make sense to have consistent data models between ALTO and IPFIX, and avoid a data model proxy if we want to compare the data.
Proposal: reuse the ElementIDs found inthe IPFIX I.E. IANA registry  <http://www.iana.org/assignments/ipfix/ipfix.xml>  somewhere in your protocol.

Disclaimer: I have not read the protocol details

Regards, Benoit.


--------------050705090805090607000605
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <pre>Dear all,

I've been reviewing draft-ietf-alto-reqs-14 and the following requirement got me thinking:

&nbsp;REQ.  ARv14-5: An ALTO client protocol MUST be extensible to enable
   support of other host group descriptor types in future.  An ALTO
   client protocol specification MUST define an appropriate procedure
   for adding new host group descriptor types, e.g., by establishing an
   IANA registry.

Why don't you reuse an existing registry, in which you will have all the
Information Elements already defined instead of defining a new one? 
WhatI have in mind: <a href="http://www.iana.org/assignments/ipfix/ipfix.xml">the IPFIX I.E. IANA registry</a>.
The piece of information I see in draft-ietf-alto-reqs-14 are IP address, prefix, BGP AS: they're in IANA.
And many other IEs are already present, for future ALTO extensions, if required.

This would not only save one registry (ALTO Endpoint Property in draft-ietf-alto-protocol-10), but offers a bigger advantage.
Let me explain.... When you will control your applications with ALTO, you will anyway want to apply a flow measurement to monitor your changes, and to serve as a feedback loop for more optimizations.
And the chances are high that you will using a NetFlow/IPFIX based mechanism. Both NetFlow and IPFIX use <a href="http://www.iana.org/assignments/ipfix/ipfix.xml">the IPFIX I.E. IANA registry</a>.

Therefore, it would make sense to have consistent data models between ALTO and IPFIX, and avoid a data model proxy if we want to compare the data.
Proposal: reuse the ElementIDs found in <a href="http://www.iana.org/assignments/ipfix/ipfix.xml">the IPFIX I.E. IANA registry</a> somewhere in your protocol.

Disclaimer: I have not read the protocol details

Regards, Benoit. 
</pre>
  </body>
</html>

--------------050705090805090607000605--

From ietfdbh@comcast.net  Fri May 11 10:37:46 2012
Return-Path: <ietfdbh@comcast.net>
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 D697121F849A for <alto@ietfa.amsl.com>; Fri, 11 May 2012 10:37:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xBA8Cl4G++Bl for <alto@ietfa.amsl.com>; Fri, 11 May 2012 10:37:46 -0700 (PDT)
Received: from qmta11.emeryville.ca.mail.comcast.net (qmta11.emeryville.ca.mail.comcast.net [76.96.27.211]) by ietfa.amsl.com (Postfix) with ESMTP id 333A221F8498 for <alto@ietf.org>; Fri, 11 May 2012 10:37:46 -0700 (PDT)
Received: from omta04.emeryville.ca.mail.comcast.net ([76.96.30.35]) by qmta11.emeryville.ca.mail.comcast.net with comcast id 8hYa1j0040lTkoCABhdmXq; Fri, 11 May 2012 17:37:46 +0000
Received: from [192.168.0.64] ([174.17.154.21]) by omta04.emeryville.ca.mail.comcast.net with comcast id 8hd51j0170Txrq68QhdDff; Fri, 11 May 2012 17:37:40 +0000
User-Agent: Microsoft-MacOutlook/14.2.1.120420
Date: Fri, 11 May 2012 10:37:04 -0700
From: David Harrington <ietfdbh@comcast.net>
To: Martin Stiemerling <martin.stiemerling@neclab.eu>, <alto@ietf.org>
Message-ID: <CBD293F5.21F07%ietfdbh@comcast.net>
Thread-Topic: [alto] WGLC: draft-ietf-alto-protocol-11
In-Reply-To: <4FACC02A.5040000@neclab.eu>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 11 May 2012 17:37:46 -0000

Hi,

As the author of rfc5706, and a long-time participant in the OPS area, let
me make some comments and provide some advice.

First, 
OAM and "Operations and Management" are not the same thing.
There is an RFC that discusses OAM terminology, and I recommend reading it
to understand the distinction (which still is NOT unambiguous).

Generally, 1) OAM happens inline as part of the protocol, 2) operations
includes consideration of the environment in which the protocol will
operate, and 3) management tends to be a combination of layer 7 protocols
that provide monitoring/management capabilities combined with
protocol-layer-specific information, such as MIB objects or ipfix
information elements or syslog structured data, etc. IETF management
protocols typically keep a clear distinction between the protocols used to
carry management information and the data models used to model the managed
functionality. 

Second, 
as the WG starts to consider how to address O&M requirements and/or OAM
requirements, I recommend starting with an understanding of the difference
between information models and data models, as described in RFC3444 (IIRC).

OPSAWG is doing a lot of work at making sure the information used by one
protocol can be correlated and/or translated between data models for use
with other management protocols.

I recommend developing a management-protocol-independent information
model, plus at least one management-protocol-specific data model (which
helps serve as a proof that the information model is viable).


Third,
The IETF currently has four main standards in the "management protocol
toolkit": SNMP (monitoring and tweaking), IPFIX (flow monitoring), Netconf
(configuration), and Syslog (logging). These are widely supported by
operators, and standard data models should be available so operators can
use these IETF management protocols to manage IETF protocols when possible.

Fourth,
RFC5706 discusses things to consider when developing a management
information model (and subsequent data models).
For example, for ALTO, an operator might want to be able to monitor what
sources are being used to gather physical network information, what
transform algorithms are being applied to the source data to produce ALTO
application-level information, and to monitor who is getting that
processed information from the ALTO server.
You might want to consider whether protocol errors are being detected
between the server and the data sources, or between the server and
specific consumers. This might be important to understand whether certain
sources or consumers are putting an unnecessary strain on the server, so a
server might choose to stop communicating with that error-generating
connection (and whether that decision should be standardized). That
infomation also might help detect why certain consumers might choose
non-optimal optimizations.

RFC5706 also discusses operational requirements. If BGP will be used to
gather source data, then BGP must be supported in the environment, and
that has operational considerations. Will all ALTO servers operate in BGP
environments? If an operator decides BP is not important to the physical
network they run, or choose not tp provide BGP data for security reasosn,
how will the ALTO environment be affected, and will this affect
interoperability across ALTO servers?

And so on ...

--
David Harrington
Internet Engineering Task Force (IETF)
Ietfdbh@comcast.net
+1-603-828-1401





On 5/11/12 12:30 AM, "Martin Stiemerling" <martin.stiemerling@neclab.eu>
wrote:

>Hi there,
>
>An important note on the ALTO protocol as part of the WGLC:
>
>The ALTO requirements have been discussed in the 2012-05-10 IESG
>telechat and one point raised which is actually of importance for the
>ALTO protocol is this:
>
>There is/was a DISCUSS on the ALTO requirements about operations and
>management (OAM) of the ALTO protocol.
>RFC 5706 (http://tools.ietf.org/html/rfc5706) gives an overview of
>points to be checked for new protocols.
>
>However, we have not considered RFC 5706 (at least to my knowledge) in
>the ALTO protocol that discusses operations and management of the ALTO
>protocol.
>
>The outcome of the IESG discussion is that the ALTO protocol must cover
>the aspect of OAM and discuss what is potentially needed and what is
>potentially not needed.
>
>For instance:
>- the support of logging at the server for failure detection is a
>potentially a good idea, though it might become touchy in the p2p use
>case.
>- discussion of what clients are supposed to do when a server fails for
>various reasons. This is probably already covered in the current ALTO
>protocol draft.
>
>Regards,
>
>   Martin
>
>-- 
>IETF Transport Area Director
>
>martin.stiemerling@neclab.eu
>
>NEC Laboratories Europe - Network Research Division NEC Europe Limited
>Registered Office: NEC House, 1 Victoria Road, London W3 6BL
>Registered in England 283
>_______________________________________________
>alto mailing list
>alto@ietf.org
>https://www.ietf.org/mailman/listinfo/alto



From sabine.randriamasy@alcatel-lucent.com  Fri May 11 11:15:41 2012
Return-Path: <sabine.randriamasy@alcatel-lucent.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 9A49621F86E2 for <alto@ietfa.amsl.com>; Fri, 11 May 2012 11:15:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.599
X-Spam-Level: 
X-Spam-Status: No, score=-9.599 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MwBZDBi7kh3r for <alto@ietfa.amsl.com>; Fri, 11 May 2012 11:15:40 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id 66E1C21F86CA for <alto@ietf.org>; Fri, 11 May 2012 11:15:40 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q4BIFcKb026335 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 11 May 2012 20:15:38 +0200
Received: from [172.27.204.75] (135.120.57.7) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 11 May 2012 20:15:38 +0200
Message-ID: <4FAD5745.2060009@alcatel-lucent.com>
Date: Fri, 11 May 2012 20:15:33 +0200
From: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Enrico Marocco <enrico.marocco@telecomitalia.it>
References: <4F8BE443.9050903@telecomitalia.it>
In-Reply-To: <4F8BE443.9050903@telecomitalia.it>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 11 May 2012 18:15:41 -0000

Hi all,

Below is my review of document "draft-ietf-alto-protocol-11.txt". At 
least Part I, until section 7.7.3.1.5 included. I will send Part II in a 
couple of hours.

Thanks,
Sabine

===============================================================================================


Document: draft-ietf-alto-protocol-11.txt
Title: ALTO Protocol
Reviewer: Sabine Randriamasy
Review Date: May 11, 2012
Part I

-----------------------------------------------------
GENERAL COMMENTS
-----------------------------------------------------

This document seems geared towards P2P applications, although the 
abstract mentions CDN and "those that have a choice in connection 
endpoints". In some places, see detailed comments, "peer" should be 
replaced by "endpoints" when referring to a content location. In Section 
8 Use Cases, some text should be added to recall this.

There was a discussion on whether to specify the MUST of the protocol. 
Is it possible to have a section listing the MUST of the protocol 
specified in this document?

-----------------------------------------------------
DETAILED COMMENTS
-----------------------------------------------------

Section 1.1 Background and Problem Statement

A couple of additional explanations would help better positioning and 
motivating ALTO. For example:

- § 1 after 1st sentence "Today, network information available to 
applications is mostly from
the view of endhosts.": I suggest to add 1 or 2 sentences on what is 
wrong with this, e.g. the fact that overlay based endpoint choice leads 
to uselessly use expensive links and lower performance due to too long 
paths.
- §1, 2nd sentence "There is no clear mechanism to convey information 
about the network (e.g., preferences) to applications": could be 
specified by saying that some sparse tools may exist but there is a need 
to have a generic and standardized mechanism accessible to all.
- §2last sentence "The mechanism should include abstractions to achieve 
concise, flexible network information expression.": is it the only 
motivation for abstraction or does abstraction also serve other purposes 
such as security/privacy for ISPs?


Section 1.3.1 Service Providers
This section is hard to understand without a hint on what kind of 
information is provided by ALTO. I suggest to add a sentence including 
abstracted network maps, asociated costs between the locations of the 
map or specific properties or access costs to these locations.

- in 1st sentence: "... the peer selection process ... " ==> "peer" 
shoud be replaced by "connection endpoints such as peers"


Section 2.1 Terminology

- in §2: the term "Endpoint" should be added
- a first section "2.1.X Endpoint" should be inserted before section 
2.1.1 Endpoint Address to better introduce Endpoint Adress and Network 
Location mentioning "Endpoint" with no prior definition.


Section 2.2 ALTO Service and Protocol Scope
- §3 "... The ALTO Information provided by the ALTO Server can be 
updated dynamically based on network conditions ...": a sentence would 
be good here to recall that ALTO does by no means replace real time 
network performance measurement services.


Section 3 Protocol Structure
- §3 3rd sentence "ALTO-Core provides the Map Service, which provides 
the core ALTO informtion to
clients". The term "ALTO-Core" should be introduced ans besides it does 
not appear again in the document.
Also replace "informtion" ==> "information".


Section 4 Network Map
- §2: "The Network Location endpoint property": i suggest "The Network 
Location Endpoint Property"


Section 7.2.1 Discovering Information Resources
- §1 "To discover available resources, an ALTO Client may request the 
Information Resource Directory": what are other means? There seem to be 
a contradiction with Section 6.2 Protocol design where item "o 
Information Resource Directory" says that "This directory is the single 
entry point to an ALTO Service."


Section 7.2.7 Parsing
- last sentence "ALTO implementations MUST ignore...": i suggest an 
insertion: "base protocol ALTO implementations MUST ignore...", or if it 
has been previously defined, the term "ALTO-core" could be used here.


Section 7.4 ALTO Errors
- §3 2nd sentence: "... information about the why a particular ...": i 
suggest to remove "the" => "... information about why a particular ..."


Section 7.4.1 Media Type
"... The media type for an Error Resource ...": does it mean "The media 
type for an ALTO Error Resource" ?


Section 7.4.2
- 1st sentence "An Error Resource has the format:": is the answer to my 
previous question is yes, then "An ALTO ALTO Error Resource has the 
format:" reads easier.


Section 7.4.3 Error Codes
- §2 last sentence: "... Table 1in the HTTP response." : blank space is 
needed after "1" ==> "... Table 1 in the HTTP response."


Section 7.6.2 Encoding
- §3 1st sentence "Any URI ... the format of an Information Resource 
Directory.": i suggest to append "request" ==> "Any URI ... the format 
of an Information Resource Directory request."
- §4 - item "capabilities": i didin't understand the sentence "or assume 
its default value", although the protocol is not expected to guide the 
ALTO Client's behavior.



Section 7.6.3 Example

In the first IRD example the last URI called 
"http://alto.example.com/endpointcost/lookup" includes the following 
capabilities:

"cost-modes" : [ "ordinal", "numerical" ],
"cost-types" : [ "routingcost", "hopcount" ]

In the second example listing URIs available in a subdomain, we have the 
same capabilities for the URI called 
"http://custom.alto.example.com/costmap/filtered"

There is a need for the ALTO Server to disambiguate this encoding. As an 
ALTO client, I don't know how to figure what Cost Mode is applied 
respectively to the Cost Type "routingcost" and "hopcount". Is it both 
modes for each cost type?

Also, as a server, how do I encode that for example "routingcost" is 
available in both "ordinal" and "numerical" modes and "hopcount" in 
"numerical" only? I guess separate URIs would be the way...


Section 7.7.1.2.4 Capabilities

- Object CostMapCapability has member "CostType cost-types<0..*>;". the 
description says: "If not present, this member MUST be interpreted as an 
empty array." On the other hand, Section 7.7.1.2 Cost Map in its §1 says 
"This resource MUST be provided for at least the ’routingcost’ Cost Type 
and ’numerical’ Cost Mode."
So would "CostType cost-types<1..*>" be more consistent?
Likewise, as the 'numerical' mode MUST be available, why not have 
CostMode cost-modes<1..*> ?
See also §7.7.3.1.3 Input Parameters, where encoding "EndpointProperty 
properties<1..*>" is used, because 'pid' MUST be available.


Section 7.7.2.2.3 Input Parameters
- item "constraints" use term "numerical cost". Onthe other hand, 
Section 7.7.2.4.4 Capabilities in its item "cost-constraints" says (last 
sentence) "... constraints may not have the intended effect for cost 
maps with the ’ordinal’ Cost Mode... ".
Although it intuitively make more sens to have constraints on numerical 
values, one may imagine that for some reasons an application clien may 
look for alternative paths that have a poorer rank but not worse that a 
given value and accordingly encode a constraint on 'ordinal' costs.
Therefore, I suggest to use term "cost value" instead of "numerical cost".


Section 7.7.3.1.3 Input Parameters
- §1 2nd sentence: "... data format of input parameteres...": typo ==> 
"... data format of input parameters..."
- item "properties": "List of endpoint properties to returned... " i 
suggest "List of endpoint properties to be returned... ". I also suggest 
to add that property 'pid' MUST be provided.


Section 7.7.3.1.4 Capabilities
- object "EndpointPropertyCapability;" has a member "EndpointProperty 
prop-types<0..*>". As 'pid' MUST be provided why not encode as 
"EndpointProperty prop-types<1..*>" ?



-----------------------------------------------------
NITS
-----------------------------------------------------

Abstract
- §3: ".... be provided by the network ..." => I suggest ".... be 
provided by the network operator ..." or any applicable term


Section 1.1 Background and Problem Statement
- 2nd sentence "... about the network ..." => I suggest "... about the 
network infrastructure ..."


Section 2.1 Terminology
- the typography should be harmonized between "endpoint address" and 
"Endpoint Address".


Section 2.2 ALTO Service and Protocol Scope

- §1 last sentence: "... deployment scenario and discovery mechanism 
..." ==> I suggest to complete as follows "... ALTO deployment scenario 
and ALTO service discovery mechanism ..."
- §2 1st sentence: "... the overall system architecture ..." ==> I 
suggest "the overall ALTO system architecture"
- §4 last sentence: "... figure for completeness but outside ..." ==> I 
suggest "... figure for completeness but are outside ..."


Section 3 Protocol Structure
- §3: i suggest to replace "functionality" by "functionalities"


Section 3.1.1 Map Service
- §1: replace "endpoints" by "Endpoints"


Section 7.4 ALTO Errors
- §3 2nd sentence: "... information about the why a particular ...": i 
suggest to remove "the" => "... information about why a particular ..."



Enrico Marocco a écrit :
> The chairs would like to declare a Working Group Last Call for
> draft-ietf-alto-protocol-11, ending Friday May 11th.
>
> Please do review the latest version of the draft, and send any comments
> to the list before the expiry of WGLC so we can get this document ready
> for the IESG.
>
>   


From sabine.randriamasy@alcatel-lucent.com  Fri May 11 16:17:12 2012
Return-Path: <sabine.randriamasy@alcatel-lucent.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 72A3D21F8618 for <alto@ietfa.amsl.com>; Fri, 11 May 2012 16:17:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.666
X-Spam-Level: 
X-Spam-Status: No, score=-8.666 tagged_above=-999 required=5 tests=[AWL=-0.717, BAYES_00=-2.599, HELO_EQ_FR=0.35, MANGLED_LIST=2.3,  RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QUoCZ2POuXIJ for <alto@ietfa.amsl.com>; Fri, 11 May 2012 16:17:11 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id F2D5221F85D2 for <alto@ietf.org>; Fri, 11 May 2012 16:17:10 -0700 (PDT)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q4BNH9rg016936 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 12 May 2012 01:17:09 +0200
Received: from [135.244.192.4] (135.120.57.7) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (135.120.45.61) with Microsoft SMTP Server (TLS) id 8.3.213.0; Sat, 12 May 2012 01:17:09 +0200
Message-ID: <4FAD9DEF.3070500@alcatel-lucent.com>
Date: Sat, 12 May 2012 01:17:03 +0200
From: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Enrico Marocco <enrico.marocco@telecomitalia.it>
References: <4F8BE443.9050903@telecomitalia.it> <4FAD5745.2060009@alcatel-lucent.com>
In-Reply-To: <4FAD5745.2060009@alcatel-lucent.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11 - Part II + Part I
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 11 May 2012 23:17:12 -0000

Hi all,

Below is Part II of my review of document 
"draft-ietf-alto-protocol-11.txt", starting at section 7.7.3.1.5 
included until end of document. I have put Part II on top of my previous 
e-mail with Part I, to have both gathered in 1 e-mail.

Thanks,
Sabine

===============================================================================================


Document: draft-ietf-alto-protocol-11.txt
Title: ALTO Protocol
Reviewer: Sabine Randriamasy
Review Date: May 11, 2012
Part II - starting section 7.7.3.1.5 included until end of document

-----------------------------------------------------
GENERAL COMMENTS ON THE DOCUMENT (Review Part II and Part I)
-----------------------------------------------------

This document is clear and well structured and provides enough 
information to specify and implement basic ALTO protocol transactions. 
Clarifications however are needed for some particular cases. The 
corresponding requests  are listed  in the  "Detailed  comments" section 
of Part I and Part II of this review.

This document seems geared towards P2P applications, although the 
abstract mentions CDN and "those that have a choice in connection 
endpoints". In some places, see detailed comments, "peer" should be 
replaced by "endpoints" when referring to a content location. In Section 
8 Use Cases, some text should be added to recall this.

There was a discussion on whether to specify the MUST of the protocol. 
Is it possible to have a section listing the MUST of the protocol 
specified in this document?

-----------------------------------------------------
DETAILED COMMENTS
-----------------------------------------------------

Section 7.7.3.1.5 Response
- §3 describing InfoResourceEndpointProperty: last sentence "... 
property values encoded as JSON Strings". Encoding property values as 
JSON strings may be too restrictive. It may as well be a constant 
number, or an array. Why not a JSON Value?

- §5 "If the ALTO Server does not define a requested property for a 
particular endpoint, then it MUST omit it from the response for only 
that endpoint.": does this mean that the corresponding pair 
{"prop-type": prop-type-value} does not appear in the array of 
EndpointProperty objects associated to this endpoint?

If an ALTO server defines a property for an endpoint but no value, what 
happens? Is simply the prop-type-value omitted?

 
Section 7.7.3.1.6 Example
An example of request/response with several properties would be good here.


Section 7.7.4.1.5 Response
- § of description of member "EndpointCostMapData" sentence "An 
implementation of the
protocol in this document SHOULD assume that the cost is a JSONNumber 
... ": I suggest using "cost value" rather than "cost". Same for 
sentence "If the ALTO Server does not define a cost from ..."


Section 8 Use Cases
There should be a couple of sentences recalling that ALTO supports a 
wider range of applications, namely "those that have a choice in 
connection endpoints" as said in Abstract although the use cases focus 
on P2P.


Section 8.1 ALTO ALTO Client Embedded in P2P Tracker
- §1 1st sentence "Many P2P currently-deployed P2P systems... ": ==>  
"Many currently-deployed P2P systems... "


Section 9.4 Mapping IPs to ASNs
- §4: The mapping could also be done for Endpoints and ASN be an 
Endpoint Property.



-----------------------------------------------------
NITS & TYPOS
-----------------------------------------------------


Section 9.3
- §2 1st sentence "The protocol specified ... (i.e., the the Endpoint 
Cost Service) ... " ==> remove one of the 2 "the"


Section 10.1 application/alto-* Media Types
- item "Published specification", last part "... see Table 2for ..." : 
blank space needed ==> "... see Table 2 for ..."



Sabine Randriamasy a écrit :
> Hi all,
>
> Below is my review of document "draft-ietf-alto-protocol-11.txt". At
> least Part I, until section 7.7.3.1.5 included. I will send Part II in a
> couple of hours.
>
> Thanks,
> Sabine
>
> ===============================================================================================
>
>
> Document: draft-ietf-alto-protocol-11.txt
> Title: ALTO Protocol
> Reviewer: Sabine Randriamasy
> Review Date: May 11, 2012
> Part I
>
> -----------------------------------------------------
> GENERAL COMMENTS
> -----------------------------------------------------
>
> This document seems geared towards P2P applications, although the
> abstract mentions CDN and "those that have a choice in connection
> endpoints". In some places, see detailed comments, "peer" should be
> replaced by "endpoints" when referring to a content location. In Section
> 8 Use Cases, some text should be added to recall this.
>
> There was a discussion on whether to specify the MUST of the protocol.
> Is it possible to have a section listing the MUST of the protocol
> specified in this document?
>
> -----------------------------------------------------
> DETAILED COMMENTS
> -----------------------------------------------------
>
> Section 1.1 Background and Problem Statement
>
> A couple of additional explanations would help better positioning and
> motivating ALTO. For example:
>
> - § 1 after 1st sentence "Today, network information available to
> applications is mostly from
> the view of endhosts.": I suggest to add 1 or 2 sentences on what is
> wrong with this, e.g. the fact that overlay based endpoint choice leads
> to uselessly use expensive links and lower performance due to too long
> paths.
> - §1, 2nd sentence "There is no clear mechanism to convey information
> about the network (e.g., preferences) to applications": could be
> specified by saying that some sparse tools may exist but there is a need
> to have a generic and standardized mechanism accessible to all.
> - §2last sentence "The mechanism should include abstractions to achieve
> concise, flexible network information expression.": is it the only
> motivation for abstraction or does abstraction also serve other purposes
> such as security/privacy for ISPs?
>
>
> Section 1.3.1 Service Providers
> This section is hard to understand without a hint on what kind of
> information is provided by ALTO. I suggest to add a sentence including
> abstracted network maps, asociated costs between the locations of the
> map or specific properties or access costs to these locations.
>
> - in 1st sentence: "... the peer selection process ... " ==> "peer"
> shoud be replaced by "connection endpoints such as peers"
>
>
> Section 2.1 Terminology
>
> - in §2: the term "Endpoint" should be added
> - a first section "2.1.X Endpoint" should be inserted before section
> 2.1.1 Endpoint Address to better introduce Endpoint Adress and Network
> Location mentioning "Endpoint" with no prior definition.
>
>
> Section 2.2 ALTO Service and Protocol Scope
> - §3 "... The ALTO Information provided by the ALTO Server can be
> updated dynamically based on network conditions ...": a sentence would
> be good here to recall that ALTO does by no means replace real time
> network performance measurement services.
>
>
> Section 3 Protocol Structure
> - §3 3rd sentence "ALTO-Core provides the Map Service, which provides
> the core ALTO informtion to
> clients". The term "ALTO-Core" should be introduced ans besides it does
> not appear again in the document.
> Also replace "informtion" ==> "information".
>
>
> Section 4 Network Map
> - §2: "The Network Location endpoint property": i suggest "The Network
> Location Endpoint Property"
>
>
> Section 7.2.1 Discovering Information Resources
> - §1 "To discover available resources, an ALTO Client may request the
> Information Resource Directory": what are other means? There seem to be
> a contradiction with Section 6.2 Protocol design where item "o
> Information Resource Directory" says that "This directory is the single
> entry point to an ALTO Service."
>
>
> Section 7.2.7 Parsing
> - last sentence "ALTO implementations MUST ignore...": i suggest an
> insertion: "base protocol ALTO implementations MUST ignore...", or if it
> has been previously defined, the term "ALTO-core" could be used here.
>
>
> Section 7.4 ALTO Errors
> - §3 2nd sentence: "... information about the why a particular ...": i
> suggest to remove "the" => "... information about why a particular ..."
>
>
> Section 7.4.1 Media Type
> "... The media type for an Error Resource ...": does it mean "The media
> type for an ALTO Error Resource" ?
>
>
> Section 7.4.2
> - 1st sentence "An Error Resource has the format:": is the answer to my
> previous question is yes, then "An ALTO ALTO Error Resource has the
> format:" reads easier.
>
>
> Section 7.4.3 Error Codes
> - §2 last sentence: "... Table 1in the HTTP response." : blank space is
> needed after "1" ==> "... Table 1 in the HTTP response."
>
>
> Section 7.6.2 Encoding
> - §3 1st sentence "Any URI ... the format of an Information Resource
> Directory.": i suggest to append "request" ==> "Any URI ... the format
> of an Information Resource Directory request."
> - §4 - item "capabilities": i didin't understand the sentence "or assume
> its default value", although the protocol is not expected to guide the
> ALTO Client's behavior.
>
>
>
> Section 7.6.3 Example
>
> In the first IRD example the last URI called
> "http://alto.example.com/endpointcost/lookup" includes the following
> capabilities:
>
> "cost-modes" : [ "ordinal", "numerical" ],
> "cost-types" : [ "routingcost", "hopcount" ]
>
> In the second example listing URIs available in a subdomain, we have the
> same capabilities for the URI called
> "http://custom.alto.example.com/costmap/filtered"
>
> There is a need for the ALTO Server to disambiguate this encoding. As an
> ALTO client, I don't know how to figure what Cost Mode is applied
> respectively to the Cost Type "routingcost" and "hopcount". Is it both
> modes for each cost type?
>
> Also, as a server, how do I encode that for example "routingcost" is
> available in both "ordinal" and "numerical" modes and "hopcount" in
> "numerical" only? I guess separate URIs would be the way...
>
>
> Section 7.7.1.2.4 Capabilities
>
> - Object CostMapCapability has member "CostType cost-types<0..*>;". the
> description says: "If not present, this member MUST be interpreted as an
> empty array." On the other hand, Section 7.7.1.2 Cost Map in its §1 says
> "This resource MUST be provided for at least the ’routingcost’ Cost Type
> and ’numerical’ Cost Mode."
> So would "CostType cost-types<1..*>" be more consistent?
> Likewise, as the 'numerical' mode MUST be available, why not have
> CostMode cost-modes<1..*> ?
> See also §7.7.3.1.3 Input Parameters, where encoding "EndpointProperty
> properties<1..*>" is used, because 'pid' MUST be available.
>
>
> Section 7.7.2.2.3 Input Parameters
> - item "constraints" use term "numerical cost". Onthe other hand,
> Section 7.7.2.4.4 Capabilities in its item "cost-constraints" says (last
> sentence) "... constraints may not have the intended effect for cost
> maps with the ’ordinal’ Cost Mode... ".
> Although it intuitively make more sens to have constraints on numerical
> values, one may imagine that for some reasons an application clien may
> look for alternative paths that have a poorer rank but not worse that a
> given value and accordingly encode a constraint on 'ordinal' costs.
> Therefore, I suggest to use term "cost value" instead of "numerical cost".
>
>
> Section 7.7.3.1.3 Input Parameters
> - §1 2nd sentence: "... data format of input parameteres...": typo ==>
> "... data format of input parameters..."
> - item "properties": "List of endpoint properties to returned... " i
> suggest "List of endpoint properties to be returned... ". I also suggest
> to add that property 'pid' MUST be provided.
>
>
> Section 7.7.3.1.4 Capabilities
> - object "EndpointPropertyCapability;" has a member "EndpointProperty
> prop-types<0..*>". As 'pid' MUST be provided why not encode as
> "EndpointProperty prop-types<1..*>" ?
>
>
>
> -----------------------------------------------------
> NITS
> -----------------------------------------------------
>
> Abstract
> - §3: ".... be provided by the network ..." => I suggest ".... be
> provided by the network operator ..." or any applicable term
>
>
> Section 1.1 Background and Problem Statement
> - 2nd sentence "... about the network ..." => I suggest "... about the
> network infrastructure ..."
>
>
> Section 2.1 Terminology
> - the typography should be harmonized between "endpoint address" and
> "Endpoint Address".
>
>
> Section 2.2 ALTO Service and Protocol Scope
>
> - §1 last sentence: "... deployment scenario and discovery mechanism
> ..." ==> I suggest to complete as follows "... ALTO deployment scenario
> and ALTO service discovery mechanism ..."
> - §2 1st sentence: "... the overall system architecture ..." ==> I
> suggest "the overall ALTO system architecture"
> - §4 last sentence: "... figure for completeness but outside ..." ==> I
> suggest "... figure for completeness but are outside ..."
>
>
> Section 3 Protocol Structure
> - §3: i suggest to replace "functionality" by "functionalities"
>
>
> Section 3.1.1 Map Service
> - §1: replace "endpoints" by "Endpoints"
>
>
> Section 7.4 ALTO Errors
> - §3 2nd sentence: "... information about the why a particular ...": i
> suggest to remove "the" => "... information about why a particular ..."
>
>
>
> Enrico Marocco a écrit :
>   
>> The chairs would like to declare a Working Group Last Call for
>> draft-ietf-alto-protocol-11, ending Friday May 11th.
>>
>> Please do review the latest version of the draft, and send any comments
>> to the list before the expiry of WGLC so we can get this document ready
>> for the IESG.
>>
>>
>>     
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>   

-- 

---------------------------------------------------------
Sabine RANDRIAMASY 
Alcatel-Lucent Bell Labs France 
Centre de Villarceau
Route de Villejust - 91620 NOZAY - FRANCE

E-MAIL : Sabine.Randriamasy@alcatel-lucent.com
TEL: +33 (0)1 30 77 27 45 
         (On Net) 2 103 27 45
---------------------------------------------------------


From ralimi@google.com  Sat May 12 12:39:32 2012
Return-Path: <ralimi@google.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 1195221F85A8 for <alto@ietfa.amsl.com>; Sat, 12 May 2012 12:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.77
X-Spam-Level: 
X-Spam-Status: No, score=-101.77 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ANAivkk8NDt for <alto@ietfa.amsl.com>; Sat, 12 May 2012 12:39:30 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id B17B121F8559 for <alto@ietf.org>; Sat, 12 May 2012 12:39:30 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so4738965pbc.31 for <alto@ietf.org>; Sat, 12 May 2012 12:39:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-system-of-record; bh=rpEwFimKWV2KRlQwEzcxmnU9NA6F6Yj9XepKxVupQf0=; b=PmGOO4QqHJL9Ar+dFkGekFIGtR9JnPSzioU/NSC1lPovdjR+i8DHHhVC8mRgGiuOYQ GXWTSvLxZ0JQ4ev1fGOjbws0ydQBAdEkBHtBCAJ+iQQE1JoafVqUfu/xGAtmzLBZzvRS fZotB2664SDWn4SfANNz1OmmEOTT3vXv+2rD8IRbkkfcgXVyV5Fn2BL/7A1FX5v4cxI5 5GZmcQNhYy6IGqe6a6q0JoDDQ93hz64JpOb87piYK9iSZ07Egb32N/tvMioc60e/i/6K 2JlqFtN/L/x4PT5RuhNgCrhzRW1VBCkh7oeSbYWRRuOAGDqWouHh/ArAxXm8m/sinysH L6tw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-system-of-record :x-gm-message-state; bh=rpEwFimKWV2KRlQwEzcxmnU9NA6F6Yj9XepKxVupQf0=; b=SRyWbJNXBKbc4TBelMDD+FCw25gUUjggmBGL1MAdk/39T2ES0S1dULy7tjY6aVMron vdjCqPbxLosbTvd5ZVIF2WPge9n08EEn6thbLUPpjKLNvY/lgSh88P3NHfu8aIikez4O cHo5cGuIN+ebPVyhrJiJLlabGyYuCoVVE8BzI9FnTXJ9NW2/zPxPlEh6p8ZRQXfYyYev Vm+KI3wFe4arQNso1VINNL6+rvs6PWa6l6HV7pAA8LuIUk12x0CzOr42qHa98E+5f7We FCMjDQWBOyofaM0JyviOt8tsJQLKzOWotZX8WZ1qhJFKXj1FX2Z/8B/W4T1Q6RdwHppP 05gw==
Received: by 10.68.191.170 with SMTP id gz10mr2294395pbc.91.1336851570453; Sat, 12 May 2012 12:39:30 -0700 (PDT)
Received: by 10.68.191.170 with SMTP id gz10mr2294375pbc.91.1336851570291; Sat, 12 May 2012 12:39:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.66.227 with HTTP; Sat, 12 May 2012 12:39:00 -0700 (PDT)
In-Reply-To: <CA+9kkMB4nUayYO3q8ydj477jh9NM8oZyXAQ5k-NsRN=KHjb3cA@mail.gmail.com>
References: <CA+9kkMB4nUayYO3q8ydj477jh9NM8oZyXAQ5k-NsRN=KHjb3cA@mail.gmail.com>
From: Richard Alimi <ralimi@google.com>
Date: Sat, 12 May 2012 12:39:00 -0700
Message-ID: <CADOmCZV3N=DrgiCX1W++OjkBhdNo4-0YMBPARJzEM9aTybSa0Q@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQkILXHYbRjJY2ljpC3yBPzYyzF+7nZvOa62tmsi+6dIulfxyG4RVhPbCJmxlBY43A2Ti+kXZhYwGb0d5OJu2bJZzFptDe8h3O8f9juDA3Ah7AUkMAYHwNNtDhPvQhkxU9cOkGgq
Cc: draft-ietf-alto-protocol.all@tools.ietf.org, alto <alto@ietf.org>, apps-discuss@ietf.org
Subject: Re: [alto] Review of draft-ietf-alto-protocol-11.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sat, 12 May 2012 19:39:32 -0000

Thanks for the review!

On Thu, Apr 26, 2012 at 2:40 PM, Ted Hardie <ted.ietf@gmail.com> wrote:
> Please resolve these comments along with any other Last Call
> comments you may receive. =A0Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>
> Document: draft-ietf-alto-protocol-11.txt
> Title: ALTO Protocol
> Reviewer: Ted Hardie
> Review Date: April 26, 2012
>
> Summary: Despite the length of this review, the document is
> fundamentally ready for publication on the standards track. =A0There
> are sections which need clarification or re-consideration, but
> they are not fundamental to the protocol's operation.
>
> Major:
>
> Section 5.1 needs clarification. =A0While it clearly introduces the
> types for the cost type and cost mode parameters, it buries the type
> for the cost itself within the description of the ordinal cost mode:
>
> 5.1.2.2. Cost Mode: ordinal
>
>
> =A0 This Cost Mode is indicated by the string 'ordinal'. =A0This mode
> =A0 indicates that the costs values to a set of Destination Network
> =A0 Locations from a particular Source Network Location are a ranking,
> =A0 with lower values indicating a higher preference. =A0The values are
> =A0 non-negative integers.
>
> This makes it unclear whether Costs of the numerical Cost Type are
> similarly restricted to non-negative integers. Based on other
> descriptions of ordinal comparison (e.g. q values in content
> negotiation), I also presume that the clients are not expected to
> infer anything about the weights based on the integers chosen for the
> ordinal type. That is: 3 PIDS with costs of 2, 4, 6 should be treated
> the same if the assigned values are 3, 17, 18, because the order is
> the same. =A0Additional text to highlight this (or provide the
> appropriate treatment) would be useful. =A0The section would also
> benefit from an example of a numerical operation other than
> normalization.

Ack - this can certainly be clarified.  Your understanding for ordinal
costs is correct.  Numerical costs can be any non-negative
floating-point number (representable in JSON, of course).

> In Section 7.2, the document describes the request/response traffic as
> based on "standard HTTP"; the security considerations sections appears
> to recommend TLS for integrity protection in 11.3 (this property is
> not mentioned in 7.2.5, which lists TLS as MAY for authentication and
> encryption). =A0This should be reconciled; if 11.3 is not recommending
> TLS or any object-based security, more detail is probably needed on
> the consequences of an attacker controlling this data.

Agree. Integrity protection and authentication are probably the
crucial ones, with encryption valuable in some deployment scenarios.
We can make these consistent.

Detail on what happens when an attacker controls the data would be
good.  I thought we had that text in one of the documents, but the
reference escapes me at the moment.  We'll at least add an explicit
pointer to where this is discussed in more detail.

>
> Minor:
>
> General comment: there is a great deal of material in this document
> that is either tutorial in nature or which defends a particular set of
> design choices (e.g. section 6.1). =A0While this material is not
> inherently bad, it is interleaved into the specification in ways that
> make it difficult to extract the concrete protocol specification. =A0If
> there were sections that the WG felt could be moved to an appendix
> summarizing the benefits of the ALTO approach and its choices, the
> spec might get significantly tighter and easier to read.

That sounds reasonable.  I'll hang on for others in the WG to respond
if there are other thoughts for which text should be moved and where.

At the very least, moving 6.1 earlier on in the document sounds reasonable.

On the flip side, another possibility would be to add a forward
pointer from the introduction to the core spec (for those who only
care about the spec pieces).

>
> In Section 4.1, the concept of a PID as an identifier is introduced,
> but without a pointer to the definition of the identifier type. =A0There
> is a forward reference to section 5, but this describes cost maps, not
> the PID identifier itself. =A0Reading (or grepping) forward provides a
> pointer to PIDName, but without a succinct relationship defined. =A0I
> suggest adapting the description in 7.7.1.1.5 for this purpose:
>
> "A PID is a US-ASCII string of type PIDName (see section 7.5.1) and
> its associated set of endpoint addresses."
>
> I believe this could be inserted between the first two sentences of
> the first paragraph in section 4.1

Sounds good to me.

>
> In Section 4.2.1, the document says:
>
> =A0 =A0A RECOMMENDED way to satisfy this property is to define a PID that
> =A0 contains the 0.0.0.0/0 prefix for IPv4 or ::/0 (for IPv6).
>
> This assumes that the cost map provided includes all IP addresses.
> While this may be true for some use cases, there are other use cases
> where it may not be true, and the text here should probably be
> modified to handle those cases. =A0Something like
>
> "A RECOMMENDED way to satisfy this property is to define a PID with
> the shortest enclosing prefix of the addresses provided in the map.
> For a map with full IPv4 reachability, this would mean including the
> 0.0.0.0/ prefix in a PID; for full IPv6 reachability, this would be
> the ::/0 prefix"
>
> might suit the case.

Sounds good.

>
> In section 7.2.2, the document says:
>
> =A0 "Note that it is possible for an ALTO Server to employ caching for th=
e
> =A0 response to a POST request. =A0This can be accomplished by returning =
an
> =A0 HTTP 303 status code ("See Other") indicating to the ALTO Client that
> =A0 the resulting Cost Map is available via a GET request to an alternate
> =A0 URL (which may be cached)."
>
> The phrase "employ caching" is ambiguous here, as the results of the
> initial POST are not cacheable even in the case of a 303; only
> the results of the later GET request are cachable. =A0Since cachability
> is a major reason cited for the re-use of HTTP, some additional text
> on the use cache control directives ("public" and "Max-age" seem
> particularly important in this context) might also be useful.

(discussed on a different thread where we seemed to reach a conclusion)

>
> In 7.4.2, the document describes the error resource, and notes this:
>
> =A0reason =A0A (free-form) human-readable explanation of the particular
> =A0 =A0 =A0error
>
> If I understand JASONString correctly, no language tag is supplied,
> so human readability will be highly variable, =A0Fixing that, rather
> than relying on a local mapping of the underlying code, is hard
> work. =A0Dropping this optional aspect of the error resource may
> be something for the WG to consider; this pushes localization
> of the error code description to the endpoint.

That seems reasonable.  The intent was to help with debugging (and not
display to a user), so I'd either be okay with removing it or keeping
it and not worrying about the language.  Is there standard guidance to
apply here?

> The endpoint property resource seems to be specified in too many
> sections for easy comprehension. =A0Section 7.7.3.1 describes it, but
> points to 7.7.3.1.4 (the related capabilities) which in turn points to
> 3.1.3, which says:
>
> =A0 This service allows ALTO Clients to look up properties for individual
> =A0 endpoints. =A0An example endpoint property is its Network Location (i=
ts
> =A0 grouping defined by the ALTO Server) or connectivity type (e.g.,
> =A0 ADSL, Cable, or FTTH).
>
> It is only in Section 10.3, with the creation of the registry, that
> it is clear that these are registered tokens, rather than free text.
> I suggest that this be clarified early, with a forward pointer to
> the actual registry.

It looks like the reference to 3.1.3 was wrong.  It should have been a
direct pointer to 10.3.  Thanks for catching that.  We can make it
clear when pointing forward to 10.3 that these are identifiers from a
registry.

> In section 9.3, the document notes that the ALTO client SHOULD use
> STUN to determine a public IP for a source address. =A0However,
> the description of the Endpoint Cost Service contains this text:
>
> =A0 =A0 =A0If the list of Source
> =A0 =A0 =A0Endpoints is empty (or not included), the ALTO Server MUST
> =A0 =A0 =A0interpret it as if it contained the Endpoint Address correspon=
ding
> =A0 =A0 =A0to the client IP address from the incoming connection
>
> It would seem a valid recommendation here would be to propose that the
> CLIENT omit the Source Endpoint where it currently recommends the use
> of STUN. =A0I infer that this is not recommended because the Endpoint
> Address service may be provided within a NAT boundary shared with the
> CLIENT, thus making the source address of the packet different from
> that which would be seen externally (resolving this would require the
> ALTO service to have general knowledge of the NAT bindings). =A0But the
> opposite case is not handled. =A0What happens when the destination
> address is within the NAT boundary of the client? =A0Won't the external
> address determined by STUN will have a similar mismatch to the true
> origin address for packets destined to the internal destination?

Yes - I see the disconnect.  I'd like to avoid solving the larger
deployment considerations under NATs (the deployment consideratoins
document should be handling that) in this document and instead focus
on the messaging details. Perhaps it would be best to change the
statement w.r.t. STUN to instead say MAY.  This document can certainly
give a concise statement of the problems you identified there.

How does that sound?

> In 9.4, it may be useful to note that there are private ASNs which
> are not unique, and that a single looking glass may therefore give
> an incomplete view of the full mapping of IP addresses to ASNs. =A0In
> general, this section seems to point to future work, and I suggest
> that it more clearly say that a standardized method for this mapping
> is left to future work.

Agree - we'll add text there to convey that.

>
>
> In section 10.4, it may be useful to advise the Expert Reviewer
> on how to handle registrations which differ only as to case;
> for example, would PRIV: or EXP: be permitted in a registration?
>
> Nits:
>
> The Abstract says:
>
> =A0 These maps provide simplified,
> =A0 yet enough information of a network for applications to effectively
> =A0 utilize.
>
> This seems to be missing a noun or to require restructuring. =A0Possibly:
>
> "These maps provide simplified information, but it is enough for
> applications to effectively use."?
>
> "Additional services are built on top the maps." =A0should be "on top of
> the maps".
>
> In the Introduction, "see below" could be shifted to a more precise
> forward reference to a specific section.
>
> In section 2.2, the document says:
>
> =A0 In particular, an ALTO Server defines network
> =A0 Endpoints (and aggregations thereof) and generic costs amongst them,
> =A0 both from the network region's own perspective.
>
> I personally found this hard to parse. =A0Some re-wording may be useful.
> (Possibly eliminating the ", both"?)

Ack.  We'll clean these up.

>
> In Figure 1, the top most enclosing box is labelled "ISP". =A0While that =
is
> certainly a common use case, there seem to be others. Given the
> preceding text, would it be more general to use the term "Network
> Region"?

Agree. "Network Region" sounds good.

>
> In section 3, the document says:
>
> "Note that functionality offered in different
> =A0 services are not totally non-overlapping (e.g., the Map Service and
> =A0 Map Filtering Service)."
>
> Would it be equivalent to say "functionality offered in different
> services may overlap"?

Agree.  Fewer double-negatives would be better :)

>
> Section 3 is titled "Protocol Structure", but the subsections are about
> specific services, and the base text doesn't really describe what
> most IETF readers will understand as a description of the structure of
> the protocol (that seems to be in Section 7). =A0A different title (maybe
> "Service framework"?) would seem to be a better fit.

Agree. I like "Service Framework"

> I believe Section 4 might read more naturally if the second paragraph
> were moved up to be first.

Agree.

> In 7.5.1, the encoding of PID Name is given in relation to a permitted
> US-ASCII code range, except for the "." separator. =A0Providing the
> related code point would be useful. =A0Several other sections use
> "alphanumeric" as a limitation without giving the code point ranges;
> in those cases, the actual code point ranges would be useful.

Ack.

> The Content-Length in some examples (e.g. in 7.6.3) are listed
> as [TODO]; this should be fixed.

Yeah - these haven't changed in a few revisions, so it would be
reasonable to resolve those TODO's now :)

> In section 9.2, the document says "one path my have a NAT64 middlebox)",
> where my should be "may".
>
> In Section 10.1, it is common for the change controller to be the IESG,
> rather than the individual editors of the draft.

Ack.

Thanks again!
Rich

From richard.alimi@gmail.com  Sat May 12 23:05:41 2012
Return-Path: <richard.alimi@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 5E12121F856F for <alto@ietfa.amsl.com>; Sat, 12 May 2012 23:05:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.044
X-Spam-Level: 
X-Spam-Status: No, score=-2.044 tagged_above=-999 required=5 tests=[AWL=0.933,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GeOu54wzbOmV for <alto@ietfa.amsl.com>; Sat, 12 May 2012 23:05:40 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id B8A3221F84B2 for <alto@ietf.org>; Sat, 12 May 2012 23:05:40 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so742905ggn.31 for <alto@ietf.org>; Sat, 12 May 2012 23:05:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=SbL4y2bSD5JMaytS7Zx1zD/PAX88V2gTyC/2h/p6b/w=; b=vMWLp1akFP1m4PpTSI0p7P+2EjCrpaVa55zL7qmWRDjviO6OWdVboNiZ1ceyPVqEjc pqp/F5fIPLJ3tiVvoWHLpwB7xvkwq7NK7gnNtb/QbjUY/RKo6FA+d1laazhEvX/QuvZc 1kuS43h0ZlnNATf5J6aUI2/gj8iS4vdsRH484Rjn4y+5IhGbhHhnHDsy4lsJSZFMnhbz llfnrn7F7H2u+DuFuDyEYu7BE80q1sHLF979sQkp6XGjutJMSVnWas/LuhRpuDh1bJeO GwQnqixpWFFNgqQKwSEKK5QL2n5uBGe6q9oDyVUTB2PtOTX3mgZOjQS9hFe+67y5QIYM F8ww==
Received: by 10.42.63.80 with SMTP id b16mr199017ici.29.1336889139940; Sat, 12 May 2012 23:05:39 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.231.209.82 with HTTP; Sat, 12 May 2012 23:05:19 -0700 (PDT)
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F23A51746@szxeml534-mbx.china.huawei.com>
References: <4F8BE443.9050903@telecomitalia.it> <E33E01DFD5BEA24B9F3F18671078951F23A51746@szxeml534-mbx.china.huawei.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Sat, 12 May 2012 23:05:19 -0700
X-Google-Sender-Auth: 27Z24tO63cPag8xSMZzhr3LTAbk
Message-ID: <CA+cvDaaPktLnyJb+tqm2KW7+qA5+bNAjToK1NjmPrA3yNFfCvg@mail.gmail.com>
To: Songhaibin <haibin.song@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 13 May 2012 06:05:41 -0000

On Mon, Apr 23, 2012 at 6:47 PM, Songhaibin <haibin.song@huawei.com> wrote:
> In general, this draft is in good shape.
>
> One randomly caught problem, in Section 5.1.2.2, the ordinal mode introdu=
ction, it says this cost mode is a ranking from a particular source to a se=
t of destinations. But in Section 5.2, the introduction of cost map structu=
re, the cost mode "ordinal" can be applied to m*n entries in the cost map. =
So I suggest to modify the previous section 5.1.2.2 to make them consistent=
.
>

Thanks for catching that. In fact, the sentence "If the Cost Mode is
'ordinal', the Path Cost of each communicating pair is relative to the
m*n entries" can probably just be removed.

Thanks,
Rich

> BR,
> -Haibin
>
>> -----Original Message-----
>> From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of =
Enrico
>> Marocco
>> Sent: Monday, April 16, 2012 5:20 PM
>> To: alto@ietf.org
>> Subject: [alto] WGLC: draft-ietf-alto-protocol-11
>>
>>
>> The chairs would like to declare a Working Group Last Call for
>> draft-ietf-alto-protocol-11, ending Friday May 11th.
>>
>> Please do review the latest version of the draft, and send any comments =
to the
>> list before the expiry of WGLC so we can get this document ready for the=
 IESG.
>>
>> --
>> Ciao,
>> Enrico
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto

From richard.alimi@gmail.com  Sun May 13 00:11:30 2012
Return-Path: <richard.alimi@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 7A96521F85C3 for <alto@ietfa.amsl.com>; Sun, 13 May 2012 00:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.127
X-Spam-Level: 
X-Spam-Status: No, score=-1.127 tagged_above=-999 required=5 tests=[AWL=-0.450, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MANGLED_LIST=2.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SsRKQaUjanoM for <alto@ietfa.amsl.com>; Sun, 13 May 2012 00:11:29 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3F6E321F85BD for <alto@ietf.org>; Sun, 13 May 2012 00:11:29 -0700 (PDT)
Received: by obbeh20 with SMTP id eh20so6864278obb.31 for <alto@ietf.org>; Sun, 13 May 2012 00:11:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=rIsL97KRj/o/pYF4oxNpHzimaUcv2e7fbXzgrwb/gLo=; b=CHtx041pgGBWp31lRux90vLyMwhPuvSHGK1Y46wX7sNIWVupM0/zoqjwS4r5QLhJTx AH8OcFepoeix2puqSoNoHxOQwusWfUzeE989S1cLuU0NLBzQ7CtU5shIemxX26ZZyxe9 oK7by/oltOINHYX7HNgQHLA/OO9L3evNM0N2pR6Tml6Zrk0XUQj2KRAYsIT1XhKY8VxQ Ij3Y2xBcWosXME+Fifu2n0Yq8a2GY+UzrVzcPtajZapE/Y0LtRi27756FJUJdJmpO2/H 1dYjt4JBoEmmlt/9etfRE4HrokhXIrl/mP1egexKQclszKRmgxRb6kfPsSnj9che1BdI AxOw==
Received: by 10.50.168.34 with SMTP id zt2mr2201873igb.10.1336893088592; Sun, 13 May 2012 00:11:28 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.231.209.82 with HTTP; Sun, 13 May 2012 00:11:08 -0700 (PDT)
In-Reply-To: <4FAD9DEF.3070500@alcatel-lucent.com>
References: <4F8BE443.9050903@telecomitalia.it> <4FAD5745.2060009@alcatel-lucent.com> <4FAD9DEF.3070500@alcatel-lucent.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Sun, 13 May 2012 00:11:08 -0700
X-Google-Sender-Auth: DbsghJsv04CxwNUL2Pq6WONnZm4
Message-ID: <CA+cvDaauTRrzSn3g_966PWyDMLvAWJxA4=g6RZLjm-W0y+_iiA@mail.gmail.com>
To: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11 - Part II + Part I
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 13 May 2012 07:11:30 -0000

Oops - I replied to the Part 1 email separately. I'll keep this one
focused on Part 2 and trim the rest from the reply to avoid confusion.

On Fri, May 11, 2012 at 4:17 PM, Sabine Randriamasy
<Sabine.Randriamasy@alcatel-lucent.com> wrote:
> -----------------------------------------------------
> DETAILED COMMENTS
> -----------------------------------------------------
>
> Section 7.7.3.1.5 Response
> - =A73 describing InfoResourceEndpointProperty: last sentence "... proper=
ty
> values encoded as JSON Strings". Encoding property values as JSON strings
> may be too restrictive. It may as well be a constant number, or an array.
> Why not a JSON Value?

I don't have a problem with making this a JSON Value for extensibility
and adopting similar text that we did for cost values (basically,
those implementing the base specification should validate that they
are strings).  If someone feels like we shouldn't do that, then please
speak up soon :)

> - =A75 "If the ALTO Server does not define a requested property for a
> particular endpoint, then it MUST omit it from the response for only that
> endpoint.": does this mean that the corresponding pair {"prop-type":
> prop-type-value} does not appear in the array of EndpointProperty objects
> associated to this endpoint?

Yes.  If it was unclear, feel free to provide alternate text to clarify it.

>
> If an ALTO server defines a property for an endpoint but no value, what
> happens? Is simply the prop-type-value omitted?

I would have considered this to be the same as not having the property
defined for that endpoint.  Would the following text make it more
clear?

"If the ALTO Server does not define a value for a requested property
for a particular endpoint, then it MUST omit it .. "

>
>
> Section 7.7.3.1.6 Example
> An example of request/response with several properties would be good here=
.
>

Makes sense - we can add that.

>
> Section 7.7.4.1.5 Response
> - =A7 of description of member "EndpointCostMapData" sentence "An
> implementation of the
> protocol in this document SHOULD assume that the cost is a JSONNumber ...=
 ":
> I suggest using "cost value" rather than "cost". Same for sentence "If th=
e
> ALTO Server does not define a cost from ..."

Sounds good to me.

>
>
> Section 8 Use Cases
> There should be a couple of sentences recalling that ALTO supports a wide=
r
> range of applications, namely "those that have a choice in connection
> endpoints" as said in Abstract although the use cases focus on P2P.

Ack.

>
> Section 8.1 ALTO ALTO Client Embedded in P2P Tracker
> - =A71 1st sentence "Many P2P currently-deployed P2P systems... ": =3D=3D=
> =A0"Many
> currently-deployed P2P systems... "
>

Ack.

>
> Section 9.4 Mapping IPs to ASNs
> - =A74: The mapping could also be done for Endpoints and ASN be an Endpoi=
nt
> Property.
>

Yes  - that is also a possibility.  We can mention this.

>
>
> -----------------------------------------------------
> NITS & TYPOS
> -----------------------------------------------------
>
>
> Section 9.3
> - =A72 1st sentence "The protocol specified ... (i.e., the the Endpoint C=
ost
> Service) ... " =3D=3D> remove one of the 2 "the"
>
>
> Section 10.1 application/alto-* Media Types
> - item "Published specification", last part "... see Table 2for ..." : bl=
ank
> space needed =3D=3D> "... see Table 2 for ..."

Ack.

Thanks for the review!
Rich

>
>
>
> Sabine Randriamasy a =E9crit :
>>
>> Hi all,
>>
>> Below is my review of document "draft-ietf-alto-protocol-11.txt". At
>> least Part I, until section 7.7.3.1.5 included. I will send Part II in a
>> couple of hours.
>>
>> Thanks,
>> Sabine
>>
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>>
>> Document: draft-ietf-alto-protocol-11.txt
>> Title: ALTO Protocol
>> Reviewer: Sabine Randriamasy
>> Review Date: May 11, 2012
>> Part I
>>
>> -----------------------------------------------------
>> GENERAL COMMENTS
>> -----------------------------------------------------
>>
>> This document seems geared towards P2P applications, although the
>> abstract mentions CDN and "those that have a choice in connection
>> endpoints". In some places, see detailed comments, "peer" should be
>> replaced by "endpoints" when referring to a content location. In Section
>> 8 Use Cases, some text should be added to recall this.
>>
>> There was a discussion on whether to specify the MUST of the protocol.
>> Is it possible to have a section listing the MUST of the protocol
>> specified in this document?
>>
>> -----------------------------------------------------
>> DETAILED COMMENTS
>> -----------------------------------------------------
>>
>> Section 1.1 Background and Problem Statement
>>
>> A couple of additional explanations would help better positioning and
>> motivating ALTO. For example:
>>
>> - =A7 1 after 1st sentence "Today, network information available to
>> applications is mostly from
>> the view of endhosts.": I suggest to add 1 or 2 sentences on what is
>> wrong with this, e.g. the fact that overlay based endpoint choice leads
>> to uselessly use expensive links and lower performance due to too long
>> paths.
>> - =A71, 2nd sentence "There is no clear mechanism to convey information
>> about the network (e.g., preferences) to applications": could be
>> specified by saying that some sparse tools may exist but there is a need
>> to have a generic and standardized mechanism accessible to all.
>> - =A72last sentence "The mechanism should include abstractions to achiev=
e
>> concise, flexible network information expression.": is it the only
>> motivation for abstraction or does abstraction also serve other purposes
>> such as security/privacy for ISPs?
>>
>>
>> Section 1.3.1 Service Providers
>> This section is hard to understand without a hint on what kind of
>> information is provided by ALTO. I suggest to add a sentence including
>> abstracted network maps, asociated costs between the locations of the
>> map or specific properties or access costs to these locations.
>>
>> - in 1st sentence: "... the peer selection process ... " =3D=3D> "peer"
>> shoud be replaced by "connection endpoints such as peers"
>>
>>
>> Section 2.1 Terminology
>>
>> - in =A72: the term "Endpoint" should be added
>> - a first section "2.1.X Endpoint" should be inserted before section
>> 2.1.1 Endpoint Address to better introduce Endpoint Adress and Network
>> Location mentioning "Endpoint" with no prior definition.
>>
>>
>> Section 2.2 ALTO Service and Protocol Scope
>> - =A73 "... The ALTO Information provided by the ALTO Server can be
>> updated dynamically based on network conditions ...": a sentence would
>> be good here to recall that ALTO does by no means replace real time
>> network performance measurement services.
>>
>>
>> Section 3 Protocol Structure
>> - =A73 3rd sentence "ALTO-Core provides the Map Service, which provides
>> the core ALTO informtion to
>> clients". The term "ALTO-Core" should be introduced ans besides it does
>> not appear again in the document.
>> Also replace "informtion" =3D=3D> "information".
>>
>>
>> Section 4 Network Map
>> - =A72: "The Network Location endpoint property": i suggest "The Network
>> Location Endpoint Property"
>>
>>
>> Section 7.2.1 Discovering Information Resources
>> - =A71 "To discover available resources, an ALTO Client may request the
>> Information Resource Directory": what are other means? There seem to be
>> a contradiction with Section 6.2 Protocol design where item "o
>> Information Resource Directory" says that "This directory is the single
>> entry point to an ALTO Service."
>>
>>
>> Section 7.2.7 Parsing
>> - last sentence "ALTO implementations MUST ignore...": i suggest an
>> insertion: "base protocol ALTO implementations MUST ignore...", or if it
>> has been previously defined, the term "ALTO-core" could be used here.
>>
>>
>> Section 7.4 ALTO Errors
>> - =A73 2nd sentence: "... information about the why a particular ...": i
>> suggest to remove "the" =3D> "... information about why a particular ...=
"
>>
>>
>> Section 7.4.1 Media Type
>> "... The media type for an Error Resource ...": does it mean "The media
>> type for an ALTO Error Resource" ?
>>
>>
>> Section 7.4.2
>> - 1st sentence "An Error Resource has the format:": is the answer to my
>> previous question is yes, then "An ALTO ALTO Error Resource has the
>> format:" reads easier.
>>
>>
>> Section 7.4.3 Error Codes
>> - =A72 last sentence: "... Table 1in the HTTP response." : blank space i=
s
>> needed after "1" =3D=3D> "... Table 1 in the HTTP response."
>>
>>
>> Section 7.6.2 Encoding
>> - =A73 1st sentence "Any URI ... the format of an Information Resource
>> Directory.": i suggest to append "request" =3D=3D> "Any URI ... the form=
at
>> of an Information Resource Directory request."
>> - =A74 - item "capabilities": i didin't understand the sentence "or assu=
me
>> its default value", although the protocol is not expected to guide the
>> ALTO Client's behavior.
>>
>>
>>
>> Section 7.6.3 Example
>>
>> In the first IRD example the last URI called
>> "http://alto.example.com/endpointcost/lookup" includes the following
>> capabilities:
>>
>> "cost-modes" : [ "ordinal", "numerical" ],
>> "cost-types" : [ "routingcost", "hopcount" ]
>>
>> In the second example listing URIs available in a subdomain, we have the
>> same capabilities for the URI called
>> "http://custom.alto.example.com/costmap/filtered"
>>
>> There is a need for the ALTO Server to disambiguate this encoding. As an
>> ALTO client, I don't know how to figure what Cost Mode is applied
>> respectively to the Cost Type "routingcost" and "hopcount". Is it both
>> modes for each cost type?
>>
>> Also, as a server, how do I encode that for example "routingcost" is
>> available in both "ordinal" and "numerical" modes and "hopcount" in
>> "numerical" only? I guess separate URIs would be the way...
>>
>>
>> Section 7.7.1.2.4 Capabilities
>>
>> - Object CostMapCapability has member "CostType cost-types<0..*>;". the
>> description says: "If not present, this member MUST be interpreted as an
>> empty array." On the other hand, Section 7.7.1.2 Cost Map in its =A71 sa=
ys
>> "This resource MUST be provided for at least the =92routingcost=92 Cost =
Type
>> and =92numerical=92 Cost Mode."
>> So would "CostType cost-types<1..*>" be more consistent?
>> Likewise, as the 'numerical' mode MUST be available, why not have
>> CostMode cost-modes<1..*> ?
>> See also =A77.7.3.1.3 Input Parameters, where encoding "EndpointProperty
>> properties<1..*>" is used, because 'pid' MUST be available.
>>
>>
>> Section 7.7.2.2.3 Input Parameters
>> - item "constraints" use term "numerical cost". Onthe other hand,
>> Section 7.7.2.4.4 Capabilities in its item "cost-constraints" says (last
>> sentence) "... constraints may not have the intended effect for cost
>> maps with the =92ordinal=92 Cost Mode... ".
>> Although it intuitively make more sens to have constraints on numerical
>> values, one may imagine that for some reasons an application clien may
>> look for alternative paths that have a poorer rank but not worse that a
>> given value and accordingly encode a constraint on 'ordinal' costs.
>> Therefore, I suggest to use term "cost value" instead of "numerical cost=
".
>>
>>
>> Section 7.7.3.1.3 Input Parameters
>> - =A71 2nd sentence: "... data format of input parameteres...": typo =3D=
=3D>
>> "... data format of input parameters..."
>> - item "properties": "List of endpoint properties to returned... " i
>> suggest "List of endpoint properties to be returned... ". I also suggest
>> to add that property 'pid' MUST be provided.
>>
>>
>> Section 7.7.3.1.4 Capabilities
>> - object "EndpointPropertyCapability;" has a member "EndpointProperty
>> prop-types<0..*>". As 'pid' MUST be provided why not encode as
>> "EndpointProperty prop-types<1..*>" ?
>>
>>
>>
>> -----------------------------------------------------
>> NITS
>> -----------------------------------------------------
>>
>> Abstract
>> - =A73: ".... be provided by the network ..." =3D> I suggest ".... be
>> provided by the network operator ..." or any applicable term
>>
>>
>> Section 1.1 Background and Problem Statement
>> - 2nd sentence "... about the network ..." =3D> I suggest "... about the
>> network infrastructure ..."
>>
>>
>> Section 2.1 Terminology
>> - the typography should be harmonized between "endpoint address" and
>> "Endpoint Address".
>>
>>
>> Section 2.2 ALTO Service and Protocol Scope
>>
>> - =A71 last sentence: "... deployment scenario and discovery mechanism
>> ..." =3D=3D> I suggest to complete as follows "... ALTO deployment scena=
rio
>> and ALTO service discovery mechanism ..."
>> - =A72 1st sentence: "... the overall system architecture ..." =3D=3D> I
>> suggest "the overall ALTO system architecture"
>> - =A74 last sentence: "... figure for completeness but outside ..." =3D=
=3D> I
>> suggest "... figure for completeness but are outside ..."
>>
>>
>> Section 3 Protocol Structure
>> - =A73: i suggest to replace "functionality" by "functionalities"
>>
>>
>> Section 3.1.1 Map Service
>> - =A71: replace "endpoints" by "Endpoints"
>>
>>
>> Section 7.4 ALTO Errors
>> - =A73 2nd sentence: "... information about the why a particular ...": i
>> suggest to remove "the" =3D> "... information about why a particular ...=
"
>>
>>
>>
>> Enrico Marocco a =E9crit :
>>
>>>
>>> The chairs would like to declare a Working Group Last Call for
>>> draft-ietf-alto-protocol-11, ending Friday May 11th.
>>>
>>> Please do review the latest version of the draft, and send any comments
>>> to the list before the expiry of WGLC so we can get this document ready
>>> for the IESG.
>>>
>>>
>>>
>>
>>
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>>
>
>
> --
>
> ---------------------------------------------------------
> Sabine RANDRIAMASY Alcatel-Lucent Bell Labs France Centre de Villarceau
> Route de Villejust - 91620 NOZAY - FRANCE
>
> E-MAIL : Sabine.Randriamasy@alcatel-lucent.com
> TEL: +33 (0)1 30 77 27 45 =A0 =A0 =A0 =A0 (On Net) 2 103 27 45
> ---------------------------------------------------------
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto

From richard.alimi@gmail.com  Sun May 13 00:13:34 2012
Return-Path: <richard.alimi@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 D2C2121F8688 for <alto@ietfa.amsl.com>; Sun, 13 May 2012 00:13:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.187
X-Spam-Level: 
X-Spam-Status: No, score=-2.187 tagged_above=-999 required=5 tests=[AWL=0.790,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rInpm9K2lsQV for <alto@ietfa.amsl.com>; Sun, 13 May 2012 00:13:33 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7A75321F866B for <alto@ietf.org>; Sun, 13 May 2012 00:13:33 -0700 (PDT)
Received: by obbeh20 with SMTP id eh20so6866746obb.31 for <alto@ietf.org>; Sun, 13 May 2012 00:13:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; bh=C2B+iI4Af3Rcp3kMk9WgXVmbeMv27Um5meEKBEOuM5A=; b=b9ACza3/09QUN369Pnn9OqfM/F85PuCSTMLG+EP1FeouDn/lC+iLGLSbYhNkxrpoFM jYsH7OhG6r6EdnWzInklanm2//omBE/UQen7Xw4W49MoQ2iFUKQAPZz5oDOQdE2OGaI/ 3ra9oAI6Z+iHX/l2Zbk8mm79f9jIC4fZGUjTaKNnl8hUP/e8i0qMBystlCutRIEHPKyL aR0ndTeUA4huY4sSwKpmp93NonMlNWhKVySGF9S24K/ZyAF3M7sYxhT8J31DZnJ9HHpx 2kRT81syfYn5npCzurP0ztzEDqI4ZStEHMcPsjW4kFTsMSIKS83pEdwkqeE6XGWQXIGN 1h5A==
Received: by 10.50.89.233 with SMTP id br9mr1937780igb.48.1336893212692; Sun, 13 May 2012 00:13:32 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.231.209.82 with HTTP; Sun, 13 May 2012 00:13:11 -0700 (PDT)
In-Reply-To: <CA+cvDab3P0-68m6+mZ+4K0FedJ7_MK6SGXhD2kQKupXuCDLgDw@mail.gmail.com>
References: <4F8BE443.9050903@telecomitalia.it> <4FAD5745.2060009@alcatel-lucent.com> <CA+cvDab3P0-68m6+mZ+4K0FedJ7_MK6SGXhD2kQKupXuCDLgDw@mail.gmail.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Sun, 13 May 2012 00:13:11 -0700
X-Google-Sender-Auth: eV9iTWAM1k-6nKi4r28kaVVijKk
Message-ID: <CA+cvDaZJ-RdJKf9mSTP0qbz3vS1mK28XQYpzpfQ69EZbMCF_5A@mail.gmail.com>
To: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>, alto@ietf.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 13 May 2012 07:13:34 -0000

adding alto WG back...

On Sat, May 12, 2012 at 11:59 PM, Richard Alimi <rich@velvetsea.net> wrote:
> On Fri, May 11, 2012 at 11:15 AM, Sabine Randriamasy
> <Sabine.Randriamasy@alcatel-lucent.com> wrote:
>>
>>
>> Hi all,
>>
>> Below is my review of document "draft-ietf-alto-protocol-11.txt". At lea=
st
>> Part I, until section 7.7.3.1.5 included. I will send Part II in a coupl=
e of
>> hours.
>>
>> Thanks,
>> Sabine
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>>
>> Document: draft-ietf-alto-protocol-11.txt
>> Title: ALTO Protocol
>> Reviewer: Sabine Randriamasy
>> Review Date: May 11, 2012
>> Part I
>>
>> -----------------------------------------------------
>> GENERAL COMMENTS
>> -----------------------------------------------------
>>
>> This document seems geared towards P2P applications, although the abstra=
ct
>> mentions CDN and "those that have a choice in connection endpoints". In =
some
>> places, see detailed comments, "peer" should be replaced by "endpoints" =
when
>> referring to a content location. In Section 8 Use Cases, some text shoul=
d be
>> added to recall this.
>
> Yes - that sounds reasonable. =A0We'll do a search for the word 'peer'
> to see if a better term can be used, and also add a reminder in the
> use cases that P2P is not the only deployment setting.
>
>> There was a discussion on whether to specify the MUST of the protocol. I=
s it
>> possible to have a section listing the MUST of the protocol specified in
>> this document?
>
> I don't recall this discussion - do you have a pointer?
>
> If I'm understanding the proposal correctly, I am concerned about how
> much duplicate information that would generate. =A0Is there an example
> RFC you could reference that does this?
>
>>
>> -----------------------------------------------------
>> DETAILED COMMENTS
>> -----------------------------------------------------
>>
>> Section 1.1 Background and Problem Statement
>>
>> A couple of additional explanations would help better positioning and
>> motivating ALTO. For example:
>>
>> - =A7 1 after 1st sentence "Today, network information available to
>> applications is mostly from
>> the view of endhosts.": I suggest to add 1 or 2 sentences on what is wro=
ng
>> with this, e.g. the fact that overlay based endpoint choice leads to
>> uselessly use expensive links and lower performance due to too long path=
s.
>
> We can add something there. A better way to phrase this might be that
> a view only from the view of the endhosts makes it
> difficult/impossible to be aware of policies or properties of the
> overall network topology.
>
>> - =A71, 2nd sentence "There is no clear mechanism to convey information =
about
>> the network (e.g., preferences) to applications": could be specified by
>> saying that some sparse tools may exist but there is a need to have a
>> generic and standardized mechanism accessible to all.
>
> Just to be sure I understand, which specific tools were you thinking
> about here? =A0BGP looking glasses or whois? =A0Or others?
>
>> - =A72last sentence "The mechanism should include abstractions to achiev=
e
>> concise, flexible network information expression.": is it the only
>> motivation for abstraction or does abstraction also serve other purposes
>> such as security/privacy for ISPs?
>
> I would tend to keep the security/privacy issue out of the
> introduction when we are motivating the protocol. =A0These are
> requirements that should (I believe, anyways) already be handled in
> the Discussion section of this document and in the requirements
> document.
>
>>
>> Section 1.3.1 Service Providers
>> This section is hard to understand without a hint on what kind of
>> information is provided by ALTO. I suggest to add a sentence including
>> abstracted network maps, asociated costs between the locations of the ma=
p or
>> specific properties or access costs to these locations.
>
> I'll see what we can do to add a small hint in here without going into de=
tail.
>
>> - in 1st sentence: "... the peer selection process ... " =3D=3D> "peer" =
shoud be
>> replaced by "connection endpoints such as peers"
>
> Ack.
>
>>
>> Section 2.1 Terminology
>>
>> - in =A72: the term "Endpoint" should be added
>> - a first section "2.1.X Endpoint" should be inserted before section 2.1=
.1
>> Endpoint Address to better introduce Endpoint Adress and Network Locatio=
n
>> mentioning "Endpoint" with no prior definition.
>
> Ack - we'll add this.
>
>> Section 2.2 ALTO Service and Protocol Scope
>> - =A73 "... The ALTO Information provided by the ALTO Server can be upda=
ted
>> dynamically based on network conditions ...": a sentence would be good h=
ere
>> to recall that ALTO does by no means replace real time network performan=
ce
>> measurement services.
>
> Do you instead mean ~real-time congestion control protocols? =A0If so,
> we can add a reminder.
>
>>
>> Section 3 Protocol Structure
>> - =A73 3rd sentence "ALTO-Core provides the Map Service, which provides =
the
>> core ALTO informtion to
>> clients". The term "ALTO-Core" should be introduced ans besides it does =
not
>> appear again in the document.
>
> Actually, I think the term can just be dropped at this point. (Let me
> know if anyone disagrees)
>
>> Also replace "informtion" =3D=3D> "information".
>
> Ack.
>
>>
>>
>> Section 4 Network Map
>> - =A72: "The Network Location endpoint property": i suggest "The Network
>> Location Endpoint Property"
>>
>>
>> Section 7.2.1 Discovering Information Resources
>> - =A71 "To discover available resources, an ALTO Client may request the
>> Information Resource Directory": what are other means? There seem to be =
a
>> contradiction with Section 6.2 Protocol design where item "o Information
>> Resource Directory" says that "This directory is the single entry point =
to
>> an ALTO Service."
>
> Does changing it from
> =A0"an ALTO Client may request ... "
> to
> =A0"an ALTO Client requests... "
> clear this up?
>
>>
>> Section 7.2.7 Parsing
>> - last sentence "ALTO implementations MUST ignore...": i suggest an
>> insertion: "base protocol ALTO implementations MUST ignore...", or if it=
 has
>> been previously defined, the term "ALTO-core" could be used here.
>
> The advice is common to any ALTO implementation, even one that is
> supporting an extension. =A0If an implementation is supporting an
> extension, then those fields are no longer "unknown".
>
> If that still isn't clear, do you have an alternate suggestion on the wor=
ding?
>
>>
>> Section 7.4 ALTO Errors
>> - =A73 2nd sentence: "... information about the why a particular ...": i
>> suggest to remove "the" =3D> "... information about why a particular ...=
"
>
> Ack - thanks.
>
>> Section 7.4.1 Media Type
>> "... The media type for an Error Resource ...": does it mean "The media =
type
>> for an ALTO Error Resource" ?
>>
>
> Yes - we'll make that more precise.
>
>>
>> Section 7.4.2
>> - 1st sentence "An Error Resource has the format:": is the answer to my
>> previous question is yes, then "An ALTO ALTO Error Resource has the form=
at:"
>> reads easier.
>>
>
> Ack - I'll just avoid the extra 'ALTO' when updating the text :)
>
>>
>> Section 7.4.3 Error Codes
>> - =A72 last sentence: "... Table 1in the HTTP response." : blank space i=
s
>> needed after "1" =3D=3D> "... Table 1 in the HTTP response."
>>
>
> Ack.
>
>>
>> Section 7.6.2 Encoding
>> - =A73 1st sentence "Any URI ... the format of an Information Resource
>> Directory.": i suggest to append "request" =3D=3D> "Any URI ... the form=
at of an
>> Information Resource Directory request."
>
> Ack.
>
>> - =A74 - item "capabilities": i didin't understand the sentence "or assu=
me its
>> default value", although the protocol is not expected to guide the ALTO
>> Client's behavior.
>
> Each capability should have a default value documented in this
> specification - the text here is only indicating that the client
> should fall back to that value. =A0Does that answer the question?
>
> Note to self: "empty array" -> "empty object" in this paragraph
>
>>
>>
>> Section 7.6.3 Example
>>
>> In the first IRD example the last URI called
>> "http://alto.example.com/endpointcost/lookup" includes the following
>> capabilities:
>>
>> "cost-modes" : [ "ordinal", "numerical" ],
>> "cost-types" : [ "routingcost", "hopcount" ]
>>
>> In the second example listing URIs available in a subdomain, we have the
>> same capabilities for the URI called
>> "http://custom.alto.example.com/costmap/filtered"
>>
>> There is a need for the ALTO Server to disambiguate this encoding. As an
>> ALTO client, I don't know how to figure what Cost Mode is applied
>> respectively to the Cost Type "routingcost" and "hopcount". Is it both m=
odes
>> for each cost type?
>>
>>
>> Also, as a server, how do I encode that for example "routingcost" is
>> available in both "ordinal" and "numerical" modes and "hopcount" in
>> "numerical" only? I guess separate URIs would be the way...
>
> Section 7.7.1.2.4. says:
> =A0 An ALTO Server MUST support all of the Cost Types listed here for
> =A0 each of the listed Cost Modes. =A0Note that an ALTO Server may provid=
e
> =A0 multiple Cost Map Information Resources, each with different
> =A0 capabilities.
>
> Does that answer both questions?
>
>> Section 7.7.1.2.4 Capabilities
>>
>> - Object CostMapCapability has member "CostType cost-types<0..*>;". the
>> description says: "If not present, this member MUST be interpreted as an
>> empty array." On the other hand, Section 7.7.1.2 Cost Map in its =A71 sa=
ys
>> "This resource MUST be provided for at least the =92routingcost=92 Cost =
Type and
>> =92numerical=92 Cost Mode."
>> So would "CostType cost-types<1..*>" be more consistent?
>> Likewise, as the 'numerical' mode MUST be available, why not have CostMo=
de
>> cost-modes<1..*> ?
>
> There are valid cases for them being empty. Specifically, this can
> happen if the server generating the Information Resource Directory is
> not authoritative as to what capabilities are supported. =A0See 7.6.3
> for an example.
>
> Each cost-map endpoint need not support the routingcost type - an ALTO
> Service must do so.
>
>> See also =A77.7.3.1.3 Input Parameters, where encoding "EndpointProperty
>> properties<1..*>" is used, because 'pid' MUST be available.
>
> Do you mean "EndpointProperty prop-types<0..*>;" instead?
>
> This has a similar reasoning to the above for cost maps.
>
>> Section 7.7.2.2.3 Input Parameters
>> - item "constraints" use term "numerical cost". Onthe other hand, Sectio=
n
>> 7.7.2.4.4 Capabilities in its item "cost-constraints" says (last sentenc=
e)
>> "... constraints may not have the intended effect for cost maps with the
>> =92ordinal=92 Cost Mode... ".
>> Although it intuitively make more sens to have constraints on numerical
>> values, one may imagine that for some reasons an application clien may l=
ook
>> for alternative paths that have a poorer rank but not worse that a given
>> value and accordingly encode a constraint on 'ordinal' costs.
>> Therefore, I suggest to use term "cost value" instead of "numerical cost=
".
>
> Agree. that should not explicitly mention numerical costs in the
> documentation for constraints. =A0Good catch.
>
>> Section 7.7.3.1.3 Input Parameters
>> - =A71 2nd sentence: "... data format of input parameteres...": typo =3D=
=3D> "...
>> data format of input parameters..."
>> - item "properties": "List of endpoint properties to returned... " i sug=
gest
>> "List of endpoint properties to be returned... ".
>
> Ack.
>
>> I also suggest to add that
>> property 'pid' MUST be provided.
>
> That is already noted in 7.7.3.1 right? =A0Note that a particular URI
> need not provide the 'pid' property - the ALTO Service as a whole
> needs to do so.
>
> This seems worth clarifying - I'll add a note to do that.
>
>>
>>
>> Section 7.7.3.1.4 Capabilities
>> - object "EndpointPropertyCapability;" has a member "EndpointProperty
>> prop-types<0..*>". As 'pid' MUST be provided why not encode as
>> "EndpointProperty prop-types<1..*>" ?
>
> Same as the response above, I believe.
>
>>
>>
>>
>> -----------------------------------------------------
>> NITS
>> -----------------------------------------------------
>>
>> Abstract
>> - =A73: ".... be provided by the network ..." =3D> I suggest ".... be pr=
ovided
>> by the network operator ..." or any applicable term
>>
>>
>> Section 1.1 Background and Problem Statement
>> - 2nd sentence "... about the network ..." =3D> I suggest "... about the
>> network infrastructure ..."
>>
>>
>> Section 2.1 Terminology
>> - the typography should be harmonized between "endpoint address" and
>> "Endpoint Address".
>>
>> Section 2.2 ALTO Service and Protocol Scope
>>
>> - =A71 last sentence: "... deployment scenario and discovery mechanism .=
.."
>> =3D=3D> I suggest to complete as follows "... ALTO deployment scenario a=
nd ALTO
>> service discovery mechanism ..."
>> - =A72 1st sentence: "... the overall system architecture ..." =3D=3D> I=
 suggest
>> "the overall ALTO system architecture"
>> - =A74 last sentence: "... figure for completeness but outside ..." =3D=
=3D> I
>> suggest "... figure for completeness but are outside ..."
>>
>>
>> Section 3 Protocol Structure
>> - =A73: i suggest to replace "functionality" by "functionalities"
>>
>>
>> Section 3.1.1 Map Service
>> - =A71: replace "endpoints" by "Endpoints"
>>
>>
>> Section 7.4 ALTO Errors
>> - =A73 2nd sentence: "... information about the why a particular ...": i
>> suggest to remove "the" =3D> "... information about why a particular ...=
"
>>
>
> Ack.
>
> Thanks!
> Rich
>
>>
>>
>> Enrico Marocco a =E9crit :
>>
>>> The chairs would like to declare a Working Group Last Call for
>>> draft-ietf-alto-protocol-11, ending Friday May 11th.
>>>
>>> Please do review the latest version of the draft, and send any comments
>>> to the list before the expiry of WGLC so we can get this document ready
>>> for the IESG.
>>>
>>>
>>
>>
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto

From richard.alimi@gmail.com  Sun May 13 00:39:23 2012
Return-Path: <richard.alimi@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 5694421F86B3 for <alto@ietfa.amsl.com>; Sun, 13 May 2012 00:39:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.319
X-Spam-Level: 
X-Spam-Status: No, score=-2.319 tagged_above=-999 required=5 tests=[AWL=0.658,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SUyGAsISP5su for <alto@ietfa.amsl.com>; Sun, 13 May 2012 00:39:22 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id A788721F856C for <alto@ietf.org>; Sun, 13 May 2012 00:39:22 -0700 (PDT)
Received: by obbeh20 with SMTP id eh20so6895912obb.31 for <alto@ietf.org>; Sun, 13 May 2012 00:39:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=EyWPRVyOTMxlfERsU+fX9/k+/3WXwORt/ECdUizwr4w=; b=WrSeBqNbVvCxPMs9YcKLXd256z/uk8novxD4kRT2MwYbdlcro93EdQC5vKciwV/sqo y1Dgz3QFOBWrsdq6JunxWqSgbCvxfuLR/8XbXF2HWL4SSS9PIkPuba113KuEPddnnrVa S4jSR+FKXny/yvGKpkxCkbGTJHXjGUHjhZds5o0gFyO0t44ZdJw4I3D8pdGV6iI4K2kL mmFmxwEs5E3dOZa/QoeszFLS9euBTzs+XM/mgDcqAx+RQY5ZqXA7V4BinCUldLQn5KTx iYXRwzv1+00K6UXK3HqtBcsvUDmCs9GRMH1ElJYK66QA+8q0Mf9CNjStQpQuXlCOz/Rk Rdwg==
Received: by 10.50.191.231 with SMTP id hb7mr1938964igc.26.1336894762286; Sun, 13 May 2012 00:39:22 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.231.209.82 with HTTP; Sun, 13 May 2012 00:38:57 -0700 (PDT)
In-Reply-To: <4FABFCEC.5070701@cisco.com>
References: <4FABFCEC.5070701@cisco.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Sun, 13 May 2012 00:38:57 -0700
X-Google-Sender-Auth: bi0KMeZ-fF9RhX04QMmqNiNAuUA
Message-ID: <CA+cvDaagjh49t5Zck1pj+yJq6UCibhHH+3FBWA8eioMDOsibsA@mail.gmail.com>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: alto@ietf.org
Subject: Re: [alto] IPFIX Information Element in the ALTO protocol
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 13 May 2012 07:39:23 -0000

On Thu, May 10, 2012 at 10:37 AM, Benoit Claise <bclaise@cisco.com> wrote:
> Dear all,
>
> I've been reviewing draft-ietf-alto-reqs-14 and the following requirement
> got me thinking:
>
> =A0REQ.  ARv14-5: An ALTO client protocol MUST be extensible to enable
>    support of other host group descriptor types in future.  An ALTO
>    client protocol specification MUST define an appropriate procedure
>    for adding new host group descriptor types, e.g., by establishing an
>    IANA registry.
>
> Why don't you reuse an existing registry, in which you will have all the
> Information Elements already defined instead of defining a new one?
> WhatI have in mind: the IPFIX I.E. IANA registry.
> The piece of information I see in draft-ietf-alto-reqs-14 are IP address,
> prefix, BGP AS: they're in IANA.
> And many other IEs are already present, for future ALTO extensions, if
> required.
>
> This would not only save one registry (ALTO Endpoint Property in
> draft-ietf-alto-protocol-10), but offers a bigger advantage.
> Let me explain.... When you will control your applications with ALTO, you
> will anyway want to apply a flow measurement to monitor your changes, and=
 to
> serve as a feedback loop for more optimizations.
> And the chances are high that you will using a NetFlow/IPFIX based
> mechanism. Both NetFlow and IPFIX use the IPFIX I.E. IANA registry.
>
> Therefore, it would make sense to have consistent data models between ALT=
O
> and IPFIX, and avoid a data model proxy if we want to compare the data.
> Proposal: reuse the ElementIDs found in the IPFIX I.E. IANA registry
> somewhere in your protocol.

The suggested use case is in place of the Endpoint Property registry?

Just to be sure I understand what would happen if we went that route,
what are the restrictions for adding new information elements?
Specifically, what kinds of elements are allowed or disallowed?

Things that have been informally discussed in the ALTO WG so far have
been things like load information and available network capacity.  Do
those fit within the ipfix model?

Thanks,
Rich

>
> Disclaimer: I have not read the protocol details
>
> Regards, Benoit.
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>

From sebi@gw01.ehlo.wurstkaes.de  Sun May 13 23:14:56 2012
Return-Path: <sebi@gw01.ehlo.wurstkaes.de>
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 A3D3F21F859E for <alto@ietfa.amsl.com>; Sun, 13 May 2012 23:14:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.057
X-Spam-Level: 
X-Spam-Status: No, score=0.057 tagged_above=-999 required=5 tests=[AWL=-2.079,  BAYES_20=-0.74, HELO_EQ_DE=0.35, MANGLED_LOAN=2.3, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tLBMQL5ahxmi for <alto@ietfa.amsl.com>; Sun, 13 May 2012 23:14:55 -0700 (PDT)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [188.246.4.151]) by ietfa.amsl.com (Postfix) with ESMTP id 47A6421F8597 for <alto@ietf.org>; Sun, 13 May 2012 23:14:53 -0700 (PDT)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1SToYV-0004FC-Cm; Mon, 14 May 2012 08:14:51 +0200
Date: Mon, 14 May 2012 08:14:51 +0200
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: draft-ietf-alto-protocol@tools.ietf.org
Message-ID: <20120514061451.GA3136@gw01.ehlo.wurstkaes.de>
References: <4F8BE443.9050903@telecomitalia.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4F8BE443.9050903@telecomitalia.it>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: [alto] alto-protocol-11 vs. alto-reqs-14
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 14 May 2012 06:14:56 -0000

Dear all,

I tried to match draft-ietf-alto-protocol-11.txt against
draft-ietf-alto-reqs-14.txt. Results see below.



A line

REQ. ARv14-X:   Full compliant : Y.Z

is to be read as:

The requirement X from draft-ietf-alto-reqs-14.txt
is fulfilled because of the mechanisms or rules specified 
in section Y.Z of draft-ietf-alto-protocol-11.txt



"There is no ..." is to be read as "I could not find ... in the document"



Thanks,
Sebastian



>    REQ.  ARv14-1: The ALTO service is provided by one or more ALTO
>    servers.  It may be queried by ALTO clients seeking guidance for
>    selecting appropriate resource providers.  ALTO clients and ALTO
>    servers MUST implement an ALTO client protocol.  An ALTO client
>    protocol MUST be able to transmit ALTO queries from an ALTO client to
>    an ALTO server, and it MUST be able to transmit the corresponding
>    ALTO replies from the ALTO server to the ALTO client.

REQ. ARv14-1:   Full compliant : 7.2

>    The detailed specification of an ALTO client protocol is out of the
>    scope of this document.  In fact, this document does not even assume
>    that there is only one single protocol specification.  However, this
>    document enumerates requirements for ALTO, to be considered when
>    specifying, assessing, or comparing protocols and implementations.
> 
> 3.1.2.  Host Group Descriptor Support
> 
>    The ALTO guidance is based on the evaluation of several resource
>    providers or groups of resource providers, considering one or more
>    rating criteria.  The resource providers or groups of resource
>    providers are characterized by means of host group descriptors.
> 
>    REQ.  ARv14-2: The ALTO client protocol MUST support the usage of
>    multiple host group descriptor types.

REQ. ARv14-2:   Full compliant : 7.5.3.1

>    REQ.  ARv14-3: ALTO clients and ALTO servers MUST clearly identify
>    the type of each host group descriptor sent in ALTO queries or
>    responses.

REQ. ARv14-3:   Full compliant : 7.5.3.2.3.

>    REQ.  ARv14-4: An ALTO client protocol MUST support the host group
>    descriptor types "IPv4 address prefix" and "IPv6 address prefix".
>    They can be used to specify the IP address of one host, or an IP
>    address range (in CIDR notation) containing all hosts in question.

REQ. ARv14-4:   Full compliant : 7.5.3.3.1., 7.5.3.3.2.

>    REQ.  ARv14-5: An ALTO client protocol MUST be extensible to enable
>    support of other host group descriptor types in future.  An ALTO
>    client protocol specification MUST define an appropriate procedure
>    for adding new host group descriptor types, e.g., by establishing an
>    IANA registry.

REQ. ARv14-5:   Partially compliant : 7.5.3.1 says: "Extension documents
    may define additional Address Types." but it does not define what
    kind of document is required (just an Internet-Draft, or
    Informational RFC, ...)

>    REQ.  ARv14-6: For host group descriptor types other than "IPv4
>    address prefix" and "IPv6 address prefix", the host group descriptor
>    type identification MUST be supplemented by a reference to a
>    facility, which can be used to translate host group descriptors of
>    that type to IPv4/IPv6 address prefixes, e.g., by means of a mapping
>    table or an algorithm.

REQ.  ARv14-6:   Partially compliant, with comment: In addition
    to IPv4/6 addresses/prefixes the document only defines one
    host group descriptor type, namely PIDs. The mapping mechanism
    from IP prefixes to PIDs ("Network Map") is described in 
    4. and 7.7.1.1.

    The document allows the definition of additional host group 
    descriptor types by means of extension documents (see ARv14-5),
    but it does not mention the mapping mechanism for them at all.

    I propose:
    1.) add a clarification in section 7.5.3.1 that the extension
    documents not only have to define new Address Types but also
    an appropriate mapping mechansim.

    2.) maybe we should spend a moment and think about whether
    the base protocol needs at least some basic infrastrucure (e.g.,
    pre-defined path names, or a standard algorithm to be execuded if a
    TypedEndpointAddr of unknown type is encountered, etc.) that
    makes defining such a mapping mechanism easier.

    3.) should section 9.4. stay in the document? It discusses 
    alternatives for mapping IP to ASN - if we can't decide that
    we want to specify exactly one of these alternatvies and add
    it to the base protocol, it is probably better to move the whole
    section to our deployment considerations document. 

>    REQ.  ARv14-7: Protocol functions for mapping other host group
>    descriptor types to IPv4/IPv6 address prefixes SHOULD be designed and
>    specified as part of an ALTO client protocol, and the corresponding
>    address mapping information SHOULD be made available by the same
>    entity that wants to use these host group descriptors within an ALTO
>    client protocol.  However, an ALTO server or an ALTO client MAY also
>    send a reference to an external mapping facility, e.g., a translation
>    table to be obtained via an alternative mechanism.

REQ.  ARv14-7:  see discussion of ARv14-6.

    Section 7.5.3.1. specifies the type 'AddressType' but no indication
    is given what to do if it is not one of the well-defined types given
    in this document. One might argue that this issue belongs to the
    "extension documents" and that therefore draft-ietf-alto-protocol-11
    is compliant to this requirement, but adding some base infrastrucure
    to the base protocol might be reasonable (see above).

>    REQ.  ARv14-8: An ALTO client protocol specification MUST define
>    mechanisms that can be used by the ALTO server to indicate that a
>    host group descriptor used by the ALTO client is of an unsupported
>    type, or that the indicated mapping mechanism could not be used.

REQ.  ARv14-8:  Compliant, with comment: E_JSON_VALUE_TYPE defined
    in 7.4.3. can be used, though it might be useful to define an
    own, less generic error message.
> 
>    REQ.  ARv14-9: An ALTO client protocol specification MUST define
>    mechanisms, which can be used by the ALTO client to indicate that a
>    host group descriptor used by the ALTO server is of an unsupported
>    type, or that the indicated mapping mechanism could not be used.

REQ.  ARv14-9:  Compliant, with comment: E_JSON_VALUE_TYPE defined
    in 7.4.3. can be used, though it might be useful to define an
    own, less generic error message.

> 3.1.3.  Rating Criteria Support
> 
>    REQ.  ARv14-10: An ALTO client protocol specification MUST define a
>    rating criterion that can be used to express and evaluate the
>    "relative operator's preference."  This is a relative measure, i.e.,
>    it is not associated with any unit of measurement.  A more-preferred
>    rating according to this criterion indicates that the application
>    should prefer the respective candidate resource provider over others
>    with less-preferred ratings (unless information from non-ALTO sources
>    suggests a different choice, such as transmission attempts suggesting
>    that the path is currently congested).  The operator of the ALTO
>    server does not have to disclose how and based on which data the
>    ratings are actually computed.  Examples could be: cost for peering
>    or transit traffic, traffic engineering inside the network, and other
>    policies.

REQ.  ARv14-10: Full compliant : 5.1.1.1

>    REQ.  ARv14-11: An ALTO client protocol MUST be extensible to enable
>    support of other rating criteria types in future.  An ALTO client
>    protocol specification MUST define an appropriate procedure for
>    adding new rating criteria types, e.g., by establishing an IANA
>    registry.

REQ.  ARv14-11:  Full compliant: 5.1.1., 10.2.

>    REQ.  ARv14-12: ALTO client protocol specifications MUST NOT define
>    rating criteria closely related to the instantaneous network
>    congestion state, i. e., rating criteria that have the primary aim to
>    serve as an alternative to established congestion control strategies,
>    such as using TCP-based transport.
> 
>       One design assumption for ALTO is that it is acceptable that the
>       host characteristics attributes, which are stored and processed in
>       the ALTO servers for giving the guidance, are updated rather
>       infrequently.  Typical update intervals may be several orders of
>       magnitude longer than the typical network-layer packet round-trip
>       time (RTT).  Therefore, ALTO cannot be a replacement for TCP-like
>       congestion control mechanisms.

REQ. ARv14-12:  Full compliant : no such attribute is defined in
    draft-ietf-alto-protocol-11

>    REQ.  ARv14-13: Applications using ALTO guidance MUST NOT rely solely
>    on the ALTO guidance to avoid causing network congestion.  Instead,
>    applications MUST use other appropriate means, such as TCP based
>    transport, to avoid causing excessive congestion.

REQ. ARv14-13:  Not applicable: This requirement is not about the
    ALTO Client Protocol (specification|implementation) itself,
    but about the application using it.

>    REQ.  ARv14-14: In the target-independent query mode, the ALTO query
>    message SHOULD allow the ALTO client to express which host
>    characteristics attributes should be returned.

REQ.  ARv14-14:  Full compliant: 7.7.2.2

>    REQ.  ARv14-15: In the target-aware query mode, the ALTO query
>    message SHOULD allow the ALTO client to express which rating criteria
>    should be considered by the server, as well as their relative
>    relevance for the specific application that will eventually make use
>    of the guidance.  The corresponding ALTO response message SHOULD
>    allow the ALTO server to express which rating criteria have been
>    considered when generating the response.

REQ.  ARv14-15:  Full compliant: 7.7.4.1.3, 7.7.4.1.5

>    REQ.  ARv14-16: An ALTO client protocol specification MUST define
>    mechanisms, which can be used by the ALTO client and the ALTO server
>    to indicate that a rating criteria used by the other party is of an
>    unsupported type.

REQ.  ARv14-16:  Full compliant: 7.4.3.

> 3.1.4.  Placement of Entities and Timing of Transactions
> 
>    With respect to the placement of ALTO clients, several modes of
>    operation exist:
> 
>    o  One mode of ALTO operation is that an ALTO client may be embedded
>       directly in the resource consumer, i.e., the application protocol
>       entity that will eventually initiate data transmission to/from the
>       selected resource provider(s) in order to access the desired
>       resource.  For example, an ALTO client could be integrated into
>       the peer of a P2P application that uses a distributed algorithm
>       such as "query flooding" for resource discovery.
> 
>    o  Another mode of operation is to integrate the ALTO client into a
>       third party such as a resource directory.  This third party may
>       issue ALTO queries to solicit preference on potential resource
>       providers, considering the respective resource consumer.  For
>       example, an ALTO client could be integrated into the tracker of a
>       tracker-based P2P application, in order to request ALTO guidance
>       on behalf of the peers contacting the tracker.
> 
>    REQ.  ARv14-17: An ALTO client protocol MUST support the mode of
>    operation in which the ALTO client is directly embedded in the
>    resource consumer.

REQ.  ARv14-17: Full Compliant: 8.2, 8.3

>    REQ.  ARv14-18: An ALTO client protocol MUST support the mode of
>    operation in which the ALTO client is embedded in a third party.
>    This third party performs queries on behalf of resource consumers.

REQ.  ARv14-18:  Full Compliant: 8.1

>    REQ.  ARv14-19: An ALTO client protocol MUST be designed in a way
>    that the ALTO service can be provided by an entity which is not the
>    operator of the underlying IP network.

REQ.  ARv12-19:  Full compliant: The ALTO protocol is based on HTTP
    (Sec.  6).  HTTP can be used to access servers anywhere in the 
    Internet, which are operated by arbitrary entities.  No additional
    single-domain or link-layer-coupled mechanisms (e.g. DHCP, IP
    multicasting/broadcasts, etc.) are mandatory.

>    REQ.  ARv14-20: An ALTO client protocol MUST be designed in a way
>    that different instances of the ALTO service operated by different
>    providers can coexist.

REQ.  ARv14-20:  Full compliant: The ALTO protocol is based on HTTP
    (Sec. 6). Servers operated by different entities can coexist.

    The ALTO server discovery mechanism, which is out of the scope of
    this document, may need additional mechanisms for selecting the
    desired ALTO server operator.

>    REQ.  ARv14-21: An ALTO client protocol specification MUST specify at
>    least one query mode, either the target-aware or the target-
>    independent query mode.

REQ.  ARv14-21:  Full compliant.  The target-independent query mode
    is implemented by the Network Map (7.7.1.1) and the Cost Map
    (7.7.1.2), which MUST be supported.

>    REQ.  ARv14-22: An ALTO client protocol specification SHOULD specify
>    both the target-aware and the target-independent query mode.  If an
>    ALTO client protocol specification specifies more than one query
>    mode, it MUST define at least one of these modes as REQUIRED to
>    implement by ALTO Clients and ALTO Servers.  Furthermore, it MUST
>    specify an appropriate protocol mechanism for negotiating between
>    ALTO Client and ALTO Server, which query mode to use.

REQ.  ARv14-22:  Full compliant.  The target-independent query mode MUST
    be supported (see ARv14-21). The target-aware query mode is
    implemented by the Endpoint Property Service, which MAY be provided
    by an ALTO server (7.7.3.1) and the Endpoint Cost Service, which MAY
    be provided by an ALTO server (7.7.4.1).


>    REQ.  ARv14-23: An ALTO client protocol SHOULD support version
>    numbering, TTL (time-to-live) attributes, and/or similar mechanisms
>    in ALTO transactions, in order to enable time validity checking for
>    caching, and to enable comparisons of multiple recommendations
>    obtained through redistribution.

REQ.  ARv14-23:  Partially compliant: Network Map Version Tag defined
    in 5.3.  TTL attribute defined in the underlying HTTP 
    ("expires"/"s-maxage" headers).

    There used to be an own section "8. Redistributable Responses"
    in draft-ietf-alto-protocol-10.txt, which has been removed in -11

    There is a reference to draft-gu-alto-redistribution-03, which
    has expired January 13, 2011, and which does not contain a
    specification of such protocol elements.

>    REQ.  ARv14-24: An ALTO client protocol SHOULD allow the ALTO server
>    to add information about appropriate modes of re-use to its ALTO
>    responses.  Re-use may include redistributing an ALTO response to
>    other parties, as well as using the same ALTO information in a
>    resource directory to improve the responses to different resource
>    consumers, within the specified lifetime of the ALTO response.  The
>    ALTO server SHOULD be able to express that
> 
>    o  no re-use should occur
> 
>    o  re-use is appropriate for a specific "target audience", i.e., a
>       set of resource consumers explicitly defined by a list of host
>       group descriptors.  The ALTO server MAY specify a "target
>       audience" in the ALTO response, which is only a subset of the
>       known actual "target audience", e.g., if required by operator
>       policies
> 
>    o  re-use is appropriate for any resource consumer that would send
>       (or cause a third party sending on behalf of it) the same ALTO
>       query (i.e., with the same query parameters, except for the
>       resource consumer ID, if applicable) to this ALTO server
> 
>    o  re-use is appropriate for any resource consumer that would send
>       (or cause a third party sending on behalf of it) the same ALTO
>       query (i.e., with the same query parameters, except for the
>       resource consumer ID, if applicable) to any other ALTO server,
>       which was discovered (using an ALTO discovery mechanism) together
>       with this ALTO server
> 
>    o  re-use is appropriate for any resource consumer that would send
>       (or cause a third party sending on behalf of it) the same ALTO
>       query (i.e., with the same query parameters, except for the
>       resource consumer ID, if applicable) to any ALTO server in the
>       whole network

REQ.  ARv14-24:  Partially compliant: first and last option supported
    by HTTP mechanisms. Second and third option relied on the now-removed
    section 8 of draft-ietf-alto-protocol-10

>    REQ.  ARv14-25: An ALTO client protocol MUST support the transport of
>    ALTO transactions even if the ALTO client is located in the private
>    address realm behind a network address translator (NAT).  There are
>    different types of NAT, see [RFC4787] and [RFC5382].

REQ.  ARv14-25:  Full compliant: The ALTO protocol is based on HTTP
    (Sec.  6).  Allowing HTTP traffic is one of the most basic requirements
    for all types of NAT. For detection of "public" IP address see 9.3.

> 3.1.5.  Protocol Extensibility
> 
>    REQ.  ARv14-26: An ALTO client protocol MUST include support for
>    adding protocol extensions in a non-disruptive, backward-compatible
>    way.

REQ.  ARv14-26:  Full compliant: 10.1


>    REQ.  ARv14-27: An ALTO client protocol MUST include protocol
>    versioning support, in order to clearly distinguish between
>    incompatible versions of the protocol.

REQ.  ARv14-27:  NOT compliant. There is no version field.
    7.6. states: "Future extensions or
    versions of the ALTO Protocol SHOULD be accomplished by extending
    existing media types or adding new media types, but retaining the
    same format for the Information Resource Directory."

    As workaround, one could define new media types such as
    alto-directory_v2_0+json   or
    alto2-directory+json

> 3.1.6.  Error Handling and Overload Protection
> 
>    REQ.  ARv14-28: An ALTO client protocol MUST use TCP based transport.

REQ.  ARv14-28:  Full compliant.  Protocol is based on HTTP (6.), which
    does not neccessarily run on top of TCP (see 1.4. of RFC 2616), but
    de-facto always does.


side note: IESG evaluation of the requirements document likely will
result in this requirement being changed to something like:

REQ.  ARv15-28 An ALTO client protocol MUST use a congestion-aware              
transport protocol, e.g., TCP.                                                  

but this will not cause any problem here.


>    REQ.  ARv14-29: An ALTO client protocol specification MUST specify
>    mechanisms, or detail how to leverage appropriate mechanisms provided
>    by underlying protocol layers, which can be used by an ALTO server to
>    inform clients about an impending or occurring overload situation,
>    and request them to throttle their query rate.
> 
>    In particular, a simple form of throttling is to let an ALTO server
>    answer a query with an error message advising the client to retry the
>    query later (e.g, using a protocol function such as HTTP's Retry-
>    After header ([RFC2616], section 14.37).  Another simple option is to
>    actually answer the query with the desired information, but adding an
>    indication that the ALTO client should not send further queries to
>    this ALTO server before an indicated period of time has elapsed.
> 
>    REQ.  ARv14-30: An ALTO client protocol specification MUST specify
>    mechanisms, or detail how to leverage appropriate mechanisms provided
>    by underlying protocol layers, which can be used by an ALTO server to
>    inform clients about an impending or occurring overload situation,
>    and redirect them to another ALTO server.
> 
>    REQ.  ARv14-31: An ALTO client protocol specification MUST specify
>    mechanisms, or detail how to leverage appropriate mechanisms provided
>    by underlying protocol layers, which can be used by an ALTO server to
>    inform clients about an impending or occurring overload situation,
>    and terminate the conversation with the ALTO client.
> 
>    REQ.  ARv14-32: An ALTO client protocol specification MUST specify
>    mechanisms, or detail how to leverage appropriate mechanisms provided
>    by underlying protocol layers, which can be used by an ALTO server to
>    inform clients about its inability to answer queries due to technical
>    problems or system maintenance, and advise them to retry the query
>    later.
> 
>    REQ.  ARv14-33: An ALTO client protocol specification MUST specify
>    mechanisms, or detail how to leverage appropriate mechanisms provided
>    by underlying protocol layers, which can be used by an ALTO server to
>    inform clients about its inability to answer queries due to technical
>    problems or system maintenance, and redirect them to another ALTO
>    server.
> 
>    REQ.  ARv14-34: An ALTO client protocol specification MUST specify
>    mechanisms, or detail how to leverage appropriate mechanisms provided
>    by underlying protocol layers, which can be used by an ALTO server to
>    inform clients about its inability to answer queries due to technical
>    problems or system maintenance, and terminate the conversation with
>    the ALTO client.

REQ.  ARv14-29..34:  Partially compliant: The protocol is based on HTTP,
    which features various appropriate protocol mechanisms (R-A header,
    3xx and 503 replies, etc.), but no specific guidance is provided
    when and how to use them in conjunction with the ALTO protocol.

> 3.2.  ALTO Server Discovery

REQ.  ARv14-35..42: not applicable to this document

> 3.3.  Security and Privacy
> 
>    REQ.  ARv14-43: An ALTO client protocol specification MUST specify
>    mechanisms for the authentication of ALTO servers, or how to leverage
>    appropriate mechanisms provided by underlying protocol layers.

REQ.  ARv14-43:  Full compliant: 7.2.5.

>    REQ.  ARv14-44: An ALTO client protocol specification MUST specify
>    mechanisms for the authentication of ALTO clients, or how to leverage
>    appropriate mechanisms provided by underlying protocol layers.
 
REQ.  ARv14-44:  Full compliant: 7.2.5.

>    REQ.  ARv14-45: An ALTO client protocol specification MUST specify
>    mechanisms for the encryption of messages, or how to leverage
>    appropriate mechanisms provided by underlying protocol layers.
 
REQ.  ARv14-45:  Full compliant: 7.2.5.

>    REQ.  ARv14-46: An ALTO client is not required to implement
>    mechanisms or to comply with rules that limit its ability to
>    redistribute information retrieved from the ALTO server to third
>    parties.

REQ.  ARv14-46: not applicable to this document. See also sec. 11.3.:
    "Digital Rights Management (DRM) techniques and legal agreements
    protecting ALTO information are outside of the scope of this
    document."

>    REQ.  ARv14-47: An ALTO client protocol MUST support different levels
>    of detail in queries and responses, in order to protect the privacy
>    of users, to ensure that the operators of ALTO servers and other
>    users of the same application cannot derive sensitive information.

REQ.  ARv14-47:  Full compliant.  Host Group Descriptors are always
    encoded as TypedEndpointAddr, which allows to use IP prefixes.
    Therefore it is possible to obfuscate the identity of candidate
    resource consumers, e.g., by specifying a broader address range
    (i.e., a shorter prefix length) than a group of hosts in question
    actually uses, or by zeroing-out or randomizing the last few bits of
    IP addresses.  However, there is the potential side effect of
    yielding inaccurate results.

>    REQ.  ARv14-48: An ALTO client protocol MAY include mechanisms that
>    can be used by the ALTO client when requesting guidance to specify
>    the resource (e.g., content identifiers) it wants to access.  An ALTO
>    server MUST provide adequate guidance even if the ALTO client prefers
>    not to specify the desired resource (e.g., keeps the data field
>    empty).  The mechanism MUST be designed in a way that the operator of
>    the ALTO server cannot easily deduce the resource identifier (e.g.,
>    file name in P2P file sharing) if the ALTO client prefers not to
>    specify it.

REQ.  ARv14-48:  Full compliant.  The optional ("MAY") feature is not
    defined and therefore, the MUST-statements do not apply.

>    REQ.  ARv14-49: An ALTO client protocol specification MUST specify
>    appropriate mechanisms for protecting the ALTO service against DoS
>    attacks, or how to leverage appropriate mechanisms provided by
>    underlying protocol layers.

REQ.  ARv14-49:  Partially compliant: The protocol is based on HTTP,
    and protecting HTTP-based services against different kinds of
    attacks, including DoS attacks, is a rather well-understood issue.
    However, no specific guidance is provided for ALTO over HTTP.


-- end --

From haibin.song@huawei.com  Mon May 14 02:26:18 2012
Return-Path: <haibin.song@huawei.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 36F5F21F860F for <alto@ietfa.amsl.com>; Mon, 14 May 2012 02:26:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qp6tUlM8-nZ0 for <alto@ietfa.amsl.com>; Mon, 14 May 2012 02:26:17 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 86E6821F8604 for <alto@ietf.org>; Mon, 14 May 2012 02:26:17 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AFX00222; Mon, 14 May 2012 05:26:17 -0400 (EDT)
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 14 May 2012 02:24:45 -0700
Received: from SZXEML430-HUB.china.huawei.com (10.72.61.38) by dfweml407-hub.china.huawei.com (10.193.5.132) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 14 May 2012 02:24:44 -0700
Received: from SZXEML534-MBX.china.huawei.com ([169.254.2.45]) by szxeml430-hub.china.huawei.com ([10.72.61.38]) with mapi id 14.01.0323.003; Mon, 14 May 2012 17:24:40 +0800
From: Songhaibin <haibin.song@huawei.com>
To: Richard Alimi <rich@velvetsea.net>
Thread-Topic: [alto] WGLC: draft-ietf-alto-protocol-11
Thread-Index: AQHNMM5feC2QQa8k7EKyXRG5gXrRyZbJAqQQ
Date: Mon, 14 May 2012 09:24:39 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F23A8370E@szxeml534-mbx.china.huawei.com>
References: <4F8BE443.9050903@telecomitalia.it> <E33E01DFD5BEA24B9F3F18671078951F23A51746@szxeml534-mbx.china.huawei.com> <CA+cvDaaPktLnyJb+tqm2KW7+qA5+bNAjToK1NjmPrA3yNFfCvg@mail.gmail.com>
In-Reply-To: <CA+cvDaaPktLnyJb+tqm2KW7+qA5+bNAjToK1NjmPrA3yNFfCvg@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.73]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 14 May 2012 09:26:18 -0000

Hi Rich,



> -----Original Message-----
> From: richard.alimi@gmail.com [mailto:richard.alimi@gmail.com] On Behalf =
Of
> Richard Alimi
> Sent: Sunday, May 13, 2012 2:05 PM
> To: Songhaibin
> Cc: Enrico Marocco; alto@ietf.org
> Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11
>=20
> On Mon, Apr 23, 2012 at 6:47 PM, Songhaibin <haibin.song@huawei.com> wrot=
e:
> > In general, this draft is in good shape.
> >
> > One randomly caught problem, in Section 5.1.2.2, the ordinal mode
> introduction, it says this cost mode is a ranking from a particular sourc=
e to a set of
> destinations. But in Section 5.2, the introduction of cost map structure,=
 the cost
> mode "ordinal" can be applied to m*n entries in the cost map. So I sugges=
t to
> modify the previous section 5.1.2.2 to make them consistent.
> >
>=20
> Thanks for catching that. In fact, the sentence "If the Cost Mode is
> 'ordinal', the Path Cost of each communicating pair is relative to the
> m*n entries" can probably just be removed.
>=20

I'm sorry that I have a different opinion here. The "ordinal" cost to entri=
es in a matrix makes sense to me. I prefer to modify the definition in 5.1.=
2.2, the ranking can be from multiple sources to multiple destinations. Or =
is there special reason to limit it to 1*n?

BR,
-Haibin

> Thanks,
> Rich
>=20
> > BR,
> > -Haibin
> >
> >> -----Original Message-----
> >> From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf O=
f
> Enrico
> >> Marocco
> >> Sent: Monday, April 16, 2012 5:20 PM
> >> To: alto@ietf.org
> >> Subject: [alto] WGLC: draft-ietf-alto-protocol-11
> >>
> >>
> >> The chairs would like to declare a Working Group Last Call for
> >> draft-ietf-alto-protocol-11, ending Friday May 11th.
> >>
> >> Please do review the latest version of the draft, and send any comment=
s to
> the
> >> list before the expiry of WGLC so we can get this document ready for t=
he
> IESG.
> >>
> >> --
> >> Ciao,
> >> Enrico
> >
> > _______________________________________________
> > alto mailing list
> > alto@ietf.org
> > https://www.ietf.org/mailman/listinfo/alto

From bclaise@cisco.com  Mon May 14 06:34:53 2012
Return-Path: <bclaise@cisco.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 A53EB21F84C8 for <alto@ietfa.amsl.com>; Mon, 14 May 2012 06:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.048
X-Spam-Level: 
X-Spam-Status: No, score=-8.048 tagged_above=-999 required=5 tests=[AWL=2.550,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QxFFEIFMsLOK for <alto@ietfa.amsl.com>; Mon, 14 May 2012 06:34:52 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 4FF1721F849A for <alto@ietf.org>; Mon, 14 May 2012 06:34:52 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q4EDYoqt029983; Mon, 14 May 2012 15:34:51 +0200 (CEST)
Received: from [10.60.67.89] (ams-bclaise-8918.cisco.com [10.60.67.89]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q4EDYneB027549; Mon, 14 May 2012 15:34:50 +0200 (CEST)
Message-ID: <4FB109F9.50006@cisco.com>
Date: Mon, 14 May 2012 15:34:49 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Richard Alimi <rich@velvetsea.net>
References: <4FABFCEC.5070701@cisco.com> <CA+cvDaagjh49t5Zck1pj+yJq6UCibhHH+3FBWA8eioMDOsibsA@mail.gmail.com>
In-Reply-To: <CA+cvDaagjh49t5Zck1pj+yJq6UCibhHH+3FBWA8eioMDOsibsA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040501020800010208060202"
Cc: Brian Trammell <trammell@tik.ee.ethz.ch>, alto@ietf.org, ipfix-chairs@tools.ietf.org
Subject: Re: [alto] IPFIX Information Element in the ALTO protocol
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 14 May 2012 13:34:53 -0000

This is a multi-part message in MIME format.
--------------040501020800010208060202
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Richard,
> On Thu, May 10, 2012 at 10:37 AM, Benoit Claise<bclaise@cisco.com>  wrote:
>> Dear all,
>>
>> I've been reviewing draft-ietf-alto-reqs-14 and the following requirement
>> got me thinking:
>>
>>   REQ.  ARv14-5: An ALTO client protocol MUST be extensible to enable
>>     support of other host group descriptor types in future.  An ALTO
>>     client protocol specification MUST define an appropriate procedure
>>     for adding new host group descriptor types, e.g., by establishing an
>>     IANA registry.
>>
>> Why don't you reuse an existing registry, in which you will have all the
>> Information Elements already defined instead of defining a new one?
>> WhatI have in mind: the IPFIX I.E. IANA registry.
>> The piece of information I see in draft-ietf-alto-reqs-14 are IP address,
>> prefix, BGP AS: they're in IANA.
>> And many other IEs are already present, for future ALTO extensions, if
>> required.
>>
>> This would not only save one registry (ALTO Endpoint Property in
>> draft-ietf-alto-protocol-10), but offers a bigger advantage.
>> Let me explain.... When you will control your applications with ALTO, you
>> will anyway want to apply a flow measurement to monitor your changes, and to
>> serve as a feedback loop for more optimizations.
>> And the chances are high that you will using a NetFlow/IPFIX based
>> mechanism. Both NetFlow and IPFIX use the IPFIX I.E. IANA registry.
>>
>> Therefore, it would make sense to have consistent data models between ALTO
>> and IPFIX, and avoid a data model proxy if we want to compare the data.
>> Proposal: reuse the ElementIDs found in the IPFIX I.E. IANA registry
>> somewhere in your protocol.
> The suggested use case is in place of the Endpoint Property registry?
I'm referring to the examples in 
http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-7.5.3
So I guess it's 
http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-10.3. 
However, 
http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-10.3 
doesn't contain the initial series of values.
>
> Just to be sure I understand what would happen if we went that route,
> what are the restrictions for adding new information elements?
> Specifically, what kinds of elements are allowed or disallowed?
>
> Things that have been informally discussed in the ALTO WG so far have
> been things like load information and available network capacity.  Do
> those fit within the ipfix model?
The IANA considerations for new IPFIX IEs is in RFC5102, 
http://tools.ietf.org/html/rfc5102#section-7.1.
It mentions: IANA through Expert Review [RFC2434 
<http://tools.ietf.org/html/rfc2434>]
The most up to date document regarding IE allocation is 
http://tools.ietf.org/html/draft-ietf-ipfix-ie-doctors-02.
I don't believe there are any limitations on for new IEs such as load 
information and available network capacity.
Copying the IPFIX chairs and Brian Trammell.

Regards, Benoit.
>
> Thanks,
> Rich
>
>> Disclaimer: I have not read the protocol details
>>
>> Regards, Benoit.
>>
>>
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>>
>


--------------040501020800010208060202
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Richard,<br>
    <blockquote
cite="mid:CA+cvDaagjh49t5Zck1pj+yJq6UCibhHH+3FBWA8eioMDOsibsA@mail.gmail.com"
      type="cite">
      <pre wrap="">On Thu, May 10, 2012 at 10:37 AM, Benoit Claise <a class="moz-txt-link-rfc2396E" href="mailto:bclaise@cisco.com">&lt;bclaise@cisco.com&gt;</a> wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Dear all,

I've been reviewing draft-ietf-alto-reqs-14 and the following requirement
got me thinking:

&nbsp;REQ.  ARv14-5: An ALTO client protocol MUST be extensible to enable
   support of other host group descriptor types in future.  An ALTO
   client protocol specification MUST define an appropriate procedure
   for adding new host group descriptor types, e.g., by establishing an
   IANA registry.

Why don't you reuse an existing registry, in which you will have all the
Information Elements already defined instead of defining a new one?
WhatI have in mind: the IPFIX I.E. IANA registry.
The piece of information I see in draft-ietf-alto-reqs-14 are IP address,
prefix, BGP AS: they're in IANA.
And many other IEs are already present, for future ALTO extensions, if
required.

This would not only save one registry (ALTO Endpoint Property in
draft-ietf-alto-protocol-10), but offers a bigger advantage.
Let me explain.... When you will control your applications with ALTO, you
will anyway want to apply a flow measurement to monitor your changes, and to
serve as a feedback loop for more optimizations.
And the chances are high that you will using a NetFlow/IPFIX based
mechanism. Both NetFlow and IPFIX use the IPFIX I.E. IANA registry.

Therefore, it would make sense to have consistent data models between ALTO
and IPFIX, and avoid a data model proxy if we want to compare the data.
Proposal: reuse the ElementIDs found in the IPFIX I.E. IANA registry
somewhere in your protocol.
</pre>
      </blockquote>
      <pre wrap="">
The suggested use case is in place of the Endpoint Property registry?</pre>
    </blockquote>
    I'm referring to the examples in
    <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-7.5.3">http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-7.5.3</a><br>
    So I guess it's
    <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-10.3">http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-10.3</a>.
    However,
    <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-10.3">http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-10.3</a>
    doesn't contain the initial series of values.<br>
    <blockquote
cite="mid:CA+cvDaagjh49t5Zck1pj+yJq6UCibhHH+3FBWA8eioMDOsibsA@mail.gmail.com"
      type="cite">
      <pre wrap="">

Just to be sure I understand what would happen if we went that route,
what are the restrictions for adding new information elements?
Specifically, what kinds of elements are allowed or disallowed?

Things that have been informally discussed in the ALTO WG so far have
been things like load information and available network capacity.  Do
those fit within the ipfix model?</pre>
    </blockquote>
    The IANA considerations for new IPFIX IEs is in RFC5102,
    <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc5102#section-7.1">http://tools.ietf.org/html/rfc5102#section-7.1</a>.<br>
    It mentions: IANA through Expert Review [<a
      href="http://tools.ietf.org/html/rfc2434" title="&quot;Guidelines
      for Writing an IANA Considerations Section in RFCs&quot;">RFC2434</a>]<br>
    The most up to date document regarding IE allocation is
    <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-ipfix-ie-doctors-02">http://tools.ietf.org/html/draft-ietf-ipfix-ie-doctors-02</a>.<br>
    I don't believe there are any limitations on for new IEs such as
    load information and available network capacity.<br>
    Copying the IPFIX chairs and Brian Trammell.<br>
    <br>
    Regards, Benoit.<br>
    <blockquote
cite="mid:CA+cvDaagjh49t5Zck1pj+yJq6UCibhHH+3FBWA8eioMDOsibsA@mail.gmail.com"
      type="cite">
      <pre wrap="">

Thanks,
Rich

</pre>
      <blockquote type="cite">
        <pre wrap="">
Disclaimer: I have not read the protocol details

Regards, Benoit.


_______________________________________________
alto mailing list
<a class="moz-txt-link-abbreviated" href="mailto:alto@ietf.org">alto@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/alto">https://www.ietf.org/mailman/listinfo/alto</a>

</pre>
      </blockquote>
      <pre wrap="">

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------040501020800010208060202--

From ted.ietf@gmail.com  Mon May 14 07:09:14 2012
Return-Path: <ted.ietf@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 86EC221F8752; Mon, 14 May 2012 07:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.594
X-Spam-Level: 
X-Spam-Status: No, score=-3.594 tagged_above=-999 required=5 tests=[AWL=0.005,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nntZi4vkK3e7; Mon, 14 May 2012 07:09:13 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9AA3521F848A; Mon, 14 May 2012 07:09:13 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so6010269vbb.31 for <multiple recipients>; Mon, 14 May 2012 07:09:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Jb8HjFePmOthOXvZaxoAAdbenouXbT/+eFgqQYRoWXU=; b=g0b9SbylXzQHUIvhSSCK0cgszoArfErTHIBEof1RGhwFQMwTqwI498jFVr9rmUjjX3 WVySYf7iNDT6O9dVmgxdRNFftc2ulqmzow/fBQ65w6WNGXFTBp5oh0w02NJ/j3NWbwP4 eZr8+H8nTdAr93wZXL9QHBCbFeXezf+LjKgDJ/qX5r7Li5bNGgzI1a0RT/c7KsheMJoS lDggBRvVCDLnvttyZ9QRRLubTaHo/Wm+sq+herECr9g64JdXqCCmScOTXOqCdcz7ocLa IBV0ht5JAXZAGgem1Tm+xTi735Nq+gL4rdqVSN4NnUEwQJGKkcqGFdKJgo9Dtn4Y/6u6 OCog==
MIME-Version: 1.0
Received: by 10.52.69.38 with SMTP id b6mr4068393vdu.22.1337004553034; Mon, 14 May 2012 07:09:13 -0700 (PDT)
Received: by 10.52.162.99 with HTTP; Mon, 14 May 2012 07:09:12 -0700 (PDT)
In-Reply-To: <CADOmCZV3N=DrgiCX1W++OjkBhdNo4-0YMBPARJzEM9aTybSa0Q@mail.gmail.com>
References: <CA+9kkMB4nUayYO3q8ydj477jh9NM8oZyXAQ5k-NsRN=KHjb3cA@mail.gmail.com> <CADOmCZV3N=DrgiCX1W++OjkBhdNo4-0YMBPARJzEM9aTybSa0Q@mail.gmail.com>
Date: Mon, 14 May 2012 07:09:12 -0700
Message-ID: <CA+9kkMD6+JdMAecz2h=CzRc6x_kt3042Lr_z0crUzzfdCXJJ5Q@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Richard Alimi <ralimi@google.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 14 May 2012 08:06:59 -0700
Cc: draft-ietf-alto-protocol.all@tools.ietf.org, alto <alto@ietf.org>, apps-discuss@ietf.org
Subject: Re: [alto] Review of draft-ietf-alto-protocol-11.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 14 May 2012 14:09:14 -0000

On Sat, May 12, 2012 at 12:39 PM, Richard Alimi <ralimi@google.com> wrote:
<snipped>
>> If I understand JASONString correctly, no language tag is supplied,
>> so human readability will be highly variable, =A0Fixing that, rather
>> than relying on a local mapping of the underlying code, is hard
>> work. =A0Dropping this optional aspect of the error resource may
>> be something for the WG to consider; this pushes localization
>> of the error code description to the endpoint.
>
> That seems reasonable. =A0The intent was to help with debugging (and not
> display to a user), so I'd either be okay with removing it or keeping
> it and not worrying about the language. =A0Is there standard guidance to
> apply here?
>

I don't think there is standard guidance.  My personal advice, free
today and worth what you pay for it, is that localization of error
codes works better if the client simply has a local table of what maps
to the code.  If you have to do language negotiation just to get the
error string right, you're introducing a lot of complexity for
marginal gain.  If it's a debug string, rather than a user-facing
error, then marking it such and noting it will contain arcana rather
than actual error explanations is probably okay.  I don't think many
people expect a localized stack trace.

<much snipped>
> Yes - I see the disconnect. =A0I'd like to avoid solving the larger
> deployment considerations under NATs (the deployment consideratoins
> document should be handling that) in this document and instead focus
> on the messaging details.

I haven't read the deployment considerations doc, but if this is
handled there, then a pointer to that would be fine.

> Perhaps it would be best to change the
> statement w.r.t. STUN to instead say MAY. =A0This document can certainly
> give a concise statement of the problems you identified there.
>
> How does that sound?
>

I don't think it is really a question of MAY vs. SHOULD.  The document
seems to be assigning responsibility to working out the NAT boundary
problem to the client.  That means the client needs some way of
determining whether it is going through an address translator to reach
 the target.  I think keeping it at SHOULD use STUN for cases where a
translation will take place is correct; the problem is it is SHOULD
NOT for cases where the source and destination are within a NAT
boundary.  If you can, I would personally say something brief like
that, and give a pointer to the deployment considerations document for
more on how you determine when you have each case.  The optimization
(omitting the Source Endpoint), just highlights the problem.


regards,

Ted Hardie

From richard.alimi@gmail.com  Mon May 14 12:37:08 2012
Return-Path: <richard.alimi@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 42D8B21F88E0 for <alto@ietfa.amsl.com>; Mon, 14 May 2012 12:37:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.564,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hvXLerseeU46 for <alto@ietfa.amsl.com>; Mon, 14 May 2012 12:37:07 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8669C21F889F for <alto@ietf.org>; Mon, 14 May 2012 12:37:07 -0700 (PDT)
Received: by dacx6 with SMTP id x6so6539832dac.31 for <alto@ietf.org>; Mon, 14 May 2012 12:37:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=1YJqDkix993MBsdqoRLYvx5dBmVEAwKrGxsddKtSHfM=; b=KNoy2APdZwiVCVq/ctly0/e6dzkq2qxbLprrYOrJ0mqsFmao74DVZFO6X102JCg0hU qA1MMA3se4fwVwXFBOWA7lpcgUlHn+K33D9wRAy2iF9svdVcbGntYU9kBGKWi3GRkd9X jGeehEOh9MtExHikq20+Cb4aPpPOvD68w+r4kgF7SY177WqhBJyeS7l5HViJxcAGI+P0 K1SIzuenqr3wAvTeq3XJKAK3nd6k4TTOGYCPCONleZROKRDT5gusxpRcDIuiOYJ2RPOV gUxdSXPvdt/tr/0vLiMFU4B9o7IswN5Po9dNrWbeySGLaQY4sx2eVSjI8rdaa5ExGj3F OIyA==
Received: by 10.50.187.228 with SMTP id fv4mr5647943igc.10.1337024227212; Mon, 14 May 2012 12:37:07 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.231.209.82 with HTTP; Mon, 14 May 2012 12:36:45 -0700 (PDT)
In-Reply-To: <4FB109F9.50006@cisco.com>
References: <4FABFCEC.5070701@cisco.com> <CA+cvDaagjh49t5Zck1pj+yJq6UCibhHH+3FBWA8eioMDOsibsA@mail.gmail.com> <4FB109F9.50006@cisco.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Mon, 14 May 2012 12:36:45 -0700
X-Google-Sender-Auth: 0pjNWywGN3mypYu7Xg04wDaynO0
Message-ID: <CA+cvDaYsHSYLj=BwE3OzzN+vtT5mK=MWpWm7SX5LFdBbVpNuPg@mail.gmail.com>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Brian Trammell <trammell@tik.ee.ethz.ch>, alto@ietf.org, ipfix-chairs@tools.ietf.org
Subject: Re: [alto] IPFIX Information Element in the ALTO protocol
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 14 May 2012 19:37:08 -0000

On Mon, May 14, 2012 at 6:34 AM, Benoit Claise <bclaise@cisco.com> wrote:
> Hi Richard,
>
> On Thu, May 10, 2012 at 10:37 AM, Benoit Claise <bclaise@cisco.com> wrote=
:
>
> Dear all,
>
> I've been reviewing draft-ietf-alto-reqs-14 and the following requirement
> got me thinking:
>
> =A0REQ.  ARv14-5: An ALTO client protocol MUST be extensible to enable
>    support of other host group descriptor types in future.  An ALTO
>    client protocol specification MUST define an appropriate procedure
>    for adding new host group descriptor types, e.g., by establishing an
>    IANA registry.
>
> Why don't you reuse an existing registry, in which you will have all the
> Information Elements already defined instead of defining a new one?
> WhatI have in mind: the IPFIX I.E. IANA registry.
> The piece of information I see in draft-ietf-alto-reqs-14 are IP address,
> prefix, BGP AS: they're in IANA.
> And many other IEs are already present, for future ALTO extensions, if
> required.
>
> This would not only save one registry (ALTO Endpoint Property in
> draft-ietf-alto-protocol-10), but offers a bigger advantage.
> Let me explain.... When you will control your applications with ALTO, you
> will anyway want to apply a flow measurement to monitor your changes, and=
 to
> serve as a feedback loop for more optimizations.
> And the chances are high that you will using a NetFlow/IPFIX based
> mechanism. Both NetFlow and IPFIX use the IPFIX I.E. IANA registry.
>
> Therefore, it would make sense to have consistent data models between ALT=
O
> and IPFIX, and avoid a data model proxy if we want to compare the data.
> Proposal: reuse the ElementIDs found in the IPFIX I.E. IANA registry
> somewhere in your protocol.
>
> The suggested use case is in place of the Endpoint Property registry?
>
> I'm referring to the examples in
> http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-7.5.3
> So I guess it's
> http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-10.3.
> However, http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-1=
0.3
> doesn't contain the initial series of values.

Those are two different things in the protocol.  The former is for
identifying endpoints themselves, the latter is for properties
associated with those endpoints.

>
>
> Just to be sure I understand what would happen if we went that route,
> what are the restrictions for adding new information elements?
> Specifically, what kinds of elements are allowed or disallowed?
>
> Things that have been informally discussed in the ALTO WG so far have
> been things like load information and available network capacity.  Do
> those fit within the ipfix model?
>
> The IANA considerations for new IPFIX IEs is in RFC5102,
> http://tools.ietf.org/html/rfc5102#section-7.1.
> It mentions: IANA through Expert Review [RFC2434]
> The most up to date document regarding IE allocation is
> http://tools.ietf.org/html/draft-ietf-ipfix-ie-doctors-02.
> I don't believe there are any limitations on for new IEs such as load
> information and available network capacity.
> Copying the IPFIX chairs and Brian Trammell.

I think the main consideration here is whether IPFIX really is the
canonical source (and is planned to be in the future) for data
that an application (note: not only network operator) would want to
know about an endpoint.  In particular, in the CDN use cases, an ALTO
map may be provided by a CDN to advertise costs to/from and properties
of various cache nodes.

>From RFC5102, Section 2.1 I see that a registration seems to enforce
that the Information Element is derived from a flow or someone
observing the flow on the network:

   description - The semantics of this Information Element.  Describes
      how this Information Element is derived from the Flow or other
      information available to the observer.

To me, that seems too restrictive for the ALTO model which is
providing information to the application layer.

Thanks,
Rich

>
> Regards, Benoit.
>
>
> Thanks,
> Rich
>
> Disclaimer: I have not read the protocol details
>
> Regards, Benoit.
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
>
>

From ralimi@google.com  Tue May 15 00:37:43 2012
Return-Path: <ralimi@google.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 0EE8B21F8701 for <alto@ietfa.amsl.com>; Tue, 15 May 2012 00:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.402, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DCjcnpML4Hl for <alto@ietfa.amsl.com>; Tue, 15 May 2012 00:37:42 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id CBD7E21F84D5 for <alto@ietf.org>; Tue, 15 May 2012 00:37:41 -0700 (PDT)
Received: by lagv3 with SMTP id v3so3017760lag.31 for <alto@ietf.org>; Tue, 15 May 2012 00:37:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-system-of-record; bh=VvChiZLIkm3Uwl1u9ciqYe/YAydY8zj0WGJbeh8D6Xk=; b=ZhkEBvIYolblh5Ymq0iZZLoehQSB/sxI+FsEOALbYwRuBnNGjhZ5eL3kRUc+97FX+d D0gqpKnk9aqsM/2vJkMvG7QNWvO6tT9JAqBwjgBaEcu8Jxm/rARmf0RvziIpMj6Wf7x9 57CDvA+273asvMXx9QZm8UBbnQXi0Fg9yYPZDWR8w3BEFjvKtJxMvh5lFW+Iuvy4vSQX qIj0eEMCx+aBvLrscBCMpIvAYtckJP5XzkgNaahNWjCGaVn0F+Mw+erxl3F/Yka3sdDy qHeSGliq4u+tCXttVtiKYXTzecg1oYshzDAkughUXadm38QotI0lgkli5IvEewIYtn1T sJsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-system-of-record :x-gm-message-state; bh=VvChiZLIkm3Uwl1u9ciqYe/YAydY8zj0WGJbeh8D6Xk=; b=S/uM1SnpERftX/pA9PReg6tLuuZYCdZtu2TLkGH+A/EFz209jNOJeD8gvjbqoNMORE Eu2eBnpUm6+zAkIB2nyW+bgBQFFbu47dWB7aUevPGh01aI9L8yQcRaVG8Q3dYKtjhoUp VTafE32hVjEnw0LAVKavufK4HDEesc1FhapANNUh89pMkvewkTVQTnzJCGIPWvFXsDI1 0d+GCm0PG1hTRdVspUvGHGsXDdGp2u3v7o5rikKXs9dsAenJ6DkQJsJHDIYRuEob9jqR qsk8rOhocKFBrZS0ycEYlACXZWF+AtX7l3QNanDPoka9jSji9PqReOQPPJZLEx8QuqXb h4Ig==
Received: by 10.112.47.8 with SMTP id z8mr1670533lbm.51.1337067460569; Tue, 15 May 2012 00:37:40 -0700 (PDT)
Received: by 10.112.47.8 with SMTP id z8mr1670526lbm.51.1337067460438; Tue, 15 May 2012 00:37:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.45.201 with HTTP; Tue, 15 May 2012 00:37:10 -0700 (PDT)
In-Reply-To: <CA+9kkMD6+JdMAecz2h=CzRc6x_kt3042Lr_z0crUzzfdCXJJ5Q@mail.gmail.com>
References: <CA+9kkMB4nUayYO3q8ydj477jh9NM8oZyXAQ5k-NsRN=KHjb3cA@mail.gmail.com> <CADOmCZV3N=DrgiCX1W++OjkBhdNo4-0YMBPARJzEM9aTybSa0Q@mail.gmail.com> <CA+9kkMD6+JdMAecz2h=CzRc6x_kt3042Lr_z0crUzzfdCXJJ5Q@mail.gmail.com>
From: Richard Alimi <ralimi@google.com>
Date: Tue, 15 May 2012 00:37:10 -0700
Message-ID: <CADOmCZXj2kLTq2oFJ+Xpz7OicQK9aTuiUBzGuQWYHUscsn-ZAg@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQlsjxzisjbKxzKY+p1/xc6bps+yrUr7tdDCgoOmDLj/Tz1C0yjXj8d8OTaTl78hadLCf583vuhDXDVNGzJtrrsW6+kTQPjj2R64am0KVCv4q0PI3ACrCg8V3F94iJrUNqnIx6JZ
Cc: draft-ietf-alto-protocol.all@tools.ietf.org, alto <alto@ietf.org>, apps-discuss@ietf.org
Subject: Re: [alto] Review of draft-ietf-alto-protocol-11.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 15 May 2012 07:37:43 -0000

On Mon, May 14, 2012 at 7:09 AM, Ted Hardie <ted.ietf@gmail.com> wrote:
> On Sat, May 12, 2012 at 12:39 PM, Richard Alimi <ralimi@google.com> wrote=
:
> <snipped>
>>> If I understand JASONString correctly, no language tag is supplied,
>>> so human readability will be highly variable, =A0Fixing that, rather
>>> than relying on a local mapping of the underlying code, is hard
>>> work. =A0Dropping this optional aspect of the error resource may
>>> be something for the WG to consider; this pushes localization
>>> of the error code description to the endpoint.
>>
>> That seems reasonable. =A0The intent was to help with debugging (and not
>> display to a user), so I'd either be okay with removing it or keeping
>> it and not worrying about the language. =A0Is there standard guidance to
>> apply here?
>>
>
> I don't think there is standard guidance. =A0My personal advice, free
> today and worth what you pay for it, is that localization of error
> codes works better if the client simply has a local table of what maps
> to the code. =A0If you have to do language negotiation just to get the
> error string right, you're introducing a lot of complexity for
> marginal gain. =A0If it's a debug string, rather than a user-facing
> error, then marking it such and noting it will contain arcana rather
> than actual error explanations is probably okay. =A0I don't think many
> people expect a localized stack trace.

Okay - I'll see if anyone else in the WG would like to comment, but
for now we can plan to remove it.

>
> <much snipped>
>> Yes - I see the disconnect. =A0I'd like to avoid solving the larger
>> deployment considerations under NATs (the deployment consideratoins
>> document should be handling that) in this document and instead focus
>> on the messaging details.
>
> I haven't read the deployment considerations doc, but if this is
> handled there, then a pointer to that would be fine.

Okay, so my memory served me incorrectly here.  I thought it was
handled there, but it wasn't...

>
>> Perhaps it would be best to change the
>> statement w.r.t. STUN to instead say MAY. =A0This document can certainly
>> give a concise statement of the problems you identified there.
>>
>> How does that sound?
>>
>
> I don't think it is really a question of MAY vs. SHOULD. =A0The document
> seems to be assigning responsibility to working out the NAT boundary
> problem to the client. =A0That means the client needs some way of
> determining whether it is going through an address translator to reach
> =A0the target. =A0I think keeping it at SHOULD use STUN for cases where a
> translation will take place is correct; the problem is it is SHOULD
> NOT for cases where the source and destination are within a NAT
> boundary. =A0If you can, I would personally say something brief like
> that, and give a pointer to the deployment considerations document for
> more on how you determine when you have each case. =A0The optimization
> (omitting the Source Endpoint), just highlights the problem.

Okay, so I think we'll need a bit more discussion on this as to how to
handle it.  I tend to think the deployment considerations document
would be a better place to handle this, but this section of it doesn't
exist yet today (contrary to my memory).

A solution without multiple levels of NATs here would be for the ALTO
Client to do the following algorithm:

  let D =3D set of destination addresses to which the cost should be querie=
d
  for each address 'a' through which the ALTO Client is reachable
(discovered via STUN, local interface address)
    Pick D_a =3D { subset of D that can reach the ALTO Client via address '=
a')
    query the Endpoint Cost Service with the source address and
destination addresses D_a

Things get hairier with multiple NATs, obviously.  The trickier part
of this would be how a client determines 'a'.  Multiple P2P
applications that I know about already implement logic for detecting
if it can use local address to talk to another peer.  We could
explicitly reference one of those as an example, but AFAIK those
algorithms mostly work only if there's a peer speaking the same P2P
protocol at the other end.

So, how about this which doesn't introduce a dependency on text which
does not yet exist in the deployment considerations document:
(1) as you suggested, indicate that the client SHOULD use STUN to
discover its own IP addresses when query for destination addresses
that are not behind the same NAT boundary, and SHOULD NOT use STUN for
destination addresses that are behind the same NAT boundary.
(2) Add this algorithm sketch as an example for using the Endpoint
Cost Service in a NAT environment, with the statement that determining
D_a may be application-dependent.

Then, if we want to add detail for specific techniques, we could add
those later in the deployment considerations document.

How does that sound?
Rich

>
>
> regards,
>
> Ted Hardie

From richard.alimi@gmail.com  Tue May 15 01:31:49 2012
Return-Path: <richard.alimi@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 261A021F893C for <alto@ietfa.amsl.com>; Tue, 15 May 2012 01:31:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level: 
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.494,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5nCcdLKwvmOj for <alto@ietfa.amsl.com>; Tue, 15 May 2012 01:31:48 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7243721F8935 for <alto@ietf.org>; Tue, 15 May 2012 01:31:48 -0700 (PDT)
Received: by yenq13 with SMTP id q13so6114494yen.31 for <alto@ietf.org>; Tue, 15 May 2012 01:31:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=iFFoCj0qQuZkUg1Aa1szVqMMGK32VRao9XyIJhnYtRw=; b=TQVYObQsOfsZVlq9h/fTn8iJ0iqAXTntxQfF/G32WurI+LlfL+iKbo2MUJacPVq3Vr Mxhdn4Q7BbqpCQRm6oZD8uvdR1oyfvAaTo5fub1OM6RTYvieOEM6HiYnTDgHV+nPrrqh ObqU1fk64wEz5K1kv7Rux9Er7UnUNaNSvvFCC9RQOXarucqC9PivVPeewjvVBqA3d1yB kEVpkRqmKxqHf+ZfQO4zZLpaY1N0KTL119xJg4kyqMWPnnETgZ0S0j/H8mh4qegQv3Bp sF1VpYU1GBUYqBTWqSs5ZnxBVe6HpgT7QjMGlell/k+4QEc7KAR8SdM+gAf0JKD/lNk5 +c6Q==
Received: by 10.50.89.233 with SMTP id br9mr6235276igb.48.1337070707868; Tue, 15 May 2012 01:31:47 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.231.209.82 with HTTP; Tue, 15 May 2012 01:31:27 -0700 (PDT)
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F23A8370E@szxeml534-mbx.china.huawei.com>
References: <4F8BE443.9050903@telecomitalia.it> <E33E01DFD5BEA24B9F3F18671078951F23A51746@szxeml534-mbx.china.huawei.com> <CA+cvDaaPktLnyJb+tqm2KW7+qA5+bNAjToK1NjmPrA3yNFfCvg@mail.gmail.com> <E33E01DFD5BEA24B9F3F18671078951F23A8370E@szxeml534-mbx.china.huawei.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Tue, 15 May 2012 01:31:27 -0700
X-Google-Sender-Auth: 6BgUvTZrGgateNuT6TNB35OoS08
Message-ID: <CA+cvDaZCtr7dY6dGG=_TBNOvbGsYAuMM7qo+DKATQGd6KAt8Eg@mail.gmail.com>
To: Songhaibin <haibin.song@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 15 May 2012 08:31:49 -0000

On Mon, May 14, 2012 at 2:24 AM, Songhaibin <haibin.song@huawei.com> wrote:
> Hi Rich,
>
>
>
>> -----Original Message-----
>> From: richard.alimi@gmail.com [mailto:richard.alimi@gmail.com] On Behalf Of
>> Richard Alimi
>> Sent: Sunday, May 13, 2012 2:05 PM
>> To: Songhaibin
>> Cc: Enrico Marocco; alto@ietf.org
>> Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11
>>
>> On Mon, Apr 23, 2012 at 6:47 PM, Songhaibin <haibin.song@huawei.com> wrote:
>> > In general, this draft is in good shape.
>> >
>> > One randomly caught problem, in Section 5.1.2.2, the ordinal mode
>> introduction, it says this cost mode is a ranking from a particular source to a set of
>> destinations. But in Section 5.2, the introduction of cost map structure, the cost
>> mode "ordinal" can be applied to m*n entries in the cost map. So I suggest to
>> modify the previous section 5.1.2.2 to make them consistent.
>> >
>>
>> Thanks for catching that. In fact, the sentence "If the Cost Mode is
>> 'ordinal', the Path Cost of each communicating pair is relative to the
>> m*n entries" can probably just be removed.
>>
>
> I'm sorry that I have a different opinion here.

No need to apologize :)

> The "ordinal" cost to entries in a matrix makes sense to me. I prefer to modify the definition in 5.1.2.2, the ranking can be from multiple sources to multiple destinations. Or is there special reason to limit it to 1*n?
>

As an author/editor, I will say that the intent was for them to be
relative to only the costs from the same source.  However, if the WG
believes that should not be he case, then please do say so.

To summarize the differences in semantics:
(a) The interpretation that an ordinal cost is relative to all other
entries in the cost map means a server could convey a policy like "I
would rather you send traffic from s1 -> d1 instead of from s2 -> d2"
(b) The interpretation that an ordinal cost is relative only to other
ordinal costs from that same source means you can't specify that
policy in an ordinal map.

The original thought was that (b) makes the protocol a bit simpler to
reason about and captures the major use cases for ordinal costs.
However, it has slightly less expressive power when it comes to
encoding policies.  It is certainly worth having the discussion as to
which way we should go.

Any other comments?

For completeness, note that we did have a discussion with regards to
whether costs had to be unique, and the decision was "no":
  http://www.ietf.org/mail-archive/web/alto/current/msg01064.html
(your question is different from that, though.)

Thanks,
Rich


> BR,
> -Haibin
>
>> Thanks,
>> Rich
>>
>> > BR,
>> > -Haibin
>> >
>> >> -----Original Message-----
>> >> From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of
>> Enrico
>> >> Marocco
>> >> Sent: Monday, April 16, 2012 5:20 PM
>> >> To: alto@ietf.org
>> >> Subject: [alto] WGLC: draft-ietf-alto-protocol-11
>> >>
>> >>
>> >> The chairs would like to declare a Working Group Last Call for
>> >> draft-ietf-alto-protocol-11, ending Friday May 11th.
>> >>
>> >> Please do review the latest version of the draft, and send any comments to
>> the
>> >> list before the expiry of WGLC so we can get this document ready for the
>> IESG.
>> >>
>> >> --
>> >> Ciao,
>> >> Enrico
>> >
>> > _______________________________________________
>> > alto mailing list
>> > alto@ietf.org
>> > https://www.ietf.org/mailman/listinfo/alto

From trammell@tik.ee.ethz.ch  Tue May 15 10:10:33 2012
Return-Path: <trammell@tik.ee.ethz.ch>
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 0944E21F89B6 for <alto@ietfa.amsl.com>; Tue, 15 May 2012 10:10:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vun-aY1I+fOR for <alto@ietfa.amsl.com>; Tue, 15 May 2012 10:10:24 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 6B0AC21F8993 for <alto@ietf.org>; Tue, 15 May 2012 10:10:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id A157AD9308; Tue, 15 May 2012 19:10:05 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id nLkNjzFFBDeC; Tue, 15 May 2012 19:10:05 +0200 (MEST)
Received: from client64-251.sdsc.edu (client64-251.sdsc.edu [132.249.64.251]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id C5D6FD930B; Tue, 15 May 2012 19:10:03 +0200 (MEST)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <CA+cvDaYsHSYLj=BwE3OzzN+vtT5mK=MWpWm7SX5LFdBbVpNuPg@mail.gmail.com>
Date: Tue, 15 May 2012 10:10:01 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD64C8C2-009E-4405-B65D-16B796BAAF09@tik.ee.ethz.ch>
References: <4FABFCEC.5070701@cisco.com> <CA+cvDaagjh49t5Zck1pj+yJq6UCibhHH+3FBWA8eioMDOsibsA@mail.gmail.com> <4FB109F9.50006@cisco.com> <CA+cvDaYsHSYLj=BwE3OzzN+vtT5mK=MWpWm7SX5LFdBbVpNuPg@mail.gmail.com>
To: Richard Alimi <rich@velvetsea.net>
X-Mailer: Apple Mail (2.1278)
X-Mailman-Approved-At: Thu, 17 May 2012 08:34:08 -0700
Cc: alto@ietf.org, ipfix-chairs@tools.ietf.org
Subject: Re: [alto] IPFIX Information Element in the ALTO protocol
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 15 May 2012 17:10:33 -0000

Hi, Rich, all,

The additions you're talking about seem on a first pass like they'd fit =
in the IPFIX information model. With respect to the definition of =
description of an Information Element, the emphasis on "flow" is really =
a historical thing. Basically, description should be specified to be =
human-readable and detailed enough that a reasonably expert person would =
know how to generate and/or interpret it. We'll remove references to =
flow from the definition of description in RFC 5102-bis.

There's a more subtle issue with potentially applying the IPFIX =
information model to ALTO: the possible need to specify an alternate =
encoding for IPFIX IEs represented in ALTO. Briefly: each IPFIX =
Information Element has a type (these cover address and time types as =
well as the basic primitives, strings, and raw octet arrays), and these =
specify encodings appropriate for using these types in IPFIX, as well: =
integers in big-endian binary, times as big-endian binary integers since =
the epoch or in NTP (era 0) format, and so on. As ALTO is JSON-based, =
these representations are somewhat less than appropriate.

Indeed, this could probably be addressed with a single specification of =
representations of IPFIX data types in ALTO (or indeed, for textual =
protocols in general). This would probably not have any surprises (v4 =
addresses in dotted-quad, v6 addresses as per RFC 4291, timestamps as =
per RFC 3339, and so on); it would just need to be written.

Best regards,

Brian

On May 14, 2012, at 12:36 PM, Richard Alimi wrote:

> On Mon, May 14, 2012 at 6:34 AM, Benoit Claise <bclaise@cisco.com> =
wrote:
>> Hi Richard,
>>=20
>> On Thu, May 10, 2012 at 10:37 AM, Benoit Claise <bclaise@cisco.com> =
wrote:
>>=20
>> Dear all,
>>=20
>> I've been reviewing draft-ietf-alto-reqs-14 and the following =
requirement
>> got me thinking:
>>=20
>>  REQ.  ARv14-5: An ALTO client protocol MUST be extensible to enable
>>   support of other host group descriptor types in future.  An ALTO
>>   client protocol specification MUST define an appropriate procedure
>>   for adding new host group descriptor types, e.g., by establishing =
an
>>   IANA registry.
>>=20
>> Why don't you reuse an existing registry, in which you will have all =
the
>> Information Elements already defined instead of defining a new one?
>> WhatI have in mind: the IPFIX I.E. IANA registry.
>> The piece of information I see in draft-ietf-alto-reqs-14 are IP =
address,
>> prefix, BGP AS: they're in IANA.
>> And many other IEs are already present, for future ALTO extensions, =
if
>> required.
>>=20
>> This would not only save one registry (ALTO Endpoint Property in
>> draft-ietf-alto-protocol-10), but offers a bigger advantage.
>> Let me explain.... When you will control your applications with ALTO, =
you
>> will anyway want to apply a flow measurement to monitor your changes, =
and to
>> serve as a feedback loop for more optimizations.
>> And the chances are high that you will using a NetFlow/IPFIX based
>> mechanism. Both NetFlow and IPFIX use the IPFIX I.E. IANA registry.
>>=20
>> Therefore, it would make sense to have consistent data models between =
ALTO
>> and IPFIX, and avoid a data model proxy if we want to compare the =
data.
>> Proposal: reuse the ElementIDs found in the IPFIX I.E. IANA registry
>> somewhere in your protocol.
>>=20
>> The suggested use case is in place of the Endpoint Property registry?
>>=20
>> I'm referring to the examples in
>> http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-7.5.3
>> So I guess it's
>> http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-10.3.
>> However, =
http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-10.3
>> doesn't contain the initial series of values.
>=20
> Those are two different things in the protocol.  The former is for
> identifying endpoints themselves, the latter is for properties
> associated with those endpoints.
>=20
>>=20
>>=20
>> Just to be sure I understand what would happen if we went that route,
>> what are the restrictions for adding new information elements?
>> Specifically, what kinds of elements are allowed or disallowed?
>>=20
>> Things that have been informally discussed in the ALTO WG so far have
>> been things like load information and available network capacity.  Do
>> those fit within the ipfix model?
>>=20
>> The IANA considerations for new IPFIX IEs is in RFC5102,
>> http://tools.ietf.org/html/rfc5102#section-7.1.
>> It mentions: IANA through Expert Review [RFC2434]
>> The most up to date document regarding IE allocation is
>> http://tools.ietf.org/html/draft-ietf-ipfix-ie-doctors-02.
>> I don't believe there are any limitations on for new IEs such as load
>> information and available network capacity.
>> Copying the IPFIX chairs and Brian Trammell.
>=20
> I think the main consideration here is whether IPFIX really is the
> canonical source (and is planned to be in the future) for data
> that an application (note: not only network operator) would want to
> know about an endpoint.  In particular, in the CDN use cases, an ALTO
> map may be provided by a CDN to advertise costs to/from and properties
> of various cache nodes.
>=20
>> =46rom RFC5102, Section 2.1 I see that a registration seems to =
enforce
> that the Information Element is derived from a flow or someone
> observing the flow on the network:
>=20
>   description - The semantics of this Information Element.  Describes
>      how this Information Element is derived from the Flow or other
>      information available to the observer.
>=20
> To me, that seems too restrictive for the ALTO model which is
> providing information to the application layer.
>=20
> Thanks,
> Rich
>=20
>>=20
>> Regards, Benoit.
>>=20
>>=20
>> Thanks,
>> Rich
>>=20
>> Disclaimer: I have not read the protocol details
>>=20
>> Regards, Benoit.
>>=20
>>=20
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>>=20
>>=20
>>=20


From haibin.song@huawei.com  Thu May 17 15:05:45 2012
Return-Path: <haibin.song@huawei.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 3FA3821F87CB for <alto@ietfa.amsl.com>; Thu, 17 May 2012 15:05:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gaKXzqOEOZFg for <alto@ietfa.amsl.com>; Thu, 17 May 2012 15:05:44 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 50A4021F87E7 for <alto@ietf.org>; Thu, 17 May 2012 15:05:44 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AGA24555; Thu, 17 May 2012 18:05:44 -0400 (EDT)
Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 17 May 2012 15:04:19 -0700
Received: from SZXEML413-HUB.china.huawei.com (10.82.67.152) by dfweml404-hub.china.huawei.com (10.193.5.203) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 17 May 2012 15:04:16 -0700
Received: from SZXEML534-MBX.china.huawei.com ([169.254.2.45]) by szxeml413-hub.china.huawei.com ([10.82.67.152]) with mapi id 14.01.0323.003; Fri, 18 May 2012 06:04:11 +0800
From: Songhaibin <haibin.song@huawei.com>
To: Richard Alimi <rich@velvetsea.net>
Thread-Topic: [alto] WGLC: draft-ietf-alto-protocol-11
Thread-Index: AQHNMM5feC2QQa8k7EKyXRG5gXrRyZbJAqQQgAD/4ICABIkz0w==
Date: Thu, 17 May 2012 22:04:10 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F23A84217@szxeml534-mbx.china.huawei.com>
References: <4F8BE443.9050903@telecomitalia.it> <E33E01DFD5BEA24B9F3F18671078951F23A51746@szxeml534-mbx.china.huawei.com> <CA+cvDaaPktLnyJb+tqm2KW7+qA5+bNAjToK1NjmPrA3yNFfCvg@mail.gmail.com> <E33E01DFD5BEA24B9F3F18671078951F23A8370E@szxeml534-mbx.china.huawei.com>, <CA+cvDaZCtr7dY6dGG=_TBNOvbGsYAuMM7qo+DKATQGd6KAt8Eg@mail.gmail.com>
In-Reply-To: <CA+cvDaZCtr7dY6dGG=_TBNOvbGsYAuMM7qo+DKATQGd6KAt8Eg@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.24.1.67]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 17 May 2012 22:05:45 -0000

________________________________________
From: alto-bounces@ietf.org [alto-bounces@ietf.org] on behalf of Richard Al=
imi [rich@velvetsea.net]
Sent: Tuesday, May 15, 2012 4:31 PM
To: Songhaibin
Cc: alto@ietf.org
Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11

On Mon, May 14, 2012 at 2:24 AM, Songhaibin <haibin.song@huawei.com> wrote:
> Hi Rich,
>
>
>
>> -----Original Message-----
>> From: richard.alimi@gmail.com [mailto:richard.alimi@gmail.com] On Behalf=
 Of
>> Richard Alimi
>> Sent: Sunday, May 13, 2012 2:05 PM
>> To: Songhaibin
>> Cc: Enrico Marocco; alto@ietf.org
>> Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11
>>
>> On Mon, Apr 23, 2012 at 6:47 PM, Songhaibin <haibin.song@huawei.com> wro=
te:
>> > In general, this draft is in good shape.
>> >
>> > One randomly caught problem, in Section 5.1.2.2, the ordinal mode
>> introduction, it says this cost mode is a ranking from a particular sour=
ce to a set of
>> destinations. But in Section 5.2, the introduction of cost map structure=
, the cost
>> mode "ordinal" can be applied to m*n entries in the cost map. So I sugge=
st to
>> modify the previous section 5.1.2.2 to make them consistent.
>> >
>>
>> Thanks for catching that. In fact, the sentence "If the Cost Mode is
>> 'ordinal', the Path Cost of each communicating pair is relative to the
>> m*n entries" can probably just be removed.
>>
>
> I'm sorry that I have a different opinion here.

No need to apologize :)

[Haibin] I only pretended to be. :)

> The "ordinal" cost to entries in a matrix makes sense to me. I prefer to =
modify the definition in 5.1.2.2, the ranking can be from multiple sources =
to multiple destinations. Or is there special reason to limit it to 1*n?
>

As an author/editor, I will say that the intent was for them to be
relative to only the costs from the same source.  However, if the WG
believes that should not be he case, then please do say so.

To summarize the differences in semantics:
(a) The interpretation that an ordinal cost is relative to all other
entries in the cost map means a server could convey a policy like "I
would rather you send traffic from s1 -> d1 instead of from s2 -> d2"
(b) The interpretation that an ordinal cost is relative only to other
ordinal costs from that same source means you can't specify that
policy in an ordinal map.

The original thought was that (b) makes the protocol a bit simpler to
reason about and captures the major use cases for ordinal costs.
However, it has slightly less expressive power when it comes to
encoding policies.  It is certainly worth having the discussion as to
which way we should go.

Any other comments?

[Haibin] I can give a use case where "option (a)" is meaningful. I think ot=
her people might give other use cases too. Assume that in CDN interconnecti=
on scenario, there are several surrogates from downstream CDN that can be i=
njected delegate contents from upstream CDN, and at the same time there are=
 a few surrogates in the upstream CDN that can provide the content. It is b=
etter to query the ALTO server do decide a path from a particuplar surrogat=
e of upstream CDN to a surrogate of downstream CDN. The ordinal costs appli=
ed to a m*n entries can be used for this decision.


For completeness, note that we did have a discussion with regards to
whether costs had to be unique, and the decision was "no":
  http://www.ietf.org/mail-archive/web/alto/current/msg01064.html
(your question is different from that, though.)

Yes. I agree with this point.

-Haibin

Thanks,
Rich


> BR,
> -Haibin
>
>> Thanks,
>> Rich
>>
>> > BR,
>> > -Haibin
>> >
>> >> -----Original Message-----
>> >> From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf =
Of
>> Enrico
>> >> Marocco
>> >> Sent: Monday, April 16, 2012 5:20 PM
>> >> To: alto@ietf.org
>> >> Subject: [alto] WGLC: draft-ietf-alto-protocol-11
>> >>
>> >>
>> >> The chairs would like to declare a Working Group Last Call for
>> >> draft-ietf-alto-protocol-11, ending Friday May 11th.
>> >>
>> >> Please do review the latest version of the draft, and send any commen=
ts to
>> the
>> >> list before the expiry of WGLC so we can get this document ready for =
the
>> IESG.
>> >>
>> >> --
>> >> Ciao,
>> >> Enrico
>> >
>> > _______________________________________________
>> > alto mailing list
>> > alto@ietf.org
>> > https://www.ietf.org/mailman/listinfo/alto
_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto=

From sabine.randriamasy@alcatel-lucent.com  Mon May 21 08:12:27 2012
Return-Path: <sabine.randriamasy@alcatel-lucent.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 0E99221F867A for <alto@ietfa.amsl.com>; Mon, 21 May 2012 08:12:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.835
X-Spam-Level: 
X-Spam-Status: No, score=-3.835 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b0NXZZbcgxeJ for <alto@ietfa.amsl.com>; Mon, 21 May 2012 08:12:25 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by ietfa.amsl.com (Postfix) with ESMTP id DF3AB21F8678 for <alto@ietf.org>; Mon, 21 May 2012 08:12:23 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q4LFCMV0007247 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 21 May 2012 17:12:22 +0200
Received: from [172.27.204.75] (135.120.57.7) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 21 May 2012 17:12:00 +0200
Message-ID: <4FBA5B39.8040505@alcatel-lucent.com>
Date: Mon, 21 May 2012 17:11:53 +0200
From: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Richard Alimi <rich@velvetsea.net>
References: <4F8BE443.9050903@telecomitalia.it> <4FAD5745.2060009@alcatel-lucent.com> <CA+cvDab3P0-68m6+mZ+4K0FedJ7_MK6SGXhD2kQKupXuCDLgDw@mail.gmail.com>
In-Reply-To: <CA+cvDab3P0-68m6+mZ+4K0FedJ7_MK6SGXhD2kQKupXuCDLgDw@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 21 May 2012 15:12:27 -0000

Hi Rich,


Richard Alimi a écrit :
> On Fri, May 11, 2012 at 11:15 AM, Sabine Randriamasy
> <Sabine.Randriamasy@alcatel-lucent.com> wrote:
>   
>> Hi all,
>>
>> Below is my review of document "draft-ietf-alto-protocol-11.txt". At least
>> Part I, until section 7.7.3.1.5 included. I will send Part II in a couple of
>> hours.
>>
>> Thanks,
>> Sabine
>>
>> ===============================================================================================
>>
>>
>> Document: draft-ietf-alto-protocol-11.txt
>> Title: ALTO Protocol
>> Reviewer: Sabine Randriamasy
>> Review Date: May 11, 2012
>> Part I
>>
>> -----------------------------------------------------
>> GENERAL COMMENTS
>> -----------------------------------------------------
>>
>> This document seems geared towards P2P applications, although the abstract
>> mentions CDN and "those that have a choice in connection endpoints". In some
>> places, see detailed comments, "peer" should be replaced by "endpoints" when
>> referring to a content location. In Section 8 Use Cases, some text should be
>> added to recall this.
>>     
>
> Yes - that sounds reasonable.  We'll do a search for the word 'peer'
> to see if a better term can be used, and also add a reminder in the
> use cases that P2P is not the only deployment setting.
>
>   
>> There was a discussion on whether to specify the MUST of the protocol. Is it
>> possible to have a section listing the MUST of the protocol specified in
>> this document?
>>     
>
> I don't recall this discussion - do you have a pointer?
>
> If I'm understanding the proposal correctly, I am concerned about how
> much duplicate information that would generate.  Is there an example
> RFC you could reference that does this?
>   
I remember there was a discussion on the list and also in Quebec that 
was on specifying the features that the ALTO MUST have. My question here 
was rather on the possibility listing the MUST identified in the doc. I 
don't have any reference of RFC doing this and as it may generate 
duplicate information then it seems preferable not to do it.
>   
>> -----------------------------------------------------
>> DETAILED COMMENTS
>> -----------------------------------------------------
>>
>> Section 1.1 Background and Problem Statement
>>
>> A couple of additional explanations would help better positioning and
>> motivating ALTO. For example:
>>
>> - § 1 after 1st sentence "Today, network information available to
>> applications is mostly from
>> the view of endhosts.": I suggest to add 1 or 2 sentences on what is wrong
>> with this, e.g. the fact that overlay based endpoint choice leads to
>> uselessly use expensive links and lower performance due to too long paths.
>>     
>
> We can add something there. A better way to phrase this might be that
> a view only from the view of the endhosts makes it
> difficult/impossible to be aware of policies or properties of the
> overall network topology.
>   
Yes, thanks
>   
>> - §1, 2nd sentence "There is no clear mechanism to convey information about
>> the network (e.g., preferences) to applications": could be specified by
>> saying that some sparse tools may exist but there is a need to have a
>> generic and standardized mechanism accessible to all.
>>     
>
> Just to be sure I understand, which specific tools were you thinking
> about here?  BGP looking glasses or whois?  Or others?
>   
I'd say both and other related such as *ClosestNode.com or others 
examples you may have in mind.
*
>   
>> - §2last sentence "The mechanism should include abstractions to achieve
>> concise, flexible network information expression.": is it the only
>> motivation for abstraction or does abstraction also serve other purposes
>> such as security/privacy for ISPs?
>>     
>
> I would tend to keep the security/privacy issue out of the
> introduction when we are motivating the protocol.  These are
> requirements that should (I believe, anyways) already be handled in
> the Discussion section of this document and in the requirements
> document.
>   
Ok
>   
>> Section 1.3.1 Service Providers
>> This section is hard to understand without a hint on what kind of
>> information is provided by ALTO. I suggest to add a sentence including
>> abstracted network maps, asociated costs between the locations of the map or
>> specific properties or access costs to these locations.
>>     
>
> I'll see what we can do to add a small hint in here without going into detail.
>   
Sure. It's just that 2 or 3 lines with basic Alto services would make 
the reading more comfortable.
>   
>> - in 1st sentence: "... the peer selection process ... " ==> "peer" shoud be
>> replaced by "connection endpoints such as peers"
>>     
>
> Ack.
>
>   
>> Section 2.1 Terminology
>>
>> - in §2: the term "Endpoint" should be added
>> - a first section "2.1.X Endpoint" should be inserted before section 2.1.1
>> Endpoint Address to better introduce Endpoint Adress and Network Location
>> mentioning "Endpoint" with no prior definition.
>>     
>
> Ack - we'll add this.
>
>   
>> Section 2.2 ALTO Service and Protocol Scope
>> - §3 "... The ALTO Information provided by the ALTO Server can be updated
>> dynamically based on network conditions ...": a sentence would be good here
>> to recall that ALTO does by no means replace real time network performance
>> measurement services.
>>     
>
> Do you instead mean ~real-time congestion control protocols?  If so,
> we can add a reminder.
>   
yes, sorry for the confusing phrasing.
>   
>> Section 3 Protocol Structure
>> - §3 3rd sentence "ALTO-Core provides the Map Service, which provides the
>> core ALTO informtion to
>> clients". The term "ALTO-Core" should be introduced ans besides it does not
>> appear again in the document.
>>     
>
> Actually, I think the term can just be dropped at this point. (Let me
> know if anyone disagrees)
>   
Ok
>   
>> Also replace "informtion" ==> "information".
>>     
>
> Ack.
>
>   
>> Section 4 Network Map
>> - §2: "The Network Location endpoint property": i suggest "The Network
>> Location Endpoint Property"
>>
>>
>> Section 7.2.1 Discovering Information Resources
>> - §1 "To discover available resources, an ALTO Client may request the
>> Information Resource Directory": what are other means? There seem to be a
>> contradiction with Section 6.2 Protocol design where item "o Information
>> Resource Directory" says that "This directory is the single entry point to
>> an ALTO Service."
>>     
>
> Does changing it from
>   "an ALTO Client may request ... "
> to
>   "an ALTO Client requests... "
> clear this up?
>   
yes
>   
>> Section 7.2.7 Parsing
>> - last sentence "ALTO implementations MUST ignore...": i suggest an
>> insertion: "base protocol ALTO implementations MUST ignore...", or if it has
>> been previously defined, the term "ALTO-core" could be used here.
>>     
>
> The advice is common to any ALTO implementation, even one that is
> supporting an extension.  If an implementation is supporting an
> extension, then those fields are no longer "unknown".
>   
Ok
> If that still isn't clear, do you have an alternate suggestion on the wording?
>   
We can leave the initial sentence
>   
>> Section 7.4 ALTO Errors
>> - §3 2nd sentence: "... information about the why a particular ...": i
>> suggest to remove "the" => "... information about why a particular ..."
>>     
>
> Ack - thanks.
>
>   
>> Section 7.4.1 Media Type
>> "... The media type for an Error Resource ...": does it mean "The media type
>> for an ALTO Error Resource" ?
>>
>>     
>
> Yes - we'll make that more precise.
>
>   
>> Section 7.4.2
>> - 1st sentence "An Error Resource has the format:": is the answer to my
>> previous question is yes, then "An ALTO ALTO Error Resource has the format:"
>> reads easier.
>>
>>     
>
> Ack - I'll just avoid the extra 'ALTO' when updating the text :)
>   
Ok :-)
>   
>> Section 7.4.3 Error Codes
>> - §2 last sentence: "... Table 1in the HTTP response." : blank space is
>> needed after "1" ==> "... Table 1 in the HTTP response."
>>
>>     
>
> Ack.
>
>   
>> Section 7.6.2 Encoding
>> - §3 1st sentence "Any URI ... the format of an Information Resource
>> Directory.": i suggest to append "request" ==> "Any URI ... the format of an
>> Information Resource Directory request."
>>     
>
> Ack.
>
>   
>> - §4 - item "capabilities": i didin't understand the sentence "or assume its
>> default value", although the protocol is not expected to guide the ALTO
>> Client's behavior.
>>     
>
> Each capability should have a default value documented in this
> specification - the text here is only indicating that the client
> should fall back to that value.  Does that answer the question?
>   
Yes. Then how about saying "or assume its default value that SHOULD be 
documented in this specification"
> Note to self: "empty array" -> "empty object" in this paragraph
>
>   
>> Section 7.6.3 Example
>>
>> In the first IRD example the last URI called
>> "http://alto.example.com/endpointcost/lookup" includes the following
>> capabilities:
>>
>> "cost-modes" : [ "ordinal", "numerical" ],
>> "cost-types" : [ "routingcost", "hopcount" ]
>>
>> In the second example listing URIs available in a subdomain, we have the
>> same capabilities for the URI called
>> "http://custom.alto.example.com/costmap/filtered"
>>
>> There is a need for the ALTO Server to disambiguate this encoding. As an
>> ALTO client, I don't know how to figure what Cost Mode is applied
>> respectively to the Cost Type "routingcost" and "hopcount". Is it both modes
>> for each cost type?
>>
>>
>> Also, as a server, how do I encode that for example "routingcost" is
>> available in both "ordinal" and "numerical" modes and "hopcount" in
>> "numerical" only? I guess separate URIs would be the way...
>>     
>
> Section 7.7.1.2.4. says:
>    An ALTO Server MUST support all of the Cost Types listed here for
>    each of the listed Cost Modes.  Note that an ALTO Server may provide
>    multiple Cost Map Information Resources, each with different
>    capabilities.
>
> Does that answer both questions?
>   
If the conclusion of this text for the example IRD is that 'routingcost' 
and 'hopcount' are each available for both 'numerical' and 'ordinal' 
mode, then, as § 7.7.1.2.4 comes after the IRD example, I think that 
things would be completely clear if § 7.6.3 would include an 
illustrative sentence like, "In this example, the ALTO server provides 
the Endpoint Cost Service for Cost Types 'routingcost' and 'hopcount', 
each available for both 'numerical' and 'ordinal' mode".

As for my 2nd question, I understand that for the mentionned case, the 
IRD then must include 2 URIs: one for 'routingcost' and the other for 
'hopcount'.
>   
>> Section 7.7.1.2.4 Capabilities
>>
>> - Object CostMapCapability has member "CostType cost-types<0..*>;". the
>> description says: "If not present, this member MUST be interpreted as an
>> empty array." On the other hand, Section 7.7.1.2 Cost Map in its §1 says
>> "This resource MUST be provided for at least the ’routingcost’ Cost Type and
>> ’numerical’ Cost Mode."
>> So would "CostType cost-types<1..*>" be more consistent?
>> Likewise, as the 'numerical' mode MUST be available, why not have CostMode
>> cost-modes<1..*> ?
>>     
>
> There are valid cases for them being empty. Specifically, this can
> happen if the server generating the Information Resource Directory is
> not authoritative as to what capabilities are supported.  See 7.6.3
> for an example.
>   
Ok
> Each cost-map endpoint need not support the routingcost type - an ALTO
> Service must do so.
>   
Ok
>   
>> See also §7.7.3.1.3 Input Parameters, where encoding "EndpointProperty
>> properties<1..*>" is used, because 'pid' MUST be available.
>>     
>
> Do you mean "EndpointProperty prop-types<0..*>;" instead?
>   
Yes, the error is on my side, there was a confusion with §7.7.3.1.4 
Capabilities.
> This has a similar reasoning to the above for cost maps.
>   
Ok
>   
>> Section 7.7.2.2.3 Input Parameters
>> - item "constraints" use term "numerical cost". Onthe other hand, Section
>> 7.7.2.4.4 Capabilities in its item "cost-constraints" says (last sentence)
>> "... constraints may not have the intended effect for cost maps with the
>> ’ordinal’ Cost Mode... ".
>> Although it intuitively make more sens to have constraints on numerical
>> values, one may imagine that for some reasons an application clien may look
>> for alternative paths that have a poorer rank but not worse that a given
>> value and accordingly encode a constraint on 'ordinal' costs.
>> Therefore, I suggest to use term "cost value" instead of "numerical cost".
>>     
>
> Agree. that should not explicitly mention numerical costs in the
> documentation for constraints.  Good catch.
>
>   
>> Section 7.7.3.1.3 Input Parameters
>> - §1 2nd sentence: "... data format of input parameteres...": typo ==> "...
>> data format of input parameters..."
>> - item "properties": "List of endpoint properties to returned... " i suggest
>> "List of endpoint properties to be returned... ".
>>     
>
> Ack.
>
>   
>> I also suggest to add that
>> property 'pid' MUST be provided.
>>     
>
> That is already noted in 7.7.3.1 right?  Note that a particular URI
> need not provide the 'pid' property - the ALTO Service as a whole
> needs to do so.
>
> This seems worth clarifying - I'll add a note to do that.
>   
Thanks
>   
>> Section 7.7.3.1.4 Capabilities
>> - object "EndpointPropertyCapability;" has a member "EndpointProperty
>> prop-types<0..*>". As 'pid' MUST be provided why not encode as
>> "EndpointProperty prop-types<1..*>" ?
>>     
>
> Same as the response above, I believe.
>   
Yes, again, my confusion.
>   
>> -----------------------------------------------------
>> NITS
>> -----------------------------------------------------
>>
>> Abstract
>> - §3: ".... be provided by the network ..." => I suggest ".... be provided
>> by the network operator ..." or any applicable term
>>
>>
>> Section 1.1 Background and Problem Statement
>> - 2nd sentence "... about the network ..." => I suggest "... about the
>> network infrastructure ..."
>>
>>
>> Section 2.1 Terminology
>> - the typography should be harmonized between "endpoint address" and
>> "Endpoint Address".
>>
>> Section 2.2 ALTO Service and Protocol Scope
>>
>> - §1 last sentence: "... deployment scenario and discovery mechanism ..."
>> ==> I suggest to complete as follows "... ALTO deployment scenario and ALTO
>> service discovery mechanism ..."
>> - §2 1st sentence: "... the overall system architecture ..." ==> I suggest
>> "the overall ALTO system architecture"
>> - §4 last sentence: "... figure for completeness but outside ..." ==> I
>> suggest "... figure for completeness but are outside ..."
>>
>>
>> Section 3 Protocol Structure
>> - §3: i suggest to replace "functionality" by "functionalities"
>>
>>
>> Section 3.1.1 Map Service
>> - §1: replace "endpoints" by "Endpoints"
>>
>>
>> Section 7.4 ALTO Errors
>> - §3 2nd sentence: "... information about the why a particular ...": i
>> suggest to remove "the" => "... information about why a particular ..."
>>
>>     
>
> Ack.
>
> Thanks!
> Rich
>
>   
>> Enrico Marocco a écrit :
>>
>>     
>>> The chairs would like to declare a Working Group Last Call for
>>> draft-ietf-alto-protocol-11, ending Friday May 11th.
>>>
>>> Please do review the latest version of the draft, and send any comments
>>> to the list before the expiry of WGLC so we can get this document ready
>>> for the IESG.
>>>
>>>
>>>       
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>>     


From sabine.randriamasy@alcatel-lucent.com  Mon May 21 09:12:21 2012
Return-Path: <sabine.randriamasy@alcatel-lucent.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 3C68021F858A for <alto@ietfa.amsl.com>; Mon, 21 May 2012 09:12:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.892
X-Spam-Level: 
X-Spam-Status: No, score=-5.892 tagged_above=-999 required=5 tests=[AWL=2.057,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MANGLED_LIST=2.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rqP0OsuMk+sp for <alto@ietfa.amsl.com>; Mon, 21 May 2012 09:12:19 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by ietfa.amsl.com (Postfix) with ESMTP id 7432921F8597 for <alto@ietf.org>; Mon, 21 May 2012 09:12:19 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q4LGCH2S021277 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 21 May 2012 18:12:17 +0200
Received: from [172.27.204.75] (135.120.57.7) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (135.120.45.62) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 21 May 2012 18:12:17 +0200
Message-ID: <4FBA6959.8050404@alcatel-lucent.com>
Date: Mon, 21 May 2012 18:12:09 +0200
From: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Richard Alimi <rich@velvetsea.net>
References: <4F8BE443.9050903@telecomitalia.it> <4FAD5745.2060009@alcatel-lucent.com> <4FAD9DEF.3070500@alcatel-lucent.com> <CA+cvDaauTRrzSn3g_966PWyDMLvAWJxA4=g6RZLjm-W0y+_iiA@mail.gmail.com>
In-Reply-To: <CA+cvDaauTRrzSn3g_966PWyDMLvAWJxA4=g6RZLjm-W0y+_iiA@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WGLC: draft-ietf-alto-protocol-11 - Part II + Part I
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Mon, 21 May 2012 16:12:21 -0000

Hi Rich,

below are my answers to your feedback on part 2
Thanks
Sabine


Richard Alimi a écrit :
> Oops - I replied to the Part 1 email separately. I'll keep this one
> focused on Part 2 and trim the rest from the reply to avoid confusion.
>
> On Fri, May 11, 2012 at 4:17 PM, Sabine Randriamasy
> <Sabine.Randriamasy@alcatel-lucent.com> wrote:
>   
>> -----------------------------------------------------
>> DETAILED COMMENTS
>> -----------------------------------------------------
>>
>> Section 7.7.3.1.5 Response
>> - §3 describing InfoResourceEndpointProperty: last sentence "... property
>> values encoded as JSON Strings". Encoding property values as JSON strings
>> may be too restrictive. It may as well be a constant number, or an array.
>> Why not a JSON Value?
>>     
>
> I don't have a problem with making this a JSON Value for extensibility
> and adopting similar text that we did for cost values (basically,
> those implementing the base specification should validate that they
> are strings).  If someone feels like we shouldn't do that, then please
> speak up soon :)
>
>   
>> - §5 "If the ALTO Server does not define a requested property for a
>> particular endpoint, then it MUST omit it from the response for only that
>> endpoint.": does this mean that the corresponding pair {"prop-type":
>> prop-type-value} does not appear in the array of EndpointProperty objects
>> associated to this endpoint?
>>     
>
> Yes.  If it was unclear, feel free to provide alternate text to clarify it.
>   
Replacing it with the sentence you propose below is fine.
>   
>> If an ALTO server defines a property for an endpoint but no value, what
>> happens? Is simply the prop-type-value omitted?
>>     
>
> I would have considered this to be the same as not having the property
> defined for that endpoint.  Would the following text make it more
> clear?
>
> "If the ALTO Server does not define a value for a requested property
> for a particular endpoint, then it MUST omit it .. "
>   
Yes, adding the term value clarifies the sentence.
>   
>> Section 7.7.3.1.6 Example
>> An example of request/response with several properties would be good here.
>>
>>     
>
> Makes sense - we can add that.
>
>   
>> Section 7.7.4.1.5 Response
>> - § of description of member "EndpointCostMapData" sentence "An
>> implementation of the
>> protocol in this document SHOULD assume that the cost is a JSONNumber ... ":
>> I suggest using "cost value" rather than "cost". Same for sentence "If the
>> ALTO Server does not define a cost from ..."
>>     
>
> Sounds good to me.
>
>   
>> Section 8 Use Cases
>> There should be a couple of sentences recalling that ALTO supports a wider
>> range of applications, namely "those that have a choice in connection
>> endpoints" as said in Abstract although the use cases focus on P2P.
>>     
>
> Ack.
>
>   
>> Section 8.1 ALTO ALTO Client Embedded in P2P Tracker
>> - §1 1st sentence "Many P2P currently-deployed P2P systems... ": ==>  "Many
>> currently-deployed P2P systems... "
>>
>>     
>
> Ack.
>
>   
>> Section 9.4 Mapping IPs to ASNs
>> - §4: The mapping could also be done for Endpoints and ASN be an Endpoint
>> Property.
>>
>>     
>
> Yes  - that is also a possibility.  We can mention this.
>
>   
>> -----------------------------------------------------
>> NITS & TYPOS
>> -----------------------------------------------------
>>
>>
>> Section 9.3
>> - §2 1st sentence "The protocol specified ... (i.e., the the Endpoint Cost
>> Service) ... " ==> remove one of the 2 "the"
>>
>>
>> Section 10.1 application/alto-* Media Types
>> - item "Published specification", last part "... see Table 2for ..." : blank
>> space needed ==> "... see Table 2 for ..."
>>     
>
> Ack.
>
> Thanks for the review!
> Rich
>
>   
>>
>> Sabine Randriamasy a écrit :
>>     
>>> Hi all,
>>>
>>> Below is my review of document "draft-ietf-alto-protocol-11.txt". At
>>> least Part I, until section 7.7.3.1.5 included. I will send Part II in a
>>> couple of hours.
>>>
>>> Thanks,
>>> Sabine
>>>
>>>
>>> ===============================================================================================
>>>
>>>
>>> Document: draft-ietf-alto-protocol-11.txt
>>> Title: ALTO Protocol
>>> Reviewer: Sabine Randriamasy
>>> Review Date: May 11, 2012
>>> Part I
>>>
>>> -----------------------------------------------------
>>> GENERAL COMMENTS
>>> -----------------------------------------------------
>>>
>>> This document seems geared towards P2P applications, although the
>>> abstract mentions CDN and "those that have a choice in connection
>>> endpoints". In some places, see detailed comments, "peer" should be
>>> replaced by "endpoints" when referring to a content location. In Section
>>> 8 Use Cases, some text should be added to recall this.
>>>
>>> There was a discussion on whether to specify the MUST of the protocol.
>>> Is it possible to have a section listing the MUST of the protocol
>>> specified in this document?
>>>
>>> -----------------------------------------------------
>>> DETAILED COMMENTS
>>> -----------------------------------------------------
>>>
>>> Section 1.1 Background and Problem Statement
>>>
>>> A couple of additional explanations would help better positioning and
>>> motivating ALTO. For example:
>>>
>>> - § 1 after 1st sentence "Today, network information available to
>>> applications is mostly from
>>> the view of endhosts.": I suggest to add 1 or 2 sentences on what is
>>> wrong with this, e.g. the fact that overlay based endpoint choice leads
>>> to uselessly use expensive links and lower performance due to too long
>>> paths.
>>> - §1, 2nd sentence "There is no clear mechanism to convey information
>>> about the network (e.g., preferences) to applications": could be
>>> specified by saying that some sparse tools may exist but there is a need
>>> to have a generic and standardized mechanism accessible to all.
>>> - §2last sentence "The mechanism should include abstractions to achieve
>>> concise, flexible network information expression.": is it the only
>>> motivation for abstraction or does abstraction also serve other purposes
>>> such as security/privacy for ISPs?
>>>
>>>
>>> Section 1.3.1 Service Providers
>>> This section is hard to understand without a hint on what kind of
>>> information is provided by ALTO. I suggest to add a sentence including
>>> abstracted network maps, asociated costs between the locations of the
>>> map or specific properties or access costs to these locations.
>>>
>>> - in 1st sentence: "... the peer selection process ... " ==> "peer"
>>> shoud be replaced by "connection endpoints such as peers"
>>>
>>>
>>> Section 2.1 Terminology
>>>
>>> - in §2: the term "Endpoint" should be added
>>> - a first section "2.1.X Endpoint" should be inserted before section
>>> 2.1.1 Endpoint Address to better introduce Endpoint Adress and Network
>>> Location mentioning "Endpoint" with no prior definition.
>>>
>>>
>>> Section 2.2 ALTO Service and Protocol Scope
>>> - §3 "... The ALTO Information provided by the ALTO Server can be
>>> updated dynamically based on network conditions ...": a sentence would
>>> be good here to recall that ALTO does by no means replace real time
>>> network performance measurement services.
>>>
>>>
>>> Section 3 Protocol Structure
>>> - §3 3rd sentence "ALTO-Core provides the Map Service, which provides
>>> the core ALTO informtion to
>>> clients". The term "ALTO-Core" should be introduced ans besides it does
>>> not appear again in the document.
>>> Also replace "informtion" ==> "information".
>>>
>>>
>>> Section 4 Network Map
>>> - §2: "The Network Location endpoint property": i suggest "The Network
>>> Location Endpoint Property"
>>>
>>>
>>> Section 7.2.1 Discovering Information Resources
>>> - §1 "To discover available resources, an ALTO Client may request the
>>> Information Resource Directory": what are other means? There seem to be
>>> a contradiction with Section 6.2 Protocol design where item "o
>>> Information Resource Directory" says that "This directory is the single
>>> entry point to an ALTO Service."
>>>
>>>
>>> Section 7.2.7 Parsing
>>> - last sentence "ALTO implementations MUST ignore...": i suggest an
>>> insertion: "base protocol ALTO implementations MUST ignore...", or if it
>>> has been previously defined, the term "ALTO-core" could be used here.
>>>
>>>
>>> Section 7.4 ALTO Errors
>>> - §3 2nd sentence: "... information about the why a particular ...": i
>>> suggest to remove "the" => "... information about why a particular ..."
>>>
>>>
>>> Section 7.4.1 Media Type
>>> "... The media type for an Error Resource ...": does it mean "The media
>>> type for an ALTO Error Resource" ?
>>>
>>>
>>> Section 7.4.2
>>> - 1st sentence "An Error Resource has the format:": is the answer to my
>>> previous question is yes, then "An ALTO ALTO Error Resource has the
>>> format:" reads easier.
>>>
>>>
>>> Section 7.4.3 Error Codes
>>> - §2 last sentence: "... Table 1in the HTTP response." : blank space is
>>> needed after "1" ==> "... Table 1 in the HTTP response."
>>>
>>>
>>> Section 7.6.2 Encoding
>>> - §3 1st sentence "Any URI ... the format of an Information Resource
>>> Directory.": i suggest to append "request" ==> "Any URI ... the format
>>> of an Information Resource Directory request."
>>> - §4 - item "capabilities": i didin't understand the sentence "or assume
>>> its default value", although the protocol is not expected to guide the
>>> ALTO Client's behavior.
>>>
>>>
>>>
>>> Section 7.6.3 Example
>>>
>>> In the first IRD example the last URI called
>>> "http://alto.example.com/endpointcost/lookup" includes the following
>>> capabilities:
>>>
>>> "cost-modes" : [ "ordinal", "numerical" ],
>>> "cost-types" : [ "routingcost", "hopcount" ]
>>>
>>> In the second example listing URIs available in a subdomain, we have the
>>> same capabilities for the URI called
>>> "http://custom.alto.example.com/costmap/filtered"
>>>
>>> There is a need for the ALTO Server to disambiguate this encoding. As an
>>> ALTO client, I don't know how to figure what Cost Mode is applied
>>> respectively to the Cost Type "routingcost" and "hopcount". Is it both
>>> modes for each cost type?
>>>
>>> Also, as a server, how do I encode that for example "routingcost" is
>>> available in both "ordinal" and "numerical" modes and "hopcount" in
>>> "numerical" only? I guess separate URIs would be the way...
>>>
>>>
>>> Section 7.7.1.2.4 Capabilities
>>>
>>> - Object CostMapCapability has member "CostType cost-types<0..*>;". the
>>> description says: "If not present, this member MUST be interpreted as an
>>> empty array." On the other hand, Section 7.7.1.2 Cost Map in its §1 says
>>> "This resource MUST be provided for at least the ’routingcost’ Cost Type
>>> and ’numerical’ Cost Mode."
>>> So would "CostType cost-types<1..*>" be more consistent?
>>> Likewise, as the 'numerical' mode MUST be available, why not have
>>> CostMode cost-modes<1..*> ?
>>> See also §7.7.3.1.3 Input Parameters, where encoding "EndpointProperty
>>> properties<1..*>" is used, because 'pid' MUST be available.
>>>
>>>
>>> Section 7.7.2.2.3 Input Parameters
>>> - item "constraints" use term "numerical cost". Onthe other hand,
>>> Section 7.7.2.4.4 Capabilities in its item "cost-constraints" says (last
>>> sentence) "... constraints may not have the intended effect for cost
>>> maps with the ’ordinal’ Cost Mode... ".
>>> Although it intuitively make more sens to have constraints on numerical
>>> values, one may imagine that for some reasons an application clien may
>>> look for alternative paths that have a poorer rank but not worse that a
>>> given value and accordingly encode a constraint on 'ordinal' costs.
>>> Therefore, I suggest to use term "cost value" instead of "numerical cost".
>>>
>>>
>>> Section 7.7.3.1.3 Input Parameters
>>> - §1 2nd sentence: "... data format of input parameteres...": typo ==>
>>> "... data format of input parameters..."
>>> - item "properties": "List of endpoint properties to returned... " i
>>> suggest "List of endpoint properties to be returned... ". I also suggest
>>> to add that property 'pid' MUST be provided.
>>>
>>>
>>> Section 7.7.3.1.4 Capabilities
>>> - object "EndpointPropertyCapability;" has a member "EndpointProperty
>>> prop-types<0..*>". As 'pid' MUST be provided why not encode as
>>> "EndpointProperty prop-types<1..*>" ?
>>>
>>>
>>>
>>> -----------------------------------------------------
>>> NITS
>>> -----------------------------------------------------
>>>
>>> Abstract
>>> - §3: ".... be provided by the network ..." => I suggest ".... be
>>> provided by the network operator ..." or any applicable term
>>>
>>>
>>> Section 1.1 Background and Problem Statement
>>> - 2nd sentence "... about the network ..." => I suggest "... about the
>>> network infrastructure ..."
>>>
>>>
>>> Section 2.1 Terminology
>>> - the typography should be harmonized between "endpoint address" and
>>> "Endpoint Address".
>>>
>>>
>>> Section 2.2 ALTO Service and Protocol Scope
>>>
>>> - §1 last sentence: "... deployment scenario and discovery mechanism
>>> ..." ==> I suggest to complete as follows "... ALTO deployment scenario
>>> and ALTO service discovery mechanism ..."
>>> - §2 1st sentence: "... the overall system architecture ..." ==> I
>>> suggest "the overall ALTO system architecture"
>>> - §4 last sentence: "... figure for completeness but outside ..." ==> I
>>> suggest "... figure for completeness but are outside ..."
>>>
>>>
>>> Section 3 Protocol Structure
>>> - §3: i suggest to replace "functionality" by "functionalities"
>>>
>>>
>>> Section 3.1.1 Map Service
>>> - §1: replace "endpoints" by "Endpoints"
>>>
>>>
>>> Section 7.4 ALTO Errors
>>> - §3 2nd sentence: "... information about the why a particular ...": i
>>> suggest to remove "the" => "... information about why a particular ..."
>>>
>>>
>>>
>>> Enrico Marocco a écrit :
>>>
>>>       
>>>> The chairs would like to declare a Working Group Last Call for
>>>> draft-ietf-alto-protocol-11, ending Friday May 11th.
>>>>
>>>> Please do review the latest version of the draft, and send any comments
>>>> to the list before the expiry of WGLC so we can get this document ready
>>>> for the IESG.
>>>>
>>>>
>>>>
>>>>         
>>> _______________________________________________
>>> alto mailing list
>>> alto@ietf.org
>>> https://www.ietf.org/mailman/listinfo/alto
>>>
>>>       
>> --
>>
>> ---------------------------------------------------------
>> Sabine RANDRIAMASY Alcatel-Lucent Bell Labs France Centre de Villarceau
>> Route de Villejust - 91620 NOZAY - FRANCE
>>
>> E-MAIL : Sabine.Randriamasy@alcatel-lucent.com
>> TEL: +33 (0)1 30 77 27 45         (On Net) 2 103 27 45
>> ---------------------------------------------------------
>>
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>>     


From internet-drafts@ietf.org  Tue May 29 06:32:52 2012
Return-Path: <internet-drafts@ietf.org>
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 EC27421F8793; Tue, 29 May 2012 06:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.363
X-Spam-Level: 
X-Spam-Status: No, score=-102.363 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OaCUcw3qbkPv; Tue, 29 May 2012 06:32:52 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CF0521F871C; Tue, 29 May 2012 06:32:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.02
Message-ID: <20120529133252.24692.74427.idtracker@ietfa.amsl.com>
Date: Tue, 29 May 2012 06:32:52 -0700
Cc: alto@ietf.org
Subject: [alto] I-D Action: draft-ietf-alto-reqs-15.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 29 May 2012 13:32:53 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Application-Layer Traffic Optimizatio=
n Working Group of the IETF.

	Title           : Application-Layer Traffic Optimization (ALTO) Requiremen=
ts
	Author(s)       : Sebastian Kiesel
                          Stefano Previdi
                          Martin Stiemerling
                          Richard Woundy
                          Yang Richard Yang
	Filename        : draft-ietf-alto-reqs-15.txt
	Pages           : 24
	Date            : 2012-05-29

   Many Internet applications are used to access resources, such as
   pieces of information or server processes that are available in
   several equivalent replicas on different hosts.  This includes, but
   is not limited to, peer-to-peer file sharing applications.  The goal
   of Application-Layer Traffic Optimization (ALTO) is to provide
   guidance to applications that have to select one or several hosts
   from a set of candidates capable of providing a desired resource.
   This guidance shall be based on parameters that affect performance
   and efficiency of the data transmission between the hosts, e.g., the
   topological distance.  The ultimate goal is to improve performance or
   Quality of Experience in the application while reducing the
   utilization of the underlying network infrastructure.

   This document enumerates requirements for specifying, assessing, or
   comparing protocols and implementations.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-alto-reqs-15.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-alto-reqs-15.txt

The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-alto-reqs/


From enrico.marocco@telecomitalia.it  Wed May 30 07:21:33 2012
Return-Path: <enrico.marocco@telecomitalia.it>
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 09BC521F8685 for <alto@ietfa.amsl.com>; Wed, 30 May 2012 07:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.472
X-Spam-Level: 
X-Spam-Status: No, score=-101.472 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245,  RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ui+9OHHNwnBZ for <alto@ietfa.amsl.com>; Wed, 30 May 2012 07:21:32 -0700 (PDT)
Received: from GRFEDG702RM001.telecomitalia.it (grfedg702rm001.telecomitalia.it [217.169.121.21]) by ietfa.amsl.com (Postfix) with ESMTP id 0730C21F86A1 for <alto@ietf.org>; Wed, 30 May 2012 07:21:32 -0700 (PDT)
Received: from grfhub703rm001.griffon.local (10.19.3.10) by GRFEDG702RM001.telecomitalia.it (10.173.88.21) with Microsoft SMTP Server (TLS) id 8.3.245.1; Wed, 30 May 2012 16:21:27 +0200
Received: from MacLab.local (10.229.8.27) by smtp.telecomitalia.it (10.19.9.236) with Microsoft SMTP Server (TLS) id 8.3.245.1; Wed, 30 May 2012 16:21:26 +0200
Message-ID: <4FC62CE6.6050002@telecomitalia.it>
Date: Wed, 30 May 2012 16:21:26 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "alto@ietf.org" <alto@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms060806040907060701030807"
X-TI-Disclaimer: Disclaimer1
Subject: [alto] Progress of draft-ietf-alto-reqs
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 30 May 2012 14:21:33 -0000

--------------ms060806040907060701030807
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,

this is to inform everyone that the draft has undergone a first IESG
review and has been updated a few times to address all the comments
received. The current version is now
http://tools.ietf.org/html/draft-ietf-alto-reqs-15

Most of the changes were clarifications, except a substantial one
consisting with the addition of one new requirement, that basically
reflects IESG guidelines for ops support in new protocols:

   REQ.  ARv15-2: An ALTO protocol MUST provide adequate mechanisms for
   operations and management support, as outlined in RFC 5706 [RFC5706].

The changes can be seen here:
http://tools.ietf.org/rfcdiff?url1=3Ddraft-ietf-alto-reqs-11.txt&url2=3Dd=
raft-ietf-alto-reqs-15.txt

We plan to move the document forward for IESG approval consideration
soon; if you see anything in the new version of the draft that may not
reflect the understanding of the WG, please speak up by Wednesday, June 6=
th.

--=20
Ciao,
Enrico


--------------ms060806040907060701030807
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINfjCC
BjQwggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOr
lr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSM
zR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6
qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSD
kOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQOJebr/f/h5t95
m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqD
CH14qywGXLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy
6QMVQjbbMXltUfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPI
zKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKf
KSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HOR
z9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9
sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCie
uoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7t
w1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQ
G2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t
5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIHQjCCBiqgAwIBAgIDAt9AMA0GCSqGSIb3DQEB
BQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTEwODIyMDYyNDA2
WhcNMTIwODIyMDM0MDM3WjB8MSAwHgYDVQQNExc0OTAyNDItOU1QZVJYRnFlVVU0QUMybTEo
MCYGA1UEAwwfZW5yaWNvLm1hcm9jY29AdGVsZWNvbWl0YWxpYS5pdDEuMCwGCSqGSIb3DQEJ
ARYfZW5yaWNvLm1hcm9jY29AdGVsZWNvbWl0YWxpYS5pdDCCASIwDQYJKoZIhvcNAQEBBQAD
ggEPADCCAQoCggEBALl4L3Uj7TJrMbll5JAyphws2AMR67q3D2FH0JmRqQ5r+ujqaxyeHcrx
Kclu2tz/D3SPtZAlcDOclxpEDbpxXlMpo+3DsbNweNgSF6mnyRDYU2ay3qO54ENz21GZ64bl
ZRsMI6KsGnxm7sORWLUdx229ijARs3aQD1js9bidUJsnxg26UvnwpJ8eGoFiCLzzsQXUD+OL
3TXEGrTzt+B2RDb13TIOe085T8jzBh08wNKPTDmKjxy5m35Xn8QfRy8b93d0wUs98Fst5iND
EgHEHc9CwurwLYrOd/1ZkbfAoRi7kRQ0Ih4wKkP+Lkww/0qHEIrrgW+aVmGjkQ0nidAaE+sC
AwEAAaOCA7owggO2MAkGA1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUF
BwMCBggrBgEFBQcDBDAdBgNVHQ4EFgQUYgEiK9qxBHth8ziqydxV7QYZn1QwHwYDVR0jBBgw
FoAUU3Ltkpzg2ssBXHx+ljVO8tS4UYIwKgYDVR0RBCMwIYEfZW5yaWNvLm1hcm9jY29AdGVs
ZWNvbWl0YWxpYS5pdDCCAiEGA1UdIASCAhgwggIUMIICEAYLKwYBBAGBtTcBAgIwggH/MC4G
CCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMDQGCCsGAQUF
BwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUucGRmMIH3BggrBgEF
BQcCAjCB6jAnFiBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTADAgEBGoG+VGhp
cyBjZXJ0aWZpY2F0ZSB3YXMgaXNzdWVkIGFjY29yZGluZyB0byB0aGUgQ2xhc3MgMSBWYWxp
ZGF0aW9uIHJlcXVpcmVtZW50cyBvZiB0aGUgU3RhcnRDb20gQ0EgcG9saWN5LCByZWxpYW5j
ZSBvbmx5IGZvciB0aGUgaW50ZW5kZWQgcHVycG9zZSBpbiBjb21wbGlhbmNlIG9mIHRoZSBy
ZWx5aW5nIHBhcnR5IG9ibGlnYXRpb25zLjCBnAYIKwYBBQUHAgIwgY8wJxYgU3RhcnRDb20g
Q2VydGlmaWNhdGlvbiBBdXRob3JpdHkwAwIBAhpkTGlhYmlsaXR5IGFuZCB3YXJyYW50aWVz
IGFyZSBsaW1pdGVkISBTZWUgc2VjdGlvbiAiTGVnYWwgYW5kIExpbWl0YXRpb25zIiBvZiB0
aGUgU3RhcnRDb20gQ0EgcG9saWN5LjA2BgNVHR8ELzAtMCugKaAnhiVodHRwOi8vY3JsLnN0
YXJ0c3NsLmNvbS9jcnR1MS1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzAB
hi1odHRwOi8vb2NzcC5zdGFydHNzbC5jb20vc3ViL2NsYXNzMS9jbGllbnQvY2EwQgYIKwYB
BQUHMAKGNmh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczEuY2xpZW50
LmNhLmNydDAjBgNVHRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcN
AQEFBQADggEBAF4gnxCzZVmINcZh7ZMB6G1+8/kV6pLqDxyUidalFSJ8KLwJxrxhESOb+E7d
JHxZBuJFH1NBXuVn+MI7rqa/HI7PkLJjkHhMH8ay7jhR2VVMIFYAqRn9O22oDDw2iEigYkgo
HcHP1vD5rtydbGr6mCcHOtWCk5B7FqEoMYTQRO1F6szoqORVaajVtZeSwtVAMufV20tohyUL
hpOH5lZDblsej2XueyJVqD8RYSUJp7w4eMpr5CTP9QdNBS0cca83JA070JMudV+ozG6ADIBx
mGPrWyPv7PmjBBGIXxPJJRxDsDyJBYhs+qh6fZWNl6WZkQNepkn7IAUB0+0ggds992kxggPQ
MIIDzAIBATCBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp
BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0
YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMC30AwCQYF
Kw4DAhoFAKCCAhAwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTIwNTMwMTQyMTI2WjAjBgkqhkiG9w0BCQQxFgQUPy85p6PoK9yOcf0x2glsa/w5YP4wXwYJ
KoZIhvcNAQkPMVIwUDALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCA
MA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGlBgkrBgEEAYI3EAQx
gZcwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQL
EyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENv
bSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDAt9AMIGnBgsqhkiG
9w0BCRACCzGBl6CBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMC30Aw
DQYJKoZIhvcNAQEBBQAEggEAtcpyo93IMXg0y6dKr3hB6eLENhhCmivSWcgcxLTrT3Ny0w5K
hDwIYCS6rJAF1nY+VgMlao5K9pjOqZOH9IIBpDXWQEsBAKtNB/eKZDOopMUqHHxuLkG+Eqa7
VyS2Gi7Eya/5VCZjPerYzyzasSDY/8wSlrBXFmdeX0/QQ6bKOrJYFVa1oGSTi4HCT6LMujXp
romidgkKwkYJtBmafYNHCYLzL1amkiNogXlz4k15pY3e37A+0Q16l6udmCrKo2iOV0oTgcwj
b6eeM14dRpNol5++oGFX19kswwGQ25kE3IBy3G5ZoFYp6tK+p07su6YzzmgePhXeyy8f6DjU
hq0ZPgAAAAAAAA==
--------------ms060806040907060701030807--
