
From yry@cs.yale.edu  Sun Jul  1 20:41:54 2012
Return-Path: <yry@cs.yale.edu>
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 42E3921F8565; Sun,  1 Jul 2012 20:41:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.778
X-Spam-Level: 
X-Spam-Status: No, score=-1.778 tagged_above=-999 required=5 tests=[AWL=-0.822, BAYES_00=-2.599, RCVD_IN_NJABL_PROXY=1.643]
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 lfCM5NeI8R0Q; Sun,  1 Jul 2012 20:41:53 -0700 (PDT)
Received: from vm-emlprdomr-06.its.yale.edu (vm-emlprdomr-06.its.yale.edu [130.132.50.147]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA8E21F8559; Sun,  1 Jul 2012 20:41:53 -0700 (PDT)
Received: from [192.168.1.108] ([221.221.21.202]) (authenticated bits=0) by vm-emlprdomr-06.its.yale.edu (8.14.4/8.14.4) with ESMTP id q623fWec023226 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 1 Jul 2012 23:41:41 -0400
Message-ID: <4FF11869.1010408@cs.yale.edu>
Date: Mon, 02 Jul 2012 11:41:29 +0800
From: "Y. Richard Yang" <yry@cs.yale.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Haiyong Xie <haiyong.xie@huawei.com>
References: <748A482AA35F7A4A8BD26465029B8C4A1B7C49EC@dfweml509-mbx.china.huawei.com>
In-Reply-To: <748A482AA35F7A4A8BD26465029B8C4A1B7C49EC@dfweml509-mbx.china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.71 on 130.132.50.147
Cc: "altoext@ietf.org" <altoext@ietf.org>, Hongtao Yin <hongtao.yin@huawei.com>, "alto@ietf.org" <alto@ietf.org>, Andreas Voellmy <andreas.voellmy@yale.edu>
Subject: Re: [alto] FW: New Version Notification for draft-xie-alto-sdn-extension-use-cases-00.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, 02 Jul 2012 03:41:54 -0000

Hi Haiyong, Tina, Hongtao, and Diego,

A good document! Here are some quick feedback:

- One take-away message that the document appears trying to convey is
Vertical (V) vs Horizontal (H) architectures. My understanding of your 
definition
is that V is a one-to-many setting, i.e., one ALTO Server to m SDN 
Controllers (SC),
while H is one-to-one, i.e., one ALTO Server to one SC. Why is the 
information flow
in H only SC <- ALTO S (Sec. 3.2), not the other way around? In an SDN 
setting, I
agree that an SC should already collect fine-grained, dynamic 
information for its
controlled domain. ALTO current does not define how its information is
collected/provisioned, but SC provides a good source (Sec. 4.3.2) of 
information
for ALTO Server to aggregate and conduct abstraction. I see good value 
in this
direction of information flow. I feel that this is mostly a common 
problem across H
and V. Hence I would not discard the H architecture right away. A 
concern is
whether we are ready to define the SC -> ALTO Server information flow,
given the "early-stageness" of SDN. A related general comment is that it 
maybe quite
helpful to extract common problems (e.g., unknown/dynamic network cost as
you mentioned) and new possibilities for ALTO when introducing SDN, 
instead of
a specific setting of a network being partitioned into many sub-networks 
in a V
architecture. What do you think? A curious question, does the ALTO servers
(as well as the SC) in H form some kind of mesh (peering) among themselves?

- The document seems to imply some kind of exclusive SC/net app setting: 
either
SC or net app, but not both. Do I misunderstand it? This depends on how one
define the scope of SC. There can still be net apps running. Does it 
make sense to
include (explicitly) the net apps into your discussions/figures to 
include 4 types
of entities: devices, SC, ALTO Server, and net apps? I like your 
distinction between
SDN-aware and SDN-unaware apps. I am not sure I fully agree or 
understand your
statement that SDN-aware apps would prefer direct communications with 
SC, but
this will be an important architecture discussion at the ALTO meeting.

Thanks.

Richard

On 6/29/12 6:15 AM, Haiyong Xie wrote:
> Hi All,
>
> This is a proposal on the interaction between ALTO and SDN we'd like to discuss at our next meeting in Vancouver. This draft replaces the older submission draft-xie-alto-sdn-use-cases-01.txt which was withdrawn already.
>
> Comments or discussions are extremely welcome and appreciated.
>
> Best regards,
> Haiyong
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Thursday, June 28, 2012 3:07 PM
> To: Haiyong Xie
> Cc: diego@tid.es; Hongtao Yin; Tina TSOU
> Subject: New Version Notification for draft-xie-alto-sdn-extension-use-cases-00.txt
>
>
> A new version of I-D, draft-xie-alto-sdn-extension-use-cases-00.txt
> has been successfully submitted by Haiyong Xie and posted to the
> IETF repository.
>
> Filename:	 draft-xie-alto-sdn-extension-use-cases
> Revision:	 00
> Title:		 Use Cases for ALTO with Software Defined Networks
> Creation date:	 2012-06-28
> WG ID:		 Individual Submission
> Number of pages: 28
> URL:             http://www.ietf.org/internet-drafts/draft-xie-alto-sdn-extension-use-cases-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-xie-alto-sdn-extension-use-cases
> Htmlized:        http://tools.ietf.org/html/draft-xie-alto-sdn-extension-use-cases-00
>
>
> Abstract:
>     The introduction of SDN fundamentally changes the way that the ALTO
>     works.  This draft describes the Vertical Architecture and the
>     Horizontal Architecture allowing coherent coexistence of application
>     layer traffic optimization (ALTO) with software defined network
>     (SDN).  Unique requirements for design and operations are identified
>     and summarized, suggesting that the Vertical Architecture allows
>     better division, management, flexibility, privacy control and long-
>     term evolution of the network.  We also define the main interactions
>     and information flows, and present a set of use cases to illustrate
>     how we extend ALTO to support SDN, in the Vertical Architecture.
>
>                                                                                    
>
>
> The IETF Secretariat
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto


From richard.alimi@gmail.com  Sun Jul  1 21:45:28 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 3372211E8140 for <alto@ietfa.amsl.com>; Sun,  1 Jul 2012 21:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[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 UXOoisB+nsMN for <alto@ietfa.amsl.com>; Sun,  1 Jul 2012 21:45:26 -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 7550011E8161 for <alto@ietf.org>; Sun,  1 Jul 2012 21:45:26 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so7210386pbc.31 for <alto@ietf.org>; Sun, 01 Jul 2012 21:45:30 -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=GVOBrF7rdwAqKBT+BDwBS1y6IQz40mHSmtZIljtWdqo=; b=tP95Ce4OFi3PvgNXqhOyijiYZmqC8ec7/3+PKfUYxf+TdMWbVuf/2r+MJwZV9nO94T nfXijd+PGLKLOfftcdVp0pLhUiW5KZr8qYq8oduT1cmcCZ2ZLgnNDsJPDwCU2BDJhLtK 1CH8HSAgzS0E8kuYccpCzS5I2vxbJL1dQWRnL/SCT7ZqB0SQyH+tn0MJI3PQMtIj5wFI VnCLSyUbdfVuWVVv3Hl6LCSwW4rRl6r11rF8PcjuaNkiXkGLDPIR9WezZVfRtDklzbvC 9b3vOahZ237IkQksENSD6kTCkyOrFh7gUhRHuqAUTnT/Kw1u1S/3vCo65cl2VJ3+DwgO RFTg==
Received: by 10.68.195.167 with SMTP id if7mr27879725pbc.16.1341204330425; Sun, 01 Jul 2012 21:45:30 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.143.28.8 with HTTP; Sun, 1 Jul 2012 21:45:10 -0700 (PDT)
In-Reply-To: <CBF4EA37.DD6D%w.roome@alcatel-lucent.com>
References: <CBF4E04F.DD08%alto-request@ietf.org> <CBF4EA37.DD6D%w.roome@alcatel-lucent.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Sun, 1 Jul 2012 21:45:10 -0700
X-Google-Sender-Auth: qwSePZfX-j9PFbERruvcz8ks2N0
Message-ID: <CA+cvDaZa6_NCgGkFPTVXc_MRM64Kn2CQZhhqSnwJ81-zx6-8Qg@mail.gmail.com>
To: Bill Roome <w.roome@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: alto@ietf.org
Subject: Re: [alto] Ordinal costs for filtered requests
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, 02 Jul 2012 04:45:28 -0000

On Wed, Jun 6, 2012 at 8:17 AM, Bill Roome <w.roome@alcatel-lucent.com> wrote:
>
>
> On 05/18/2012 15:00, "alto-request@ietf.org" <alto-request@ietf.org> wrote:
>
>>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 :)
>>
>>[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
>>other people might give other use cases too. Assume that in CDN
>>interconnection scenario, there are several surrogates from downstream CDN
>>that can be injected 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 better to query the ALTO server do decide a path from a
>>particuplar surrogate of upstream CDN to a surrogate of downstream CDN.
>>The
>>ordinal costs applied to a m*n entries can be used for this decision.
>
> I always assumed "option a": ordinals are relative to all costs
> in this response, not just the costs for the same source. Of course,
> "option a" automatically satisfies "option b", so if a server is
> willing to do (a), then the server is in compliance regardless of
> what we decide.

Alright - this all seems reasonable to me.   We'll update the draft to
make it clear that the proper interpretation is (a), that an ordinal
cost is relative to all other entries in the map.

Thanks,
Rich

>
>         - Bill Roome
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto

From richard.alimi@gmail.com  Sun Jul  1 21:51:13 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 20BDC21F8809 for <alto@ietfa.amsl.com>; Sun,  1 Jul 2012 21:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 xkIJrB3cW92k for <alto@ietfa.amsl.com>; Sun,  1 Jul 2012 21:51:11 -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 7CD4221F8805 for <alto@ietf.org>; Sun,  1 Jul 2012 21:51:11 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so7215301pbc.31 for <alto@ietf.org>; Sun, 01 Jul 2012 21:51:15 -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=apS90Ilp9f9BEO9/vR5KWXJ8o2lUNYeE2m9ymGJ9ZSY=; b=d+LLQ1ZqlXXvOMOyWxf1oAMth2b3uLshjTjG7BoeEuoXsiisf8rBfYFE5xaynDH8qn 32jNd1WkRNS1aFFr+kkZZIDqM6jDBCKwLl8MNu42Z3/OurUEl3CATxWW0Ipmw1vTy675 Gdef0HymHEKbluOVTdf8XmJ3xXwF3zfp0h5kzSZCDhRIjz4ILcu9aWUZHZX3yOFG9iQ0 rzjIT4WHN1rAM31zgRzLxno7BYUdDH29QH1+seuLoNPB5zihRLa3zXgy3LXlFLSSBQWc FUdUYHLjDsWFrTAW9oLz8nHBVHoVpy7UhvTV8zmBgke42N+VqPCpk12dgNDfYbxezl/7 FlEw==
Received: by 10.66.75.225 with SMTP id f1mr17175424paw.35.1341204674981; Sun, 01 Jul 2012 21:51:14 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.143.28.8 with HTTP; Sun, 1 Jul 2012 21:50:54 -0700 (PDT)
In-Reply-To: <CBF4FED9.DD88%w.roome@alcatel-lucent.com>
References: <CBF4E053.DD08%alto-request@ietf.org> <CBF4FED9.DD88%w.roome@alcatel-lucent.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Sun, 1 Jul 2012 21:50:54 -0700
X-Google-Sender-Auth: VZb6fozsrgiZKT1UxS8r4_UK2vs
Message-ID: <CA+cvDaY8mzptaFoUTkXXv_ruF65Ft0WwomERrUaLvfnohnyKzw@mail.gmail.com>
To: Bill Roome <w.roome@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: alto@ietf.org
Subject: Re: [alto] Problem with endpoint property response in draft 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, 02 Jul 2012 04:51:14 -0000

On Wed, Jun 6, 2012 at 10:01 AM, Bill Roome <w.roome@alcatel-lucent.com> wrote:
> {7.7.3.1.5} -- Endpoint Property Response -- says
>
> The ALTO Server MAY include the Version Tag (Section 5.3) of the
> Network Map used to generate the response (if desired and applicable)
> as the 'map-vtag' member in the response. If the 'pid' property is
> returned for any endpoints in the response, the 'map-vtag' member is
> REQUIRED instead of OPTIONAL.
>
>
> However the example in {7.7.3.1.6} doesn't follow that rule. It's
>
>   {
>     "meta" : {},
>     "data": {
>       "ipv4:192.0.2.34"    : { "pid": "PID1" },
>       "ipv4:203.0.113.129" : { "pid": "PID3" }
>     }
>   }
>
>
> where it should be
>
>   {
>     "meta" : {},
>     "data": {
>       "map-vtag" : "1266506139",
>       "ipv4:192.0.2.34"    : { "pid": "PID1" },
>       "ipv4:203.0.113.129" : { "pid": "PID3" }
>     }
>   }
>
>
> But that has an unfortunate complication. Before, all the keys in the "data"
> object were endpoints.
> But now, a key is an endpoint address UNLESS it's "map-vtag". Granted,
> that's not ambiguous, because
> "map-vtag" can't possibly be an endpoint address.
>
> But still it's annoying. Compare that with the a filtered network-map
> response:
>
>    {
>      "meta" : {},
>      "data" : {
>        "map-vtag" : "1266506139",
>        "map" : {
>          "PID1" : {
>            "ipv4" : [ "192.0.2.0/24", "198.51.100.0/24" ]
>          },
>          "PID2" : {
>            "ipv4": [ "198.51.100.128/24" ]
>          }
>        }
>      }
>    }
>
> There the PID name keys are all in a "map" object. So for consistency,
> the properties in an endpoint prop response should also be under a "map":
>
>   {
>
>     "meta" : {},
>     "data": {
>       "map-vtag" : "1266506139",
>       "map" : {
>          "ipv4:192.0.2.34"    : { "pid": "PID1" },
>          "ipv4:203.0.113.129" : { "pid": "PID3" }
>       }
>     }
>   }
>
>
> Comments?

Thanks for catching this.  I completely agree with the suggested
approach of putting all of of the properties within a 'map' object.
That seems to be a much cleaner approach.

Thanks,
Rich

>
> - Bill Roome
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>

From richard.alimi@gmail.com  Sun Jul  1 22:08:52 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 9FBB111E8158 for <alto@ietfa.amsl.com>; Sun,  1 Jul 2012 22:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[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 GG1SCiitXzZ3 for <alto@ietfa.amsl.com>; Sun,  1 Jul 2012 22:08:50 -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 B4ADA11E8160 for <alto@ietf.org>; Sun,  1 Jul 2012 22:08:50 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so7231019pbc.31 for <alto@ietf.org>; Sun, 01 Jul 2012 22:08:54 -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=kgUCq9ALadgnMraECdI9le15vLbi79lAMlt+B7Reo70=; b=BfwBI/5dafg9MjJoVKCgYxEpygA8qMO+gyYUkX9nOwdWNUHOQu5UU0FlIEDgylc3N7 5WizP5o4X7ysSfgz9hhNAAAhWl1rBpshuhiIHhuR5BFJyBLPbhaufpju+PNEoB+ztn+5 8npviBvM5ykqCsJH2GcOb2xo7t7MiSiUxcbp/5k7z39o9k6GmLU7XtfJKcGZu1t29I46 JPHqEsgi1j9bcsOkD//CL+mVJBbrgeEC6lgvBhIOu88ifCA3DLemt7OgRACs3m9asaQs LZJjNuLo+XK7kC1mPB23K/I6jfOSWs7JSvdurSoleqyeakXczF6YaY0sn5eTghF1Daaa e6MQ==
Received: by 10.66.75.225 with SMTP id f1mr17255815paw.35.1341205734823; Sun, 01 Jul 2012 22:08:54 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.143.28.8 with HTTP; Sun, 1 Jul 2012 22:08:34 -0700 (PDT)
In-Reply-To: <CA+cvDaagS11X_ktV-AnO4ppYyE52FSuFgeZhabqw4j9efGp8zg@mail.gmail.com>
References: <4F8BE443.9050903@telecomitalia.it> <4FAD5745.2060009@alcatel-lucent.com> <CA+cvDab3P0-68m6+mZ+4K0FedJ7_MK6SGXhD2kQKupXuCDLgDw@mail.gmail.com> <4FBA5B39.8040505@alcatel-lucent.com> <CA+cvDaagS11X_ktV-AnO4ppYyE52FSuFgeZhabqw4j9efGp8zg@mail.gmail.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Sun, 1 Jul 2012 22:08:34 -0700
X-Google-Sender-Auth: wR9_N5NXvPAB4ci4FPyVwoN5cw8
Message-ID: <CA+cvDabKnT=o34G3ogtkT=cAgAe=ak3OETPhu+n_cxFZt7+e=w@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
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, 02 Jul 2012 05:08:52 -0000

[ mistakenly dropped alto list from my reply...]

On Sun, Jul 1, 2012 at 10:05 PM, Richard Alimi <rich@velvetsea.net> wrote:
> On Mon, May 21, 2012 at 8:11 AM, Sabine Randriamasy
> <Sabine.Randriamasy@alcatel-lucent.com> wrote:
>>
>> Hi Rich,
>>
>>
>> Richard Alimi a =E9crit :
>>
>>> 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 cou=
ple
>>>> 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". I=
n
>>>> some
>>>> places, see detailed comments, "peer" should be replaced by "endpoints=
"
>>>> when
>>>> referring to a content location. In Section 8 Use Cases, some text sho=
uld
>>>> 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 wa=
s on
>> specifying the features that the ALTO MUST have. My question here was ra=
ther
>> 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.
>
> Given the concern over a large amount of duplicate text in the draft,
> I'd like to leave such a list out unless there are others in the WG
> that feel strongly that we should have it.
>
>>
>>>
>>>>
>>>> -----------------------------------------------------
>>>> 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.
>>>>
>>>
>>>
>>> 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
>>
>>>
>>>>
>>>> - =A71, 2nd sentence "There is no clear mechanism to convey informatio=
n
>>>> about
>>>> the network (e.g., preferences) to applications": could be specified b=
y
>>>> 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 exampl=
es
>> you may have in mind.
>
> I think we can expand this sentence to mention some existing examples.
>  As far as arguing that there needs to be a standardized mechanism, I
> think the Problem Statement document should do that already.
>
>>
>> *
>>>
>>>
>>>>
>>>> - =A72last sentence "The mechanism should include abstractions to achi=
eve
>>>> concise, flexible network information expression.": is it the only
>>>> motivation for abstraction or does abstraction also serve other purpos=
es
>>>> 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 th=
e
>> reading more comfortable.
>>
>>>
>>>>
>>>> - 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 Locat=
ion
>>>> 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 up=
dated
>>>> 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
>>>> - =A73 3rd sentence "ALTO-Core provides the Map Service, which provide=
s the
>>>> core ALTO informtion to
>>>> clients". The term "ALTO-Core" should be introduced ans besides it doe=
s
>>>> 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" =3D=3D> "information".
>>>>
>>>
>>>
>>> Ack.
>>>
>>>
>>>>
>>>> Section 4 Network Map
>>>> - =A72: "The Network Location endpoint property": i suggest "The Netwo=
rk
>>>> Location Endpoint Property"
>>>>
>>>>
>>>> Section 7.2.1 Discovering Information Resources
>>>> - =A71 "To discover available resources, an ALTO Client may request th=
e
>>>> Information Resource Directory": what are other means? There seem to b=
e a
>>>> contradiction with Section 6.2 Protocol design where item "o Informati=
on
>>>> Resource Directory" says that "This directory is the single entry poin=
t
>>>> 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
>>>> - =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 medi=
a
>>>> 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 m=
y
>>>> 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
>>>> - =A72 last sentence: "... Table 1in the HTTP response." : blank space=
 is
>>>> 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 fo=
rmat of
>>>> an
>>>> Information Resource Directory request."
>>>>
>>>
>>>
>>> Ack.
>>>
>>>
>>>>
>>>> - =A74 - item "capabilities": i didin't understand the sentence "or as=
sume
>>>> its
>>>> default value", although the protocol is not expected to guide the ALT=
O
>>>> 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"
>
> That sounds fine, but I'll just rephrase to say "or assume its default
> value which is documented in this specification."   I don't think
> normative language is needed there, since the instruction applies to
> the document authors/editors/WG and not the implementers.
>
>>
>>> 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 t=
he
>>>> 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, t=
hen,
>> as =A7 7.7.1.2.4 comes after the IRD example, I think that things would =
be
>> completely clear if =A7 7.6.3 would include an illustrative sentence lik=
e, "In
>> this example, the ALTO server provides the Endpoint Cost Service for Cos=
t
>> Types 'routingcost' and 'hopcount', each available for both 'numerical' =
and
>> 'ordinal' mode".
>
> That sounds fine to me. We'll add a hint here.
>
>> As for my 2nd question, I understand that for the mentionned case, the I=
RD
>> 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..*>;". th=
e
>>>> 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 =
says
>>>> "This resource MUST be provided for at least the =92routingcost=92 Cos=
t 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..*> ?
>>>>
>>>
>>>
>>> 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 =A77.7.3.1.3 Input Parameters, where encoding "EndpointProper=
ty
>>>> 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 =A77.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, Sect=
ion
>>>> 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 t=
he
>>>> =92ordinal=92 Cost Mode... ".
>>>> Although it intuitively make more sens to have constraints on numerica=
l
>>>> 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 giv=
en
>>>> 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
>>>> - =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... ".
>>>>
>>>
>>>
>>> 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
>>>> - =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 t=
he
>>>> 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=
 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 .=
.."
>>>>
>>>>
>>>
>>>
>>> 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 commen=
ts
>>>>> to the list before the expiry of WGLC so we can get this document rea=
dy
>>>>> for the IESG.
>>>>>
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> alto mailing list
>>>> alto@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/alto
>>>>
>>
>>

From yang.r.yang@gmail.com  Sun Jul  1 22:26:49 2012
Return-Path: <yang.r.yang@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 5582311E8175 for <alto@ietfa.amsl.com>; Sun,  1 Jul 2012 22:26:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, 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 I8e5AP18B23Q for <alto@ietfa.amsl.com>; Sun,  1 Jul 2012 22:26:48 -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 5465911E8161 for <alto@ietf.org>; Sun,  1 Jul 2012 22:26:48 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so8853272obb.31 for <alto@ietf.org>; Sun, 01 Jul 2012 22:26:52 -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:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=nm/U7gKtKyRtFJFH4/C4ZdU2j9syTtC3HqZiXyjPMok=; b=tpNZNQozD76Za0RaAioRHqOqR/a4D8sOz4f7z45/7NICdTSjHo5HMcyQs7up304Hcw 2O7jEHqryhT6ghgSbHq3Gx6I/7BCbEaZgoAbwTZEFMu0qgWq/khhbR7op6fCB0sh42d8 NrqNrWxm+DJL98COertrT5tEhg5LVQnDwn8ZG6eZRFBoUihVQnzp0VqmBmhtHMNANV4Y KeYUApDjIxkfKjRaUK27qAl2TIKNW5S/xupoyPVLtBM073TqQFQyYxZWgtQKo9/QK/tX rAfq3tK0E0CZNGIKe/rDNIdmZyvP5wiNN8cfYEgCwt+bHpiDSwv+IgB3794Dnrp1blrz vngg==
MIME-Version: 1.0
Received: by 10.60.22.165 with SMTP id e5mr9955186oef.60.1341206812047; Sun, 01 Jul 2012 22:26:52 -0700 (PDT)
Sender: yang.r.yang@gmail.com
Received: by 10.76.86.136 with HTTP; Sun, 1 Jul 2012 22:26:52 -0700 (PDT)
In-Reply-To: <CA+cvDaY8mzptaFoUTkXXv_ruF65Ft0WwomERrUaLvfnohnyKzw@mail.gmail.com>
References: <CBF4E053.DD08%alto-request@ietf.org> <CBF4FED9.DD88%w.roome@alcatel-lucent.com> <CA+cvDaY8mzptaFoUTkXXv_ruF65Ft0WwomERrUaLvfnohnyKzw@mail.gmail.com>
Date: Mon, 2 Jul 2012 13:26:52 +0800
X-Google-Sender-Auth: QExgsPlNjgFWjKeBdR-KkdJjY8k
Message-ID: <CANUuoLoWCRW6dh9VYx86bOrz5vxWyR5nKgS8TWuxCTM=55+6XQ@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: Richard Alimi <rich@velvetsea.net>
Content-Type: multipart/alternative; boundary=e89a8fb1ed3c9a379104c3d20b3b
Cc: Bill Roome <w.roome@alcatel-lucent.com>, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Problem with endpoint property response in draft 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, 02 Jul 2012 05:26:49 -0000

--e89a8fb1ed3c9a379104c3d20b3b
Content-Type: text/plain; charset=ISO-8859-1

On Monday, July 2, 2012, Richard Alimi wrote:

> On Wed, Jun 6, 2012 at 10:01 AM, Bill Roome <w.roome@alcatel-lucent.com<javascript:;>>
> wrote:
> > {7.7.3.1.5} -- Endpoint Property Response -- says
> >
> > The ALTO Server MAY include the Version Tag (Section 5.3) of the
> > Network Map used to generate the response (if desired and applicable)
> > as the 'map-vtag' member in the response. If the 'pid' property is
> > returned for any endpoints in the response, the 'map-vtag' member is
> > REQUIRED instead of OPTIONAL.
> >
> >
> > However the example in {7.7.3.1.6} doesn't follow that rule. It's
> >
> >   {
> >     "meta" : {},
> >     "data": {
> >       "ipv4:192.0.2.34"    : { "pid": "PID1" },
> >       "ipv4:203.0.113.129" : { "pid": "PID3" }
> >     }
> >   }
> >
> >
> > where it should be
> >
> >   {
> >     "meta" : {},
> >     "data": {
> >       "map-vtag" : "1266506139",
> >       "ipv4:192.0.2.34"    : { "pid": "PID1" },
> >       "ipv4:203.0.113.129" : { "pid": "PID3" }
> >     }
> >   }
> >
> >
> > But that has an unfortunate complication. Before, all the keys in the
> "data"
> > object were endpoints.
> > But now, a key is an endpoint address UNLESS it's "map-vtag". Granted,
> > that's not ambiguous, because
> > "map-vtag" can't possibly be an endpoint address.
> >
> > But still it's annoying. Compare that with the a filtered network-map
> > response:
> >
> >    {
> >      "meta" : {},
> >      "data" : {
> >        "map-vtag" : "1266506139",
> >        "map" : {
> >          "PID1" : {
> >            "ipv4" : [ "192.0.2.0/24", "198.51.100.0/24" ]
> >          },
> >          "PID2" : {
> >            "ipv4": [ "198.51.100.128/24" ]
> >          }
> >        }
> >      }
> >    }
> >
> > There the PID name keys are all in a "map" object. So for consistency,
> > the properties in an endpoint prop response should also be under a "map":
> >
> >   {
> >
> >     "meta" : {},
> >     "data": {
> >       "map-vtag" : "1266506139",
> >       "map" : {
> >          "ipv4:192.0.2.34"    : { "pid": "PID1" },
> >          "ipv4:203.0.113.129" : { "pid": "PID3" }
> >       }
> >     }
> >   }
> >
> >
> > Comments?
>
> I like this revision too. Here the "map" really means the specific
"mapping" from
 key(s) to value(s). It is consistent.

- yry



> Thanks for catching this.  I completely agree with the suggested
> approach of putting all of of the properties within a 'map' object.
> That seems to be a much cleaner approach.
>
> Thanks,
> Rich
>
> >
> > - Bill Roome
> >
> >
> > _______________________________________________
> > alto mailing list
> > alto@ietf.org <javascript:;>
> > https://www.ietf.org/mailman/listinfo/alto
> >
> _______________________________________________
> alto mailing list
> alto@ietf.org <javascript:;>
> https://www.ietf.org/mailman/listinfo/alto
>

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

<br><br>On Monday, July 2, 2012, Richard Alimi  wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">On Wed, Jun 6, 2012 at 10:01 AM, Bill Roome &lt;<a href=3D"ja=
vascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;w.roome@alcatel-lucen=
t.com&#39;)">w.roome@alcatel-lucent.com</a>&gt; wrote:<br>

&gt; {7.7.3.1.5} -- Endpoint Property Response -- says<br>
&gt;<br>
&gt; The ALTO Server MAY include the Version Tag (Section 5.3) of the<br>
&gt; Network Map used to generate the response (if desired and applicable)<=
br>
&gt; as the &#39;map-vtag&#39; member in the response. If the &#39;pid&#39;=
 property is<br>
&gt; returned for any endpoints in the response, the &#39;map-vtag&#39; mem=
ber is<br>
&gt; REQUIRED instead of OPTIONAL.<br>
&gt;<br>
&gt;<br>
&gt; However the example in {7.7.3.1.6} doesn&#39;t follow that rule. It&#3=
9;s<br>
&gt;<br>
&gt; =A0 {<br>
&gt; =A0 =A0 &quot;meta&quot; : {},<br>
&gt; =A0 =A0 &quot;data&quot;: {<br>
&gt; =A0 =A0 =A0 &quot;ipv4:192.0.2.34&quot; =A0 =A0: { &quot;pid&quot;: &q=
uot;PID1&quot; },<br>
&gt; =A0 =A0 =A0 &quot;ipv4:203.0.113.129&quot; : { &quot;pid&quot;: &quot;=
PID3&quot; }<br>
&gt; =A0 =A0 }<br>
&gt; =A0 }<br>
&gt;<br>
&gt;<br>
&gt; where it should be<br>
&gt;<br>
&gt; =A0 {<br>
&gt; =A0 =A0 &quot;meta&quot; : {},<br>
&gt; =A0 =A0 &quot;data&quot;: {<br>
&gt; =A0 =A0 =A0 &quot;map-vtag&quot; : &quot;1266506139&quot;,<br>
&gt; =A0 =A0 =A0 &quot;ipv4:192.0.2.34&quot; =A0 =A0: { &quot;pid&quot;: &q=
uot;PID1&quot; },<br>
&gt; =A0 =A0 =A0 &quot;ipv4:203.0.113.129&quot; : { &quot;pid&quot;: &quot;=
PID3&quot; }<br>
&gt; =A0 =A0 }<br>
&gt; =A0 }<br>
&gt;<br>
&gt;<br>
&gt; But that has an unfortunate complication. Before, all the keys in the =
&quot;data&quot;<br>
&gt; object were endpoints.<br>
&gt; But now, a key is an endpoint address UNLESS it&#39;s &quot;map-vtag&q=
uot;. Granted,<br>
&gt; that&#39;s not ambiguous, because<br>
&gt; &quot;map-vtag&quot; can&#39;t possibly be an endpoint address.<br>
&gt;<br>
&gt; But still it&#39;s annoying. Compare that with the a filtered network-=
map<br>
&gt; response:<br>
&gt;<br>
&gt; =A0 =A0{<br>
&gt; =A0 =A0 =A0&quot;meta&quot; : {},<br>
&gt; =A0 =A0 =A0&quot;data&quot; : {<br>
&gt; =A0 =A0 =A0 =A0&quot;map-vtag&quot; : &quot;1266506139&quot;,<br>
&gt; =A0 =A0 =A0 =A0&quot;map&quot; : {<br>
&gt; =A0 =A0 =A0 =A0 =A0&quot;PID1&quot; : {<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0&quot;ipv4&quot; : [ &quot;<a href=3D"http://19=
2.0.2.0/24" target=3D"_blank">192.0.2.0/24</a>&quot;, &quot;<a href=3D"http=
://198.51.100.0/24" target=3D"_blank">198.51.100.0/24</a>&quot; ]<br>
&gt; =A0 =A0 =A0 =A0 =A0},<br>
&gt; =A0 =A0 =A0 =A0 =A0&quot;PID2&quot; : {<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0&quot;ipv4&quot;: [ &quot;<a href=3D"http://198=
.51.100.128/24" target=3D"_blank">198.51.100.128/24</a>&quot; ]<br>
&gt; =A0 =A0 =A0 =A0 =A0}<br>
&gt; =A0 =A0 =A0 =A0}<br>
&gt; =A0 =A0 =A0}<br>
&gt; =A0 =A0}<br>
&gt;<br>
&gt; There the PID name keys are all in a &quot;map&quot; object. So for co=
nsistency,<br>
&gt; the properties in an endpoint prop response should also be under a &qu=
ot;map&quot;:<br>
&gt;<br>
&gt; =A0 {<br>
&gt;<br>
&gt; =A0 =A0 &quot;meta&quot; : {},<br>
&gt; =A0 =A0 &quot;data&quot;: {<br>
&gt; =A0 =A0 =A0 &quot;map-vtag&quot; : &quot;1266506139&quot;,<br>
&gt; =A0 =A0 =A0 &quot;map&quot; : {<br>
&gt; =A0 =A0 =A0 =A0 =A0&quot;ipv4:192.0.2.34&quot; =A0 =A0: { &quot;pid&qu=
ot;: &quot;PID1&quot; },<br>
&gt; =A0 =A0 =A0 =A0 =A0&quot;ipv4:203.0.113.129&quot; : { &quot;pid&quot;:=
 &quot;PID3&quot; }<br>
&gt; =A0 =A0 =A0 }<br>
&gt; =A0 =A0 }<br>
&gt; =A0 }<br>
&gt;<br>
&gt;<br>
&gt; Comments?<br>
<br></blockquote><div>I like this revision too. Here the &quot;map&quot; re=
ally means the specific &quot;mapping&quot; from</div><div>=A0key(s) to val=
ue(s). It is consistent.</div><div><br></div><div>- yry<span></span></div>
<br><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks for catching this. =A0I completely agree with the suggested<br>
approach of putting all of of the properties within a &#39;map&#39; object.=
<br>
That seems to be a much cleaner approach.<br>
<br>
Thanks,<br>
Rich<br>
<br>
&gt;<br>
&gt; - Bill Roome<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; alto mailing list<br>
&gt; <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;alt=
o@ietf.org&#39;)">alto@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/alto</a><br>
&gt;<br>
_______________________________________________<br>
alto mailing list<br>
<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;alto@iet=
f.org&#39;)">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
</blockquote>

--e89a8fb1ed3c9a379104c3d20b3b--

From richard.alimi@gmail.com  Sun Jul  1 23:39:15 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 9179411E810D for <alto@ietfa.amsl.com>; Sun,  1 Jul 2012 23:39:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.414
X-Spam-Level: 
X-Spam-Status: No, score=-0.414 tagged_above=-999 required=5 tests=[AWL=-2.563, BAYES_50=0.001, FM_FORGED_GMAIL=0.622, MANGLED_LOAN=2.3, RCVD_IN_DNSWL_LOW=-1, 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 ztRPchYRPA44 for <alto@ietfa.amsl.com>; Sun,  1 Jul 2012 23:39:13 -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 9418011E8079 for <alto@ietf.org>; Sun,  1 Jul 2012 23:39:13 -0700 (PDT)
Received: by dacx6 with SMTP id x6so7163979dac.31 for <alto@ietf.org>; Sun, 01 Jul 2012 23:39:17 -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=xCjOKgjKXMx9TduTqxB+61NnpMvK6WmNhYLR++gZ9AY=; b=dqWsOmNcszfZvT1PXxx8/xyAXQL4u0Kf+NzlLIhXjS9D+bmGfvAMI612SK30l7Q5li ZF1bNhIVlX0wsH4cKU8TYGnBcgGJThnxy9kEgNLMQWEBM7VtKM0zQM4uIwMlJMp++Ib9 wuDO0L1CAqv9dnfDbIYeZH7vtJXqDRT+qk/FmF40yQmTljXs+9Uoaj782H/5HQqD4/Co UYnsmK6b7Fyx4ZIwUdPoPaRY+NavT4cBGsoeP4frqpKt3BBmoOCjbCmBNLPYqe2fJ+f1 dg6nada85/19xWvioI+2VSBzf4oVal/hZz+aoe9laeu0qP5jjJ2/VL4G6uZPBAfA/8O6 jOig==
Received: by 10.68.195.167 with SMTP id if7mr28475921pbc.16.1341211157667; Sun, 01 Jul 2012 23:39:17 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.143.28.8 with HTTP; Sun, 1 Jul 2012 23:38:57 -0700 (PDT)
In-Reply-To: <20120514061451.GA3136@gw01.ehlo.wurstkaes.de>
References: <4F8BE443.9050903@telecomitalia.it> <20120514061451.GA3136@gw01.ehlo.wurstkaes.de>
From: Richard Alimi <rich@velvetsea.net>
Date: Sun, 1 Jul 2012 23:38:57 -0700
X-Google-Sender-Auth: RlG2-ZaHoDx9aHCLqutC6gUKRIk
Message-ID: <CA+cvDab1XR40W7FBHhDNOTTag7tvSihVe7BSMVbAP6W-Qtk91A@mail.gmail.com>
To: Sebastian Kiesel <ietf-alto@skiesel.de>
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-ietf-alto-protocol@tools.ietf.org, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [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, 02 Jul 2012 06:39:15 -0000

Thank you very much Sebastian for putting this together!

There are few responses inline for the ones that were not fully
compliant.  I either made an attempt to indicate why the protocol is
the way it is for the benefit of others (or to open up discussion), or
raised a question on how we can resolve it.

On Sun, May 13, 2012 at 11:14 PM, Sebastian Kiesel <ietf-alto@skiesel.de> wrote:
> 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, ...)

It needs something more than just an I-D since that is a pretty low bar.

Do people think a registry is needed for this?  If not, perhaps we can
just make this more explicit that it needs to be a standards-track
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.

At least in the initial discussions of ALTO, there was mention about
using these for addresses other than IP addresses, such as e.164
numbers.  That said, I haven't seen any concrete use cases for
anything other than IP addresses or things that can map to IP
addresses.

I don't intend to start a debate on the requirements document at this
stage, but I'm a bit hesitant to say that extensions MUST do this.  I
completely agree that those proposing extensions should be thinking
about this, but tend to think that MUST is too strong.  How about
extending 7.5.3.1 to state "extension documents defining a new Address
Type SHOULD also document a mechanism to map addresses of the new type
to IPv4 and/or IPv6 addresses prefixes."

>
>     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.

Do you have any thoughts on what this might look like?

>     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.

Moving this to the deployment considerations document sounds reasonable to me.

>>    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).

Agree that we should resolve this.  We can leave resolving this to
discussion 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.

I tend to think it's best to leave this one as partially compliant for
now, and leave the additional expiration field for when there is an
extension to support redistribution (the section that was removed in
-11).  Any disagreement with that?

>
>>    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

Yeah - I'm personally okay with this current state, since we
consciously removed the section on Redistribution and left that for an
extension.

>
>>    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

The use of JSON and Section 7.2.7 also helps with extensions.

>>    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

Yeah.  There was a discussion when going to the REST-ful approach
about whether we wanted any explicit version numbers or not.  The idea
was that we didn't need an ALTO version number exposed to applications
if we used media types appropriately.  Using media types like you
suggested is certainly one approach.

>> 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.

We also had a discussion about this in the protocol overhaul for
making it REST-ful.  The guidance we received there was to not repeat
details from RFC2616.  I'm not sure I see much utility in adding
specifics in the ALTO protocol document, since it would basically
amount to saying "If you think you are overloaded, you are free to
return a 503."  Then, if we were to add that, people would ask "you
gave me guidance on using 503, but you didn't tell me when I should or
should not use chunked transfer encoding.. how about that??"  The idea
was that the statements in Section 7.2, as well as some intelligence
on behalf of implementers on how to apply RFC2616, would answer all of
these questions.

>> 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.

Agree. See comment above.

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

From Martin.Stiemerling@neclab.eu  Mon Jul  2 07:58: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 A7B5F21F869D for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 07:58:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, 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 06blQFD+KMiZ for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 07:58:57 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 7917721F869E for <alto@ietf.org>; Mon,  2 Jul 2012 07:58:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id A4F931016F2 for <alto@ietf.org>; Mon,  2 Jul 2012 16:59:38 +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 B25gsOzIt4sp for <alto@ietf.org>; Mon,  2 Jul 2012 16:59:38 +0200 (CEST)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 8E5DF1016F1 for <alto@ietf.org>; Mon,  2 Jul 2012 16:59:33 +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; Mon, 2 Jul 2012 17:00:04 +0200
Message-ID: <4FF1B72C.4000209@neclab.eu>
Date: Mon, 2 Jul 2012 16:58:52 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: <alto@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Subject: [alto] Way forward for the Resdistribution
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, 02 Jul 2012 14:58:57 -0000

Hi all,

I have just read the ALTO protocol slides of the meeting in Paris and do 
wonder what has ultimately happened to the redistribution, as the slide 
state:

"Will be submitted as separate draft that may make use of JOSE"
(http://www.ietf.org/proceedings/83/slides/slides-83-alto-2.pdf)

This functionality is gone from the base protocol, but we do not have 
any replacement insight. Do we completely abandon this?

Thanks,

   Martin
-- 
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 Martin.Stiemerling@neclab.eu  Mon Jul  2 08:06:05 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 4142621F86CE for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 08:06:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.456
X-Spam-Level: 
X-Spam-Status: No, score=-102.456 tagged_above=-999 required=5 tests=[AWL=-0.084, 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 xnydaZfs7Xsy for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 08:06:03 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6847D21F86BA for <alto@ietf.org>; Mon,  2 Jul 2012 08:06:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 9B5271016F4; Mon,  2 Jul 2012 17:06:49 +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 7ayw5Xm1LGCf; Mon,  2 Jul 2012 17:06:49 +0200 (CEST)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 775951016F3; Mon,  2 Jul 2012 17:06:29 +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; Mon, 2 Jul 2012 17:07:00 +0200
Message-ID: <4FF1B8CB.7090005@neclab.eu>
Date: Mon, 2 Jul 2012 17:05:47 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: Richard Alimi <rich@velvetsea.net>
References: <4F8BE443.9050903@telecomitalia.it> <20120514061451.GA3136@gw01.ehlo.wurstkaes.de> <CA+cvDab1XR40W7FBHhDNOTTag7tvSihVe7BSMVbAP6W-Qtk91A@mail.gmail.com>
In-Reply-To: <CA+cvDab1XR40W7FBHhDNOTTag7tvSihVe7BSMVbAP6W-Qtk91A@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Cc: draft-ietf-alto-protocol@tools.ietf.org, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [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, 02 Jul 2012 15:06:05 -0000

[writing with no Area Director hat on, i.e., as a random community member]
Hi Richard, all,

On 07/02/2012 08:38 AM, Richard Alimi wrote:
[...]

>> 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, ...)
>
> It needs something more than just an I-D since that is a pretty low bar.

You can specify 'protocol specification' or 'expert review' as the bar 
for an extension.
See also RFC 5226 for a discussion of this:
http://tools.ietf.org/html/rfc5226

>
> Do people think a registry is needed for this?  If not, perhaps we can
> just make this more explicit that it needs to be a standards-track
> RFC.

There should be a registry where you can add additional address types. 
Otherwise it is really hard to get new address types in a clean way into 
the protocol.
A registry allows also to keep track about all existing address types 
(out of the ALTO protocol and what comes later on).

>
>>>     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.
>
> At least in the initial discussions of ALTO, there was mention about
> using these for addresses other than IP addresses, such as e.164
> numbers.  That said, I haven't seen any concrete use cases for
> anything other than IP addresses or things that can map to IP
> addresses.
>
> I don't intend to start a debate on the requirements document at this
> stage, but I'm a bit hesitant to say that extensions MUST do this.  I
> completely agree that those proposing extensions should be thinking
> about this, but tend to think that MUST is too strong.  How about
> extending 7.5.3.1 to state "extension documents defining a new Address
> Type SHOULD also document a mechanism to map addresses of the new type
> to IPv4 and/or IPv6 addresses prefixes."

A SHOULD is fine, as it implies that people must say why they are not 
specifying a mapping mechanism.

>
>>
>>      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.
>
> Do you have any thoughts on what this might look like?

An appropriate error message with a path name delivered through this 
would good. However, this is just a proposal.

>
>>      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.
>
> Moving this to the deployment considerations document sounds reasonable to me.

+1

>
>>>     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-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.
>
> I tend to think it's best to leave this one as partially compliant for
> now, and leave the additional expiration field for when there is an
> extension to support redistribution (the section that was removed in
> -11).  Any disagreement with that?

Not from my side.

>
>>
>>>     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
>
> Yeah - I'm personally okay with this current state, since we
> consciously removed the section on Redistribution and left that for an
> extension.

If we allow to be partially compliant, we should at least note that the 
missing points are part of a future redistribution mechanism and 
therefore not specified in the current ALTO protocol.

>
>>
>>>     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
>
> The use of JSON and Section 7.2.7 also helps with extensions.
>
>>>     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
>
> Yeah.  There was a discussion when going to the REST-ful approach
> about whether we wanted any explicit version numbers or not.  The idea
> was that we didn't need an ALTO version number exposed to applications
> if we used media types appropriately.  Using media types like you
> suggested is certainly one approach.

Irrespectively of what mechanisms is being used, this protocol needs 
versioning support. However, I'm not sure that media-types are the best 
way forward for this.
What would be a different approach when using media types?


>
>>> 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.
>
> We also had a discussion about this in the protocol overhaul for
> making it REST-ful.  The guidance we received there was to not repeat
> details from RFC2616.  I'm not sure I see much utility in adding
> specifics in the ALTO protocol document, since it would basically
> amount to saying "If you think you are overloaded, you are free to
> return a 503."  Then, if we were to add that, people would ask "you
> gave me guidance on using 503, but you didn't tell me when I should or
> should not use chunked transfer encoding.. how about that??"  The idea
> was that the statements in Section 7.2, as well as some intelligence
> on behalf of implementers on how to apply RFC2616, would answer all of
> these questions.

That is not a good way of specifying things. There is no need to say how 
a 503 response looks like, but it is definitely good to say when an ALTO 
protocol must reply with such a code. "intelligence ...of implementers" 
will cause ALTO protocol implementations that do not interoperate.

>
>>> 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.
>
> Agree. See comment above.

Give at least guidance where to read on to protect against such threads. 
Otherwise this specification is incomplete.

   Martin


-- 
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 Martin.Stiemerling@neclab.eu  Mon Jul  2 08:17:52 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 770DF21F85D7 for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 08:17:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.454
X-Spam-Level: 
X-Spam-Status: No, score=-102.454 tagged_above=-999 required=5 tests=[AWL=-0.082, 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 O29tIgxhtMLB for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 08:17:51 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 8236621F8598 for <alto@ietf.org>; Mon,  2 Jul 2012 08:17:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id D54481016F3; Mon,  2 Jul 2012 17:18:37 +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 ryBZJpVQdZh8; Mon,  2 Jul 2012 17:18:37 +0200 (CEST)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id BC5A61016F1; Mon,  2 Jul 2012 17:18: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; Mon, 2 Jul 2012 17:18:53 +0200
Message-ID: <4FF1BB8F.8010803@neclab.eu>
Date: Mon, 2 Jul 2012 17:17:35 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: Richard Alimi <rich@velvetsea.net>
References: <4F8BE443.9050903@telecomitalia.it> <20120514061451.GA3136@gw01.ehlo.wurstkaes.de> <CA+cvDab1XR40W7FBHhDNOTTag7tvSihVe7BSMVbAP6W-Qtk91A@mail.gmail.com> <4FF1B8CB.7090005@neclab.eu>
In-Reply-To: <4FF1B8CB.7090005@neclab.eu>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Cc: draft-ietf-alto-protocol@tools.ietf.org, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [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, 02 Jul 2012 15:17:52 -0000

Adding something to my last email, after an offline discussion with 
Sebastian:

[...]
>>>
>>> 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.
>>
>> At least in the initial discussions of ALTO, there was mention about
>> using these for addresses other than IP addresses, such as e.164
>> numbers.  That said, I haven't seen any concrete use cases for
>> anything other than IP addresses or things that can map to IP
>> addresses.
>>
>> I don't intend to start a debate on the requirements document at this
>> stage, but I'm a bit hesitant to say that extensions MUST do this.  I
>> completely agree that those proposing extensions should be thinking
>> about this, but tend to think that MUST is too strong.  How about
>> extending 7.5.3.1 to state "extension documents defining a new Address
>> Type SHOULD also document a mechanism to map addresses of the new type
>> to IPv4 and/or IPv6 addresses prefixes."
>
> A SHOULD is fine, as it implies that people must say why they are not
> specifying a mapping mechanism.

Thinking twice about it:
The requirements are actually crisp about that: The MUST document such a 
mapping. Therefore we should have it this way in the protocol.
Such an extension is sort of useless, at least by today's measures, if 
there is no mapping mechanism to IPV4/IPv6 addresses.

   Martin

-- 
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 sabine.randriamasy@alcatel-lucent.com  Mon Jul  2 08:20:55 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 E5D9E21F86EC for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 08:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 SfEGzm7-caxn for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 08:20:54 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [62.23.212.56]) by ietfa.amsl.com (Postfix) with ESMTP id 909D621F86EB for <alto@ietf.org>; Mon,  2 Jul 2012 08:20:53 -0700 (PDT)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q62FEQtq019571 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 2 Jul 2012 17:20:55 +0200
Received: from [172.27.204.47] (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; Mon, 2 Jul 2012 17:20:37 +0200
Message-ID: <4FF1BC40.7070807@alcatel-lucent.com>
Date: Mon, 2 Jul 2012 17:20:32 +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> <4FBA5B39.8040505@alcatel-lucent.com> <CA+cvDaagS11X_ktV-AnO4ppYyE52FSuFgeZhabqw4j9efGp8zg@mail.gmail.com>
In-Reply-To: <CA+cvDaagS11X_ktV-AnO4ppYyE52FSuFgeZhabqw4j9efGp8zg@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.83
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, 02 Jul 2012 15:20:56 -0000

Hi Rich,

Richard Alimi a écrit :
> On Mon, May 21, 2012 at 8:11 AM, Sabine Randriamasy
> <Sabine.Randriamasy@alcatel-lucent.com> wrote:
>   
>> 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.
>>     
>
> Given the concern over a large amount of duplicate text in the draft,
> I'd like to leave such a list out unless there are others in the WG
> that feel strongly that we should have it.
>   
Sure, I think we have agreed upon this.
>   
>>>> -----------------------------------------------------
>>>> 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.
>>     
>
> I think we can expand this sentence to mention some existing examples.
>   
thanks
>  As far as arguing that there needs to be a standardized mechanism, I
> think the Problem Statement document should do that already.
>   
Ok. I figured 2-4 lines could help but don't want to overload the text. 
So refering to the pb statement is fine.
>   
>> *
>>     
>>>       
>>>> - §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"
>>     
>
> That sounds fine, but I'll just rephrase to say "or assume its default
> value which is documented in this specification."   I don't think
> normative language is needed there, since the instruction applies to
> the document authors/editors/WG and not the implementers.
>   
Ok
>   
>>> 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".
>>     
>
> That sounds fine to me. We'll add a hint here.
>   
Thanks
>   
>> 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 sebi@gw01.ehlo.wurstkaes.de  Mon Jul  2 08:28:18 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 A73F021F86EF for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 08:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.136
X-Spam-Level: 
X-Spam-Status: No, score=-2.136 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 M9wrkEGQqbb9 for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 08:28:17 -0700 (PDT)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [188.246.4.151]) by ietfa.amsl.com (Postfix) with ESMTP id 182AE21F85D2 for <alto@ietf.org>; Mon,  2 Jul 2012 08:28:14 -0700 (PDT)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1SliXS-0000AH-L5; Mon, 02 Jul 2012 17:27:46 +0200
Date: Mon, 2 Jul 2012 17:27:46 +0200
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: Richard Alimi <rich@velvetsea.net>
Message-ID: <20120702152746.GU5342@gw01.ehlo.wurstkaes.de>
References: <4F8BE443.9050903@telecomitalia.it> <20120514061451.GA3136@gw01.ehlo.wurstkaes.de> <CA+cvDab1XR40W7FBHhDNOTTag7tvSihVe7BSMVbAP6W-Qtk91A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+cvDab1XR40W7FBHhDNOTTag7tvSihVe7BSMVbAP6W-Qtk91A@mail.gmail.com>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: draft-ietf-alto-protocol@tools.ietf.org, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [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, 02 Jul 2012 15:28:18 -0000

Hi Rich,

I need some more time to comment on the other issues, but let me write
about one thing before I forget it again :)

> >     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.
> 
> At least in the initial discussions of ALTO, there was mention about
> using these for addresses other than IP addresses, such as e.164
> numbers.  That said, I haven't seen any concrete use cases for
> anything other than IP addresses or things that can map to IP
> addresses.
> 
> I don't intend to start a debate on the requirements document at this
> stage, but I'm a bit hesitant to say that extensions MUST do this.  I
> completely agree that those proposing extensions should be thinking
> about this, but tend to think that MUST is too strong.  How about
> extending 7.5.3.1 to state "extension documents defining a new Address
> Type SHOULD also document a mechanism to map addresses of the new type
> to IPv4 and/or IPv6 addresses prefixes."


I propose to write in 7.5.3.1:

"Extension documents may define additional Address Types and the 
corresponding mechanisms to map these adresses from/to IPv4/IPv6
addresses/prefixes."

That way you neither have to contradict nor reinforce the requirements
document.


Thanks,
Sebastian

From sebi@gw01.ehlo.wurstkaes.de  Mon Jul  2 08:44:45 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 C1FC921F8631 for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 08:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.192
X-Spam-Level: 
X-Spam-Status: No, score=-2.192 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 yFfsRPJsljea for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 08:44:45 -0700 (PDT)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [188.246.4.151]) by ietfa.amsl.com (Postfix) with ESMTP id 3991821F850B for <alto@ietf.org>; Mon,  2 Jul 2012 08:44:42 -0700 (PDT)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1Slin9-0000BF-Qp; Mon, 02 Jul 2012 17:43:59 +0200
Date: Mon, 2 Jul 2012 17:43:59 +0200
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: Richard Alimi <rich@velvetsea.net>
Message-ID: <20120702154359.GV5342@gw01.ehlo.wurstkaes.de>
References: <4F8BE443.9050903@telecomitalia.it> <4FAD5745.2060009@alcatel-lucent.com> <CA+cvDab3P0-68m6+mZ+4K0FedJ7_MK6SGXhD2kQKupXuCDLgDw@mail.gmail.com> <CA+cvDaZJ-RdJKf9mSTP0qbz3vS1mK28XQYpzpfQ69EZbMCF_5A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CA+cvDaZJ-RdJKf9mSTP0qbz3vS1mK28XQYpzpfQ69EZbMCF_5A@mail.gmail.com>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: 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, 02 Jul 2012 15:44:45 -0000

Sabine, Rich,


> >> 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.

In RFC 5693 we have defined the term "resource provider" (and many more,
maybe we should check the protocol draft again for correct usage of the
ALTO terminology?).

Btw. "Content Location" would IMO not be general enough, as we could use
ALTO also, e.g., to find a "good" media relay for VoIP NAT traversal.


Thanks
Sebastian

From richard.alimi@gmail.com  Mon Jul  2 10:38:10 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 DF19211E809C for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 10:38:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.427,  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 ML7xkSYU0cY1 for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 10:38:10 -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 0B3B321F8737 for <alto@ietf.org>; Mon,  2 Jul 2012 10:38:10 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so8095943pbc.31 for <alto@ietf.org>; Mon, 02 Jul 2012 10:38:15 -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=AJHHR5Jq54lIq+G5+bZhw/6SQ6H9HRkR+nd92TNUnzw=; b=MunsgPuJHUWlh+FVdlmrFuwGzTTDK+d7QZIN1pThC+xynbo6M70SAaer4ESa6pvxx0 fvXM9iZ6QOxfJGiSdw/EDdmlKUeXtRWECtx273qto7u5buXAf1deT/87YEudd6iYw9/T vQzBitU0/P2Gl2Ll8cu27C3Uc6y05A3DRjPzU7e7dJNbWhmXXT/djSltYi7h3FhBMncf 7eByi7k3aisi38Z2DWrjmGonMqpm5PmAMF1UHfnD9AqGOy0X1qJOZtjeDLfdnfI0Qrok yZB2yhInMgnKcBwHybMM8vh+2klcKMPgajSiCsURqMB8XYthB6dJQawcWDSBr74IlXEC 6qeA==
Received: by 10.68.211.41 with SMTP id mz9mr16759pbc.12.1341250695615; Mon, 02 Jul 2012 10:38:15 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.143.28.8 with HTTP; Mon, 2 Jul 2012 10:37:55 -0700 (PDT)
In-Reply-To: <4FF1B72C.4000209@neclab.eu>
References: <4FF1B72C.4000209@neclab.eu>
From: Richard Alimi <rich@velvetsea.net>
Date: Mon, 2 Jul 2012 10:37:55 -0700
X-Google-Sender-Auth: KQv783f9exd5zaaTOSSbjxFkIzk
Message-ID: <CA+cvDaZvZAE2yUdvM3i09QEccghMpsEZbV3DAz3JVX7e+jJapA@mail.gmail.com>
To: Martin Stiemerling <martin.stiemerling@neclab.eu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: alto@ietf.org
Subject: Re: [alto] Way forward for the Resdistribution
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, 02 Jul 2012 17:38:11 -0000

The material has been migrated to another document locally, but it
isn't yet ready for submission.    I don't think it should be
completely abandoned, but in my opinion the priority is lower than
getting the base protocol.  As was mentioned in the discussion w.r.t.
requirements, there are some things that it provides such as
guidelines on which clients should make use of the information and for
how long (above and beyond what we get for free from HTTP caching).

With your AD hat on, do we need the additional document to be
explicitly mentioned in the charter?

Rich

On Mon, Jul 2, 2012 at 7:58 AM, Martin Stiemerling
<martin.stiemerling@neclab.eu> wrote:
> Hi all,
>
> I have just read the ALTO protocol slides of the meeting in Paris and do
> wonder what has ultimately happened to the redistribution, as the slide
> state:
>
> "Will be submitted as separate draft that may make use of JOSE"
> (http://www.ietf.org/proceedings/83/slides/slides-83-alto-2.pdf)
>
> This functionality is gone from the base protocol, but we do not have any
> replacement insight. Do we completely abandon this?
>
> Thanks,
>
>   Martin
> --
> 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 haiyong.xie@huawei.com  Mon Jul  2 10:57:56 2012
Return-Path: <haiyong.xie@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 10E0C11E80E2; Mon,  2 Jul 2012 10:57:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, 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 9vtk7eBdNB3S; Mon,  2 Jul 2012 10:57:55 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id F1B8511E80C1; Mon,  2 Jul 2012 10:57:54 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHJ52964; Mon, 02 Jul 2012 13:58:00 -0400 (EDT)
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 2 Jul 2012 10:56:08 -0700
Received: from [127.0.0.1] (10.193.38.33) by smtpsus.huawei.com (10.193.5.134) with Microsoft SMTP Server id 14.1.323.3; Mon, 2 Jul 2012 10:56:02 -0700
Message-ID: <4FF1DF7B.9080500@huawei.com>
Date: Mon, 2 Jul 2012 10:50:51 -0700
From: Haiyong Xie <haiyong.xie@huawei.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8
MIME-Version: 1.0
To: "Y. Richard Yang" <yry@cs.yale.edu>
References: <748A482AA35F7A4A8BD26465029B8C4A1B7C49EC@dfweml509-mbx.china.huawei.com> <4FF11869.1010408@cs.yale.edu>
In-Reply-To: <4FF11869.1010408@cs.yale.edu>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.193.38.33]
X-CFilter-Loop: Reflected
Cc: "altoext@ietf.org" <altoext@ietf.org>, "alto@ietf.org" <alto@ietf.org>, Andreas Voellmy <andreas.voellmy@yale.edu>, Hongtao Yin <hongtao.yin@huawei.com>
Subject: Re: [alto] FW: New Version Notification for draft-xie-alto-sdn-extension-use-cases-00.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, 02 Jul 2012 17:57:56 -0000

Hi Richard,

Thanks very much for your comments. Please see my inline responses below.

On 07/01/2012 08:41 PM, Y. Richard Yang wrote:
> Hi Haiyong, Tina, Hongtao, and Diego,
>
> A good document! Here are some quick feedback:
>
> - One take-away message that the document appears trying to convey is
> Vertical (V) vs Horizontal (H) architectures. My understanding of your
> definition
> is that V is a one-to-many setting, i.e., one ALTO Server to m SDN
> Controllers (SC),
> while H is one-to-one, i.e., one ALTO Server to one SC. 

The H architecture implies that the network should NOT be segmented,
i.e., there exists only one SC; otherwise, the network will have
multiple ALTO servers, each is working with corresponding SC only, but
without exchanging information among multiple ALTO servers (we do not
have a protocol to do so yet).

> Why is the information flow
> in H only SC <- ALTO S (Sec. 3.2), not the other way around? In an SDN
> setting, I
> agree that an SC should already collect fine-grained, dynamic
> information for its
> controlled domain. ALTO current does not define how its information is
> collected/provisioned, but SC provides a good source (Sec. 4.3.2) of
> information
> for ALTO Server to aggregate and conduct abstraction. I see good value
> in this
> direction of information flow. I feel that this is mostly a common
> problem across H
> and V. Hence I would not discard the H architecture right away. 

Adding SC->ALTO S in the H architecture does not add much new value.
Since the ALTO Server is working for the specific SDN domain only, the
more important of problem, i.e., how to coordinate multiple SCs in the
whole network, remains unsolved. Plus, in the H architecture, we really
do not have to differentiate ALTO S from SC, as the former could be
easily integrated into the latter (since SC has the most updated network
information already).

I agree that generally speaking, adding the SC->ALTO S information flow
is pretty helpful to ALTO, as this enables ALTO to collect network
information, which has not been addressed previously yet. However, we
believe that the main distinctions between the V and H architectures
include not only whether we have the SC->ALTO S flow, but also how we
should decompose the ALTO related functionalities and design an
efficient, evolvable architecture to support the growth of both SDN and
ALTO.

> A concern is
> whether we are ready to define the SC -> ALTO Server information flow,
> given the "early-stageness" of SDN. A related general comment is that
> it maybe quite
> helpful to extract common problems (e.g., unknown/dynamic network cost as
> you mentioned) and new possibilities for ALTO when introducing SDN,
> instead of
> a specific setting of a network being partitioned into many
> sub-networks in a V
> architecture. What do you think? 

Partitioning the network and defining common problems/possibilities of
SC->ALTO S information flow are two orthogonal problems. We believe that
both are equally important. However, the first problem (partitioning the
network) will largely determine what the SDN+ALTO architecture looks
like, while the second problem is more about the types of detailed
network information, its format, etc. From this perspective, it seems
that the first problem is more important -- if the architecture is not
set right at the beginning, to fix it at some later time would be
difficult and costly. This draft is mainly focusing on the first
problem, we may need another draft dedicated to the second problem.

> A curious question, does the ALTO servers
> (as well as the SC) in H form some kind of mesh (peering) among
> themselves?

Given current status of ALTO, we assumed that there is no peering among
ALTO servers. However, if ALTO server peering becomes available and
adopted, then the H architecture (and the SC->ALTO S flow) would make
much more sense, which allows us to compare the two architectures more
thoroughly.

>
> - The document seems to imply some kind of exclusive SC/net app
> setting: either
> SC or net app, but not both. Do I misunderstand it? This depends on
> how one
> define the scope of SC. There can still be net apps running. Does it
> make sense to
> include (explicitly) the net apps into your discussions/figures to
> include 4 types
> of entities: devices, SC, ALTO Server, and net apps? 

Actually we did not mean to imply any kind of exclusive SC/net app
setting. We need to update the draft to make it more explicit. In the
figures, we did not include the net apps for the sake of simplicity.
When we update the draft, we will add them to the figures.

> I like your distinction between
> SDN-aware and SDN-unaware apps. I am not sure I fully agree or
> understand your
> statement that SDN-aware apps would prefer direct communications with
> SC, but
> this will be an important architecture discussion at the ALTO meeting.

What we have in mind is that since some apps are SDN aware, then it may
prefer to behave differently from SDN unware apps (which does not
directly communicate with SC), i.e., directly communicate with SC, which
allows more flexibility and new possibilities of leveraging the SDN
capabilities. Apparently discussions would be very helpful, and I am
sure it would be a very interesting discussion about SDN-awareness and
-unawareness at the ALTO meeting.

>
> Thanks.
>
> Richard
>
> On 6/29/12 6:15 AM, Haiyong Xie wrote:
>> Hi All,
>>
>> This is a proposal on the interaction between ALTO and SDN we'd like
>> to discuss at our next meeting in Vancouver. This draft replaces the
>> older submission draft-xie-alto-sdn-use-cases-01.txt which was
>> withdrawn already.
>>
>> Comments or discussions are extremely welcome and appreciated.
>>
>> Best regards,
>> Haiyong
>>
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> Sent: Thursday, June 28, 2012 3:07 PM
>> To: Haiyong Xie
>> Cc: diego@tid.es; Hongtao Yin; Tina TSOU
>> Subject: New Version Notification for
>> draft-xie-alto-sdn-extension-use-cases-00.txt
>>
>>
>> A new version of I-D, draft-xie-alto-sdn-extension-use-cases-00.txt
>> has been successfully submitted by Haiyong Xie and posted to the
>> IETF repository.
>>
>> Filename:     draft-xie-alto-sdn-extension-use-cases
>> Revision:     00
>> Title:         Use Cases for ALTO with Software Defined Networks
>> Creation date:     2012-06-28
>> WG ID:         Individual Submission
>> Number of pages: 28
>> URL:            
>> http://www.ietf.org/internet-drafts/draft-xie-alto-sdn-extension-use-cases-00.txt
>> Status:         
>> http://datatracker.ietf.org/doc/draft-xie-alto-sdn-extension-use-cases
>> Htmlized:       
>> http://tools.ietf.org/html/draft-xie-alto-sdn-extension-use-cases-00
>>
>>
>> Abstract:
>>     The introduction of SDN fundamentally changes the way that the ALTO
>>     works.  This draft describes the Vertical Architecture and the
>>     Horizontal Architecture allowing coherent coexistence of application
>>     layer traffic optimization (ALTO) with software defined network
>>     (SDN).  Unique requirements for design and operations are identified
>>     and summarized, suggesting that the Vertical Architecture allows
>>     better division, management, flexibility, privacy control and long-
>>     term evolution of the network.  We also define the main interactions
>>     and information flows, and present a set of use cases to illustrate
>>     how we extend ALTO to support SDN, in the Vertical Architecture.
>>
>>                                                                                   
>>
>>
>> The IETF Secretariat
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>
> .
>


From richard.alimi@gmail.com  Mon Jul  2 11:10:11 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 52CAB21F875A for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 11:10:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[AWL=0.366,  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 1PEn3ZTfHv+G for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 11:10:10 -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 8A7B721F8752 for <alto@ietf.org>; Mon,  2 Jul 2012 11:10:10 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so4887369ggn.31 for <alto@ietf.org>; Mon, 02 Jul 2012 11:10:16 -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=I9lNNhM3BrobaEm6gkI/uSt7YRtQAabYyzzwpvgSpFA=; b=KBy2I9a1L6NSYcEBGE/gBzdQzGvvr/qyJQn1W1nYmvBsbqNQmJYzsXCEYnZsz8kIbC bUjx0cN8uBKcJ/tRkthZYQNlbotgfh6yCAZoI4bLD1/Pr0R0QSRWnNDvKUdH1EovQbXx XnYCTzDX/vBqpUScdw3t3eDZLIgmp7X0oeDs9mXiGxCkEG11Le72MQLhNdd38K30KW2x Fev2riWXBHUJUp3PR0hldBmEI/Y9UNwBqvalrNjWDPy/2pkdSOKDEPar7gvBRjmCfwdv gwSjZTzY05pztSF48DKqbWbHnPXiaFu+FZrwk3tKUpJJ2FZa23gt4wnk0NMX1GeQdMZd 6S7A==
Received: by 10.68.231.8 with SMTP id tc8mr175553pbc.140.1341252615537; Mon, 02 Jul 2012 11:10:15 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.143.28.8 with HTTP; Mon, 2 Jul 2012 11:09:51 -0700 (PDT)
In-Reply-To: <20120702154359.GV5342@gw01.ehlo.wurstkaes.de>
References: <4F8BE443.9050903@telecomitalia.it> <4FAD5745.2060009@alcatel-lucent.com> <CA+cvDab3P0-68m6+mZ+4K0FedJ7_MK6SGXhD2kQKupXuCDLgDw@mail.gmail.com> <CA+cvDaZJ-RdJKf9mSTP0qbz3vS1mK28XQYpzpfQ69EZbMCF_5A@mail.gmail.com> <20120702154359.GV5342@gw01.ehlo.wurstkaes.de>
From: Richard Alimi <rich@velvetsea.net>
Date: Mon, 2 Jul 2012 11:09:51 -0700
X-Google-Sender-Auth: 9BoJ9GROsV52FXLOuGB04D0HcZ4
Message-ID: <CA+cvDaYdzoGub0gvwbV2EfvCTmnS73Q5gSf+pvDH-sCsRjtPQg@mail.gmail.com>
To: Sebastian Kiesel <ietf-alto@skiesel.de>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 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, 02 Jul 2012 18:10:11 -0000

On Mon, Jul 2, 2012 at 8:43 AM, Sebastian Kiesel <ietf-alto@skiesel.de> wrote:
> Sabine, Rich,
>
>
>> >> 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.
>
> In RFC 5693 we have defined the term "resource provider" (and many more,
> maybe we should check the protocol draft again for correct usage of the
> ALTO terminology?).

For the specific point about use of the word "peer", when looking
through the -11 version, the primary use is in section 8 where we are
explicitly talking about p2p use cases. That use seems fine to me.
There are a couple of places where 'peer' may be somewhat limiting
(e.g., section 11.2) and should be changed.

We can certainly do an inventory on terminology to see if anything
else from RFC5693 should be applied.  I'm pretty sure it won't just be
substituting "endpoints" with either "resource consumer" or "resource
provider" though, since that depends quite a bit on how the
application uses ALTO information, and what the costs actually
represent. That is, we can't simply say that that a resource consumer
is choosing a resource provider.  It's conceivable that the resource
provider could be doing the choosing in a push-based protocol.  As a
slightly more interesting example, what if I also wanted to try and
reduce latency for ACKs in the opposite direction to protect myself
against asymmetric routing - then then I'd be querying a latency map
for the cost from the resource consumer to the resource provider.   In
the ALTO Protocol we try to simply express these as costs between
endpoints. It's an application-level concern about who does the
choosing, and making sure they are using the costs appropriately.

All that said, I think we do need to improve the protocol draft to
explicitly say how "endpoint" relates to "resource consumer" and
"resource provider" which is mentioned in other documents.  How about
the following:

Add this to Section 2.1.1:
  "An Endpoint Address is typically either the address of a Resource
Provider or Resource Consumer."

Add change this text in Section 5:
  "Each Path Cost is the end-to-end cost from the source to the destination."
to instead read:
  "Each Path Cost is the end-to-end cost from the source to the
destination.  For example, if the cost is expected correlated with
throughput, a typical application concerned with bulk data transfer
may use the Resource Provider as the source, and Resource Consumer as
the destination."

>
> Btw. "Content Location" would IMO not be general enough, as we could use
> ALTO also, e.g., to find a "good" media relay for VoIP NAT traversal.

Agree.

>
>
> Thanks
> Sebastian

From richard.alimi@gmail.com  Mon Jul  2 11:35:21 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 9836611E80EF for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 11:35:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.543
X-Spam-Level: 
X-Spam-Status: No, score=-2.543 tagged_above=-999 required=5 tests=[AWL=0.207,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 TzrUl3y3HpP4 for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 11:35:20 -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 E1D2911E80D1 for <alto@ietf.org>; Mon,  2 Jul 2012 11:35:19 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so8160738pbc.31 for <alto@ietf.org>; Mon, 02 Jul 2012 11:35:25 -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=9M75Yj+X8XYuFce76f4b99yR8buRBmUMCDnH+N63/Ew=; b=FthtkiaLBAXNfvH8a+oD7T26bkYo6T5qDXyq7nf2mZwToc2wdl9Em3CN+w6YQ4nJwz rKaAJCJoAyXMvSZnuNd+Lc0GNRXPhb1lGtXG+4yD0g/Fa2kYD+s8YCszb3vAAPkAfF0I rElOzAkUggTDGR5t94uQSh4abe6dQ+UJWxwFvgYAt8AUBLerfwVQr3BZa1Zx7u/vbwUU HTCs2a6q8Qcg0C7//6z3SHfJHeHBwrd96CrNhGoPw3T52VVy1yKUItct5BMuKmi5fMe9 +T9COgRqbFSfkbeH5hSirq9GsbnuVt2k7zxFC+ZRCKI2IljjCB/GPjh55XZbZmnE196K RoEA==
Received: by 10.68.231.8 with SMTP id tc8mr369076pbc.140.1341254125510; Mon, 02 Jul 2012 11:35:25 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.143.28.8 with HTTP; Mon, 2 Jul 2012 11:35:05 -0700 (PDT)
In-Reply-To: <4FF1B8CB.7090005@neclab.eu>
References: <4F8BE443.9050903@telecomitalia.it> <20120514061451.GA3136@gw01.ehlo.wurstkaes.de> <CA+cvDab1XR40W7FBHhDNOTTag7tvSihVe7BSMVbAP6W-Qtk91A@mail.gmail.com> <4FF1B8CB.7090005@neclab.eu>
From: Richard Alimi <rich@velvetsea.net>
Date: Mon, 2 Jul 2012 11:35:05 -0700
X-Google-Sender-Auth: nH2I66Clfs4j8kpd_-4JHGUi2mw
Message-ID: <CA+cvDabEaB8N5835xuECtqKMejLVaOk5qRgeTnAimL=6gCVHUA@mail.gmail.com>
To: Martin Stiemerling <martin.stiemerling@neclab.eu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-ietf-alto-protocol@tools.ietf.org, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [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, 02 Jul 2012 18:35:21 -0000

On Mon, Jul 2, 2012 at 8:05 AM, Martin Stiemerling
<martin.stiemerling@neclab.eu> wrote:
> [writing with no Area Director hat on, i.e., as a random community member]

Good to have you back :)

> Hi Richard, all,
>
> On 07/02/2012 08:38 AM, Richard Alimi wrote:
> [...]
>
>
>>> 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, ...)
>>
>>
>> It needs something more than just an I-D since that is a pretty low bar.
>
>
> You can specify 'protocol specification' or 'expert review' as the bar for
> an extension.
> See also RFC 5226 for a discussion of this:
> http://tools.ietf.org/html/rfc5226
>
>
>>
>> Do people think a registry is needed for this?  If not, perhaps we can
>> just make this more explicit that it needs to be a standards-track
>> RFC.
>
>
> There should be a registry where you can add additional address types.
> Otherwise it is really hard to get new address types in a clean way into the
> protocol.
> A registry allows also to keep track about all existing address types (out
> of the ALTO protocol and what comes later on).

Right - okay. We'll add an Address Type registry.  That said, it'd be
really nice to point to an existing registry. I think we'd need the
following for such a registry:
(1) A textual string for an address type itself
(2) A specification (preferably a pointer to one) for how to serialize
and deserialize a textual address of that type.
(3) (maybe, depending on the result of the discussion below) a
statement of how an address type can be mapped into IPv4/v6 addresses.

However, when browsing through the available IANA registries I didn't
see one that really matched those requirements.  Does anyone have a
better option before we go about defining our own?

>>
>>>>     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.
>>
>>
>> At least in the initial discussions of ALTO, there was mention about
>> using these for addresses other than IP addresses, such as e.164
>> numbers.  That said, I haven't seen any concrete use cases for
>> anything other than IP addresses or things that can map to IP
>> addresses.
>>
>> I don't intend to start a debate on the requirements document at this
>> stage, but I'm a bit hesitant to say that extensions MUST do this.  I
>> completely agree that those proposing extensions should be thinking
>> about this, but tend to think that MUST is too strong.  How about
>> extending 7.5.3.1 to state "extension documents defining a new Address
>> Type SHOULD also document a mechanism to map addresses of the new type
>> to IPv4 and/or IPv6 addresses prefixes."
>
>
> A SHOULD is fine, as it implies that people must say why they are not
> specifying a mapping mechanism.

I'll save my reply for your later followup.

>>
>>>
>>>      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.
>>
>>
>> Do you have any thoughts on what this might look like?
>
>
> An appropriate error message with a path name delivered through this would
> good. However, this is just a proposal.
>
>
>>
>>>      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.
>>
>>
>> Moving this to the deployment considerations document sounds reasonable to
>> me.
>
>
> +1
>
>
>>
>>>>     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-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.
>>
>>
>> I tend to think it's best to leave this one as partially compliant for
>> now, and leave the additional expiration field for when there is an
>> extension to support redistribution (the section that was removed in
>> -11).  Any disagreement with that?
>
>
> Not from my side.
>
>
>>
>>>
>>>>     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
>>
>>
>> Yeah - I'm personally okay with this current state, since we
>> consciously removed the section on Redistribution and left that for an
>> extension.
>
>
> If we allow to be partially compliant, we should at least note that the
> missing points are part of a future redistribution mechanism and therefore
> not specified in the current ALTO protocol.

Sounds good to me.  We can add a note here.

>
>
>>
>>>
>>>>     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
>>
>>
>> The use of JSON and Section 7.2.7 also helps with extensions.
>>
>>>>     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
>>
>>
>> Yeah.  There was a discussion when going to the REST-ful approach
>> about whether we wanted any explicit version numbers or not.  The idea
>> was that we didn't need an ALTO version number exposed to applications
>> if we used media types appropriately.  Using media types like you
>> suggested is certainly one approach.
>
>
> Irrespectively of what mechanisms is being used, this protocol needs
> versioning support. However, I'm not sure that media-types are the best way
> forward for this.
> What would be a different approach when using media types?

Do you mean a different approach *than* using media types?  One other
option would be to revert revert back to what we had before, which is
have an explicit field in each and every response.

Here's one pointer to mailing list discussions about protocol
versioning and media types:
  http://www.mail-archive.com/alto@ietf.org/msg00609.html
I'll note that our AD at the time (Lisa) was one of the people
suggesting we use content negotiation to provide protocol versioning.

My preference would be to not re-hash the merits of protocol
versioning unless we think there is a clear technical advantage over
what we have now.

>>
>>>> 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.
>>
>>
>> We also had a discussion about this in the protocol overhaul for
>> making it REST-ful.  The guidance we received there was to not repeat
>> details from RFC2616.  I'm not sure I see much utility in adding
>> specifics in the ALTO protocol document, since it would basically
>> amount to saying "If you think you are overloaded, you are free to
>> return a 503."  Then, if we were to add that, people would ask "you
>> gave me guidance on using 503, but you didn't tell me when I should or
>> should not use chunked transfer encoding.. how about that??"  The idea
>> was that the statements in Section 7.2, as well as some intelligence
>> on behalf of implementers on how to apply RFC2616, would answer all of
>> these questions.
>
>
> That is not a good way of specifying things. There is no need to say how a
> 503 response looks like, but it is definitely good to say when an ALTO
> protocol must reply with such a code. "intelligence ...of implementers" will
> cause ALTO protocol implementations that do not interoperate.

If we want to make revisions here, can you give some guidance on where
we should recommend certain usage of HTTP and where we shouldn't?
Should it be just additional text to ensure that we satisfy the
requirements on overload control, or additional guidance on how to to
employ other parts of HTTP such as transfer encoding, caching, when to
use redirects, etc?

>>>> 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.
>>
>>
>> Agree. See comment above.
>
>
> Give at least guidance where to read on to protect against such threads.
> Otherwise this specification is incomplete.
>
>   Martin
>
>
> --
> 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 richard.alimi@gmail.com  Mon Jul  2 11:41:31 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 6F4D111E8111 for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 11:41:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.184,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 8l2jaI94gT3k for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 11:41: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 879A411E8105 for <alto@ietf.org>; Mon,  2 Jul 2012 11:41:30 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so8169899pbc.31 for <alto@ietf.org>; Mon, 02 Jul 2012 11:41:36 -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=pZcEsE0Z0T8grFdugbvMylCg94EvSyew2E1MyC2ysNM=; b=wr/iXRjtYJvp8ox77/jd645BjW+2+a/kcavnontuVAqgQx+DevS7QAZz9V/JkQ9H3N HMhnF+3Zw/wTwJXT9XaulHUAUAu8syff752aL3Z3k8+JD3ovY9mvuUwWD9bhRc5jIWUf 7G55pdXocvewqMZKoBrFTerIlF1lcMCTTIR5SxGroCYYIxkqXfjkodA1RlHmtXbekw8V NaPx+Wg9wLwnKQ9p1H546yJnqUkNXBGPiQPIEDFv5XDiBDGJayNzpz3WwSM0v9qS+J5a +jgsH8oNx2dmIZmWBM4pfBU2E3qODvX/89Xq+IOZ5IfVXkMCyacFSYFTe8EWyPmYaG62 69QQ==
Received: by 10.68.217.3 with SMTP id ou3mr439510pbc.117.1341254496249; Mon, 02 Jul 2012 11:41:36 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.143.28.8 with HTTP; Mon, 2 Jul 2012 11:41:15 -0700 (PDT)
In-Reply-To: <20120702152746.GU5342@gw01.ehlo.wurstkaes.de>
References: <4F8BE443.9050903@telecomitalia.it> <20120514061451.GA3136@gw01.ehlo.wurstkaes.de> <CA+cvDab1XR40W7FBHhDNOTTag7tvSihVe7BSMVbAP6W-Qtk91A@mail.gmail.com> <20120702152746.GU5342@gw01.ehlo.wurstkaes.de>
From: Richard Alimi <rich@velvetsea.net>
Date: Mon, 2 Jul 2012 11:41:15 -0700
X-Google-Sender-Auth: p72bi378lFMfkU5wVuvZaFbJejA
Message-ID: <CA+cvDaYmWrcTEiWNLYhphH9x6D=KvO2tacReQNJLZVn-KuBxwQ@mail.gmail.com>
To: Sebastian Kiesel <ietf-alto@skiesel.de>
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-ietf-alto-protocol@tools.ietf.org, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [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, 02 Jul 2012 18:41:31 -0000

On Mon, Jul 2, 2012 at 8:27 AM, Sebastian Kiesel <ietf-alto@skiesel.de> wrote:
> Hi Rich,
>
> I need some more time to comment on the other issues, but let me write
> about one thing before I forget it again :)
>
>> >     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.
>>
>> At least in the initial discussions of ALTO, there was mention about
>> using these for addresses other than IP addresses, such as e.164
>> numbers.  That said, I haven't seen any concrete use cases for
>> anything other than IP addresses or things that can map to IP
>> addresses.
>>
>> I don't intend to start a debate on the requirements document at this
>> stage, but I'm a bit hesitant to say that extensions MUST do this.  I
>> completely agree that those proposing extensions should be thinking
>> about this, but tend to think that MUST is too strong.  How about
>> extending 7.5.3.1 to state "extension documents defining a new Address
>> Type SHOULD also document a mechanism to map addresses of the new type
>> to IPv4 and/or IPv6 addresses prefixes."
>
>
> I propose to write in 7.5.3.1:
>
> "Extension documents may define additional Address Types and the
> corresponding mechanisms to map these adresses from/to IPv4/IPv6
> addresses/prefixes."
>
> That way you neither have to contradict nor reinforce the requirements
> document.

This sounds good to me.  Depending on what we do with a registry, it
may make sense to put this as one of the criteria for adding a new
entry instead.

>
>
> Thanks,
> Sebastian

From sebi@gw01.ehlo.wurstkaes.de  Mon Jul  2 13:22:18 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 46FCA11E80C4 for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 13:22:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[AWL=-0.262, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_14=0.6]
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 7ZMd9VCwgRRr for <alto@ietfa.amsl.com>; Mon,  2 Jul 2012 13:22:17 -0700 (PDT)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [188.246.4.151]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB4E11E8080 for <alto@ietf.org>; Mon,  2 Jul 2012 13:22:16 -0700 (PDT)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1Sln8V-0002hu-Be; Mon, 02 Jul 2012 22:22:19 +0200
Date: Mon, 2 Jul 2012 22:22:19 +0200
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: Richard Alimi <rich@velvetsea.net>
Message-ID: <20120702202219.GX5342@gw01.ehlo.wurstkaes.de>
References: <4F8BE443.9050903@telecomitalia.it> <4FAD5745.2060009@alcatel-lucent.com> <CA+cvDab3P0-68m6+mZ+4K0FedJ7_MK6SGXhD2kQKupXuCDLgDw@mail.gmail.com> <CA+cvDaZJ-RdJKf9mSTP0qbz3vS1mK28XQYpzpfQ69EZbMCF_5A@mail.gmail.com> <20120702154359.GV5342@gw01.ehlo.wurstkaes.de> <CA+cvDaYdzoGub0gvwbV2EfvCTmnS73Q5gSf+pvDH-sCsRjtPQg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+cvDaYdzoGub0gvwbV2EfvCTmnS73Q5gSf+pvDH-sCsRjtPQg@mail.gmail.com>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: 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, 02 Jul 2012 20:22:18 -0000

Hi Rich,

On Mon, Jul 02, 2012 at 11:09:51AM -0700, Richard Alimi wrote:
> We can certainly do an inventory on terminology to see if anything
> else from RFC5693 should be applied.  I'm pretty sure it won't just be
> substituting "endpoints" with either "resource consumer" or "resource
> provider" though, since that depends quite a bit on how the
> application uses ALTO information, and what the costs actually
> represent. 


> That is, we can't simply say that that a resource consumer
> is choosing a resource provider.

I would exactly say this. 

Or maybe, to be more precise: A resource consumer chooses - or asks a
third party to choose on behalf of it - one or several resource
providers from a set of candidate resource providers (and ALTO is
consulted in order to improve that decision).

However, it it is important that resource is not neccessarily a file or
content stream. Therefore, the above sentence does not imply that most
of the data flows from the resource provider(s) to the resource consumer!
Because we might have independent control and data connections
it would also be too simplistic to say the resource consumer
is the "connection/flow initiator", though most of the time this is true.


> It's conceivable that the resource
> provider could be doing the choosing in a push-based protocol.

If we have a push-based protocol, where one could send some
kind of information to one of several "sinks", I'd say that the
(ALTO-/RFC5693-)resources are these sinks, and the "pusher"
is the resource consumer, which consumes the sink-resource.


> As a
> slightly more interesting example, what if I also wanted to try and
> reduce latency for ACKs in the opposite direction to protect myself
> against asymmetric routing - then then I'd be querying a latency map
> for the cost from the resource consumer to the resource provider.   In
> the ALTO Protocol we try to simply express these as costs between
> endpoints. 

ack.

> It's an application-level concern about who does the
> choosing, and making sure they are using the costs appropriately.

Each application uses its own terminology and has specific ideas on who
assumes the roles of "client", "server", "peer", ...
My understanding of the ALTO terminology is that we can use it to
describe the (ALTO-relevant) features of an arbitrary protocol in
a uniform way. And in particular, I would describe the general
ALTO problem as:

We have 1 resource consumer and N candidate resource providers.
We want to have data flows between the resource consumer and
M < N resource providers. Therefore, we need to choose M out of N,
and ALTO is supposed to help on that decision.

> All that said, I think we do need to improve the protocol draft to
> explicitly say how "endpoint" relates to "resource consumer" and
> "resource provider" which is mentioned in other documents.  How about
> the following:
> 
> Add this to Section 2.1.1:
>   "An Endpoint Address is typically either the address of a Resource
> Provider or Resource Consumer."

Is it always the address of exactly one host (either r.prov. or r.cons.)?
Otherwise, the already defined term "host group descriptor" might make
sense?

> Add change this text in Section 5:
>   "Each Path Cost is the end-to-end cost from the source to the destination."
> to instead read:
>   "Each Path Cost is the end-to-end cost from the source to the
> destination.  For example, if the cost is expected correlated with
> throughput, a typical application concerned with bulk data transfer
> may use the Resource Provider as the source, and Resource Consumer as
> the destination."

change "a typical application concerned with bulk data transfer"
to "a typical application concerned with bulk data retrieval", then
we have one of the most important use cases as an example - though
the example does not reflect the full complexity of that issue ...

  S.

From yang.r.yang@gmail.com  Tue Jul  3 00:15:42 2012
Return-Path: <yang.r.yang@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 C706221F8602 for <alto@ietfa.amsl.com>; Tue,  3 Jul 2012 00:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.511
X-Spam-Level: 
X-Spam-Status: No, score=-2.511 tagged_above=-999 required=5 tests=[AWL=-0.135, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_14=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 LPFN6h5zQY2N for <alto@ietfa.amsl.com>; Tue,  3 Jul 2012 00:15:41 -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 789FF21F84F9 for <alto@ietf.org>; Tue,  3 Jul 2012 00:15:41 -0700 (PDT)
Received: by yenq13 with SMTP id q13so5456362yen.31 for <alto@ietf.org>; Tue, 03 Jul 2012 00:15: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:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=3SbGQd7WIQqcuqghRpk7ggZ2QSFeDyi76oGbgKYTDfg=; b=uz34aztAiVPsA/rogJzQwqbuVebvZb50ru9RgTv5EKGMBQlTXIO5qK8TtCSzDdl9bz B2cnE9LWC9P5cbRpK+5+wG1cjV6s8DaT2w7Bhzig78pqPcN51LD1T11oAEj3a/eF9dYh 9FrkjK5Bvor/wqwCtybV0HmgbqfQd6wO88aFXktuQlUrLe6eqBR6FNMACsLdKFz8iV2W kzWuohD4WHFmD2PfmIhaUjJ7DNL7wOozVXi5v5U+nkdsjzFaJYMsmW1yRK8KQfrIPgaV xmpx9U7T6cSnSbycFypNRfGku5RBopB1RGeznyKbj1mBrYa7hN0sBb39ecaiLfaXyYhM 7ffg==
MIME-Version: 1.0
Received: by 10.60.0.164 with SMTP id 4mr16947246oef.4.1341299748295; Tue, 03 Jul 2012 00:15:48 -0700 (PDT)
Sender: yang.r.yang@gmail.com
Received: by 10.76.86.136 with HTTP; Tue, 3 Jul 2012 00:15:48 -0700 (PDT)
In-Reply-To: <20120702202219.GX5342@gw01.ehlo.wurstkaes.de>
References: <4F8BE443.9050903@telecomitalia.it> <4FAD5745.2060009@alcatel-lucent.com> <CA+cvDab3P0-68m6+mZ+4K0FedJ7_MK6SGXhD2kQKupXuCDLgDw@mail.gmail.com> <CA+cvDaZJ-RdJKf9mSTP0qbz3vS1mK28XQYpzpfQ69EZbMCF_5A@mail.gmail.com> <20120702154359.GV5342@gw01.ehlo.wurstkaes.de> <CA+cvDaYdzoGub0gvwbV2EfvCTmnS73Q5gSf+pvDH-sCsRjtPQg@mail.gmail.com> <20120702202219.GX5342@gw01.ehlo.wurstkaes.de>
Date: Tue, 3 Jul 2012 15:15:48 +0800
X-Google-Sender-Auth: 3LT6D-5BVnAFFNDk-qUYMw45ia0
Message-ID: <CANUuoLqpJTQy6WbHjiX75YJmLEDV+yg1E_8-GX1okHOoH0CJdg@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: Sebastian Kiesel <ietf-alto@skiesel.de>
Content-Type: multipart/alternative; boundary=e89a8fb1ec7008d51104c3e7af7c
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, 03 Jul 2012 07:15:42 -0000

--e89a8fb1ec7008d51104c3e7af7c
Content-Type: text/plain; charset=ISO-8859-1

Hi Sebastian, Rich,

On Tuesday, July 3, 2012, Sebastian Kiesel wrote:
For example, the resource consumer may not ask, as
>
> Hi Rich,
>
> On Mon, Jul 02, 2012 at 11:09:51AM -0700, Richard Alimi wrote:
> > We can certainly do an inventory on terminology to see if anything
> > else from RFC5693 should be applied.  I'm pretty sure it won't just be
> > substituting "endpoints" with either "resource consumer" or "resource
> > provider" though, since that depends quite a bit on how the
> > application uses ALTO information, and what the costs actually
> > represent.
>
>
> > That is, we can't simply say that that a resource consumer
> > is choosing a resource provider.
>
> I would exactly say this.
>
> Or maybe, to be more precise: A resource consumer chooses - or asks a
> third party to choose on behalf of it - one or several resource
> providers from a set of candidate resource providers (and ALTO is
> consulted in order to improve that decision).


Using your good reasoning below, even the preceding sentence may have
subtlety: "ask" may imply some messages, but the app may not have a
message. How about remove "ask"?



> However, it it is important that resource is not neccessarily a file or
> content stream. Therefore, the above sentence does not imply that most
> of the data flows from the resource provider(s) to the resource consumer!
> Because we might have independent control and data connections
> it would also be too simplistic to say the resource consumer
> is the "connection/flow initiator", though most of the time this is true.
>
>
> > It's conceivable that the resource
> > provider could be doing the choosing in a push-based protocol.
>
> If we have a push-based protocol, where one could send some
> kind of information to one of several "sinks", I'd say that the
> (ALTO-/RFC5693-)resources are these sinks, and the "pusher"
> is the resource consumer, which consumes the sink-resource.
>
>
> > As a
> > slightly more interesting example, what if I also wanted to try and
> > reduce latency for ACKs in the opposite direction to protect myself
> > against asymmetric routing - then then I'd be querying a latency map
> > for the cost from the resource consumer to the resource provider.   In
> > the ALTO Protocol we try to simply express these as costs between
> > endpoints.
>
> ack.
>
> > It's an application-level concern about who does the
> > choosing, and making sure they are using the costs appropriately.
>
> Each application uses its own terminology and has specific ideas on who
> assumes the roles of "client", "server", "peer", ...
> My understanding of the ALTO terminology is that we can use it to
> describe the (ALTO-relevant) features of an arbitrary protocol in
> a uniform way. And in particular, I would describe the general
> ALTO problem as:
>
> We have 1 resource consumer and N candidate resource providers.
> We want to have data flows between the resource consumer and
> M < N resource providers. Therefore, we need to choose M out of N,
> and ALTO is supposed to help on that decision.
>
> > All that said, I think we do need to improve the protocol draft to
> > explicitly say how "endpoint" relates to "resource consumer" and
> > "resource provider" which is mentioned in other documents.  How about
> > the following:
> >
> > Add this to Section 2.1.1:
> >   "An Endpoint Address is typically either the address of a Resource
> > Provider or Resource Consumer."


Suppose we want to simplify the definition by removing "address" from the
the above.
Then we have "An Endpoint is typically either a Resource Provider or
Resource
Consumer." How does this read? What is an atypical case?

>
> Is it always the address of exactly one host (either r.prov. or r.cons.)?
> Otherwise, the already defined term "host group descriptor" might make
> sense?
>
> > Add change this text in Section 5:
> >   "Each Path Cost is the end-to-end cost from the source to the
> destination."
> > to instead read:
> >   "Each Path Cost is the end-to-end cost from the source to the
> > destination.  For example, if the cost is expected correlated with
> > throughput, a typical application concerned with bulk data transfer
> > may use the Resource Provider as the source, and Resource Consumer as
> > the destination."
>
> change "a typical application concerned with bulk data transfer"
> to "a typical application concerned with bulk data retrieval", then
> we have one of the most important use cases as an example - though
> the example does not reflect the full complexity of that issue ...
>
> Agree on the subtlety. Instead of an example in the definition,  how about
a
short discussion paragraph starting as "Each application has its
interpretation
on who assumes the role of ... and hence how to utilize Path Cost provided
by ALTO. For example, ..."

-yry


>   S.
> _______________________________________________
> alto mailing list
> alto@ietf.org <javascript:;>
> https://www.ietf.org/mailman/listinfo/alto
>

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

Hi Sebastian, Rich,<br><br>On Tuesday, July 3, 2012, Sebastian Kiesel  wrot=
e:<br><span class=3D"Apple-style-span" style>For example, the resource cons=
umer may not ask, as</span><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Rich,<br>
<br>
On Mon, Jul 02, 2012 at 11:09:51AM -0700, Richard Alimi wrote:<br>
&gt; We can certainly do an inventory on terminology to see if anything<br>
&gt; else from RFC5693 should be applied. =A0I&#39;m pretty sure it won&#39=
;t just be<br>
&gt; substituting &quot;endpoints&quot; with either &quot;resource consumer=
&quot; or &quot;resource<br>
&gt; provider&quot; though, since that depends quite a bit on how the<br>
&gt; application uses ALTO information, and what the costs actually<br>
&gt; represent.<br>
<br>
<br>
&gt; That is, we can&#39;t simply say that that a resource consumer<br>
&gt; is choosing a resource provider.<br>
<br>
I would exactly say this.<br>
<br>
Or maybe, to be more precise: A resource consumer chooses - or asks a<br>
third party to choose on behalf of it - one or several resource<br>
providers from a set of candidate resource providers (and ALTO is<br>
consulted in order to improve that decision).</blockquote><div>=A0</div><di=
v>Using your good reasoning below, even the preceding sentence may have</di=
v><div>subtlety: &quot;ask&quot; may imply some messages, but the app may n=
ot have a</div>
<div>message. How about remove &quot;ask&quot;?</div><br><div></div><div>=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
However, it it is important that resource is not neccessarily a file or<br>
content stream. Therefore, the above sentence does not imply that most<br>
of the data flows from the resource provider(s) to the resource consumer!<b=
r>
Because we might have independent control and data connections<br>
it would also be too simplistic to say the resource consumer<br>
is the &quot;connection/flow initiator&quot;, though most of the time this =
is true.<br>
<br>
<br>
&gt; It&#39;s conceivable that the resource<br>
&gt; provider could be doing the choosing in a push-based protocol.<br>
<br>
If we have a push-based protocol, where one could send some<br>
kind of information to one of several &quot;sinks&quot;, I&#39;d say that t=
he<br>
(ALTO-/RFC5693-)resources are these sinks, and the &quot;pusher&quot;<br>
is the resource consumer, which consumes the sink-resource.<br>
<br>
<br>
&gt; As a<br>
&gt; slightly more interesting example, what if I also wanted to try and<br=
>
&gt; reduce latency for ACKs in the opposite direction to protect myself<br=
>
&gt; against asymmetric routing - then then I&#39;d be querying a latency m=
ap<br>
&gt; for the cost from the resource consumer to the resource provider. =A0 =
In<br>
&gt; the ALTO Protocol we try to simply express these as costs between<br>
&gt; endpoints.<br>
<br>
ack.<br>
<br>
&gt; It&#39;s an application-level concern about who does the<br>
&gt; choosing, and making sure they are using the costs appropriately.<br>
<br>
Each application uses its own terminology and has specific ideas on who<br>
assumes the roles of &quot;client&quot;, &quot;server&quot;, &quot;peer&quo=
t;, ...<br>
My understanding of the ALTO terminology is that we can use it to<br>
describe the (ALTO-relevant) features of an arbitrary protocol in<br>
a uniform way. And in particular, I would describe the general<br>
ALTO problem as:<br>
<br>
We have 1 resource consumer and N candidate resource providers.<br>
We want to have data flows between the resource consumer and<br>
M &lt; N resource providers. Therefore, we need to choose M out of N,<br>
and ALTO is supposed to help on that decision.<br>
<br>
&gt; All that said, I think we do need to improve the protocol draft to<br>
&gt; explicitly say how &quot;endpoint&quot; relates to &quot;resource cons=
umer&quot; and<br>
&gt; &quot;resource provider&quot; which is mentioned in other documents. =
=A0How about<br>
&gt; the following:<br>
&gt;<br>
&gt; Add this to Section 2.1.1:<br>
&gt; =A0 &quot;An Endpoint Address is typically either the address of a Res=
ource<br>
&gt; Provider or Resource Consumer.&quot;</blockquote><div><br></div><div>S=
uppose we want to simplify the definition by removing &quot;address&quot; f=
rom the the above.=A0<span></span></div><div>Then we have &quot;An Endpoint=
 is typically either a Resource Provider or Resource</div>
<div>Consumer.&quot; How does this read? What is an atypical case?=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Is it always the address of exactly one host (either r.prov. or r.cons.)?<b=
r>
Otherwise, the already defined term &quot;host group descriptor&quot; might=
 make<br>
sense?<br>
<br>
&gt; Add change this text in Section 5:<br>
&gt; =A0 &quot;Each Path Cost is the end-to-end cost from the source to the=
 destination.&quot;<br>
&gt; to instead read:<br>
&gt; =A0 &quot;Each Path Cost is the end-to-end cost from the source to the=
<br>
&gt; destination. =A0For example, if the cost is expected correlated with<b=
r>
&gt; throughput, a typical application concerned with bulk data transfer<br=
>
&gt; may use the Resource Provider as the source, and Resource Consumer as<=
br>
&gt; the destination.&quot;<br>
<br>
change &quot;a typical application concerned with bulk data transfer&quot;<=
br>
to &quot;a typical application concerned with bulk data retrieval&quot;, th=
en<br>
we have one of the most important use cases as an example - though<br>
the example does not reflect the full complexity of that issue ...<br>
<br></blockquote><div>Agree on the subtlety. Instead of an example in the d=
efinition, =A0how about a=A0</div><div>short discussion paragraph starting =
as &quot;Each application has its interpretation</div><div>on who assumes t=
he role of ... and hence how to utilize Path Cost provided</div>
<div>by ALTO. For example, ...&quot;</div><div><br></div><div>-yry</div><di=
v>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">
=A0 S.<br>
_______________________________________________<br>
alto mailing list<br>
<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;alto@iet=
f.org&#39;)">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
</blockquote>

--e89a8fb1ec7008d51104c3e7af7c--

From Martin.Stiemerling@neclab.eu  Tue Jul  3 06:19:58 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 DD6E821F8862 for <alto@ietfa.amsl.com>; Tue,  3 Jul 2012 06:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.565
X-Spam-Level: 
X-Spam-Status: No, score=-102.565 tagged_above=-999 required=5 tests=[AWL=0.034, 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 8Oof57oeGDOS for <alto@ietfa.amsl.com>; Tue,  3 Jul 2012 06:19:58 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 1E51021F885E for <alto@ietf.org>; Tue,  3 Jul 2012 06:19:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id C3426101711; Tue,  3 Jul 2012 15:20:55 +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 g3ClC1qrk7tY; Tue,  3 Jul 2012 15:20:55 +0200 (CEST)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id A850D10170F; Tue,  3 Jul 2012 15:20:45 +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; Tue, 3 Jul 2012 15:21:13 +0200
Message-ID: <4FF2F17B.1050300@neclab.eu>
Date: Tue, 3 Jul 2012 15:19:55 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: Richard Alimi <rich@velvetsea.net>
References: <4FF1B72C.4000209@neclab.eu> <CA+cvDaZvZAE2yUdvM3i09QEccghMpsEZbV3DAz3JVX7e+jJapA@mail.gmail.com>
In-Reply-To: <CA+cvDaZvZAE2yUdvM3i09QEccghMpsEZbV3DAz3JVX7e+jJapA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Cc: alto@ietf.org
Subject: Re: [alto] Way forward for the Resdistribution
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, 03 Jul 2012 13:19:59 -0000

On 07/02/2012 07:37 PM, Richard Alimi wrote:
> The material has been migrated to another document locally, but it
> isn't yet ready for submission.    I don't think it should be
> completely abandoned, but in my opinion the priority is lower than
> getting the base protocol.  As was mentioned in the discussion w.r.t.
> requirements, there are some things that it provides such as
> guidelines on which clients should make use of the information and for
> how long (above and beyond what we get for free from HTTP caching).
>
> With your AD hat on, do we need the additional document to be
> explicitly mentioned in the charter?

It would be good to see this draft submitted. Getting a new milestone 
for this is not a big deal if the WG is in agreement.

   Martin

>
> Rich
>
> On Mon, Jul 2, 2012 at 7:58 AM, Martin Stiemerling
> <martin.stiemerling@neclab.eu> wrote:
>> Hi all,
>>
>> I have just read the ALTO protocol slides of the meeting in Paris and do
>> wonder what has ultimately happened to the redistribution, as the slide
>> state:
>>
>> "Will be submitted as separate draft that may make use of JOSE"
>> (http://www.ietf.org/proceedings/83/slides/slides-83-alto-2.pdf)
>>
>> This functionality is gone from the base protocol, but we do not have any
>> replacement insight. Do we completely abandon this?
>>
>> Thanks,
>>
>>    Martin
>> --
>> 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

-- 
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 sabine.randriamasy@alcatel-lucent.com  Tue Jul  3 08:35:59 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 D6B4B21F87A7 for <alto@ietfa.amsl.com>; Tue,  3 Jul 2012 08:35:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.949
X-Spam-Level: 
X-Spam-Status: No, score=-7.949 tagged_above=-999 required=5 tests=[AWL=1.700,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_14=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 bqe4nzn97Rbv for <alto@ietfa.amsl.com>; Tue,  3 Jul 2012 08:35:58 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by ietfa.amsl.com (Postfix) with ESMTP id 9519821F853F for <alto@ietf.org>; Tue,  3 Jul 2012 08:35:58 -0700 (PDT)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q63Fa2f7014339 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 3 Jul 2012 17:36:02 +0200
Received: from [172.27.204.47] (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; Tue, 3 Jul 2012 17:36:02 +0200
Message-ID: <4FF3115C.1020304@alcatel-lucent.com>
Date: Tue, 3 Jul 2012 17:35:56 +0200
From: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: "Y. Richard Yang" <yry@cs.yale.edu>
References: <4F8BE443.9050903@telecomitalia.it>	<4FAD5745.2060009@alcatel-lucent.com>	<CA+cvDab3P0-68m6+mZ+4K0FedJ7_MK6SGXhD2kQKupXuCDLgDw@mail.gmail.com>	<CA+cvDaZJ-RdJKf9mSTP0qbz3vS1mK28XQYpzpfQ69EZbMCF_5A@mail.gmail.com>	<20120702154359.GV5342@gw01.ehlo.wurstkaes.de>	<CA+cvDaYdzoGub0gvwbV2EfvCTmnS73Q5gSf+pvDH-sCsRjtPQg@mail.gmail.com>	<20120702202219.GX5342@gw01.ehlo.wurstkaes.de> <CANUuoLqpJTQy6WbHjiX75YJmLEDV+yg1E_8-GX1okHOoH0CJdg@mail.gmail.com>
In-Reply-To: <CANUuoLqpJTQy6WbHjiX75YJmLEDV+yg1E_8-GX1okHOoH0CJdg@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; 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: Tue, 03 Jul 2012 15:36:00 -0000

Hi Sebastian, Rich, Richard

Y. Richard Yang a écrit :
> Hi Sebastian, Rich,
>
> On Tuesday, July 3, 2012, Sebastian Kiesel wrote:
> For example, the resource consumer may not ask, as
>
>     Hi Rich,
>
>     On Mon, Jul 02, 2012 at 11:09:51AM -0700, Richard Alimi wrote:
>     > We can certainly do an inventory on terminology to see if anything
>     > else from RFC5693 should be applied.  I'm pretty sure it won't
>     just be
>     > substituting "endpoints" with either "resource consumer" or
>     "resource
>     > provider" though, since that depends quite a bit on how the
>     > application uses ALTO information, and what the costs actually
>     > represent.
>
>
>     > That is, we can't simply say that that a resource consumer
>     > is choosing a resource provider.
>
>     I would exactly say this.
>
>     Or maybe, to be more precise: A resource consumer chooses - or asks a
>     third party to choose on behalf of it - one or several resource
>     providers from a set of candidate resource providers (and ALTO is
>     consulted in order to improve that decision).
>
>  
> Using your good reasoning below, even the preceding sentence may have
> subtlety: "ask" may imply some messages, but the app may not have a
> message. How about remove "ask"?
>
>  
>
>     However, it it is important that resource is not neccessarily a
>     file or
>     content stream. Therefore, the above sentence does not imply that most
>     of the data flows from the resource provider(s) to the resource
>     consumer!
>     Because we might have independent control and data connections
>     it would also be too simplistic to say the resource consumer
>     is the "connection/flow initiator", though most of the time this
>     is true.
>
>
>     > It's conceivable that the resource
>     > provider could be doing the choosing in a push-based protocol.
>
>     If we have a push-based protocol, where one could send some
>     kind of information to one of several "sinks", I'd say that the
>     (ALTO-/RFC5693-)resources are these sinks, and the "pusher"
>     is the resource consumer, which consumes the sink-resource.
>
>
>     > As a
>     > slightly more interesting example, what if I also wanted to try and
>     > reduce latency for ACKs in the opposite direction to protect myself
>     > against asymmetric routing - then then I'd be querying a latency map
>     > for the cost from the resource consumer to the resource
>     provider.   In
>     > the ALTO Protocol we try to simply express these as costs between
>     > endpoints.
>
>     ack.
>
>     > It's an application-level concern about who does the
>     > choosing, and making sure they are using the costs appropriately.
>
>     Each application uses its own terminology and has specific ideas
>     on who
>     assumes the roles of "client", "server", "peer", ...
>     My understanding of the ALTO terminology is that we can use it to
>     describe the (ALTO-relevant) features of an arbitrary protocol in
>     a uniform way. And in particular, I would describe the general
>     ALTO problem as:
>
>     We have 1 resource consumer and N candidate resource providers.
>     We want to have data flows between the resource consumer and
>     M < N resource providers. Therefore, we need to choose M out of N,
>     and ALTO is supposed to help on that decision.
>
>     > All that said, I think we do need to improve the protocol draft to
>     > explicitly say how "endpoint" relates to "resource consumer" and
>     > "resource provider" which is mentioned in other documents.  How
>     about
>     > the following:
>     >
>     > Add this to Section 2.1.1:
>     >   "An Endpoint Address is typically either the address of a Resource
>     > Provider or Resource Consumer."
>
>
> Suppose we want to simplify the definition by removing "address" from 
> the the above. 
> Then we have "An Endpoint is typically either a Resource Provider or 
> Resource
> Consumer." How does this read? What is an atypical case?
This reads clear. An ALTO Endpoint covers both Consumer and Provider. 
Resources pushers and sinks are implicitely mapped onto source and 
destination in the ALTO Cost Maps, that thus also support asymetrical 
traffic cases. 
Would this point fit in the Endpoint definition section planned before 
current Section 2.1.1 Endpoint address ?
>
>
>     Is it always the address of exactly one host (either r.prov. or
>     r.cons.)?
>     Otherwise, the already defined term "host group descriptor" might make
>     sense?
>
I agree with this question as Section 2.1.3 Network Location says:  
"denoting a single endpoint or
group of endpoints". Section 5 may address this question this with some 
additonal text.
Section 5 currently says:

"An ALTO Cost Map defines Path Costs pairwise amongst sets of source
and destination Network Locations. Each Path Cost is the end-to-end
cost from the source to the destination."

How about adding a sentence like:

"The Path Cost between Network Locations grouping several Endpoints 
(opt: and represented by their PID) is provided by The ALTO Cost Map 
Service. The ALTO protocol additonally MAY provide Path Costs between 
individual Endpoints (opt: represented by their address) via the ALTO 
Endpoint Cost Service."
>
>
>     > Add change this text in Section 5:
>     >   "Each Path Cost is the end-to-end cost from the source to the
>     destination."
>     > to instead read:
>     >   "Each Path Cost is the end-to-end cost from the source to the
>     > destination.  For example, if the cost is expected correlated with
>     > throughput, a typical application concerned with bulk data transfer
>     > may use the Resource Provider as the source, and Resource
>     Consumer as
>     > the destination."
>
>     change "a typical application concerned with bulk data transfer"
>     to "a typical application concerned with bulk data retrieval", then
>     we have one of the most important use cases as an example - though
>     the example does not reflect the full complexity of that issue ...
>
> Agree on the subtlety. Instead of an example in the definition,  how 
> about a 
> short discussion paragraph starting as "Each application has its 
> interpretation
> on who assumes the role of ... and hence how to utilize Path Cost provided
> by ALTO. For example, ..."
yes, and again say that the application must be aware that the roles 
that they have set are to be mapped with the roles of source and 
destination implicitely encoded in the ALTO Cost Maps.

Re-adding a comment from Sebastian yesterday, I have the following :

Sebastian: "Btw. "Content Location" would IMO not be general enough, as we could use
ALTO also, e.g., to find a "good" media relay for VoIP NAT traversal."

It may be interesting to consider other cases such as media relays. Wouldn't it be worth adding such a use case to be discussed in either the ALTO or i2aex WG? Do you have one in mind? 

Sabine


>
> -yry
>  
>
>       S.
>     _______________________________________________
>     alto mailing list
>     alto@ietf.org <javascript:;>
>     https://www.ietf.org/mailman/listinfo/alto
>


From Martin.Stiemerling@neclab.eu  Tue Jul  3 12:46:29 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 1B4A211E81D3 for <alto@ietfa.amsl.com>; Tue,  3 Jul 2012 12:46:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.454
X-Spam-Level: 
X-Spam-Status: No, score=-102.454 tagged_above=-999 required=5 tests=[AWL=-0.082, 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 1IXaMRqqDdMB for <alto@ietfa.amsl.com>; Tue,  3 Jul 2012 12:46:28 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id CC6D111E8170 for <alto@ietf.org>; Tue,  3 Jul 2012 12:46:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 7CF07101712; Tue,  3 Jul 2012 21:47:28 +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 rQ6WxKW2bRJy; Tue,  3 Jul 2012 21:47:28 +0200 (CEST)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 608CF1016F5; Tue,  3 Jul 2012 21:47:08 +0200 (CEST)
Received: from [10.7.0.105] (10.7.0.105) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 3 Jul 2012 21:47:35 +0200
Message-ID: <4FF34C05.2010400@neclab.eu>
Date: Tue, 3 Jul 2012 21:46:13 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: Richard Alimi <rich@velvetsea.net>
References: <4F8BE443.9050903@telecomitalia.it> <20120514061451.GA3136@gw01.ehlo.wurstkaes.de> <CA+cvDab1XR40W7FBHhDNOTTag7tvSihVe7BSMVbAP6W-Qtk91A@mail.gmail.com> <4FF1B8CB.7090005@neclab.eu> <CA+cvDabEaB8N5835xuECtqKMejLVaOk5qRgeTnAimL=6gCVHUA@mail.gmail.com>
In-Reply-To: <CA+cvDabEaB8N5835xuECtqKMejLVaOk5qRgeTnAimL=6gCVHUA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.7.0.105]
Cc: draft-ietf-alto-protocol@tools.ietf.org, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [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: Tue, 03 Jul 2012 19:46:29 -0000

On 07/02/2012 08:35 PM, Richard Alimi wrote:
> On Mon, Jul 2, 2012 at 8:05 AM, Martin Stiemerling
> <martin.stiemerling@neclab.eu> wrote:
>> [writing with no Area Director hat on, i.e., as a random community member]
>
> Good to have you back :)

Thanks, finally there is time again for ALTO :)

>
>> Hi Richard, all,
>>
>> On 07/02/2012 08:38 AM, Richard Alimi wrote:
>> [...]
>>
>>
>>>> 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, ...)
>>>
>>>
>>> It needs something more than just an I-D since that is a pretty low bar.
>>
>>
>> You can specify 'protocol specification' or 'expert review' as the bar for
>> an extension.
>> See also RFC 5226 for a discussion of this:
>> http://tools.ietf.org/html/rfc5226
>>
>>
>>>
>>> Do people think a registry is needed for this?  If not, perhaps we can
>>> just make this more explicit that it needs to be a standards-track
>>> RFC.
>>
>>
>> There should be a registry where you can add additional address types.
>> Otherwise it is really hard to get new address types in a clean way into the
>> protocol.
>> A registry allows also to keep track about all existing address types (out
>> of the ALTO protocol and what comes later on).
>
> Right - okay. We'll add an Address Type registry.  That said, it'd be
> really nice to point to an existing registry. I think we'd need the
> following for such a registry:
> (1) A textual string for an address type itself
> (2) A specification (preferably a pointer to one) for how to serialize
> and deserialize a textual address of that type.
> (3) (maybe, depending on the result of the discussion below) a
> statement of how an address type can be mapped into IPv4/v6 addresses.
>
> However, when browsing through the available IANA registries I didn't
> see one that really matched those requirements.  Does anyone have a
> better option before we go about defining our own?

We need to create our own registry for this, which isn't a big deal. 
Just write this up in the IANA considerations section.

>
>>>
>>>>>      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.
>>>>
>>>>
[...]

>>>
>>>
>>> The use of JSON and Section 7.2.7 also helps with extensions.
>>>
>>>>>      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
>>>
>>>
>>> Yeah.  There was a discussion when going to the REST-ful approach
>>> about whether we wanted any explicit version numbers or not.  The idea
>>> was that we didn't need an ALTO version number exposed to applications
>>> if we used media types appropriately.  Using media types like you
>>> suggested is certainly one approach.
>>
>>
>> Irrespectively of what mechanisms is being used, this protocol needs
>> versioning support. However, I'm not sure that media-types are the best way
>> forward for this.
>> What would be a different approach when using media types?
>
> Do you mean a different approach *than* using media types?  One other
> option would be to revert revert back to what we had before, which is
> have an explicit field in each and every response.
>
> Here's one pointer to mailing list discussions about protocol
> versioning and media types:
>    http://www.mail-archive.com/alto@ietf.org/msg00609.html
> I'll note that our AD at the time (Lisa) was one of the people
> suggesting we use content negotiation to provide protocol versioning.
>
> My preference would be to not re-hash the merits of protocol
> versioning unless we think there is a clear technical advantage over
> what we have now.

Let me go through the old email thread to see what happened back then.

>
>>>
>>>>> 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..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.
>>>
>>>
>>> We also had a discussion about this in the protocol overhaul for
>>> making it REST-ful.  The guidance we received there was to not repeat
>>> details from RFC2616.  I'm not sure I see much utility in adding
>>> specifics in the ALTO protocol document, since it would basically
>>> amount to saying "If you think you are overloaded, you are free to
>>> return a 503."  Then, if we were to add that, people would ask "you
>>> gave me guidance on using 503, but you didn't tell me when I should or
>>> should not use chunked transfer encoding.. how about that??"  The idea
>>> was that the statements in Section 7.2, as well as some intelligence
>>> on behalf of implementers on how to apply RFC2616, would answer all of
>>> these questions.
>>
>>
>> That is not a good way of specifying things. There is no need to say how a
>> 503 response looks like, but it is definitely good to say when an ALTO
>> protocol must reply with such a code. "intelligence ...of implementers" will
>> cause ALTO protocol implementations that do not interoperate.
>
> If we want to make revisions here, can you give some guidance on where
> we should recommend certain usage of HTTP and where we shouldn't?
> Should it be just additional text to ensure that we satisfy the
> requirements on overload control, or additional guidance on how to to
> employ other parts of HTTP such as transfer encoding, caching, when to
> use redirects, etc?

I would describe only mechanisms which are required by the protocol (or 
by the requirements). The protocol spec must say: return a 503 if 
overloaded, for instance. I do not see the need to specify how ALTO is 
using each and every feature of HTTP, but it should be clear how 
functionality required by the ALTO protocol is mapped to the underlying 
HTTP protocol.

Thanks,

   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 Martin.Stiemerling@neclab.eu  Tue Jul  3 12:50:37 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 B8F2921F8759 for <alto@ietfa.amsl.com>; Tue,  3 Jul 2012 12:50:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.452
X-Spam-Level: 
X-Spam-Status: No, score=-102.452 tagged_above=-999 required=5 tests=[AWL=-0.080, 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 4f6Kc1yVOqgy for <alto@ietfa.amsl.com>; Tue,  3 Jul 2012 12:50:37 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id D54E721F876F for <alto@ietf.org>; Tue,  3 Jul 2012 12:50:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 9F3EA101718; Tue,  3 Jul 2012 21:51:37 +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 ohCjmKAeHylh; Tue,  3 Jul 2012 21:51:37 +0200 (CEST)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 43735101714; Tue,  3 Jul 2012 21:51:17 +0200 (CEST)
Received: from [10.7.0.105] (10.7.0.105) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 3 Jul 2012 21:51:23 +0200
Message-ID: <4FF34CE8.6030901@neclab.eu>
Date: Tue, 3 Jul 2012 21:50:00 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: Richard Alimi <rich@velvetsea.net>
References: <4F8BE443.9050903@telecomitalia.it> <20120514061451.GA3136@gw01.ehlo.wurstkaes.de> <CA+cvDab1XR40W7FBHhDNOTTag7tvSihVe7BSMVbAP6W-Qtk91A@mail.gmail.com> <20120702152746.GU5342@gw01.ehlo.wurstkaes.de> <CA+cvDaYmWrcTEiWNLYhphH9x6D=KvO2tacReQNJLZVn-KuBxwQ@mail.gmail.com>
In-Reply-To: <CA+cvDaYmWrcTEiWNLYhphH9x6D=KvO2tacReQNJLZVn-KuBxwQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.7.0.105]
Cc: draft-ietf-alto-protocol@tools.ietf.org, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [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: Tue, 03 Jul 2012 19:50:38 -0000

On 07/02/2012 08:41 PM, Richard Alimi wrote:
> On Mon, Jul 2, 2012 at 8:27 AM, Sebastian Kiesel <ietf-alto@skiesel.de> wrote:
>> Hi Rich,
>>
>> I need some more time to comment on the other issues, but let me write
>> about one thing before I forget it again :)
>>
>>>>      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.
>>>
>>> At least in the initial discussions of ALTO, there was mention about
>>> using these for addresses other than IP addresses, such as e.164
>>> numbers.  That said, I haven't seen any concrete use cases for
>>> anything other than IP addresses or things that can map to IP
>>> addresses.
>>>
>>> I don't intend to start a debate on the requirements document at this
>>> stage, but I'm a bit hesitant to say that extensions MUST do this.  I
>>> completely agree that those proposing extensions should be thinking
>>> about this, but tend to think that MUST is too strong.  How about
>>> extending 7.5.3.1 to state "extension documents defining a new Address
>>> Type SHOULD also document a mechanism to map addresses of the new type
>>> to IPv4 and/or IPv6 addresses prefixes."
>>
>>
>> I propose to write in 7.5.3.1:
>>
>> "Extension documents may define additional Address Types and the
>> corresponding mechanisms to map these adresses from/to IPv4/IPv6
>> addresses/prefixes."
>>
>> That way you neither have to contradict nor reinforce the requirements
>> document.
>
> This sounds good to me.  Depending on what we do with a registry, it
> may make sense to put this as one of the criteria for adding a new
> entry instead.

Sebastian's text is good.
Not sure what you are saying with the registry -- probably too late for me

   Martin

>
>>
>>
>> Thanks,
>> Sebastian
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>

-- 
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 Martin.Stiemerling@neclab.eu  Tue Jul  3 13:02:24 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 0129611E8195 for <alto@ietfa.amsl.com>; Tue,  3 Jul 2012 13:02:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.563
X-Spam-Level: 
X-Spam-Status: No, score=-102.563 tagged_above=-999 required=5 tests=[AWL=0.036, 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 yH9rn59lU-et for <alto@ietfa.amsl.com>; Tue,  3 Jul 2012 13:02:23 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 2411E11E8189 for <alto@ietf.org>; Tue,  3 Jul 2012 13:02:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 46841101717; Tue,  3 Jul 2012 22:03:24 +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 p-acCXW2GScU; Tue,  3 Jul 2012 22:03:24 +0200 (CEST)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 29F73101716; Tue,  3 Jul 2012 22:03:09 +0200 (CEST)
Received: from [10.7.0.105] (10.7.0.105) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 3 Jul 2012 22:03:36 +0200
Message-ID: <4FF34FC6.9040502@neclab.eu>
Date: Tue, 3 Jul 2012 22:02:14 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
References: <4F8BE443.9050903@telecomitalia.it>	<4FAD5745.2060009@alcatel-lucent.com>	<CA+cvDab3P0-68m6+mZ+4K0FedJ7_MK6SGXhD2kQKupXuCDLgDw@mail.gmail.com>	<CA+cvDaZJ-RdJKf9mSTP0qbz3vS1mK28XQYpzpfQ69EZbMCF_5A@mail.gmail.com>	<20120702154359.GV5342@gw01.ehlo.wurstkaes.de>	<CA+cvDaYdzoGub0gvwbV2EfvCTmnS73Q5gSf+pvDH-sCsRjtPQg@mail.gmail.com>	<20120702202219.GX5342@gw01.ehlo.wurstkaes.de> <CANUuoLqpJTQy6WbHjiX75YJmLEDV+yg1E_8-GX1okHOoH0CJdg@mail.gmail.com> <4FF3115C.1020304@alcatel-lucent.com>
In-Reply-To: <4FF3115C.1020304@alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.7.0.105]
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, 03 Jul 2012 20:02:24 -0000

Sabine,

On 07/03/2012 05:35 PM, Sabine Randriamasy wrote:
[...]

>> Agree on the subtlety. Instead of an example in the definition,  how
>> about a short discussion paragraph starting as "Each application has
>> its interpretation
>> on who assumes the role of ... and hence how to utilize Path Cost
>> provided
>> by ALTO. For example, ..."
> yes, and again say that the application must be aware that the roles
> that they have set are to be mapped with the roles of source and
> destination implicitely encoded in the ALTO Cost Maps.
>
> Re-adding a comment from Sebastian yesterday, I have the following :
>
> Sebastian: "Btw. "Content Location" would IMO not be general enough, as
> we could use
> ALTO also, e.g., to find a "good" media relay for VoIP NAT traversal."
>
> It may be interesting to consider other cases such as media relays.
> Wouldn't it be worth adding such a use case to be discussed in either
> the ALTO or i2aex WG? Do you have one in mind?

There are probably other use cases just around the corner.

However, we should use all energy to finalize the ALTO protocol spec 
right now.

   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 guyingjie@huawei.com  Tue Jul  3 18:24:36 2012
Return-Path: <guyingjie@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 DEB2311E80DE for <alto@ietfa.amsl.com>; Tue,  3 Jul 2012 18:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.212
X-Spam-Level: 
X-Spam-Status: No, score=-97.212 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345, 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 D3bQCymC9Z+2 for <alto@ietfa.amsl.com>; Tue,  3 Jul 2012 18:24:36 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 1A1DA11E80D9 for <alto@ietf.org>; Tue,  3 Jul 2012 18:24:36 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHR70019; Tue, 03 Jul 2012 21:24:45 -0400 (EDT)
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 3 Jul 2012 18:23:21 -0700
Received: from SZXEML414-HUB.china.huawei.com (10.82.67.153) by dfweml408-hub.china.huawei.com (10.193.5.134) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 3 Jul 2012 18:23:24 -0700
Received: from SZXEML511-MBS.china.huawei.com ([169.254.4.86]) by SZXEML414-HUB.china.huawei.com ([10.82.67.153]) with mapi id 14.01.0323.003; Wed, 4 Jul 2012 09:23:11 +0800
From: "Guyingjie (Yingjie)" <guyingjie@huawei.com>
To: Martin Stiemerling <martin.stiemerling@neclab.eu>, Richard Alimi <rich@velvetsea.net>, Roni even <Even.roni@huawei.com>, Richard Alimi <ralimi@google.com>
Thread-Topic: [alto] Way forward for the Resdistribution
Thread-Index: AQHNWGNAKXxeiUrn70aXGlRsXiyIypcVu/CAgAFKP4CAAU4McA==
Date: Wed, 4 Jul 2012 01:23:10 +0000
Message-ID: <A27496C192613C44A82D819E1B98DB573402F332@SZXEML511-MBS.china.huawei.com>
References: <4FF1B72C.4000209@neclab.eu> <CA+cvDaZvZAE2yUdvM3i09QEccghMpsEZbV3DAz3JVX7e+jJapA@mail.gmail.com> <4FF2F17B.1050300@neclab.eu>
In-Reply-To: <4FF2F17B.1050300@neclab.eu>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.122.45]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: [alto] =?gb2312?b?tPC4tDogIFdheSBmb3J3YXJkIGZvciB0aGUgUmVzZGlz?= =?gb2312?b?dHJpYnV0aW9u?=
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, 04 Jul 2012 01:24:37 -0000

SGkgTWFydGluIGFuZCBhbGwsDQpUaGUgYmFzZSBwcm90b2NvbCB1c2VkIHRvIHJlZmVyIHRvIGRy
YWZ0LWd1LWFsdG8tcmVkaXN0cmlidXRpb24sIGFuZCBJIGFtIG9uZSBvZiB0aGUgYXV0aG9ycywg
dG9nZXRoZXIgd2l0aCBSaWNoYXJkIGFuZCBSb25pLiANCklzIHRoZXJlIGFueSBwbGFuIGZvciB0
aGUgbmV3IGRlZGljYXRlZCByZWRpc3RyaWJ1dGlvbiBkcmFmdCwgZS5nLiBjb250cmlidXRvcnMg
YW5kIGRyYWZ0IHBsYW4/DQoNCkkgYW0gbm90IHZlcnkgYWN0aXZlIGluIEFMVE8gZm9yIHNvbWV0
aW1lLCBzbyBJIG1heWJlIG1pc3Mgc29tZSBkaXNjdXNzaW9uIGluIHRoZSBtYWlsIGxpc3Qgb24g
cmVkaXN0cmlidXRpb24uIA0KUGVyc29uYWxseSwgSSB3b3VsZCBzdWdnZXN0IHRvIGF3YWtlIHRo
ZSBkcmFmdC1ndS1hbHRvLXJlZGlzdHJpYnV0aW9uLCBzaW5jZSB0aGVyZSBpcyBtYW55IGRldGFp
bCB0ZWNobmljYWwgY29uc2lkZXJhdGlvbnMgZm9yIHJlZGlzdHJpYnV0aW9uLiBPciBhdCBsZWFz
dCB3ZSBzaG91bGQgdGFrZSB0aGUgQmFzaWMgcmVxdWlyZW1lbnRzIGFuZCBBTFRPIFJlZGlzdHJp
YnV0aW9uIFNvbHV0aW9ucyBBbmFseXNpcyB0byB0aGUgbmV3IGRyYWZ0IGlmIHRoZXJlIGlzIGFu
eS4NCg0KQmVzdCBSZWdhcmRzDQpHdSBZaW5namllDQoNCg0KLS0tLS3Tyrz+1K28/i0tLS0tDQq3
orz+yMs6IGFsdG8tYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmFsdG8tYm91bmNlc0BpZXRmLm9y
Z10gtPqx7SBNYXJ0aW4gU3RpZW1lcmxpbmcNCreiy83KsbzkOiAyMDEyxOo31MIzyNUgwNbA1jIx
OjIwDQrK1bz+yMs6IFJpY2hhcmQgQWxpbWkNCrOty806IGFsdG9AaWV0Zi5vcmcNCtb3zOI6IFJl
OiBbYWx0b10gV2F5IGZvcndhcmQgZm9yIHRoZSBSZXNkaXN0cmlidXRpb24NCg0KDQoNCk9uIDA3
LzAyLzIwMTIgMDc6MzcgUE0sIFJpY2hhcmQgQWxpbWkgd3JvdGU6DQo+IFRoZSBtYXRlcmlhbCBo
YXMgYmVlbiBtaWdyYXRlZCB0byBhbm90aGVyIGRvY3VtZW50IGxvY2FsbHksIGJ1dCBpdA0KPiBp
c24ndCB5ZXQgcmVhZHkgZm9yIHN1Ym1pc3Npb24uICAgIEkgZG9uJ3QgdGhpbmsgaXQgc2hvdWxk
IGJlDQo+IGNvbXBsZXRlbHkgYWJhbmRvbmVkLCBidXQgaW4gbXkgb3BpbmlvbiB0aGUgcHJpb3Jp
dHkgaXMgbG93ZXIgdGhhbg0KPiBnZXR0aW5nIHRoZSBiYXNlIHByb3RvY29sLiAgQXMgd2FzIG1l
bnRpb25lZCBpbiB0aGUgZGlzY3Vzc2lvbiB3LnIudC4NCj4gcmVxdWlyZW1lbnRzLCB0aGVyZSBh
cmUgc29tZSB0aGluZ3MgdGhhdCBpdCBwcm92aWRlcyBzdWNoIGFzDQo+IGd1aWRlbGluZXMgb24g
d2hpY2ggY2xpZW50cyBzaG91bGQgbWFrZSB1c2Ugb2YgdGhlIGluZm9ybWF0aW9uIGFuZCBmb3IN
Cj4gaG93IGxvbmcgKGFib3ZlIGFuZCBiZXlvbmQgd2hhdCB3ZSBnZXQgZm9yIGZyZWUgZnJvbSBI
VFRQIGNhY2hpbmcpLg0KPg0KPiBXaXRoIHlvdXIgQUQgaGF0IG9uLCBkbyB3ZSBuZWVkIHRoZSBh
ZGRpdGlvbmFsIGRvY3VtZW50IHRvIGJlDQo+IGV4cGxpY2l0bHkgbWVudGlvbmVkIGluIHRoZSBj
aGFydGVyPw0KDQpJdCB3b3VsZCBiZSBnb29kIHRvIHNlZSB0aGlzIGRyYWZ0IHN1Ym1pdHRlZC4g
R2V0dGluZyBhIG5ldyBtaWxlc3RvbmUgDQpmb3IgdGhpcyBpcyBub3QgYSBiaWcgZGVhbCBpZiB0
aGUgV0cgaXMgaW4gYWdyZWVtZW50Lg0KDQogICBNYXJ0aW4NCg0KPg0KPiBSaWNoDQo+DQo+IE9u
IE1vbiwgSnVsIDIsIDIwMTIgYXQgNzo1OCBBTSwgTWFydGluIFN0aWVtZXJsaW5nDQo+IDxtYXJ0
aW4uc3RpZW1lcmxpbmdAbmVjbGFiLmV1PiB3cm90ZToNCj4+IEhpIGFsbCwNCj4+DQo+PiBJIGhh
dmUganVzdCByZWFkIHRoZSBBTFRPIHByb3RvY29sIHNsaWRlcyBvZiB0aGUgbWVldGluZyBpbiBQ
YXJpcyBhbmQgZG8NCj4+IHdvbmRlciB3aGF0IGhhcyB1bHRpbWF0ZWx5IGhhcHBlbmVkIHRvIHRo
ZSByZWRpc3RyaWJ1dGlvbiwgYXMgdGhlIHNsaWRlDQo+PiBzdGF0ZToNCj4+DQo+PiAiV2lsbCBi
ZSBzdWJtaXR0ZWQgYXMgc2VwYXJhdGUgZHJhZnQgdGhhdCBtYXkgbWFrZSB1c2Ugb2YgSk9TRSIN
Cj4+IChodHRwOi8vd3d3LmlldGYub3JnL3Byb2NlZWRpbmdzLzgzL3NsaWRlcy9zbGlkZXMtODMt
YWx0by0yLnBkZikNCj4+DQo+PiBUaGlzIGZ1bmN0aW9uYWxpdHkgaXMgZ29uZSBmcm9tIHRoZSBi
YXNlIHByb3RvY29sLCBidXQgd2UgZG8gbm90IGhhdmUgYW55DQo+PiByZXBsYWNlbWVudCBpbnNp
Z2h0LiBEbyB3ZSBjb21wbGV0ZWx5IGFiYW5kb24gdGhpcz8NCj4+DQo+PiBUaGFua3MsDQo+Pg0K
Pj4gICAgTWFydGluDQo+PiAtLQ0KPj4gbWFydGluLnN0aWVtZXJsaW5nQG5lY2xhYi5ldQ0KPj4N
Cj4+IE5FQyBMYWJvcmF0b3JpZXMgRXVyb3BlIC0gTmV0d29yayBSZXNlYXJjaCBEaXZpc2lvbiBO
RUMgRXVyb3BlIExpbWl0ZWQNCj4+IFJlZ2lzdGVyZWQgT2ZmaWNlOiBORUMgSG91c2UsIDEgVmlj
dG9yaWEgUm9hZCwgTG9uZG9uIFczIDZCTA0KPj4gUmVnaXN0ZXJlZCBpbiBFbmdsYW5kIDI4Mw0K
Pj4NCj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
PiBhbHRvIG1haWxpbmcgbGlzdA0KPj4gYWx0b0BpZXRmLm9yZw0KPj4gaHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9hbHRvDQoNCi0tIA0KbWFydGluLnN0aWVtZXJsaW5nQG5l
Y2xhYi5ldQ0KDQpORUMgTGFib3JhdG9yaWVzIEV1cm9wZSAtIE5ldHdvcmsgUmVzZWFyY2ggRGl2
aXNpb24gTkVDIEV1cm9wZSBMaW1pdGVkDQpSZWdpc3RlcmVkIE9mZmljZTogTkVDIEhvdXNlLCAx
IFZpY3RvcmlhIFJvYWQsIExvbmRvbiBXMyA2QkwNClJlZ2lzdGVyZWQgaW4gRW5nbGFuZCAyODMN
Cg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KYWx0
byBtYWlsaW5nIGxpc3QNCmFsdG9AaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vYWx0bw0K

From yry@cs.yale.edu  Wed Jul  4 03:17:32 2012
Return-Path: <yry@cs.yale.edu>
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 0D39821F87A8; Wed,  4 Jul 2012 03:17:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level: 
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[AWL=0.111,  BAYES_00=-2.599, J_CHICKENPOX_34=0.6]
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 N0DP3bQDqZq5; Wed,  4 Jul 2012 03:17:30 -0700 (PDT)
Received: from vm-emlprdomr-06.its.yale.edu (vm-emlprdomr-06.its.yale.edu [130.132.50.147]) by ietfa.amsl.com (Postfix) with ESMTP id 9F71121F87A3; Wed,  4 Jul 2012 03:17:30 -0700 (PDT)
Received: from [192.168.1.108] ([221.221.23.217]) (authenticated bits=0) by vm-emlprdomr-06.its.yale.edu (8.14.4/8.14.4) with ESMTP id q64AHR0P006445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 4 Jul 2012 06:17:29 -0400
Message-ID: <4FF41835.5020002@cs.yale.edu>
Date: Wed, 04 Jul 2012 18:17:25 +0800
From: "Y. Richard Yang" <yry@cs.yale.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Haiyong Xie <haiyong.xie@huawei.com>
References: <748A482AA35F7A4A8BD26465029B8C4A1B7C49EC@dfweml509-mbx.china.huawei.com> <4FF11869.1010408@cs.yale.edu> <4FF1DF7B.9080500@huawei.com>
In-Reply-To: <4FF1DF7B.9080500@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.71 on 130.132.50.147
Cc: "altoext@ietf.org" <altoext@ietf.org>, "alto@ietf.org" <alto@ietf.org>, Andreas Voellmy <andreas.voellmy@yale.edu>, Hongtao Yin <hongtao.yin@huawei.com>
Subject: Re: [alto] FW: New Version Notification for draft-xie-alto-sdn-extension-use-cases-00.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, 04 Jul 2012 10:17:32 -0000

On 7/3/12 1:50 AM, Haiyong Xie wrote:
> Hi Richard,
>
> Thanks very much for your comments. Please see my inline responses below.
>
> On 07/01/2012 08:41 PM, Y. Richard Yang wrote:
>> Hi Haiyong, Tina, Hongtao, and Diego,
>>
>> A good document! Here are some quick feedback:
>>
>> - One take-away message that the document appears trying to convey is
>> Vertical (V) vs Horizontal (H) architectures. My understanding of your
>> definition
>> is that V is a one-to-many setting, i.e., one ALTO Server to m SDN
>> Controllers (SC),
>> while H is one-to-one, i.e., one ALTO Server to one SC.
> The H architecture implies that the network should NOT be segmented,
> i.e., there exists only one SC; otherwise, the network will have
> multiple ALTO servers, each is working with corresponding SC only, but
> without exchanging information among multiple ALTO servers (we do not
> have a protocol to do so yet).
>
This is different from my understanding. I thought that H still could allow
network partition, say m sub-networks. Then there are m SCs and m ALTO
servers. The m SCs can form a mesh/peering to work together. Now I 
understand
your design. But how about the partitioned H design? Is it allowed? If 
there are
convincing use cases for inter-ALTO Server in your design, then it
identifies a need for inter-ALTO. What do you think?

>> Why is the information flow
>> in H only SC <- ALTO S (Sec. 3.2), not the other way around? In an SDN
>> setting, I
>> agree that an SC should already collect fine-grained, dynamic
>> information for its
>> controlled domain. ALTO currently does not define how its information is
>> collected/provisioned, but SC provides a good source (Sec. 4.3.2) of
>> information
>> for ALTO Server to aggregate and conduct abstraction. I see good value
>> in this
>> direction of information flow. I feel that this is mostly a common
>> problem across H
>> and V. Hence I would not discard the H architecture right away.
> Adding SC->ALTO S in the H architecture does not add much new value.
> Since the ALTO Server is working for the specific SDN domain only, the
> more important of problem, i.e., how to coordinate multiple SCs in the
> whole network, remains unsolved. Plus, in the H architecture, we really
> do not have to differentiate ALTO S from SC, as the former could be
> easily integrated into the latter (since SC has the most updated network
> information already).

 From a modular design's point view, an SC could be a multiple-functional
components, multiple-machines system (e.g., front end, policy server,
database server). Hence, although conceptually we could say that an ALTO
Server can be integrated into an SC, a more detailed may reveal more 
structures.
> I agree that generally speaking, adding the SC->ALTO S information flow
> is pretty helpful to ALTO, as this enables ALTO to collect network
> information, which has not been addressed previously yet. However, we
> believe that the main distinctions between the V and H architectures
> include not only whether we have the SC->ALTO S flow, but also how we
> should decompose the ALTO related functionalities and design an
> efficient, evolvable architecture to support the growth of both SDN and
> ALTO.
>
>> A concern is
>> whether we are ready to define the SC -> ALTO Server information flow,
>> given the "early-stageness" of SDN. A related general comment is that
>> it maybe quite
>> helpful to extract common problems (e.g., unknown/dynamic network cost as
>> you mentioned) and new possibilities for ALTO when introducing SDN,
>> instead of
>> a specific setting of a network being partitioned into many
>> sub-networks in a V
>> architecture. What do you think?
> Partitioning the network and defining common problems/possibilities of
> SC->ALTO S information flow are two orthogonal problems. We believe that
> both are equally important. However, the first problem (partitioning the
> network) will largely determine what the SDN+ALTO architecture looks
> like, while the second problem is more about the types of detailed
> network information, its format, etc. From this perspective, it seems
> that the first problem is more important -- if the architecture is not
> set right at the beginning, to fix it at some later time would be
> difficult and costly. This draft is mainly focusing on the first
> problem, we may need another draft dedicated to the second problem.
>
Defining the first problem--partitioning the network clearly provides a
good use case and problem problem definition. This is a quite interesting
perspective.

>> A curious question, does the ALTO servers
>> (as well as the SC) in H form some kind of mesh (peering) among
>> themselves?
> Given current status of ALTO, we assumed that there is no peering among
> ALTO servers. However, if ALTO server peering becomes available and
> adopted, then the H architecture (and the SC->ALTO S flow) would make
> much more sense, which allows us to compare the two architectures more
> thoroughly.
>
>> - The document seems to imply some kind of exclusive SC/net app
>> setting: either
>> SC or net app, but not both. Do I misunderstand it? This depends on
>> how one
>> define the scope of SC. There can still be net apps running. Does it
>> make sense to
>> include (explicitly) the net apps into your discussions/figures to
>> include 4 types
>> of entities: devices, SC, ALTO Server, and net apps?
> Actually we did not mean to imply any kind of exclusive SC/net app
> setting. We need to update the draft to make it more explicit. In the
> figures, we did not include the net apps for the sake of simplicity.
> When we update the draft, we will add them to the figures.
>
sounds good.
>> I like your distinction between
>> SDN-aware and SDN-unaware apps. I am not sure I fully agree or
>> understand your
>> statement that SDN-aware apps would prefer direct communications with
>> SC, but
>> this will be an important architecture discussion at the ALTO meeting.
> What we have in mind is that since some apps are SDN aware, then it may
> prefer to behave differently from SDN unware apps (which does not
> directly communicate with SC), i.e., directly communicate with SC, which
> allows more flexibility and new possibilities of leveraging the SDN
> capabilities. Apparently discussions would be very helpful, and I am
> sure it would be a very interesting discussion about SDN-awareness and
> -unawareness at the ALTO meeting.
>
>> Thanks.
>>
>> Richard
>>
>> On 6/29/12 6:15 AM, Haiyong Xie wrote:
>>> Hi All,
>>>
>>> This is a proposal on the interaction between ALTO and SDN we'd like
>>> to discuss at our next meeting in Vancouver. This draft replaces the
>>> older submission draft-xie-alto-sdn-use-cases-01.txt which was
>>> withdrawn already.
>>>
>>> Comments or discussions are extremely welcome and appreciated.
>>>
>>> Best regards,
>>> Haiyong
>>>
>>> -----Original Message-----
>>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>>> Sent: Thursday, June 28, 2012 3:07 PM
>>> To: Haiyong Xie
>>> Cc: diego@tid.es; Hongtao Yin; Tina TSOU
>>> Subject: New Version Notification for
>>> draft-xie-alto-sdn-extension-use-cases-00.txt
>>>
>>>
>>> A new version of I-D, draft-xie-alto-sdn-extension-use-cases-00.txt
>>> has been successfully submitted by Haiyong Xie and posted to the
>>> IETF repository.
>>>
>>> Filename:     draft-xie-alto-sdn-extension-use-cases
>>> Revision:     00
>>> Title:         Use Cases for ALTO with Software Defined Networks
>>> Creation date:     2012-06-28
>>> WG ID:         Individual Submission
>>> Number of pages: 28
>>> URL:
>>> http://www.ietf.org/internet-drafts/draft-xie-alto-sdn-extension-use-cases-00.txt
>>> Status:
>>> http://datatracker.ietf.org/doc/draft-xie-alto-sdn-extension-use-cases
>>> Htmlized:
>>> http://tools.ietf.org/html/draft-xie-alto-sdn-extension-use-cases-00
>>>
>>>
>>> Abstract:
>>>      The introduction of SDN fundamentally changes the way that the ALTO
>>>      works.  This draft describes the Vertical Architecture and the
>>>      Horizontal Architecture allowing coherent coexistence of application
>>>      layer traffic optimization (ALTO) with software defined network
>>>      (SDN).  Unique requirements for design and operations are identified
>>>      and summarized, suggesting that the Vertical Architecture allows
>>>      better division, management, flexibility, privacy control and long-
>>>      term evolution of the network.  We also define the main interactions
>>>      and information flows, and present a set of use cases to illustrate
>>>      how we extend ALTO to support SDN, in the Vertical Architecture.
>>>
>>>                                                                                    
>>>
>>>
>>> The IETF Secretariat
>>> _______________________________________________
>>> alto mailing list
>>> alto@ietf.org
>>> https://www.ietf.org/mailman/listinfo/alto
>> .
>>


From Martin.Stiemerling@neclab.eu  Wed Jul  4 06:50:36 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 11AF421F8594 for <alto@ietfa.amsl.com>; Wed,  4 Jul 2012 06:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.747
X-Spam-Level: 
X-Spam-Status: No, score=-98.747 tagged_above=-999 required=5 tests=[AWL=-3.782, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, SARE_SUB_ENC_GB2312=1.345, 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 rXSb25gYCrPR for <alto@ietfa.amsl.com>; Wed,  4 Jul 2012 06:50:33 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 10F8121F852D for <alto@ietf.org>; Wed,  4 Jul 2012 06:50:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 6421A10172C; Wed,  4 Jul 2012 15:51:43 +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 Tra-510DiJHK; Wed,  4 Jul 2012 15:51:43 +0200 (CEST)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 49CFD10172A; Wed,  4 Jul 2012 15:51:18 +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; Wed, 4 Jul 2012 15:51:43 +0200
Message-ID: <4FF44A19.6020703@neclab.eu>
Date: Wed, 4 Jul 2012 15:50:17 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: "Guyingjie (Yingjie)" <guyingjie@huawei.com>
References: <4FF1B72C.4000209@neclab.eu> <CA+cvDaZvZAE2yUdvM3i09QEccghMpsEZbV3DAz3JVX7e+jJapA@mail.gmail.com> <4FF2F17B.1050300@neclab.eu> <A27496C192613C44A82D819E1B98DB573402F332@SZXEML511-MBS.china.huawei.com>
In-Reply-To: <A27496C192613C44A82D819E1B98DB573402F332@SZXEML511-MBS.china.huawei.com>
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [10.1.1.190]
Cc: Richard Alimi <ralimi@google.com>, "alto@ietf.org" <alto@ietf.org>, Roni even <Even.roni@huawei.com>
Subject: Re: [alto] =?gb2312?b?tPC4tDogIFdheSBmb3J3YXJkIGZvciB0aGUgUmVzZGlz?= =?gb2312?b?dHJpYnV0aW9u?=
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, 04 Jul 2012 13:50:36 -0000

Yingjie,

I had basically the same questions and it seems that Rich Alimi has
something in the pipe.

  Martin

On 07/04/2012 03:23 AM, Guyingjie (Yingjie) wrote:
> Hi Martin and all,
> The base protocol used to refer to draft-gu-alto-redistribution, and I am one of the authors, together with Richard and Roni.
> Is there any plan for the new dedicated redistribution draft, e.g. contributors and draft plan?
> 
> I am not very active in ALTO for sometime, so I maybe miss some discussion in the mail list on redistribution.
> Personally, I would suggest to awake the draft-gu-alto-redistribution, since there is many detail technical considerations for redistribution. Or at least we should take the Basic requirements and ALTO Redistribution Solutions Analysis to the new draft if there is any.
> 
> Best Regards
> Gu Yingjie
> 
> 
> -----ÓÊ¼þÔ­¼þ-----
> ·¢¼þÈË: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] ´ú±í Martin Stiemerling
> ·¢ËÍÊ±¼ä: 2012Äê7ÔÂ3ÈÕ ÀÖÀÖ21:20
> ÊÕ¼þÈË: Richard Alimi
> ³­ËÍ: alto@ietf.org
> Ö÷Ìâ: Re: [alto] Way forward for the Resdistribution
> 
> 
> 
> On 07/02/2012 07:37 PM, Richard Alimi wrote:
>> The material has been migrated to another document locally, but it
>> isn't yet ready for submission.    I don't think it should be
>> completely abandoned, but in my opinion the priority is lower than
>> getting the base protocol.  As was mentioned in the discussion w.r.t.
>> requirements, there are some things that it provides such as
>> guidelines on which clients should make use of the information and for
>> how long (above and beyond what we get for free from HTTP caching).
>>
>> With your AD hat on, do we need the additional document to be
>> explicitly mentioned in the charter?
> 
> It would be good to see this draft submitted. Getting a new milestone
> for this is not a big deal if the WG is in agreement.
> 
>     Martin
> 
>>
>> Rich
>>
>> On Mon, Jul 2, 2012 at 7:58 AM, Martin Stiemerling
>> <martin.stiemerling@neclab.eu> wrote:
>>> Hi all,
>>>
>>> I have just read the ALTO protocol slides of the meeting in Paris and do
>>> wonder what has ultimately happened to the redistribution, as the slide
>>> state:
>>>
>>> "Will be submitted as separate draft that may make use of JOSE"
>>> (http://www.ietf.org/proceedings/83/slides/slides-83-alto-2.pdf)
>>>
>>> This functionality is gone from the base protocol, but we do not have any
>>> replacement insight. Do we completely abandon this?
>>>
>>> Thanks,
>>>
>>>     Martin
>>> --
>>> 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
> 

-- 
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 haiyong.xie@huawei.com  Fri Jul  6 10:05:52 2012
Return-Path: <haiyong.xie@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 9856621F876E; Fri,  6 Jul 2012 10:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level: 
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, 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 Lmwe12W8JwhL; Fri,  6 Jul 2012 10:05:51 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id BB78721F8714; Fri,  6 Jul 2012 10:05:51 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHT64223; Fri, 06 Jul 2012 13:06:08 -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; Fri, 6 Jul 2012 10:05:02 -0700
Received: from [127.0.0.1] (10.193.38.33) by smtpsus.huawei.com (10.193.5.132) with Microsoft SMTP Server id 14.1.323.3; Fri, 6 Jul 2012 10:04:52 -0700
Message-ID: <4FF71A79.9090401@huawei.com>
Date: Fri, 6 Jul 2012 10:03:53 -0700
From: Haiyong Xie <haiyong.xie@huawei.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8
MIME-Version: 1.0
To: "Y. Richard Yang" <yry@cs.yale.edu>
References: <748A482AA35F7A4A8BD26465029B8C4A1B7C49EC@dfweml509-mbx.china.huawei.com> <4FF11869.1010408@cs.yale.edu> <4FF1DF7B.9080500@huawei.com> <4FF41835.5020002@cs.yale.edu>
In-Reply-To: <4FF41835.5020002@cs.yale.edu>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.193.38.33]
X-CFilter-Loop: Reflected
Cc: "altoext@ietf.org" <altoext@ietf.org>, "alto@ietf.org" <alto@ietf.org>, Andreas Voellmy <andreas.voellmy@yale.edu>, Hongtao Yin <hongtao.yin@huawei.com>
Subject: Re: [alto] FW: New Version Notification for draft-xie-alto-sdn-extension-use-cases-00.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: Fri, 06 Jul 2012 17:05:52 -0000

Hi Richard,

Please see my inline comments.

On 07/04/2012 03:17 AM, Y. Richard Yang wrote:
> ...
>> The H architecture implies that the network should NOT be segmented,
>> i.e., there exists only one SC; otherwise, the network will have
>> multiple ALTO servers, each is working with corresponding SC only, but
>> without exchanging information among multiple ALTO servers (we do not
>> have a protocol to do so yet).
>>
>
> This is different from my understanding. I thought that H still could
> allow
> network partition, say m sub-networks. Then there are m SCs and m ALTO
> servers. The m SCs can form a mesh/peering to work together. Now I
> understand
> your design. But how about the partitioned H design? Is it allowed? If
> there are
> convincing use cases for inter-ALTO Server in your design, then it
> identifies a need for inter-ALTO. What do you think?

H could allow network partition provided that the following two
conditions are satisfied:
(1) m SCs can form a mesh/peering to work together
(2) m ALTO servers could work jointly (e.g., by forming mesh/peering
among themselves).

Currently, we have a draft draft-yin-sdn-sdni-00.txt (
http://www.ietf.org/id/draft-yin-sdn-sdni-00.txt ) dedicated to
condition (1), and this draft hopeful could provide a starting point for
solving the SC mesh/peering problem. However, we are not aware of any
draft that solves condition (2). If you know any such work that could be
leveraged to solve (2), please kindly let us know.

Given the current status, we think that it is difficult (or too early)
to do network partition in the H architecture. However, if both of the
above two conditions are satisfied, I believe network partitioning is
feasible in the H architecture.

Regarding inter-ALTO, we think that although it is doable, but we do not
see convincing use cases yet; we compared the need for inter-SDN-domain
and inter-ALTO, and think that inter-SDN-domain has more convincing uses
cases (see our draft draft-yin-sdn-sdni-00).

>
>>> ......
>> Adding SC->ALTO S in the H architecture does not add much new value.
>> Since the ALTO Server is working for the specific SDN domain only, the
>> more important of problem, i.e., how to coordinate multiple SCs in the
>> whole network, remains unsolved. Plus, in the H architecture, we really
>> do not have to differentiate ALTO S from SC, as the former could be
>> easily integrated into the latter (since SC has the most updated network
>> information already).
>
> From a modular design's point view, an SC could be a multiple-functional
> components, multiple-machines system (e.g., front end, policy server,
> database server). Hence, although conceptually we could say that an ALTO
> Server can be integrated into an SC, a more detailed may reveal more
> structures.

Agreed. Our viewpoint is that since SC architecture and standard are not
settled yet (they are still evolving), we'd better not rush into the
approach of integrating SC and ALTO; instead, separating them is a
safer, more flexible and economic approach.

>> ......
>> Partitioning the network and defining common problems/possibilities of
>> SC->ALTO S information flow are two orthogonal problems. We believe that
>> both are equally important. However, the first problem (partitioning the
>> network) will largely determine what the SDN+ALTO architecture looks
>> like, while the second problem is more about the types of detailed
>> network information, its format, etc. From this perspective, it seems
>> that the first problem is more important -- if the architecture is not
>> set right at the beginning, to fix it at some later time would be
>> difficult and costly. This draft is mainly focusing on the first
>> problem, we may need another draft dedicated to the second problem.
>>
> Defining the first problem--partitioning the network clearly provides a
> good use case and problem problem definition. This is a quite interesting
> perspective.
Agreed.

From richard.alimi@gmail.com  Sun Jul  8 10:09:36 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 493FE21F85AF for <alto@ietfa.amsl.com>; Sun,  8 Jul 2012 10:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.584
X-Spam-Level: 
X-Spam-Status: No, score=-2.584 tagged_above=-999 required=5 tests=[AWL=0.166,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 aevPYRZ6Kv7n for <alto@ietfa.amsl.com>; Sun,  8 Jul 2012 10:09:35 -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 EB42A21F8568 for <alto@ietf.org>; Sun,  8 Jul 2012 10:09:34 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so18330460pbc.31 for <alto@ietf.org>; Sun, 08 Jul 2012 10:09:57 -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=/qjF6cqHBiABPaD/5W2+714Iol/1JJ0M6Is1csV3KrQ=; b=xct/7UbQzfihGCPouuTSBRKq3yzfuhS2kTKX1eODp/KiQYJjVhlR/+OXec1pdmod27 dJi05ylbZcQwK6Iao3WBg4Fa2Fukc54pFP8cF+FWl+iemnlU0zZHnXzGKzPrni59yJVD ezJ6/Gt9lLoS7HiBWtylheSLPEcronJ8RrkjbkmGdbIQCAKFFMnshnle9sSI2mnVsmFH NMF20SHO1Rdna+2LofkX+jGIiw7joQMGU7IoaXnmsqzKNyj7HYhSxCEPnkcBRiYHufpa 07BK1TTK4u+F/CpDDeaY9aE048NBWamo8NFyPaTH3B/5YR9Yi/1feqPlGSGQtyLZ8thv z4Yw==
Received: by 10.66.85.36 with SMTP id e4mr59634955paz.32.1341767397184; Sun, 08 Jul 2012 10:09:57 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.143.28.8 with HTTP; Sun, 8 Jul 2012 10:09:36 -0700 (PDT)
In-Reply-To: <4FF34C05.2010400@neclab.eu>
References: <4F8BE443.9050903@telecomitalia.it> <20120514061451.GA3136@gw01.ehlo.wurstkaes.de> <CA+cvDab1XR40W7FBHhDNOTTag7tvSihVe7BSMVbAP6W-Qtk91A@mail.gmail.com> <4FF1B8CB.7090005@neclab.eu> <CA+cvDabEaB8N5835xuECtqKMejLVaOk5qRgeTnAimL=6gCVHUA@mail.gmail.com> <4FF34C05.2010400@neclab.eu>
From: Richard Alimi <rich@velvetsea.net>
Date: Sun, 8 Jul 2012 10:09:36 -0700
X-Google-Sender-Auth: Mx5jEymkwQkxBxjLAjlN2XBnhcw
Message-ID: <CA+cvDaYq+t8ezFNgwuvDpuBcJP_s8QsUWEvHTW-q9eDZbd+36g@mail.gmail.com>
To: Martin Stiemerling <martin.stiemerling@neclab.eu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-ietf-alto-protocol@tools.ietf.org, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [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: Sun, 08 Jul 2012 17:09:36 -0000

On Tue, Jul 3, 2012 at 12:46 PM, Martin Stiemerling
<martin.stiemerling@neclab.eu> wrote:
>
>
> On 07/02/2012 08:35 PM, Richard Alimi wrote:
>>
>> On Mon, Jul 2, 2012 at 8:05 AM, Martin Stiemerling
>> <martin.stiemerling@neclab.eu> wrote:
>>>
>>> [writing with no Area Director hat on, i.e., as a random community
>>> member]
>>
>>
>> Good to have you back :)
>
>
> Thanks, finally there is time again for ALTO :)
>
>
>>
>>> Hi Richard, all,
>>>
>>> On 07/02/2012 08:38 AM, Richard Alimi wrote:
>>> [...]
>>>
>>>
>>>>> 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, ...)
>>>>
>>>>
>>>>
>>>> It needs something more than just an I-D since that is a pretty low bar.
>>>
>>>
>>>
>>> You can specify 'protocol specification' or 'expert review' as the bar
>>> for
>>> an extension.
>>> See also RFC 5226 for a discussion of this:
>>> http://tools.ietf.org/html/rfc5226
>>>
>>>
>>>>
>>>> Do people think a registry is needed for this?  If not, perhaps we can
>>>> just make this more explicit that it needs to be a standards-track
>>>> RFC.
>>>
>>>
>>>
>>> There should be a registry where you can add additional address types.
>>> Otherwise it is really hard to get new address types in a clean way into
>>> the
>>> protocol.
>>> A registry allows also to keep track about all existing address types
>>> (out
>>> of the ALTO protocol and what comes later on).
>>
>>
>> Right - okay. We'll add an Address Type registry.  That said, it'd be
>> really nice to point to an existing registry. I think we'd need the
>> following for such a registry:
>> (1) A textual string for an address type itself
>> (2) A specification (preferably a pointer to one) for how to serialize
>> and deserialize a textual address of that type.
>> (3) (maybe, depending on the result of the discussion below) a
>> statement of how an address type can be mapped into IPv4/v6 addresses.
>>
>> However, when browsing through the available IANA registries I didn't
>> see one that really matched those requirements.  Does anyone have a
>> better option before we go about defining our own?
>
>
> We need to create our own registry for this, which isn't a big deal. Just
> write this up in the IANA considerations section.

Sounds good to me.

>
>
>>
>>>>
>>>>>>      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.
>>>>>
>>>>>
>>>>>
> [...]
>
>
>>>>
>>>>
>>>> The use of JSON and Section 7.2.7 also helps with extensions.
>>>>
>>>>>>      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
>>>>
>>>>
>>>>
>>>> Yeah.  There was a discussion when going to the REST-ful approach
>>>> about whether we wanted any explicit version numbers or not.  The idea
>>>> was that we didn't need an ALTO version number exposed to applications
>>>> if we used media types appropriately.  Using media types like you
>>>> suggested is certainly one approach.
>>>
>>>
>>>
>>> Irrespectively of what mechanisms is being used, this protocol needs
>>> versioning support. However, I'm not sure that media-types are the best
>>> way
>>> forward for this.
>>> What would be a different approach when using media types?
>>
>>
>> Do you mean a different approach *than* using media types?  One other
>> option would be to revert revert back to what we had before, which is
>> have an explicit field in each and every response.
>>
>> Here's one pointer to mailing list discussions about protocol
>> versioning and media types:
>>    http://www.mail-archive.com/alto@ietf.org/msg00609.html
>> I'll note that our AD at the time (Lisa) was one of the people
>> suggesting we use content negotiation to provide protocol versioning.
>>
>> My preference would be to not re-hash the merits of protocol
>> versioning unless we think there is a clear technical advantage over
>> what we have now.
>
>
> Let me go through the old email thread to see what happened back then.
>
>
>>
>>>>
>>>>>> 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..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.
>>>>
>>>>
>>>>
>>>> We also had a discussion about this in the protocol overhaul for
>>>> making it REST-ful.  The guidance we received there was to not repeat
>>>> details from RFC2616.  I'm not sure I see much utility in adding
>>>> specifics in the ALTO protocol document, since it would basically
>>>> amount to saying "If you think you are overloaded, you are free to
>>>> return a 503."  Then, if we were to add that, people would ask "you
>>>> gave me guidance on using 503, but you didn't tell me when I should or
>>>> should not use chunked transfer encoding.. how about that??"  The idea
>>>> was that the statements in Section 7.2, as well as some intelligence
>>>> on behalf of implementers on how to apply RFC2616, would answer all of
>>>> these questions.
>>>
>>>
>>>
>>> That is not a good way of specifying things. There is no need to say how
>>> a
>>> 503 response looks like, but it is definitely good to say when an ALTO
>>> protocol must reply with such a code. "intelligence ...of implementers"
>>> will
>>> cause ALTO protocol implementations that do not interoperate.
>>
>>
>> If we want to make revisions here, can you give some guidance on where
>> we should recommend certain usage of HTTP and where we shouldn't?
>> Should it be just additional text to ensure that we satisfy the
>> requirements on overload control, or additional guidance on how to to
>> employ other parts of HTTP such as transfer encoding, caching, when to
>> use redirects, etc?
>
>
> I would describe only mechanisms which are required by the protocol (or by
> the requirements). The protocol spec must say: return a 503 if overloaded,
> for instance. I do not see the need to specify how ALTO is using each and
> every feature of HTTP, but it should be clear how functionality required by
> the ALTO protocol is mapped to the underlying HTTP protocol.

Okay - we'll add some text for overload control.

Thanks,
Rich

>
> Thanks,
>
>   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 leeyoung@huawei.com  Sun Jul  8 21:48:37 2012
Return-Path: <leeyoung@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 575F321F852B; Sun,  8 Jul 2012 21:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.561
X-Spam-Level: 
X-Spam-Status: No, score=-6.561 tagged_above=-999 required=5 tests=[AWL=0.038,  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 vs8qFJoZdLxL; Sun,  8 Jul 2012 21:48:36 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 03E0B21F852A; Sun,  8 Jul 2012 21:48:35 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHV89123; Mon, 09 Jul 2012 00:48:59 -0400 (EDT)
Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Sun, 8 Jul 2012 21:48:37 -0700
Received: from dfweml511-mbx.china.huawei.com ([169.254.16.20]) by dfweml404-hub.china.huawei.com ([10.193.5.203]) with mapi id 14.01.0323.003; Sun, 8 Jul 2012 21:48:38 -0700
From: Leeyoung <leeyoung@huawei.com>
To: "alto@ietf.org" <alto@ietf.org>, "altoext@ietf.org" <altoext@ietf.org>
Thread-Topic: New Version Notification for draft-lee-alto-ext-dc-resource-00.txt
Thread-Index: AQHNXY1JHWFc1RpFJkuiWBzS1J5hNZcgX7IQ
Date: Mon, 9 Jul 2012 04:48:37 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E1720CC2C24@dfweml511-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.129.92]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [alto] FW: New Version Notification for draft-lee-alto-ext-dc-resource-00.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, 09 Jul 2012 04:48:37 -0000

SGkgQWxsLA0KDQpBcyBwYXJ0IG9mIHRoZSBpMmFleCBpbml0aWF0aXZlLCB0aGlzIGRyYWZ0IGFk
ZHJlc3NlcyBob3cgQUxUTyBwcm90b2NvbCBjYW4gYmUgdXNlZCB0byBjb2xsZWN0IERDIHJlc291
cmNlIGluZm9ybWF0aW9uLg0KDQpZb3VyIGNvbW1lbnRzIGFyZSBhcHByZWNpYXRlZC4gVGhhbmtz
Lg0KDQpZb3VuZw0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpbnRlcm5l
dC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmddIA0KU2Vu
dDogU3VuZGF5LCBKdWx5IDA4LCAyMDEyIDExOjQyIFBNDQpUbzogTGVleW91bmcNCkNjOiBTcmVl
a2FudGggbWFkaGF2YW47IGdyZWdiQGdyb3R0by1uZXR3b3JraW5nLmNvbTsgRGhydXYgRGhvZHkN
ClN1YmplY3Q6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtbGVlLWFsdG8tZXh0
LWRjLXJlc291cmNlLTAwLnR4dA0KDQoNCkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1sZWUt
YWx0by1leHQtZGMtcmVzb3VyY2UtMDAudHh0DQpoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0
dGVkIGJ5IFlvdW5nIExlZSBhbmQgcG9zdGVkIHRvIHRoZQ0KSUVURiByZXBvc2l0b3J5Lg0KDQpG
aWxlbmFtZToJIGRyYWZ0LWxlZS1hbHRvLWV4dC1kYy1yZXNvdXJjZQ0KUmV2aXNpb246CSAwMA0K
VGl0bGU6CQkgQUxUTyBFeHRlbnNpb25zIGZvciBDb2xsZWN0aW5nIERhdGEgQ2VudGVyIFJlc291
cmNlIEluZm9ybWF0aW9uDQpDcmVhdGlvbiBkYXRlOgkgMjAxMi0wNy0wOA0KV0cgSUQ6CQkgSW5k
aXZpZHVhbCBTdWJtaXNzaW9uDQpOdW1iZXIgb2YgcGFnZXM6IDEwDQpVUkw6ICAgICAgICAgICAg
IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWxlZS1hbHRvLWV4dC1k
Yy1yZXNvdXJjZS0wMC50eHQNClN0YXR1czogICAgICAgICAgaHR0cDovL2RhdGF0cmFja2VyLmll
dGYub3JnL2RvYy9kcmFmdC1sZWUtYWx0by1leHQtZGMtcmVzb3VyY2UNCkh0bWxpemVkOiAgICAg
ICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtbGVlLWFsdG8tZXh0LWRjLXJlc291
cmNlLTAwDQoNCg0KQWJzdHJhY3Q6DQogICBJbiBhIG5ldHdvcmtlZCBhcHBsaWNhdGlvbiBlbnZp
cm9ubWVudCB3aGVyZSByZXNvdXJjZXMgKGUuZy4sDQogICBjb21wdXRpbmcsIHN0b3JhZ2UsIGV0
Yy4pIGFyZSBnZW9ncmFwaGljYWxseSBkaXN0cmlidXRlZCBpbiBEYXRhDQogICBDZW50ZXJzLCBh
IGtleSBkZWNpc2lvbiBpcyB0byBhbGxvY2F0ZSB0aGUgYXBwbGljYXRpb24gcmVxdWVzdCB0byBh
bg0KICAgIm9wdGltYWwiIERhdGEgQ2VudGVyIGxvY2F0aW9uIGluIHdoaWNoIHRvIGhvc3QgdGhl
IGFwcGxpY2F0aW9uDQogICByZXF1ZXN0LiBLZXkgY29uc3RyYWludHMgaW4gdGhpcyBkZWNpc2lv
biBpbmNsdWRlIHJlc291cmNlDQogICBhdmFpbGFiaWxpdHksIG5ldHdvcmsgY29zdCwgaW5mcmFz
dHJ1Y3R1cmUgY29uc3RyYWludHMgKGUuZy4sIHBvd2VyKQ0KICAgYW5kIG90aGVycy4gVGhpcyBk
cmFmdCBwcm9wb3NlcyBhbiBBTFRPIGV4dGVuc2lvbiB0byBzdXBwb3J0IGRhdGENCiAgIGNlbnRl
ciByZXNvdXJjZSBpbmZvcm1hdGlvbiBtb2RlbCBhbmQgaXRzIHJlbGF0ZWQgcHJvdG9jb2wNCiAg
IGV4dGVuc2lvbnMgYXMgcGFydCBvZiB0aGUgaW5mcmFzdHJ1Y3R1cmUgdG8gYXBwbGljYXRpb24g
aW5mb3JtYXRpb24NCiAgIGV4cG9zdXJlIChpMmFleCkgaW5pdGlhdGl2ZS4NCg0KICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIA0KDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0DQo=

From richard.alimi@gmail.com  Sun Jul  8 21:58:52 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 C90CB21F869C for <alto@ietfa.amsl.com>; Sun,  8 Jul 2012 21:58:52 -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.036, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_14=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 D3xjkeDECj4j for <alto@ietfa.amsl.com>; Sun,  8 Jul 2012 21:58:52 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id F19CA21F8668 for <alto@ietf.org>; Sun,  8 Jul 2012 21:58:50 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so10662233ghb.31 for <alto@ietf.org>; Sun, 08 Jul 2012 21:59:14 -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=zPb1tGtjDRF5wWUzro0hPth7hq7r5OvJ2fNy8H05ML4=; b=o+dTUaS17rszqrvV3x7AW0fwf8/ClUUnRDRDqnjdJ+uvN8qjmwGDBOcsvWcVgl7OAP 83ml17L+z4MS8ZliOIrCeOjYLuNxrpjtBSZAIVskbfMzFk8+1jYeGwJjmxXWO+jOUWnR tEVWgMbwBfRmWx2mdJugrDy0FK9SU6Y0eQ0v+tNVrSpKi2Ly5/v3/58la5TnkLg2Jck1 wqdIgVhBrshPNBc3L8h2C4gwsYoG8qWwxVFh6KtdPe3vRhkw9GHx+IjHXA98XDI2cml4 f9bVMgLIBafBYyEvW/nr/WP/xlJxplTUddsdmuBYdYHKO2C5HD+Un1HLpWFLlnCM3PKj 4vuA==
Received: by 10.66.81.3 with SMTP id v3mr7003979pax.62.1341809954104; Sun, 08 Jul 2012 21:59:14 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.143.28.8 with HTTP; Sun, 8 Jul 2012 21:58:53 -0700 (PDT)
In-Reply-To: <CANUuoLqpJTQy6WbHjiX75YJmLEDV+yg1E_8-GX1okHOoH0CJdg@mail.gmail.com>
References: <4F8BE443.9050903@telecomitalia.it> <4FAD5745.2060009@alcatel-lucent.com> <CA+cvDab3P0-68m6+mZ+4K0FedJ7_MK6SGXhD2kQKupXuCDLgDw@mail.gmail.com> <CA+cvDaZJ-RdJKf9mSTP0qbz3vS1mK28XQYpzpfQ69EZbMCF_5A@mail.gmail.com> <20120702154359.GV5342@gw01.ehlo.wurstkaes.de> <CA+cvDaYdzoGub0gvwbV2EfvCTmnS73Q5gSf+pvDH-sCsRjtPQg@mail.gmail.com> <20120702202219.GX5342@gw01.ehlo.wurstkaes.de> <CANUuoLqpJTQy6WbHjiX75YJmLEDV+yg1E_8-GX1okHOoH0CJdg@mail.gmail.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Sun, 8 Jul 2012 21:58:53 -0700
X-Google-Sender-Auth: LGyr_cLGKH-2CklDFPkRFqtu0Ug
Message-ID: <CA+cvDaZaZ3uxUYvz0x9KJGLUXhu=K2qfQV36Bqc0m3ZveEqFNQ@mail.gmail.com>
To: "Y. Richard Yang" <yry@cs.yale.edu>
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: Mon, 09 Jul 2012 04:58:53 -0000

On Tue, Jul 3, 2012 at 12:15 AM, Y. Richard Yang <yry@cs.yale.edu> wrote:
> Hi Sebastian, Rich,
>
> On Tuesday, July 3, 2012, Sebastian Kiesel wrote:
> For example, the resource consumer may not ask, as
>>
>> Hi Rich,
>>
>> On Mon, Jul 02, 2012 at 11:09:51AM -0700, Richard Alimi wrote:
>> > We can certainly do an inventory on terminology to see if anything
>> > else from RFC5693 should be applied.  I'm pretty sure it won't just be
>> > substituting "endpoints" with either "resource consumer" or "resource
>> > provider" though, since that depends quite a bit on how the
>> > application uses ALTO information, and what the costs actually
>> > represent.
>>
>>
>> > That is, we can't simply say that that a resource consumer
>> > is choosing a resource provider.
>>
>> I would exactly say this.
>>
>> Or maybe, to be more precise: A resource consumer chooses - or asks a
>> third party to choose on behalf of it - one or several resource
>> providers from a set of candidate resource providers (and ALTO is
>> consulted in order to improve that decision).
>
>
> Using your good reasoning below, even the preceding sentence may have
> subtlety: "ask" may imply some messages, but the app may not have a
> message. How about remove "ask"?
>
>
>>
>> However, it it is important that resource is not neccessarily a file or
>> content stream. Therefore, the above sentence does not imply that most
>> of the data flows from the resource provider(s) to the resource consumer!
>> Because we might have independent control and data connections
>> it would also be too simplistic to say the resource consumer
>> is the "connection/flow initiator", though most of the time this is true.
>>
>>
>> > It's conceivable that the resource
>> > provider could be doing the choosing in a push-based protocol.
>>
>> If we have a push-based protocol, where one could send some
>> kind of information to one of several "sinks", I'd say that the
>> (ALTO-/RFC5693-)resources are these sinks, and the "pusher"
>> is the resource consumer, which consumes the sink-resource.
>>
>>
>> > As a
>> > slightly more interesting example, what if I also wanted to try and
>> > reduce latency for ACKs in the opposite direction to protect myself
>> > against asymmetric routing - then then I'd be querying a latency map
>> > for the cost from the resource consumer to the resource provider.   In
>> > the ALTO Protocol we try to simply express these as costs between
>> > endpoints.
>>
>> ack.
>>
>> > It's an application-level concern about who does the
>> > choosing, and making sure they are using the costs appropriately.
>>
>> Each application uses its own terminology and has specific ideas on who
>> assumes the roles of "client", "server", "peer", ...
>> My understanding of the ALTO terminology is that we can use it to
>> describe the (ALTO-relevant) features of an arbitrary protocol in
>> a uniform way. And in particular, I would describe the general
>> ALTO problem as:
>>
>> We have 1 resource consumer and N candidate resource providers.
>> We want to have data flows between the resource consumer and
>> M < N resource providers. Therefore, we need to choose M out of N,
>> and ALTO is supposed to help on that decision.

I agree that this is a good way to state the common use case.

>>
>> > All that said, I think we do need to improve the protocol draft to
>> > explicitly say how "endpoint" relates to "resource consumer" and
>> > "resource provider" which is mentioned in other documents.  How about
>> > the following:
>> >
>> > Add this to Section 2.1.1:
>> >   "An Endpoint Address is typically either the address of a Resource
>> > Provider or Resource Consumer."
>
>
> Suppose we want to simplify the definition by removing "address" from the
> the above.
> Then we have "An Endpoint is typically either a Resource Provider or
> Resource
> Consumer." How does this read? What is an atypical case?

Removing address sounds good to me.  One of the suggestions elsewhere
on the list was to add 'Endpoint' as a term, so I put this text in
that new section.

>> Is it always the address of exactly one host (either r.prov. or r.cons.)?
>> Otherwise, the already defined term "host group descriptor" might make
>> sense?
>>
>> > Add change this text in Section 5:
>> >   "Each Path Cost is the end-to-end cost from the source to the
>> > destination."
>> > to instead read:
>> >   "Each Path Cost is the end-to-end cost from the source to the
>> > destination.  For example, if the cost is expected correlated with
>> > throughput, a typical application concerned with bulk data transfer
>> > may use the Resource Provider as the source, and Resource Consumer as
>> > the destination."
>>
>> change "a typical application concerned with bulk data transfer"
>> to "a typical application concerned with bulk data retrieval", then
>> we have one of the most important use cases as an example - though
>> the example does not reflect the full complexity of that issue ...
>>
> Agree on the subtlety. Instead of an example in the definition,  how about a
> short discussion paragraph starting as "Each application has its
> interpretation
> on who assumes the role of ... and hence how to utilize Path Cost provided
> by ALTO. For example, ..."

Thank you Sebastian and Richard for the suggestions.  How about the
following paragraph added to Section 5 just after paragraph 2:

  Each application may independently determine how the Resource Consumer
  and Resource Provider are designated as the source or destination, and hence
  how to utilize the Path Cost provided by ALTO.  For example,
  if the cost is expected to be correlated with throughput, a typical
  application concerned with bulk data retrieval may use the Resource Provider
  as the source, and Resource Consumer as the destination.

Thanks,
Rich

>
> -yry
>
>>
>>   S.
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto

From ben@niven-jenkins.co.uk  Sun Jul  8 22:34:16 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 BC08B21F8686 for <alto@ietfa.amsl.com>; Sun,  8 Jul 2012 22:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.505
X-Spam-Level: 
X-Spam-Status: No, score=-101.505 tagged_above=-999 required=5 tests=[AWL=0.866, 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 xnkMhX1ESfAw for <alto@ietfa.amsl.com>; Sun,  8 Jul 2012 22:34:16 -0700 (PDT)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id E8DDE21F8675 for <alto@ietf.org>; Sun,  8 Jul 2012 22:34:15 -0700 (PDT)
Received: from cpc4-cmbg17-2-0-cust814.5-4.cable.virginmedia.com ([86.14.227.47] helo=[192.168.0.33]) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1So6cH-0000pN-Na; Mon, 09 Jul 2012 06:34:38 +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+cvDab1XR40W7FBHhDNOTTag7tvSihVe7BSMVbAP6W-Qtk91A@mail.gmail.com>
Date: Mon, 9 Jul 2012 06:34:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <005034CF-005D-4400-817F-E2D2AAF6608F@niven-jenkins.co.uk>
References: <4F8BE443.9050903@telecomitalia.it> <20120514061451.GA3136@gw01.ehlo.wurstkaes.de> <CA+cvDab1XR40W7FBHhDNOTTag7tvSihVe7BSMVbAP6W-Qtk91A@mail.gmail.com>
To: Richard Alimi <rich@velvetsea.net>
X-Mailer: Apple Mail (2.1084)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: draft-ietf-alto-protocol@tools.ietf.org, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [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, 09 Jul 2012 05:34:16 -0000

Rich, Colleagues,

Some comments from me inline...

On 2 Jul 2012, at 07:38, Richard Alimi wrote:
> On Sun, May 13, 2012 at 11:14 PM, Sebastian Kiesel =
<ietf-alto@skiesel.de> wrote:
>>>   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
>>>=20
>>>   o  no re-use should occur
>>>=20
>>>   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
>>>=20
>>>   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
>>>=20
>>>   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
>>>=20
>>>   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
>>=20
>> 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
>=20
> Yeah - I'm personally okay with this current state, since we
> consciously removed the section on Redistribution and left that for an
> extension.

It's a while since I looked at ALTO in detail so my memory of various =
aspects is a little hazy but I wonder if the HTTP Vary header can help =
us here?

>>>   REQ.  ARv14-27: An ALTO client protocol MUST include protocol
>>>   versioning support, in order to clearly distinguish between
>>>   incompatible versions of the protocol.
>>=20
>> 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."
>>=20
>>    As workaround, one could define new media types such as
>>    alto-directory_v2_0+json   or
>>    alto2-directory+json
>=20
> Yeah.  There was a discussion when going to the REST-ful approach
> about whether we wanted any explicit version numbers or not.  The idea
> was that we didn't need an ALTO version number exposed to applications
> if we used media types appropriately.  Using media types like you
> suggested is certainly one approach.

Using media types along with HTTP conneg gives the advantage that the =
client can specified a prioritised list of versions (of media-types) =
that it supports in its requests and the server can respond =
appropriately (including an appropriate error response if it cannot =
serialise the response in the requested media-type version(s), e.g. =
because it needs to use a higher versioned media-type than the client =
supports).

The other advantage is that the protocol machinery to do the negotiation =
already exists in HTTP and we do not need to redefine ALTO specific =
protocol machinery to perform the same function.

The downside is we end up minting new media-types for incompatible =
changes between ALTO versions, but minting a new media-type is "cheap".

Ben


From richard.alimi@gmail.com  Sun Jul  8 22:41:13 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 C35D311E8080 for <alto@ietfa.amsl.com>; Sun,  8 Jul 2012 22:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[AWL=0.153,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 RiZlR4gPFAo2 for <alto@ietfa.amsl.com>; Sun,  8 Jul 2012 22:41:13 -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 129A411E8079 for <alto@ietf.org>; Sun,  8 Jul 2012 22:41:13 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so19192233pbc.31 for <alto@ietf.org>; Sun, 08 Jul 2012 22:41:37 -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=DhnH4q9NlD8mUXLOqrl2gazzEEfk7BbYspS6mQQMoL0=; b=CEawklzRv0tFJUczqgbWjyPJwldQpRqa8CkaWM08j6nHjFUyoGjtIaTG8FVyXGiBkE dYwzZHovrbTnoYhd8RjIvrARvftbrahAy0Ivs4AvpQEL094GWd5VKjQuwMvfdIGriTzU h6uvIg0z5wonN5XicjcxEMr8c694nI49QiMErFnPfb7Zp60j3/KrBl5EqliCWCIDJ3gi nFkRf0kZQSTwoTbozpBhlACo8OsW5a47nAR70I9RMgcoicYPmgn227pPJMJIO9cBQXzo e9TvsBq1ooF8+nE4IzVkeDcAzplCw7fzsFSVdbkxRnbiWoAbdR6PETI42j+QKSB/1Idi 7dyw==
Received: by 10.68.241.228 with SMTP id wl4mr56649773pbc.51.1341812496779; Sun, 08 Jul 2012 22:41:36 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.143.28.8 with HTTP; Sun, 8 Jul 2012 22:41:16 -0700 (PDT)
In-Reply-To: <005034CF-005D-4400-817F-E2D2AAF6608F@niven-jenkins.co.uk>
References: <4F8BE443.9050903@telecomitalia.it> <20120514061451.GA3136@gw01.ehlo.wurstkaes.de> <CA+cvDab1XR40W7FBHhDNOTTag7tvSihVe7BSMVbAP6W-Qtk91A@mail.gmail.com> <005034CF-005D-4400-817F-E2D2AAF6608F@niven-jenkins.co.uk>
From: Richard Alimi <rich@velvetsea.net>
Date: Sun, 8 Jul 2012 22:41:16 -0700
X-Google-Sender-Auth: 97V_56S18-SWzRUQBXZRM4r04V0
Message-ID: <CA+cvDaazJ8smspUTPUzx24zvF-ymVi8UPFM62aH9Q1J1Xqjpwg@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: draft-ietf-alto-protocol@tools.ietf.org, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [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, 09 Jul 2012 05:41:13 -0000

On Sun, Jul 8, 2012 at 10:34 PM, Ben Niven-Jenkins
<ben@niven-jenkins.co.uk> wrote:
> Rich, Colleagues,
>
> Some comments from me inline...
>
> On 2 Jul 2012, at 07:38, Richard Alimi wrote:
>> On Sun, May 13, 2012 at 11:14 PM, Sebastian Kiesel <ietf-alto@skiesel.de=
> wrote:
>>>>   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-remove=
d
>>>    section 8 of draft-ietf-alto-protocol-10
>>
>> Yeah - I'm personally okay with this current state, since we
>> consciously removed the section on Redistribution and left that for an
>> extension.
>
> It's a while since I looked at ALTO in detail so my memory of various asp=
ects is a little hazy but I wonder if the HTTP Vary header can help us here=
?

It may help with parts of it, but note that some of these requirements
depend on ALTO-layer information and not HTTP headers.  Additionally,
the redistribution mechanism was also designed for sending ALTO
resources via non-HTTP protocols.

>
>>>>   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
>>
>> Yeah.  There was a discussion when going to the REST-ful approach
>> about whether we wanted any explicit version numbers or not.  The idea
>> was that we didn't need an ALTO version number exposed to applications
>> if we used media types appropriately.  Using media types like you
>> suggested is certainly one approach.
>
> Using media types along with HTTP conneg gives the advantage that the cli=
ent can specified a prioritised list of versions (of media-types) that it s=
upports in its requests and the server can respond appropriately (including=
 an appropriate error response if it cannot serialise the response in the r=
equested media-type version(s), e.g. because it needs to use a higher versi=
oned media-type than the client supports).
>
> The other advantage is that the protocol machinery to do the negotiation =
already exists in HTTP and we do not need to redefine ALTO specific protoco=
l machinery to perform the same function.
>
> The downside is we end up minting new media-types for incompatible change=
s between ALTO versions, but minting a new media-type is "cheap".
>
> Ben
>

From enrico.marocco@telecomitalia.it  Mon Jul  9 00:49:52 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 E6E2421F8666 for <alto@ietfa.amsl.com>; Mon,  9 Jul 2012 00:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.719
X-Spam-Level: 
X-Spam-Status: No, score=-101.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 RizAJUOD2DMo for <alto@ietfa.amsl.com>; Mon,  9 Jul 2012 00:49:52 -0700 (PDT)
Received: from GRFEDG701RM001.telecomitalia.it (grfedg701rm001.telecomitalia.it [217.169.121.20]) by ietfa.amsl.com (Postfix) with ESMTP id 00B4821F8594 for <alto@ietf.org>; Mon,  9 Jul 2012 00:49:51 -0700 (PDT)
Received: from grfhub702rm001.griffon.local (10.19.3.9) by GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP Server (TLS) id 8.3.245.1; Mon, 9 Jul 2012 09:50:12 +0200
Received: from MacLab.local (10.229.8.43) by smtp.telecomitalia.it (10.19.9.235) with Microsoft SMTP Server (TLS) id 8.3.245.1; Mon, 9 Jul 2012 09:50:11 +0200
Message-ID: <4FFA8D33.6060706@telecomitalia.it>
Date: Mon, 9 Jul 2012 09:50:11 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "alto@ietf.org" <alto@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms000705040308020105000900"
X-TI-Disclaimer: Disclaimer1
Subject: [alto] Agenda requests for IETF 84
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, 09 Jul 2012 07:49:53 -0000

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

Folks,

if you have any requests for agenda slots at the next IETF meeting,
please send them to Vijay and me by Tuesday, July 17. As usual, priority
will be given to charter items, and to topics that have been already
presented and discussed on the list.

In order to lower the loss probability, please send your request even if
you have already sent it before this call went out.

--=20
Ciao,
Enrico


--------------ms000705040308020105000900
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+0ggds992kxggPd
MIID2QIBATCBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp
BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0
YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMC30AwCQYF
Kw4DAhoFAKCCAh0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTIwNzA5MDc1MDExWjAjBgkqhkiG9w0BCQQxFgQUshQbMVKVw9/b593dLhrCLDwZm2owbAYJ
KoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4G
CCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB
pQYJKwYBBAGCNxAEMYGXMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20g
THRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG
A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EC
AwLfQDCBpwYLKoZIhvcNAQkQAgsxgZeggZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQQIDAt9AMA0GCSqGSIb3DQEBAQUABIIBAFC8DZR3lWuw23Dxpzt429rYls+iyUe8
2ZrVqszugcCT5q0ueaQ+YzXD8BEZ9QI8jpqe47U2FEv+ychYPY8BIoD6wYsPx4Hq/WFDiDjO
esbqsfauYzPEFwItsQhH7fjFsDrXsVVoDFA74d/rYklHqZxhqJEwx0kmp6fzbOw1J6eMK4BB
RPlHo2CPAQYXF4XypUi4XHRVYkBfZaGwL05oDt1J+boacZkKXgmuQNkc/NuMJUeEd5navCAT
2pa1PQu7mp6bHeVVIS0pqLXJwBNzHA+5mybAsBXRftfZJnsC4MxOrNbvWrW5Y9K+AgDpMaRl
Za6NaLOEx7dDcf/jGMxnSbUAAAAAAAA=
--------------ms000705040308020105000900--

From yang.r.yang@gmail.com  Mon Jul  9 07:52:09 2012
Return-Path: <yang.r.yang@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 0FCEC21F84B3 for <alto@ietfa.amsl.com>; Mon,  9 Jul 2012 07:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.777
X-Spam-Level: 
X-Spam-Status: No, score=-2.777 tagged_above=-999 required=5 tests=[AWL=0.199,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 8pBnaD5BdIPD for <alto@ietfa.amsl.com>; Mon,  9 Jul 2012 07:52:08 -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 4E07411E8098 for <alto@ietf.org>; Mon,  9 Jul 2012 07:52:08 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so696007obb.31 for <alto@ietf.org>; Mon, 09 Jul 2012 07:52:31 -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:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=AK3aAtev0MYVa6t0wUdzcEmItqOzPFgzqnYM+4dvNJQ=; b=Jw1XAqUTS3UXnz7L5Vj+WCUSvKIM2AKEdvqU+JLH5/F64dVd/xnpmENG2+46NTleN+ 6P/rHVaf9VeWfDiya85jAQGAobDBj16+914Jxoo/nHSShNmJp/WsjM9KTMNQ4kFOo8ky iPHUnasFeDpMl+ZpGKJlD7EbTL6c+x1q89/XWSUL/H625BkEdvgQaaXvuvYMReu7jHUa fF4tzqs5dUtbTIXOx3YfAlNWdWa4l55LJZNZoYhq+byT3s0/WTW09syupoxBltyRjvOT WcyqzGhXyWgno8pJ+7J6pjDxwTgy8BbWn6bW5m+IQLpN5bQbF1ktBe+6kLngJP0nSA/e rPYA==
MIME-Version: 1.0
Received: by 10.182.146.84 with SMTP id ta20mr36462644obb.19.1341845551380; Mon, 09 Jul 2012 07:52:31 -0700 (PDT)
Sender: yang.r.yang@gmail.com
Received: by 10.76.86.136 with HTTP; Mon, 9 Jul 2012 07:52:31 -0700 (PDT)
In-Reply-To: <CA+cvDaZaZ3uxUYvz0x9KJGLUXhu=K2qfQV36Bqc0m3ZveEqFNQ@mail.gmail.com>
References: <4F8BE443.9050903@telecomitalia.it> <4FAD5745.2060009@alcatel-lucent.com> <CA+cvDab3P0-68m6+mZ+4K0FedJ7_MK6SGXhD2kQKupXuCDLgDw@mail.gmail.com> <CA+cvDaZJ-RdJKf9mSTP0qbz3vS1mK28XQYpzpfQ69EZbMCF_5A@mail.gmail.com> <20120702154359.GV5342@gw01.ehlo.wurstkaes.de> <CA+cvDaYdzoGub0gvwbV2EfvCTmnS73Q5gSf+pvDH-sCsRjtPQg@mail.gmail.com> <20120702202219.GX5342@gw01.ehlo.wurstkaes.de> <CANUuoLqpJTQy6WbHjiX75YJmLEDV+yg1E_8-GX1okHOoH0CJdg@mail.gmail.com> <CA+cvDaZaZ3uxUYvz0x9KJGLUXhu=K2qfQV36Bqc0m3ZveEqFNQ@mail.gmail.com>
Date: Mon, 9 Jul 2012 22:52:31 +0800
X-Google-Sender-Auth: f_6__jJQIBt6l7hP-TZvhscKjto
Message-ID: <CANUuoLoUyry9OyKnfzTa-3MRazJc8DMuHcqxdEvVgpt6eN4x0g@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: Richard Alimi <rich@velvetsea.net>
Content-Type: multipart/alternative; boundary=f46d0444ed0b6ef7e704c466c384
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, 09 Jul 2012 14:52:09 -0000

--f46d0444ed0b6ef7e704c466c384
Content-Type: text/plain; charset=ISO-8859-1

On Monday, July 9, 2012, Richard Alimi wrote:

>
>
> Thank you Sebastian and Richard for the suggestions.  How about the
> following paragraph added to Section 5 just after paragraph 2:
>
>   Each application may independently determine how the Resource Consumer
>   and Resource Provider are designated as the source or destination, and
> hence
>   how to utilize the Path Cost provided by ALTO.  For example,
>   if the cost is expected to be correlated with throughput, a typical
>   application concerned with bulk data retrieval may use the Resource
> Provider
>   as the source, and Resource Consumer as the destination.
>
>
Looks good to me.

Thanks!

Richard


> Thanks,
> Rich
>
> >
> > -yry
> >
> >>
> >>   S.
> >> _______________________________________________
> >> alto mailing list
> >> alto@ietf.org <javascript:;>
> >> https://www.ietf.org/mailman/listinfo/alto
>

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

<br><br>On Monday, July 9, 2012, Richard Alimi  wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><br>
<br>
Thank you Sebastian and Richard for the suggestions. =A0How about the<br>
following paragraph added to Section 5 just after paragraph 2:<br>
<br>
=A0 Each application may independently determine how the Resource Consumer<=
br>
=A0 and Resource Provider are designated as the source or destination, and =
hence<br>
=A0 how to utilize the Path Cost provided by ALTO. =A0For example,<br>
=A0 if the cost is expected to be correlated with throughput, a typical<br>
=A0 application concerned with bulk data retrieval may use the Resource Pro=
vider<br>
=A0 as the source, and Resource Consumer as the destination.<br>
<br></blockquote><div><br></div><div>Looks good to me.</div><div><br></div>=
<div>Thanks!<span></span></div><div><br></div><div>Richard</div><div>=A0</d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">

Thanks,<br>
Rich<br>
<br>
&gt;<br>
&gt; -yry<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; =A0 S.<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; alto mailing list<br>
&gt;&gt; <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39=
;alto@ietf.org&#39;)">alto@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/alto</a><br>
</blockquote>

--f46d0444ed0b6ef7e704c466c384--

From leeyoung@huawei.com  Mon Jul  9 09:11:19 2012
Return-Path: <leeyoung@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 013B121F85E1; Mon,  9 Jul 2012 09:11:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.569
X-Spam-Level: 
X-Spam-Status: No, score=-6.569 tagged_above=-999 required=5 tests=[AWL=0.030,  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 shOWCJwvddxL; Mon,  9 Jul 2012 09:11:18 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 3C01121F85CD; Mon,  9 Jul 2012 09:11:18 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHP29111; Mon, 09 Jul 2012 12:11:43 -0400 (EDT)
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 9 Jul 2012 09:10:25 -0700
Received: from dfweml511-mbx.china.huawei.com ([169.254.16.20]) by dfweml405-hub.china.huawei.com ([10.193.5.102]) with mapi id 14.01.0323.003; Mon, 9 Jul 2012 09:10:07 -0700
From: Leeyoung <leeyoung@huawei.com>
To: "altoext@ietf.org" <altoext@ietf.org>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: New Version Notification for draft-lee-alto-app-net-info-exchange-00.txt
Thread-Index: AQHNXezKiq06aNW+qEK628+HsIpQSZchHgHw
Date: Mon, 9 Jul 2012 16:10:06 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E1720CC2D35@dfweml511-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.151]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [alto] FW: New Version Notification for	draft-lee-alto-app-net-info-exchange-00.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, 09 Jul 2012 16:11:19 -0000

SGkgQWxsLA0KDQpXZSBoYXZlIGp1c3QgcHVibGlzaGVkIEFMVE8gZXh0ZW5zaW9uIHRvIHN1cHBv
cnQgYXBwbGljYXRpb24gYW5kIG5ldHdvcmsgcmVzb3VyY2UgaW5mb3JtYXRpb24gZXhjaGFuZ2Ug
Zm9yIGhpZ2ggYmFuZHdpZHRoIGFwcGxpY2F0aW9ucy4NClRoaXMgaXMgcGFydCBvZiB0aGUgaTJh
ZXggaW5pdGlhdGl2ZS4gDQoNClRoYW5rcyBpbiBhZHZhbmNlIGZvciB5b3VyIGNvbW1lbnQgYW5k
IGRpc2N1c3Npb24uIA0KDQpZb3VuZw0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJv
bTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYu
b3JnXSANClNlbnQ6IE1vbmRheSwgSnVseSAwOSwgMjAxMiAxMTowNiBBTQ0KVG86IExlZXlvdW5n
DQpDYzogY2hvaXRzQGV0cmkucmUua3I7IFNyZWVrYW50aCBtYWRoYXZhbjsgZ3JlZ2JAZ3JvdHRv
LW5ldHdvcmtpbmcuY29tOyBEaHJ1diBEaG9keQ0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZp
Y2F0aW9uIGZvciBkcmFmdC1sZWUtYWx0by1hcHAtbmV0LWluZm8tZXhjaGFuZ2UtMDAudHh0DQoN
Cg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWxlZS1hbHRvLWFwcC1uZXQtaW5mby1leGNo
YW5nZS0wMC50eHQNCmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgWW91bmcgTGVl
IGFuZCBwb3N0ZWQgdG8gdGhlDQpJRVRGIHJlcG9zaXRvcnkuDQoNCkZpbGVuYW1lOgkgZHJhZnQt
bGVlLWFsdG8tYXBwLW5ldC1pbmZvLWV4Y2hhbmdlDQpSZXZpc2lvbjoJIDAwDQpUaXRsZToJCSBB
TFRPIEV4dGVuc2lvbnMgdG8gU3VwcG9ydCBBcHBsaWNhdGlvbiBhbmQgTmV0d29yayBSZXNvdXJj
ZSBJbmZvcm1hdGlvbiBFeGNoYW5nZSBmb3IgSGlnaCBCYW5kd2lkdGggQXBwbGljYXRpb25zDQpD
cmVhdGlvbiBkYXRlOgkgMjAxMi0wNy0wOQ0KV0cgSUQ6CQkgSW5kaXZpZHVhbCBTdWJtaXNzaW9u
DQpOdW1iZXIgb2YgcGFnZXM6IDE0DQpVUkw6ICAgICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5v
cmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWxlZS1hbHRvLWFwcC1uZXQtaW5mby1leGNoYW5nZS0w
MC50eHQNClN0YXR1czogICAgICAgICAgaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9k
cmFmdC1sZWUtYWx0by1hcHAtbmV0LWluZm8tZXhjaGFuZ2UNCkh0bWxpemVkOiAgICAgICAgaHR0
cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtbGVlLWFsdG8tYXBwLW5ldC1pbmZvLWV4Y2hh
bmdlLTAwDQoNCg0KQWJzdHJhY3Q6DQpUaGlzIGRyYWZ0IHByb3Bvc2VzIEFMVE8gaW5mb3JtYXRp
b24gbW9kZWwgYW5kIHByb3RvY29sIGV4dGVuc2lvbnMgdG8NCnN1cHBvcnQgYXBwbGljYXRpb24g
YW5kIG5ldHdvcmsgcmVzb3VyY2UgaW5mb3JtYXRpb24gZXhjaGFuZ2UgZm9yIGhpZ2gNCmJhbmR3
aWR0aCBhcHBsaWNhdGlvbnMgaW4gcGFydGlhbGx5IGNvbnRyb2xsZWQgYW5kIGNvbnRyb2xsZWQN
CmVudmlyb25tZW50cyBhcyBwYXJ0IG9mIHRoZSBpbmZyYXN0cnVjdHVyZSB0byBhcHBsaWNhdGlv
biBpbmZvcm1hdGlvbg0KZXhwb3N1cmUgKGkyYWV4KSBpbml0aWF0aXZlLg0KDQoNCg0KICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIA0KDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0DQo=

From diego@tid.es  Mon Jul  9 09:21:10 2012
Return-Path: <diego@tid.es>
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 41FB511E80FA for <alto@ietfa.amsl.com>; Mon,  9 Jul 2012 09:21:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.822
X-Spam-Level: 
X-Spam-Status: No, score=-4.822 tagged_above=-999 required=5 tests=[AWL=-0.637, BAYES_40=-0.185, 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 4wxNZDuDfNrG for <alto@ietfa.amsl.com>; Mon,  9 Jul 2012 09:21:09 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id F0BCC11E80FC for <alto@ietf.org>; Mon,  9 Jul 2012 09:21:08 -0700 (PDT)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M6W000UTIRXSM@tid.hi.inet> for alto@ietf.org; Mon, 09 Jul 2012 18:21:33 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id C6.71.02752.C050BFF4; Mon, 09 Jul 2012 18:21:33 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0M6W000UOIRWSM@tid.hi.inet> for alto@ietf.org; Mon, 09 Jul 2012 18:21:32 +0200 (MEST)
Received: from EX10-MB1-MAD.hi.inet ([fe80::a473:4f3e:f8db:1855]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0298.004; Mon, 09 Jul 2012 18:21:32 +0200
Date: Mon, 09 Jul 2012 16:21:31 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <4FFA8D33.6060706@telecomitalia.it>
X-Originating-IP: [10.95.64.115]
To: Enrico Marocco <enrico.marocco@telecomitalia.it>
Message-id: <09CCA18B-5B48-4429-B1B3-E017D9A9EBB1@tid.es>
Content-id: <2385E34EF981C54A9946748A772BEF67@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US, es-ES
Thread-topic: [alto] Agenda requests for IETF 84
Thread-index: AQHNXaeA8C10GLshPEak4Kb4l3NpqpchAPaA
X-AuditID: 0a5f4e69-b7f6d6d000000ac0-27-4ffb050c2959
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrNKsWRmVeSWpSXmKPExsXCFe9nqMvL+tvfYPEeJouH2/eyOjB6LFny kymAMYrLJiU1J7MstUjfLoEr48nZVawF9zgrts2+zNzA+IG9i5GTQ0LARKL/xj8mCFtM4sK9 9WxdjFwcQgLbGSX+HrnPCuH8YJSY96INKrOUUWL5981gLSwCqhL3t11nBrHZgOxHzb+BxrJz CAvoS2xPBIlyChhIdLcuYoNYoCDx59xjli5GDg4RoMVd51VBwswCyhLnVtxkBbF5BSwlVi38 zQIRN5M48PM6O0RcUOLH5HtQcR2J3u/fmCFscYnm1ptQcW2JJ+8ugM1hFJCVeDd/PpgtAnTC 2aaZULaRxPo/V6F+F5BYsuc8M4QtKvHy8T+wGiGg45tXbmKfwCgxC8kZs5CcMQvJGbOQnDEL yRkLGFlXMYoVJxVlpmeU5CZm5qQbGOllZOpl5qWWbGKExFzmDsblO1UOMQpwMCrx8EpM++Qv xJpYVlyZe4hRkoNJSZT3IuNvfyG+pPyUyozE4oz4otKc1OJDjBIczEoivIu+/vIX4k1JrKxK LcqHSclwcChJ8P5gBmoTLEpNT61Iy8wBJhaYNBMHJ0g7D1B7K0gNb3FBYm5xZjpE/hSjpJQ4 73uQhABIIqM0D673FaM40JHCvAIsQFkeYAqE63oFNJAJaGB7D8g9xSWJCCmpBsapE6yzpuqx Lzz5pzqWU+gKo9ypF0q5DcLx84LYpbbUWfdGbAqwP6V11tZ15eW1P49osR4UUdxjpHf28vO3 vEunT+Rouu74vUjknaiHViHXvPotIkbnBGo/FD6qM1ryfeoSYT0eCyGNvBf7vtQfOLQxMz1q svnhc+Y1ncGLjFx1Etw9Ml/MT1RiKc5INNRiLipOBACmakDkPgMAAA==
References: <4FFA8D33.6060706@telecomitalia.it>
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Agenda requests for IETF 84
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, 09 Jul 2012 16:21:10 -0000

Hi Enrico,

On 9 Jul 2012, at 09:50 , Enrico Marocco wrote:
> if you have any requests for agenda slots at the next IETF meeting,
> please send them to Vijay and me by Tuesday, July 17. As usual, priority
> will be given to charter items, and to topics that have been already
> presented and discussed on the list.
>
> In order to lower the loss probability, please send your request even if
> you have already sent it before this call went out.


This is a re-sending ot the request for a slot to introduce this draft:

http://datatracker.ietf.org/doc/draft-xie-alto-sdn-use-cases/

Be goode,

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: diego@tid.es
Tel:    +34 913 129 041
Mobile: +34 682 051 091
-----------------------------------------


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

From iesg-secretary@ietf.org  Mon Jul  9 09:36:12 2012
Return-Path: <iesg-secretary@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 A7B2621F84A5; Mon,  9 Jul 2012 09:36:12 -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 XMXO6bALiqSN; Mon,  9 Jul 2012 09:36:12 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D95C911E809C; Mon,  9 Jul 2012 09:36:11 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.30p3
Message-ID: <20120709163611.29783.42041.idtracker@ietfa.amsl.com>
Date: Mon, 09 Jul 2012 09:36:11 -0700
Cc: alto mailing list <alto@ietf.org>, alto chair <alto-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [alto] Document Action: 'Application-Layer Traffic Optimization (ALTO)	Requirements' to Informational RFC (draft-ietf-alto-reqs-16.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, 09 Jul 2012 16:36:12 -0000

The IESG has approved the following document:
- 'Application-Layer Traffic Optimization (ALTO) Requirements'
  (draft-ietf-alto-reqs-16.txt) as Informational RFC

This document is the product of the Application-Layer Traffic
Optimization Working Group.

The IESG contact persons are Wesley Eddy and Martin Stiemerling.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-alto-reqs/




Technical Summary

This is a procedural document, listing requirements for the protocol
the ALTO WG is chartered to standardize. The abstract of the draft
provides an accurate summary:

Many Internet applications are used to access resources, such as
pieces of information or server processes, which 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, which have to select one or several hosts
from a set of candidates, that are able to provide 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 resource consumption in the underlying network
infrastructure.

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

Working Group Summary

The document has had reviews by key WG members, as well as by members
of WGs that are considering the work of the alto WG as the basis for
their standardization work (esp. decade and cdni WGs). It has been
intetionally kept alive, refined and reviewed in several iterations,
for quite a long time to track new requirements during the early phase
of the specification work. Since the specs are now generally
considered mature, the WG has expressed strong consensus to move it toward
publication.

Document Quality

The document has received extended review by WG members, as well as by
contributors of other WGs (esp. DECADE and CDNI) that are considering
the ALTO protocol as the basis for their specification work. 

Personnel

   Document Shepherd: Enrico Marocco
   Responsible Area Director: Wesley Eddy




From haibin.song@huawei.com  Tue Jul 10 02:27:16 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 9F2DF21F8601 for <alto@ietfa.amsl.com>; Tue, 10 Jul 2012 02:27:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.279
X-Spam-Level: 
X-Spam-Status: No, score=-6.279 tagged_above=-999 required=5 tests=[AWL=0.320,  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 RZ9B15sU8irt for <alto@ietfa.amsl.com>; Tue, 10 Jul 2012 02:27:16 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id CE53921F85FD for <alto@ietf.org>; Tue, 10 Jul 2012 02:27:15 -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 AHP92175; Tue, 10 Jul 2012 05:27:43 -0400 (EDT)
Received: from DFWEML403-HUB.china.huawei.com (10.193.5.151) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 10 Jul 2012 02:25:10 -0700
Received: from SZXEML407-HUB.china.huawei.com (10.82.67.94) by dfweml403-hub.china.huawei.com (10.193.5.151) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 10 Jul 2012 02:25:09 -0700
Received: from SZXEML534-MBX.china.huawei.com ([169.254.2.243]) by szxeml407-hub.china.huawei.com ([10.82.67.94]) with mapi id 14.01.0323.003; Tue, 10 Jul 2012 17:25:01 +0800
From: Songhaibin <haibin.song@huawei.com>
To: Sebastian Kiesel <ietf-alto@skiesel.de>
Thread-Topic: [alto] ALTO discovery in roaming scenario
Thread-Index: Ac0Fw01LNWVAmHe9T920S4QOtl0VRwG9ShOAADD7c2X//8qrgIAAjJtG/4DH49D+/mR/0P37yYCw+/c7DDD34dq8AO/DUJpA34XcZvC/CyywAP4GwybA
Date: Tue, 10 Jul 2012 09:25:00 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F23AED0FF@szxeml534-mbx.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F1586EC4E@szxeml534-mbx.china.huawei.com> <CA+cvDaYGgupkhMcTGsZvH=0RHBm3BB-G4VPA1PJKZFN9bNLm8A@mail.gmail.com> <E33E01DFD5BEA24B9F3F18671078951F1586EE0E@szxeml534-mbx.china.huawei.com> <E33E01DFD5BEA24B9F3F18671078951F23AAAEAE@szxeml534-mbx.china.huawei.com> <2A886F9088894347A3BE0CC5B7A85F3E891A9BB692@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E33E01DFD5BEA24B9F3F18671078951F23AB4448@szxeml534-mbx.china.huawei.com> <2A886F9088894347A3BE0CC5B7A85F3E891A9BB6B2@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E33E01DFD5BEA24B9F3F18671078951F23AB998C@szxeml534-mbx.china.huawei.com> <2A886F9088894347A3BE0CC5B7A85F3E891A9BB830@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E33E01DFD5BEA24B9F3F18671078951F23AC8D73@szxeml534-mbs.china.huawei.com> <20120630184923.GS5342@gw01.ehlo.wurstkaes.de>
In-Reply-To: <20120630184923.GS5342@gw01.ehlo.wurstkaes.de>
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] ALTO discovery in roaming scenario
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, 10 Jul 2012 09:27:16 -0000

Sebastian and all,

I'm late for answering your questions.

I would answer "yes" to the first two questions you raised.=20

For the third question, I think the discovery document is not going to stan=
dardize the way for ALTO server discovery, it is only standardize the servi=
ce tag for one discovery option using U-NAPTR. There are variable discovery=
 methods available. So there is no one standard way. Or could you specify o=
ne standard way that every application should obey to achieve interoperabil=
ity?

> If you use triangular routing it might make sense to use the
> care-of-address instead of the home address. But this may depend on many
> things, e.g., are you mostly sending data or mostly receiving data?
> So it may also be wise not to do that ...
>=20

This is a good question. It should use one ALTO server when it receives dat=
a and another ALTO server while it sends data. Should one end-host be tied =
with only one ALTO server?

It is easy to generalize the mobile and proxy based scenarios I raised, or =
even generalize the whole document into only one short paragraph such like =
"find the resource consumer's domain name, then use the U-NAPTR method with=
 the new defined service tag...", if we do not go to the details.=20

BR,
-Haibin


> -----Original Message-----
> From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of
> Sebastian Kiesel
> Sent: Sunday, July 01, 2012 2:49 AM
> To: Songhaibin
> Cc: alto@ietf.org
> Subject: Re: [alto] ALTO discovery in roaming scenario
>=20
> Haibin, all,
>=20
> On Sat, Jun 30, 2012 at 02:35:06AM +0000, Songhaibin wrote:
> > I'm very glad that you understand my proposal. If the text missed some
> > technical details of ALTO discovery in mobile IPv4 and mobile IPv6, I
> > think we can clarify them in the draft. But I cannot agree that we do
> > not need text about the right IP address selection (in mobility and
> > proxy based scenarios) in the document.
> >
> > What do other people think on this issue?
>=20
> I like Michael's proposal ...
>=20
> > > "In general, the ALTO server discovery should be based on the IP
> > > address that is used to communicate with other peers".
>=20
> ... because it is short and generic. I think it is better to give
> general guidelines (if possible) instead of going into the details
> of various mobility mechanisms.
>=20
>=20
> I think Michael's proposal is perfect for all mobility, VPN and proxy
> architectures I can think of, except for one: Mobile IP with triangular
> routing.
>=20
> If you use triangular routing it might make sense to use the
> care-of-address instead of the home address. But this may depend on many
> things, e.g., are you mostly sending data or mostly receiving data?
> So it may also be wise not to do that ...
>=20
>=20
>=20
>=20
> May I ask you and the other folks here three questions:
>=20
>=20
> 1.) Is Mobile IP with triangular routing a relevant use case?
>     (Or is there another relevant mobility mechanism for which Michael's
>     proposal does not make sense?)
>=20
> 2.) Are we really sure that it is a good idea to optimize based
>     on the CoA (or deviate from Michael's proposal in some other way)?
>     E.g., are there simulation results or field trials showing
>     that much better results could be achived?
>=20
> 3.) Do we really need to standardize this, in order to guarantee
>     interoperability (we could leave the decision up to the
>     implementors, as long as we are sure that letting them choose does
>     not harm interoperability)?
>=20
>=20
> I think adding lots of text about mobility mechanisms in general and the
> triangular routing use case in particular makes only sense if a
> significant number of people answers three times "yes".
>=20
> Personally, I would answer three times with "no" ...
>=20
>=20
>=20
> Thanks
>    Sebastian
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto

From michael.scharf@alcatel-lucent.com  Tue Jul 10 04:33:16 2012
Return-Path: <michael.scharf@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 9197221F858E for <alto@ietfa.amsl.com>; Tue, 10 Jul 2012 04:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.963
X-Spam-Level: 
X-Spam-Status: No, score=-9.963 tagged_above=-999 required=5 tests=[AWL=0.286,  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 SpoDiE+SWojB for <alto@ietfa.amsl.com>; Tue, 10 Jul 2012 04:33:16 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id CDEE121F858D for <alto@ietf.org>; Tue, 10 Jul 2012 04:33:15 -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 q6ABXY3t015557 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 10 Jul 2012 13:33:35 +0200
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.55]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Tue, 10 Jul 2012 13:33:34 +0200
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Songhaibin <haibin.song@huawei.com>, Sebastian Kiesel <ietf-alto@skiesel.de>
Date: Tue, 10 Jul 2012 13:33:32 +0200
Thread-Topic: [alto] ALTO discovery in roaming scenario
Thread-Index: Ac0Fw01LNWVAmHe9T920S4QOtl0VRwG9ShOAADD7c2X//8qrgIAAjJtG/4DH49D+/mR/0P37yYCw+/c7DDD34dq8AO/DUJpA34XcZvC/CyywAP4GwybA/A1hScA=
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E891A9BB9FB@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
References: <E33E01DFD5BEA24B9F3F18671078951F1586EC4E@szxeml534-mbx.china.huawei.com> <CA+cvDaYGgupkhMcTGsZvH=0RHBm3BB-G4VPA1PJKZFN9bNLm8A@mail.gmail.com> <E33E01DFD5BEA24B9F3F18671078951F1586EE0E@szxeml534-mbx.china.huawei.com> <E33E01DFD5BEA24B9F3F18671078951F23AAAEAE@szxeml534-mbx.china.huawei.com> <2A886F9088894347A3BE0CC5B7A85F3E891A9BB692@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E33E01DFD5BEA24B9F3F18671078951F23AB4448@szxeml534-mbx.china.huawei.com> <2A886F9088894347A3BE0CC5B7A85F3E891A9BB6B2@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E33E01DFD5BEA24B9F3F18671078951F23AB998C@szxeml534-mbx.china.huawei.com> <2A886F9088894347A3BE0CC5B7A85F3E891A9BB830@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E33E01DFD5BEA24B9F3F18671078951F23AC8D73@szxeml534-mbs.china.huawei.com> <20120630184923.GS5342@gw01.ehlo.wurstkaes.de> <E33E01DFD5BEA24B9F3F18671078951F23AED0FF@szxeml534-mbx.china.huawei.com>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F23AED0FF@szxeml534-mbx.china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] ALTO discovery in roaming scenario
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, 10 Jul 2012 11:33:16 -0000

Haibin,=20

> I would answer "yes" to the first two questions you raised.=20

Well, I disagree with both, but I am willing to learn from real-world data.

> It is easy to generalize the mobile and proxy based scenarios=20
> I raised, or even generalize the whole document into only one=20
> short paragraph such like "find the resource consumer's=20
> domain name, then use the U-NAPTR method with the new defined=20
> service tag...", if we do not go to the details.=20

As I mentioned before, there is a quite a number of IETF protocols providin=
g mobility (in a somehow loose sense):

- Proxy Mobile IP
- Mobile IPv4 (MIPv4)
- Mobile IPv6 (MIPv6)
- Hierarchical Mobile IPv6 (HMIPv6)
- NEMO
- SHIM6
- HIP
- LISP (partly)
- ...

Do you argue that we have to go into technical details for all of them? Do =
you plan to write that text?

Or do you argue that MIPv4 (which your suggested text apparently assumes) i=
s the only relevant protocol that ALTO discovery has to consider in details=
?

Note that the current draft already has text on mobility and NAT, unlike fo=
r instance RFC 5986. I agree that in addition to NAT, proxies should be men=
tioned. And we should indeed highlight that
the IP address that is used for communication actually matters, in particul=
ar also in mobility scenarios.

But beyond that, I really wonder how you want to specify in detail how to d=
eal with the wide variety of mobility and proxy solutions known in the IETF=
. This could end up in an endless story.

Michael

From haibin.song@huawei.com  Tue Jul 10 23:07:58 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 4A14221F8555 for <alto@ietfa.amsl.com>; Tue, 10 Jul 2012 23:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.295
X-Spam-Level: 
X-Spam-Status: No, score=-6.295 tagged_above=-999 required=5 tests=[AWL=0.304,  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 HoiXwkkKys1Y for <alto@ietfa.amsl.com>; Tue, 10 Jul 2012 23:07:57 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2E1C821F8554 for <alto@ietf.org>; Tue, 10 Jul 2012 23:07:57 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AHQ63624; Wed, 11 Jul 2012 02:08:26 -0400 (EDT)
Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 10 Jul 2012 23:05:26 -0700
Received: from SZXEML422-HUB.china.huawei.com (10.82.67.161) by dfweml404-hub.china.huawei.com (10.193.5.203) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 10 Jul 2012 23:05:29 -0700
Received: from SZXEML534-MBX.china.huawei.com ([169.254.2.243]) by szxeml422-hub.china.huawei.com ([10.82.67.161]) with mapi id 14.01.0323.003; Wed, 11 Jul 2012 14:05:25 +0800
From: Songhaibin <haibin.song@huawei.com>
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>, Sebastian Kiesel <ietf-alto@skiesel.de>
Thread-Topic: [alto] ALTO discovery in roaming scenario
Thread-Index: Ac0Fw01LNWVAmHe9T920S4QOtl0VRwG9ShOAADD7c2X//8qrgIAAjJtG/4DH49D+/mR/0P37yYCw+/c7DDD34dq8AO/DUJpA34XcZvC/CyywAP4GwybA/A1hScD4GYfUkA==
Date: Wed, 11 Jul 2012 06:05:24 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F23AED708@szxeml534-mbx.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F1586EC4E@szxeml534-mbx.china.huawei.com> <CA+cvDaYGgupkhMcTGsZvH=0RHBm3BB-G4VPA1PJKZFN9bNLm8A@mail.gmail.com> <E33E01DFD5BEA24B9F3F18671078951F1586EE0E@szxeml534-mbx.china.huawei.com> <E33E01DFD5BEA24B9F3F18671078951F23AAAEAE@szxeml534-mbx.china.huawei.com> <2A886F9088894347A3BE0CC5B7A85F3E891A9BB692@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E33E01DFD5BEA24B9F3F18671078951F23AB4448@szxeml534-mbx.china.huawei.com> <2A886F9088894347A3BE0CC5B7A85F3E891A9BB6B2@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E33E01DFD5BEA24B9F3F18671078951F23AB998C@szxeml534-mbx.china.huawei.com> <2A886F9088894347A3BE0CC5B7A85F3E891A9BB830@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E33E01DFD5BEA24B9F3F18671078951F23AC8D73@szxeml534-mbs.china.huawei.com> <20120630184923.GS5342@gw01.ehlo.wurstkaes.de> <E33E01DFD5BEA24B9F3F18671078951F23AED0FF@szxeml534-mbx.china.huawei.com> <2A886F9088894347A3BE0CC5B7A85F3E891A9BB9FB@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
In-Reply-To: <2A886F9088894347A3BE0CC5B7A85F3E891A9BB9FB@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.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] ALTO discovery in roaming scenario
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, 11 Jul 2012 06:07:58 -0000

Michael,

> Note that the current draft already has text on mobility and NAT, unlike =
for
> instance RFC 5986. I agree that in addition to NAT, proxies should be men=
tioned.
> And we should indeed highlight that
> the IP address that is used for communication actually matters, in partic=
ular also
> in mobility scenarios.
>=20
> But beyond that, I really wonder how you want to specify in detail how to=
 deal
> with the wide variety of mobility and proxy solutions known in the IETF. =
This
> could end up in an endless story.

OK. Then how about using your and Sebastian's suggested general statement a=
bout using the client's communication IP address, and highlight proxy based=
 with one or two sentences?

I'm not convinced that we should ignore the scenarios when the above senten=
ces cannot work. Maybe we can give guidance in the document, that there cou=
ld be exceptions and using the text about triangle routing from my original=
 email as an example. Then we do not go to every exceptions in mobility. I'=
m not familiar with all the mobility technologies, but some will not impact=
 ALTO discovery such as HIP which is a 3.5 layer technology.  Does that mak=
e sense and look like a simple way to handle it in the draft?

I can help to modify the draft if we can achieve a consensus here.

BR,
-Haibin

> -----Original Message-----
> From: Scharf, Michael (Michael) [mailto:michael.scharf@alcatel-lucent.com=
]
> Sent: Tuesday, July 10, 2012 7:34 PM
> To: Songhaibin; Sebastian Kiesel
> Cc: alto@ietf.org
> Subject: RE: [alto] ALTO discovery in roaming scenario
>=20
> Haibin,
>=20
> > I would answer "yes" to the first two questions you raised.
>=20
> Well, I disagree with both, but I am willing to learn from real-world dat=
a.
>=20
> > It is easy to generalize the mobile and proxy based scenarios
> > I raised, or even generalize the whole document into only one
> > short paragraph such like "find the resource consumer's
> > domain name, then use the U-NAPTR method with the new defined
> > service tag...", if we do not go to the details.
>=20
> As I mentioned before, there is a quite a number of IETF protocols provid=
ing
> mobility (in a somehow loose sense):
>=20
> - Proxy Mobile IP
> - Mobile IPv4 (MIPv4)
> - Mobile IPv6 (MIPv6)
> - Hierarchical Mobile IPv6 (HMIPv6)
> - NEMO
> - SHIM6
> - HIP
> - LISP (partly)
> - ...
>=20
> Do you argue that we have to go into technical details for all of them? D=
o you
> plan to write that text?
>=20
> Or do you argue that MIPv4 (which your suggested text apparently assumes)=
 is
> the only relevant protocol that ALTO discovery has to consider in details=
?
>=20
> Note that the current draft already has text on mobility and NAT, unlike =
for
> instance RFC 5986. I agree that in addition to NAT, proxies should be men=
tioned.
> And we should indeed highlight that
> the IP address that is used for communication actually matters, in partic=
ular also
> in mobility scenarios.
>=20
> But beyond that, I really wonder how you want to specify in detail how to=
 deal
> with the wide variety of mobility and proxy solutions known in the IETF. =
This
> could end up in an endless story.
>=20
> Michael

From internet-drafts@ietf.org  Wed Jul 11 10:16:08 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 BA96A11E8112; Wed, 11 Jul 2012 10:16:08 -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=[AWL=0.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 uGgzYofY+2PN; Wed, 11 Jul 2012 10:16:08 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1046B21F852D; Wed, 11 Jul 2012 10:16:08 -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.30p3
Message-ID: <20120711171608.16399.10488.idtracker@ietfa.amsl.com>
Date: Wed, 11 Jul 2012 10:16:08 -0700
Cc: alto@ietf.org
Subject: [alto] I-D Action: draft-ietf-alto-protocol-12.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, 11 Jul 2012 17:16:09 -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 Optimization Wo=
rking Group of the IETF.

	Title           : ALTO Protocol
	Author(s)       : Richard Alimi
                          Reinaldo Penno
                          Y. Richard Yang
	Filename        : draft-ietf-alto-protocol-12.txt
	Pages           : 72
	Date            : 2012-07-11

Abstract:
   Networking applications today already have access to a great amount
   of Inter-Provider network topology information.  For example, views
   of the Internet routing table are easily available at looking glass
   servers and entirely practical to be downloaded by clients.  What is
   missing is knowledge of the underlying network topology from the ISP
   or Content Provider (henceforth referred as Provider) point of view.
   In other words, what a Provider prefers in terms of traffic
   optimization -- and a way to distribute it.

   The ALTO Service provides network information (e.g., basic network
   location structure, preferences of network paths) with the goal of
   modifying network resource consumption patterns while maintaining or
   improving application performance.  The basic information of ALTO is
   based on abstract maps of a network.  These maps provide a simplified
   view, yet enough information about a network for applications to
   effectively utilize them.  Additional services are built on top the
   maps.

   This document describes a protocol implementing the ALTO Service.
   Although the ALTO service would primarily be provided by the network
   operator (e.g., an ISP), content providers and third parties could
   also operate this service.  Applications that could use this service
   are those that have a choice in connection endpoints.  Examples of
   such applications are peer-to-peer (P2P) and content delivery
   networks.



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

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-alto-protocol-12

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-alto-protocol-12


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


From richard.alimi@gmail.com  Wed Jul 11 10:26:42 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 1948211E8101 for <alto@ietfa.amsl.com>; Wed, 11 Jul 2012 10:26:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level: 
X-Spam-Status: No, score=-2.722 tagged_above=-999 required=5 tests=[AWL=0.255,  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 W1+5R6TUTz+6 for <alto@ietfa.amsl.com>; Wed, 11 Jul 2012 10:26:41 -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 4A02711E80E8 for <alto@ietf.org>; Wed, 11 Jul 2012 10:26:41 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so995771vbb.31 for <alto@ietf.org>; Wed, 11 Jul 2012 10:27:12 -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; bh=UrhSYuPbnTPd63KtJBBSGk1L/zW1Je93195aQ0/6F/E=; b=YVBVYj6aXJKIGyqplKNPqxKveqknu/ujF2h6J62NKADtznes4qVBsNm7jQfsmdlBJb Ce/UPf7zRuWPrbM+Uiw6UBQ+mLkPF1iypIHw7BRxQuoYtAcDnLWSB2vpwy1UDZcMBlSC eCx2QIKaQQSReVEYItfbK3NsPx3ZvoOUj8RhbGdW3RyjrAKOznr+4fEkvH0CbsbZYs0i +vPMbFhyb6m7QHQDFR4ZVvGlYQ1N/mW+8RLI7VQiKtfJGidjf+18j2/h5KQq2aiZ0BTo 9rThazwe0DulVK/DZ1kfV16u+HWEjRA4HrxfTaTOxfpbhVIqLajxB18MHgeeMOJrIa80 Tp+A==
Received: by 10.52.155.193 with SMTP id vy1mr19852980vdb.123.1342027632012; Wed, 11 Jul 2012 10:27:12 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.58.161.240 with HTTP; Wed, 11 Jul 2012 10:26:51 -0700 (PDT)
In-Reply-To: <20120711171608.16399.10488.idtracker@ietfa.amsl.com>
References: <20120711171608.16399.10488.idtracker@ietfa.amsl.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Wed, 11 Jul 2012 10:26:51 -0700
X-Google-Sender-Auth: k8VtYSuJDcOgqQYfkfgY8AlyUVs
Message-ID: <CA+cvDabW17VfVF4w+u0FkvFAF9v0zuzPw1DOP+proBouOCKzJg@mail.gmail.com>
To: alto@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [alto] I-D Action: draft-ietf-alto-protocol-12.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, 11 Jul 2012 17:26:42 -0000

I believe this should address all of the WGLC comments received, with
the exception of handling the operations and management requirements.
Those are underway; I posted a new version now to give folks more time
to ensure that the WGLC comments were addressed appropriately.

Thanks,
Rich

On Wed, Jul 11, 2012 at 10:16 AM,  <internet-drafts@ietf.org> wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the Application-Layer Traffic Optimization Working Group of the IETF.
>
>         Title           : ALTO Protocol
>         Author(s)       : Richard Alimi
>                           Reinaldo Penno
>                           Y. Richard Yang
>         Filename        : draft-ietf-alto-protocol-12.txt
>         Pages           : 72
>         Date            : 2012-07-11
>
> Abstract:
>    Networking applications today already have access to a great amount
>    of Inter-Provider network topology information.  For example, views
>    of the Internet routing table are easily available at looking glass
>    servers and entirely practical to be downloaded by clients.  What is
>    missing is knowledge of the underlying network topology from the ISP
>    or Content Provider (henceforth referred as Provider) point of view.
>    In other words, what a Provider prefers in terms of traffic
>    optimization -- and a way to distribute it.
>
>    The ALTO Service provides network information (e.g., basic network
>    location structure, preferences of network paths) with the goal of
>    modifying network resource consumption patterns while maintaining or
>    improving application performance.  The basic information of ALTO is
>    based on abstract maps of a network.  These maps provide a simplified
>    view, yet enough information about a network for applications to
>    effectively utilize them.  Additional services are built on top the
>    maps.
>
>    This document describes a protocol implementing the ALTO Service.
>    Although the ALTO service would primarily be provided by the network
>    operator (e.g., an ISP), content providers and third parties could
>    also operate this service.  Applications that could use this service
>    are those that have a choice in connection endpoints.  Examples of
>    such applications are peer-to-peer (P2P) and content delivery
>    networks.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-alto-protocol
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-alto-protocol-12
>
> A diff from previous version is available at:
> http://tools.ietf.org/rfcdiff?url2=draft-ietf-alto-protocol-12
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto

From michael.scharf@alcatel-lucent.com  Wed Jul 11 13:00:40 2012
Return-Path: <michael.scharf@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 C027F11E80A2 for <alto@ietfa.amsl.com>; Wed, 11 Jul 2012 13:00:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level: 
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[AWL=0.250,  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 rPuSZ4JKc0Yu for <alto@ietfa.amsl.com>; Wed, 11 Jul 2012 13:00:40 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id E143D11E808E for <alto@ietf.org>; Wed, 11 Jul 2012 13:00:39 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q6BK12GM028349 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 11 Jul 2012 22:01:02 +0200
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.55]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Wed, 11 Jul 2012 22:01:01 +0200
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Songhaibin <haibin.song@huawei.com>, Sebastian Kiesel <ietf-alto@skiesel.de>
Date: Wed, 11 Jul 2012 22:01:01 +0200
Thread-Topic: [alto] ALTO discovery in roaming scenario
Thread-Index: Ac0Fw01LNWVAmHe9T920S4QOtl0VRwG9ShOAADD7c2X//8qrgIAAjJtG/4DH49D+/mR/0P37yYCw+/c7DDD34dq8AO/DUJpA34XcZvC/CyywAP4GwybA/A1hScD4GYfUkPAyJghw
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E891A9BBA57@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
References: <E33E01DFD5BEA24B9F3F18671078951F1586EC4E@szxeml534-mbx.china.huawei.com> <CA+cvDaYGgupkhMcTGsZvH=0RHBm3BB-G4VPA1PJKZFN9bNLm8A@mail.gmail.com> <E33E01DFD5BEA24B9F3F18671078951F1586EE0E@szxeml534-mbx.china.huawei.com> <E33E01DFD5BEA24B9F3F18671078951F23AAAEAE@szxeml534-mbx.china.huawei.com> <2A886F9088894347A3BE0CC5B7A85F3E891A9BB692@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E33E01DFD5BEA24B9F3F18671078951F23AB4448@szxeml534-mbx.china.huawei.com> <2A886F9088894347A3BE0CC5B7A85F3E891A9BB6B2@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E33E01DFD5BEA24B9F3F18671078951F23AB998C@szxeml534-mbx.china.huawei.com> <2A886F9088894347A3BE0CC5B7A85F3E891A9BB830@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E33E01DFD5BEA24B9F3F18671078951F23AC8D73@szxeml534-mbs.china.huawei.com> <20120630184923.GS5342@gw01.ehlo.wurstkaes.de> <E33E01DFD5BEA24B9F3F18671078951F23AED0FF@szxeml534-mbx.china.huawei.com> <2A886F9088894347A3BE0CC5B7A85F3E891A9BB9FB@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <E33E01DFD5BEA24B9F3F18671078951F23AED708@szxeml534-mbx.china.huawei.com>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F23AED708@szxeml534-mbx.china.huawei.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] ALTO discovery in roaming scenario
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, 11 Jul 2012 20:00:40 -0000

Haibin,

> OK. Then how about using your and Sebastian's suggested=20
> general statement about using the client's communication IP=20
> address, and highlight proxy based with one or two sentences?

This looks like a reasonable idea.=20

> I'm not convinced that we should ignore the scenarios when=20
> the above sentences cannot work. Maybe we can give guidance=20
> in the document, that there could be exceptions and using the=20
> text about triangle routing from my original email as an=20
> example. Then we do not go to every exceptions in mobility.=20
> I'm not familiar with all the mobility technologies, but some=20
> will not impact ALTO discovery such as HIP which is a 3.5=20
> layer technology.  Does that make sense and look like a=20
> simple way to handle it in the draft?

The draft has to be updated anyway, given the feedback in the last meeting.=
 Certainly, triangular routing can be mentioned as an example for a specifi=
c challenge.

As a side note: AFAIK, HIP decouples the application and the IP stack, i. e=
., the application may not easily know what IP address is actually used by =
the protocol stack (there may be work-arounds, of course). I guess that thi=
s could actually be a quite significant obstacle for ALTO if an app needs t=
he IP address to get ALTO guidance. Anyway, I think that this should be out=
-of-scope.

Michael

From vkg@bell-labs.com  Wed Jul 11 15:02: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 59BDC11E813D for <alto@ietfa.amsl.com>; Wed, 11 Jul 2012 15:02:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.599
X-Spam-Level: 
X-Spam-Status: No, score=-107.599 tagged_above=-999 required=5 tests=[AWL=-1.000, 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 afH-lqPO8LZW for <alto@ietfa.amsl.com>; Wed, 11 Jul 2012 15:02:48 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 414F111E80B6 for <alto@ietf.org>; Wed, 11 Jul 2012 15:02:48 -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 q6BM3Ijw006776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <alto@ietf.org>; Wed, 11 Jul 2012 17:03:19 -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 q6BM3Hak002111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Wed, 11 Jul 2012 17:03:18 -0500
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q6BM3H7W012459 for <alto@ietf.org>; Wed, 11 Jul 2012 17:03:17 -0500 (CDT)
Message-ID: <4FFDF98F.9030804@bell-labs.com>
Date: Wed, 11 Jul 2012 17:09:19 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
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.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Subject: [alto] NomCom 2012-13 call for volunteers
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, 11 Jul 2012 22:02:49 -0000

Folks: The NomCom call for volunteers is now open.
Please consider volunteering on it if you can.

Thanks,

---------- Forwarded message ----------
From: NomCom Chair <nomcom-chair@ietf.org>
Date: Fri, Jul 6, 2012 at 2:15 PM
Subject: NomCom 2012-13 Call for Volunteers
To: IETF Announcement List <ietf-announce@ietf.org>

The IETF nominating committee process for 2012-13 has begun. The IETF
nominating committee appoints folks to fill the open slots on the
IAOC, the IAB, and the IESG. The 10 nominating committee members are
selected randomly from a pool of volunteers. The more volunteers, the
better chance we have of choosing a random yet representative cross
section of the IETF population.  The details of the operation of the
nomcom can be found in RFC 3777.

To be eligible, volunteers for the nomcom need to have attended 3 of
the past 5 IETF meetings as of the time this announcement goes out.
That is, 3 meetings from IETF 79 (Beijing) - IETF 83 (Paris). If you
qualify, and if you will not be seeking appointment to any of the open
positions that this nomcom will be filling, please consider
volunteering.

The list of people whose terms end with the March 2013 IETF meeting,
and thus the positions for which the nominating committee is
responsible for filling, are as follows:

IAOC:
--------
Dave Crocker

IAB:
--------
Alissa Cooper
Joel Halpern
David Kessens
Danny McPherson
Jon Peterson
Dave Thaler

IESG:
--------
Russ Housley (General Area)
Pete Resnick (Applications Area)
Ralph Droms (Internet Area)
Ronald Bonica (Operations and Management Area)
Robert Sparks (Real-Time Applications and Infrastructure Area)
Adrian Farrel (Routing Area)
Stephen Farrell (Security Area)
Wesley Eddy (Transport Area)

The primary activity for this nomcom will begin in August 2012 and
should be completed in January 2013. The nomcom will be collecting
requirements from the community, as well as talking to candidates and
obtaining feedback from community members about candidates. There will
be regularly scheduled conference calls to ensure progress. Thus,
being a nomcom member does require some time commitment.

Please volunteer by sending an email before 11:59 pm EDT (UTC - 4
hours) August 5, 2012 as follows:

To: mlepinski.ietf@gmail.com
Subject: Nomcom 2012-13 Volunteer

Please include the following information in the body:

<Your Full Name>  // As you enter in the IETF Registration Form,
                     // First/Given name followed by Last/Family Name
<Current Primary Affiliation>
                 // typically what goes in the Company field
                 //  in the IETF Registration Form
[<all email addresses used to Register for the past 5 IETF meetings>]
<Preferred email address>  //
<Telephone number>         // For confirmation if selected

Please expect an email response from me within 3 business days stating
whether or not you are qualified.  If you don't receive a response,
please re-send your email with the tag "RESEND:" added to the subject
line.

If you are not yet sure you would like to volunteer, please consider
that nomcom members play a very important role in shaping the
leadership of the IETF.  Ensuring the leadership of the IETF is fair
and balanced and comprised of those who can lead the IETF in the right
direction is an important responsibility that rests on the IETF
participants at large. Volunteering for the nomcom is a good way of
contributing toward that goal.

I will be publishing a more detailed timetable for nomcom activities,
as well as details of the randomness seeds to be used for the RFC 3797
selection process, within the next couple weeks.

Thank you,
Matthew Lepinski
mlepinski.ietf@gmail.com
nomcom-chair@ietf.org

---- End of forwarded message ------

- 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 Martin.Stiemerling@neclab.eu  Thu Jul 12 13:07:48 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 C6FDE21F8732; Thu, 12 Jul 2012 13:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.481
X-Spam-Level: 
X-Spam-Status: No, score=-102.481 tagged_above=-999 required=5 tests=[AWL=0.118, 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 pzVdREojYctf; Thu, 12 Jul 2012 13:07:47 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 36AAE21F8548; Thu, 12 Jul 2012 13:07:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 79D60101812; Thu, 12 Jul 2012 22:10:39 +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 ge0B45iF6lG8; Thu, 12 Jul 2012 22:10:39 +0200 (CEST)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 5CFB3101811; Thu, 12 Jul 2012 22:10:24 +0200 (CEST)
Received: from [10.7.0.105] (10.7.0.105) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 12 Jul 2012 22:08:03 +0200
Message-ID: <4FFF2E8F.4040807@neclab.eu>
Date: Thu, 12 Jul 2012 22:07:43 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: Leeyoung <leeyoung@huawei.com>
References: <7AEB3D6833318045B4AE71C2C87E8E1720CC2D35@dfweml511-mbx.china.huawei.com>
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E1720CC2D35@dfweml511-mbx.china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.7.0.105]
Cc: "altoext@ietf.org" <altoext@ietf.org>, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] [altoext] FW: New Version Notification for	draft-lee-alto-app-net-info-exchange-00.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, 12 Jul 2012 20:07:48 -0000

A gentle reminder to avoid cross-posting to several mailing list.

Thank you,

   Martin

On 07/09/2012 06:10 PM, Leeyoung wrote:
> Hi All,
>
> We have just published ALTO extension to support application and network resource information exchange for high bandwidth applications.
> This is part of the i2aex initiative.
>
> Thanks in advance for your comment and discussion.
>
> Young
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Monday, July 09, 2012 11:06 AM
> To: Leeyoung
> Cc: choits@etri.re.kr; Sreekanth madhavan; gregb@grotto-networking.com; Dhruv Dhody
> Subject: New Version Notification for draft-lee-alto-app-net-info-exchange-00.txt
>
>
> A new version of I-D, draft-lee-alto-app-net-info-exchange-00.txt
> has been successfully submitted by Young Lee and posted to the
> IETF repository.
>
> Filename:	 draft-lee-alto-app-net-info-exchange
> Revision:	 00
> Title:		 ALTO Extensions to Support Application and Network Resource Information Exchange for High Bandwidth Applications
> Creation date:	 2012-07-09
> WG ID:		 Individual Submission
> Number of pages: 14
> URL:             http://www.ietf.org/internet-drafts/draft-lee-alto-app-net-info-exchange-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-lee-alto-app-net-info-exchange
> Htmlized:        http://tools.ietf.org/html/draft-lee-alto-app-net-info-exchange-00
>
>
> Abstract:
> This draft proposes ALTO information model and protocol extensions to
> support application and network resource information exchange for high
> bandwidth applications in partially controlled and controlled
> environments as part of the infrastructure to application information
> exposure (i2aex) initiative.
>
>
>
>
>
>
> The IETF Secretariat
> _______________________________________________
> altoext mailing list
> altoext@ietf.org
> https://www.ietf.org/mailman/listinfo/altoext
>

-- 
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 emile.stephan@orange.com  Fri Jul 13 00:43:59 2012
Return-Path: <emile.stephan@orange.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 1EB5021F8619; Fri, 13 Jul 2012 00:43:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
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 B02C5X3QUguE; Fri, 13 Jul 2012 00:43:58 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 2DFAE21F859A; Fri, 13 Jul 2012 00:43:58 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id C609B22C65D; Fri, 13 Jul 2012 09:44:32 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id A6352238056; Fri, 13 Jul 2012 09:44:32 +0200 (CEST)
Received: from PEXCVZYM14.corporate.adroot.infra.ftgroup ([fe80::a42f:c628:bc76:d592]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0298.004; Fri, 13 Jul 2012 09:44:29 +0200
From: <emile.stephan@orange.com>
To: "altoext@ietf.org" <altoext@ietf.org>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: I-D Action: draft-stephan-cdni-alto-session-ext-01.txt
Thread-Index: AQHNXefao1xR7iCq10qmF5ry5uYxAJcm2HZQ
Date: Fri, 13 Jul 2012 07:44:28 +0000
Message-ID: <20420_1342165472_4FFFD1E0_20420_1369_1_5AE9CCAA1B4A2248AB61B4C7F0AD5FB902E808@PEXCVZYM14.corporate.adroot.infra.ftgroup>
References: <20120709153022.16781.2010.idtracker@ietfa.amsl.com>
In-Reply-To: <20120709153022.16781.2010.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.3]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.6.19.115414
Subject: [alto] TR: I-D Action: draft-stephan-cdni-alto-session-ext-01.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: Fri, 13 Jul 2012 07:43:59 -0000

Hi=20

We updated the draft draft-stephan-cdni-alto-session-ext.

This version focuses on the situation where a CDNi ALTO server has to excha=
nge information with an ALTO client of an affiliate and with an ALTO client=
 of a competitor.

Comments are welcome.

Regards
Emile

-----Message d'origine-----
De=A0: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org]=
 De la part de internet-drafts@ietf.org
Envoy=E9=A0: lundi 9 juillet 2012 17:30
=C0=A0: i-d-announce@ietf.org
Objet=A0: I-D Action: draft-stephan-cdni-alto-session-ext-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.


	Title           : ALTO session for CDN Interconnection
	Author(s)       : Emile Stephan
                          Selim Ellouze
	Filename        : draft-stephan-cdni-alto-session-ext-01.txt
	Pages           : 22
	Date            : 2012-07-09

Abstract:
   The selection of a downstream CDN by an upstream CDN is based on
   multi-dimensional criteria such as the number of hops, the
   performance of the connections between the user-agent and downstream
   CDNs, the availability of downstream CDNs resources and business
   policies.  Various protocols, such as BGP or ALTO, may be used by a
   downstream CDN to expose content routing information and
   interconnection preferences to an upstream CDN.  This draft specifies
   the parameters of an ALTO session between two interconnected CDNs.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-stephan-cdni-alto-session-ext

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-stephan-cdni-alto-session-ext-01

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-stephan-cdni-alto-session-ext-01


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

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ie=
tf.org/ietf/1shadow-sites.txt

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


From enrico.marocco@telecomitalia.it  Mon Jul 16 00:38:22 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 C21EE21F8469 for <alto@ietfa.amsl.com>; Mon, 16 Jul 2012 00:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.719
X-Spam-Level: 
X-Spam-Status: No, score=-101.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 Dn+ySJPuyjUJ for <alto@ietfa.amsl.com>; Mon, 16 Jul 2012 00:38:22 -0700 (PDT)
Received: from GRFEDG701RM001.telecomitalia.it (grfedg701rm001.telecomitalia.it [217.169.121.20]) by ietfa.amsl.com (Postfix) with ESMTP id D87EA21F8471 for <alto@ietf.org>; Mon, 16 Jul 2012 00:38:21 -0700 (PDT)
Received: from grfhub701rm001.griffon.local (10.19.3.8) by GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP Server (TLS) id 8.3.245.1; Mon, 16 Jul 2012 09:39:01 +0200
Received: from host10-247-static.125-81-b.business.telecomitalia.it (163.162.33.19) by smtp.telecomitalia.it (10.19.9.234) with Microsoft SMTP Server (TLS) id 8.3.245.1; Mon, 16 Jul 2012 09:39:01 +0200
Message-ID: <5003C514.70806@telecomitalia.it>
Date: Mon, 16 Jul 2012 09:39:00 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "alto@ietf.org" <alto@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms050700080308030502000809"
X-TI-Disclaimer: Disclaimer1
Subject: [alto] WebSocket-based notifications
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, 16 Jul 2012 07:38:22 -0000

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

Folks,

Jan and I have just submitted a draft proposing a server-to-client
notification mechanism based on the WebSocket protocol:
http://tools.ietf.org/html/draft-marocco-alto-ws-01

The mechanism proposed is one of the several possible, and the draft at
this point delineates the idea only at quite a high level, without
delving too deep into the details. Yet it should be enough to start a
focused discussion, so please, if you are interested in the topic, take
a quick read and share your thoughts on the list -- whether you feel
this is a promising way to go, or if you have alternatives that you
think would fit better.

--=20
Ciao,
Enrico


--------------ms050700080308030502000809
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+0ggds992kxggPd
MIID2QIBATCBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp
BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0
YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMC30AwCQYF
Kw4DAhoFAKCCAh0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTIwNzE2MDczOTAwWjAjBgkqhkiG9w0BCQQxFgQU6Kfn+wrmFzMfvNekt1atj6EgbbwwbAYJ
KoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4G
CCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB
pQYJKwYBBAGCNxAEMYGXMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20g
THRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG
A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EC
AwLfQDCBpwYLKoZIhvcNAQkQAgsxgZeggZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQQIDAt9AMA0GCSqGSIb3DQEBAQUABIIBAE9pP1Vm3rZ5Vebcy3ty6GBPQ6Qbahbx
G8XyzgjDJOkn4VqHwOCbe8PApFscBH1lnamDlXmd4tEG1U/ONJeaTgGv58Gtnclx41DtHadV
/+TqsbReiAfzjYvaN48A6UMcfQT9KCWCGgK3vRfCEYMq9PkXa9Q1nlIVMAGUKyNbmD6IFVyE
VGQ7NqOJZMosITAyOZuwQD8sf/kUFsbWVoI3mOBGy4YvO9Y9+ra03+zJsxZfQeDy1/Xgbry5
QAve13kwtBI4jPLhLjPS47eGbVbChfLZY977GvooqbOClmi5JWqvy3aqtOhdWnUI2utUbpGg
vEQSW8sHWTjoGcjwh/RYxcwAAAAAAAA=
--------------ms050700080308030502000809--

From nico.schwan@alcatel-lucent.com  Mon Jul 16 06:06:20 2012
Return-Path: <nico.schwan@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 7E3D321F87FD for <alto@ietfa.amsl.com>; Mon, 16 Jul 2012 06:06:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[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 YewN3pwk-rVk for <alto@ietfa.amsl.com>; Mon, 16 Jul 2012 06:06:19 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 937BD21F8532 for <alto@ietf.org>; Mon, 16 Jul 2012 06:06:19 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q6GD6xlU005825 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 16 Jul 2012 15:07:00 +0200
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.55]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Mon, 16 Jul 2012 15:06:47 +0200
From: "Schwan, Nico (Nico)" <nico.schwan@alcatel-lucent.com>
To: "alto@ietf.org" <alto@ietf.org>
Date: Mon, 16 Jul 2012 15:06:46 +0200
Thread-Topic: New version: draft-schwan-alto-incr-updates-02.txt
Thread-Index: Ac1jU9pnb89QN6W3SHWam0gr2KsTRQ==
Message-ID: <E45D69B5D95C074A90D71F60F6A18EF0891BB53FF8@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "Roome, W D" <w.roome@alcatel-lucent.com>
Subject: [alto] New version: draft-schwan-alto-incr-updates-02.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, 16 Jul 2012 13:06:20 -0000

All,

we have submitted an updated version of the "ALTO Incremental Updates" draf=
t which analyses options for partial updates of ALTO Network and Cost Maps.=
 In this version we have further detailed the solution which is based on Fi=
ltered Map Services. As suggested in the last meeting we have also included=
 a short numerical evaluation of the most promising options in the draft. O=
ur main findings are that for more than 100 PIDs partial updates are useful=
, and that the solution based on Filtered Maps is more efficient than JSON =
Patch in terms of needed bytes for encoding.

Any comments on the discussed options, the numbers, or anything else are we=
lcome!

Thanks,

Nico


--------------

A new version of I-D, draft-schwan-alto-incr-updates-02.txt
has been successfully submitted by Nico Schwan and posted to the IETF repos=
itory.

Filename:	 draft-schwan-alto-incr-updates
Revision:	 02
Title:		 ALTO Incremental Updates
Creation date:	 2012-07-16
WG ID:		 Individual Submission
Number of pages: 26
URL:             http://www.ietf.org/internet-drafts/draft-schwan-alto-incr=
-updates-02.txt
Status:          http://datatracker.ietf.org/doc/draft-schwan-alto-incr-upd=
ates
Htmlized:        http://tools.ietf.org/html/draft-schwan-alto-incr-updates-=
02
Diff:            http://tools.ietf.org/rfcdiff?url2=3Ddraft-schwan-alto-inc=
r-updates-02

Abstract:
   The goal of Application-Layer Traffic Optimization (ALTO) is to
   bridge the gap between network and applications by provisioning
   network related information.  This allows applications to make
   informed decisions, for example when selecting a target host from a
   set of candidates.

   Therefore an ALTO server provides network and cost maps to its
   clients.  This draft discusses options on how to provide incremental
   updates for these maps, with the goal of reducing the amount of data
   needed for transmitting the maps and shortly evaluates the two most
   promising options.




From Jan.Seedorf@neclab.eu  Mon Jul 16 08:09:56 2012
Return-Path: <Jan.Seedorf@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 7C32E21F866E; Mon, 16 Jul 2012 08:09:56 -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 eOjamGOkUtA8; Mon, 16 Jul 2012 08:09:52 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id F2FB821F84B2; Mon, 16 Jul 2012 08:09:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 96DF210185B; Mon, 16 Jul 2012 17:13:31 +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 f+ssd0UehYGy; Mon, 16 Jul 2012 17:13:31 +0200 (CEST)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 7E4B010185A; Mon, 16 Jul 2012 17:13:21 +0200 (CEST)
Received: from Polydeuces.office.hd ([169.254.3.121]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Mon, 16 Jul 2012 17:11:14 +0200
From: Jan Seedorf <Jan.Seedorf@neclab.eu>
To: "cdni@ietf.org" <cdni@ietf.org>
Thread-Topic: New Version Notification for draft-seedorf-cdni-request-routing-alto-02.txt
Thread-Index: AQHNY15wovoZxXUnakaSGgdYe+9n4ZcsAo0A
Date: Mon, 16 Jul 2012 15:11:12 +0000
Message-ID: <2779C9F0771F974CAD742BAE6D9904FE32CBC581@Polydeuces.office.hd>
References: <20120716142050.3763.72206.idtracker@ietfa.amsl.com>
In-Reply-To: <20120716142050.3763.72206.idtracker@ietfa.amsl.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.2.227]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: [alto] FW: New Version Notification for	draft-seedorf-cdni-request-routing-alto-02.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, 16 Jul 2012 15:09:56 -0000

RGVhciBhbGwsDQoNCkkgaGF2ZSBqdXN0IHN1Ym1pdHRlZCBhIG5ldyB2ZXJzaW9uIG9mIGRyYWZ0
LXNlZWRvcmYtY2RuaS1yZXF1ZXN0LXJvdXRpbmctYWx0by4gQXMgYmVmb3JlLCB0aGUgZHJhZnQg
b3V0bGluZXMgaG93IEFMVE8gY291bGQgYmUgdXNlZCBmb3IgQ0ROSSByZXF1ZXN0IHJvdXRpbmcs
IGluIHBhcnRpY3VsYXIgZm9yIGRvd25zdHJlYW0gQ0ROIHNlbGVjdGlvbi4gVGhlIG5ldyB2ZXJz
aW9uIGNsYXJpZmllcyBzb21lIGFkZGl0aW9uYWwgYXNzdW1wdGlvbnMsIHJlZmVycyB0byBzb21l
IG9mIHRoZSBsYXRlc3QgZGlzY3Vzc2lvbnMgd2UgaGF2ZSBoYWQgaW4gdGhlIGZvb3RwcmludC9j
YXBhYmlsaXRpZXMgZGVzaWduIHRlYW0sIGFuZCBhbHNvIGdpdmVzIHNvbWUgbW9yZSBjb25jcmV0
ZSBleGFtcGxlcyBvbiBob3cgQUxUTyBuZXR3b3JrIGFuZCBjb3N0IG1hcHMgd291bGQgbG9vayBs
aWtlIGFuZCB3aGF0IHRoZSBkZXNpZ24gY2hvaWNlcyBoZXJlIGFyZS4NCg0KQ29tbWVudHMgYXJl
IHdlbGNvbWUuDQoNClNlZSB5b3UgaW4gVmFuY291dmVyLA0KDQogLSBKYW4NCg0KLS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRv
OmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10gDQpTZW50OiBNb25kYXksIEp1bHkgMTYsIDIwMTIg
NDoyMSBQTQ0KVG86IEphbiBTZWVkb3JmDQpTdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRp
b24gZm9yIGRyYWZ0LXNlZWRvcmYtY2RuaS1yZXF1ZXN0LXJvdXRpbmctYWx0by0wMi50eHQNCg0K
DQpBIG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtc2VlZG9yZi1jZG5pLXJlcXVlc3Qtcm91dGlu
Zy1hbHRvLTAyLnR4dA0KaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBKYW4gU2Vl
ZG9yZiBhbmQgcG9zdGVkIHRvIHRoZQ0KSUVURiByZXBvc2l0b3J5Lg0KDQpGaWxlbmFtZToJIGRy
YWZ0LXNlZWRvcmYtY2RuaS1yZXF1ZXN0LXJvdXRpbmctYWx0bw0KUmV2aXNpb246CSAwMg0KVGl0
bGU6CQkgQ0ROSSBSZXF1ZXN0IFJvdXRpbmcgd2l0aCBBTFRPDQpDcmVhdGlvbiBkYXRlOgkgMjAx
Mi0wNy0xNg0KV0cgSUQ6CQkgSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQpOdW1iZXIgb2YgcGFnZXM6
IDIwDQpVUkw6ICAgICAgICAgICAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRz
L2RyYWZ0LXNlZWRvcmYtY2RuaS1yZXF1ZXN0LXJvdXRpbmctYWx0by0wMi50eHQNClN0YXR1czog
ICAgICAgICAgaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1zZWVkb3JmLWNk
bmktcmVxdWVzdC1yb3V0aW5nLWFsdG8NCkh0bWxpemVkOiAgICAgICAgaHR0cDovL3Rvb2xzLmll
dGYub3JnL2h0bWwvZHJhZnQtc2VlZG9yZi1jZG5pLXJlcXVlc3Qtcm91dGluZy1hbHRvLTAyDQpE
aWZmOiAgICAgICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQt
c2VlZG9yZi1jZG5pLXJlcXVlc3Qtcm91dGluZy1hbHRvLTAyDQoNCkFic3RyYWN0Og0KICAgTmV0
d29yayBTZXJ2aWNlIFByb3ZpZGVycyAoTlNQcykgYXJlIGN1cnJlbnRseSBjb25zaWRlcmluZyB0
byBkZXBsb3kNCiAgIENvbnRlbnQgRGVsaXZlcnkgTmV0d29ya3MgKENETnMpIHdpdGhpbiB0aGVp
ciBuZXR3b3Jrcy4gIEFzIGENCiAgIGNvbnNlcXVlbmNlIG9mIHRoaXMgZGV2ZWxvcG1lbnQsIHRo
ZXJlIGlzIGEgbmVlZCBmb3IgaW50ZXJjb25uZWN0aW5nDQogICB0aGVzZSBsb2NhbCBDRE5zLiAg
VGhlIG5lY2Vzc2FyeSBpbnRlcmZhY2VzIGZvciBpbnRlci1jb25uZWN0aW5nIENETnMNCiAgIGFy
ZSBjdXJyZW50bHkgYmVpbmcgZGVmaW5lZCBpbiB0aGUgQ29udGVudCBEZWxpdmVyeSBOZXR3b3Jr
cw0KICAgSW50ZXJjb25uZWN0aW9uIChDRE5JKSBXRy4gIFRoaXMgZG9jdW1lbnQgZm9jdXNzZXMg
b24gdGhlIFJlcXVlc3QNCiAgIFJvdXRpbmcgSW50ZXJmYWNlIG9mIENETkksIGFuZCBtb3JlIHNw
ZWNpZmljYWxseSBvbiBob3cgdGhlIHNvbHV0aW9ucw0KICAgY3VycmVudGx5IGJlaW5nIGRlZmlu
ZWQgaW4gdGhlIEFwcGxpY2F0aW9uIExheWVyIFRyYWZmaWMgT3B0aW1pemF0aW9uDQogICAoQUxU
TykgV0cgY2FuIGltcHJvdmUgQ0ROSSByZXF1ZXN0IHJvdXRpbmcuICBUaGUgb3ZlcmFsbCBpbnRl
bnRpb24NCiAgIGJlaGluZCB0aGlzIGRvY3VtZW50IGlzIHRvIGZvc3RlciBkaXNjdXNzaW9ucyAo
aW4gdGhlIENETkkgYXMgd2VsbCBhcw0KICAgaW4gdGhlIEFMVE8gV0cpIHJlZ2FyZGluZyBpZiwg
aG93LCBhbmQgdW5kZXIgd2hhdCBjb25kaXRpb25zIEFMVE8gY2FuDQogICBiZSB1c2VmdWwgdG8g
b3B0aW1pemUgQ0ROSSByZXF1ZXN0IHJvdXRpbmcuICBBcyBiYXNpcyBmb3IgdGhpcw0KICAgZGlz
Y3Vzc2lvbiwgdGhpcyBkb2N1bWVudCBwcm92aWRlcyBjb25jcmV0ZSBleGFtcGxlcyBvZiBob3cg
QUxUTyBjYW4NCiAgIGJlIGludGVncmF0ZWQgd2l0aGluIENETkkgcmVxdWVzdCByb3V0aW5nIGFu
ZCBpbiBwYXJ0aWN1bGFyIGluIHRoZQ0KICAgcHJvY2VzcyBvZiBzZWxlY3RpbmcgYSBkb3duc3Ry
ZWFtIENETi4gIFRoZSBleGFtcGxlcyBpbiB0aGlzIGRvY3VtZW50DQogICBhcmUgYmFzZWQgb24g
dGhlIHVzZSBjYXNlcyBhbmQgZXhhbXBsZXMgY3VycmVudGx5IGJlaW5nIGRpc2N1c3NlZCBpbg0K
ICAgdGhlIENETkkgV0cuDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICANCg0KDQpUaGUgSUVU
RiBTZWNyZXRhcmlhdA0K

From internet-drafts@ietf.org  Mon Jul 16 13:23:49 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 08A7011E80F0; Mon, 16 Jul 2012 13:23:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.488
X-Spam-Level: 
X-Spam-Status: No, score=-102.488 tagged_above=-999 required=5 tests=[AWL=0.111, 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 PMpiPvyvagL1; Mon, 16 Jul 2012 13:23:48 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C2F611E8091; Mon, 16 Jul 2012 13:23:48 -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.30p3
Message-ID: <20120716202348.29757.94852.idtracker@ietfa.amsl.com>
Date: Mon, 16 Jul 2012 13:23:48 -0700
Cc: alto@ietf.org
Subject: [alto] I-D Action: draft-ietf-alto-server-discovery-04.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, 16 Jul 2012 20:23:49 -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 Optimization Wo=
rking Group of the IETF.

	Title           : ALTO Server Discovery
	Author(s)       : Sebastian Kiesel
                          Martin Stiemerling
                          Nico Schwan
                          Michael Scharf
                          Haibin Song
	Filename        : draft-ietf-alto-server-discovery-04.txt
	Pages           : 26
	Date            : 2012-07-16

Abstract:
   The goal of Application-Layer Traffic Optimization (ALTO) is to
   provide guidance to applications, which have to select one or several
   hosts from a set of candidates that are able to provide a desired
   resource.

   Entities seeking guidance need to discover and possibly select an
   ALTO server to ask.  This is called ALTO server discovery.  This memo
   describes an ALTO server discovery mechanism based on several
   alternative mechanisms that are applicable when the resource consumer
   is co-located with the ALTO client.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-alto-server-discovery

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-alto-server-discovery-04

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-alto-server-discovery-04


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


From Martin.Stiemerling@neclab.eu  Mon Jul 16 13:29:33 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 07D1111E8142 for <alto@ietfa.amsl.com>; Mon, 16 Jul 2012 13:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.493
X-Spam-Level: 
X-Spam-Status: No, score=-102.493 tagged_above=-999 required=5 tests=[AWL=0.106, 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 giNRwSKEclRl for <alto@ietfa.amsl.com>; Mon, 16 Jul 2012 13:29:30 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id A884111E80A3 for <alto@ietf.org>; Mon, 16 Jul 2012 13:29:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id C3497101862 for <alto@ietf.org>; Mon, 16 Jul 2012 22:33:11 +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 3XejW6LrOgJL for <alto@ietf.org>; Mon, 16 Jul 2012 22:33:11 +0200 (CEST)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id A28B610185F for <alto@ietf.org>; Mon, 16 Jul 2012 22:33:06 +0200 (CEST)
Received: from [10.7.0.105] (10.7.0.105) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 16 Jul 2012 22:30:58 +0200
Message-ID: <500479D0.3050504@neclab.eu>
Date: Mon, 16 Jul 2012 22:30:08 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: "alto@ietf.org" <alto@ietf.org>
References: <20120716202348.29757.94852.idtracker@ietfa.amsl.com>
In-Reply-To: <20120716202348.29757.94852.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20120716202348.29757.94852.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.7.0.105]
Subject: [alto] Fwd:  I-D Action: draft-ietf-alto-server-discovery-04.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, 16 Jul 2012 20:29:33 -0000

[writing without AD hat on]
Hi there,

This update of the ALTO server discovery addresses the comments we have 
received during the last meeting, especially to remove the 3rd party 
server discovery and to focus on deployments with DHCP and PPP.

Please note that the 3rd party server discovery part is now documented 
in draft-kist-alto-3pdisc-00.txt
(https://datatracker.ietf.org/doc/draft-kist-alto-3pdisc/)

  Martin



-------- Original Message --------
Subject: [alto] I-D Action: draft-ietf-alto-server-discovery-04.txt
Date: Mon, 16 Jul 2012 13:23:48 -0700
From: <internet-drafts@ietf.org>
To: <i-d-announce@ietf.org>
CC: <alto@ietf.org>


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

	Title           : ALTO Server Discovery
	Author(s)       : Sebastian Kiesel
                           Martin Stiemerling
                           Nico Schwan
                           Michael Scharf
                           Haibin Song
	Filename        : draft-ietf-alto-server-discovery-04.txt
	Pages           : 26
	Date            : 2012-07-16

Abstract:
    The goal of Application-Layer Traffic Optimization (ALTO) is to
    provide guidance to applications, which have to select one or several
    hosts from a set of candidates that are able to provide a desired
    resource.

    Entities seeking guidance need to discover and possibly select an
    ALTO server to ask.  This is called ALTO server discovery.  This memo
    describes an ALTO server discovery mechanism based on several
    alternative mechanisms that are applicable when the resource consumer
    is co-located with the ALTO client.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-alto-server-discovery

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-alto-server-discovery-04

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=draft-ietf-alto-server-discovery-04


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

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

-- 
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 enrico.marocco@telecomitalia.it  Wed Jul 18 00:37:53 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 03BEF21F8629 for <alto@ietfa.amsl.com>; Wed, 18 Jul 2012 00:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.789
X-Spam-Level: 
X-Spam-Status: No, score=-100.789 tagged_above=-999 required=5 tests=[AWL=-0.929, BAYES_20=-0.74, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245,  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 AOJvjtJIgXGi for <alto@ietfa.amsl.com>; Wed, 18 Jul 2012 00:37:52 -0700 (PDT)
Received: from GRFEDG701RM001.telecomitalia.it (grfedg701rm001.telecomitalia.it [217.169.121.20]) by ietfa.amsl.com (Postfix) with ESMTP id 0D23521F8624 for <alto@ietf.org>; Wed, 18 Jul 2012 00:37:51 -0700 (PDT)
Received: from grfhub703rm001.griffon.local (10.19.3.10) by GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP Server (TLS) id 8.3.245.1; Wed, 18 Jul 2012 09:38:38 +0200
Received: from host8-247-static.125-81-b.business.telecomitalia.it (163.162.33.18) by smtp.telecomitalia.it (10.19.9.236) with Microsoft SMTP Server (TLS) id 8.3.245.1; Wed, 18 Jul 2012 09:38:37 +0200
Message-ID: <500667FD.6090107@telecomitalia.it>
Date: Wed, 18 Jul 2012 09:38:37 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "alto@ietf.org" <alto@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040906090103020408060603"
X-TI-Disclaimer: Disclaimer1
Subject: [alto] Preliminary agenda for IETF 84
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, 18 Jul 2012 07:37:53 -0000

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

Hi all,

a draft agenda for the next face to face meeting is available at:
http://www.ietf.org/proceedings/84/agenda/agenda-84-alto

The primary goal of the meeting will be to agree on the final post-WGLC
changes to the protocol specs and give our AD confidence for moving it
forward in the publication process. Then, we hope to close all the
remaining issues with the discovery mechanism to get it ready for WGLC
and, finally, we want to give some time to proponents of concrete
proposals for future extensions, that mostly follow on the i2aex BoF
that was held in Paris.

Please take a look at the agenda and, especially if you've sent a
request you think has not been properly served, feel free to suggest any
changes.

Enrico


--------------ms040906090103020408060603
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+0ggds992kxggPd
MIID2QIBATCBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp
BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0
YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMC30AwCQYF
Kw4DAhoFAKCCAh0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTIwNzE4MDczODM3WjAjBgkqhkiG9w0BCQQxFgQUyes3qNpMhaW+WphAqeMgX3pVG7owbAYJ
KoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4G
CCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB
pQYJKwYBBAGCNxAEMYGXMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20g
THRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG
A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EC
AwLfQDCBpwYLKoZIhvcNAQkQAgsxgZeggZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQQIDAt9AMA0GCSqGSIb3DQEBAQUABIIBABzMvpI7E9HicASHpfHwc+wzqwzL1Cs/
arn1PZ2hBzAY1meOUWNmy1WescfjkFoPGZPqAeagAOsONhP+Iq8SgVwIfEPVyYD8ZPJ3RE3P
KsYur4u7NvOPVxlip3hTg6AVbA+lKXjE3EsNiAFFkasyjWiruY4Q6tpv711h/BWziKIzNNth
CBWqRsK5zEJ+zWp8iRCC6KhIRww6vokPRfT2VdI+8srjaQ0OqE36oRHZ+9d/QgypTR/KjcGd
NyWCxSBF+OzXApFX5y84L0JAqzqU7pwjJ6h4cWxvZXSaygJ43idNrEG+igjXGxYqEb18Y/Bk
gMxxDhiwlmOlOt+QoxcfdCEAAAAAAAA=
--------------ms040906090103020408060603--

From ravi.nandiraju@huawei.com  Fri Jul 20 05:16:42 2012
Return-Path: <ravi.nandiraju@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 CDE4721F8570 for <alto@ietfa.amsl.com>; Fri, 20 Jul 2012 05:16:42 -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 EwscDe+IvMWj for <alto@ietfa.amsl.com>; Fri, 20 Jul 2012 05:16:42 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2CEEA21F84C2 for <alto@ietf.org>; Fri, 20 Jul 2012 05:16:42 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AIE68584; Fri, 20 Jul 2012 08:17:38 -0400 (EDT)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 20 Jul 2012 05:15:53 -0700
Received: from SZXEML419-HUB.china.huawei.com (10.82.67.158) by dfweml406-hub.china.huawei.com (10.193.5.131) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 20 Jul 2012 05:15:59 -0700
Received: from SZXEML523-MBS.china.huawei.com ([169.254.6.147]) by szxeml419-hub.china.huawei.com ([10.82.67.158]) with mapi id 14.01.0323.003; Fri, 20 Jul 2012 20:15:45 +0800
From: Ravi nandiraju <ravi.nandiraju@huawei.com>
To: Enrico Marocco <enrico.marocco@telecomitalia.it>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: [alto] WebSocket-based notifications
Thread-Index: AQHNYyYb4mU7ZTbG0kmBbVNyNwcp9ZcyFpFD
Date: Fri, 20 Jul 2012 12:15:44 +0000
Message-ID: <7FA18E7BC523F04096632E46DA905D7A51DC0EA7@szxeml523-mbs.china.huawei.com>
References: <5003C514.70806@telecomitalia.it>
In-Reply-To: <5003C514.70806@telecomitalia.it>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.96.96]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [alto] WebSocket-based notifications
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, 20 Jul 2012 12:16:43 -0000

Hi Enrico,
  I went through the proposed mechanism of notifications based on WebSocket=
 protocol. I think this mechanism has the additional overhead of server nee=
ding to keep the connection alive for all the clients which need notificati=
on. This works well if the number of clients are less. In case of scenarios=
 where the clients are more, then the server needs to manage a lot of conne=
ctions.=20

The additonal drawback of this mechanism is that if there is no change in t=
he map data then the connections still needs to be managed by the server.

-Ravi

________________________________________
From: alto-bounces@ietf.org [alto-bounces@ietf.org] on behalf of Enrico Mar=
occo [enrico.marocco@telecomitalia.it]
Sent: Monday, July 16, 2012 1:09 PM
To: alto@ietf.org
Subject: [alto] WebSocket-based notifications

Folks,

Jan and I have just submitted a draft proposing a server-to-client
notification mechanism based on the WebSocket protocol:
http://tools.ietf.org/html/draft-marocco-alto-ws-01

The mechanism proposed is one of the several possible, and the draft at
this point delineates the idea only at quite a high level, without
delving too deep into the details. Yet it should be enough to start a
focused discussion, so please, if you are interested in the topic, take
a quick read and share your thoughts on the list -- whether you feel
this is a promising way to go, or if you have alternatives that you
think would fit better.

--
Ciao,
Enrico=

From enrico.marocco@telecomitalia.it  Fri Jul 20 06:01:08 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 6317B21F862B for <alto@ietfa.amsl.com>; Fri, 20 Jul 2012 06:01:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.719
X-Spam-Level: 
X-Spam-Status: No, score=-101.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 QdCDr5NDh8qs for <alto@ietfa.amsl.com>; Fri, 20 Jul 2012 06:01:07 -0700 (PDT)
Received: from GRFEDG702RM001.telecomitalia.it (grfedg702rm001.telecomitalia.it [217.169.121.21]) by ietfa.amsl.com (Postfix) with ESMTP id 4E49F21F8629 for <alto@ietf.org>; Fri, 20 Jul 2012 06:01:07 -0700 (PDT)
Received: from grfhub702rm001.griffon.local (10.19.3.9) by GRFEDG702RM001.telecomitalia.it (10.173.88.21) with Microsoft SMTP Server (TLS) id 8.3.245.1; Fri, 20 Jul 2012 15:01:59 +0200
Received: from MacLab.local (10.229.8.26) by smtp.telecomitalia.it (10.19.9.235) with Microsoft SMTP Server (TLS) id 8.3.245.1; Fri, 20 Jul 2012 15:01:58 +0200
Message-ID: <500956C6.6050809@telecomitalia.it>
Date: Fri, 20 Jul 2012 15:01:58 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Ravi nandiraju <ravi.nandiraju@huawei.com>
References: <5003C514.70806@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC0EA7@szxeml523-mbs.china.huawei.com>
In-Reply-To: <7FA18E7BC523F04096632E46DA905D7A51DC0EA7@szxeml523-mbs.china.huawei.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms050001040001020607050307"
X-TI-Disclaimer: Disclaimer1
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WebSocket-based notifications
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, 20 Jul 2012 13:01:08 -0000

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

There certainly is additional overhead with any push notification
mechanism, esp. as compared to the simple pull model. For sure in terms
of resources needed for maintaining the subscription state of the
clients to be notified and for keeping the notification channels alive.
But that's a price you have to pay if you want to have server-initiated
notifications and in the end I believe the transport protocol will
hardly have a significant impact on it. Can you point out where you
think in WebSocket lays the additional overhead other alternatives do
not suffer from?

Enrico

On 7/20/12 2:15 PM, Ravi nandiraju wrote:
> Hi Enrico,
>   I went through the proposed mechanism of notifications based on WebSo=
cket protocol. I think this mechanism has the additional overhead of serv=
er needing to keep the connection alive for all the clients which need no=
tification. This works well if the number of clients are less. In case of=
 scenarios where the clients are more, then the server needs to manage a =
lot of connections.=20
>=20
> The additonal drawback of this mechanism is that if there is no change =
in the map data then the connections still needs to be managed by the ser=
ver.
>=20
> -Ravi
>=20
> ________________________________________
> From: alto-bounces@ietf.org [alto-bounces@ietf.org] on behalf of Enrico=
 Marocco [enrico.marocco@telecomitalia.it]
> Sent: Monday, July 16, 2012 1:09 PM
> To: alto@ietf.org
> Subject: [alto] WebSocket-based notifications
>=20
> Folks,
>=20
> Jan and I have just submitted a draft proposing a server-to-client
> notification mechanism based on the WebSocket protocol:
> http://tools.ietf.org/html/draft-marocco-alto-ws-01
>=20
> The mechanism proposed is one of the several possible, and the draft at=

> this point delineates the idea only at quite a high level, without
> delving too deep into the details. Yet it should be enough to start a
> focused discussion, so please, if you are interested in the topic, take=

> a quick read and share your thoughts on the list -- whether you feel
> this is a promising way to go, or if you have alternatives that you
> think would fit better.
>=20
> --
> Ciao,
> Enrico



--------------ms050001040001020607050307
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+0ggds992kxggPd
MIID2QIBATCBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp
BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0
YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMC30AwCQYF
Kw4DAhoFAKCCAh0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTIwNzIwMTMwMTU4WjAjBgkqhkiG9w0BCQQxFgQUyRzjMTz9vdFwiEnL/FbUj1Ig19cwbAYJ
KoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4G
CCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB
pQYJKwYBBAGCNxAEMYGXMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20g
THRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG
A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EC
AwLfQDCBpwYLKoZIhvcNAQkQAgsxgZeggZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQQIDAt9AMA0GCSqGSIb3DQEBAQUABIIBAJ+e29o234kRxUJS/stqIiOeYNQR7Cid
3EgR0KoWxbhduP3c0E2CnyQ2AU45e3Ynuj1Mfv9VlSAFjUw4+42dDiG8c5m+c8KSZ2NnS2X1
Qnn1G6jMksEUy1AT+SE5C/u41E8Wm9J5LMUbzvfp5a02niwreqRUymz56mvAy3B3WBM6P2s6
Rl/kS2DuyQX4+wkRPlD4qndx1iS09xTh9CeBmcWYrnWTqvLPVL1pLJB1BEFOR/mqPvy7yZBM
wIowpSeJuQ2/h20vwC/5dpM4atuN1K6UIynr3xlLFcDjrCSKXybZHb16uqzUHqYOc+Ap4+aa
EeAXuzWzvDqqdvlBt6s5rwMAAAAAAAA=
--------------ms050001040001020607050307--

From ravi.nandiraju@huawei.com  Mon Jul 23 00:07:22 2012
Return-Path: <ravi.nandiraju@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 DA2B621F84F2 for <alto@ietfa.amsl.com>; Mon, 23 Jul 2012 00:07:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, 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 pIsUx8PGUWp9 for <alto@ietfa.amsl.com>; Mon, 23 Jul 2012 00:07:20 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 8C86D21F84EC for <alto@ietf.org>; Mon, 23 Jul 2012 00:07:20 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AIG33985; Mon, 23 Jul 2012 03:07:14 -0400 (EDT)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 23 Jul 2012 00:04:11 -0700
Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by dfweml406-hub.china.huawei.com (10.193.5.131) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 23 Jul 2012 00:04:10 -0700
Received: from SZXEML523-MBS.china.huawei.com ([169.254.6.147]) by szxeml410-hub.china.huawei.com ([10.82.67.137]) with mapi id 14.01.0323.003; Mon, 23 Jul 2012 15:04:07 +0800
From: Ravi nandiraju <ravi.nandiraju@huawei.com>
To: Enrico Marocco <enrico.marocco@telecomitalia.it>
Thread-Topic: [alto] WebSocket-based notifications
Thread-Index: AQHNYyYb4mU7ZTbG0kmBbVNyNwcp9ZcyFpFD//+MtwCABNifeQ==
Date: Mon, 23 Jul 2012 07:04:07 +0000
Message-ID: <7FA18E7BC523F04096632E46DA905D7A51DC1F08@szxeml523-mbs.china.huawei.com>
References: <5003C514.70806@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC0EA7@szxeml523-mbs.china.huawei.com>, <500956C6.6050809@telecomitalia.it>
In-Reply-To: <500956C6.6050809@telecomitalia.it>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.96.96]
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] WebSocket-based notifications
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, 23 Jul 2012 07:07:23 -0000

Hi Enrico,
   The overhead which I was mentioning in my previous e-mail was about mana=
ging the connections even when there is no change in the ALTO map informati=
on. I think an explicit subscription/notification mechanism which we propos=
ed in [http://tools.ietf.org/html/draft-alto-caching-subscription-00#sectio=
n-8] does not have this overhead because the server would initiate the conn=
ection only when required. The server does'nt need to maintain the connecti=
on when there is no change in the map information.
   The mechanism which is proposed in the websocket based notification is a=
n implicit subscription where the connection implies the subscription. To k=
eep the subscription alive, the connection needs to be alive. In many cases=
, the client just wants to subscribe and get notified only when there is a =
change in the map data otherwise the connection is just an overhead.

-Ravi
________________________________________
From: Enrico Marocco [enrico.marocco@telecomitalia.it]
Sent: Friday, July 20, 2012 6:31 PM
To: Ravi nandiraju
Cc: alto@ietf.org
Subject: Re: [alto] WebSocket-based notifications

There certainly is additional overhead with any push notification
mechanism, esp. as compared to the simple pull model. For sure in terms
of resources needed for maintaining the subscription state of the
clients to be notified and for keeping the notification channels alive.
But that's a price you have to pay if you want to have server-initiated
notifications and in the end I believe the transport protocol will
hardly have a significant impact on it. Can you point out where you
think in WebSocket lays the additional overhead other alternatives do
not suffer from?

Enrico

On 7/20/12 2:15 PM, Ravi nandiraju wrote:
> Hi Enrico,
>   I went through the proposed mechanism of notifications based on WebSock=
et protocol. I think this mechanism has the additional overhead of server n=
eeding to keep the connection alive for all the clients which need notifica=
tion. This works well if the number of clients are less. In case of scenari=
os where the clients are more, then the server needs to manage a lot of con=
nections.
>
> The additonal drawback of this mechanism is that if there is no change in=
 the map data then the connections still needs to be managed by the server.
>
> -Ravi
>
> ________________________________________
> From: alto-bounces@ietf.org [alto-bounces@ietf.org] on behalf of Enrico M=
arocco [enrico.marocco@telecomitalia.it]
> Sent: Monday, July 16, 2012 1:09 PM
> To: alto@ietf.org
> Subject: [alto] WebSocket-based notifications
>
> Folks,
>
> Jan and I have just submitted a draft proposing a server-to-client
> notification mechanism based on the WebSocket protocol:
> http://tools.ietf.org/html/draft-marocco-alto-ws-01
>
> The mechanism proposed is one of the several possible, and the draft at
> this point delineates the idea only at quite a high level, without
> delving too deep into the details. Yet it should be enough to start a
> focused discussion, so please, if you are interested in the topic, take
> a quick read and share your thoughts on the list -- whether you feel
> this is a promising way to go, or if you have alternatives that you
> think would fit better.
>
> --
> Ciao,
> Enrico=

From enrico.marocco@telecomitalia.it  Mon Jul 23 00:44:21 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 4916321F86C5 for <alto@ietfa.amsl.com>; Mon, 23 Jul 2012 00:44:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.954
X-Spam-Level: 
X-Spam-Status: No, score=-100.954 tagged_above=-999 required=5 tests=[AWL=0.165, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245,  J_CHICKENPOX_42=0.6, 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 bLwS9oe8meYr for <alto@ietfa.amsl.com>; Mon, 23 Jul 2012 00:44:20 -0700 (PDT)
Received: from GRFEDG702RM001.telecomitalia.it (grfedg702rm001.telecomitalia.it [217.169.121.21]) by ietfa.amsl.com (Postfix) with ESMTP id 24CCD21F86AB for <alto@ietf.org>; Mon, 23 Jul 2012 00:44:17 -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; Mon, 23 Jul 2012 09:44:09 +0200
Received: from host11-247-static.125-81-b.business.telecomitalia.it (163.162.33.18) by smtp.telecomitalia.it (10.19.9.236) with Microsoft SMTP Server (TLS) id 8.3.245.1; Mon, 23 Jul 2012 09:44:09 +0200
Message-ID: <500D00C9.6070706@telecomitalia.it>
Date: Mon, 23 Jul 2012 09:44:09 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Ravi nandiraju <ravi.nandiraju@huawei.com>
References: <5003C514.70806@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC0EA7@szxeml523-mbs.china.huawei.com>, <500956C6.6050809@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F08@szxeml523-mbs.china.huawei.com>
In-Reply-To: <7FA18E7BC523F04096632E46DA905D7A51DC1F08@szxeml523-mbs.china.huawei.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms060803060801010203050409"
X-TI-Disclaimer: Disclaimer1
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WebSocket-based notifications
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, 23 Jul 2012 07:44:21 -0000

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

Ok, I see you point. I agree that, for resources that rarely change
there may be even a substantial gain with having the connection
initiated by the server only upon an update event. On the flip side, for
constantly changing resources (e.g. representing uptime-like information
about server load) the overhead of a full HTTP request for each and
every update would easily exceed the overhead due to maintaining a
websocket connection.

More concerning than overhead is however the reachability requirement
that a mechanism based on server-initiated connections pose on the
client side, and that in fact would make it unsuited for any host
residing behind a NAT -- the vast majority of end-user devices.

Enrico

On 7/23/12 9:04 AM, Ravi nandiraju wrote:
> Hi Enrico,
>    The overhead which I was mentioning in my previous e-mail was about =
managing the connections even when there is no change in the ALTO map inf=
ormation. I think an explicit subscription/notification mechanism which w=
e proposed in [http://tools.ietf.org/html/draft-alto-caching-subscription=
-00#section-8] does not have this overhead because the server would initi=
ate the connection only when required. The server does'nt need to maintai=
n the connection when there is no change in the map information.
>    The mechanism which is proposed in the websocket based notification =
is an implicit subscription where the connection implies the subscription=
=2E To keep the subscription alive, the connection needs to be alive. In =
many cases, the client just wants to subscribe and get notified only when=
 there is a change in the map data otherwise the connection is just an ov=
erhead.
>=20
> -Ravi
> ________________________________________
> From: Enrico Marocco [enrico.marocco@telecomitalia.it]
> Sent: Friday, July 20, 2012 6:31 PM
> To: Ravi nandiraju
> Cc: alto@ietf.org
> Subject: Re: [alto] WebSocket-based notifications
>=20
> There certainly is additional overhead with any push notification
> mechanism, esp. as compared to the simple pull model. For sure in terms=

> of resources needed for maintaining the subscription state of the
> clients to be notified and for keeping the notification channels alive.=

> But that's a price you have to pay if you want to have server-initiated=

> notifications and in the end I believe the transport protocol will
> hardly have a significant impact on it. Can you point out where you
> think in WebSocket lays the additional overhead other alternatives do
> not suffer from?
>=20
> Enrico
>=20
> On 7/20/12 2:15 PM, Ravi nandiraju wrote:
>> Hi Enrico,
>>   I went through the proposed mechanism of notifications based on WebS=
ocket protocol. I think this mechanism has the additional overhead of ser=
ver needing to keep the connection alive for all the clients which need n=
otification. This works well if the number of clients are less. In case o=
f scenarios where the clients are more, then the server needs to manage a=
 lot of connections.
>>
>> The additonal drawback of this mechanism is that if there is no change=
 in the map data then the connections still needs to be managed by the se=
rver.
>>
>> -Ravi
>>
>> ________________________________________
>> From: alto-bounces@ietf.org [alto-bounces@ietf.org] on behalf of Enric=
o Marocco [enrico.marocco@telecomitalia.it]
>> Sent: Monday, July 16, 2012 1:09 PM
>> To: alto@ietf.org
>> Subject: [alto] WebSocket-based notifications
>>
>> Folks,
>>
>> Jan and I have just submitted a draft proposing a server-to-client
>> notification mechanism based on the WebSocket protocol:
>> http://tools.ietf.org/html/draft-marocco-alto-ws-01
>>
>> The mechanism proposed is one of the several possible, and the draft a=
t
>> this point delineates the idea only at quite a high level, without
>> delving too deep into the details. Yet it should be enough to start a
>> focused discussion, so please, if you are interested in the topic, tak=
e
>> a quick read and share your thoughts on the list -- whether you feel
>> this is a promising way to go, or if you have alternatives that you
>> think would fit better.
>>
>> --
>> Ciao,
>> Enrico



--------------ms060803060801010203050409
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+0ggds992kxggPd
MIID2QIBATCBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp
BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0
YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMC30AwCQYF
Kw4DAhoFAKCCAh0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTIwNzIzMDc0NDA5WjAjBgkqhkiG9w0BCQQxFgQUSOtwm1d0T246ZYE2StgV/IZKsB4wbAYJ
KoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4G
CCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB
pQYJKwYBBAGCNxAEMYGXMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20g
THRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG
A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EC
AwLfQDCBpwYLKoZIhvcNAQkQAgsxgZeggZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQQIDAt9AMA0GCSqGSIb3DQEBAQUABIIBAF3YZMLaco2+hStk4DpFupRgfEK4Z2nB
9ziMA3lwL2ZF2e5xBP/58iFYIjC6dNCqaHc4S3CrML5ZgMh7x+/fguGoN1/tFRv1tB76io4W
VifDOOZANhsA8x7lXfp5/ZMtBJe/UglUPdYzgzxM09Myk2W1NbxrdAoRsHxwsi0dGxm5SrcF
7TCT7XhtFWJ6wZvHybGal+T3VhGDs1ckaKfnwIq2ZfpEiM1LXFRaTdi7c53MTUfsrJD4+kGp
TCpt9zkCQiMQoSqtC2ewy2fRk5BRDKBblFy6cackJH4SxueM5xznpKwRKI2jPYMJkP983glQ
Vp8mxgTxIGXd0Pw9+IHh8EsAAAAAAAA=
--------------ms060803060801010203050409--

From ravi.nandiraju@huawei.com  Tue Jul 24 02:59:54 2012
Return-Path: <ravi.nandiraju@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 6C0D921F850C for <alto@ietfa.amsl.com>; Tue, 24 Jul 2012 02:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level: 
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, 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 6KuVGLMn+L59 for <alto@ietfa.amsl.com>; Tue, 24 Jul 2012 02:59:53 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2777421F8501 for <alto@ietf.org>; Tue, 24 Jul 2012 02:59:53 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AIH31438; Tue, 24 Jul 2012 05:59:52 -0400 (EDT)
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 24 Jul 2012 02:57:33 -0700
Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by dfweml407-hub.china.huawei.com (10.193.5.132) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 24 Jul 2012 02:57:35 -0700
Received: from SZXEML523-MBS.china.huawei.com ([169.254.6.147]) by szxeml410-hub.china.huawei.com ([10.82.67.137]) with mapi id 14.01.0323.003; Tue, 24 Jul 2012 17:57:28 +0800
From: Ravi nandiraju <ravi.nandiraju@huawei.com>
To: Enrico Marocco <enrico.marocco@telecomitalia.it>
Thread-Topic: [alto] WebSocket-based notifications
Thread-Index: AQHNYyYb4mU7ZTbG0kmBbVNyNwcp9ZcyFpFD//+MtwCABNifef//hZOAgAI9U7o=
Date: Tue, 24 Jul 2012 09:57:28 +0000
Message-ID: <7FA18E7BC523F04096632E46DA905D7A51DC1F55@szxeml523-mbs.china.huawei.com>
References: <5003C514.70806@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC0EA7@szxeml523-mbs.china.huawei.com>, <500956C6.6050809@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F08@szxeml523-mbs.china.huawei.com>, <500D00C9.6070706@telecomitalia.it>
In-Reply-To: <500D00C9.6070706@telecomitalia.it>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.96.96]
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] WebSocket-based notifications
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, 24 Jul 2012 09:59:54 -0000

Hi Enrico,

   Yes. Websockets will be useful for cases where there are frequent notifi=
cations (like server load etc). This is only one use case for subscription/=
notification. IMO, we should define a generic framework for subscription/no=
tification which includes support for things like multiple event subscripti=
on and does'nt have the overhead of persistent connections when the clients=
 are not interested to keep them.
   Regarding the server creating a connection to the client, the client exp=
licitly advertises its contact address for the server to connect to. The re=
achability problem should be solved by the client.

-Ravi

________________________________________
From: Enrico Marocco [enrico.marocco@telecomitalia.it]
Sent: Monday, July 23, 2012 1:14 PM
To: Ravi nandiraju
Cc: alto@ietf.org
Subject: Re: [alto] WebSocket-based notifications

Ok, I see you point. I agree that, for resources that rarely change
there may be even a substantial gain with having the connection
initiated by the server only upon an update event. On the flip side, for
constantly changing resources (e.g. representing uptime-like information
about server load) the overhead of a full HTTP request for each and
every update would easily exceed the overhead due to maintaining a
websocket connection.

More concerning than overhead is however the reachability requirement
that a mechanism based on server-initiated connections pose on the
client side, and that in fact would make it unsuited for any host
residing behind a NAT -- the vast majority of end-user devices.

Enrico

On 7/23/12 9:04 AM, Ravi nandiraju wrote:
> Hi Enrico,
>    The overhead which I was mentioning in my previous e-mail was about ma=
naging the connections even when there is no change in the ALTO map informa=
tion. I think an explicit subscription/notification mechanism which we prop=
osed in [http://tools.ietf.org/html/draft-alto-caching-subscription-00#sect=
ion-8] does not have this overhead because the server would initiate the co=
nnection only when required. The server does'nt need to maintain the connec=
tion when there is no change in the map information.
>    The mechanism which is proposed in the websocket based notification is=
 an implicit subscription where the connection implies the subscription. To=
 keep the subscription alive, the connection needs to be alive. In many cas=
es, the client just wants to subscribe and get notified only when there is =
a change in the map data otherwise the connection is just an overhead.
>
> -Ravi
> ________________________________________
> From: Enrico Marocco [enrico.marocco@telecomitalia.it]
> Sent: Friday, July 20, 2012 6:31 PM
> To: Ravi nandiraju
> Cc: alto@ietf.org
> Subject: Re: [alto] WebSocket-based notifications
>
> There certainly is additional overhead with any push notification
> mechanism, esp. as compared to the simple pull model. For sure in terms
> of resources needed for maintaining the subscription state of the
> clients to be notified and for keeping the notification channels alive.
> But that's a price you have to pay if you want to have server-initiated
> notifications and in the end I believe the transport protocol will
> hardly have a significant impact on it. Can you point out where you
> think in WebSocket lays the additional overhead other alternatives do
> not suffer from?
>
> Enrico
>
> On 7/20/12 2:15 PM, Ravi nandiraju wrote:
>> Hi Enrico,
>>   I went through the proposed mechanism of notifications based on WebSoc=
ket protocol. I think this mechanism has the additional overhead of server =
needing to keep the connection alive for all the clients which need notific=
ation. This works well if the number of clients are less. In case of scenar=
ios where the clients are more, then the server needs to manage a lot of co=
nnections.
>>
>> The additonal drawback of this mechanism is that if there is no change i=
n the map data then the connections still needs to be managed by the server=
.
>>
>> -Ravi
>>
>> ________________________________________
>> From: alto-bounces@ietf.org [alto-bounces@ietf.org] on behalf of Enrico =
Marocco [enrico.marocco@telecomitalia.it]
>> Sent: Monday, July 16, 2012 1:09 PM
>> To: alto@ietf.org
>> Subject: [alto] WebSocket-based notifications
>>
>> Folks,
>>
>> Jan and I have just submitted a draft proposing a server-to-client
>> notification mechanism based on the WebSocket protocol:
>> http://tools.ietf.org/html/draft-marocco-alto-ws-01
>>
>> The mechanism proposed is one of the several possible, and the draft at
>> this point delineates the idea only at quite a high level, without
>> delving too deep into the details. Yet it should be enough to start a
>> focused discussion, so please, if you are interested in the topic, take
>> a quick read and share your thoughts on the list -- whether you feel
>> this is a promising way to go, or if you have alternatives that you
>> think would fit better.
>>
>> --
>> Ciao,
>> Enrico=

From enrico.marocco@telecomitalia.it  Tue Jul 24 03:40:25 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 9D20D21F8647 for <alto@ietfa.amsl.com>; Tue, 24 Jul 2012 03:40:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.419
X-Spam-Level: 
X-Spam-Status: No, score=-101.419 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_42=0.6, 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 dBpWpFmuujB8 for <alto@ietfa.amsl.com>; Tue, 24 Jul 2012 03:40:25 -0700 (PDT)
Received: from GRFEDG701RM001.telecomitalia.it (grfedg701rm001.telecomitalia.it [217.169.121.20]) by ietfa.amsl.com (Postfix) with ESMTP id AE61321F8631 for <alto@ietf.org>; Tue, 24 Jul 2012 03:40:24 -0700 (PDT)
Received: from grfhub702rm001.griffon.local (10.19.3.9) by GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP Server (TLS) id 8.3.245.1; Tue, 24 Jul 2012 12:40:20 +0200
Received: from MacLab.local (10.229.8.78) by smtp.telecomitalia.it (10.19.9.235) with Microsoft SMTP Server (TLS) id 8.3.245.1; Tue, 24 Jul 2012 12:40:16 +0200
Message-ID: <500E7B90.9030902@telecomitalia.it>
Date: Tue, 24 Jul 2012 12:40:16 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Ravi nandiraju <ravi.nandiraju@huawei.com>
References: <5003C514.70806@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC0EA7@szxeml523-mbs.china.huawei.com>, <500956C6.6050809@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F08@szxeml523-mbs.china.huawei.com>, <500D00C9.6070706@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F55@szxeml523-mbs.china.huawei.com>
In-Reply-To: <7FA18E7BC523F04096632E46DA905D7A51DC1F55@szxeml523-mbs.china.huawei.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms020000050703030308030500"
X-TI-Disclaimer: Disclaimer1
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WebSocket-based notifications
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, 24 Jul 2012 10:40:25 -0000

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

On 7/24/12 11:57 AM, Ravi nandiraju wrote:
> Yes. Websockets will be useful for cases where there are frequent
> notifications (like server load etc). This is only one use case for
> subscription/notification. IMO, we should define a generic framework
> for subscription/notification which includes support for things like
> multiple event subscription and does'nt have the overhead of
> persistent connections when the clients are not interested to keep
> them.

This is actually something the authors would like to get feedback about,
i.e. whether people prefer to have one connection per resource, or some
sort of subscription protocol running for multiple resources on a single
connection. The draft at this point suggests the former approach,
basically for simplicity.

> Regarding the server creating a connection to the client, the client
> explicitly advertises its contact address for the server to connect
> to. The reachability problem should be solved by the client.

I cannot think of any way for the client to solve the reachability
problem that is less demanding in terms of resources than a
client-initiated connection. Can you suggest one that works with today's
firewalls, access gateways and carrier NATs?

--=20
Ciao,
Enrico



--------------ms020000050703030308030500
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+0ggds992kxggPd
MIID2QIBATCBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp
BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0
YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMC30AwCQYF
Kw4DAhoFAKCCAh0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTIwNzI0MTA0MDE2WjAjBgkqhkiG9w0BCQQxFgQUtYV5PTv+3BSabJ7+WyNfV34T61wwbAYJ
KoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4G
CCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB
pQYJKwYBBAGCNxAEMYGXMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20g
THRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG
A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EC
AwLfQDCBpwYLKoZIhvcNAQkQAgsxgZeggZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQQIDAt9AMA0GCSqGSIb3DQEBAQUABIIBAF6qOpfQtALHDAKfnEhPz+32/Ms8G9Ut
kD9qD1CgQ/XgdGm/aVbMvN17db5Mui+w/cwwN4vcgQO7jif/dqofFVBHUKLtLog6OQtX/xmU
FyOD5kGHoPYLvyW13hSVXuEF3nCRBZVGja1sBBnYbWjllIhC4zP1FKOGw15B9SyFrIvY/rhT
5qbenJC1mEIcbBzphkBRfT75eyFMZtgllNbDHEhF7tqNxQ9Mdcfwc/rWsmSp8jbG8x+BQDIs
jAWsKV86TVWOSH//3+AvWujnl2TB18HjBfyAnwvvpVQrYDrhkzh4dWD8vFJMUN3lnQSNwaNl
yOddM04I4jlGt6nPZehzK9IAAAAAAAA=
--------------ms020000050703030308030500--

From ravi.nandiraju@huawei.com  Tue Jul 24 22:49:54 2012
Return-Path: <ravi.nandiraju@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 6741821F84B6 for <alto@ietfa.amsl.com>; Tue, 24 Jul 2012 22:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level: 
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, 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 xZyUMx79v8Vo for <alto@ietfa.amsl.com>; Tue, 24 Jul 2012 22:49:53 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 3A92021F845D for <alto@ietf.org>; Tue, 24 Jul 2012 22:49:53 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AIH99667; Wed, 25 Jul 2012 01:49:52 -0400 (EDT)
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 24 Jul 2012 22:47:16 -0700
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by dfweml407-hub.china.huawei.com (10.193.5.132) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 24 Jul 2012 22:47:20 -0700
Received: from SZXEML523-MBS.china.huawei.com ([169.254.6.147]) by szxeml401-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Wed, 25 Jul 2012 13:47:13 +0800
From: Ravi nandiraju <ravi.nandiraju@huawei.com>
To: Enrico Marocco <enrico.marocco@telecomitalia.it>
Thread-Topic: [alto] WebSocket-based notifications
Thread-Index: AQHNYyYb4mU7ZTbG0kmBbVNyNwcp9ZcyFpFD//+MtwCABNifef//hZOAgAI9U7r//4Y3AAA4xtTz
Date: Wed, 25 Jul 2012 05:47:12 +0000
Message-ID: <7FA18E7BC523F04096632E46DA905D7A51DC1F7C@szxeml523-mbs.china.huawei.com>
References: <5003C514.70806@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC0EA7@szxeml523-mbs.china.huawei.com>, <500956C6.6050809@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F08@szxeml523-mbs.china.huawei.com>, <500D00C9.6070706@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F55@szxeml523-mbs.china.huawei.com>, <500E7B90.9030902@telecomitalia.it>
In-Reply-To: <500E7B90.9030902@telecomitalia.it>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.96.96]
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] WebSocket-based notifications
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, 25 Jul 2012 05:49:54 -0000

I agree that NAT traversal is complex but that is for a peer to peer networ=
k where both the peers are behind NATs and they need to figure out their re=
achability. In case of ALTO we don't have that kind of complexity. The ALTO=
 client which expects the server to connect to it needs to ensure that it i=
s reachable on that address/port from an external/internal network. This is=
 same as the way an ALTO server behind a carrier firewall is configured to =
be reachable to clients outside.

I don't envisage ALTO clients like home devices using the subscription mech=
anism because, for a home device client it is easier to query the ALTO serv=
er for a changed map information rather than going for a subscription.=20

IMO, this subscription mechanism would be useful for infrastructure cases l=
ike gateway devices, CDN, inter-DC etc where the problem of reachability is=
 not so complex as in the case of peer to peer.

Please let me know if there is something I am missing here.

-Ravi
________________________________________
From: Enrico Marocco [enrico.marocco@telecomitalia.it]
Sent: Tuesday, July 24, 2012 4:10 PM
To: Ravi nandiraju
Cc: alto@ietf.org
Subject: Re: [alto] WebSocket-based notifications

On 7/24/12 11:57 AM, Ravi nandiraju wrote:
> Yes. Websockets will be useful for cases where there are frequent
> notifications (like server load etc). This is only one use case for
> subscription/notification. IMO, we should define a generic framework
> for subscription/notification which includes support for things like
> multiple event subscription and does'nt have the overhead of
> persistent connections when the clients are not interested to keep
> them.

This is actually something the authors would like to get feedback about,
i.e. whether people prefer to have one connection per resource, or some
sort of subscription protocol running for multiple resources on a single
connection. The draft at this point suggests the former approach,
basically for simplicity.

> Regarding the server creating a connection to the client, the client
> explicitly advertises its contact address for the server to connect
> to. The reachability problem should be solved by the client.

I cannot think of any way for the client to solve the reachability
problem that is less demanding in terms of resources than a
client-initiated connection. Can you suggest one that works with today's
firewalls, access gateways and carrier NATs?

--
Ciao,
Enrico=

From enrico.marocco@telecomitalia.it  Wed Jul 25 00:44:06 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 3128221F84D6 for <alto@ietfa.amsl.com>; Wed, 25 Jul 2012 00:44:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.619
X-Spam-Level: 
X-Spam-Status: No, score=-101.619 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245,  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 rVuOOqMobNgS for <alto@ietfa.amsl.com>; Wed, 25 Jul 2012 00:44:05 -0700 (PDT)
Received: from GRFEDG701RM001.telecomitalia.it (grfedg701rm001.telecomitalia.it [217.169.121.20]) by ietfa.amsl.com (Postfix) with ESMTP id 3C9E221F84DC for <alto@ietf.org>; Wed, 25 Jul 2012 00:44:05 -0700 (PDT)
Received: from grfhub701rm001.griffon.local (10.19.3.8) by GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP Server (TLS) id 8.3.245.1; Wed, 25 Jul 2012 09:43:57 +0200
Received: from MacLab.local (10.229.8.78) by smtp.telecomitalia.it (10.19.9.234) with Microsoft SMTP Server (TLS) id 8.3.245.1; Wed, 25 Jul 2012 09:43:57 +0200
Message-ID: <500FA3BC.5040003@telecomitalia.it>
Date: Wed, 25 Jul 2012 09:43:56 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Ravi nandiraju <ravi.nandiraju@huawei.com>
References: <5003C514.70806@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC0EA7@szxeml523-mbs.china.huawei.com>, <500956C6.6050809@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F08@szxeml523-mbs.china.huawei.com>, <500D00C9.6070706@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F55@szxeml523-mbs.china.huawei.com>, <500E7B90.9030902@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F7C@szxeml523-mbs.china.huawei.com>
In-Reply-To: <7FA18E7BC523F04096632E46DA905D7A51DC1F7C@szxeml523-mbs.china.huawei.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms000203030006020103090104"
X-TI-Disclaimer: Disclaimer1
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WebSocket-based notifications
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, 25 Jul 2012 07:44:06 -0000

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

On 7/25/12 7:47 AM, Ravi nandiraju wrote:
> I don't envisage ALTO clients like home devices using the
> subscription mechanism because, for a home device client it is easier
> to query the ALTO server for a changed map information rather than
> going for a subscription.

Just to be clear, here by "home device" you actually mean "user
devices", i.e. any laptop, desktop, smartphone and whatnot that may for
example run in a home network.

> IMO, this subscription mechanism would be useful for infrastructure
> cases like gateway devices, CDN, inter-DC etc where the problem of
> reachability is not so complex as in the case of peer to peer.

And useless in any environments where global reachability cannot be
taken for granted. Agreed.

--=20
Ciao,
Enrico


--------------ms000203030006020103090104
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+0ggds992kxggPd
MIID2QIBATCBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp
BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0
YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMC30AwCQYF
Kw4DAhoFAKCCAh0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTIwNzI1MDc0MzU2WjAjBgkqhkiG9w0BCQQxFgQUHipFFZl1Df239Fg/0ERgqP1OTiMwbAYJ
KoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4G
CCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB
pQYJKwYBBAGCNxAEMYGXMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20g
THRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG
A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EC
AwLfQDCBpwYLKoZIhvcNAQkQAgsxgZeggZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQQIDAt9AMA0GCSqGSIb3DQEBAQUABIIBAJpV8Zo/9+f63uCS1534Bfr3N7s9SkAx
b/3x7P6xQgUnoPCOSdjd8xD0FE2y59P6TkBzIs7IljZfFYoX4dU/XMjT22TwNxLkHUAbcT/j
Pz+ujgWcdLm7Qs9/PdkWsZHTzn9NfluTnZHdUn6sdhWEFgGM1iho+mvRfE7o65f9avK8g4ou
URG6sHEJe23i+Sx/icx0F8bWNccqta5Ip0wGoC5++xIGePyL78Fg0+IewYFi1sM9vJ1Bm50L
E7wRCp96uGvN41mW5znvLEB7ItzjIxXkFBzMguezX8NoYjvLOdL/O048KyobSel7RmOtdZph
dOvukC49pr9IRB9kcNoCh3QAAAAAAAA=
--------------ms000203030006020103090104--

From ravi.nandiraju@huawei.com  Wed Jul 25 01:43:31 2012
Return-Path: <ravi.nandiraju@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 0868621F858F for <alto@ietfa.amsl.com>; Wed, 25 Jul 2012 01:43:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.374
X-Spam-Level: 
X-Spam-Status: No, score=-6.374 tagged_above=-999 required=5 tests=[AWL=0.225,  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 6CTUE4eMq+Cs for <alto@ietfa.amsl.com>; Wed, 25 Jul 2012 01:43:30 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 658D721F858D for <alto@ietf.org>; Wed, 25 Jul 2012 01:43:30 -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 AIB19532; Wed, 25 Jul 2012 04:43:30 -0400 (EDT)
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 25 Jul 2012 01:39:49 -0700
Received: from SZXEML440-HUB.china.huawei.com (10.72.61.75) by dfweml405-hub.china.huawei.com (10.193.5.102) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 25 Jul 2012 01:39:48 -0700
Received: from SZXEML523-MBS.china.huawei.com ([169.254.6.147]) by SZXEML440-HUB.china.huawei.com ([10.72.61.75]) with mapi id 14.01.0323.003; Wed, 25 Jul 2012 16:39:42 +0800
From: Ravi nandiraju <ravi.nandiraju@huawei.com>
To: Enrico Marocco <enrico.marocco@telecomitalia.it>
Thread-Topic: [alto] WebSocket-based notifications
Thread-Index: AQHNYyYb4mU7ZTbG0kmBbVNyNwcp9ZcyFpFD//+MtwCABNifef//hZOAgAI9U7r//4Y3AAA4xtTz//+a2gCAAJCTDw==
Date: Wed, 25 Jul 2012 08:39:42 +0000
Message-ID: <7FA18E7BC523F04096632E46DA905D7A51DC1F9B@szxeml523-mbs.china.huawei.com>
References: <5003C514.70806@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC0EA7@szxeml523-mbs.china.huawei.com>, <500956C6.6050809@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F08@szxeml523-mbs.china.huawei.com>, <500D00C9.6070706@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F55@szxeml523-mbs.china.huawei.com>, <500E7B90.9030902@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F7C@szxeml523-mbs.china.huawei.com>, <500FA3BC.5040003@telecomitalia.it>
In-Reply-To: <500FA3BC.5040003@telecomitalia.it>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.96.96]
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] WebSocket-based notifications
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, 25 Jul 2012 08:43:31 -0000

________________________________________
From: Enrico Marocco [enrico.marocco@telecomitalia.it]
Sent: Wednesday, July 25, 2012 1:13 PM
To: Ravi nandiraju
Cc: alto@ietf.org
Subject: Re: [alto] WebSocket-based notifications

On 7/25/12 7:47 AM, Ravi nandiraju wrote:
> I don't envisage ALTO clients like home devices using the
> subscription mechanism because, for a home device client it is easier
> to query the ALTO server for a changed map information rather than
> going for a subscription.

Just to be clear, here by "home device" you actually mean "user
devices", i.e. any laptop, desktop, smartphone and whatnot that may for
example run in a home network.

[Ravi] Yes. What I meant by "home device" are the devices which are used by=
 end users as P2P clients and which could potentially use ALTO as clients.

> IMO, this subscription mechanism would be useful for infrastructure
> cases like gateway devices, CDN, inter-DC etc where the problem of
> reachability is not so complex as in the case of peer to peer.

And useless in any environments where global reachability cannot be
taken for granted. Agreed.

[Ravi] Basically what I meant was, we don't need to consider the case of  "=
user devices" for subscription/notification because for them it is easier t=
o query the information based on need rather than subscribing. I am not ver=
y clear if reachability is really a concern in the use case for ALTO subscr=
iption/notification.

--
Ciao,
Enrico=

From yang.r.yang@gmail.com  Wed Jul 25 04:40:27 2012
Return-Path: <yang.r.yang@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 EB8B721F851E for <alto@ietfa.amsl.com>; Wed, 25 Jul 2012 04:40:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.818
X-Spam-Level: 
X-Spam-Status: No, score=-2.818 tagged_above=-999 required=5 tests=[AWL=0.158,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 YZNrPhI+eQgc for <alto@ietfa.amsl.com>; Wed, 25 Jul 2012 04:40:26 -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 CD12921F850D for <alto@ietf.org>; Wed, 25 Jul 2012 04:40:25 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so1143875obb.31 for <alto@ietf.org>; Wed, 25 Jul 2012 04:40:25 -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:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ZU3U1S1KF5hLBdAQ7YPklJLPPOVnVlxEdlK6TMh1WlE=; b=VBCv19lBdsL/25OocGCVvDJlLaXaxkkI60cf9Dvnuf1qqB8gYJIzFVvTTLAUtDDhp2 I320s5jzyFm6xDWsxP6a3kp9GeZK6Q85PWxnHGedVBpK+nl66WcK5pYjFctsPr7ri4IY qD3MNNmr/9ME58BowzF8vFPNSqo/J/maa3UPqnN7K/OdavajbVX/MoFueVHQfw4NMKEl iZkKesrP8De/EI5tWDhUq/6TI7vc0bgo4c+RjrwcCEz7q4xW1r/aNKmRPyNaun2deVG8 gHyFFubTo2ILnGscWfGwne+TQRtsyLRsVGP4Jkih0dFkj4J3Ko84n8qrzpVFuCn0GfPM vdLQ==
MIME-Version: 1.0
Received: by 10.60.22.165 with SMTP id e5mr33619745oef.60.1343216425334; Wed, 25 Jul 2012 04:40:25 -0700 (PDT)
Sender: yang.r.yang@gmail.com
Received: by 10.76.86.136 with HTTP; Wed, 25 Jul 2012 04:40:25 -0700 (PDT)
In-Reply-To: <7FA18E7BC523F04096632E46DA905D7A51DC1F9B@szxeml523-mbs.china.huawei.com>
References: <5003C514.70806@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC0EA7@szxeml523-mbs.china.huawei.com> <500956C6.6050809@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F08@szxeml523-mbs.china.huawei.com> <500D00C9.6070706@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F55@szxeml523-mbs.china.huawei.com> <500E7B90.9030902@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F7C@szxeml523-mbs.china.huawei.com> <500FA3BC.5040003@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F9B@szxeml523-mbs.china.huawei.com>
Date: Wed, 25 Jul 2012 19:40:25 +0800
X-Google-Sender-Auth: dPHaqctImxVbWd5ldbu-PKZ8LV0
Message-ID: <CANUuoLp47j8ekOQ37T04eLUTH_pRfyRNBHhUFJhXTBER40RHkA@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: Ravi nandiraju <ravi.nandiraju@huawei.com>
Content-Type: multipart/alternative; boundary=e89a8fb1ed3ce3770f04c5a5f1be
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WebSocket-based notifications
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, 25 Jul 2012 11:40:27 -0000

--e89a8fb1ed3ce3770f04c5a5f1be
Content-Type: text/plain; charset=ISO-8859-1

Hi Enrico, Ravi,

On Wednesday, July 25, 2012, Ravi nandiraju wrote:

>
>
> ________________________________________
> From: Enrico Marocco [enrico.marocco@telecomitalia.it <javascript:;>]
> Sent: Wednesday, July 25, 2012 1:13 PM
> To: Ravi nandiraju
> Cc: alto@ietf.org <javascript:;>
> Subject: Re: [alto] WebSocket-based notifications
>
> On 7/25/12 7:47 AM, Ravi nandiraju wrote:
> > I don't envisage ALTO clients like home devices using the
> > subscription mechanism because, for a home device client it is easier
> > to query the ALTO server for a changed map information rather than
> > going for a subscription.
>
>

> Just to be clear, here by "home device" you actually mean "user
> devices", i.e. any laptop, desktop, smartphone and whatnot that may for
> example run in a home network.
>
> [Ravi] Yes. What I meant by "home device" are the devices which are used
> by end users as P2P clients and which could potentially use ALTO as clients.
>
> > IMO, this subscription mechanism would be useful for infrastructure
> > cases like gateway devices, CDN, inter-DC etc where the problem of
> > reachability is not so complex as in the case of peer to peer.
>
> And useless in any environments where global reachability cannot be
> taken for granted. Agreed.
>
> [Ravi] Basically what I meant was, we don't need to consider the case of
>  "user devices" for subscription/notification because for them it is easier
> to query the information based on need rather than subscribing. I am not
> very clear if reachability is really a concern in the use case for ALTO
> subscription/notification.


Interesting perspective to focus on the desgn scenario. Ignoring
reachability for a moment and considering only overhead, since the number
of user devices will be large, the design of user-device-pull vs that of
server-push-to-user-device will be a trade off between bandwidth/throughput
vs server connection/open connection overheads. In this setting, I agree
that user-device-pull appears to be more preferred. On the other hand, if
we consider alto as a mechanism for network to update info to user devices
(e.g., end point properties, in a general context; i am even thinking of
network notify user device its last mile usage/quota/load properties), then
server-push-to-user-device can have benefits, such as low latency. What do
you think or this is too pushed?

Thanks!

Richard


>
> --
> Ciao,
> Enrico
> _______________________________________________
> alto mailing list
> alto@ietf.org <javascript:;>
> https://www.ietf.org/mailman/listinfo/alto
>

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

Hi Enrico, Ravi,<br><br>On Wednesday, July 25, 2012, Ravi nandiraju  wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><br>
<br>
________________________________________<br>
From: Enrico Marocco [<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cv=
ml&#39;, &#39;enrico.marocco@telecomitalia.it&#39;)">enrico.marocco@telecom=
italia.it</a>]<br>
Sent: Wednesday, July 25, 2012 1:13 PM<br>
To: Ravi nandiraju<br>
Cc: <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;alto=
@ietf.org&#39;)">alto@ietf.org</a><br>
Subject: Re: [alto] WebSocket-based notifications<br>
<br>
On 7/25/12 7:47 AM, Ravi nandiraju wrote:<br>
&gt; I don&#39;t envisage ALTO clients like home devices using the<br>
&gt; subscription mechanism because, for a home device client it is easier<=
br>
&gt; to query the ALTO server for a changed map information rather than<br>
&gt; going for a subscription.<br><br></blockquote><div>=A0</div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
Just to be clear, here by &quot;home device&quot; you actually mean &quot;u=
ser<br>
devices&quot;, i.e. any laptop, desktop, smartphone and whatnot that may fo=
r<br>
example run in a home network.<br>
<br>
[Ravi] Yes. What I meant by &quot;home device&quot; are the devices which a=
re used by end users as P2P clients and which could potentially use ALTO as=
 clients.<br>
<br>
&gt; IMO, this subscription mechanism would be useful for infrastructure<br=
>
&gt; cases like gateway devices, CDN, inter-DC etc where the problem of<br>
&gt; reachability is not so complex as in the case of peer to peer.<br>
<br>
And useless in any environments where global reachability cannot be<br>
taken for granted. Agreed.<br>
<br>
[Ravi] Basically what I meant was, we don&#39;t need to consider the case o=
f =A0&quot;user devices&quot; for subscription/notification because for the=
m it is easier to query the information based on need rather than subscribi=
ng. I am not very clear if reachability is really a concern in the use case=
 for ALTO subscription/notification.</blockquote>
<div><br></div><div>Interesting perspective to focus on the desgn scenario.=
 Ignoring reachability for a moment and considering only overhead, since th=
e number of user devices will be large, the design of user-device-pull vs t=
hat of server-push-to-user-device will be a trade off between bandwidth/thr=
oughput vs server connection/open connection overheads. In this setting, I =
agree that user-device-pull appears to be more preferred. On the other hand=
, if we consider alto as a mechanism for network to update info to user dev=
ices (e.g., end point properties, in a general context; i am even thinking =
of network notify user device its last mile usage/quota/load properties), t=
hen server-push-to-user-device can have benefits, such as low latency. What=
 do you think or this is too pushed?</div>
<div><br></div><div>Thanks!</div><div><br></div><span></span><div>Richard</=
div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
--<br>
Ciao,<br>
Enrico<br>
_______________________________________________<br>
alto mailing list<br>
<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;alto@iet=
f.org&#39;)">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
</blockquote>

--e89a8fb1ed3ce3770f04c5a5f1be--

From tnadeau@juniper.net  Thu Jul 26 11:06:43 2012
Return-Path: <tnadeau@juniper.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 9447E21F85F7; Thu, 26 Jul 2012 11:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.309
X-Spam-Level: 
X-Spam-Status: No, score=-6.309 tagged_above=-999 required=5 tests=[AWL=0.290,  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 B1Kqd6m-KCHI; Thu, 26 Jul 2012 11:06:42 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id B5BB721F861E; Thu, 26 Jul 2012 11:06:34 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKUBGHJN+nS851zOdeAP4iS+xW/auReO3Y@postini.com; Thu, 26 Jul 2012 11:06:41 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 26 Jul 2012 11:05:20 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Thu, 26 Jul 2012 14:05:19 -0400
From: Thomas Nadeau <tnadeau@juniper.net>
To: "mpls@ietf.org" <mpls@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "alto@ietf.org" <alto@ietf.org>
Date: Thu, 26 Jul 2012 14:05:18 -0400
Thread-Topic: Interface to the Internet Routing System (IRS) Discussion List Created
Thread-Index: Ac1rWTdkMa/o1HJvQ46cDHHzjaMH4g==
Message-ID: <CC36FF1E.2727%tnadeau@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "wardd@cisco.com" <wardd@cisco.com>, Alia Atlas <akatlas@juniper.net>
Subject: [alto] Interface to the Internet Routing System (IRS) Discussion List Created
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, 26 Jul 2012 18:06:43 -0000

We have created a non-WG mailing list to discuss IRS.

The purpose of the list:

This list is for the discussion of an interface to the routing system (IRS)=
 that allows applications to rapidly and dynamically install routing state =
into routers, and to learn sufficient information from routers to make time=
ly, data-based decisions about what routing state to specify. Such an inter=
face would facilitate control and diagnosis of the routing infrastructure, =
as well as enabling sophisticated applications to be built on top of today'=
s routed networks.  The IRS is conceived as a programmatic, streaming inter=
face for transferring state into and out of the Internet's routing system, =
recognizing that the routing system and a router's OS provide useful mechan=
isms that applications could harness to accomplish application-level goals.=
  A fundamental component of the IRS is a clear data model that defines the=
 semantics of the information that can be written and read.
An initial framework document for IRS is available here:

http://www.lucidvision.com/draft-ward-irs-framework-00.txt

To subscribe, please visit the following:

https://www.ietf.org/mailman/listinfo/irs-discuss




From sreekanth.madhavan@huawei.com  Thu Jul 26 22:00:45 2012
Return-Path: <sreekanth.madhavan@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 18A0A21F854F for <alto@ietfa.amsl.com>; Thu, 26 Jul 2012 22:00:45 -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 zuh2C+vm9WYz for <alto@ietfa.amsl.com>; Thu, 26 Jul 2012 22:00:44 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id C314221F853F for <alto@ietf.org>; Thu, 26 Jul 2012 22:00:43 -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 AIC73668; Fri, 27 Jul 2012 01:00:41 -0400 (EDT)
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 26 Jul 2012 21:58:15 -0700
Received: from SZXEML412-HUB.china.huawei.com (10.82.67.91) by dfweml405-hub.china.huawei.com (10.193.5.102) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 26 Jul 2012 21:57:58 -0700
Received: from blrprnc03ns (10.18.96.92) by szxeml412-hub.china.huawei.com (10.82.67.91) with Microsoft SMTP Server id 14.1.323.3; Fri, 27 Jul 2012 12:57:55 +0800
From: sreekanth madhavan <sreekanthm@huawei.com>
To: "'Schwan, Nico (Nico)'" <nico.schwan@alcatel-lucent.com>, "'Roome, W D'" <w.roome@alcatel-lucent.com>
References: <E45D69B5D95C074A90D71F60F6A18EF0891BB53FF8@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
In-Reply-To: <E45D69B5D95C074A90D71F60F6A18EF0891BB53FF8@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
Date: Fri, 27 Jul 2012 10:27:54 +0530
Message-ID: <002c01cd6bb4$62a8b000$27fa1000$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac1jU9pnb89QN6W3SHWam0gr2KsTRQIYAJUQ
Content-Language: en-us
X-Originating-IP: [10.18.96.92]
X-CFilter-Loop: Reflected
Cc: alto@ietf.org
Subject: Re: [alto] New version: draft-schwan-alto-incr-updates-02.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: Fri, 27 Jul 2012 05:00:45 -0000

Hi,

I have reviewed the draft. Following are my comments: 

Section 3.1.  HTTP 

   HTTP [RFC2616] provides request-header fields to express conditional 
   requests.  Typically these conditional requests are used by caches to 
   decide whether a copy of a resource they have can be served to a 
   requesting client directly or not.  Responses to conditional HTTP 
   requests must be exactly the same as for normal HTTP GET requests. 
   Thus sending a modified map version (i.e. a partial update) violates 
   the HTTP standard.  Conditional requests can still be used to avoid 
   transmitting an unchanged Map multiple times.  The options are 
   discussed in the following. 
    
[sreekanth]: RFC 3229 defines how delta encoding can be supported as an
compatible 
extension to HTTP/1.1. Can't we use the same framework for alto incremental
updates ? 


Section 3.1.1: If-Modified-Since HTTP Header 

[sreekanth]: This timestamp-based approach is prone to error because of the
lack 
   of timestamp resolution: if a resource changes twice during one second, 
   the change might not be detectable. It is better to use the ETag.


IMO notification based cache invalidation mechanism can be added as an
alternate approach.

Regards,
Sreekanth 


-----Original Message-----
From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of
Schwan, Nico (Nico)
Sent: Monday, July 16, 2012 6:37 PM
To: alto@ietf.org
Cc: Roome, W D
Subject: [alto] New version: draft-schwan-alto-incr-updates-02.txt

All,

we have submitted an updated version of the "ALTO Incremental Updates" draft
which analyses options for partial updates of ALTO Network and Cost Maps. In
this version we have further detailed the solution which is based on
Filtered Map Services. As suggested in the last meeting we have also
included a short numerical evaluation of the most promising options in the
draft. Our main findings are that for more than 100 PIDs partial updates are
useful, and that the solution based on Filtered Maps is more efficient than
JSON Patch in terms of needed bytes for encoding.

Any comments on the discussed options, the numbers, or anything else are
welcome!

Thanks,

Nico


--------------

A new version of I-D, draft-schwan-alto-incr-updates-02.txt
has been successfully submitted by Nico Schwan and posted to the IETF
repository.

Filename:	 draft-schwan-alto-incr-updates
Revision:	 02
Title:		 ALTO Incremental Updates
Creation date:	 2012-07-16
WG ID:		 Individual Submission
Number of pages: 26
URL:
http://www.ietf.org/internet-drafts/draft-schwan-alto-incr-updates-02.txt
Status:
http://datatracker.ietf.org/doc/draft-schwan-alto-incr-updates
Htmlized:
http://tools.ietf.org/html/draft-schwan-alto-incr-updates-02
Diff:
http://tools.ietf.org/rfcdiff?url2=draft-schwan-alto-incr-updates-02

Abstract:
   The goal of Application-Layer Traffic Optimization (ALTO) is to
   bridge the gap between network and applications by provisioning
   network related information.  This allows applications to make
   informed decisions, for example when selecting a target host from a
   set of candidates.

   Therefore an ALTO server provides network and cost maps to its
   clients.  This draft discusses options on how to provide incremental
   updates for these maps, with the goal of reducing the amount of data
   needed for transmitting the maps and shortly evaluates the two most
   promising options.



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


From diego@tid.es  Fri Jul 27 04:01:08 2012
Return-Path: <diego@tid.es>
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 9441421F8629; Fri, 27 Jul 2012 04:01:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.245
X-Spam-Level: 
X-Spam-Status: No, score=-6.245 tagged_above=-999 required=5 tests=[AWL=0.354,  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 3lmyU6XeuHgq; Fri, 27 Jul 2012 04:01:07 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 5601C21F8616; Fri, 27 Jul 2012 04:01:06 -0700 (PDT)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M7T00FZOFXAS6@tid.hi.inet>; Fri, 27 Jul 2012 13:01:05 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id B9.B5.02752.1F472105; Fri, 27 Jul 2012 13:01:05 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0M7T00CK8FXTTL@tid.hi.inet>; Fri, 27 Jul 2012 13:01:05 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([fe80::a90d:2f68:6fb8:5c75]) by ex10-htcas3-mad.hi.inet ([::1]) with mapi id 14.02.0298.004; Fri, 27 Jul 2012 13:01:05 +0200
Date: Fri, 27 Jul 2012 11:01:04 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <4FF71A79.9090401@huawei.com>
X-Originating-IP: [10.95.64.115]
To: Haiyong Xie <haiyong.xie@huawei.com>, "Y. Richard Yang" <yry@cs.yale.edu>
Message-id: <3A03EB9D-6ED0-4D75-9696-A6B3CA612564@tid.es>
Content-id: <C1C2B1C3D6FDF940A704E07647C13258@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US
Thread-topic: [alto] New Version Notification for draft-xie-alto-sdn-extension-use-cases-00.txt
Thread-index: AQHNa+cdHMaCNh1KlUS4hLI6mOBs5g==
X-AuditID: 0a5f4e69-b7f6d6d000000ac0-e4-501274f1e93d
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrEKsWRmVeSWpSXmKPExsXCFe9nqPuxRCjA4NkqLYuH2/eyWtyaPInd gcljyZKfTAGMUVw2Kak5mWWpRfp2CVwZjRPPsRVs5q+YdrKNrYFxN08XIyeHhICJxPRtR5gh bDGJC/fWs3UxcnEICWxnlHj2ew0rhPOMUaLz1HZ2CGcpo8TK9YuAHA4OFgFVievnAkG62YDM R82/2UFsYYEEifa3n9lASjgFtCRerJWCWKAg8efcYxYQW0TAV2LG/EtMICOZBU4zSrxd8wqs l1fAUuLK43ZGEJtZwEziwvRLLBBxQYkfk++xQMR1JHq/f2OGsMUlmltvQsW1JZ68u8AKYjMC ffP91BomkBtEBBIlGh/GQ+zVk3hw6Bk7xD0CEkv2nId6XlTi5eN/UP9eZZR43NzAPIFRYhaS M2YhOWMWkjNmITljFpIzFjCyrmIUK04qykzPKMlNzMxJNzDSy8jUy8xLLdnECInAzB2My3eq HGIU4GBU4uHV2CQYIMSaWFZcmXuIUZKDSUmU91OxUIAQX1J+SmVGYnFGfFFpTmrxIUYJDmYl Ed6vtkA53pTEyqrUonyYlAwHh5IE7xOQNsGi1PTUirTMHGCagUkzcXCCtPMAtR8EqeEtLkjM Lc5Mh8ifYpSUEuc9CpIQAElklObB9b5iFAc6Upj3IkiWB5gQ4bpeAQ1kAhpoEQ02sCQRISXV wOg0W2xW/+HCdrvoAibvmws/yPbabz0b/oxN8ZW4ltWnosh1a3U91X2+6/Kpsky8kLfr8Mbk 0/u1bsQtVng2T1tIJrB+1dsptqE/6490L1aL9d28I9Hvzx+7nfOCKgTFJpTEed3Ls1A47aL/ 6Ns1j8oPTu4dFrFHFyTkbcmMuJcjfH+nNJ+EkxJLcUaioRZzUXEiAFIwNXBFAwAA
References: <748A482AA35F7A4A8BD26465029B8C4A1B7C49EC@dfweml509-mbx.china.huawei.com> <4FF11869.1010408@cs.yale.edu> <4FF1DF7B.9080500@huawei.com> <4FF41835.5020002@cs.yale.edu> <4FF71A79.9090401@huawei.com>
Cc: "altoext@ietf.org" <altoext@ietf.org>, Hongtao Yin <hongtao.yin@huawei.com>, "alto@ietf.org" <alto@ietf.org>, Andreas Voellmy <andreas.voellmy@yale.edu>
Subject: Re: [alto] New Version Notification for draft-xie-alto-sdn-extension-use-cases-00.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: Fri, 27 Jul 2012 11:01:08 -0000

Hi,

Now that I have had time to re-read this thread and go through the document=
s,
the comments and the slides we are preparing for our next meeting in
Vancouver, I have come to a couple of conclusions I want to share with you.

The first of all is that we'd probably have to change the title. Both
the contents and the discussions around are more related to architecture
than to anything else. What if we change it into something like "Architectu=
re
for ALTO and SDN interoperation"

The second is related to the conditions for "network partition" (that I
prefer to call "subnetwork interconnection" or "federation", if you like)
in the H architecture. Hayiyong put two conditions:

On 6 Jul 2012, at 19:03 , Haiyong Xie wrote:
> H could allow network partition provided that the following two
> conditions are satisfied:
> (1) m SCs can form a mesh/peering to work together
> (2) m ALTO servers could work jointly (e.g., by forming mesh/peering
> among themselves).

And somehow implies they are both necessary. I think federation could be
achieved as long as just one of them is provided. In the first case, each
AS would learn data from the integrated view of its corresponding SC. In
the second case, SCs would know about other domains through what their
associated ASes have received.

Be goode,

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: diego@tid.es
Tel:    +34 913 129 041
Mobile: +34 682 051 091
-----------------------------------------


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

From nico.schwan@alcatel-lucent.com  Fri Jul 27 04:59:29 2012
Return-Path: <nico.schwan@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 ECB9221F8655 for <alto@ietfa.amsl.com>; Fri, 27 Jul 2012 04:59:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[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 DkcHA6HmGnVI for <alto@ietfa.amsl.com>; Fri, 27 Jul 2012 04:59:29 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 1413121F861B for <alto@ietf.org>; Fri, 27 Jul 2012 04:59:28 -0700 (PDT)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q6RBwqMs006873 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 27 Jul 2012 13:59:22 +0200
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.55]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Fri, 27 Jul 2012 13:59:18 +0200
From: "Schwan, Nico (Nico)" <nico.schwan@alcatel-lucent.com>
To: sreekanth madhavan <sreekanthm@huawei.com>, "Roome, W D" <w.roome@alcatel-lucent.com>
Date: Fri, 27 Jul 2012 13:59:17 +0200
Thread-Topic: [alto] New version: draft-schwan-alto-incr-updates-02.txt
Thread-Index: Ac1jU9pnb89QN6W3SHWam0gr2KsTRQIYAJUQAA1AoRA=
Message-ID: <E45D69B5D95C074A90D71F60F6A18EF0891BB54122@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
References: <E45D69B5D95C074A90D71F60F6A18EF0891BB53FF8@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com> <002c01cd6bb4$62a8b000$27fa1000$@com>
In-Reply-To: <002c01cd6bb4$62a8b000$27fa1000$@com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] New version: draft-schwan-alto-incr-updates-02.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: Fri, 27 Jul 2012 11:59:30 -0000

Sreekanth,

thanks for your comments!
=20
> I have reviewed the draft. Following are my comments:
>=20
> Section 3.1.  HTTP
>=20
>    HTTP [RFC2616] provides request-header fields to express conditional
>    requests.  Typically these conditional requests are used by caches
> to
>    decide whether a copy of a resource they have can be served to a
>    requesting client directly or not.  Responses to conditional HTTP
>    requests must be exactly the same as for normal HTTP GET requests.
>    Thus sending a modified map version (i.e. a partial update) violates
>    the HTTP standard.  Conditional requests can still be used to avoid
>    transmitting an unchanged Map multiple times.  The options are
>    discussed in the following.
>=20
> [sreekanth]: RFC 3229 defines how delta encoding can be supported as an
> compatible extension to HTTP/1.1. Can't we use the same framework for
> alto incremental updates ?
>=20
Thanks for the pointer. This is certainly something we need to consider. Af=
ter a quick search I don't have the impression that HTTP delta encoding is =
currently widely used. Do you or anyone else have an idea to what extend th=
is is actually supported in today's implementations?

>=20
> Section 3.1.1: If-Modified-Since HTTP Header
>=20
> [sreekanth]: This timestamp-based approach is prone to error because of
> the
> lack
>    of timestamp resolution: if a resource changes twice during one
> second,
>    the change might not be detectable. It is better to use the ETag.
One main assumption for the ALTO map-based approach is that the information=
 provided in these maps is static for a longer period of time, thus changes=
 on sub-second timeframe seem unlikely. I see your point though.

Regards,

Nico


>=20
>=20
> IMO notification based cache invalidation mechanism can be added as an
> alternate approach.
>=20
> Regards,
> Sreekanth
>=20
>=20
> -----Original Message-----
> From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of
> Schwan, Nico (Nico)
> Sent: Monday, July 16, 2012 6:37 PM
> To: alto@ietf.org
> Cc: Roome, W D
> Subject: [alto] New version: draft-schwan-alto-incr-updates-02.txt
>=20
> All,
>=20
> we have submitted an updated version of the "ALTO Incremental Updates"
> draft
> which analyses options for partial updates of ALTO Network and Cost
> Maps. In
> this version we have further detailed the solution which is based on
> Filtered Map Services. As suggested in the last meeting we have also
> included a short numerical evaluation of the most promising options in
> the
> draft. Our main findings are that for more than 100 PIDs partial
> updates are
> useful, and that the solution based on Filtered Maps is more efficient
> than
> JSON Patch in terms of needed bytes for encoding.
>=20
> Any comments on the discussed options, the numbers, or anything else
> are
> welcome!
>=20
> Thanks,
>=20
> Nico
>=20
>=20
> --------------
>=20
> A new version of I-D, draft-schwan-alto-incr-updates-02.txt
> has been successfully submitted by Nico Schwan and posted to the IETF
> repository.
>=20
> Filename:	 draft-schwan-alto-incr-updates
> Revision:	 02
> Title:		 ALTO Incremental Updates
> Creation date:	 2012-07-16
> WG ID:		 Individual Submission
> Number of pages: 26
> URL:
> http://www.ietf.org/internet-drafts/draft-schwan-alto-incr-updates-
> 02.txt
> Status:
> http://datatracker.ietf.org/doc/draft-schwan-alto-incr-updates
> Htmlized:
> http://tools.ietf.org/html/draft-schwan-alto-incr-updates-02
> Diff:
> http://tools.ietf.org/rfcdiff?url2=3Ddraft-schwan-alto-incr-updates-02
>=20
> Abstract:
>    The goal of Application-Layer Traffic Optimization (ALTO) is to
>    bridge the gap between network and applications by provisioning
>    network related information.  This allows applications to make
>    informed decisions, for example when selecting a target host from a
>    set of candidates.
>=20
>    Therefore an ALTO server provides network and cost maps to its
>    clients.  This draft discusses options on how to provide incremental
>    updates for these maps, with the goal of reducing the amount of data
>    needed for transmitting the maps and shortly evaluates the two most
>    promising options.
>=20
>=20
>=20
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto


From diego@tid.es  Sun Jul 29 16:43:08 2012
Return-Path: <diego@tid.es>
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 B0B3F21F84AF for <alto@ietfa.amsl.com>; Sun, 29 Jul 2012 16:43:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.054
X-Spam-Level: 
X-Spam-Status: No, score=-5.054 tagged_above=-999 required=5 tests=[AWL=-0.869, BAYES_40=-0.185, 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 JfpqfMt4FqSU for <alto@ietfa.amsl.com>; Sun, 29 Jul 2012 16:43:07 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 4C92E21F84A6 for <alto@ietf.org>; Sun, 29 Jul 2012 16:43:07 -0700 (PDT)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M7Y003UN4JU4V@tid.hi.inet> for alto@ietf.org; Mon, 30 Jul 2012 01:43:06 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 00.3E.02752.A8AC5105; Mon, 30 Jul 2012 01:43:06 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0M7Y003UH4JT4V@tid.hi.inet> for alto@ietf.org; Mon, 30 Jul 2012 01:43:05 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([fe80::a90d:2f68:6fb8:5c75]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0298.004; Mon, 30 Jul 2012 01:43:02 +0200
Date: Sun, 29 Jul 2012 23:43:04 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <CANUuoLp47j8ekOQ37T04eLUTH_pRfyRNBHhUFJhXTBER40RHkA@mail.gmail.com>
X-Originating-IP: [10.95.64.115]
To: Enrico Marocco <enrico.marocco@telecomitalia.it>, "Y. Richard Yang" <yry@cs.yale.edu>, Ravi nandiraju <ravi.nandiraju@huawei.com>
Message-id: <D209E532-B82C-4D5A-A92F-11936B6F58C9@tid.es>
Content-id: <E9646B8F9281BF4DB472F64CF766294F@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US
Thread-topic: [alto] WebSocket-based notifications
Thread-index: AQHNYyYan87dYnznSkGoYMAsxNBUvZcx+vIAgAAM6wCABFMDgIAACy+AgAG3lQCAAAv1AIABQHMAgAAgnQCAAA+VAIAAMn6AgAa+qwA=
X-AuditID: 0a5f4e69-b7f6d6d000000ac0-e5-5015ca8a5c8d
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrNKsWRmVeSWpSXmKPExsXCFe9nqNt1SjTAoO0Ih8XD7XtZHRg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVMfvrRJaCq5wVSw+/Y2tg/MbexcjBISFgIjFzT2EXIyeQKSZx 4d56ti5GLg4hge2MEkfO3WKFcH4wSjycN5UFpEpIYCmjxOUeKxCbRUBV4tzOx8wgNhuQ/aj5 NzuILSxgKDFt8yYmkAWcAsESs6emQCxQkPhz7jELyEwRgXZGiSm/OsHqmQWUJc6tuMkKYvMK WEo8O3GDEaSXWcBM4uznaoiwoMSPyfdYIMp1JHq/f2OGsMUlmltvQsW1JZ68uwA2hhHome+n 1jCB2CICRhL/treyQdgVErtXHGKEuEdAYsme88wQtqjEy8f/oP7tYJU43fuAdQKjxCyEM2Yh OWMWkjNmITljFpIzFjCyrmIUK04qykzPKMlNzMxJNzDSy8jUy8xLLdnECIm5zB2My3eqHGIU 4GBU4uHV2CQYIMSaWFZcmXuIUZKDSUmUV/iwaIAQX1J+SmVGYnFGfFFpTmrxIUYJDmYlEd5H sUA53pTEyqrUonyYlAwHh5IE7/aTQCnBotT01Iq0zBxgYoFJM3FwgrTzALVrgtTwFhck5hZn pkPkTzFKSonzngNJCIAkMkrz4HpfMYoDHSnM2wiS5QGmQLiuV0ADmYAGWkQLgQwsSURISTUw HtGa/vlXXdJSjYbOGVI2MZ+VI/h05TO2L5h/tTDkasbBCqllu78n8+fzFenLcPfGpJXmcYjP eLXsYtO6o3Mmlc1aU7xff11zstN0A1WeGw8l5TIq1UMXcRuHfOtqObHox5PVk6yCJ8m+PJ/q om5z/Hzgg9qnz17qaX4983LS9S3Kk6JCUmtPKLEUZyQaajEXFScCAK/YPlQ+AwAA
References: <5003C514.70806@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC0EA7@szxeml523-mbs.china.huawei.com> <500956C6.6050809@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F08@szxeml523-mbs.china.huawei.com> <500D00C9.6070706@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F55@szxeml523-mbs.china.huawei.com> <500E7B90.9030902@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F7C@szxeml523-mbs.china.huawei.com> <500FA3BC.5040003@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F9B@szxeml523-mbs.china.huawei.com> <CANUuoLp47j8ekOQ37T04eLUTH_pRfyRNBHhUFJhXTBER40RHkA@mail.gmail.com>
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WebSocket-based notifications
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, 29 Jul 2012 23:43:08 -0000

Hi,

Just to add another bit of confusion...

When reading this thread I was wondering whether a solution based on
bi-directional data streams, that would keep one single connection per
client-server association while allowing for different resources to be
queried and updated, could be considered.

What I have in mind is the use of XMPP for bi-directional ALTO
interactions. Apart from the features outlined in the paragraph above, it
does fit well with ALTO encoding and operational semantics, and
there is a well established corpus of (many of them open) implementations.

Be goode,

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: diego@tid.es
Tel:    +34 913 129 041
Mobile: +34 682 051 091
-----------------------------------------


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

From richard.alimi@gmail.com  Sun Jul 29 23:43:37 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 042C711E813F for <alto@ietfa.amsl.com>; Sun, 29 Jul 2012 23:43:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.74
X-Spam-Level: 
X-Spam-Status: No, score=-2.74 tagged_above=-999 required=5 tests=[AWL=0.237,  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 0wmaNzzbxEVW for <alto@ietfa.amsl.com>; Sun, 29 Jul 2012 23:43:35 -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 A4A3211E8132 for <alto@ietf.org>; Sun, 29 Jul 2012 23:43:35 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so4809988ggn.31 for <alto@ietf.org>; Sun, 29 Jul 2012 23:43:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=yd0IZUgk2Ay0SQLd1X+9ZDJq7tbbQa0f3bZ2zZz284M=; b=e9Pb0iNJdZW208TLeHjc6F2siwZYGOpLkTjKNh+WC45TuUvwogJFc5GfFfW18QF4Ty Qx+MqLfNqRWKbw/2hzn3TGo4rMDW4hLPb5INi9AF5x/2ygP/XL8W7FYAljJv2P+W9I4u eR/RU465n49HYG+jf7NYnnPnTczhqY3gksvAZgNiC2ODMGPBsdPoeF7qfl2VyCm7wnwN buVtipQ5+kezKj0e+J7iejLZhB5fi9CH2WTgL+4s3HH16/esyTtwUJojsK7E5CWUZci4 eLFh7ldIYt/wmAWA9MgWihGs/hDFCq7eYr8ia1SO3OkTrXGq+I65Aoa+eg3NQe/Okpxb 7DDg==
Received: by 10.50.196.232 with SMTP id ip8mr7533440igc.50.1343630612428; Sun, 29 Jul 2012 23:43:32 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.43.119.67 with HTTP; Sun, 29 Jul 2012 23:43:12 -0700 (PDT)
From: Richard Alimi <rich@velvetsea.net>
Date: Sun, 29 Jul 2012 23:43:12 -0700
X-Google-Sender-Auth: tHwrAlJjo1cQBpjUJv6f2P804gY
Message-ID: <CA+cvDaZZ7ow7QWMjmGkLs0E7c0PK2KjPApVtr_z4qQTOyBTwpQ@mail.gmail.com>
To: alto@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [alto] ALTO Operations and Management
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, 30 Jul 2012 06:43:37 -0000

Hi All,

As you probably know, one of the new requirements on the protocol is:
   An ALTO client protocol MUST provide adequate
   mechanisms for operations and management support, as outlined in RFC
   5706 [RFC5706].

The points raised by RFC5706 are very good and should indeed be
solved. What I'm missing currently is a clear picture of exactly what
this requirement dictates for draft-ietf-alto-protocol.  In
particular, the scope of RFC5706 is *huge* - to address every
suggested point fully would take another couple of years (e.g.,
specify a management API for ALTO Servers, a configuration language,
techniques for verifying end-to-end operation, etc).

I'll suggest a way forwards - please provide feedback if you have a
chance.  I'd really like to get something mostly complete by the end
of IETF week if possible.

Proposal:

If we separate Operations (RFC5706, Section 2) from Management
(RFC5706, Section 3), I can make the following general observation:
- Operations: the protocol draft seems like a fine place to document
these, with the exception of 2.6 ("Verifying Correct Operation") which
is covered in Section 6.3 of draft-ietf-alto-deployments-04
- Management: draft-ietf-alto-deployments seems to already cover some
of this, and could probably be expanded to cover the rest (well, the
rest that we intend to solve) to keep the related information
together.  That seems preferable than copying a bunch of content from
draft-ietf-alto-deployments into draft-ietf-alto-protocol when we had
intentionally kept them separate in the first place.  The exception to
this might be dictating which protocols to use for some functions that
we know would be needed (syslog, IPFIX), which seem fine to have in
draft-ietf-alto-protocol.

Thoughts on that?  The intent isn't to just punt this over to another
draft, but rather to avoid duplicating text between different
documents and finish the protocol draft in a reasonable amount of
time.

If that *does* sound reasonable, I can write up some more concrete
text for the Operations section with a pointer indicating that
Management considerations are being documented in
draft-ietf-alto-deployments (seems like an Informative reference, so
that should be fine?)

If that *doesn't* sound reasonable, I'd really like to hear from
people what should be documented in the ALTO Protocol draft itself to
support Operations and Management.  Below my signature, I've included
some quick notes below about what I think *could* be discussed for
most of the points raised by RFC5706.  I don't think the authors of
the new requirement envisioned all of that to be included in
draft-ietf-alto-protocol, but I'd need some help in defining where to
draw the line.

Thanks,
Rich

-- Operations --

(1) Installation and Initial Setup
- By default an ALTO Server may be configured with a single PID
containing all IPv4/IPv6 addresses and a Cost Map with no entries.
Something more interesting should be configured explicitly (either
dynamically or statically).
- Specifications for underlying protocols (e.g., TCP, HTTP) should be
consulted for their available settings/defaults.

(2) Migration Path
- No migration path for ALTO Servers since there is no previous
protocol providing same functionality.
- Client-side: Applications making use of other data sources for
network information should consider ALTO an additional source of
information, but ALTO need not be the sole source of network
information.

(3) Requirements on Other Protocols and Functional Components
- Protocol-wise, ALTO assumes standard HTTP and JSON implementations exist.
- Functional-wise: An ALTO Server assumes that it can gather
sufficient information to populate Network and Cost maps.  "Sufficient
information" is dependent on the information being exposed, but likely
includes information such as IGP and EGP RIBs (more details in Section
2.2 of draft-ietf-alto-protocol-12).  Specific mechanisms have been
suggested in the past as extensions (e.g.,
draft-medved-alto-svr-apis-00).

(4) Impact on Network Operation
- Operators should consider impacts on (or integration with) Traffic
Engineering, since ALTO may shift traffic patterns.
- Privacy considerations for ISPs (see 10.1 of draft-ietf-alto-protocol-12)
- Impact of incorrect/faked guidance (see 10.3 of
draft-ietf-alto-deployments-04)

(5) Verifying Correct Operation
- For ALTO-specific monitoring and metrics, see 6.3 of
draft-ietf-alto-deployments-04

-- Management --

(1) Interoperability
- A common management API would be desirable given that ALTO Servers
may typically be configured with dynamic data from various sources,
and ALTO Servers are intended to scale horizontally for
fault-tolerance and reliability
  - management protocol should operate semantically at the level of
ALTO maps or other exposed information
- Entities that compute dynamic maps/guidance and entities that
measure ALTO's effects should use IPFIX information elements
- ALTO Servers should use syslog to log events.

(2) Management Information
- Informational Model
  - Data Sources - the set of data sources made available to an ALTO Server
  - Information Resource Directory - the set of ALTO Information
exposed by an ALTO Server
  - Section 4 and 5 of draft-ietf-alto-protocol-12 describe Network
Map, PIDs and Cost Maps, which are central entities of the
informational model.
  - ALTO guidance: ALTO Server may use internal logic/algorithms to
generate responses to ALTO Clients (map and endpoint-based queries);
may be customized to a particular deployment environment, so not
standardized (as long as responses follow protocol spec). May use
Network Map and Cost Map to answer queries, or may use custom logic.

(3) Fault Management
- To be discussed in 6.3 of draft-ietf-alto-deployments

(4) Configuration Management
- ALTO Server requires at least the following (high-level) logical inputs:
  - Data Sources (raw network , or explicitly-provided ALTO-level
information such as a Network Map and Cost Map)
  - Security policies
- Configuration interface should use ALTO data structures (as
specified in the ALTO Protocol itself) wherever possible to configure
the ALTO information exposed by an ALTO Server.  Specific syntax may
differ if porting to a language that is not JSON, but structures
should remain consistent.
- Specify standard configuration language and interface for interoperability
- Multiple ALTO Servers my be deployed for horizontal scalability. A
centralized configuration database may be used to ensure they are
providing the desired ALTO information with appropriate security
controls.  The ALTO information (e.g., Network Maps and Cost Maps)
being served by each ALTO Server, as well as security policies (HTTP
authentication, SSL/TLS client/server authentication, SSL/TLS
encryption parameters) intended to serve the same information should
be monitored for consistency.
- Verifying Correct Operation: Discussed in 6.3 of
draft-ietf-alto-deployments (and future revisions)

(5) Accounting Management
- Discussed in 6.3 of draft-ietf-alto-deployments (and future revisions)

(6) Performance Management
- List interesting counters
  - e.g., Number of requests for each service, responses, bytes
in/out, CPU utilization, ALTO map/guidance updates, number of PIDs,
map sizes (bytes, number of entries), etc
- Interesting data accessible by IPFIX
  - e.g., bytes per src/dst IP
- network devices
  - link utilization

(7) Security Management
- Readers should refer to documentation on HTTP and SSL/TLS.
- ALTO Servers will typically receive a large number of requests.
Intrusion Detection Systems that can separate malicious attacks from
noise are suggested when generating alerts.


Thanks,
Rich

From vkg@bell-labs.com  Mon Jul 30 10:23:47 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 66EB311E8143 for <alto@ietfa.amsl.com>; Mon, 30 Jul 2012 10:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.599
X-Spam-Level: 
X-Spam-Status: No, score=-108.599 tagged_above=-999 required=5 tests=[AWL=-2.000, 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 nErB83aj5s61 for <alto@ietfa.amsl.com>; Mon, 30 Jul 2012 10:23:46 -0700 (PDT)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 7177511E812F for <alto@ietf.org>; Mon, 30 Jul 2012 10:23:46 -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 q6UHNjOY022776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Mon, 30 Jul 2012 12:23:45 -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 q6UHNjPG010837 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Mon, 30 Jul 2012 12:23:45 -0500
Received: from shoonya.ih.lucent.com (vkg.lra.lucent.com [135.244.41.9]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q6UHNhAp006317 for <alto@ietf.org>; Mon, 30 Jul 2012 12:23:45 -0500 (CDT)
Message-ID: <5016C320.9020208@bell-labs.com>
Date: Mon, 30 Jul 2012 12:23:44 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120605 Thunderbird/13.0
MIME-Version: 1.0
To: alto <alto@ietf.org>
References: <20120730032233.17770.35790.idtracker@ietfa.amsl.com>
In-Reply-To: <20120730032233.17770.35790.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20120730032233.17770.35790.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; 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
Subject: [alto] Fwd: Need volunteers for the NomCom
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, 30 Jul 2012 17:23:47 -0000

Folks: NomCom is still looking for volunteers.  Please do consider
volunteering.

Thanks,

-------- Original Message --------
Subject: Need volunteers for the NomCom
Date: Sun, 29 Jul 2012 20:22:33 -0700
From: NomCom Chair <nomcom-chair@ietf.org>
To: Working Group Chairs <wgchairs@ietf.org>

We are currently looking for volunteers to serve on the 2012-2013 NomCom.
As you know, the success of the NomCom process depends crucially on
having a large pool of volunteers from throughout the IETF community.
In particular, it is valuable for the pool of volunteers to have strong
representation from all of the technical areas within the IETF.

I understand that not all IETF participants read the IETF announce list
frequently. Therefore, if you would be willing to inform active 
participants
in your working groups about this year's call for NomCom volunteers, I
would greatly appreciate it.

The NomCom 2012-2013 Call for Volunteers is open until this Sunday,
August 5. Details can be found at: 
https://datatracker.ietf.org/ann/nomcom/49851/

Thank you for your help,
- Matt Lepinski
   mlepinski.ietf@gmail.com
   nomcom-chair@ietf.org

- 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 sabine.randriamasy@alcatel-lucent.com  Mon Jul 30 10:37:06 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 76DF211E80AE for <alto@ietfa.amsl.com>; Mon, 30 Jul 2012 10:37:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.674
X-Spam-Level: 
X-Spam-Status: No, score=-9.674 tagged_above=-999 required=5 tests=[AWL=0.575,  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 OVqY26q-A7NV for <alto@ietfa.amsl.com>; Mon, 30 Jul 2012 10:37:05 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id 9382311E808E for <alto@ietf.org>; Mon, 30 Jul 2012 10:37:05 -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 q6UHb2X5032179 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 30 Jul 2012 19:37:02 +0200
Received: from [172.27.204.117] (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; Mon, 30 Jul 2012 19:37:02 +0200
Message-ID: <5016C638.10203@alcatel-lucent.com>
Date: Mon, 30 Jul 2012 19:36:56 +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: <20120711171608.16399.10488.idtracker@ietfa.amsl.com> <CA+cvDabW17VfVF4w+u0FkvFAF9v0zuzPw1DOP+proBouOCKzJg@mail.gmail.com>
In-Reply-To: <CA+cvDabW17VfVF4w+u0FkvFAF9v0zuzPw1DOP+proBouOCKzJg@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; 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] I-D Action: draft-ietf-alto-protocol-12.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, 30 Jul 2012 17:37:06 -0000

Hi Rich,

I just came across one point regarding constraints in input parameters 
in POST requests for the Filtered Cost map and Endpoint Cost Services.

In Section 6.8.2.2.3 Input Parameters (for filtered cost map), object 
ReqFilteredCostMap has a member
'JSONString constraints<0..*>'

In Section 6.8.4.1.3 Input Parameters, object ReqEndpointCostMap has a 
member 'JSONString constraints' and
refers to §6.8.2.2  for the description.
Is there an objection to also have 'JSONString constraints<0..*>' for 
the EP cost service as having several constraints on a cost type may 
also be needed in the ECS ?

Thanks
Sabine


Richard Alimi a écrit :
> I believe this should address all of the WGLC comments received, with
> the exception of handling the operations and management requirements.
> Those are underway; I posted a new version now to give folks more time
> to ensure that the WGLC comments were addressed appropriately.
>
> Thanks,
> Rich
>
> On Wed, Jul 11, 2012 at 10:16 AM,  <internet-drafts@ietf.org> wrote:
>   
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>  This draft is a work item of the Application-Layer Traffic Optimization Working Group of the IETF.
>>
>>         Title           : ALTO Protocol
>>         Author(s)       : Richard Alimi
>>                           Reinaldo Penno
>>                           Y. Richard Yang
>>         Filename        : draft-ietf-alto-protocol-12.txt
>>         Pages           : 72
>>         Date            : 2012-07-11
>>
>> Abstract:
>>    Networking applications today already have access to a great amount
>>    of Inter-Provider network topology information.  For example, views
>>    of the Internet routing table are easily available at looking glass
>>    servers and entirely practical to be downloaded by clients.  What is
>>    missing is knowledge of the underlying network topology from the ISP
>>    or Content Provider (henceforth referred as Provider) point of view.
>>    In other words, what a Provider prefers in terms of traffic
>>    optimization -- and a way to distribute it.
>>
>>    The ALTO Service provides network information (e.g., basic network
>>    location structure, preferences of network paths) with the goal of
>>    modifying network resource consumption patterns while maintaining or
>>    improving application performance.  The basic information of ALTO is
>>    based on abstract maps of a network.  These maps provide a simplified
>>    view, yet enough information about a network for applications to
>>    effectively utilize them.  Additional services are built on top the
>>    maps.
>>
>>    This document describes a protocol implementing the ALTO Service.
>>    Although the ALTO service would primarily be provided by the network
>>    operator (e.g., an ISP), content providers and third parties could
>>    also operate this service.  Applications that could use this service
>>    are those that have a choice in connection endpoints.  Examples of
>>    such applications are peer-to-peer (P2P) and content delivery
>>    networks.
>>
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-alto-protocol
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-alto-protocol-12
>>
>> A diff from previous version is available at:
>> http://tools.ietf.org/rfcdiff?url2=draft-ietf-alto-protocol-12
>>
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>>     
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>   


From yang.r.yang@gmail.com  Mon Jul 30 17:45:02 2012
Return-Path: <yang.r.yang@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 BD3D111E80BA for <alto@ietfa.amsl.com>; Mon, 30 Jul 2012 17:45:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.85
X-Spam-Level: 
X-Spam-Status: No, score=-2.85 tagged_above=-999 required=5 tests=[AWL=0.126,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 YbsA1cD-xIps for <alto@ietfa.amsl.com>; Mon, 30 Jul 2012 17:45:01 -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 051FB11E80A2 for <alto@ietf.org>; Mon, 30 Jul 2012 17:45:00 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so11132852obb.31 for <alto@ietf.org>; Mon, 30 Jul 2012 17:45:00 -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:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=kIP8hfA/M1UdFV285rcK3Z2Xg+3GlK3eNJY9jZxfSwo=; b=0o6rnkoGQQly77Vo9XaCV7tJGXt1QJpyT3dof3abXgjZAxcumP+f3obzY1kJzTUWjc E+gR7rVvjDy9WjWvVA4j4ZDMQpyS5tWmgLJcnigunD3OgAyl7h9HQKrpnbSGVSxAqbeQ d1dFtfAKHjCWSRSJitbeBPMdFFbVRgwF32Hc02XKEUOgX/5C5dayFt3DW8Pq5o/TXxmi yLJdJmKinTH675ZLSoHqzP/WvkVC5nibvq3Iso/EhHVLcOG+KbUvKQNdBxjN4XFhYLmb LN0ENVzqTNMXW9+JmIWZ22Nzqk8LGEVTI4fLdm0jUT9m8aanDvMMCNXDQhR0CpBcvpTR U5mg==
MIME-Version: 1.0
Received: by 10.182.231.6 with SMTP id tc6mr20427265obc.63.1343695500494; Mon, 30 Jul 2012 17:45:00 -0700 (PDT)
Sender: yang.r.yang@gmail.com
Received: by 10.76.86.136 with HTTP; Mon, 30 Jul 2012 17:45:00 -0700 (PDT)
In-Reply-To: <CA+cvDaZZ7ow7QWMjmGkLs0E7c0PK2KjPApVtr_z4qQTOyBTwpQ@mail.gmail.com>
References: <CA+cvDaZZ7ow7QWMjmGkLs0E7c0PK2KjPApVtr_z4qQTOyBTwpQ@mail.gmail.com>
Date: Tue, 31 Jul 2012 08:45:00 +0800
X-Google-Sender-Auth: 4bTcniRU7yq5Ha_Y8MOtSMy09L4
Message-ID: <CANUuoLrMKU6R9MGqFoMFpwD6QFiTX2Gvsy8GHsjt230p5yodpg@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: Richard Alimi <rich@velvetsea.net>
Content-Type: multipart/alternative; boundary=f46d0446312cfe472704c6157c0c
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] ALTO Operations and Management
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, 31 Jul 2012 00:45:03 -0000

--f46d0446312cfe472704c6157c0c
Content-Type: text/plain; charset=ISO-8859-1

Hi Rich,

A very good effort to support Operations and Management. A rough separation
along the line between Operations and Management to use two documents seems
to be reasonable to me. If anyone has pointers on how another similar
protocol handles O/M, it will be helpful.

A particular item that appears to be challenging, as you also pointed out,
is Configuration Management (item 4 in your email). I can imagine that a
network operator may use a proprietary configuration specification system
or we need to develop a standard format (as you mentioned in your outline)?
If only static configuration is allowed, the task may be manageable, but
dynamic input (and transformation may be involved), and hence I see
challenge here. A complex Configuration Management Specification may also
lead to a complex management API (e.g., consistency of extracting data from
multiples ounces such as MIBs).

Another comment is on Fault Detection and Verfcation of Operation. Since
your these is on robust configuration/verification, we know it can get
complex/sophisticated quickly. Simply responding to some probes may not be
enough... How do we agree on the detection and verification scheme?

The 3rd comment is on other Services beyond Net and Cost Maps. Do we
include them?

Thanks!

Richard

On Sunday, July 29, 2012, Richard Alimi wrote:

> Hi All,
>
> As you probably know, one of the new requirements on the protocol is:
>    An ALTO client protocol MUST provide adequate
>    mechanisms for operations and management support, as outlined in RFC
>    5706 [RFC5706].
>
> The points raised by RFC5706 are very good and should indeed be
> solved. What I'm missing currently is a clear picture of exactly what
> this requirement dictates for draft-ietf-alto-protocol.  In
> particular, the scope of RFC5706 is *huge* - to address every
> suggested point fully would take another couple of years (e.g.,
> specify a management API for ALTO Servers, a configuration language,
> techniques for verifying end-to-end operation, etc).
>
> I'll suggest a way forwards - please provide feedback if you have a
> chance.  I'd really like to get something mostly complete by the end
> of IETF week if possible.
>
> Proposal:
>
> If we separate Operations (RFC5706, Section 2) from Management
> (RFC5706, Section 3), I can make the following general observation:
> - Operations: the protocol draft seems like a fine place to document
> these, with the exception of 2.6 ("Verifying Correct Operation") which
> is covered in Section 6.3 of draft-ietf-alto-deployments-04
> - Management: draft-ietf-alto-deployments seems to already cover some
> of this, and could probably be expanded to cover the rest (well, the
> rest that we intend to solve) to keep the related information
> together.  That seems preferable than copying a bunch of content from
> draft-ietf-alto-deployments into draft-ietf-alto-protocol when we had
> intentionally kept them separate in the first place.  The exception to
> this might be dictating which protocols to use for some functions that
> we know would be needed (syslog, IPFIX), which seem fine to have in
> draft-ietf-alto-protocol.
>
> Thoughts on that?  The intent isn't to just punt this over to another
> draft, but rather to avoid duplicating text between different
> documents and finish the protocol draft in a reasonable amount of
> time.
>
> If that *does* sound reasonable, I can write up some more concrete
> text for the Operations section with a pointer indicating that
> Management considerations are being documented in
> draft-ietf-alto-deployments (seems like an Informative reference, so
> that should be fine?)
>
> If that *doesn't* sound reasonable, I'd really like to hear from
> people what should be documented in the ALTO Protocol draft itself to
> support Operations and Management.  Below my signature, I've included
> some quick notes below about what I think *could* be discussed for
> most of the points raised by RFC5706.  I don't think the authors of
> the new requirement envisioned all of that to be included in
> draft-ietf-alto-protocol, but I'd need some help in defining where to
> draw the line.
>
> Thanks,
> Rich
>
> -- Operations --
>
> (1) Installation and Initial Setup
> - By default an ALTO Server may be configured with a single PID
> containing all IPv4/IPv6 addresses and a Cost Map with no entries.
> Something more interesting should be configured explicitly (either
> dynamically or statically).
> - Specifications for underlying protocols (e.g., TCP, HTTP) should be
> consulted for their available settings/defaults.
>
> (2) Migration Path
> - No migration path for ALTO Servers since there is no previous
> protocol providing same functionality.
> - Client-side: Applications making use of other data sources for
> network information should consider ALTO an additional source of
> information, but ALTO need not be the sole source of network
> information.
>
> (3) Requirements on Other Protocols and Functional Components
> - Protocol-wise, ALTO assumes standard HTTP and JSON implementations exist.
> - Functional-wise: An ALTO Server assumes that it can gather
> sufficient information to populate Network and Cost maps.  "Sufficient
> information" is dependent on the information being exposed, but likely
> includes information such as IGP and EGP RIBs (more details in Section
> 2.2 of draft-ietf-alto-protocol-12).  Specific mechanisms have been
> suggested in the past as extensions (e.g.,
> draft-medved-alto-svr-apis-00).
>
> (4) Impact on Network Operation
> - Operators should consider impacts on (or integration with) Traffic
> Engineering, since ALTO may shift traffic patterns.
> - Privacy considerations for ISPs (see 10.1 of draft-ietf-alto-protocol-12)
> - Impact of incorrect/faked guidance (see 10.3 of
> draft-ietf-alto-deployments-04)
>
> (5) Verifying Correct Operation
> - For ALTO-specific monitoring and metrics, see 6.3 of
> draft-ietf-alto-deployments-04
>
> -- Management --
>
> (1) Interoperability
> - A common management API would be desirable given that ALTO Servers
> may typically be configured with dynamic data from various sources,
> and ALTO Servers are intended to scale horizontally for
> fault-tolerance and reliability
>   - management protocol should operate semantically at the level of
> ALTO maps or other exposed information
> - Entities that compute dynamic maps/guidance and entities that
> measure ALTO's effects should use IPFIX information elements
> - ALTO Servers should use syslog to log events.
>
> (2) Management Information
> - Informational Model
>   - Data Sources - the set of data sources made available to an ALTO Server
>   - Information Resource Directory - the set of ALTO Information
> exposed by an ALTO Server
>   - Section 4 and 5 of draft-ietf-alto-protocol-12 describe Network
> Map, PIDs and Cost Maps, which are central entities of the
> informational model.
>   - ALTO guidance: ALTO Server may use internal logic/algorithms to
> generate responses to ALTO Clients (map and endpoint-based queries);
> may be customized to a particular deployment environment, so not
> standardized (as long as responses follow protocol spec). May use
> Network Map and Cost Map to answer queries, or may use custom logic.
>
> (3) Fault Management
> - To be discussed in 6.3 of draft-ietf-alto-deployments
>
> (4) Configuration Management
> - ALTO Server requires at least the following (high-level) logical inputs:
>   - Data Sources (raw network , or explicitly-provided ALTO-level
> information such as a Network Map and Cost Map)
>   - Security policies
> - Configuration interface should use ALTO data structures (as
> specified in the ALTO Protocol itself) wherever possible to configure
> the ALTO information exposed by an ALTO Server.  Specific syntax may
> differ if porting to a language that is not JSON, but structures
> should remain consistent.
> - Specify standard configuration language and interface for
> interoperability
> - Multiple ALTO Servers my be deployed for horizontal scalability. A
> centralized configuration database may be used to ensure they are
> providing the desired ALTO information with appropriate security
> controls.  The ALTO information (e.g., Network Maps and Cost Maps)
> being served by each ALTO Server, as well as security policies (HTTP
> authentication, SSL/TLS client/server authentication, SSL/TLS
> encryption parameters) intended to serve the same information should
> be monitored for consistency.
> - Verifying Correct Operation: Discussed in 6.3 of
> draft-ietf-alto-deployments (and future revisions)
>
> (5) Accounting Management
> - Discussed in 6.3 of draft-ietf-alto-deployments (and future revisions)
>
> (6) Performance Management
> - List interesting counters
>   - e.g., Number of requests for each service, responses, bytes
> in/out, CPU utilization, ALTO map/guidance updates, number of PIDs,
> map sizes (bytes, number of entries), etc
> - Interesting data accessible by IPFIX
>   - e.g., bytes per src/dst IP
> - network devices
>   - link utilization
>
> (7) Security Management
> - Readers should refer to documentation on HTTP and SSL/TLS.
> - ALTO Servers will typically receive a large number of requests.
> Intrusion Detection Systems that can separate malicious attacks from
> noise are suggested when generating alerts.
>
>
> Thanks,
> Rich
> _______________________________________________
> alto mailing list
> alto@ietf.org <javascript:;>
> https://www.ietf.org/mailman/listinfo/alto
>

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

Hi Rich,<div><br></div><div>A very good effort to support Operations and Ma=
nagement. A rough separation along the line between Operations and Manageme=
nt to use two documents seems to be reasonable to me. If anyone has pointer=
s on how another similar protocol handles O/M, it will be helpful.</div>
<div><br></div><div>A particular item that appears to be challenging, as yo=
u also pointed out, is Configuration Management (item 4 in your email). I c=
an imagine that a network operator may use a proprietary configuration spec=
ification system or we need to develop a standard format (as you mentioned =
in your outline)? If only static configuration is allowed, the task may be =
manageable, but dynamic input (and transformation may be involved), and hen=
ce I see challenge here. A complex Configuration Management Specification m=
ay also lead to a complex management API (e.g., consistency of extracting d=
ata from multiples ounces such as MIBs).=A0</div>
<div><br></div><div>Another comment is on Fault Detection and Verfcation of=
 Operation. Since your these is on robust configuration/verification, we kn=
ow it can get complex/sophisticated quickly. Simply responding to some prob=
es may not be enough... How do we agree on the detection and verification s=
cheme?</div>
<div><br></div><div>The 3rd comment is on other Services beyond Net and Cos=
t Maps. Do we include them?</div><div><br></div><div>Thanks!<span></span></=
div><div><br></div><div>Richard<br><br>On Sunday, July 29, 2012, Richard Al=
imi  wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi All,<br>
<br>
As you probably know, one of the new requirements on the protocol is:<br>
=A0 =A0An ALTO client protocol MUST provide adequate<br>
=A0 =A0mechanisms for operations and management support, as outlined in RFC=
<br>
=A0 =A05706 [RFC5706].<br>
<br>
The points raised by RFC5706 are very good and should indeed be<br>
solved. What I&#39;m missing currently is a clear picture of exactly what<b=
r>
this requirement dictates for draft-ietf-alto-protocol. =A0In<br>
particular, the scope of RFC5706 is *huge* - to address every<br>
suggested point fully would take another couple of years (e.g.,<br>
specify a management API for ALTO Servers, a configuration language,<br>
techniques for verifying end-to-end operation, etc).<br>
<br>
I&#39;ll suggest a way forwards - please provide feedback if you have a<br>
chance. =A0I&#39;d really like to get something mostly complete by the end<=
br>
of IETF week if possible.<br>
<br>
Proposal:<br>
<br>
If we separate Operations (RFC5706, Section 2) from Management<br>
(RFC5706, Section 3), I can make the following general observation:<br>
- Operations: the protocol draft seems like a fine place to document<br>
these, with the exception of 2.6 (&quot;Verifying Correct Operation&quot;) =
which<br>
is covered in Section 6.3 of draft-ietf-alto-deployments-04<br>
- Management: draft-ietf-alto-deployments seems to already cover some<br>
of this, and could probably be expanded to cover the rest (well, the<br>
rest that we intend to solve) to keep the related information<br>
together. =A0That seems preferable than copying a bunch of content from<br>
draft-ietf-alto-deployments into draft-ietf-alto-protocol when we had<br>
intentionally kept them separate in the first place. =A0The exception to<br=
>
this might be dictating which protocols to use for some functions that<br>
we know would be needed (syslog, IPFIX), which seem fine to have in<br>
draft-ietf-alto-protocol.<br>
<br>
Thoughts on that? =A0The intent isn&#39;t to just punt this over to another=
<br>
draft, but rather to avoid duplicating text between different<br>
documents and finish the protocol draft in a reasonable amount of<br>
time.<br>
<br>
If that *does* sound reasonable, I can write up some more concrete<br>
text for the Operations section with a pointer indicating that<br>
Management considerations are being documented in<br>
draft-ietf-alto-deployments (seems like an Informative reference, so<br>
that should be fine?)<br>
<br>
If that *doesn&#39;t* sound reasonable, I&#39;d really like to hear from<br=
>
people what should be documented in the ALTO Protocol draft itself to<br>
support Operations and Management. =A0Below my signature, I&#39;ve included=
<br>
some quick notes below about what I think *could* be discussed for<br>
most of the points raised by RFC5706. =A0I don&#39;t think the authors of<b=
r>
the new requirement envisioned all of that to be included in<br>
draft-ietf-alto-protocol, but I&#39;d need some help in defining where to<b=
r>
draw the line.<br>
<br>
Thanks,<br>
Rich<br>
<br>
-- Operations --<br>
<br>
(1) Installation and Initial Setup<br>
- By default an ALTO Server may be configured with a single PID<br>
containing all IPv4/IPv6 addresses and a Cost Map with no entries.<br>
Something more interesting should be configured explicitly (either<br>
dynamically or statically).<br>
- Specifications for underlying protocols (e.g., TCP, HTTP) should be<br>
consulted for their available settings/defaults.<br>
<br>
(2) Migration Path<br>
- No migration path for ALTO Servers since there is no previous<br>
protocol providing same functionality.<br>
- Client-side: Applications making use of other data sources for<br>
network information should consider ALTO an additional source of<br>
information, but ALTO need not be the sole source of network<br>
information.<br>
<br>
(3) Requirements on Other Protocols and Functional Components<br>
- Protocol-wise, ALTO assumes standard HTTP and JSON implementations exist.=
<br>
- Functional-wise: An ALTO Server assumes that it can gather<br>
sufficient information to populate Network and Cost maps. =A0&quot;Sufficie=
nt<br>
information&quot; is dependent on the information being exposed, but likely=
<br>
includes information such as IGP and EGP RIBs (more details in Section<br>
2.2 of draft-ietf-alto-protocol-12). =A0Specific mechanisms have been<br>
suggested in the past as extensions (e.g.,<br>
draft-medved-alto-svr-apis-00).<br>
<br>
(4) Impact on Network Operation<br>
- Operators should consider impacts on (or integration with) Traffic<br>
Engineering, since ALTO may shift traffic patterns.<br>
- Privacy considerations for ISPs (see 10.1 of draft-ietf-alto-protocol-12)=
<br>
- Impact of incorrect/faked guidance (see 10.3 of<br>
draft-ietf-alto-deployments-04)<br>
<br>
(5) Verifying Correct Operation<br>
- For ALTO-specific monitoring and metrics, see 6.3 of<br>
draft-ietf-alto-deployments-04<br>
<br>
-- Management --<br>
<br>
(1) Interoperability<br>
- A common management API would be desirable given that ALTO Servers<br>
may typically be configured with dynamic data from various sources,<br>
and ALTO Servers are intended to scale horizontally for<br>
fault-tolerance and reliability<br>
=A0 - management protocol should operate semantically at the level of<br>
ALTO maps or other exposed information<br>
- Entities that compute dynamic maps/guidance and entities that<br>
measure ALTO&#39;s effects should use IPFIX information elements<br>
- ALTO Servers should use syslog to log events.<br>
<br>
(2) Management Information<br>
- Informational Model<br>
=A0 - Data Sources - the set of data sources made available to an ALTO Serv=
er<br>
=A0 - Information Resource Directory - the set of ALTO Information<br>
exposed by an ALTO Server<br>
=A0 - Section 4 and 5 of draft-ietf-alto-protocol-12 describe Network<br>
Map, PIDs and Cost Maps, which are central entities of the<br>
informational model.<br>
=A0 - ALTO guidance: ALTO Server may use internal logic/algorithms to<br>
generate responses to ALTO Clients (map and endpoint-based queries);<br>
may be customized to a particular deployment environment, so not<br>
standardized (as long as responses follow protocol spec). May use<br>
Network Map and Cost Map to answer queries, or may use custom logic.<br>
<br>
(3) Fault Management<br>
- To be discussed in 6.3 of draft-ietf-alto-deployments<br>
<br>
(4) Configuration Management<br>
- ALTO Server requires at least the following (high-level) logical inputs:<=
br>
=A0 - Data Sources (raw network , or explicitly-provided ALTO-level<br>
information such as a Network Map and Cost Map)<br>
=A0 - Security policies<br>
- Configuration interface should use ALTO data structures (as<br>
specified in the ALTO Protocol itself) wherever possible to configure<br>
the ALTO information exposed by an ALTO Server. =A0Specific syntax may<br>
differ if porting to a language that is not JSON, but structures<br>
should remain consistent.<br>
- Specify standard configuration language and interface for interoperabilit=
y<br>
- Multiple ALTO Servers my be deployed for horizontal scalability. A<br>
centralized configuration database may be used to ensure they are<br>
providing the desired ALTO information with appropriate security<br>
controls. =A0The ALTO information (e.g., Network Maps and Cost Maps)<br>
being served by each ALTO Server, as well as security policies (HTTP<br>
authentication, SSL/TLS client/server authentication, SSL/TLS<br>
encryption parameters) intended to serve the same information should<br>
be monitored for consistency.<br>
- Verifying Correct Operation: Discussed in 6.3 of<br>
draft-ietf-alto-deployments (and future revisions)<br>
<br>
(5) Accounting Management<br>
- Discussed in 6.3 of draft-ietf-alto-deployments (and future revisions)<br=
>
<br>
(6) Performance Management<br>
- List interesting counters<br>
=A0 - e.g., Number of requests for each service, responses, bytes<br>
in/out, CPU utilization, ALTO map/guidance updates, number of PIDs,<br>
map sizes (bytes, number of entries), etc<br>
- Interesting data accessible by IPFIX<br>
=A0 - e.g., bytes per src/dst IP<br>
- network devices<br>
=A0 - link utilization<br>
<br>
(7) Security Management<br>
- Readers should refer to documentation on HTTP and SSL/TLS.<br>
- ALTO Servers will typically receive a large number of requests.<br>
Intrusion Detection Systems that can separate malicious attacks from<br>
noise are suggested when generating alerts.<br>
<br>
<br>
Thanks,<br>
Rich<br>
_______________________________________________<br>
alto mailing list<br>
<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;alto@iet=
f.org&#39;)">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
</blockquote></div>

--f46d0446312cfe472704c6157c0c--

From richard.alimi@gmail.com  Tue Jul 31 08:07:11 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 6CF4621F86AA for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 08:07:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.756
X-Spam-Level: 
X-Spam-Status: No, score=-2.756 tagged_above=-999 required=5 tests=[AWL=0.221,  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 5k1bRVjm2X6J for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 08:07:10 -0700 (PDT)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1F5CC21F8687 for <alto@ietf.org>; Tue, 31 Jul 2012 08:07:10 -0700 (PDT)
Received: by qaea16 with SMTP id a16so1766462qae.10 for <alto@ietf.org>; Tue, 31 Jul 2012 08:07:09 -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=Ffqe9JxyNBF0GY2Pp4ukhckR91Or6uelMgXIcXmAQeo=; b=EUTwHJUWZ48zaHekwahZiclr2IIVgOC69wp4QMAvXFj7of8aIMX4FDL9Yn8dgIznSH vrBC12ljtOxsA/1jEoFIC/3i2gUZUYM0BmhdWeX+9dKzROcxpbqUuKPmJhWipBSCBug1 qg/xVfJUwk0+JBpXPS38LOoI9KPP540ay2RsRAIpnEv/wVcOrEVgomYFgmfyEdZxoWX1 Kg8yoUN5OkIXt5PGjJNAyOsBpsirX1NqRyaZXTgi6DA87K6DDC/0o4RJ7IQpdvZ0Zhlq C1Vo50m9tD4l1coQ3qrueM4Eg5zp4vVNcEpFX8olu1qFCBNxAQW9EeyFHp8zZSH35W2S 4P8Q==
Received: by 10.58.168.211 with SMTP id zy19mr2796356veb.25.1343747229430; Tue, 31 Jul 2012 08:07:09 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.58.79.234 with HTTP; Tue, 31 Jul 2012 08:06:49 -0700 (PDT)
In-Reply-To: <CANUuoLrMKU6R9MGqFoMFpwD6QFiTX2Gvsy8GHsjt230p5yodpg@mail.gmail.com>
References: <CA+cvDaZZ7ow7QWMjmGkLs0E7c0PK2KjPApVtr_z4qQTOyBTwpQ@mail.gmail.com> <CANUuoLrMKU6R9MGqFoMFpwD6QFiTX2Gvsy8GHsjt230p5yodpg@mail.gmail.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Tue, 31 Jul 2012 08:06:49 -0700
X-Google-Sender-Auth: 03MPNxoGnuX6W2iAlHnq_knYDyI
Message-ID: <CA+cvDaYcd73OB9OoP=5xfPij39ufpW8f-7umHeZp9fEd5sBSPA@mail.gmail.com>
To: "Y. Richard Yang" <yry@cs.yale.edu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] ALTO Operations and Management
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, 31 Jul 2012 15:07:11 -0000

On Mon, Jul 30, 2012 at 5:45 PM, Y. Richard Yang <yry@cs.yale.edu> wrote:
> Hi Rich,
>
> A very good effort to support Operations and Management. A rough separation
> along the line between Operations and Management to use two documents seems
> to be reasonable to me. If anyone has pointers on how another similar
> protocol handles O/M, it will be helpful.
>
> A particular item that appears to be challenging, as you also pointed out,
> is Configuration Management (item 4 in your email). I can imagine that a
> network operator may use a proprietary configuration specification system or
> we need to develop a standard format (as you mentioned in your outline)?

RFC5706 seems to strongly hint (and I agree) that interoperability is
important even for configuration management.  If I were an operator
using equipment from multiple vendors, I might write the necessary
scripting and abstractions to ease management, but I'd probably prefer
this to be uniform and not have to implement my own abstraction layer.

> If
> only static configuration is allowed, the task may be manageable, but
> dynamic input (and transformation may be involved), and hence I see
> challenge here. A complex Configuration Management Specification may also
> lead to a complex management API (e.g., consistency of extracting data from
> multiples ounces such as MIBs).

Completely agreed.  I think most deployments would benefit from having
dynamic updates, particularly in the cost maps.  I could imagine a
couple of ways to approach such an API:
(1) Provide an API to explicitly configure maps (and perhaps some sort
of equivalent for the endpoint-based services), and leave mechanisms
computing the ALTO information (and integration with data sources) out
of scope.
(2) Do (1) and also specify how this ties into various data sources.

>
> Another comment is on Fault Detection and Verfcation of Operation. Since
> your these is on robust configuration/verification, we know it can get
> complex/sophisticated quickly. Simply responding to some probes may not be
> enough... How do we agree on the detection and verification scheme?

I'm not sure :) Fault detection and verification can be complicated
enough when you know most things about the system.  In the ALTO case,
there are at least a few things that are going to make this much
harder:
- We tell ALTO clients that this is just another data source and that
it is purely advisory.  It isn't necessarily clear whether changes are
due to ALTO or some other data source.
- In certain deployment environments, application developers probably
will not configure ALTO Clients to supply performance feedback or
application-level details even if we provided an interface
- This is only a portion of Internet traffic, and it isn't clear
whether a particular packet was influenced by ALTO or not since ALTO
doesn't (currently) have any dataplane components.
- ALTO guidance from one ISP may influence traffic patterns in another ISP.

>
> The 3rd comment is on other Services beyond Net and Cost Maps. Do we include
> them?

Yes - they should be included too.  Apologies for omitting them from
my initial note - I was mainly trying to sketch the overall components
involved.

Thanks!
Rich

>
> Thanks!
>
> Richard
>
>
> On Sunday, July 29, 2012, Richard Alimi wrote:
>>
>> Hi All,
>>
>> As you probably know, one of the new requirements on the protocol is:
>>    An ALTO client protocol MUST provide adequate
>>    mechanisms for operations and management support, as outlined in RFC
>>    5706 [RFC5706].
>>
>> The points raised by RFC5706 are very good and should indeed be
>> solved. What I'm missing currently is a clear picture of exactly what
>> this requirement dictates for draft-ietf-alto-protocol.  In
>> particular, the scope of RFC5706 is *huge* - to address every
>> suggested point fully would take another couple of years (e.g.,
>> specify a management API for ALTO Servers, a configuration language,
>> techniques for verifying end-to-end operation, etc).
>>
>> I'll suggest a way forwards - please provide feedback if you have a
>> chance.  I'd really like to get something mostly complete by the end
>> of IETF week if possible.
>>
>> Proposal:
>>
>> If we separate Operations (RFC5706, Section 2) from Management
>> (RFC5706, Section 3), I can make the following general observation:
>> - Operations: the protocol draft seems like a fine place to document
>> these, with the exception of 2.6 ("Verifying Correct Operation") which
>> is covered in Section 6.3 of draft-ietf-alto-deployments-04
>> - Management: draft-ietf-alto-deployments seems to already cover some
>> of this, and could probably be expanded to cover the rest (well, the
>> rest that we intend to solve) to keep the related information
>> together.  That seems preferable than copying a bunch of content from
>> draft-ietf-alto-deployments into draft-ietf-alto-protocol when we had
>> intentionally kept them separate in the first place.  The exception to
>> this might be dictating which protocols to use for some functions that
>> we know would be needed (syslog, IPFIX), which seem fine to have in
>> draft-ietf-alto-protocol.
>>
>> Thoughts on that?  The intent isn't to just punt this over to another
>> draft, but rather to avoid duplicating text between different
>> documents and finish the protocol draft in a reasonable amount of
>> time.
>>
>> If that *does* sound reasonable, I can write up some more concrete
>> text for the Operations section with a pointer indicating that
>> Management considerations are being documented in
>> draft-ietf-alto-deployments (seems like an Informative reference, so
>> that should be fine?)
>>
>> If that *doesn't* sound reasonable, I'd really like to hear from
>> people what should be documented in the ALTO Protocol draft itself to
>> support Operations and Management.  Below my signature, I've included
>> some quick notes below about what I think *could* be discussed for
>> most of the points raised by RFC5706.  I don't think the authors of
>> the new requirement envisioned all of that to be included in
>> draft-ietf-alto-protocol, but I'd need some help in defining where to
>> draw the line.
>>
>> Thanks,
>> Rich
>>
>> -- Operations --
>>
>> (1) Installation and Initial Setup
>> - By default an ALTO Server may be configured with a single PID
>> containing all IPv4/IPv6 addresses and a Cost Map with no entries.
>> Something more interesting should be configured explicitly (either
>> dynamically or statically).
>> - Specifications for underlying protocols (e.g., TCP, HTTP) should be
>> consulted for their available settings/defaults.
>>
>> (2) Migration Path
>> - No migration path for ALTO Servers since there is no previous
>> protocol providing same functionality.
>> - Client-side: Applications making use of other data sources for
>> network information should consider ALTO an additional source of
>> information, but ALTO need not be the sole source of network
>> information.
>>
>> (3) Requirements on Other Protocols and Functional Components
>> - Protocol-wise, ALTO assumes standard HTTP and JSON implementations
>> exist.
>> - Functional-wise: An ALTO Server assumes that it can gather
>> sufficient information to populate Network and Cost maps.  "Sufficient
>> information" is dependent on the information being exposed, but likely
>> includes information such as IGP and EGP RIBs (more details in Section
>> 2.2 of draft-ietf-alto-protocol-12).  Specific mechanisms have been
>> suggested in the past as extensions (e.g.,
>> draft-medved-alto-svr-apis-00).
>>
>> (4) Impact on Network Operation
>> - Operators should consider impacts on (or integration with) Traffic
>> Engineering, since ALTO may shift traffic patterns.
>> - Privacy considerations for ISPs (see 10.1 of
>> draft-ietf-alto-protocol-12)
>> - Impact of incorrect/faked guidance (see 10.3 of
>> draft-ietf-alto-deployments-04)
>>
>> (5) Verifying Correct Operation
>> - For ALTO-specific monitoring and metrics, see 6.3 of
>> draft-ietf-alto-deployments-04
>>
>> -- Management --
>>
>> (1) Interoperability
>> - A common management API would be desirable given that ALTO Servers
>> may typically be configured with dynamic data from various sources,
>> and ALTO Servers are intended to scale horizontally for
>> fault-tolerance and reliability
>>   - management protocol should operate semantically at the level of
>> ALTO maps or other exposed information
>> - Entities that compute dynamic maps/guidance and entities that
>> measure ALTO's effects should use IPFIX information elements
>> - ALTO Servers should use syslog to log events.
>>
>> (2) Management Information
>> - Informational Model
>>   - Data Sources - the set of data sources made available to an ALTO
>> Server
>>   - Information Resource Directory - the set of ALTO Information
>> exposed by an ALTO Server
>>   - Section 4 and 5 of draft-ietf-alto-protocol-12 describe Network
>> Map, PIDs and Cost Maps, which are central entities of the
>> informational model.
>>   - ALTO guidance: ALTO Server may use internal logic/algorithms to
>> generate responses to ALTO Clients (map and endpoint-based queries);
>> may be customized to a particular deployment environment, so not
>> standardized (as long as responses follow protocol spec). May use
>> Network Map and Cost Map to answer queries, or may use custom logic.
>>
>> (3) Fault Management
>> - To be discussed in 6.3 of draft-ietf-alto-deployments
>>
>> (4) Configuration Management
>> - ALTO Server requires at least the following (high-level) logical inputs:
>>   - Data Sources (raw network , or explicitly-provided ALTO-level
>> information such as a Network Map and Cost Map)
>>   - Security policies
>> - Configuration interface should use ALTO data structures (as
>> specified in the ALTO Protocol itself) wherever possible to configure
>> the ALTO information exposed by an ALTO Server.  Specific syntax may
>> differ if porting to a language that is not JSON, but structures
>> should remain consistent.
>> - Specify standard configuration language and interface for
>> interoperability
>> - Multiple ALTO Servers my be deployed for horizontal scalability. A
>> centralized configuration database may be used to ensure they are
>> providing the desired ALTO information with appropriate security
>> controls.  The ALTO information (e.g., Network Maps and Cost Maps)
>> being served by each ALTO Server, as well as security policies (HTTP
>> authentication, SSL/TLS client/server authentication, SSL/TLS
>> encryption parameters) intended to serve the same information should
>> be monitored for consistency.
>> - Verifying Correct Operation: Discussed in 6.3 of
>> draft-ietf-alto-deployments (and future revisions)
>>
>> (5) Accounting Management
>> - Discussed in 6.3 of draft-ietf-alto-deployments (and future revisions)
>>
>> (6) Performance Management
>> - List interesting counters
>>   - e.g., Number of requests for each service, responses, bytes
>> in/out, CPU utilization, ALTO map/guidance updates, number of PIDs,
>> map sizes (bytes, number of entries), etc
>> - Interesting data accessible by IPFIX
>>   - e.g., bytes per src/dst IP
>> - network devices
>>   - link utilization
>>
>> (7) Security Management
>> - Readers should refer to documentation on HTTP and SSL/TLS.
>> - ALTO Servers will typically receive a large number of requests.
>> Intrusion Detection Systems that can separate malicious attacks from
>> noise are suggested when generating alerts.
>>
>>
>> Thanks,
>> Rich
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto

From richard.alimi@gmail.com  Tue Jul 31 08:30:48 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 A10F321F86BA for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 08:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.77
X-Spam-Level: 
X-Spam-Status: No, score=-2.77 tagged_above=-999 required=5 tests=[AWL=0.207,  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 RPHDuV2trEea for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 08:30:48 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id C089021F8671 for <alto@ietf.org>; Tue, 31 Jul 2012 08:30:47 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so6322194vcb.31 for <alto@ietf.org>; Tue, 31 Jul 2012 08:30:47 -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=NqMynroqYYXaLsRi7UDhb1M0hBdezyal3foJxdGRZmc=; b=ECF3CEsgrJFA3bI6ZtAhFuVTDNFwIhUjCtZMZmcaY4pytZDaE6Hvob3w8HO5VOf6yR +GGZgtdYHQVWg2xGU7bPnm5+AV+zjs9BKiYiuGBy2pPCQ+gH6LCi9K/YCPDWynG8Y8J9 tc1sbkb6v5d3Wl+sv1ibEkZmO5cFkEzMygl1utvoxhTujctcbCAWrmeDfvLPpW8vb/vO MJFo5ItrKOn925OwZeIZCnCpav9hQ33EgGVXScQ2zy8+eakcW9svmCQV5hdvVFIPkf0O IAlKAVaDO/gf+xRGd91UHPKIUxpU/rcAt0T59lmc+kCNAZuB5/hKNqmvkIZTV0EXpEp2 acHg==
Received: by 10.52.155.193 with SMTP id vy1mr12532946vdb.123.1343748647251; Tue, 31 Jul 2012 08:30:47 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.58.79.234 with HTTP; Tue, 31 Jul 2012 08:30:26 -0700 (PDT)
In-Reply-To: <5016C638.10203@alcatel-lucent.com>
References: <20120711171608.16399.10488.idtracker@ietfa.amsl.com> <CA+cvDabW17VfVF4w+u0FkvFAF9v0zuzPw1DOP+proBouOCKzJg@mail.gmail.com> <5016C638.10203@alcatel-lucent.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Tue, 31 Jul 2012 08:30:26 -0700
X-Google-Sender-Auth: lV9t0AnZOlkr6lqQzq0PUrDyhn8
Message-ID: <CA+cvDab=7Y9r+MN9aZB_2Ob0ceQPCpe0c1gpEvb6JAaB-8NdfQ@mail.gmail.com>
To: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] I-D Action: draft-ietf-alto-protocol-12.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, 31 Jul 2012 15:30:48 -0000

On Mon, Jul 30, 2012 at 10:36 AM, Sabine Randriamasy
<Sabine.Randriamasy@alcatel-lucent.com> wrote:
> Hi Rich,
>
> I just came across one point regarding constraints in input parameters in
> POST requests for the Filtered Cost map and Endpoint Cost Services.
>
> In Section 6.8.2.2.3 Input Parameters (for filtered cost map), object
> ReqFilteredCostMap has a member
> 'JSONString constraints<0..*>'
>
> In Section 6.8.4.1.3 Input Parameters, object ReqEndpointCostMap has a
> member 'JSONString constraints' and
> refers to =A76.8.2.2  for the description.
> Is there an objection to also have 'JSONString constraints<0..*>' for the=
 EP
> cost service as having several constraints on a cost type may also be nee=
ded
> in the ECS ?

Thanks for catching this.  This is a mistake in the specification and
I've made the edit in our SVN repository so that fix will be included
when we submit the next version.

>
> Thanks
> Sabine
>
>
> Richard Alimi a =E9crit :
>
>> I believe this should address all of the WGLC comments received, with
>> the exception of handling the operations and management requirements.
>> Those are underway; I posted a new version now to give folks more time
>> to ensure that the WGLC comments were addressed appropriately.
>>
>> Thanks,
>> Rich
>>
>> On Wed, Jul 11, 2012 at 10:16 AM,  <internet-drafts@ietf.org> wrote:
>>
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories.
>>>  This draft is a work item of the Application-Layer Traffic Optimizatio=
n
>>> Working Group of the IETF.
>>>
>>>         Title           : ALTO Protocol
>>>         Author(s)       : Richard Alimi
>>>                           Reinaldo Penno
>>>                           Y. Richard Yang
>>>         Filename        : draft-ietf-alto-protocol-12.txt
>>>         Pages           : 72
>>>         Date            : 2012-07-11
>>>
>>> Abstract:
>>>    Networking applications today already have access to a great amount
>>>    of Inter-Provider network topology information.  For example, views
>>>    of the Internet routing table are easily available at looking glass
>>>    servers and entirely practical to be downloaded by clients.  What is
>>>    missing is knowledge of the underlying network topology from the ISP
>>>    or Content Provider (henceforth referred as Provider) point of view.
>>>    In other words, what a Provider prefers in terms of traffic
>>>    optimization -- and a way to distribute it.
>>>
>>>    The ALTO Service provides network information (e.g., basic network
>>>    location structure, preferences of network paths) with the goal of
>>>    modifying network resource consumption patterns while maintaining or
>>>    improving application performance.  The basic information of ALTO is
>>>    based on abstract maps of a network.  These maps provide a simplifie=
d
>>>    view, yet enough information about a network for applications to
>>>    effectively utilize them.  Additional services are built on top the
>>>    maps.
>>>
>>>    This document describes a protocol implementing the ALTO Service.
>>>    Although the ALTO service would primarily be provided by the network
>>>    operator (e.g., an ISP), content providers and third parties could
>>>    also operate this service.  Applications that could use this service
>>>    are those that have a choice in connection endpoints.  Examples of
>>>    such applications are peer-to-peer (P2P) and content delivery
>>>    networks.
>>>
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-alto-protocol
>>>
>>> There's also a htmlized version available at:
>>> http://tools.ietf.org/html/draft-ietf-alto-protocol-12
>>>
>>> A diff from previous version is available at:
>>> http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-alto-protocol-12
>>>
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>> _______________________________________________
>>> alto mailing list
>>> alto@ietf.org
>>> https://www.ietf.org/mailman/listinfo/alto
>>>
>>
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>>
>
>

From sabine.randriamasy@alcatel-lucent.com  Tue Jul 31 10:21:19 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 1570A21F8673 for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 10:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.639
X-Spam-Level: 
X-Spam-Status: No, score=-8.639 tagged_above=-999 required=5 tests=[AWL=-0.690, BAYES_00=-2.599, HELO_EQ_FR=0.35, MANGLED_NAIL=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 HFvZp4JYCepS for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 10:21:18 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id B9D1C21F866D for <alto@ietf.org>; Tue, 31 Jul 2012 10:21:17 -0700 (PDT)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q6VHKmMX020733 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 31 Jul 2012 19:20:48 +0200
Received: from [172.27.204.117] (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; Tue, 31 Jul 2012 19:20:47 +0200
Message-ID: <501813EA.2040808@alcatel-lucent.com>
Date: Tue, 31 Jul 2012 19:20:42 +0200
From: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Leeyoung <leeyoung@huawei.com>
References: <7AEB3D6833318045B4AE71C2C87E8E1720CC2D35@dfweml511-mbx.china.huawei.com> <5016C0DD.8050909@alcatel-lucent.com> <7AEB3D6833318045B4AE71C2C87E8E172905E3A2@dfweml511-mbs.china.huawei.com>
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E172905E3A2@dfweml511-mbs.china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] [altoext] FW: New Version Notification	for	draft-lee-alto-app-net-info-exchange-00.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, 31 Jul 2012 17:21:19 -0000

Hi Young,
Thanks for your answers. Please see inline for further comments.
I have put the "alto" list in Cc rather than "altoext" which will be closed.
Best regards
Sabine

Leeyoung a écrit :
> Hi Sabine,
>
> Thanks for providing your comments to our drafts. Please see in-line for my response.
>
> Best Regards,
> Young
>
> -----Original Message-----
> From: Sabine Randriamasy [mailto:Sabine.Randriamasy@alcatel-lucent.com] 
> Sent: Monday, July 30, 2012 12:14 PM
> To: Leeyoung
> Cc: altoext@ietf.org
> Subject: Re: [altoext] FW: New Version Notification for draft-lee-alto-app-net-info-exchange-00.txt
>
> Hi Young,
>
> I have read your draft and have a couple of comments and questions.
>
> In Section 2 Problem statement, I agree with the need to reduce the 
> amount of conveyed ALTO information through topology filtering and 
> constraint-based response filtering. The ALTO base protocol specifies 
> these features for the Cost Map, Filtered cost map and Endpoint cost 
> services. I also agree with the necessity to provide several types of 
> cost information which stresses the necessity of extended filtering 
> mechanisms. In the Constraints filtering extensions of Section 3, I 
> didnt' really get how information confidentiality is preserved and the 
> proposed specification raised the questions detailed below.
>
> YOUNG>> Information confidentiality is a big issue which the current draft has not addressed yet. The current draft was written in the "controlled" or "partially controlled" environments which means there is a trusted relationship amongst the entities involving the exchanges of resource data. 
> In generic framework where there may be no such trusted relationship amongst the entities, we need to address such issue down the road. 
>   
Ok. Indeed, ALTO environment control is introduced in the Introduction. 
I was mislead by seing "Such information may be considered sensitive to 
the network provider just as..." just before "Section 3 provides ALTO 
information model and protocol extensions to support... "
> I also agree that detailing end to end path costs at the link level at 
> some places can be beneficial, especially for local bottlenecks 
> sometimes with fast changing cost values. Figure 2 shows an example with 
> Link capacity costs but section 2 uses them rather as capacity, where I 
> figure the higher the better. Without a hint on how path costs are 
> calculated it is hard to follow the rationale on the DC choice by ER1. 
> See also the questions detailed below.
>
> YOUNG>> We actually enhanced this mechanism in section 6 of  draft-bernstein-alto-large-bandwidth-cases-02.txt
> where we include path vector along with link b/w. Path vector indicates shared link information from which
> The bottle neck link can be identified. 
>
> For instance, consider the following example from the draft. 
>
>
>          +----+                  L0 Wt=10,BW=50         +----+
>          | N0 |-----------------------------------------| N3 |
>          +----+  `.                                     +----+
>            |       `. L4 Wt=7                             |
>            |         `-. BW=40                            |
>            |            `.  +----+                        |
>            |              `.| N4 |                        |
>            | L1          .' +----+                        |
>            | Wt=10      /                          L2     |
>            | BW=45     /                           Wt=12  |
>            |          /L5 Wt=10                    BW=30  |
>            |        .'    BW=45                           |
>            |       /                                      |
>            |      /                                       |
>          +----+ .'              L3 Wt=15 BW=42          +----+
>          | N1 |.........................................| N2 |
>          +----+                                         +----+
>
> Now suppose the network of Figure 1 is a TDM network controlled by 
> GMPLS. Once again N0 representing a large data center and nodes N2
> and N3 as potential clients. However in this case the network provider 
> offers an additional path, P3, for getting from N0-N2.
>
>    Path  Src-Dest    Path Vector    Path Cost
>
>    P1    N0-N2       {L0, L2}       22
>    P2    N0-N3       {L0}           10
>    P3    N0-N2       {L1,L3}        25
>    ----------------------------------
>    Link        Bandwidth
>    L0             50
>    L1             45
>    L2             30
>    L3             42
>
> So the draft now propose that the network can provide abstract path 
> list along with link bottlenecks. We also provide how this mechanism 
> works for IP and other types of networks. 
>   
I'm fine with the rationale in 
draft-bernstein-alto-large-bandwidth-cases-02.txt. It's just that in 
draft-lee-alto-app-net-info-exchange-00.txt I missed the relation 
between the "LinkCapacity Cost" & ALTO Cost Map in Figure 2 and also the 
explanatory text text. Maybe a little clarifying edition can help.  
> I will provide the responses to your detail questions later. 
> Thanks. 
>
> Young
>
>
>
>          
>
> Thanks,
> Sabine
>
> ------------------------- Detailed questions -----------------------------
>
> ++ Section 3.1 ALTO Query from Application Stratum to Network Stratum
> Names used in the list of requested information may be misleading:
> - A 'Cost Type' see base protocol (§5.1.1) is expected to indicate an 
> attribute that has a value such as number, boolean, string... and is is 
> rather "semantic". 'summary' and 'graph' are cost attributes of 
> different nature.
> - 'Constraints' such as 'min/max metric' look like objectives rather 
> than expressions such as 'lt. value' as specified in the base protocol 
> (§ 6.8.2.2.3)
> - what kind of information is member 'Parameters' is supposed to carry 
> and for what use?
> - Some members listed here do not appear in the ALTO Query Information 
> Model of §3.3: 'parameters' 'objective-function'. Neither do they appear 
> in the example of §3.5
>
>
> ++ Section 3.2 ALTO response from Network ....
> - The list of S-D pairs should carry the Cost Type *values* as the 
> supported Cost Types are expected to be listed and checked in the IRD.
> - 'Constraint values': need to be clarified: is it the actual cost 
> value? then the draft should specifiy that the constraits relate to Cost 
> Types (as defined in §5.1.1).
> - how is the 'Administration Domain ID' of a S-D pair reported and why 
> is it needed?  
>
>
> ++ Section 3.3 Information Model of ALTO Query ...
> Looking at the specification here, it is hard to figure out what is 
> really extended here w.r.t. the Endpoint Cost Service query input 
> specified in the base protocol.
> - A new media type "CsoReqEndpointCostMap" and differs from 
> "ReqEndpointCostMap" of the base protocol in that the set in member 
> 'contraints' is encoded/interpreted differently, according to example in 
> §3.5. Then a different member name than 'contraints' should be used.
> - As for member 'endpoints': unless you need to specify only 1 src EP, 
> what is the need to define a new object "EndpointFilterExt" instead of 
> keeping the "EndpointFilter"?
>
>
> ++ Section 3.4 Information Model of ALTO Response ...
> - object CsoInfoResourceEndpointCostMap has the same structure than 
> InfoResourceEndpointCostMap of base protocol
> - what in the list of §3.2 does object 'DstCostsConstraints' refer to?
> - this object seem to be encoded like a set of JSONNumbers that are the 
> values of resp. hopcount, latency and packet loss. So I guess, they 
> should be arranged in an array.
> - why is this set of cost types already set at this level of 
> specification? 
>
>
> ++ Section 3.5 ALTO protocol extension...
> I agree with the idea of providing several Cost Type values at a time 
> but the encoding could be lighter. The draft "Multi-Cost ALTO" proposes 
> one example.
> There is a real need that this section be harmonized with the previous 
> specification sections, as the encoding provided in the examples are 
> misleading.
>
>
> ++ Section 4.1 Representing....
> - this section is rather about representing links and their attributes, 
> so could be named accordingly
> - the graph specification is curretnly a list of links, do you intend to 
> extend so that one can infer its structure?  
> - is there a reason preventing member 'r-cap' to be specified as 
> JSONNumber capacity?
> - what is the usage of wt at this level of a spec ? (could also be 
> 'JSONNumber weight')
>
> Leeyoung a écrit :
>   
>> Hi All,
>>
>> We have just published ALTO extension to support application and network resource information exchange for high bandwidth applications.
>> This is part of the i2aex initiative. 
>>
>> Thanks in advance for your comment and discussion. 
>>
>> Young
>>
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
>> Sent: Monday, July 09, 2012 11:06 AM
>> To: Leeyoung
>> Cc: choits@etri.re.kr; Sreekanth madhavan; gregb@grotto-networking.com; Dhruv Dhody
>> Subject: New Version Notification for draft-lee-alto-app-net-info-exchange-00.txt
>>
>>
>> A new version of I-D, draft-lee-alto-app-net-info-exchange-00.txt
>> has been successfully submitted by Young Lee and posted to the
>> IETF repository.
>>
>> Filename:	 draft-lee-alto-app-net-info-exchange
>> Revision:	 00
>> Title:		 ALTO Extensions to Support Application and Network Resource Information Exchange for High Bandwidth Applications
>> Creation date:	 2012-07-09
>> WG ID:		 Individual Submission
>> Number of pages: 14
>> URL:             http://www.ietf.org/internet-drafts/draft-lee-alto-app-net-info-exchange-00.txt
>> Status:          http://datatracker.ietf.org/doc/draft-lee-alto-app-net-info-exchange
>> Htmlized:        http://tools.ietf.org/html/draft-lee-alto-app-net-info-exchange-00
>>
>>
>> Abstract:
>> This draft proposes ALTO information model and protocol extensions to
>> support application and network resource information exchange for high
>> bandwidth applications in partially controlled and controlled
>> environments as part of the infrastructure to application information
>> exposure (i2aex) initiative.
>>
>>
>>
>>                                                                                   
>>
>>
>> The IETF Secretariat
>> _______________________________________________
>> altoext mailing list
>> altoext@ietf.org
>> https://www.ietf.org/mailman/listinfo/altoext
>>   
>>     
>
>   


From sabine.randriamasy@alcatel-lucent.com  Tue Jul 31 11:05:40 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 5EF3321F873A for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 11:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.674
X-Spam-Level: 
X-Spam-Status: No, score=-9.674 tagged_above=-999 required=5 tests=[AWL=0.575,  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 lm6c6D6ZTkuw for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 11:05:39 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id B726C21F8871 for <alto@ietf.org>; Tue, 31 Jul 2012 11:05:37 -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 q6VI5RoW019744 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 31 Jul 2012 20:05:32 +0200
Received: from [172.27.204.117] (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; Tue, 31 Jul 2012 20:05:10 +0200
Message-ID: <50181E51.9020102@alcatel-lucent.com>
Date: Tue, 31 Jul 2012 20:05:05 +0200
From: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Leeyoung <leeyoung@huawei.com>
References: <7AEB3D6833318045B4AE71C2C87E8E1720CC2D35@dfweml511-mbx.china.huawei.com> <5016C0DD.8050909@alcatel-lucent.com> <7AEB3D6833318045B4AE71C2C87E8E172905E4F5@dfweml511-mbs.china.huawei.com>
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E172905E4F5@dfweml511-mbs.china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; 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] [altoext] FW: New Version Notification	for	draft-lee-alto-app-net-info-exchange-00.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, 31 Jul 2012 18:05:40 -0000

Hi Young,

Thanks a lot for your answers. Please see some more comments inline.
Again with now the ALTO list in Cc
Best regards
Sabine

Leeyoung a écrit :
> Hi Sabine,
>
> Here's my response to your comments to your detail questions. Please see in-line.
> Sreekants or Greg may be able to provide more comments later. 
>
> Thanks,
> Young
>
> -----Original Message-----
> From: Sabine Randriamasy [mailto:Sabine.Randriamasy@alcatel-lucent.com] 
> Sent: Monday, July 30, 2012 12:14 PM
> To: Leeyoung
> Cc: altoext@ietf.org
> Subject: Re: [altoext] FW: New Version Notification for draft-lee-alto-app-net-info-exchange-00.txt
>
> Hi Young,
>
> I have read your draft and have a couple of comments and questions.
>
> In Section 2 Problem statement, I agree with the need to reduce the 
> amount of conveyed ALTO information through topology filtering and 
> constraint-based response filtering. The ALTO base protocol specifies 
> these features for the Cost Map, Filtered cost map and Endpoint cost 
> services. I also agree with the necessity to provide several types of 
> cost information which stresses the necessity of extended filtering 
> mechanisms. In the Constraints filtering extensions of Section 3, I 
> didnt' really get how information confidentiality is preserved and the 
> proposed specification raised the questions detailed below.
>
> I also agree that detailing end to end path costs at the link level at 
> some places can be beneficial, especially for local bottlenecks 
> sometimes with fast changing cost values. Figure 2 shows an example with 
> Link capacity costs but section 2 uses them rather as capacity, where I 
> figure the higher the better. Without a hint on how path costs are 
> calculated it is hard to follow the rationale on the DC choice by ER1. 
> See also the questions detailed below.
>
> Thanks,
> Sabine
>
> ------------------------- Detailed questions -----------------------------
>
> ++ Section 3.1 ALTO Query from Application Stratum to Network Stratum
> Names used in the list of requested information may be misleading:
> - A 'Cost Type' see base protocol (§5.1.1) is expected to indicate an 
> attribute that has a value such as number, boolean, string... and is is 
> rather "semantic". 'summary' and 'graph' are cost attributes of 
> different nature.
>
> YOUNG>> Thanks. Agreed. We may define a new cost attribute (TBD the name).
>
> - 'Constraints' such as 'min/max metric' look like objectives rather 
> than expressions such as 'lt. value' as specified in the base protocol 
> (§ 6.8.2.2.3)
>
> YOUNG>> In the encoding example we gave in the draft, we used the constraints
> Convention such as 'lt, gt, eq, ...' Please see Section 3.5.
>   
Ok. Then it may help if the text in §3.1 is reflecting such an 
expression of constraints.
>
> - what kind of information is member 'Parameters' is supposed to carry 
> and for what use?
>
> YOUNG>> We put it as a place holder for indicating values of the resulting graph or link
> representation of network abstraction, but in the actually encoding example, we simply used
> what is defined in DstCostsConstraints Object (such as pktloss, etc.) to indicate the vaules
> associated with the S-D path. We can delete it if this is not necessary. 
>   
Or maybe clarify the definition.
>
> - Some members listed here do not appear in the ALTO Query Information 
> Model of §3.3: 'parameters' 'objective-function'. Neither do they appear 
> in the example of §3.5
>
> YOUNG>> Good observation. We put them as a place holder for future enhancement. 
>
> ++ Section 3.2 ALTO response from Network ....
> - The list of S-D pairs should carry the Cost Type *values* as the 
> supported Cost Types are expected to be listed and checked in the IRD.
>
> YOUNG>> We did not mean not leaving it out. See Section 3.5 example if that satisfies your question. 
>   
Ok, then adding the *value* to "cost type" would fully clarify
>
> - 'Constraint values': need to be clarified: is it the actual cost 
> value? then the draft should specifiy that the constraits relate to Cost 
> Types (as defined in §5.1.1).
>
> YOUNG>> Yes. Agree. 
>
> - how is the 'Administration Domain ID' of a S-D pair reported and why 
> is it needed?  
>
> YOUNG>> Sorry for poor writing. We didn't mean this Admin Domain ID of a S-D pair. We actually meant here ALTO client may collect network resource information from different network domains in case of the multi-domain scenario. 
>   
ok
> ++ Section 3.3 Information Model of ALTO Query ...
> Looking at the specification here, it is hard to figure out what is 
> really extended here w.r.t. the Endpoint Cost Service query input 
> specified in the base protocol.
>
> YOUNG>> Agreed. We will indicate what is new in the revision.
>
> - A new media type "CsoReqEndpointCostMap" and differs from 
> "ReqEndpointCostMap" of the base protocol in that the set in member 
> 'contraints' is encoded/interpreted differently, according to example in 
> §3.5. Then a different member name than 'contraints' should be used.
>
> YOUNG>> Yes, we will make it clear. 
>   
Ok
>
> - As for member 'endpoints': unless you need to specify only 1 src EP, 
> what is the need to define a new object "EndpointFilterExt" instead of 
> keeping the "EndpointFilter"?
>
> YOUNG>> We may have a case in which to specify more than 1 src EP. The example is 
> Simply an example with only 1 src EP. We have other examples where multiple sources may need to be specified. 
>   
Ok. Then why not keeping "EndpointFilter"?
> ++ Section 3.4 Information Model of ALTO Response ...
> - object CsoInfoResourceEndpointCostMap has the same structure than 
> InfoResourceEndpointCostMap of base protocol
>
> YOUNG>> Yes, we did not mean to invent new object.
>   
Ok. I guess a later version with updated information models and examples 
will clarify this as well. 
> - what in the list of §3.2 does object 'DstCostsConstraints' refer to?
> - this object seem to be encoded like a set of JSONNumbers that are the 
> values of resp. hopcount, latency and packet loss. So I guess, they 
> should be arranged in an array.
>
> YOUNG>> Actually it refers to constraint values. I tend to agree with you. 
>
> - why is this set of cost types already set at this level of 
> specification? 
>
> YOUNG>> I don't understand this question. 
>   
I meant the list of cost types used in the constraints could be more 
generic.
> ++ Section 3.5 ALTO protocol extension...
> I agree with the idea of providing several Cost Type values at a time 
> but the encoding could be lighter. The draft "Multi-Cost ALTO" proposes 
> one example.
> There is a real need that this section be harmonized with the previous 
> specification sections, as the encoding provided in the examples are 
> misleading.
>
> YOUNG>> Yes, we should have referred to your multi-cost draft properly. We did not mean to propose a new thing with respect to multi-cost. We will clean up what is new and what is referenced in the revision. 
>   
Ok.
>
> ++ Section 4.1 Representing....
> - this section is rather about representing links and their attributes, 
> so could be named accordingly
>
> YOUNG>> We discussed this aspect previously. Do you have a good suggestion of
> Naming? 
>   
How about something like "Representing links and their attributes" ?
>
> - the graph specification is curretnly a list of links, do you intend to 
> extend so that one can infer its structure?  
>
> YOUNG>> Please look at draft-bernstein-alto-large-bandwidth-cases-02.txt for
> Further enhancement from this. We want to represent some path vector only with shared links and the link cost of those shared links so that some level of structure may be inferred by Application stratum.
>   
Ok.
>
> - is there a reason preventing member 'r-cap' to be specified as 
> JSONNumber capacity?
>
> YOUNG>> I think we can. But I defer this question to Greg.
>
> - what is the usage of wt at this level of a spec ? (could also be 
> 'JSONNumber weight')
>
> YOUNG>> Weight is similar to routing 'cost' notion of OSPF or other link cost that operators use for non-TE link cost. 
>   
I was mislead by the name 'wt' (sorry forgot the expression in the other 
draft). 
> Leeyoung a écrit :
>   
>> Hi All,
>>
>> We have just published ALTO extension to support application and network resource information exchange for high bandwidth applications.
>> This is part of the i2aex initiative. 
>>
>> Thanks in advance for your comment and discussion. 
>>
>> Young
>>
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
>> Sent: Monday, July 09, 2012 11:06 AM
>> To: Leeyoung
>> Cc: choits@etri.re.kr; Sreekanth madhavan; gregb@grotto-networking.com; Dhruv Dhody
>> Subject: New Version Notification for draft-lee-alto-app-net-info-exchange-00.txt
>>
>>
>> A new version of I-D, draft-lee-alto-app-net-info-exchange-00.txt
>> has been successfully submitted by Young Lee and posted to the
>> IETF repository.
>>
>> Filename:	 draft-lee-alto-app-net-info-exchange
>> Revision:	 00
>> Title:		 ALTO Extensions to Support Application and Network Resource Information Exchange for High Bandwidth Applications
>> Creation date:	 2012-07-09
>> WG ID:		 Individual Submission
>> Number of pages: 14
>> URL:             http://www.ietf.org/internet-drafts/draft-lee-alto-app-net-info-exchange-00.txt
>> Status:          http://datatracker.ietf.org/doc/draft-lee-alto-app-net-info-exchange
>> Htmlized:        http://tools.ietf.org/html/draft-lee-alto-app-net-info-exchange-00
>>
>>
>> Abstract:
>> This draft proposes ALTO information model and protocol extensions to
>> support application and network resource information exchange for high
>> bandwidth applications in partially controlled and controlled
>> environments as part of the infrastructure to application information
>> exposure (i2aex) initiative.
>>
>>
>>
>>                                                                                   
>>
>>
>> The IETF Secretariat
>> _______________________________________________
>> altoext mailing list
>> altoext@ietf.org
>> https://www.ietf.org/mailman/listinfo/altoext
>>   
>>     
>
>   


From leeyoung@huawei.com  Tue Jul 31 11:08:52 2012
Return-Path: <leeyoung@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 74B4421F88D0 for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 11:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.352
X-Spam-Level: 
X-Spam-Status: No, score=-5.352 tagged_above=-999 required=5 tests=[AWL=-1.053, BAYES_00=-2.599, MANGLED_NAIL=2.3, 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 ntXsksN3Ew55 for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 11:08:51 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 1047C21F88CC for <alto@ietf.org>; Tue, 31 Jul 2012 11:08:51 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AIM87321; Tue, 31 Jul 2012 14:08:50 -0400 (EDT)
Received: from DFWEML406-HUB.china.huawei.com (10.193.5.131) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 31 Jul 2012 11:06:04 -0700
Received: from dfweml511-mbs.china.huawei.com ([169.254.15.49]) by dfweml406-hub.china.huawei.com ([10.193.5.131]) with mapi id 14.01.0323.003; Tue, 31 Jul 2012 11:06:05 -0700
From: Leeyoung <leeyoung@huawei.com>
To: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
Thread-Topic: [altoext] FW: New Version Notification	for draft-lee-alto-app-net-info-exchange-00.txt
Thread-Index: AQHNbnbFyCKU9p001Ui91Q4XnV6GlJdCER3wgAII7QD//5YScA==
Date: Tue, 31 Jul 2012 18:06:04 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E172905E823@dfweml511-mbs.china.huawei.com>
References: <7AEB3D6833318045B4AE71C2C87E8E1720CC2D35@dfweml511-mbx.china.huawei.com> <5016C0DD.8050909@alcatel-lucent.com> <7AEB3D6833318045B4AE71C2C87E8E172905E3A2@dfweml511-mbs.china.huawei.com> <501813EA.2040808@alcatel-lucent.com>
In-Reply-To: <501813EA.2040808@alcatel-lucent.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.129.234]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] [altoext] FW: New Version Notification	for	draft-lee-alto-app-net-info-exchange-00.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, 31 Jul 2012 18:08:52 -0000

Hi Sabine,

Thanks for your further comments. Please see in-line for my response.

Best Regards,
Young
=20

-----Original Message-----
From: Sabine Randriamasy [mailto:Sabine.Randriamasy@alcatel-lucent.com]=20
Sent: Tuesday, July 31, 2012 12:21 PM
To: Leeyoung
Cc: alto@ietf.org
Subject: Re: [altoext] FW: New Version Notification for draft-lee-alto-app-=
net-info-exchange-00.txt


Hi Young,
Thanks for your answers. Please see inline for further comments.
I have put the "alto" list in Cc rather than "altoext" which will be closed=
.
Best regards
Sabine

Leeyoung a =E9crit :
> Hi Sabine,
>
> Thanks for providing your comments to our drafts. Please see in-line for =
my response.
>
> Best Regards,
> Young
>
> -----Original Message-----
> From: Sabine Randriamasy [mailto:Sabine.Randriamasy@alcatel-lucent.com]=20
> Sent: Monday, July 30, 2012 12:14 PM
> To: Leeyoung
> Cc: altoext@ietf.org
> Subject: Re: [altoext] FW: New Version Notification for draft-lee-alto-ap=
p-net-info-exchange-00.txt
>
> Hi Young,
>
> I have read your draft and have a couple of comments and questions.
>
> In Section 2 Problem statement, I agree with the need to reduce the=20
> amount of conveyed ALTO information through topology filtering and=20
> constraint-based response filtering. The ALTO base protocol specifies=20
> these features for the Cost Map, Filtered cost map and Endpoint cost=20
> services. I also agree with the necessity to provide several types of=20
> cost information which stresses the necessity of extended filtering=20
> mechanisms. In the Constraints filtering extensions of Section 3, I=20
> didnt' really get how information confidentiality is preserved and the=20
> proposed specification raised the questions detailed below.
>
> YOUNG>> Information confidentiality is a big issue which the current draf=
t has not addressed yet. The current draft was written in the "controlled" =
or "partially controlled" environments which means there is a trusted relat=
ionship amongst the entities involving the exchanges of resource data.=20
> In generic framework where there may be no such trusted relationship amon=
gst the entities, we need to address such issue down the road.=20
>  =20
Ok. Indeed, ALTO environment control is introduced in the Introduction.=20
I was mislead by seing "Such information may be considered sensitive to=20
the network provider just as..." just before "Section 3 provides ALTO=20
information model and protocol extensions to support... "

YOUNG>> We will clarify this.=20

> I also agree that detailing end to end path costs at the link level at=20
> some places can be beneficial, especially for local bottlenecks=20
> sometimes with fast changing cost values. Figure 2 shows an example with=
=20
> Link capacity costs but section 2 uses them rather as capacity, where I=20
> figure the higher the better. Without a hint on how path costs are=20
> calculated it is hard to follow the rationale on the DC choice by ER1.=20
> See also the questions detailed below.
>
> YOUNG>> We actually enhanced this mechanism in section 6 of  draft-bernst=
ein-alto-large-bandwidth-cases-02.txt
> where we include path vector along with link b/w. Path vector indicates s=
hared link information from which
> The bottle neck link can be identified.=20
>
> For instance, consider the following example from the draft.=20
>
>
>          +----+                  L0 Wt=3D10,BW=3D50         +----+
>          | N0 |-----------------------------------------| N3 |
>          +----+  `.                                     +----+
>            |       `. L4 Wt=3D7                             |
>            |         `-. BW=3D40                            |
>            |            `.  +----+                        |
>            |              `.| N4 |                        |
>            | L1          .' +----+                        |
>            | Wt=3D10      /                          L2     |
>            | BW=3D45     /                           Wt=3D12  |
>            |          /L5 Wt=3D10                    BW=3D30  |
>            |        .'    BW=3D45                           |
>            |       /                                      |
>            |      /                                       |
>          +----+ .'              L3 Wt=3D15 BW=3D42          +----+
>          | N1 |.........................................| N2 |
>          +----+                                         +----+
>
> Now suppose the network of Figure 1 is a TDM network controlled by=20
> GMPLS. Once again N0 representing a large data center and nodes N2
> and N3 as potential clients. However in this case the network provider=20
> offers an additional path, P3, for getting from N0-N2.
>
>    Path  Src-Dest    Path Vector    Path Cost
>
>    P1    N0-N2       {L0, L2}       22
>    P2    N0-N3       {L0}           10
>    P3    N0-N2       {L1,L3}        25
>    ----------------------------------
>    Link        Bandwidth
>    L0             50
>    L1             45
>    L2             30
>    L3             42
>
> So the draft now propose that the network can provide abstract path=20
> list along with link bottlenecks. We also provide how this mechanism=20
> works for IP and other types of networks.=20
>  =20
I'm fine with the rationale in=20
draft-bernstein-alto-large-bandwidth-cases-02.txt. It's just that in=20
draft-lee-alto-app-net-info-exchange-00.txt I missed the relation=20
between the "LinkCapacity Cost" & ALTO Cost Map in Figure 2 and also the=20
explanatory text text. Maybe a little clarifying edition can help. =20


YOUNG>> Yes, we will clarify in the revision. We did not have time to synch=
ronize between uses-case 01 and 02.

> I will provide the responses to your detail questions later.=20
> Thanks.=20
>
> Young
>
>
>
>         =20
>
> Thanks,
> Sabine
>
> ------------------------- Detailed questions ----------------------------=
-
>
> ++ Section 3.1 ALTO Query from Application Stratum to Network Stratum
> Names used in the list of requested information may be misleading:
> - A 'Cost Type' see base protocol (=A75.1.1) is expected to indicate an=20
> attribute that has a value such as number, boolean, string... and is is=20
> rather "semantic". 'summary' and 'graph' are cost attributes of=20
> different nature.
> - 'Constraints' such as 'min/max metric' look like objectives rather=20
> than expressions such as 'lt. value' as specified in the base protocol=20
> (=A7 6.8.2.2.3)
> - what kind of information is member 'Parameters' is supposed to carry=20
> and for what use?
> - Some members listed here do not appear in the ALTO Query Information=20
> Model of =A73.3: 'parameters' 'objective-function'. Neither do they appea=
r=20
> in the example of =A73.5
>
>
> ++ Section 3.2 ALTO response from Network ....
> - The list of S-D pairs should carry the Cost Type *values* as the=20
> supported Cost Types are expected to be listed and checked in the IRD.
> - 'Constraint values': need to be clarified: is it the actual cost=20
> value? then the draft should specifiy that the constraits relate to Cost=
=20
> Types (as defined in =A75.1.1).
> - how is the 'Administration Domain ID' of a S-D pair reported and why=20
> is it needed? =20
>
>
> ++ Section 3.3 Information Model of ALTO Query ...
> Looking at the specification here, it is hard to figure out what is=20
> really extended here w.r.t. the Endpoint Cost Service query input=20
> specified in the base protocol.
> - A new media type "CsoReqEndpointCostMap" and differs from=20
> "ReqEndpointCostMap" of the base protocol in that the set in member=20
> 'contraints' is encoded/interpreted differently, according to example in=
=20
> =A73.5. Then a different member name than 'contraints' should be used.
> - As for member 'endpoints': unless you need to specify only 1 src EP,=20
> what is the need to define a new object "EndpointFilterExt" instead of=20
> keeping the "EndpointFilter"?
>
>
> ++ Section 3.4 Information Model of ALTO Response ...
> - object CsoInfoResourceEndpointCostMap has the same structure than=20
> InfoResourceEndpointCostMap of base protocol
> - what in the list of =A73.2 does object 'DstCostsConstraints' refer to?
> - this object seem to be encoded like a set of JSONNumbers that are the=20
> values of resp. hopcount, latency and packet loss. So I guess, they=20
> should be arranged in an array.
> - why is this set of cost types already set at this level of=20
> specification?=20
>
>
> ++ Section 3.5 ALTO protocol extension...
> I agree with the idea of providing several Cost Type values at a time=20
> but the encoding could be lighter. The draft "Multi-Cost ALTO" proposes=20
> one example.
> There is a real need that this section be harmonized with the previous=20
> specification sections, as the encoding provided in the examples are=20
> misleading.
>
>
> ++ Section 4.1 Representing....
> - this section is rather about representing links and their attributes,=20
> so could be named accordingly
> - the graph specification is curretnly a list of links, do you intend to=
=20
> extend so that one can infer its structure? =20
> - is there a reason preventing member 'r-cap' to be specified as=20
> JSONNumber capacity?
> - what is the usage of wt at this level of a spec ? (could also be=20
> 'JSONNumber weight')
>
> Leeyoung a =E9crit :
>  =20
>> Hi All,
>>
>> We have just published ALTO extension to support application and network=
 resource information exchange for high bandwidth applications.
>> This is part of the i2aex initiative.=20
>>
>> Thanks in advance for your comment and discussion.=20
>>
>> Young
>>
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20
>> Sent: Monday, July 09, 2012 11:06 AM
>> To: Leeyoung
>> Cc: choits@etri.re.kr; Sreekanth madhavan; gregb@grotto-networking.com; =
Dhruv Dhody
>> Subject: New Version Notification for draft-lee-alto-app-net-info-exchan=
ge-00.txt
>>
>>
>> A new version of I-D, draft-lee-alto-app-net-info-exchange-00.txt
>> has been successfully submitted by Young Lee and posted to the
>> IETF repository.
>>
>> Filename:	 draft-lee-alto-app-net-info-exchange
>> Revision:	 00
>> Title:		 ALTO Extensions to Support Application and Network Resource Inf=
ormation Exchange for High Bandwidth Applications
>> Creation date:	 2012-07-09
>> WG ID:		 Individual Submission
>> Number of pages: 14
>> URL:             http://www.ietf.org/internet-drafts/draft-lee-alto-app-=
net-info-exchange-00.txt
>> Status:          http://datatracker.ietf.org/doc/draft-lee-alto-app-net-=
info-exchange
>> Htmlized:        http://tools.ietf.org/html/draft-lee-alto-app-net-info-=
exchange-00
>>
>>
>> Abstract:
>> This draft proposes ALTO information model and protocol extensions to
>> support application and network resource information exchange for high
>> bandwidth applications in partially controlled and controlled
>> environments as part of the infrastructure to application information
>> exposure (i2aex) initiative.
>>
>>
>>
>>                                                                         =
         =20
>>
>>
>> The IETF Secretariat
>> _______________________________________________
>> altoext mailing list
>> altoext@ietf.org
>> https://www.ietf.org/mailman/listinfo/altoext
>>  =20
>>    =20
>
>  =20


From leeyoung@huawei.com  Tue Jul 31 11:16:10 2012
Return-Path: <leeyoung@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 61A0421F88A8 for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 11:16:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.436
X-Spam-Level: 
X-Spam-Status: No, score=-6.436 tagged_above=-999 required=5 tests=[AWL=0.163,  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 l3rKU+JOUP22 for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 11:16:09 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 0B78421F88A2 for <alto@ietf.org>; Tue, 31 Jul 2012 11:16:08 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AIM87789; Tue, 31 Jul 2012 14:16:08 -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; Tue, 31 Jul 2012 11:14:35 -0700
Received: from dfweml511-mbs.china.huawei.com ([169.254.15.49]) by dfweml407-hub.china.huawei.com ([10.193.5.132]) with mapi id 14.01.0323.003; Tue, 31 Jul 2012 11:14:30 -0700
From: Leeyoung <leeyoung@huawei.com>
To: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
Thread-Topic: [altoext] FW: New Version Notification	for draft-lee-alto-app-net-info-exchange-00.txt
Thread-Index: AQHNbnbFyCKU9p001Ui91Q4XnV6GlJdCZ+tQgAG+hoD//4sF0A==
Date: Tue, 31 Jul 2012 18:14:29 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E172905E833@dfweml511-mbs.china.huawei.com>
References: <7AEB3D6833318045B4AE71C2C87E8E1720CC2D35@dfweml511-mbx.china.huawei.com> <5016C0DD.8050909@alcatel-lucent.com> <7AEB3D6833318045B4AE71C2C87E8E172905E4F5@dfweml511-mbs.china.huawei.com> <50181E51.9020102@alcatel-lucent.com>
In-Reply-To: <50181E51.9020102@alcatel-lucent.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.129.234]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] [altoext] FW: New Version Notification	for	draft-lee-alto-app-net-info-exchange-00.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, 31 Jul 2012 18:16:10 -0000

Hi Sabine,

Thanks again for your further comment. Please see in-line for my response.

Best Regards,
Young

-----Original Message-----
From: Sabine Randriamasy [mailto:Sabine.Randriamasy@alcatel-lucent.com]=20
Sent: Tuesday, July 31, 2012 1:05 PM
To: Leeyoung
Cc: alto@ietf.org
Subject: Re: [altoext] FW: New Version Notification for draft-lee-alto-app-=
net-info-exchange-00.txt


Hi Young,

Thanks a lot for your answers. Please see some more comments inline.
Again with now the ALTO list in Cc
Best regards
Sabine

Leeyoung a =E9crit :
> Hi Sabine,
>
> Here's my response to your comments to your detail questions. Please see =
in-line.
> Sreekants or Greg may be able to provide more comments later.=20
>
> Thanks,
> Young
>
> -----Original Message-----
> From: Sabine Randriamasy [mailto:Sabine.Randriamasy@alcatel-lucent.com]=20
> Sent: Monday, July 30, 2012 12:14 PM
> To: Leeyoung
> Cc: altoext@ietf.org
> Subject: Re: [altoext] FW: New Version Notification for draft-lee-alto-ap=
p-net-info-exchange-00.txt
>
> Hi Young,
>
> I have read your draft and have a couple of comments and questions.
>
> In Section 2 Problem statement, I agree with the need to reduce the=20
> amount of conveyed ALTO information through topology filtering and=20
> constraint-based response filtering. The ALTO base protocol specifies=20
> these features for the Cost Map, Filtered cost map and Endpoint cost=20
> services. I also agree with the necessity to provide several types of=20
> cost information which stresses the necessity of extended filtering=20
> mechanisms. In the Constraints filtering extensions of Section 3, I=20
> didnt' really get how information confidentiality is preserved and the=20
> proposed specification raised the questions detailed below.
>
> I also agree that detailing end to end path costs at the link level at=20
> some places can be beneficial, especially for local bottlenecks=20
> sometimes with fast changing cost values. Figure 2 shows an example with=
=20
> Link capacity costs but section 2 uses them rather as capacity, where I=20
> figure the higher the better. Without a hint on how path costs are=20
> calculated it is hard to follow the rationale on the DC choice by ER1.=20
> See also the questions detailed below.
>
> Thanks,
> Sabine
>
> ------------------------- Detailed questions ----------------------------=
-
>
> ++ Section 3.1 ALTO Query from Application Stratum to Network Stratum
> Names used in the list of requested information may be misleading:
> - A 'Cost Type' see base protocol (=A75.1.1) is expected to indicate an=20
> attribute that has a value such as number, boolean, string... and is is=20
> rather "semantic". 'summary' and 'graph' are cost attributes of=20
> different nature.
>
> YOUNG>> Thanks. Agreed. We may define a new cost attribute (TBD the name)=
.
>
> - 'Constraints' such as 'min/max metric' look like objectives rather=20
> than expressions such as 'lt. value' as specified in the base protocol=20
> (=A7 6.8.2.2.3)
>
> YOUNG>> In the encoding example we gave in the draft, we used the constra=
ints
> Convention such as 'lt, gt, eq, ...' Please see Section 3.5.
>  =20
Ok. Then it may help if the text in =A73.1 is reflecting such an=20
expression of constraints.

YOUNG>> Yes we will add explanation text in Section 3.1 on these constraint=
s convention.=20
>
> - what kind of information is member 'Parameters' is supposed to carry=20
> and for what use?
>
> YOUNG>> We put it as a place holder for indicating values of the resultin=
g graph or link
> representation of network abstraction, but in the actually encoding examp=
le, we simply used
> what is defined in DstCostsConstraints Object (such as pktloss, etc.) to =
indicate the vaules
> associated with the S-D path. We can delete it if this is not necessary.=
=20
>  =20
Or maybe clarify the definition.

YOUNG>> Yes. Will provide.=20
>
> - Some members listed here do not appear in the ALTO Query Information=20
> Model of =A73.3: 'parameters' 'objective-function'. Neither do they appea=
r=20
> in the example of =A73.5
>
> YOUNG>> Good observation. We put them as a place holder for future enhanc=
ement.=20
>
> ++ Section 3.2 ALTO response from Network ....
> - The list of S-D pairs should carry the Cost Type *values* as the=20
> supported Cost Types are expected to be listed and checked in the IRD.
>
> YOUNG>> We did not mean not leaving it out. See Section 3.5 example if th=
at satisfies your question.=20
>  =20
Ok, then adding the *value* to "cost type" would fully clarify

YOUNG>> OK.

>
> - 'Constraint values': need to be clarified: is it the actual cost=20
> value? then the draft should specifiy that the constraits relate to Cost=
=20
> Types (as defined in =A75.1.1).
>
> YOUNG>> Yes. Agree.=20
>
> - how is the 'Administration Domain ID' of a S-D pair reported and why=20
> is it needed? =20
>
> YOUNG>> Sorry for poor writing. We didn't mean this Admin Domain ID of a =
S-D pair. We actually meant here ALTO client may collect network resource i=
nformation from different network domains in case of the multi-domain scena=
rio.=20
>  =20
ok
> ++ Section 3.3 Information Model of ALTO Query ...
> Looking at the specification here, it is hard to figure out what is=20
> really extended here w.r.t. the Endpoint Cost Service query input=20
> specified in the base protocol.
>
> YOUNG>> Agreed. We will indicate what is new in the revision.
>
> - A new media type "CsoReqEndpointCostMap" and differs from=20
> "ReqEndpointCostMap" of the base protocol in that the set in member=20
> 'contraints' is encoded/interpreted differently, according to example in=
=20
> =A73.5. Then a different member name than 'contraints' should be used.
>
> YOUNG>> Yes, we will make it clear.=20
>  =20
Ok
>
> - As for member 'endpoints': unless you need to specify only 1 src EP,=20
> what is the need to define a new object "EndpointFilterExt" instead of=20
> keeping the "EndpointFilter"?
>
> YOUNG>> We may have a case in which to specify more than 1 src EP. The ex=
ample is=20
> Simply an example with only 1 src EP. We have other examples where multip=
le sources may need to be specified.=20
>  =20
Ok. Then why not keeping "EndpointFilter"?

YOUNG>>=20
> ++ Section 3.4 Information Model of ALTO Response ...
> - object CsoInfoResourceEndpointCostMap has the same structure than=20
> InfoResourceEndpointCostMap of base protocol
>
> YOUNG>> Yes, we did not mean to invent new object.
>  =20
Ok. I guess a later version with updated information models and examples=20
will clarify this as well.=20

YOUNG>> Will clarify this in the revision.

> - what in the list of =A73.2 does object 'DstCostsConstraints' refer to?
> - this object seem to be encoded like a set of JSONNumbers that are the=20
> values of resp. hopcount, latency and packet loss. So I guess, they=20
> should be arranged in an array.
>
> YOUNG>> Actually it refers to constraint values. I tend to agree with you=
.=20
>
> - why is this set of cost types already set at this level of=20
> specification?=20
>
> YOUNG>> I don't understand this question.=20
>  =20
I meant the list of cost types used in the constraints could be more=20
generic.

YOUNG>> Let's discuss this point face-to-face.=20

> ++ Section 3.5 ALTO protocol extension...
> I agree with the idea of providing several Cost Type values at a time=20
> but the encoding could be lighter. The draft "Multi-Cost ALTO" proposes=20
> one example.
> There is a real need that this section be harmonized with the previous=20
> specification sections, as the encoding provided in the examples are=20
> misleading.
>
> YOUNG>> Yes, we should have referred to your multi-cost draft properly. W=
e did not mean to propose a new thing with respect to multi-cost. We will c=
lean up what is new and what is referenced in the revision.=20
>  =20
Ok.
>
> ++ Section 4.1 Representing....
> - this section is rather about representing links and their attributes,=20
> so could be named accordingly
>
> YOUNG>> We discussed this aspect previously. Do you have a good suggestio=
n of
> Naming?=20
>  =20
How about something like "Representing links and their attributes" ?

YOUNG>> This sounds good to me.=20

>
> - the graph specification is curretnly a list of links, do you intend to=
=20
> extend so that one can infer its structure? =20
>
> YOUNG>> Please look at draft-bernstein-alto-large-bandwidth-cases-02.txt =
for
> Further enhancement from this. We want to represent some path vector only=
 with shared links and the link cost of those shared links so that some lev=
el of structure may be inferred by Application stratum.
>  =20
Ok.
>
> - is there a reason preventing member 'r-cap' to be specified as=20
> JSONNumber capacity?
>
> YOUNG>> I think we can. But I defer this question to Greg.
>
> - what is the usage of wt at this level of a spec ? (could also be=20
> 'JSONNumber weight')
>
> YOUNG>> Weight is similar to routing 'cost' notion of OSPF or other link =
cost that operators use for non-TE link cost.=20
>  =20
I was mislead by the name 'wt' (sorry forgot the expression in the other=20
draft).=20

YOUNG>> OK

> Leeyoung a =E9crit :
>  =20
>> Hi All,
>>
>> We have just published ALTO extension to support application and network=
 resource information exchange for high bandwidth applications.
>> This is part of the i2aex initiative.=20
>>
>> Thanks in advance for your comment and discussion.=20
>>
>> Young
>>
>> -----Original Message-----
>> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]=20
>> Sent: Monday, July 09, 2012 11:06 AM
>> To: Leeyoung
>> Cc: choits@etri.re.kr; Sreekanth madhavan; gregb@grotto-networking.com; =
Dhruv Dhody
>> Subject: New Version Notification for draft-lee-alto-app-net-info-exchan=
ge-00.txt
>>
>>
>> A new version of I-D, draft-lee-alto-app-net-info-exchange-00.txt
>> has been successfully submitted by Young Lee and posted to the
>> IETF repository.
>>
>> Filename:	 draft-lee-alto-app-net-info-exchange
>> Revision:	 00
>> Title:		 ALTO Extensions to Support Application and Network Resource Inf=
ormation Exchange for High Bandwidth Applications
>> Creation date:	 2012-07-09
>> WG ID:		 Individual Submission
>> Number of pages: 14
>> URL:             http://www.ietf.org/internet-drafts/draft-lee-alto-app-=
net-info-exchange-00.txt
>> Status:          http://datatracker.ietf.org/doc/draft-lee-alto-app-net-=
info-exchange
>> Htmlized:        http://tools.ietf.org/html/draft-lee-alto-app-net-info-=
exchange-00
>>
>>
>> Abstract:
>> This draft proposes ALTO information model and protocol extensions to
>> support application and network resource information exchange for high
>> bandwidth applications in partially controlled and controlled
>> environments as part of the infrastructure to application information
>> exposure (i2aex) initiative.
>>
>>
>>
>>                                                                         =
         =20
>>
>>
>> The IETF Secretariat
>> _______________________________________________
>> altoext mailing list
>> altoext@ietf.org
>> https://www.ietf.org/mailman/listinfo/altoext
>>  =20
>>    =20
>
>  =20


From stpeter@stpeter.im  Tue Jul 31 11:26:43 2012
Return-Path: <stpeter@stpeter.im>
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 6E68721F894B for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 11:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level: 
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, 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 R7kGUgdATdil for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 11:26:42 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 9AADD21F8940 for <alto@ietf.org>; Tue, 31 Jul 2012 11:26:42 -0700 (PDT)
Received: from [64.101.72.45] (unknown [64.101.72.45]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 383804009B; Tue, 31 Jul 2012 12:46:26 -0600 (MDT)
Message-ID: <50182360.40601@stpeter.im>
Date: Tue, 31 Jul 2012 12:26:40 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "Diego R. Lopez" <diego@tid.es>
References: <5003C514.70806@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC0EA7@szxeml523-mbs.china.huawei.com> <500956C6.6050809@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F08@szxeml523-mbs.china.huawei.com> <500D00C9.6070706@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F55@szxeml523-mbs.china.huawei.com> <500E7B90.9030902@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F7C@szxeml523-mbs.china.huawei.com> <500FA3BC.5040003@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F9B@szxeml523-mbs.china.huawei.com> <CANUuoLp47j8ekOQ37T04eLUTH_pRfyRNBHhUFJhXTBER40RHkA@mail.gmail.com> <D209E532-B82C-4D5A-A92F-11936B6F58C9@tid.es>
In-Reply-To: <D209E532-B82C-4D5A-A92F-11936B6F58C9@tid.es>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WebSocket-based notifications
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, 31 Jul 2012 18:26:43 -0000

On 7/29/12 5:43 PM, Diego R. Lopez wrote:
> Hi,
> 
> Just to add another bit of confusion...
> 
> When reading this thread I was wondering whether a solution based on
> bi-directional data streams, that would keep one single connection per
> client-server association while allowing for different resources to be
> queried and updated, could be considered.
> 
> What I have in mind is the use of XMPP for bi-directional ALTO
> interactions. Apart from the features outlined in the paragraph above, it
> does fit well with ALTO encoding and operational semantics, and
> there is a well established corpus of (many of them open) implementations.

It certainly seems to me that we could use XMPP here. However, I'll need
to read draft-marocco-alto-ws before providing more detailed comments. :)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From ietf@meetecho.com  Tue Jul 31 16:05:15 2012
Return-Path: <ietf@meetecho.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 7ACFA21F880B for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 16:05:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.541
X-Spam-Level: 
X-Spam-Status: No, score=0.541 tagged_above=-999 required=5 tests=[AWL=-0.700,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_BL_SPAMCOP_NET=1.96]
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 54eJowsl0c0W for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 16:05:15 -0700 (PDT)
Received: from smtplq04.aruba.it (smtplqs-out18.aruba.it [62.149.158.58]) by ietfa.amsl.com (Postfix) with SMTP id 8C30E21F8795 for <alto@ietf.org>; Tue, 31 Jul 2012 16:05:14 -0700 (PDT)
Received: (qmail 17023 invoked by uid 89); 31 Jul 2012 23:05:12 -0000
Received: from unknown (HELO smtp8.aruba.it) (62.149.158.228) by smtplq04.aruba.it with SMTP; 31 Jul 2012 23:05:12 -0000
Received: (qmail 1785 invoked by uid 89); 31 Jul 2012 23:05:12 -0000
Received: from unknown (HELO ?130.129.21.177?) (alex@meetecho.com@130.129.21.177) by smtp8.ad.aruba.it with ESMTPA; 31 Jul 2012 23:05:12 -0000
Message-ID: <501864A5.4000806@meetecho.com>
Date: Wed, 01 Aug 2012 01:05:09 +0200
From: Meetecho IETF support <ietf@meetecho.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: alto@ietf.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: smtplq04.aruba.it 1.6.2 0/1000/N
Subject: [alto] Meetecho support for ALTO WG
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, 31 Jul 2012 23:05:15 -0000

Hi all,

a virtual room has been reserved on the Meetecho system for today's
ALTO WG meeting session.

Access to the on-line session (including audio and video streams) will
be available at:
http://www.meetecho.com/ietf84/alto

The Meetecho session automatically logs you into the standard IETF
jabber room. So, from there, you can have an integrated experience
involving all media and allowing you to interact with the room.
Remote participants might also send their own voice to the room, if they
want to, by either calling a landline phone number, or using our
embedded VoIP applet (in this last case they are *strongly* advised to
use a headset).

A tutorial of interactivity features of the tool can be found at:
http://www.meetecho.com/ietf84

Cheers,
the Meetecho team

-- 
Meetecho s.r.l.
Web Conferencing and Collaboration Tools
www.meetecho.com

From emile.stephan@orange.com  Tue Jul 31 17:55:24 2012
Return-Path: <emile.stephan@orange.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 A3B6D21F881E for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 17:55:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=0.001]
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 ord4jUr44rxh for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 17:55:23 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 597E221F880C for <alto@ietf.org>; Tue, 31 Jul 2012 17:55:23 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id B86813B4439; Wed,  1 Aug 2012 02:55:22 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 9596D238048; Wed,  1 Aug 2012 02:55:22 +0200 (CEST)
Received: from PEXCVZYM14.corporate.adroot.infra.ftgroup ([fe80::a42f:c628:bc76:d592]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0298.004; Wed, 1 Aug 2012 02:55:22 +0200
From: <emile.stephan@orange.com>
To: "Jan Seedorf (Jan.Seedorf@neclab.eu)" <Jan.Seedorf@neclab.eu>, "Enrico Marocco (enrico.marocco@telecomitalia.it)" <enrico.marocco@telecomitalia.it>
Thread-Topic: netconf over WS & netconf RFC on  subscription and notification
Thread-Index: Ac1vgDsLkBEDtH24RuerxsEgaZrtzQ==
Date: Wed, 1 Aug 2012 00:55:21 +0000
Message-ID: <7642_1343782522_50187E7A_7642_5931_1_5AE9CCAA1B4A2248AB61B4C7F0AD5FB903FA5A@PEXCVZYM14.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.2]
Content-Type: multipart/alternative; boundary="_000_5AE9CCAA1B4A2248AB61B4C7F0AD5FB903FA5APEXCVZYM14corpora_"
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.7.31.223622
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: [alto] netconf over WS & netconf RFC on subscription and notification
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, 01 Aug 2012 00:55:24 -0000

--_000_5AE9CCAA1B4A2248AB61B4C7F0AD5FB903FA5APEXCVZYM14corpora_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Jan and Enrico,

Here are the NETCONF rfcs (extracted from the tutorial made by J=FCrgen on =
Sunday http://cnds.eecs.jacobs-university.de/slides/2012-ietf-84-netconf-ya=
ng.pdf )

RFC 6241 PS NETCONF Protocol Version 1.1
RFC 6242 PS NETCONF over SSH Version 1.1
RFC 6243 PS NETCONF With-defaults Capability
RFC 6470 PS NETCONF Base Notications
RFC 6536 PS NETCONF Access Control Model
RFC 5717 PS NETCONF Partial Locking
RFC 5277 PS NETCONF Event Notications
RFC 6022 PS NETCONF Monitoring
RFC 6244 I NETCONF / YANG Architecture

Further RFCs define additional transports

Current proposal related to WebSocket  http://tools.ietf.org/agenda/84/slid=
es/slides-84-netconf-2.pdf

Regards
Emile

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


--_000_5AE9CCAA1B4A2248AB61B4C7F0AD5FB903FA5APEXCVZYM14corpora_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"FR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Jan and Enrico,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Here are the NETCONF rfcs (extr=
acted from the tutorial made by J=FCrgen on Sunday
<a href=3D"http://cnds.eecs.jacobs-university.de/slides/2012-ietf-84-netcon=
f-yang.pdf">
http://cnds.eecs.jacobs-university.de/slides/2012-ietf-84-netconf-yang.pdf<=
/a> )<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">RFC 6241 PS NETCONF Protocol Version 1.1<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">RFC 6242 PS NETCONF over SSH Ve=
rsion 1.1<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">RFC 6243 PS NETCONF With-defaul=
ts Capability<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">RFC 6470 PS NETCONF Base Notica=
tions<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">RFC 6536 PS NETCONF Access Cont=
rol Model<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">RFC 5717 PS NETCONF Partial Loc=
king<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">RFC 5277 PS NETCONF Event Notic=
ations<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">RFC 6022 PS NETCONF Monitoring<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">RFC 6244 I NETCONF / YANG Archi=
tecture<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Further RFCs define additional =
transports<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Current proposal related to Web=
Socket &nbsp;</span><a href=3D"http://tools.ietf.org/agenda/84/slides/slide=
s-84-netconf-2.pdf"><span lang=3D"EN-US">http://tools.ietf.org/agenda/84/sl=
ides/slides-84-netconf-2.pdf</span></a><span lang=3D"EN-US"><o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">Regards<o:p></o:p></p>
<p class=3D"MsoNormal">Emile<o:p></o:p></p>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.
</PRE></body>
</html>

--_000_5AE9CCAA1B4A2248AB61B4C7F0AD5FB903FA5APEXCVZYM14corpora_--
