
From vkg@bell-labs.com  Tue Jun  5 06:27:04 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 5C53C21F86AF for <alto@ietfa.amsl.com>; Tue,  5 Jun 2012 06:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.8
X-Spam-Level: 
X-Spam-Status: No, score=-105.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799, 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 mwN3KLBZY5lz for <alto@ietfa.amsl.com>; Tue,  5 Jun 2012 06:27:04 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 43F2C21F8665 for <alto@ietf.org>; Tue,  5 Jun 2012 06:26:59 -0700 (PDT)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q55DQwiI019937 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <alto@ietf.org>; Tue, 5 Jun 2012 08:26:58 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q55DQw1U029651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Tue, 5 Jun 2012 08:26:58 -0500
Received: from shoonya.ih.lucent.com (shoonya.mh.lucent.com [135.222.138.246]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q55DQvrA009998 for <alto@ietf.org>; Tue, 5 Jun 2012 08:26:57 -0500 (CDT)
Message-ID: <4FCE0A70.2080501@bell-labs.com>
Date: Tue, 05 Jun 2012 08:32:32 -0500
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: alto <alto@ietf.org>
References: <4FCE07D1.8030102@neclab.eu>
In-Reply-To: <4FCE07D1.8030102@neclab.eu>
X-Forwarded-Message-Id: <4FCE07D1.8030102@neclab.eu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: [alto] Fwd: Call for Papers: IAB/IRTF Workshop on Congestion Control for Interactive Real-Time Communication, July 28, 2012 Vancouver, Canada
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, 05 Jun 2012 13:27:04 -0000

---------- Forwarded message ----------
From: IAB Chair <iab-chair@iab.org>
Date: Wed, May 23, 2012 at 12:47 PM
Subject: [IAB] Call for Papers: IAB/IRTF Workshop on Congestion
Control for Interactive Real-Time Communication, July 28, 2012
Vancouver, Canada
To: ietf-announce@ietf.org
Cc: iab@iab.org


IAB / IRTF Workshop on
Congestion Control for Interactive
Real-Time Communication

July 28, 2012
Vancouver, Canada



The IAB and IRTF will hold a workshop on Congestion Control for
Interactive Real-Time Communication" in Vancouver, Canada on Saturday,
July 28th, 2012 prior to the IETF-84 meeting (see
http://www.ietf.org/meeting/84/index.html).  Participation at the
workshop is free of charge. There is no requirement to either register
with or attend the IETF-84 meeting that follows the workshop.



The workshop organizers would like to foster a discussion on:

What are appropriate congestion signals to use for interactive media and
data?
What existing congestion control algorithms are appropriate for
interactive media and data? What properties would be desirable in new
congestion control algorithms?
Measurement and/or simulations of new congestion signals (e.g.,
delay-based) and their interaction with existing congestion control
mechanisms.
What are good available techniques for adjusting sending rates for
interactive media and data? What are the limits of those techniques?
What properties would be desirable in new techniques?
What application-specific considerations have to be taken into account?
How can we ensure that real-time communications are well-behaved with
respect to other Internet applications while still providing good
quality?
What should the IETF and/or IRTF do?

The organizers seek position papers on any or all of these topics, as
well as other topics related to congestion control for interactive
realtime media.



Every prospective workshop participant must submit a position paper
containing a name and an email address. Authors of accepted papers
will be invited to the workshop. Papers up to 3 pages, formatted in
HTML, PDF, or plain text (for example, as a submitted Internet-Draft)
are ideal. Accepted position papers will be published.  Additional
details about the meeting venue will be provided to authors of
accepted papers.

Important Dates

Position paper submission deadline:          June 23, 2012
Notification to paper authors:                       June 30, 2012
Workshop date:                                             July 28, 2012

Additional Details

Additional details on the workshop as well as the submission process
is available at http://www.iab.org/cc-workshop/

Contact

To sponsors: If you are interested to help us working towards better
interactive media congestion control mechanisms on the Internet (such
as by making a contribution towards catering costs and room rental),
please contact us!

In case of questions please send email to mary.ietf.barnes at gmail.com.

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

- 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 w.roome@alcatel-lucent.com  Wed Jun  6 08:18:03 2012
Return-Path: <w.roome@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 2041921F88BB for <alto@ietfa.amsl.com>; Wed,  6 Jun 2012 08:18:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 0YVwum-RCf-0 for <alto@ietfa.amsl.com>; Wed,  6 Jun 2012 08:18:02 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 68D5321F88B9 for <alto@ietf.org>; Wed,  6 Jun 2012 08:18:02 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q56FI1FS020154 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <alto@ietf.org>; Wed, 6 Jun 2012 10:18:01 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q56FI0EF014472 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Wed, 6 Jun 2012 10:18:01 -0500
Received: from [135.222.152.198] (wdr-i7mbp.mh.lucent.com [135.222.152.198]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q56FHwKh011669 for <alto@ietf.org>; Wed, 6 Jun 2012 10:17:59 -0500 (CDT)
User-Agent: Microsoft-MacOutlook/14.2.2.120421
Date: Wed, 06 Jun 2012 11:17:58 -0400
From: Bill Roome <w.roome@alcatel-lucent.com>
To: <alto@ietf.org>
Message-ID: <CBF4EA37.DD6D%w.roome@alcatel-lucent.com>
Thread-Topic: Ordinal costs for filtered requests
In-Reply-To: <CBF4E04F.DD08%alto-request@ietf.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
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: Wed, 06 Jun 2012 15:18:03 -0000

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.

	- Bill Roome



From w.roome@alcatel-lucent.com  Wed Jun  6 10:01:18 2012
Return-Path: <w.roome@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 3934721F8735 for <alto@ietfa.amsl.com>; Wed,  6 Jun 2012 10:01:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.901
X-Spam-Level: 
X-Spam-Status: No, score=-7.901 tagged_above=-999 required=5 tests=[AWL=-2.699, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, 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 Pz-F++udF7u5 for <alto@ietfa.amsl.com>; Wed,  6 Jun 2012 10:01:17 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 55D0B21F86E0 for <alto@ietf.org>; Wed,  6 Jun 2012 10:01:17 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id q56H1ElL017704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <alto@ietf.org>; Wed, 6 Jun 2012 12:01:14 -0500 (CDT)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q56H1EHn030773 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Wed, 6 Jun 2012 12:01:14 -0500
Received: from [135.222.152.198] (wdr-i7mbp.mh.lucent.com [135.222.152.198]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q56H1B50023908 for <alto@ietf.org>; Wed, 6 Jun 2012 12:01:12 -0500 (CDT)
User-Agent: Microsoft-MacOutlook/14.2.2.120421
Date: Wed, 06 Jun 2012 13:01:11 -0400
From: Bill Roome <w.roome@alcatel-lucent.com>
To: <alto@ietf.org>
Message-ID: <CBF4FED9.DD88%w.roome@alcatel-lucent.com>
Thread-Topic: Problem with endpoint property response in draft 11
In-Reply-To: <CBF4E053.DD08%alto-request@ietf.org>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3421832473_5641883"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: [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: Wed, 06 Jun 2012 17:01:18 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3421832473_5641883
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

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

> - Bill Roome



--B_3421832473_5641883
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); "><div><fo=
nt class=3D"Apple-style-span" face=3D"Monaco" size=3D"2">{7.7.3.1.5} -- Endpoint P=
roperty Response -- says</font></div><div><font class=3D"Apple-style-span" fac=
e=3D"Monaco" size=3D"2"><br></font></div><div><blockquote style=3D"margin-top: 0px=
; margin-right: 0px; margin-bottom: 0px; margin-left: 40px; border-top-style=
: none; border-right-style: none; border-bottom-style: none; border-left-sty=
le: none; border-width: initial; border-color: initial; padding-top: 0px; pa=
dding-right: 0px; padding-bottom: 0px; padding-left: 0px; "><div><font class=
=3D"Apple-style-span" face=3D"Monaco" size=3D"2">The ALTO Server MAY include the V=
ersion Tag (Section 5.3) of the</font></div><div><font class=3D"Apple-style-sp=
an" face=3D"Monaco" size=3D"2">   Network Map used to generate the response (if =
desired and applicable)</font></div><div><font class=3D"Apple-style-span" face=
=3D"Monaco" size=3D"2">   as the 'map-vtag' member in the response.  If the 'pid=
' property is</font></div><div><font class=3D"Apple-style-span" face=3D"Monaco" =
size=3D"2">   returned for any endpoints in the response, the 'map-vtag' membe=
r is</font></div><div><font class=3D"Apple-style-span" face=3D"Monaco" size=3D"2">=
   REQUIRED instead of OPTIONAL.</font></div></blockquote><div><font class=3D"=
Apple-style-span" face=3D"Monaco" size=3D"2"><br></font></div><div><font class=3D"=
Apple-style-span" face=3D"Monaco" size=3D"2">However the example in {7.7.3.1.6} =
doesn't follow that rule. It's</font></div><div><font class=3D"Apple-style-spa=
n" face=3D"Monaco" size=3D"2"><br></font></div><div><blockquote style=3D"margin:0 =
0 0 40px; border:none; padding:0px;"><div><font class=3D"Apple-style-span" fac=
e=3D"Monaco" size=3D"2">&nbsp; {</font></div><div><font class=3D"Apple-style-span"=
 face=3D"Monaco" size=3D"2">&nbsp; &nbsp; "meta" : {},</font></div><div><font cl=
ass=3D"Apple-style-span" face=3D"Monaco" size=3D"2">&nbsp; &nbsp; "data": {</font>=
</div><div><font class=3D"Apple-style-span" face=3D"Monaco" size=3D"2">&nbsp; &nbs=
p; &nbsp; "ipv4:192.0.2.34" &nbsp; &nbsp;: { "pid": "PID1" },</font></div><d=
iv><font class=3D"Apple-style-span" face=3D"Monaco" size=3D"2">&nbsp; &nbsp; &nbsp=
; "ipv4:203.0.113.129" : { "pid": "PID3" }</font></div><div><font class=3D"App=
le-style-span" face=3D"Monaco" size=3D"2">&nbsp; &nbsp; }</font></div><div><font=
 class=3D"Apple-style-span" face=3D"Monaco" size=3D"2">&nbsp; }</font></div></bloc=
kquote></div><div><font class=3D"Apple-style-span" face=3D"Monaco" size=3D"2"><br>=
</font></div><div><font class=3D"Apple-style-span" face=3D"Monaco" size=3D"2">wher=
e it should be</font></div><div><font class=3D"Apple-style-span" face=3D"Monaco"=
 size=3D"2"><br></font></div><div><blockquote style=3D"margin:0 0 0 40px; border=
:none; padding:0px;"><div><font class=3D"Apple-style-span" face=3D"Monaco" size=3D=
"2">&nbsp; {</font></div><div><font class=3D"Apple-style-span" face=3D"Monaco" s=
ize=3D"2">&nbsp; &nbsp; "meta" : {},</font></div><div><font class=3D"Apple-style=
-span" face=3D"Monaco" size=3D"2">&nbsp; &nbsp; "data": {</font></div><div><font=
 class=3D"Apple-style-span" face=3D"Monaco" size=3D"2">&nbsp; &nbsp;&nbsp;&nbsp; "=
map-vtag" : "1266506139",</font></div><div><font class=3D"Apple-style-span" fa=
ce=3D"Monaco" size=3D"2">&nbsp; &nbsp; &nbsp; "ipv4:192.0.2.34" &nbsp; &nbsp;: {=
 "pid": "PID1" },</font></div><div><font class=3D"Apple-style-span" face=3D"Mona=
co" size=3D"2">&nbsp; &nbsp; &nbsp; "ipv4:203.0.113.129" : { "pid": "PID3" }</=
font></div><div><font class=3D"Apple-style-span" face=3D"Monaco" size=3D"2">&nbsp;=
 &nbsp; }</font></div><div><font class=3D"Apple-style-span" face=3D"Monaco" size=
=3D"2">&nbsp; }</font></div></blockquote></div><div><font class=3D"Apple-style-s=
pan" face=3D"Monaco" size=3D"2"><br></font></div><div><font class=3D"Apple-style-s=
pan" face=3D"Monaco" size=3D"2">But that has an unfortunate complication. Before=
, all the keys in the "data" object were endpoints.</font></div></div><div><=
font class=3D"Apple-style-span" face=3D"Monaco" size=3D"2">But now, a key is an en=
dpoint address UNLESS it's "map-vtag". Granted, that's not ambiguous, becaus=
e</font></div><div><font class=3D"Apple-style-span" face=3D"Monaco" size=3D"2">"ma=
p-vtag" can't possibly be an endpoint address.</font></div><div><font class=3D=
"Apple-style-span" face=3D"Monaco" size=3D"2"><br></font></div><div><font class=3D=
"Apple-style-span" face=3D"Monaco" size=3D"2">But still it's annoying. Compare t=
hat with the a filtered network-map response:</font></div><div><font class=3D"=
Apple-style-span" face=3D"Monaco" size=3D"2"><br></font></div><div><blockquote s=
tyle=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 4=
0px; border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: initial;=
 padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padding-left: 0p=
x; "><div><font class=3D"Apple-style-span" face=3D"Monaco" size=3D"2"><div>&nbsp; =
&nbsp;{</div><div>&nbsp; &nbsp; &nbsp;"meta" : {},</div><div>&nbsp; &nbsp; &=
nbsp;"data" : {</div><div>&nbsp; &nbsp; &nbsp; &nbsp;"map-vtag" : "126650613=
9",</div><div>&nbsp; &nbsp; &nbsp; &nbsp;"map" : {</div></font><font class=3D"=
Apple-style-span" face=3D"Monaco" size=3D"2"><div>&nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp;"PID1" : {</div></font><font class=3D"Apple-style-span" face=3D"Monaco" size=
=3D"2"><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"ipv4" : [ "192.0.2.0/24"=
, "198.51.100.0/24" ]</div></font><font class=3D"Apple-style-span" face=3D"Monac=
o" size=3D"2"><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;},</div><div>&nbsp; &nbsp=
; &nbsp; &nbsp; &nbsp;"PID2" : {</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp;"ipv4": [ "198.51.100.128/24" ]</div><div>&nbsp; &nbsp; &nbsp; &nbsp=
; &nbsp;}</div><div>&nbsp; &nbsp; &nbsp; &nbsp;}</div><div>&nbsp; &nbsp; &nb=
sp;}</div><div>&nbsp; &nbsp;}</div><div><br></div></font></div></blockquote>=
<div><font class=3D"Apple-style-span" face=3D"Monaco" size=3D"2">There the PID nam=
e keys are all in a "map" object. So for consistency,</font></div><div><font=
 class=3D"Apple-style-span" face=3D"Monaco" size=3D"2">the properties in an endpoi=
nt prop response should also be under a "map":</font></div><div><font class=3D=
"Apple-style-span" face=3D"Monaco" size=3D"2"><br></font></div><blockquote style=
=3D"margin:0 0 0 40px; border:none; padding:0px;"><div><font class=3D"Apple-styl=
e-span" face=3D"Monaco" size=3D"2">&nbsp; {</font></div></blockquote><div><div><=
blockquote style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; ma=
rgin-left: 40px; border-top-style: none; border-right-style: none; border-bo=
ttom-style: none; border-left-style: none; border-width: initial; border-col=
or: initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; padd=
ing-left: 0px; "><div><font class=3D"Apple-style-span" face=3D"Monaco" size=3D"2">=
&nbsp; &nbsp; "meta" : {},</font></div><div><font class=3D"Apple-style-span" f=
ace=3D"Monaco" size=3D"2">&nbsp; &nbsp; "data": {</font></div><div><font class=3D"=
Apple-style-span" face=3D"Monaco" size=3D"2">&nbsp; &nbsp;&nbsp;&nbsp; "map-vtag=
" : "1266506139",</font></div><div><font class=3D"Apple-style-span" face=3D"Mona=
co" size=3D"2">&nbsp; &nbsp; &nbsp; "map" : {</font></div><div><font class=3D"Ap=
ple-style-span" face=3D"Monaco" size=3D"2">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;"ip=
v4:192.0.2.34" &nbsp; &nbsp;: { "pid": "PID1" },</font></div><div><font clas=
s=3D"Apple-style-span" face=3D"Monaco" size=3D"2">&nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p;"ipv4:203.0.113.129" : { "pid": "PID3" }</font></div><div><font class=3D"App=
le-style-span" face=3D"Monaco" size=3D"2">&nbsp; &nbsp; &nbsp; }</font></div><di=
v><font class=3D"Apple-style-span" face=3D"Monaco" size=3D"2">&nbsp; &nbsp; }</fon=
t></div><div><font class=3D"Apple-style-span" face=3D"Monaco" size=3D"2">&nbsp; }<=
/font></div></blockquote></div><font class=3D"Apple-style-span" face=3D"Monaco" =
size=3D"2"><font class=3D"Apple-style-span" face=3D"Monaco" size=3D"2"><blockquote s=
tyle=3D"margin:0 0 0 40px; border:none; padding:0px;"><div><br></div></blockqu=
ote><div>Comments?</div><div><br></div><blockquote style=3D"margin:0 0 0 40px;=
 border:none; padding:0px;"><div>- Bill Roome</div></blockquote></font></fon=
t></div></div></body></html>

--B_3421832473_5641883--



From richard.alimi@gmail.com  Wed Jun 13 05:22: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 71BAE21F865B for <alto@ietfa.amsl.com>; Wed, 13 Jun 2012 05:22:08 -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 H4QKNnN4gPGf for <alto@ietfa.amsl.com>; Wed, 13 Jun 2012 05:22:07 -0700 (PDT)
Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by ietfa.amsl.com (Postfix) with ESMTP id 9443B21F8503 for <alto@ietf.org>; Wed, 13 Jun 2012 05:22:07 -0700 (PDT)
Received: by dadv36 with SMTP id v36so1214238dad.27 for <alto@ietf.org>; Wed, 13 Jun 2012 05:22:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=mLLRHLt3mLbkfVhChtEmjB3DEsPVv5Wb1oRifYUwMH0=; b=BTDz+Gzvpv8cr38wXy7HhoRYz87rTI9sAsjhzNnUfO/ZE2tBBEbIf9jNtGLbRg5+97 ZZ+WQBU21HQUob+8ztWy27z/UjAB5fu/t/jOEG2/QCsWAQYgiUR65ErQF7ZYZsfLypqQ TBbb9l1TQskoWwM7xxXZRDZuGrmTvZUVLcIG47oGOwL/Lcbb+U+EMkEfZL/V42S0krLs gmRvStpFFylb83Cguh2IET/o6806ct1Dq2ETWSA1wTrFofCcDVMGIXBX/M43fyMSGTwA veBPbPCZYElrb7dc9zWt7oKJOJcGprk0otrmcUsH1CRcldzybr+2wCQ6bTBHIPUC9QSs x/Qg==
Received: by 10.68.244.100 with SMTP id xf4mr50074185pbc.147.1339590127203; Wed, 13 Jun 2012 05:22:07 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.142.140.2 with HTTP; Wed, 13 Jun 2012 05:21:46 -0700 (PDT)
In-Reply-To: <DD64C8C2-009E-4405-B65D-16B796BAAF09@tik.ee.ethz.ch>
References: <4FABFCEC.5070701@cisco.com> <CA+cvDaagjh49t5Zck1pj+yJq6UCibhHH+3FBWA8eioMDOsibsA@mail.gmail.com> <4FB109F9.50006@cisco.com> <CA+cvDaYsHSYLj=BwE3OzzN+vtT5mK=MWpWm7SX5LFdBbVpNuPg@mail.gmail.com> <DD64C8C2-009E-4405-B65D-16B796BAAF09@tik.ee.ethz.ch>
From: Richard Alimi <rich@velvetsea.net>
Date: Wed, 13 Jun 2012 05:21:46 -0700
X-Google-Sender-Auth: wyl2Q3UGuyYkqBA54IqIA2vbHuc
Message-ID: <CA+cvDaZotqptcU=U1=vvCSME4uwnUi+pAcR0qs7LpDeZ6iNyaQ@mail.gmail.com>
To: Brian Trammell <trammell@tik.ee.ethz.ch>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: alto@ietf.org, ipfix-chairs@tools.ietf.org
Subject: Re: [alto] IPFIX Information Element in the ALTO protocol
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 12:22:11 -0000

On Tue, May 15, 2012 at 10:10 AM, Brian Trammell
<trammell@tik.ee.ethz.ch> wrote:
> Hi, Rich, all,
>
> The additions you're talking about seem on a first pass like they'd fit i=
n the IPFIX information model. With respect to the definition of descriptio=
n of an Information Element, the emphasis on "flow" is really a historical =
thing. Basically, description should be specified to be human-readable and =
detailed enough that a reasonably expert person would know how to generate =
and/or interpret it. We'll remove references to flow from the definition of=
 description in RFC 5102-bis.
>

The text regarding it being information being available to the
observer would be too limiting for the ALTO case too.

If both of those requirements were removed, what are the guidelines on
new information elements that would be accepted into the information
element registry?

> There's a more subtle issue with potentially applying the IPFIX informati=
on model to ALTO: the possible need to specify an alternate encoding for IP=
FIX IEs represented in ALTO. Briefly: each IPFIX Information Element has a =
type (these cover address and time types as well as the basic primitives, s=
trings, and raw octet arrays), and these specify encodings appropriate for =
using these types in IPFIX, as well: integers in big-endian binary, times a=
s big-endian binary integers since the epoch or in NTP (era 0) format, and =
so on. As ALTO is JSON-based, these representations are somewhat less than =
appropriate.
>
> Indeed, this could probably be addressed with a single specification of r=
epresentations of IPFIX data types in ALTO (or indeed, for textual protocol=
s in general). This would probably not have any surprises (v4 addresses in =
dotted-quad, v6 addresses as per RFC 4291, timestamps as per RFC 3339, and =
so on); it would just need to be written.
>

Thank you very much for the proposal for using this registry in ALTO.
My personal opinion is that using IPFIX information element registry
doesn't seem to be a great match to replace ALTO's endpoint property
registry.  The win doesn't seem to be that great to me, and it also
requires writing a new spec to map the datatypes.

If others in the ALTO WG feel differently, then please speak up.

Thanks,
Rich

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

From richard.alimi@gmail.com  Wed Jun 13 08:47: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 EE0EA21F862F for <alto@ietfa.amsl.com>; Wed, 13 Jun 2012 08:47:21 -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 nYghsBBDVp9k for <alto@ietfa.amsl.com>; Wed, 13 Jun 2012 08:47:21 -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 14A2F21F85C2 for <alto@ietf.org>; Wed, 13 Jun 2012 08:47:21 -0700 (PDT)
Received: by dacx6 with SMTP id x6so1209175dac.31 for <alto@ietf.org>; Wed, 13 Jun 2012 08:47:20 -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=qaQ2YP9nnIn4zfnN/iToTPhRCVG8Mnk8DpR2yA3PPjA=; b=isAevRVqvMgpg46VfZ8dISRc+bb+b5l7zwJxx7U4RY4OsyfCliJBivxZrhr6my/Omy Gh57ZAX5Liv2+chkODgRe6QWlEcviDGdMU7INXvbzz+fsqXEuCXtx2PtNflhdsj2rugf LRzkqAt8q2gpcsWK+kzAK3rHgfo9ebC8G1hfw6PbtMMLCRB8GkP2z+RwewiBWrANdjny 0W6TmRp26SpffBWDaH0gbDW2SfTyrnEkVo/CtMD7GOEeO/wKxhzzaJfToLx+ot9EaO3n 0VCabazfdwvjKK4metlGnpSiwzBGeQgv7XAdDBTG4NLHqEyYhfKKSmLsP0206nMUHGvO 35Tg==
Received: by 10.68.225.9 with SMTP id rg9mr51701856pbc.137.1339602440805; Wed, 13 Jun 2012 08:47:20 -0700 (PDT)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.142.140.2 with HTTP; Wed, 13 Jun 2012 08:46:59 -0700 (PDT)
In-Reply-To: <92B7945E-3D89-4619-AF84-BA355E498620@tik.ee.ethz.ch>
References: <4FABFCEC.5070701@cisco.com> <CA+cvDaagjh49t5Zck1pj+yJq6UCibhHH+3FBWA8eioMDOsibsA@mail.gmail.com> <4FB109F9.50006@cisco.com> <CA+cvDaYsHSYLj=BwE3OzzN+vtT5mK=MWpWm7SX5LFdBbVpNuPg@mail.gmail.com> <DD64C8C2-009E-4405-B65D-16B796BAAF09@tik.ee.ethz.ch> <CA+cvDaZotqptcU=U1=vvCSME4uwnUi+pAcR0qs7LpDeZ6iNyaQ@mail.gmail.com> <92B7945E-3D89-4619-AF84-BA355E498620@tik.ee.ethz.ch>
From: Richard Alimi <rich@velvetsea.net>
Date: Wed, 13 Jun 2012 08:46:59 -0700
X-Google-Sender-Auth: Mh82eXBbLQma-RV5GUhQmnrg8xI
Message-ID: <CA+cvDaajj65yKmo75=hm2vMSprBeju3gbiWPqo3g8o0wNZC2eA@mail.gmail.com>
To: Brian Trammell <trammell@tik.ee.ethz.ch>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: alto@ietf.org, ipfix-chairs@tools.ietf.org
Subject: Re: [alto] IPFIX Information Element in the ALTO protocol
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 15:47:22 -0000

On Wed, Jun 13, 2012 at 5:36 AM, Brian Trammell <trammell@tik.ee.ethz.ch> w=
rote:
> Hi, Rich, all,
>
> On Jun 13, 2012, at 2:21 PM, Richard Alimi wrote:
>
>> On Tue, May 15, 2012 at 10:10 AM, Brian Trammell
>> <trammell@tik.ee.ethz.ch> wrote:
>>> Hi, Rich, all,
>>>
>>> The additions you're talking about seem on a first pass like they'd fit=
 in the IPFIX information model. With respect to the definition of descript=
ion of an Information Element, the emphasis on "flow" is really a historica=
l thing. Basically, description should be specified to be human-readable an=
d detailed enough that a reasonably expert person would know how to generat=
e and/or interpret it. We'll remove references to flow from the definition =
of description in RFC 5102-bis.
>>>
>>
>> The text regarding it being information being available to the
>> observer would be too limiting for the ALTO case too.
>
> Hm... how can a device export information about something it can't observ=
e / doesn't know?

ALTO may know information about the endpoint, but not observe data
packets to/from it.

(I interpreted 'observer' to be the entity that contains an
Observation Point as defined in RFC5101.)

>
>> If both of those requirements were removed, what are the guidelines on
>> new information elements that would be accepted into the information
>> element registry?
>
> http://tools.ietf.org/html/draft-ietf-ipfix-ie-doctors-03 mostly covers t=
his, though it handles the case of applying the entire IPFIX protocol (see =
section 3) as opposed to just using the information model for a new applica=
tion/protocol. Section 4 contains detailed guidelines for defining new Info=
rmation Elements (summarized in Section 7 in checklist form), though again =
this is geared toward IEs for usage with the IPFIX protocol.
>
>>> There's a more subtle issue with potentially applying the IPFIX informa=
tion model to ALTO: the possible need to specify an alternate encoding for =
IPFIX IEs represented in ALTO. Briefly: each IPFIX Information Element has =
a type (these cover address and time types as well as the basic primitives,=
 strings, and raw octet arrays), and these specify encodings appropriate fo=
r using these types in IPFIX, as well: integers in big-endian binary, times=
 as big-endian binary integers since the epoch or in NTP (era 0) format, an=
d so on. As ALTO is JSON-based, these representations are somewhat less tha=
n appropriate.
>>>
>>> Indeed, this could probably be addressed with a single specification of=
 representations of IPFIX data types in ALTO (or indeed, for textual protoc=
ols in general). This would probably not have any surprises (v4 addresses i=
n dotted-quad, v6 addresses as per RFC 4291, timestamps as per RFC 3339, an=
d so on); it would just need to be written.
>>>
>>
>> Thank you very much for the proposal for using this registry in ALTO.
>> My personal opinion is that using IPFIX information element registry
>> doesn't seem to be a great match to replace ALTO's endpoint property
>> registry. =A0The win doesn't seem to be that great to me, and it also
>> requires writing a new spec to map the datatypes.
>
> Indeed; do let me know if I can be of any further assistance. For what it=
's worth, I suspect we'll define text-friendly representations for the IPFI=
X datatypes sooner or later anyway.
>
> Cheers,
>
> Brian
>
>> If others in the ALTO WG feel differently, then please speak up.
>>
>> Thanks,
>> Rich
>>
>>> Best regards,
>>>
>>> Brian
>>>
>>> On May 14, 2012, at 12:36 PM, Richard Alimi wrote:
>>>
>>>> On Mon, May 14, 2012 at 6:34 AM, Benoit Claise <bclaise@cisco.com> wro=
te:
>>>>> Hi Richard,
>>>>>
>>>>> On Thu, May 10, 2012 at 10:37 AM, Benoit Claise <bclaise@cisco.com> w=
rote:
>>>>>
>>>>> Dear all,
>>>>>
>>>>> I've been reviewing draft-ietf-alto-reqs-14 and the following require=
ment
>>>>> got me thinking:
>>>>>
>>>>> =A0REQ. =A0ARv14-5: An ALTO client protocol MUST be extensible to ena=
ble
>>>>> =A0 support of other host group descriptor types in future. =A0An ALT=
O
>>>>> =A0 client protocol specification MUST define an appropriate procedur=
e
>>>>> =A0 for adding new host group descriptor types, e.g., by establishing=
 an
>>>>> =A0 IANA registry.
>>>>>
>>>>> Why don't you reuse an existing registry, in which you will have all =
the
>>>>> Information Elements already defined instead of defining a new one?
>>>>> WhatI have in mind: the IPFIX I.E. IANA registry.
>>>>> The piece of information I see in draft-ietf-alto-reqs-14 are IP addr=
ess,
>>>>> prefix, BGP AS: they're in IANA.
>>>>> And many other IEs are already present, for future ALTO extensions, i=
f
>>>>> required.
>>>>>
>>>>> This would not only save one registry (ALTO Endpoint Property in
>>>>> draft-ietf-alto-protocol-10), but offers a bigger advantage.
>>>>> Let me explain.... When you will control your applications with ALTO,=
 you
>>>>> will anyway want to apply a flow measurement to monitor your changes,=
 and to
>>>>> serve as a feedback loop for more optimizations.
>>>>> And the chances are high that you will using a NetFlow/IPFIX based
>>>>> mechanism. Both NetFlow and IPFIX use the IPFIX I.E. IANA registry.
>>>>>
>>>>> Therefore, it would make sense to have consistent data models between=
 ALTO
>>>>> and IPFIX, and avoid a data model proxy if we want to compare the dat=
a.
>>>>> Proposal: reuse the ElementIDs found in the IPFIX I.E. IANA registry
>>>>> somewhere in your protocol.
>>>>>
>>>>> The suggested use case is in place of the Endpoint Property registry?
>>>>>
>>>>> I'm referring to the examples in
>>>>> http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-7.5.3
>>>>> So I guess it's
>>>>> http://tools.ietf.org/html/draft-ietf-alto-protocol-11#section-10.3.
>>>>> However, http://tools.ietf.org/html/draft-ietf-alto-protocol-11#secti=
on-10.3
>>>>> doesn't contain the initial series of values.
>>>>
>>>> Those are two different things in the protocol. =A0The former is for
>>>> identifying endpoints themselves, the latter is for properties
>>>> associated with those endpoints.
>>>>
>>>>>
>>>>>
>>>>> Just to be sure I understand what would happen if we went that route,
>>>>> what are the restrictions for adding new information elements?
>>>>> Specifically, what kinds of elements are allowed or disallowed?
>>>>>
>>>>> Things that have been informally discussed in the ALTO WG so far have
>>>>> been things like load information and available network capacity. =A0=
Do
>>>>> those fit within the ipfix model?
>>>>>
>>>>> The IANA considerations for new IPFIX IEs is in RFC5102,
>>>>> http://tools.ietf.org/html/rfc5102#section-7.1.
>>>>> It mentions: IANA through Expert Review [RFC2434]
>>>>> The most up to date document regarding IE allocation is
>>>>> http://tools.ietf.org/html/draft-ietf-ipfix-ie-doctors-02.
>>>>> I don't believe there are any limitations on for new IEs such as load
>>>>> information and available network capacity.
>>>>> Copying the IPFIX chairs and Brian Trammell.
>>>>
>>>> I think the main consideration here is whether IPFIX really is the
>>>> canonical source (and is planned to be in the future) for data
>>>> that an application (note: not only network operator) would want to
>>>> know about an endpoint. =A0In particular, in the CDN use cases, an ALT=
O
>>>> map may be provided by a CDN to advertise costs to/from and properties
>>>> of various cache nodes.
>>>>
>>>>> From RFC5102, Section 2.1 I see that a registration seems to enforce
>>>> that the Information Element is derived from a flow or someone
>>>> observing the flow on the network:
>>>>
>>>> =A0 description - The semantics of this Information Element. =A0Descri=
bes
>>>> =A0 =A0 =A0how this Information Element is derived from the Flow or ot=
her
>>>> =A0 =A0 =A0information available to the observer.
>>>>
>>>> To me, that seems too restrictive for the ALTO model which is
>>>> providing information to the application layer.
>>>>
>>>> Thanks,
>>>> Rich
>>>>
>>>>>
>>>>> Regards, Benoit.
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Rich
>>>>>
>>>>> Disclaimer: I have not read the protocol details
>>>>>
>>>>> Regards, Benoit.
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> alto mailing list
>>>>> alto@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/alto
>>>>>
>>>>>
>>>>>
>>>
>

From trammell@tik.ee.ethz.ch  Wed Jun 13 05:36:44 2012
Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9544821F8593 for <alto@ietfa.amsl.com>; Wed, 13 Jun 2012 05:36:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.398
X-Spam-Level: 
X-Spam-Status: No, score=-6.398 tagged_above=-999 required=5 tests=[AWL=0.201,  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 g9rcxJ8O9hNp for <alto@ietfa.amsl.com>; Wed, 13 Jun 2012 05:36:42 -0700 (PDT)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id F1F5321F849B for <alto@ietf.org>; Wed, 13 Jun 2012 05:36:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 180F4D9308; Wed, 13 Jun 2012 14:36:41 +0200 (MEST)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id lBEd5PVt4Pgb; Wed, 13 Jun 2012 14:36:40 +0200 (MEST)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id D0678D9300; Wed, 13 Jun 2012 14:36:40 +0200 (MEST)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset=iso-8859-1
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <CA+cvDaZotqptcU=U1=vvCSME4uwnUi+pAcR0qs7LpDeZ6iNyaQ@mail.gmail.com>
Date: Wed, 13 Jun 2012 14:36:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <92B7945E-3D89-4619-AF84-BA355E498620@tik.ee.ethz.ch>
References: <4FABFCEC.5070701@cisco.com> <CA+cvDaagjh49t5Zck1pj+yJq6UCibhHH+3FBWA8eioMDOsibsA@mail.gmail.com> <4FB109F9.50006@cisco.com> <CA+cvDaYsHSYLj=BwE3OzzN+vtT5mK=MWpWm7SX5LFdBbVpNuPg@mail.gmail.com> <DD64C8C2-009E-4405-B65D-16B796BAAF09@tik.ee.ethz.ch> <CA+cvDaZotqptcU=U1=vvCSME4uwnUi+pAcR0qs7LpDeZ6iNyaQ@mail.gmail.com>
To: Richard Alimi <rich@velvetsea.net>
X-Mailer: Apple Mail (2.1278)
X-Mailman-Approved-At: Fri, 15 Jun 2012 00:21:32 -0700
Cc: alto@ietf.org, ipfix-chairs@tools.ietf.org
Subject: Re: [alto] IPFIX Information Element in the ALTO protocol
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 12:36:44 -0000

Hi, Rich, all,

On Jun 13, 2012, at 2:21 PM, Richard Alimi wrote:

> On Tue, May 15, 2012 at 10:10 AM, Brian Trammell
> <trammell@tik.ee.ethz.ch> wrote:
>> Hi, Rich, all,
>>=20
>> The additions you're talking about seem on a first pass like they'd =
fit in the IPFIX information model. With respect to the definition of =
description of an Information Element, the emphasis on "flow" is really =
a historical thing. Basically, description should be specified to be =
human-readable and detailed enough that a reasonably expert person would =
know how to generate and/or interpret it. We'll remove references to =
flow from the definition of description in RFC 5102-bis.
>>=20
>=20
> The text regarding it being information being available to the
> observer would be too limiting for the ALTO case too.

Hm... how can a device export information about something it can't =
observe / doesn't know?

> If both of those requirements were removed, what are the guidelines on
> new information elements that would be accepted into the information
> element registry?

http://tools.ietf.org/html/draft-ietf-ipfix-ie-doctors-03 mostly covers =
this, though it handles the case of applying the entire IPFIX protocol =
(see section 3) as opposed to just using the information model for a new =
application/protocol. Section 4 contains detailed guidelines for =
defining new Information Elements (summarized in Section 7 in checklist =
form), though again this is geared toward IEs for usage with the IPFIX =
protocol.

>> There's a more subtle issue with potentially applying the IPFIX =
information model to ALTO: the possible need to specify an alternate =
encoding for IPFIX IEs represented in ALTO. Briefly: each IPFIX =
Information Element has a type (these cover address and time types as =
well as the basic primitives, strings, and raw octet arrays), and these =
specify encodings appropriate for using these types in IPFIX, as well: =
integers in big-endian binary, times as big-endian binary integers since =
the epoch or in NTP (era 0) format, and so on. As ALTO is JSON-based, =
these representations are somewhat less than appropriate.
>>=20
>> Indeed, this could probably be addressed with a single specification =
of representations of IPFIX data types in ALTO (or indeed, for textual =
protocols in general). This would probably not have any surprises (v4 =
addresses in dotted-quad, v6 addresses as per RFC 4291, timestamps as =
per RFC 3339, and so on); it would just need to be written.
>>=20
>=20
> Thank you very much for the proposal for using this registry in ALTO.
> My personal opinion is that using IPFIX information element registry
> doesn't seem to be a great match to replace ALTO's endpoint property
> registry.  The win doesn't seem to be that great to me, and it also
> requires writing a new spec to map the datatypes.

Indeed; do let me know if I can be of any further assistance. For what =
it's worth, I suspect we'll define text-friendly representations for the =
IPFIX datatypes sooner or later anyway.

Cheers,

Brian

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


From internet-drafts@ietf.org  Fri Jun 15 03:03:50 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 6BBB221F85C0; Fri, 15 Jun 2012 03:03:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.463
X-Spam-Level: 
X-Spam-Status: No, score=-102.463 tagged_above=-999 required=5 tests=[AWL=-0.091, 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 40+gpiOGYR+f; Fri, 15 Jun 2012 03:03:50 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E17221F85A0; Fri, 15 Jun 2012 03:03:50 -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.20
Message-ID: <20120615100350.32124.11329.idtracker@ietfa.amsl.com>
Date: Fri, 15 Jun 2012 03:03:50 -0700
Cc: alto@ietf.org
Subject: [alto] I-D Action: 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: Fri, 15 Jun 2012 10:03:50 -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           : Application-Layer Traffic Optimization (ALTO) Requiremen=
ts
	Author(s)       : Sebastian Kiesel
                          Stefano Previdi
                          Martin Stiemerling
                          Richard Woundy
                          Yang Richard Yang
	Filename        : draft-ietf-alto-reqs-16.txt
	Pages           : 24
	Date            : 2012-06-15

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

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


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

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

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


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


From haibin.song@huawei.com  Mon Jun 18 04:23:05 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 63B6A21F8473 for <alto@ietfa.amsl.com>; Mon, 18 Jun 2012 04:23:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.229
X-Spam-Level: 
X-Spam-Status: No, score=-5.229 tagged_above=-999 required=5 tests=[AWL=-0.119, BAYES_05=-1.11, 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 j+GpAqyKRyPT for <alto@ietfa.amsl.com>; Mon, 18 Jun 2012 04:23:04 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 3238021F8508 for <alto@ietf.org>; Mon, 18 Jun 2012 04:23:04 -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 AGZ97860; Mon, 18 Jun 2012 07:23:02 -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, 18 Jun 2012 04:21:43 -0700
Received: from SZXEML414-HUB.china.huawei.com (10.82.67.153) by dfweml406-hub.china.huawei.com (10.193.5.131) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 18 Jun 2012 04:21:42 -0700
Received: from SZXEML534-MBX.china.huawei.com ([169.254.2.36]) by SZXEML414-HUB.china.huawei.com ([10.82.67.153]) with mapi id 14.01.0323.003; Mon, 18 Jun 2012 19:21:33 +0800
From: Songhaibin <haibin.song@huawei.com>
To: Songhaibin <haibin.song@huawei.com>, Richard Alimi <rich@velvetsea.net>
Thread-Topic: [alto] ALTO discovery in roaming scenario
Thread-Index: Ac0Fw01LNWVAmHe9T920S4QOtl0VRwG9ShOAADD7c2X//8qrgIAAjJtG/4DH49A=
Date: Mon, 18 Jun 2012 11:21:31 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F23AAAEAE@szxeml534-mbx.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F15864255@szxeml534-mbx.china.huawei.com> <CA+cvDabLFKH_Pi0z7vhyXjOhcx3ya-YcJLOR8aMKvx-RN2wxaw@mail.gmail.com> <E33E01DFD5BEA24B9F3F18671078951F1586EC4E@szxeml534-mbx.china.huawei.com>, <CA+cvDaYGgupkhMcTGsZvH=0RHBm3BB-G4VPA1PJKZFN9bNLm8A@mail.gmail.com> <E33E01DFD5BEA24B9F3F18671078951F1586EE0E@szxeml534-mbx.china.huawei.com>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F1586EE0E@szxeml534-mbx.china.huawei.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: Mon, 18 Jun 2012 11:23:05 -0000

I would like to dig this from the tomb and see how the WG would like to sol=
ve the ALTO discovery in the roaming/nomadic scenario. I would also like to=
 see it in the ALTO server discovery document.

-Haibin



> -----Original Message-----
> From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of
> Songhaibin
> Sent: Thursday, March 29, 2012 8:34 PM
> To: Richard Alimi
> Cc: alto@ietf.org
> Subject: Re: [alto] ALTO discovery in roaming scenario
>=20
> Hi Rich,
>=20
> I think your proposal makes sense. The wikipedia document
> http://en.wikipedia.org/wiki/Mobile_IP provides some links to relative RF=
Cs. We
> may find details in these RFCs. I will also try to read them.
>=20
> BR,
> -Haibin
>=20
> ________________________________________
> From: richard.alimi@gmail.com [richard.alimi@gmail.com] on behalf of Rich=
ard
> Alimi [rich@velvetsea.net]
> Sent: Thursday, March 29, 2012 8:09 PM
> To: Songhaibin
> Cc: alto@ietf.org
> Subject: Re: [alto] ALTO discovery in roaming scenario
>=20
> On Thu, Mar 29, 2012 at 12:26 AM, Songhaibin <haibin.song@huawei.com>
> wrote:
> > Hi Rich,
> >
> > Thank you for the discussion. See inline.
> >
> > ________________________________________
> > From: richard.alimi@gmail.com [richard.alimi@gmail.com] on behalf of Ri=
chard
> Alimi [rich@velvetsea.net]
> > Sent: Wednesday, March 28, 2012 11:57 PM
> > To: Songhaibin
> > Cc: alto@ietf.org
> > Subject: Re: [alto] ALTO discovery in roaming scenario
> >
> > On Mon, Mar 19, 2012 at 4:28 AM, Songhaibin <haibin.song@huawei.com>
> wrote:
> >> Hi,
> >>
> >> The indicated by the subject, which is perhaps not fully solved in the=
 discovery
> draft, I guess at least the following scenarios should be considered. As =
I'm not an
> expert on roaming technology, please correct me if you find I am wrong.
> >>
> >> (1) The ALTO client has left its home network, and its IP address is d=
ynamically
> assigned by the current network provider (through DHCP or any other metho=
d),
> but the ALTO client still uses its home agent to access the Internet. In =
this case,
> the ALTO server resided in its home network should be the right ALTO serv=
er to
> be discovered.
> >>
> >> (2) The ALTO client has left its home network, and its IP address is d=
ynamically
> assigned by the current network provider, and the ALTO client uses the fo=
reign
> agent to access Internet or uses its IP address directly to access Intern=
et. In this
> scenario, the ALTO server resided in the current network should be the ri=
ght one.
> And the existing discovery mechanism works in this scenario.
> >>
> >> (3) If the ALTO client has a persistent IP address when roaming, and i=
t uses
> home agent to access Internet, but make large data route to the foreign a=
gent
> directly (optimized routing mode). In this scenario, the ALTO server resi=
ded in the
> current network should be the right one to be discovered. However, if it =
does not
> adopt the optimized routing mode, the ALTO server in the home network sho=
uld
> be the right one.
> >>
> >
> > I'm not familiar with the technologies backing this, but what entity
> > decides the route that a particular packet will take? Is this DPI
> > living in the network where the client is roaming?  Or is it some
> > entity on the client itself?
> >
> > [Haibin] No, it is not DPI based. Although I'm not an expert on this ei=
ther, but I
> think in the mobile IPv6 scenario, the decision is made through the negot=
iation
> among the mobile node, home agent, and other correspondent nodes.
> >
>=20
> Thinking about this at the high level, If the mobile node is involved
> in the negotiation, then it seems like it could work like the
> following for this case:
> (1) Discover an ALTO Server using the home agent (same as case 1 above)
> (2) Discover an ALTO Server using the current network (same as case 2 abo=
ve)
> (3) When it comes time to apply the ALTO information, apply the
> correct set depending on the routing for that particular request.
>=20
> Is that compatible with whatever technologies are used for these scenario=
s?
>=20
> Details on how this works and the negotiation actually takes place
> would be useful.
>=20
> Rich
>=20
> > BR,
> > -Haibin
> >
> >> (4) (this one is not about roaming) Assume in a big company which has =
a few
> branch offices in different locations, and VPN tunnels are used to connec=
t these
> branch offices, employees use one proxy to access Internet. Then the ALTO
> server discovery should be based on the proxy's IP address instead of the=
 user's
> IP address.  It also applies to other similar scenarios when end-hosts us=
ing
> proxies.
> >>
> >> It might not be a problem when doing third party discovery, but have t=
o
> consider when doing the discovery by the end-host itself.
> >>
> >> BR,
> >> -Haibin
> >> _______________________________________________
> >> 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 Tina.Tsou.Zouting@huawei.com  Tue Jun 19 10:03:01 2012
Return-Path: <Tina.Tsou.Zouting@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 61CFD11E8088 for <alto@ietfa.amsl.com>; Tue, 19 Jun 2012 10:03:01 -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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K6Uli2AFta23 for <alto@ietfa.amsl.com>; Tue, 19 Jun 2012 10:02:59 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id B7DCE11E80C8 for <alto@ietf.org>; Tue, 19 Jun 2012 10:02:59 -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 AHI25011; Tue, 19 Jun 2012 13:02:59 -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; Tue, 19 Jun 2012 10:01:20 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.109]) by dfweml406-hub.china.huawei.com ([10.193.5.131]) with mapi id 14.01.0323.003; Tue, 19 Jun 2012 10:01:18 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: "alto@ietf.org" <alto@ietf.org>
Thread-Topic: New Version Notification for draft-xie-alto-sdn-use-cases-00.txt
Thread-Index: AQHNTjcTUCusIz+/3UmIzTQpdTVSVg==
Date: Tue, 19 Jun 2012 17:01:17 +0000
Message-ID: <1CCC8BC4-3BA1-4C4E-9FEE-D4C0A5E7E756@huawei.com>
References: <20120619161741.7714.11649.idtracker@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4011676D2DD350498155D413E678DB03@huawei.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [alto] Fwd: New Version Notification for draft-xie-alto-sdn-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: Tue, 19 Jun 2012 17:03:01 -0000

For your comments.

Tina

Begin forwarded message:

> A new version of I-D, draft-xie-alto-sdn-use-cases-00.txt
> has been successfully submitted by Tina Tsou and posted to the
> IETF repository.
>=20
> Filename:     draft-xie-alto-sdn-use-cases
> Revision:     00
> Title:         Use Cases for ALTO with Software Defined Networks
> Creation date:     2012-06-19
> WG ID:         Individual Submission
> Number of pages: 26
> URL:             http://www.ietf.org/internet-drafts/draft-xie-alto-sdn-u=
se-cases-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-xie-alto-sdn-use-c=
ases
> Htmlized:        http://tools.ietf.org/html/draft-xie-alto-sdn-use-cases-=
00
>=20
>=20
> Abstract:
>   This draft describes a general, umbrella use case that illustrates
>   application layer traffic optimization with software defined
>   networks. Unique requirements for design and operations are
>   identified and summarized. Under this umbrella, this draft also
>   elaborates three detailed use cases. In addition, extensions to the
>   existing ALTO protocol are recommended.
>=20
>=20
>=20
>=20
> The IETF Secretariat

From michael.scharf@alcatel-lucent.com  Wed Jun 20 05:08:22 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 CD68921F86CB for <alto@ietfa.amsl.com>; Wed, 20 Jun 2012 05:08:22 -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 eE6RIBwKv46r for <alto@ietfa.amsl.com>; Wed, 20 Jun 2012 05:08:21 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id C65B721F8600 for <alto@ietf.org>; Wed, 20 Jun 2012 05:08:20 -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 q5KC3WhG022090 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 20 Jun 2012 14:08:08 +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; Wed, 20 Jun 2012 14:07:18 +0200
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Songhaibin <haibin.song@huawei.com>
Date: Wed, 20 Jun 2012 14:07:16 +0200
Thread-Topic: [alto] ALTO discovery in roaming scenario
Thread-Index: Ac0Fw01LNWVAmHe9T920S4QOtl0VRwG9ShOAADD7c2X//8qrgIAAjJtG/4DH49D+/mR/0A==
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E891A9BB692@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
References: <E33E01DFD5BEA24B9F3F18671078951F15864255@szxeml534-mbx.china.huawei.com> <CA+cvDabLFKH_Pi0z7vhyXjOhcx3ya-YcJLOR8aMKvx-RN2wxaw@mail.gmail.com> <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>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F23AAAEAE@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.83
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, 20 Jun 2012 12:08:23 -0000

Haibin,

The draft already states:

   o  A change of the IP address at an interface invalidates the result
      of the ALTO server discovery procedure.  For instance, if the IP
      address assigned to a mobile host changes due to host mobility, it
      is required to run the ALTO server discovery procedure for the new
      IP address without relying on earlier gained information.

Could you please explain what text is missing in the draft, and what techni=
cal solution you suggest? For instance, if the mobile network uses "Proxy M=
obile IP"?

My understanding is that in reality roaming/normadic use results in either =
of two possibilities:

(1) There is a change of the IP address of the mobile host. This case is al=
ready explained in the draft.

(2) The IP address of the mobile host does not change. Then, the host remai=
ns in the same IP subnet, and thus the ALTO discovery result is still valid=
.

In both cases, the current text in the discovery draft seems to be just fin=
e, right?

Thanks

Michael


> -----Original Message-----
> From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On=20
> Behalf Of Songhaibin
> Sent: Monday, June 18, 2012 1:22 PM
> To: Songhaibin; Richard Alimi
> Cc: alto@ietf.org
> Subject: Re: [alto] ALTO discovery in roaming scenario
>=20
> I would like to dig this from the tomb and see how the WG=20
> would like to solve the ALTO discovery in the roaming/nomadic=20
> scenario. I would also like to see it in the ALTO server=20
> discovery document.
>=20
> -Haibin
>=20
>=20
>=20
> > -----Original Message-----
> > From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org]=20
> On Behalf=20
> > Of Songhaibin
> > Sent: Thursday, March 29, 2012 8:34 PM
> > To: Richard Alimi
> > Cc: alto@ietf.org
> > Subject: Re: [alto] ALTO discovery in roaming scenario
> >=20
> > Hi Rich,
> >=20
> > I think your proposal makes sense. The wikipedia document=20
> > http://en.wikipedia.org/wiki/Mobile_IP provides some links=20
> to relative=20
> > RFCs. We may find details in these RFCs. I will also try to=20
> read them.
> >=20
> > BR,
> > -Haibin
> >=20
> > ________________________________________
> > From: richard.alimi@gmail.com [richard.alimi@gmail.com] on=20
> behalf of=20
> > Richard Alimi [rich@velvetsea.net]
> > Sent: Thursday, March 29, 2012 8:09 PM
> > To: Songhaibin
> > Cc: alto@ietf.org
> > Subject: Re: [alto] ALTO discovery in roaming scenario
> >=20
> > On Thu, Mar 29, 2012 at 12:26 AM, Songhaibin=20
> <haibin.song@huawei.com>
> > wrote:
> > > Hi Rich,
> > >
> > > Thank you for the discussion. See inline.
> > >
> > > ________________________________________
> > > From: richard.alimi@gmail.com [richard.alimi@gmail.com]=20
> on behalf of=20
> > > Richard
> > Alimi [rich@velvetsea.net]
> > > Sent: Wednesday, March 28, 2012 11:57 PM
> > > To: Songhaibin
> > > Cc: alto@ietf.org
> > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > >
> > > On Mon, Mar 19, 2012 at 4:28 AM, Songhaibin=20
> <haibin.song@huawei.com>
> > wrote:
> > >> Hi,
> > >>
> > >> The indicated by the subject, which is perhaps not fully=20
> solved in=20
> > >> the discovery
> > draft, I guess at least the following scenarios should be=20
> considered.=20
> > As I'm not an expert on roaming technology, please correct=20
> me if you find I am wrong.
> > >>
> > >> (1) The ALTO client has left its home network, and its=20
> IP address=20
> > >> is dynamically
> > assigned by the current network provider (through DHCP or any other=20
> > method), but the ALTO client still uses its home agent to=20
> access the=20
> > Internet. In this case, the ALTO server resided in its home network=20
> > should be the right ALTO server to be discovered.
> > >>
> > >> (2) The ALTO client has left its home network, and its=20
> IP address=20
> > >> is dynamically
> > assigned by the current network provider, and the ALTO=20
> client uses the=20
> > foreign agent to access Internet or uses its IP address directly to=20
> > access Internet. In this scenario, the ALTO server resided=20
> in the current network should be the right one.
> > And the existing discovery mechanism works in this scenario.
> > >>
> > >> (3) If the ALTO client has a persistent IP address when roaming,=20
> > >> and it uses
> > home agent to access Internet, but make large data route to the=20
> > foreign agent directly (optimized routing mode). In this=20
> scenario, the=20
> > ALTO server resided in the current network should be the=20
> right one to=20
> > be discovered. However, if it does not adopt the optimized routing=20
> > mode, the ALTO server in the home network should be the right one.
> > >>
> > >
> > > I'm not familiar with the technologies backing this, but=20
> what entity=20
> > > decides the route that a particular packet will take? Is this DPI=20
> > > living in the network where the client is roaming?  Or is it some=20
> > > entity on the client itself?
> > >
> > > [Haibin] No, it is not DPI based. Although I'm not an=20
> expert on this=20
> > > either, but I
> > think in the mobile IPv6 scenario, the decision is made through the=20
> > negotiation among the mobile node, home agent, and other=20
> correspondent nodes.
> > >
> >=20
> > Thinking about this at the high level, If the mobile node=20
> is involved=20
> > in the negotiation, then it seems like it could work like the=20
> > following for this case:
> > (1) Discover an ALTO Server using the home agent (same as case 1=20
> > above)
> > (2) Discover an ALTO Server using the current network (same=20
> as case 2=20
> > above)
> > (3) When it comes time to apply the ALTO information, apply the=20
> > correct set depending on the routing for that particular request.
> >=20
> > Is that compatible with whatever technologies are used for=20
> these scenarios?
> >=20
> > Details on how this works and the negotiation actually takes place=20
> > would be useful.
> >=20
> > Rich
> >=20
> > > BR,
> > > -Haibin
> > >
> > >> (4) (this one is not about roaming) Assume in a big=20
> company which=20
> > >> has a few
> > branch offices in different locations, and VPN tunnels are used to=20
> > connect these branch offices, employees use one proxy to access=20
> > Internet. Then the ALTO server discovery should be based on the=20
> > proxy's IP address instead of the user's IP address.  It=20
> also applies=20
> > to other similar scenarios when end-hosts using proxies.
> > >>
> > >> It might not be a problem when doing third party discovery, but=20
> > >> have to
> > consider when doing the discovery by the end-host itself.
> > >>
> > >> BR,
> > >> -Haibin
> > >> _______________________________________________
> > >> 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
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
> =

From haibin.song@huawei.com  Wed Jun 20 20:03:00 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 47E9921F8568 for <alto@ietfa.amsl.com>; Wed, 20 Jun 2012 20:03:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.077
X-Spam-Level: 
X-Spam-Status: No, score=-6.077 tagged_above=-999 required=5 tests=[AWL=0.522,  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 qbUnANhmqKBF for <alto@ietfa.amsl.com>; Wed, 20 Jun 2012 20:02:59 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 47BB721F8567 for <alto@ietf.org>; Wed, 20 Jun 2012 20:02:59 -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 AHB98685; Wed, 20 Jun 2012 23:02:59 -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; Wed, 20 Jun 2012 20:02:09 -0700
Received: from SZXEML431-HUB.china.huawei.com (10.72.61.39) by dfweml406-hub.china.huawei.com (10.193.5.131) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 20 Jun 2012 20:02:13 -0700
Received: from SZXEML534-MBX.china.huawei.com ([169.254.2.36]) by szxeml431-hub.china.huawei.com ([10.72.61.39]) with mapi id 14.01.0323.003; Thu, 21 Jun 2012 11:02:08 +0800
From: Songhaibin <haibin.song@huawei.com>
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
Thread-Topic: [alto] ALTO discovery in roaming scenario
Thread-Index: Ac0Fw01LNWVAmHe9T920S4QOtl0VRwG9ShOAADD7c2X//8qrgIAAjJtG/4DH49D+/mR/0P37yYCw
Date: Thu, 21 Jun 2012 03:02:07 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F23AB4448@szxeml534-mbx.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F15864255@szxeml534-mbx.china.huawei.com> <CA+cvDabLFKH_Pi0z7vhyXjOhcx3ya-YcJLOR8aMKvx-RN2wxaw@mail.gmail.com> <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>
In-Reply-To: <2A886F9088894347A3BE0CC5B7A85F3E891A9BB692@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: Thu, 21 Jun 2012 03:03:00 -0000

Please imagine a gateway/proxy based network access, the ALTO client is the=
 end host, but actually the IP address for gateway/proxy which connect the =
end host to the network should be used for ALTO server discovery. The chang=
e of end-host IP and gateway/proxy IP is independent somehow. I hope this c=
larification helps.

BR,
-Haibin

> -----Original Message-----
> From: Scharf, Michael (Michael) [mailto:michael.scharf@alcatel-lucent.com=
]
> Sent: Wednesday, June 20, 2012 8:07 PM
> To: Songhaibin
> Cc: alto@ietf.org
> Subject: RE: [alto] ALTO discovery in roaming scenario
>=20
> Haibin,
>=20
> The draft already states:
>=20
>    o  A change of the IP address at an interface invalidates the result
>       of the ALTO server discovery procedure.  For instance, if the IP
>       address assigned to a mobile host changes due to host mobility, it
>       is required to run the ALTO server discovery procedure for the new
>       IP address without relying on earlier gained information.
>=20
> Could you please explain what text is missing in the draft, and what tech=
nical
> solution you suggest? For instance, if the mobile network uses "Proxy Mob=
ile
> IP"?
>=20
> My understanding is that in reality roaming/normadic use results in eithe=
r of two
> possibilities:
>=20
> (1) There is a change of the IP address of the mobile host. This case is =
already
> explained in the draft.
>=20
> (2) The IP address of the mobile host does not change. Then, the host rem=
ains in
> the same IP subnet, and thus the ALTO discovery result is still valid.
>=20
> In both cases, the current text in the discovery draft seems to be just f=
ine, right?
>=20
> Thanks
>=20
> Michael
>=20
>=20
> > -----Original Message-----
> > From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On
> > Behalf Of Songhaibin
> > Sent: Monday, June 18, 2012 1:22 PM
> > To: Songhaibin; Richard Alimi
> > Cc: alto@ietf.org
> > Subject: Re: [alto] ALTO discovery in roaming scenario
> >
> > I would like to dig this from the tomb and see how the WG
> > would like to solve the ALTO discovery in the roaming/nomadic
> > scenario. I would also like to see it in the ALTO server
> > discovery document.
> >
> > -Haibin
> >
> >
> >
> > > -----Original Message-----
> > > From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org]
> > On Behalf
> > > Of Songhaibin
> > > Sent: Thursday, March 29, 2012 8:34 PM
> > > To: Richard Alimi
> > > Cc: alto@ietf.org
> > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > >
> > > Hi Rich,
> > >
> > > I think your proposal makes sense. The wikipedia document
> > > http://en.wikipedia.org/wiki/Mobile_IP provides some links
> > to relative
> > > RFCs. We may find details in these RFCs. I will also try to
> > read them.
> > >
> > > BR,
> > > -Haibin
> > >
> > > ________________________________________
> > > From: richard.alimi@gmail.com [richard.alimi@gmail.com] on
> > behalf of
> > > Richard Alimi [rich@velvetsea.net]
> > > Sent: Thursday, March 29, 2012 8:09 PM
> > > To: Songhaibin
> > > Cc: alto@ietf.org
> > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > >
> > > On Thu, Mar 29, 2012 at 12:26 AM, Songhaibin
> > <haibin.song@huawei.com>
> > > wrote:
> > > > Hi Rich,
> > > >
> > > > Thank you for the discussion. See inline.
> > > >
> > > > ________________________________________
> > > > From: richard.alimi@gmail.com [richard.alimi@gmail.com]
> > on behalf of
> > > > Richard
> > > Alimi [rich@velvetsea.net]
> > > > Sent: Wednesday, March 28, 2012 11:57 PM
> > > > To: Songhaibin
> > > > Cc: alto@ietf.org
> > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > >
> > > > On Mon, Mar 19, 2012 at 4:28 AM, Songhaibin
> > <haibin.song@huawei.com>
> > > wrote:
> > > >> Hi,
> > > >>
> > > >> The indicated by the subject, which is perhaps not fully
> > solved in
> > > >> the discovery
> > > draft, I guess at least the following scenarios should be
> > considered.
> > > As I'm not an expert on roaming technology, please correct
> > me if you find I am wrong.
> > > >>
> > > >> (1) The ALTO client has left its home network, and its
> > IP address
> > > >> is dynamically
> > > assigned by the current network provider (through DHCP or any other
> > > method), but the ALTO client still uses its home agent to
> > access the
> > > Internet. In this case, the ALTO server resided in its home network
> > > should be the right ALTO server to be discovered.
> > > >>
> > > >> (2) The ALTO client has left its home network, and its
> > IP address
> > > >> is dynamically
> > > assigned by the current network provider, and the ALTO
> > client uses the
> > > foreign agent to access Internet or uses its IP address directly to
> > > access Internet. In this scenario, the ALTO server resided
> > in the current network should be the right one.
> > > And the existing discovery mechanism works in this scenario.
> > > >>
> > > >> (3) If the ALTO client has a persistent IP address when roaming,
> > > >> and it uses
> > > home agent to access Internet, but make large data route to the
> > > foreign agent directly (optimized routing mode). In this
> > scenario, the
> > > ALTO server resided in the current network should be the
> > right one to
> > > be discovered. However, if it does not adopt the optimized routing
> > > mode, the ALTO server in the home network should be the right one.
> > > >>
> > > >
> > > > I'm not familiar with the technologies backing this, but
> > what entity
> > > > decides the route that a particular packet will take? Is this DPI
> > > > living in the network where the client is roaming?  Or is it some
> > > > entity on the client itself?
> > > >
> > > > [Haibin] No, it is not DPI based. Although I'm not an
> > expert on this
> > > > either, but I
> > > think in the mobile IPv6 scenario, the decision is made through the
> > > negotiation among the mobile node, home agent, and other
> > correspondent nodes.
> > > >
> > >
> > > Thinking about this at the high level, If the mobile node
> > is involved
> > > in the negotiation, then it seems like it could work like the
> > > following for this case:
> > > (1) Discover an ALTO Server using the home agent (same as case 1
> > > above)
> > > (2) Discover an ALTO Server using the current network (same
> > as case 2
> > > above)
> > > (3) When it comes time to apply the ALTO information, apply the
> > > correct set depending on the routing for that particular request.
> > >
> > > Is that compatible with whatever technologies are used for
> > these scenarios?
> > >
> > > Details on how this works and the negotiation actually takes place
> > > would be useful.
> > >
> > > Rich
> > >
> > > > BR,
> > > > -Haibin
> > > >
> > > >> (4) (this one is not about roaming) Assume in a big
> > company which
> > > >> has a few
> > > branch offices in different locations, and VPN tunnels are used to
> > > connect these branch offices, employees use one proxy to access
> > > Internet. Then the ALTO server discovery should be based on the
> > > proxy's IP address instead of the user's IP address.  It
> > also applies
> > > to other similar scenarios when end-hosts using proxies.
> > > >>
> > > >> It might not be a problem when doing third party discovery, but
> > > >> have to
> > > consider when doing the discovery by the end-host itself.
> > > >>
> > > >> BR,
> > > >> -Haibin
> > > >> _______________________________________________
> > > >> 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
> > _______________________________________________
> > alto mailing list
> > alto@ietf.org
> > https://www.ietf.org/mailman/listinfo/alto
> >

From michael.scharf@alcatel-lucent.com  Thu Jun 21 01:18:18 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 A78C421F85C0 for <alto@ietfa.amsl.com>; Thu, 21 Jun 2012 01:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.249
X-Spam-Level: 
X-Spam-Status: No, score=-8.249 tagged_above=-999 required=5 tests=[AWL=-2.000, 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 bBql4MxY4BZT for <alto@ietfa.amsl.com>; Thu, 21 Jun 2012 01:18:15 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [62.23.212.56]) by ietfa.amsl.com (Postfix) with ESMTP id 2F04E21F85AD for <alto@ietf.org>; Thu, 21 Jun 2012 01:18:12 -0700 (PDT)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q5L8Fwii028967 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 21 Jun 2012 10:18:01 +0200
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.55]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Thu, 21 Jun 2012 10:17:59 +0200
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Songhaibin <haibin.song@huawei.com>
Date: Thu, 21 Jun 2012 10:17:58 +0200
Thread-Topic: [alto] ALTO discovery in roaming scenario
Thread-Index: Ac0Fw01LNWVAmHe9T920S4QOtl0VRwG9ShOAADD7c2X//8qrgIAAjJtG/4DH49D+/mR/0P37yYCw+/c7DDA=
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E891A9BB6B2@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
References: <E33E01DFD5BEA24B9F3F18671078951F15864255@szxeml534-mbx.china.huawei.com> <CA+cvDabLFKH_Pi0z7vhyXjOhcx3ya-YcJLOR8aMKvx-RN2wxaw@mail.gmail.com> <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>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F23AB4448@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.83
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: Thu, 21 Jun 2012 08:18:18 -0000

Haibin,

Can you please explain how the scenario you describe is different to a norm=
al NAT middlebox?

Regarding NAT, the draft right now states that there are various methods to=
 find out the right IP address:

   A client can have several candidate IP addresses that it may use for
   the discovery process.  For example if it is located behind a NAT, a
   private and a public IP address may be used for the discovery
   process.  It depends on the deployment scenario which of the IP
   addresses is the correct one.  Thus it is out-of-scope of this
   document to specify how exactly the client finds the right IP
   address.  However in the following we list methods that may be used
   in order to determine these candidate IP addresses.  Generally in P2P
   environments peers already have implemented mechanisms for NAT-
   traversal.  This includes proprietary solutions to determine a peer's
   public IP address, for example by asking a neighbour peer about its
   record of the own IP address.  Non-proprietary solutions that are
   favorable include the Session Traversal Utilities for NAT (STUN)
   [RFC5986] protocol to determine the public address.  If the client is
   behind a residential gateway another option may be to use Universal
   Plug and Play (UPnP) [UPnP-IGD-WANIPConnection1] or the NAT Port
   Mapping Protocol (NAT-PMP) [I-D.cheshire-nat-pmp].


What text do you suggest to add to that?

Thanks,

Michael


> -----Original Message-----
> From: Songhaibin [mailto:haibin.song@huawei.com]=20
> Sent: Thursday, June 21, 2012 5:02 AM
> To: Scharf, Michael (Michael)
> Cc: alto@ietf.org
> Subject: RE: [alto] ALTO discovery in roaming scenario
>=20
> Please imagine a gateway/proxy based network access, the ALTO=20
> client is the end host, but actually the IP address for=20
> gateway/proxy which connect the end host to the network=20
> should be used for ALTO server discovery. The change of=20
> end-host IP and gateway/proxy IP is independent somehow. I=20
> hope this clarification helps.
>=20
> BR,
> -Haibin
>=20
> > -----Original Message-----
> > From: Scharf, Michael (Michael)=20
> > [mailto:michael.scharf@alcatel-lucent.com]
> > Sent: Wednesday, June 20, 2012 8:07 PM
> > To: Songhaibin
> > Cc: alto@ietf.org
> > Subject: RE: [alto] ALTO discovery in roaming scenario
> >=20
> > Haibin,
> >=20
> > The draft already states:
> >=20
> >    o  A change of the IP address at an interface=20
> invalidates the result
> >       of the ALTO server discovery procedure.  For=20
> instance, if the IP
> >       address assigned to a mobile host changes due to host=20
> mobility, it
> >       is required to run the ALTO server discovery=20
> procedure for the new
> >       IP address without relying on earlier gained information.
> >=20
> > Could you please explain what text is missing in the draft,=20
> and what=20
> > technical solution you suggest? For instance, if the mobile network=20
> > uses "Proxy Mobile IP"?
> >=20
> > My understanding is that in reality roaming/normadic use results in=20
> > either of two
> > possibilities:
> >=20
> > (1) There is a change of the IP address of the mobile host.=20
> This case=20
> > is already explained in the draft.
> >=20
> > (2) The IP address of the mobile host does not change.=20
> Then, the host=20
> > remains in the same IP subnet, and thus the ALTO discovery=20
> result is still valid.
> >=20
> > In both cases, the current text in the discovery draft=20
> seems to be just fine, right?
> >=20
> > Thanks
> >=20
> > Michael
> >=20
> >=20
> > > -----Original Message-----
> > > From: alto-bounces@ietf.org=20
> [mailto:alto-bounces@ietf.org] On Behalf=20
> > > Of Songhaibin
> > > Sent: Monday, June 18, 2012 1:22 PM
> > > To: Songhaibin; Richard Alimi
> > > Cc: alto@ietf.org
> > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > >
> > > I would like to dig this from the tomb and see how the WG=20
> would like=20
> > > to solve the ALTO discovery in the roaming/nomadic=20
> scenario. I would=20
> > > also like to see it in the ALTO server discovery document.
> > >
> > > -Haibin
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org]
> > > On Behalf
> > > > Of Songhaibin
> > > > Sent: Thursday, March 29, 2012 8:34 PM
> > > > To: Richard Alimi
> > > > Cc: alto@ietf.org
> > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > >
> > > > Hi Rich,
> > > >
> > > > I think your proposal makes sense. The wikipedia document=20
> > > > http://en.wikipedia.org/wiki/Mobile_IP provides some links
> > > to relative
> > > > RFCs. We may find details in these RFCs. I will also try to
> > > read them.
> > > >
> > > > BR,
> > > > -Haibin
> > > >
> > > > ________________________________________
> > > > From: richard.alimi@gmail.com [richard.alimi@gmail.com] on
> > > behalf of
> > > > Richard Alimi [rich@velvetsea.net]
> > > > Sent: Thursday, March 29, 2012 8:09 PM
> > > > To: Songhaibin
> > > > Cc: alto@ietf.org
> > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > >
> > > > On Thu, Mar 29, 2012 at 12:26 AM, Songhaibin
> > > <haibin.song@huawei.com>
> > > > wrote:
> > > > > Hi Rich,
> > > > >
> > > > > Thank you for the discussion. See inline.
> > > > >
> > > > > ________________________________________
> > > > > From: richard.alimi@gmail.com [richard.alimi@gmail.com]
> > > on behalf of
> > > > > Richard
> > > > Alimi [rich@velvetsea.net]
> > > > > Sent: Wednesday, March 28, 2012 11:57 PM
> > > > > To: Songhaibin
> > > > > Cc: alto@ietf.org
> > > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > > >
> > > > > On Mon, Mar 19, 2012 at 4:28 AM, Songhaibin
> > > <haibin.song@huawei.com>
> > > > wrote:
> > > > >> Hi,
> > > > >>
> > > > >> The indicated by the subject, which is perhaps not fully
> > > solved in
> > > > >> the discovery
> > > > draft, I guess at least the following scenarios should be
> > > considered.
> > > > As I'm not an expert on roaming technology, please correct
> > > me if you find I am wrong.
> > > > >>
> > > > >> (1) The ALTO client has left its home network, and its
> > > IP address
> > > > >> is dynamically
> > > > assigned by the current network provider (through DHCP or any=20
> > > > other method), but the ALTO client still uses its home agent to
> > > access the
> > > > Internet. In this case, the ALTO server resided in its home=20
> > > > network should be the right ALTO server to be discovered.
> > > > >>
> > > > >> (2) The ALTO client has left its home network, and its
> > > IP address
> > > > >> is dynamically
> > > > assigned by the current network provider, and the ALTO
> > > client uses the
> > > > foreign agent to access Internet or uses its IP address=20
> directly=20
> > > > to access Internet. In this scenario, the ALTO server resided
> > > in the current network should be the right one.
> > > > And the existing discovery mechanism works in this scenario.
> > > > >>
> > > > >> (3) If the ALTO client has a persistent IP address when=20
> > > > >> roaming, and it uses
> > > > home agent to access Internet, but make large data route to the=20
> > > > foreign agent directly (optimized routing mode). In this
> > > scenario, the
> > > > ALTO server resided in the current network should be the
> > > right one to
> > > > be discovered. However, if it does not adopt the=20
> optimized routing=20
> > > > mode, the ALTO server in the home network should be the=20
> right one.
> > > > >>
> > > > >
> > > > > I'm not familiar with the technologies backing this, but
> > > what entity
> > > > > decides the route that a particular packet will take? Is this=20
> > > > > DPI living in the network where the client is=20
> roaming?  Or is it=20
> > > > > some entity on the client itself?
> > > > >
> > > > > [Haibin] No, it is not DPI based. Although I'm not an
> > > expert on this
> > > > > either, but I
> > > > think in the mobile IPv6 scenario, the decision is made through=20
> > > > the negotiation among the mobile node, home agent, and other
> > > correspondent nodes.
> > > > >
> > > >
> > > > Thinking about this at the high level, If the mobile node
> > > is involved
> > > > in the negotiation, then it seems like it could work like the=20
> > > > following for this case:
> > > > (1) Discover an ALTO Server using the home agent (same as case 1
> > > > above)
> > > > (2) Discover an ALTO Server using the current network (same
> > > as case 2
> > > > above)
> > > > (3) When it comes time to apply the ALTO information, apply the=20
> > > > correct set depending on the routing for that=20
> particular request.
> > > >
> > > > Is that compatible with whatever technologies are used for
> > > these scenarios?
> > > >
> > > > Details on how this works and the negotiation actually=20
> takes place=20
> > > > would be useful.
> > > >
> > > > Rich
> > > >
> > > > > BR,
> > > > > -Haibin
> > > > >
> > > > >> (4) (this one is not about roaming) Assume in a big
> > > company which
> > > > >> has a few
> > > > branch offices in different locations, and VPN tunnels=20
> are used to=20
> > > > connect these branch offices, employees use one proxy to access=20
> > > > Internet. Then the ALTO server discovery should be based on the=20
> > > > proxy's IP address instead of the user's IP address.  It
> > > also applies
> > > > to other similar scenarios when end-hosts using proxies.
> > > > >>
> > > > >> It might not be a problem when doing third party=20
> discovery, but=20
> > > > >> have to
> > > > consider when doing the discovery by the end-host itself.
> > > > >>
> > > > >> BR,
> > > > >> -Haibin
> > > > >> _______________________________________________
> > > > >> 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
> > > _______________________________________________
> > > alto mailing list
> > > alto@ietf.org
> > > https://www.ietf.org/mailman/listinfo/alto
> > >
> =

From diego@tid.es  Thu Jun 28 04:41:53 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 0CC9121F8470; Thu, 28 Jun 2012 04:41:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.708
X-Spam-Level: 
X-Spam-Status: No, score=-5.708 tagged_above=-999 required=5 tests=[AWL=0.891,  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 p57lhntCYcMG; Thu, 28 Jun 2012 04:41:52 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2FF2621F846B; Thu, 28 Jun 2012 04:41:44 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M6B000RUSHJKH@tid.hi.inet>; Thu, 28 Jun 2012 13:41:43 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 85.76.26499.6F24CEF4; Thu, 28 Jun 2012 13:41:42 +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 <0M6B000RRSHIKH@tid.hi.inet>; Thu, 28 Jun 2012 13:41:42 +0200 (MEST)
Received: from EX10-MB1-MAD.hi.inet ([fe80::a473:4f3e:f8db:1855]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0298.004; Thu, 28 Jun 2012 13:41:42 +0200
Date: Thu, 28 Jun 2012 11:41:42 +0000
From: "Diego R. Lopez" <diego@tid.es>
X-Originating-IP: [10.95.64.115]
To: "altoext@ietf.org" <altoext@ietf.org>, "alto@ietf.org" <alto@ietf.org>
Message-id: <9DA8756D-A668-4346-87CB-7588702545CE@tid.es>
Content-id: <3137E1C66641264B971C1571AF50D1F3@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US
Thread-topic: New Version Notification for draft-xie-alto-sdn-use-cases-01.txt
Thread-index: AQHNVNUN4ov5TcMXoUW5lM/yL/uM3w==
X-AuditID: 0a5f4068-b7f206d000006783-c1-4fec42f620ef
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprJKsWRmVeSWpSXmKPExsXCFe/ApfvN6Y2/wderVhYPt+9ltbg1eRK7 A5PHkiU/mQIYo7hsUlJzMstSi/TtErgypn7rYC/okazo2X2BrYFxh0QXIyeHhICJxP8/55kg bDGJC/fWs3UxcnEICWxklDh+YSMThPMMyHl1FiqzlFGi58QHZpAWFgFViecH9oHZbED2o+bf 7CC2sICfxML+u8wQYxUk/px7zAJiiwh4SZzrvQFm8wpYSqy8/AlsNbOAmcS1i2fZIeKCEj8m 3wOq4QCKq0tMmZILUSIu0dx6kwXCVpSYtqiBEcRmBLr6+6k1TBDj/SRO7nkNtUpP4vqDI2wQ JwhILNlzHuocUYmXj/+xgthCAg4Sq1bOYp3AKDYLyRWzkFwxC+GKWUiumIXkigWMrKsYxYqT ijLTM0pyEzNz0g0M9TIy9TLzUks2MULiKWMH4/KdKocYBTgYlXh4tbxe+wuxJpYVV+YeYpTk YFIS5WUHRqMQX1J+SmVGYnFGfFFpTmrxIUYJDmYlEd7vcUDlvCmJlVWpRfkwKRkODiUJXi6Q NsGi1PTUirTMHGDSgEkzcXCCtPMAtcuC1PAWFyTmFmemQ+RPMUpKifP+cwRKCIAkMkrz4Hpf MYoDHSnMqwjSxgNMb3Bdr4AGMgENdAoAuae4JBEhJdXAmOwYHDylLUHIoixIeSXnQ0cb87le KZlL3iVc+nlBwt3wwec7tWaz7wndX/jiRYMvi+jJN9/Xt0k/WOp8V3DHiuMbfip+9uhLfLsl 4P+Gedv+Re0T0T3z5r/PleOlN7VmCiy61/l326YJKzrWqu6580k78ZlA8nvnsA6t+A9uvz9d D1ZJ73k46ZESS3FGoqEWc1FxIgDeZP5ZLAMAAA==
References: <20120628022346.4612.84400.idtracker@ietfa.amsl.com>
Subject: [alto] Fwd: New Version Notification for draft-xie-alto-sdn-use-cases-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: Thu, 28 Jun 2012 11:41:53 -0000

DQpIaSwNCg0KVGhpcyBpcyBhIHByb3Bvc2FsIG9uIHRoZSBpbnRlcmFjdGlvbiBiZXR3ZWVuIEFM
VE8gYW5kIFNETiB3ZSdkIGxpa2UgdG8gZGlzY3Vzcw0KYXQgb3VyIG5leHQgbWVldGluZyBpbiBW
YW5jb3V2ZXIuDQoNCkNvbW1lbnRzIHdpbGwgYmUgZXh0cmVtZWx5IGFwcHJlY2lhdGVkLg0KDQpC
ZSBnb29kZSwNCg0KQmVnaW4gZm9yd2FyZGVkIG1lc3NhZ2U6DQo+IEEgbmV3IHZlcnNpb24gb2Yg
SS1ELCBkcmFmdC14aWUtYWx0by1zZG4tdXNlLWNhc2VzLTAxLnR4dA0KPiBoYXMgYmVlbiBzdWNj
ZXNzZnVsbHkgc3VibWl0dGVkIGJ5IEhhaXlvbmcgWGllIGFuZCBwb3N0ZWQgdG8gdGhlDQo+IElF
VEYgcmVwb3NpdG9yeS4NCj4NCj4gRmlsZW5hbWU6ICAgICAgZHJhZnQteGllLWFsdG8tc2RuLXVz
ZS1jYXNlcw0KPiBSZXZpc2lvbjogICAgICAwMQ0KPiBUaXRsZTogICAgICAgICAgICAgICAgIFVz
ZSBDYXNlcyBmb3IgQUxUTyB3aXRoIFNvZnR3YXJlIERlZmluZWQgTmV0d29ya3MNCj4gQ3JlYXRp
b24gZGF0ZTogICAgICAgICAyMDEyLTA2LTI3DQo+IFdHIElEOiAgICAgICAgICAgICAgICAgSW5k
aXZpZHVhbCBTdWJtaXNzaW9uDQo+IE51bWJlciBvZiBwYWdlczogMjgNCj4gVVJMOiAgICAgICAg
ICAgICBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC14aWUtYWx0by1z
ZG4tdXNlLWNhc2VzLTAxLnR4dA0KPiBTdGF0dXM6ICAgICAgICAgIGh0dHA6Ly9kYXRhdHJhY2tl
ci5pZXRmLm9yZy9kb2MvZHJhZnQteGllLWFsdG8tc2RuLXVzZS1jYXNlcw0KPiBIdG1saXplZDog
ICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXhpZS1hbHRvLXNkbi11c2Ut
Y2FzZXMtMDENCj4gRGlmZjogICAgICAgICAgICBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlm
Zj91cmwyPWRyYWZ0LXhpZS1hbHRvLXNkbi11c2UtY2FzZXMtMDENCj4NCj4gQWJzdHJhY3Q6DQo+
ICAgVGhlIGludHJvZHVjdGlvbiBvZiBTRE4gZnVuZGFtZW50YWxseSBjaGFuZ2VzIHRoZSB3YXkg
dGhhdCB0aGUgQUxUTw0KPiAgIHdvcmtzLiAgVGhpcyBkcmFmdCBkZXNjcmliZXMgdGhlIFZlcnRp
Y2FsIEFyY2hpdGVjdHVyZSBhbmQgdGhlDQo+ICAgSG9yaXpvbnRhbCBBcmNoaXRlY3R1cmUgYWxs
b3dpbmcgY29oZXJlbnQgY29leGlzdGVuY2Ugb2YgYXBwbGljYXRpb24NCj4gICBsYXllciB0cmFm
ZmljIG9wdGltaXphdGlvbiAoQUxUTykgd2l0aCBzb2Z0d2FyZSBkZWZpbmVkIG5ldHdvcmsNCj4g
ICAoU0ROKS4gIFVuaXF1ZSByZXF1aXJlbWVudHMgZm9yIGRlc2lnbiBhbmQgb3BlcmF0aW9ucyBh
cmUgaWRlbnRpZmllZA0KPiAgIGFuZCBzdW1tYXJpemVkLCBzdWdnZXN0aW5nIHRoYXQgdGhlIFZl
cnRpY2FsIEFyY2hpdGVjdHVyZSBhbGxvd3MNCj4gICBiZXR0ZXIgZGl2aXNpb24sIG1hbmFnZW1l
bnQsIGZsZXhpYmlsaXR5LCBwcml2YWN5IGNvbnRyb2wgYW5kIGxvbmctDQo+ICAgdGVybSBldm9s
dXRpb24gb2YgdGhlIG5ldHdvcmsuICBXZSBhbHNvIGRlZmluZSB0aGUgbWFpbiBpbnRlcmFjdGlv
bnMNCj4gICBhbmQgaW5mb3JtYXRpb24gZmxvd3MsIGFuZCBwcmVzZW50IGEgc2V0IG9mIHVzZSBj
YXNlcyB0byBpbGx1c3RyYXRlDQo+ICAgaG93IHdlIGV4dGVuZCBBTFRPIHRvIHN1cHBvcnQgU0RO
LCBpbiB0aGUgVmVydGljYWwgQXJjaGl0ZWN0dXJlLg0KPg0KPg0KPg0KPg0KPiBUaGUgSUVURiBT
ZWNyZXRhcmlhdA0KDQoNCi0tDQoiRXN0YSB2ZXogbm8gZmFsbGFyZW1vcywgRG9jdG9yIEluZmll
cm5vIg0KDQpEciBEaWVnbyBSLiBMb3Bleg0KVGVsZWZvbmljYSBJK0QNCmh0dHA6Ly9wZW9wbGUu
dGlkLmVzL2RpZWdvLmxvcGV6Lw0KDQplLW1haWw6IGRpZWdvQHRpZC5lcw0KVGVsOiAgICArMzQg
OTEzIDEyOSAwNDENCk1vYmlsZTogKzM0IDY4MiAwNTEgMDkxDQotLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQoNCkVzdGUgbWVuc2FqZSBzZSBkaXJpZ2UgZXhjbHVzaXZhbWVudGUgYSBzdSBkZXN0aW5h
dGFyaW8uIFB1ZWRlIGNvbnN1bHRhciBudWVzdHJhIHBvbMOtdGljYSBkZSBlbnbDrW8geSByZWNl
cGNpw7NuIGRlIGNvcnJlbyBlbGVjdHLDs25pY28gZW4gZWwgZW5sYWNlIHNpdHVhZG8gbcOhcyBh
YmFqby4NClRoaXMgbWVzc2FnZSBpcyBpbnRlbmRlZCBleGNsdXNpdmVseSBmb3IgaXRzIGFkZHJl
c3NlZS4gV2Ugb25seSBzZW5kIGFuZCByZWNlaXZlIGVtYWlsIG9uIHRoZSBiYXNpcyBvZiB0aGUg
dGVybXMgc2V0IG91dCBhdC4NCmh0dHA6Ly93d3cudGlkLmVzL0VTL1BBR0lOQVMvZGlzY2xhaW1l
ci5hc3B4DQo=

From Tina.Tsou.Zouting@huawei.com  Thu Jun 28 10:18:05 2012
Return-Path: <Tina.Tsou.Zouting@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 D74B921F85A0; Thu, 28 Jun 2012 10:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.743
X-Spam-Level: 
X-Spam-Status: No, score=-4.743 tagged_above=-999 required=5 tests=[AWL=0.103,  BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, 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 rmPXyfgOrXk6; Thu, 28 Jun 2012 10:18:05 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 1DBF421F854F; Thu, 28 Jun 2012 10:18:05 -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 AHH11080; Thu, 28 Jun 2012 13:18:04 -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; Thu, 28 Jun 2012 10:16:35 -0700
Received: from dfweml513-mbx.china.huawei.com ([169.254.3.109]) by dfweml408-hub.china.huawei.com ([10.193.5.134]) with mapi id 14.01.0323.003; Thu, 28 Jun 2012 10:16:40 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: "Diego R. Lopez" <diego@tid.es>
Thread-Topic: [alto] Fwd: New Version Notification for draft-xie-alto-sdn-use-cases-01.txt
Thread-Index: AQHNVSMJb5jv8Wdw7k2aRUTS9hbZ2JcP+UmG
Date: Thu, 28 Jun 2012 17:16:40 +0000
Message-ID: <EEF6980D-8040-4FBD-94D7-5651DE4D0F07@huawei.com>
References: <20120628022346.4612.84400.idtracker@ietfa.amsl.com>, <9DA8756D-A668-4346-87CB-7588702545CE@tid.es>
In-Reply-To: <9DA8756D-A668-4346-87CB-7588702545CE@tid.es>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "altoext@ietf.org" <altoext@ietf.org>, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Fwd: New Version Notification for	draft-xie-alto-sdn-use-cases-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: Thu, 28 Jun 2012 17:18:06 -0000

VGhpcyBkcmFmdCB3aWxsIGJlIGRlbW9uc3RyYXRlZCBAIDFzdCBiaXRzLWFuZC1iaXRlcyBldmVu
dCBpbiBJRVRGLTg0LCB3aXRoIHZlbmRvcnMgaW50ZXJvcGVkLg0KVGhlIGN1cnJlbnQgaW5mb3Jt
YXRpb24gaXMgYXQNCmh0dHA6Ly93d3cuaWV0Zi5vcmcvbWVldGluZy84NC9iaXRzLW4tYml0ZXMu
aHRtbA0KDQpUaW5hDQoNCk9uIEp1biAyOCwgMjAxMiwgYXQgNDo0MiBBTSwgIkRpZWdvIFIuIExv
cGV6IiA8ZGllZ29AdGlkLmVzPiB3cm90ZToNCg0KPiANCj4gSGksDQo+IA0KPiBUaGlzIGlzIGEg
cHJvcG9zYWwgb24gdGhlIGludGVyYWN0aW9uIGJldHdlZW4gQUxUTyBhbmQgU0ROIHdlJ2QgbGlr
ZSB0byBkaXNjdXNzDQo+IGF0IG91ciBuZXh0IG1lZXRpbmcgaW4gVmFuY291dmVyLg0KPiANCj4g
Q29tbWVudHMgd2lsbCBiZSBleHRyZW1lbHkgYXBwcmVjaWF0ZWQuDQo+IA0KPiBCZSBnb29kZSwN
Cj4gDQo+IEJlZ2luIGZvcndhcmRlZCBtZXNzYWdlOg0KPj4gQSBuZXcgdmVyc2lvbiBvZiBJLUQs
IGRyYWZ0LXhpZS1hbHRvLXNkbi11c2UtY2FzZXMtMDEudHh0DQo+PiBoYXMgYmVlbiBzdWNjZXNz
ZnVsbHkgc3VibWl0dGVkIGJ5IEhhaXlvbmcgWGllIGFuZCBwb3N0ZWQgdG8gdGhlDQo+PiBJRVRG
IHJlcG9zaXRvcnkuDQo+PiANCj4+IEZpbGVuYW1lOiAgICAgIGRyYWZ0LXhpZS1hbHRvLXNkbi11
c2UtY2FzZXMNCj4+IFJldmlzaW9uOiAgICAgIDAxDQo+PiBUaXRsZTogICAgICAgICAgICAgICAg
IFVzZSBDYXNlcyBmb3IgQUxUTyB3aXRoIFNvZnR3YXJlIERlZmluZWQgTmV0d29ya3MNCj4+IENy
ZWF0aW9uIGRhdGU6ICAgICAgICAgMjAxMi0wNi0yNw0KPj4gV0cgSUQ6ICAgICAgICAgICAgICAg
ICBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCj4+IE51bWJlciBvZiBwYWdlczogMjgNCj4+IFVSTDog
ICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQteGll
LWFsdG8tc2RuLXVzZS1jYXNlcy0wMS50eHQNCj4+IFN0YXR1czogICAgICAgICAgaHR0cDovL2Rh
dGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC14aWUtYWx0by1zZG4tdXNlLWNhc2VzDQo+PiBI
dG1saXplZDogICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXhpZS1hbHRv
LXNkbi11c2UtY2FzZXMtMDENCj4+IERpZmY6ICAgICAgICAgICAgaHR0cDovL3Rvb2xzLmlldGYu
b3JnL3JmY2RpZmY/dXJsMj1kcmFmdC14aWUtYWx0by1zZG4tdXNlLWNhc2VzLTAxDQo+PiANCj4+
IEFic3RyYWN0Og0KPj4gIFRoZSBpbnRyb2R1Y3Rpb24gb2YgU0ROIGZ1bmRhbWVudGFsbHkgY2hh
bmdlcyB0aGUgd2F5IHRoYXQgdGhlIEFMVE8NCj4+ICB3b3Jrcy4gIFRoaXMgZHJhZnQgZGVzY3Jp
YmVzIHRoZSBWZXJ0aWNhbCBBcmNoaXRlY3R1cmUgYW5kIHRoZQ0KPj4gIEhvcml6b250YWwgQXJj
aGl0ZWN0dXJlIGFsbG93aW5nIGNvaGVyZW50IGNvZXhpc3RlbmNlIG9mIGFwcGxpY2F0aW9uDQo+
PiAgbGF5ZXIgdHJhZmZpYyBvcHRpbWl6YXRpb24gKEFMVE8pIHdpdGggc29mdHdhcmUgZGVmaW5l
ZCBuZXR3b3JrDQo+PiAgKFNETikuICBVbmlxdWUgcmVxdWlyZW1lbnRzIGZvciBkZXNpZ24gYW5k
IG9wZXJhdGlvbnMgYXJlIGlkZW50aWZpZWQNCj4+ICBhbmQgc3VtbWFyaXplZCwgc3VnZ2VzdGlu
ZyB0aGF0IHRoZSBWZXJ0aWNhbCBBcmNoaXRlY3R1cmUgYWxsb3dzDQo+PiAgYmV0dGVyIGRpdmlz
aW9uLCBtYW5hZ2VtZW50LCBmbGV4aWJpbGl0eSwgcHJpdmFjeSBjb250cm9sIGFuZCBsb25nLQ0K
Pj4gIHRlcm0gZXZvbHV0aW9uIG9mIHRoZSBuZXR3b3JrLiAgV2UgYWxzbyBkZWZpbmUgdGhlIG1h
aW4gaW50ZXJhY3Rpb25zDQo+PiAgYW5kIGluZm9ybWF0aW9uIGZsb3dzLCBhbmQgcHJlc2VudCBh
IHNldCBvZiB1c2UgY2FzZXMgdG8gaWxsdXN0cmF0ZQ0KPj4gIGhvdyB3ZSBleHRlbmQgQUxUTyB0
byBzdXBwb3J0IFNETiwgaW4gdGhlIFZlcnRpY2FsIEFyY2hpdGVjdHVyZS4NCj4+IA0KPj4gDQo+
PiANCj4+IA0KPj4gVGhlIElFVEYgU2VjcmV0YXJpYXQNCj4gDQo+IA0KPiAtLQ0KPiAiRXN0YSB2
ZXogbm8gZmFsbGFyZW1vcywgRG9jdG9yIEluZmllcm5vIg0KPiANCj4gRHIgRGllZ28gUi4gTG9w
ZXoNCj4gVGVsZWZvbmljYSBJK0QNCj4gaHR0cDovL3Blb3BsZS50aWQuZXMvZGllZ28ubG9wZXov
DQo+IA0KPiBlLW1haWw6IGRpZWdvQHRpZC5lcw0KPiBUZWw6ICAgICszNCA5MTMgMTI5IDA0MQ0K
PiBNb2JpbGU6ICszNCA2ODIgMDUxIDA5MQ0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLQ0KPiANCj4gDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQo+IA0KPiBFc3RlIG1lbnNhamUgc2UgZGlyaWdlIGV4Y2x1c2l2YW1lbnRlIGEgc3UgZGVzdGlu
YXRhcmlvLiBQdWVkZSBjb25zdWx0YXIgbnVlc3RyYSBwb2yoqnRpY2EgZGUgZW52qKpvIHkgcmVj
ZXBjaaiubiBkZSBjb3JyZW8gZWxlY3RyqK5uaWNvIGVuIGVsIGVubGFjZSBzaXR1YWRvIG2oonMg
YWJham8uDQo+IFRoaXMgbWVzc2FnZSBpcyBpbnRlbmRlZCBleGNsdXNpdmVseSBmb3IgaXRzIGFk
ZHJlc3NlZS4gV2Ugb25seSBzZW5kIGFuZCByZWNlaXZlIGVtYWlsIG9uIHRoZSBiYXNpcyBvZiB0
aGUgdGVybXMgc2V0IG91dCBhdC4NCj4gaHR0cDovL3d3dy50aWQuZXMvRVMvUEFHSU5BUy9kaXNj
bGFpbWVyLmFzcHgNCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCj4gYWx0byBtYWlsaW5nIGxpc3QNCj4gYWx0b0BpZXRmLm9yZw0KPiBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FsdG8NCg==

From haiyong.xie@huawei.com  Thu Jun 28 15:16:44 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 28AFA11E80EB; Thu, 28 Jun 2012 15:16:44 -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 ywNWpwsvZvP6; Thu, 28 Jun 2012 15:16:43 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 5D60D11E80D0; Thu, 28 Jun 2012 15:16: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 AHH27169; Thu, 28 Jun 2012 18:16:43 -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; Thu, 28 Jun 2012 15:15:16 -0700
Received: from DFWEML509-MBX.china.huawei.com ([169.254.11.219]) by dfweml406-hub.china.huawei.com ([10.193.5.131]) with mapi id 14.01.0323.003; Thu, 28 Jun 2012 15:15:05 -0700
From: Haiyong Xie <haiyong.xie@huawei.com>
To: "alto@ietf.org" <alto@ietf.org>, "altoext@ietf.org" <altoext@ietf.org>
Thread-Topic: New Version Notification for draft-xie-alto-sdn-extension-use-cases-00.txt
Thread-Index: AQHNVXppIrODMuolQE6EgEaSIjo7a5cQSw6Q
Date: Thu, 28 Jun 2012 22:15:05 +0000
Message-ID: <748A482AA35F7A4A8BD26465029B8C4A1B7C49EC@dfweml509-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.130.121]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Hongtao Yin <hongtao.yin@huawei.com>
Subject: [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: Thu, 28 Jun 2012 22:16:44 -0000

SGkgQWxsLA0KDQpUaGlzIGlzIGEgcHJvcG9zYWwgb24gdGhlIGludGVyYWN0aW9uIGJldHdlZW4g
QUxUTyBhbmQgU0ROIHdlJ2QgbGlrZSB0byBkaXNjdXNzIGF0IG91ciBuZXh0IG1lZXRpbmcgaW4g
VmFuY291dmVyLiBUaGlzIGRyYWZ0IHJlcGxhY2VzIHRoZSBvbGRlciBzdWJtaXNzaW9uIGRyYWZ0
LXhpZS1hbHRvLXNkbi11c2UtY2FzZXMtMDEudHh0IHdoaWNoIHdhcyB3aXRoZHJhd24gYWxyZWFk
eS4NCg0KQ29tbWVudHMgb3IgZGlzY3Vzc2lvbnMgYXJlIGV4dHJlbWVseSB3ZWxjb21lIGFuZCBh
cHByZWNpYXRlZC4NCg0KQmVzdCByZWdhcmRzLA0KSGFpeW9uZw0KDQotLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KRnJvbTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJu
ZXQtZHJhZnRzQGlldGYub3JnXSANClNlbnQ6IFRodXJzZGF5LCBKdW5lIDI4LCAyMDEyIDM6MDcg
UE0NClRvOiBIYWl5b25nIFhpZQ0KQ2M6IGRpZWdvQHRpZC5lczsgSG9uZ3RhbyBZaW47IFRpbmEg
VFNPVQ0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC14aWUtYWx0
by1zZG4tZXh0ZW5zaW9uLXVzZS1jYXNlcy0wMC50eHQNCg0KDQpBIG5ldyB2ZXJzaW9uIG9mIEkt
RCwgZHJhZnQteGllLWFsdG8tc2RuLWV4dGVuc2lvbi11c2UtY2FzZXMtMDAudHh0DQpoYXMgYmVl
biBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IEhhaXlvbmcgWGllIGFuZCBwb3N0ZWQgdG8gdGhl
DQpJRVRGIHJlcG9zaXRvcnkuDQoNCkZpbGVuYW1lOgkgZHJhZnQteGllLWFsdG8tc2RuLWV4dGVu
c2lvbi11c2UtY2FzZXMNClJldmlzaW9uOgkgMDANClRpdGxlOgkJIFVzZSBDYXNlcyBmb3IgQUxU
TyB3aXRoIFNvZnR3YXJlIERlZmluZWQgTmV0d29ya3MNCkNyZWF0aW9uIGRhdGU6CSAyMDEyLTA2
LTI4DQpXRyBJRDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCk51bWJlciBvZiBwYWdlczogMjgN
ClVSTDogICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJh
ZnQteGllLWFsdG8tc2RuLWV4dGVuc2lvbi11c2UtY2FzZXMtMDAudHh0DQpTdGF0dXM6ICAgICAg
ICAgIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQteGllLWFsdG8tc2RuLWV4
dGVuc2lvbi11c2UtY2FzZXMNCkh0bWxpemVkOiAgICAgICAgaHR0cDovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQteGllLWFsdG8tc2RuLWV4dGVuc2lvbi11c2UtY2FzZXMtMDANCg0KDQpBYnN0
cmFjdDoNCiAgIFRoZSBpbnRyb2R1Y3Rpb24gb2YgU0ROIGZ1bmRhbWVudGFsbHkgY2hhbmdlcyB0
aGUgd2F5IHRoYXQgdGhlIEFMVE8NCiAgIHdvcmtzLiAgVGhpcyBkcmFmdCBkZXNjcmliZXMgdGhl
IFZlcnRpY2FsIEFyY2hpdGVjdHVyZSBhbmQgdGhlDQogICBIb3Jpem9udGFsIEFyY2hpdGVjdHVy
ZSBhbGxvd2luZyBjb2hlcmVudCBjb2V4aXN0ZW5jZSBvZiBhcHBsaWNhdGlvbg0KICAgbGF5ZXIg
dHJhZmZpYyBvcHRpbWl6YXRpb24gKEFMVE8pIHdpdGggc29mdHdhcmUgZGVmaW5lZCBuZXR3b3Jr
DQogICAoU0ROKS4gIFVuaXF1ZSByZXF1aXJlbWVudHMgZm9yIGRlc2lnbiBhbmQgb3BlcmF0aW9u
cyBhcmUgaWRlbnRpZmllZA0KICAgYW5kIHN1bW1hcml6ZWQsIHN1Z2dlc3RpbmcgdGhhdCB0aGUg
VmVydGljYWwgQXJjaGl0ZWN0dXJlIGFsbG93cw0KICAgYmV0dGVyIGRpdmlzaW9uLCBtYW5hZ2Vt
ZW50LCBmbGV4aWJpbGl0eSwgcHJpdmFjeSBjb250cm9sIGFuZCBsb25nLQ0KICAgdGVybSBldm9s
dXRpb24gb2YgdGhlIG5ldHdvcmsuICBXZSBhbHNvIGRlZmluZSB0aGUgbWFpbiBpbnRlcmFjdGlv
bnMNCiAgIGFuZCBpbmZvcm1hdGlvbiBmbG93cywgYW5kIHByZXNlbnQgYSBzZXQgb2YgdXNlIGNh
c2VzIHRvIGlsbHVzdHJhdGUNCiAgIGhvdyB3ZSBleHRlbmQgQUxUTyB0byBzdXBwb3J0IFNETiwg
aW4gdGhlIFZlcnRpY2FsIEFyY2hpdGVjdHVyZS4NCg0KICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IA0KDQoNClRoZSBJRVRGIFNlY3JldGFyaWF0DQo=

From haibin.song@huawei.com  Fri Jun 29 02:28:37 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 EF7A221F8731 for <alto@ietfa.amsl.com>; Fri, 29 Jun 2012 02:28:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.12
X-Spam-Level: 
X-Spam-Status: No, score=-6.12 tagged_above=-999 required=5 tests=[AWL=0.479,  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 DTquks8mfHMM for <alto@ietfa.amsl.com>; Fri, 29 Jun 2012 02:28:36 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 3F4DA21F8723 for <alto@ietf.org>; Fri, 29 Jun 2012 02:28:36 -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 AHO81139; Fri, 29 Jun 2012 05:28:36 -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; Fri, 29 Jun 2012 02:28:19 -0700
Received: from SZXEML426-HUB.china.huawei.com (10.72.61.34) by dfweml403-hub.china.huawei.com (10.193.5.151) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 29 Jun 2012 02:28:15 -0700
Received: from SZXEML534-MBX.china.huawei.com ([169.254.2.36]) by szxeml426-hub.china.huawei.com ([10.72.61.34]) with mapi id 14.01.0323.003; Fri, 29 Jun 2012 17:28:10 +0800
From: Songhaibin <haibin.song@huawei.com>
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
Thread-Topic: [alto] ALTO discovery in roaming scenario
Thread-Index: Ac0Fw01LNWVAmHe9T920S4QOtl0VRwG9ShOAADD7c2X//8qrgIAAjJtG/4DH49D+/mR/0P37yYCw+/c7DDD34dq8AA==
Date: Fri, 29 Jun 2012 09:28:10 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F23AB998C@szxeml534-mbx.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F15864255@szxeml534-mbx.china.huawei.com> <CA+cvDabLFKH_Pi0z7vhyXjOhcx3ya-YcJLOR8aMKvx-RN2wxaw@mail.gmail.com> <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>
In-Reply-To: <2A886F9088894347A3BE0CC5B7A85F3E891A9BB6B2@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: Fri, 29 Jun 2012 09:28:38 -0000

Sorry for the late reply.

Here is a little text I proposed to add:

" A mobile node has two addresses - a permanent home address and a care-of =
address (CoA), which is associated with the network the mobile node is visi=
ting. When acting as transmitter, a mobile node sends packets directly to t=
he other communicating node, without sending the packets through the home a=
gent, using its permanent home address as the source address for the IP pac=
kets. This is known as triangular routing. In this case, the ALTO server di=
scovered by the CoA would be used to get the transmission guidance. However=
, it still uses the ALTO server discovered by its home address or home agen=
t address to get guidance to retrieve content from content sources in the n=
etwork.

The foreign agent could also employ reverse tunneling by tunneling the mobi=
le node's packets to the home agent, which in turn forwards them to the com=
municating node. This is needed in networks whose gateway routers check tha=
t the source IP address of the mobile host belongs to their subnet or disca=
rd the packet otherwise. In this case, the ALTO server discovered by the mo=
bile node's home address or home agent address would always be the right ch=
oice.

If an end host uses proxy to access the network, such as in a company which=
 uses VPN tunnels to connect different sub-divisions in different locations=
, the proxy IP address should be used for the ALTO server discovery instead=
 of the end host's IP address.

In general, according to the data path, the client's IP address/agent's IP =
address which directly connect and route the client's data to/from Internet=
 should be used for the correspondence ALTO server discovery."

Does this make sense?

-Haibin

> -----Original Message-----
> From: Scharf, Michael (Michael) [mailto:michael.scharf@alcatel-lucent.com=
]
> Sent: Thursday, June 21, 2012 4:18 PM
> To: Songhaibin
> Cc: alto@ietf.org
> Subject: RE: [alto] ALTO discovery in roaming scenario
>=20
> Haibin,
>=20
> Can you please explain how the scenario you describe is different to a no=
rmal
> NAT middlebox?
>=20
> Regarding NAT, the draft right now states that there are various methods =
to find
> out the right IP address:
>=20
>    A client can have several candidate IP addresses that it may use for
>    the discovery process.  For example if it is located behind a NAT, a
>    private and a public IP address may be used for the discovery
>    process.  It depends on the deployment scenario which of the IP
>    addresses is the correct one.  Thus it is out-of-scope of this
>    document to specify how exactly the client finds the right IP
>    address.  However in the following we list methods that may be used
>    in order to determine these candidate IP addresses.  Generally in P2P
>    environments peers already have implemented mechanisms for NAT-
>    traversal.  This includes proprietary solutions to determine a peer's
>    public IP address, for example by asking a neighbour peer about its
>    record of the own IP address.  Non-proprietary solutions that are
>    favorable include the Session Traversal Utilities for NAT (STUN)
>    [RFC5986] protocol to determine the public address.  If the client is
>    behind a residential gateway another option may be to use Universal
>    Plug and Play (UPnP) [UPnP-IGD-WANIPConnection1] or the NAT Port
>    Mapping Protocol (NAT-PMP) [I-D.cheshire-nat-pmp].
>=20
>=20
> What text do you suggest to add to that?
>=20
> Thanks,
>=20
> Michael
>=20
>=20
> > -----Original Message-----
> > From: Songhaibin [mailto:haibin.song@huawei.com]
> > Sent: Thursday, June 21, 2012 5:02 AM
> > To: Scharf, Michael (Michael)
> > Cc: alto@ietf.org
> > Subject: RE: [alto] ALTO discovery in roaming scenario
> >
> > Please imagine a gateway/proxy based network access, the ALTO
> > client is the end host, but actually the IP address for
> > gateway/proxy which connect the end host to the network
> > should be used for ALTO server discovery. The change of
> > end-host IP and gateway/proxy IP is independent somehow. I
> > hope this clarification helps.
> >
> > BR,
> > -Haibin
> >
> > > -----Original Message-----
> > > From: Scharf, Michael (Michael)
> > > [mailto:michael.scharf@alcatel-lucent.com]
> > > Sent: Wednesday, June 20, 2012 8:07 PM
> > > To: Songhaibin
> > > Cc: alto@ietf.org
> > > Subject: RE: [alto] ALTO discovery in roaming scenario
> > >
> > > Haibin,
> > >
> > > The draft already states:
> > >
> > >    o  A change of the IP address at an interface
> > invalidates the result
> > >       of the ALTO server discovery procedure.  For
> > instance, if the IP
> > >       address assigned to a mobile host changes due to host
> > mobility, it
> > >       is required to run the ALTO server discovery
> > procedure for the new
> > >       IP address without relying on earlier gained information.
> > >
> > > Could you please explain what text is missing in the draft,
> > and what
> > > technical solution you suggest? For instance, if the mobile network
> > > uses "Proxy Mobile IP"?
> > >
> > > My understanding is that in reality roaming/normadic use results in
> > > either of two
> > > possibilities:
> > >
> > > (1) There is a change of the IP address of the mobile host.
> > This case
> > > is already explained in the draft.
> > >
> > > (2) The IP address of the mobile host does not change.
> > Then, the host
> > > remains in the same IP subnet, and thus the ALTO discovery
> > result is still valid.
> > >
> > > In both cases, the current text in the discovery draft
> > seems to be just fine, right?
> > >
> > > Thanks
> > >
> > > Michael
> > >
> > >
> > > > -----Original Message-----
> > > > From: alto-bounces@ietf.org
> > [mailto:alto-bounces@ietf.org] On Behalf
> > > > Of Songhaibin
> > > > Sent: Monday, June 18, 2012 1:22 PM
> > > > To: Songhaibin; Richard Alimi
> > > > Cc: alto@ietf.org
> > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > >
> > > > I would like to dig this from the tomb and see how the WG
> > would like
> > > > to solve the ALTO discovery in the roaming/nomadic
> > scenario. I would
> > > > also like to see it in the ALTO server discovery document.
> > > >
> > > > -Haibin
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org]
> > > > On Behalf
> > > > > Of Songhaibin
> > > > > Sent: Thursday, March 29, 2012 8:34 PM
> > > > > To: Richard Alimi
> > > > > Cc: alto@ietf.org
> > > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > > >
> > > > > Hi Rich,
> > > > >
> > > > > I think your proposal makes sense. The wikipedia document
> > > > > http://en.wikipedia.org/wiki/Mobile_IP provides some links
> > > > to relative
> > > > > RFCs. We may find details in these RFCs. I will also try to
> > > > read them.
> > > > >
> > > > > BR,
> > > > > -Haibin
> > > > >
> > > > > ________________________________________
> > > > > From: richard.alimi@gmail.com [richard.alimi@gmail.com] on
> > > > behalf of
> > > > > Richard Alimi [rich@velvetsea.net]
> > > > > Sent: Thursday, March 29, 2012 8:09 PM
> > > > > To: Songhaibin
> > > > > Cc: alto@ietf.org
> > > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > > >
> > > > > On Thu, Mar 29, 2012 at 12:26 AM, Songhaibin
> > > > <haibin.song@huawei.com>
> > > > > wrote:
> > > > > > Hi Rich,
> > > > > >
> > > > > > Thank you for the discussion. See inline.
> > > > > >
> > > > > > ________________________________________
> > > > > > From: richard.alimi@gmail.com [richard.alimi@gmail.com]
> > > > on behalf of
> > > > > > Richard
> > > > > Alimi [rich@velvetsea.net]
> > > > > > Sent: Wednesday, March 28, 2012 11:57 PM
> > > > > > To: Songhaibin
> > > > > > Cc: alto@ietf.org
> > > > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > > > >
> > > > > > On Mon, Mar 19, 2012 at 4:28 AM, Songhaibin
> > > > <haibin.song@huawei.com>
> > > > > wrote:
> > > > > >> Hi,
> > > > > >>
> > > > > >> The indicated by the subject, which is perhaps not fully
> > > > solved in
> > > > > >> the discovery
> > > > > draft, I guess at least the following scenarios should be
> > > > considered.
> > > > > As I'm not an expert on roaming technology, please correct
> > > > me if you find I am wrong.
> > > > > >>
> > > > > >> (1) The ALTO client has left its home network, and its
> > > > IP address
> > > > > >> is dynamically
> > > > > assigned by the current network provider (through DHCP or any
> > > > > other method), but the ALTO client still uses its home agent to
> > > > access the
> > > > > Internet. In this case, the ALTO server resided in its home
> > > > > network should be the right ALTO server to be discovered.
> > > > > >>
> > > > > >> (2) The ALTO client has left its home network, and its
> > > > IP address
> > > > > >> is dynamically
> > > > > assigned by the current network provider, and the ALTO
> > > > client uses the
> > > > > foreign agent to access Internet or uses its IP address
> > directly
> > > > > to access Internet. In this scenario, the ALTO server resided
> > > > in the current network should be the right one.
> > > > > And the existing discovery mechanism works in this scenario.
> > > > > >>
> > > > > >> (3) If the ALTO client has a persistent IP address when
> > > > > >> roaming, and it uses
> > > > > home agent to access Internet, but make large data route to the
> > > > > foreign agent directly (optimized routing mode). In this
> > > > scenario, the
> > > > > ALTO server resided in the current network should be the
> > > > right one to
> > > > > be discovered. However, if it does not adopt the
> > optimized routing
> > > > > mode, the ALTO server in the home network should be the
> > right one.
> > > > > >>
> > > > > >
> > > > > > I'm not familiar with the technologies backing this, but
> > > > what entity
> > > > > > decides the route that a particular packet will take? Is this
> > > > > > DPI living in the network where the client is
> > roaming?  Or is it
> > > > > > some entity on the client itself?
> > > > > >
> > > > > > [Haibin] No, it is not DPI based. Although I'm not an
> > > > expert on this
> > > > > > either, but I
> > > > > think in the mobile IPv6 scenario, the decision is made through
> > > > > the negotiation among the mobile node, home agent, and other
> > > > correspondent nodes.
> > > > > >
> > > > >
> > > > > Thinking about this at the high level, If the mobile node
> > > > is involved
> > > > > in the negotiation, then it seems like it could work like the
> > > > > following for this case:
> > > > > (1) Discover an ALTO Server using the home agent (same as case 1
> > > > > above)
> > > > > (2) Discover an ALTO Server using the current network (same
> > > > as case 2
> > > > > above)
> > > > > (3) When it comes time to apply the ALTO information, apply the
> > > > > correct set depending on the routing for that
> > particular request.
> > > > >
> > > > > Is that compatible with whatever technologies are used for
> > > > these scenarios?
> > > > >
> > > > > Details on how this works and the negotiation actually
> > takes place
> > > > > would be useful.
> > > > >
> > > > > Rich
> > > > >
> > > > > > BR,
> > > > > > -Haibin
> > > > > >
> > > > > >> (4) (this one is not about roaming) Assume in a big
> > > > company which
> > > > > >> has a few
> > > > > branch offices in different locations, and VPN tunnels
> > are used to
> > > > > connect these branch offices, employees use one proxy to access
> > > > > Internet. Then the ALTO server discovery should be based on the
> > > > > proxy's IP address instead of the user's IP address.  It
> > > > also applies
> > > > > to other similar scenarios when end-hosts using proxies.
> > > > > >>
> > > > > >> It might not be a problem when doing third party
> > discovery, but
> > > > > >> have to
> > > > > consider when doing the discovery by the end-host itself.
> > > > > >>
> > > > > >> BR,
> > > > > >> -Haibin
> > > > > >> _______________________________________________
> > > > > >> 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
> > > > _______________________________________________
> > > > alto mailing list
> > > > alto@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/alto
> > > >
> >

From michael.scharf@alcatel-lucent.com  Fri Jun 29 07:58:46 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 24B9E21F86E3 for <alto@ietfa.amsl.com>; Fri, 29 Jun 2012 07:58:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.849
X-Spam-Level: 
X-Spam-Status: No, score=-9.849 tagged_above=-999 required=5 tests=[AWL=0.400,  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 wGvhPhl5dcxX for <alto@ietfa.amsl.com>; Fri, 29 Jun 2012 07:58:44 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by ietfa.amsl.com (Postfix) with ESMTP id DF89D21F856D for <alto@ietf.org>; Fri, 29 Jun 2012 07:58:43 -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 q5TEwOtu006472 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 29 Jun 2012 16:58:33 +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, 29 Jun 2012 16:58:29 +0200
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Songhaibin <haibin.song@huawei.com>
Date: Fri, 29 Jun 2012 16:58:27 +0200
Thread-Topic: [alto] ALTO discovery in roaming scenario
Thread-Index: Ac0Fw01LNWVAmHe9T920S4QOtl0VRwG9ShOAADD7c2X//8qrgIAAjJtG/4DH49D+/mR/0P37yYCw+/c7DDD34dq8AO/DUJpA
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E891A9BB830@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
References: <E33E01DFD5BEA24B9F3F18671078951F15864255@szxeml534-mbx.china.huawei.com> <CA+cvDabLFKH_Pi0z7vhyXjOhcx3ya-YcJLOR8aMKvx-RN2wxaw@mail.gmail.com> <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>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F23AB998C@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.13
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: Fri, 29 Jun 2012 14:58:46 -0000

I might be wrong, but I think that this description is specific to a networ=
k that uses "mobile IP". It misses the differences between "mobile IPv4" an=
d "mobile IPv6" (different realization of triangular routing, foreign agent=
, etc.).

I don't think that adding text specific to selected mobility mechanisms is =
the right approach for this draft. For instance, mobile networks can instea=
d use "proxy mobile IP". In that case, a mobile node has no two addresses a=
s described in your text. And there are many other existing proposals for m=
obility mechanisms for IP (hierarchical mobility, network mobility, etc.). =
We should not start to discuss technical details of proposed IP mobility so=
lutions in an ALTO draft, imho.

I think that all those use cases can simply be summarized by:  "In general,=
 the ALTO server discovery should be based on the IP address that is used t=
o communicate with other peers".

Right?

Michael


> -----Original Message-----
> From: Songhaibin [mailto:haibin.song@huawei.com]
> Sent: Friday, June 29, 2012 11:28 AM
> To: Scharf, Michael (Michael)
> Cc: alto@ietf.org
> Subject: RE: [alto] ALTO discovery in roaming scenario
>
> Sorry for the late reply.
>
> Here is a little text I proposed to add:
>
> " A mobile node has two addresses - a permanent home address
> and a care-of address (CoA), which is associated with the
> network the mobile node is visiting. When acting as
> transmitter, a mobile node sends packets directly to the
> other communicating node, without sending the packets through
> the home agent, using its permanent home address as the
> source address for the IP packets. This is known as
> triangular routing. In this case, the ALTO server discovered
> by the CoA would be used to get the transmission guidance.
> However, it still uses the ALTO server discovered by its home
> address or home agent address to get guidance to retrieve
> content from content sources in the network.
>
> The foreign agent could also employ reverse tunneling by
> tunneling the mobile node's packets to the home agent, which
> in turn forwards them to the communicating node. This is
> needed in networks whose gateway routers check that the
> source IP address of the mobile host belongs to their subnet
> or discard the packet otherwise. In this case, the ALTO
> server discovered by the mobile node's home address or home
> agent address would always be the right choice.
>
> If an end host uses proxy to access the network, such as in a
> company which uses VPN tunnels to connect different
> sub-divisions in different locations, the proxy IP address
> should be used for the ALTO server discovery instead of the
> end host's IP address.
>
> In general, according to the data path, the client's IP
> address/agent's IP address which directly connect and route
> the client's data to/from Internet should be used for the
> correspondence ALTO server discovery."
>
> Does this make sense?
>
> -Haibin
>
> > -----Original Message-----
> > From: Scharf, Michael (Michael)
> > [mailto:michael.scharf@alcatel-lucent.com]
> > Sent: Thursday, June 21, 2012 4:18 PM
> > To: Songhaibin
> > Cc: alto@ietf.org
> > Subject: RE: [alto] ALTO discovery in roaming scenario
> >
> > Haibin,
> >
> > Can you please explain how the scenario you describe is
> different to a
> > normal NAT middlebox?
> >
> > Regarding NAT, the draft right now states that there are various
> > methods to find out the right IP address:
> >
> >    A client can have several candidate IP addresses that it
> may use for
> >    the discovery process.  For example if it is located
> behind a NAT, a
> >    private and a public IP address may be used for the discovery
> >    process.  It depends on the deployment scenario which of the IP
> >    addresses is the correct one.  Thus it is out-of-scope of this
> >    document to specify how exactly the client finds the right IP
> >    address.  However in the following we list methods that
> may be used
> >    in order to determine these candidate IP addresses.
> Generally in P2P
> >    environments peers already have implemented mechanisms for NAT-
> >    traversal.  This includes proprietary solutions to
> determine a peer's
> >    public IP address, for example by asking a neighbour
> peer about its
> >    record of the own IP address.  Non-proprietary solutions that are
> >    favorable include the Session Traversal Utilities for NAT (STUN)
> >    [RFC5986] protocol to determine the public address.  If
> the client is
> >    behind a residential gateway another option may be to
> use Universal
> >    Plug and Play (UPnP) [UPnP-IGD-WANIPConnection1] or the NAT Port
> >    Mapping Protocol (NAT-PMP) [I-D.cheshire-nat-pmp].
> >
> >
> > What text do you suggest to add to that?
> >
> > Thanks,
> >
> > Michael
> >
> >
> > > -----Original Message-----
> > > From: Songhaibin [mailto:haibin.song@huawei.com]
> > > Sent: Thursday, June 21, 2012 5:02 AM
> > > To: Scharf, Michael (Michael)
> > > Cc: alto@ietf.org
> > > Subject: RE: [alto] ALTO discovery in roaming scenario
> > >
> > > Please imagine a gateway/proxy based network access, the
> ALTO client
> > > is the end host, but actually the IP address for
> gateway/proxy which
> > > connect the end host to the network should be used for
> ALTO server
> > > discovery. The change of end-host IP and gateway/proxy IP is
> > > independent somehow. I hope this clarification helps.
> > >
> > > BR,
> > > -Haibin
> > >
> > > > -----Original Message-----
> > > > From: Scharf, Michael (Michael)
> > > > [mailto:michael.scharf@alcatel-lucent.com]
> > > > Sent: Wednesday, June 20, 2012 8:07 PM
> > > > To: Songhaibin
> > > > Cc: alto@ietf.org
> > > > Subject: RE: [alto] ALTO discovery in roaming scenario
> > > >
> > > > Haibin,
> > > >
> > > > The draft already states:
> > > >
> > > >    o  A change of the IP address at an interface
> > > invalidates the result
> > > >       of the ALTO server discovery procedure.  For
> > > instance, if the IP
> > > >       address assigned to a mobile host changes due to host
> > > mobility, it
> > > >       is required to run the ALTO server discovery
> > > procedure for the new
> > > >       IP address without relying on earlier gained information.
> > > >
> > > > Could you please explain what text is missing in the draft,
> > > and what
> > > > technical solution you suggest? For instance, if the mobile
> > > > network uses "Proxy Mobile IP"?
> > > >
> > > > My understanding is that in reality roaming/normadic
> use results
> > > > in either of two
> > > > possibilities:
> > > >
> > > > (1) There is a change of the IP address of the mobile host.
> > > This case
> > > > is already explained in the draft.
> > > >
> > > > (2) The IP address of the mobile host does not change.
> > > Then, the host
> > > > remains in the same IP subnet, and thus the ALTO discovery
> > > result is still valid.
> > > >
> > > > In both cases, the current text in the discovery draft
> > > seems to be just fine, right?
> > > >
> > > > Thanks
> > > >
> > > > Michael
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: alto-bounces@ietf.org
> > > [mailto:alto-bounces@ietf.org] On Behalf
> > > > > Of Songhaibin
> > > > > Sent: Monday, June 18, 2012 1:22 PM
> > > > > To: Songhaibin; Richard Alimi
> > > > > Cc: alto@ietf.org
> > > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > > >
> > > > > I would like to dig this from the tomb and see how the WG
> > > would like
> > > > > to solve the ALTO discovery in the roaming/nomadic
> > > scenario. I would
> > > > > also like to see it in the ALTO server discovery document.
> > > > >
> > > > > -Haibin
> > > > >
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org]
> > > > > On Behalf
> > > > > > Of Songhaibin
> > > > > > Sent: Thursday, March 29, 2012 8:34 PM
> > > > > > To: Richard Alimi
> > > > > > Cc: alto@ietf.org
> > > > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > > > >
> > > > > > Hi Rich,
> > > > > >
> > > > > > I think your proposal makes sense. The wikipedia document
> > > > > > http://en.wikipedia.org/wiki/Mobile_IP provides some links
> > > > > to relative
> > > > > > RFCs. We may find details in these RFCs. I will also try to
> > > > > read them.
> > > > > >
> > > > > > BR,
> > > > > > -Haibin
> > > > > >
> > > > > > ________________________________________
> > > > > > From: richard.alimi@gmail.com [richard.alimi@gmail.com] on
> > > > > behalf of
> > > > > > Richard Alimi [rich@velvetsea.net]
> > > > > > Sent: Thursday, March 29, 2012 8:09 PM
> > > > > > To: Songhaibin
> > > > > > Cc: alto@ietf.org
> > > > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > > > >
> > > > > > On Thu, Mar 29, 2012 at 12:26 AM, Songhaibin
> > > > > <haibin.song@huawei.com>
> > > > > > wrote:
> > > > > > > Hi Rich,
> > > > > > >
> > > > > > > Thank you for the discussion. See inline.
> > > > > > >
> > > > > > > ________________________________________
> > > > > > > From: richard.alimi@gmail.com [richard.alimi@gmail.com]
> > > > > on behalf of
> > > > > > > Richard
> > > > > > Alimi [rich@velvetsea.net]
> > > > > > > Sent: Wednesday, March 28, 2012 11:57 PM
> > > > > > > To: Songhaibin
> > > > > > > Cc: alto@ietf.org
> > > > > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > > > > >
> > > > > > > On Mon, Mar 19, 2012 at 4:28 AM, Songhaibin
> > > > > <haibin.song@huawei.com>
> > > > > > wrote:
> > > > > > >> Hi,
> > > > > > >>
> > > > > > >> The indicated by the subject, which is perhaps not fully
> > > > > solved in
> > > > > > >> the discovery
> > > > > > draft, I guess at least the following scenarios should be
> > > > > considered.
> > > > > > As I'm not an expert on roaming technology, please correct
> > > > > me if you find I am wrong.
> > > > > > >>
> > > > > > >> (1) The ALTO client has left its home network, and its
> > > > > IP address
> > > > > > >> is dynamically
> > > > > > assigned by the current network provider (through
> DHCP or any
> > > > > > other method), but the ALTO client still uses its
> home agent
> > > > > > to
> > > > > access the
> > > > > > Internet. In this case, the ALTO server resided in its home
> > > > > > network should be the right ALTO server to be discovered.
> > > > > > >>
> > > > > > >> (2) The ALTO client has left its home network, and its
> > > > > IP address
> > > > > > >> is dynamically
> > > > > > assigned by the current network provider, and the ALTO
> > > > > client uses the
> > > > > > foreign agent to access Internet or uses its IP address
> > > directly
> > > > > > to access Internet. In this scenario, the ALTO
> server resided
> > > > > in the current network should be the right one.
> > > > > > And the existing discovery mechanism works in this scenario.
> > > > > > >>
> > > > > > >> (3) If the ALTO client has a persistent IP address when
> > > > > > >> roaming, and it uses
> > > > > > home agent to access Internet, but make large data route to
> > > > > > the foreign agent directly (optimized routing mode). In this
> > > > > scenario, the
> > > > > > ALTO server resided in the current network should be the
> > > > > right one to
> > > > > > be discovered. However, if it does not adopt the
> > > optimized routing
> > > > > > mode, the ALTO server in the home network should be the
> > > right one.
> > > > > > >>
> > > > > > >
> > > > > > > I'm not familiar with the technologies backing this, but
> > > > > what entity
> > > > > > > decides the route that a particular packet will take? Is
> > > > > > > this DPI living in the network where the client is
> > > roaming?  Or is it
> > > > > > > some entity on the client itself?
> > > > > > >
> > > > > > > [Haibin] No, it is not DPI based. Although I'm not an
> > > > > expert on this
> > > > > > > either, but I
> > > > > > think in the mobile IPv6 scenario, the decision is made
> > > > > > through the negotiation among the mobile node, home
> agent, and
> > > > > > other
> > > > > correspondent nodes.
> > > > > > >
> > > > > >
> > > > > > Thinking about this at the high level, If the mobile node
> > > > > is involved
> > > > > > in the negotiation, then it seems like it could
> work like the
> > > > > > following for this case:
> > > > > > (1) Discover an ALTO Server using the home agent
> (same as case
> > > > > > 1
> > > > > > above)
> > > > > > (2) Discover an ALTO Server using the current network (same
> > > > > as case 2
> > > > > > above)
> > > > > > (3) When it comes time to apply the ALTO information, apply
> > > > > > the correct set depending on the routing for that
> > > particular request.
> > > > > >
> > > > > > Is that compatible with whatever technologies are used for
> > > > > these scenarios?
> > > > > >
> > > > > > Details on how this works and the negotiation actually
> > > takes place
> > > > > > would be useful.
> > > > > >
> > > > > > Rich
> > > > > >
> > > > > > > BR,
> > > > > > > -Haibin
> > > > > > >
> > > > > > >> (4) (this one is not about roaming) Assume in a big
> > > > > company which
> > > > > > >> has a few
> > > > > > branch offices in different locations, and VPN tunnels
> > > are used to
> > > > > > connect these branch offices, employees use one proxy to
> > > > > > access Internet. Then the ALTO server discovery should be
> > > > > > based on the proxy's IP address instead of the user's IP
> > > > > > address.  It
> > > > > also applies
> > > > > > to other similar scenarios when end-hosts using proxies.
> > > > > > >>
> > > > > > >> It might not be a problem when doing third party
> > > discovery, but
> > > > > > >> have to
> > > > > > consider when doing the discovery by the end-host itself.
> > > > > > >>
> > > > > > >> BR,
> > > > > > >> -Haibin
> > > > > > >> _______________________________________________
> > > > > > >> 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
> > > > > _______________________________________________
> > > > > alto mailing list
> > > > > alto@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/alto
> > > > >
> > >
>

From haibin.song@huawei.com  Fri Jun 29 19:35:15 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 6EB6121F84C8 for <alto@ietfa.amsl.com>; Fri, 29 Jun 2012 19:35:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.157
X-Spam-Level: 
X-Spam-Status: No, score=-6.157 tagged_above=-999 required=5 tests=[AWL=0.442,  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 NYiwFSk+2f1K for <alto@ietfa.amsl.com>; Fri, 29 Jun 2012 19:35:13 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2CA5A11E8073 for <alto@ietf.org>; Fri, 29 Jun 2012 19:35:13 -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 AHP30916; Fri, 29 Jun 2012 22:35:12 -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; Fri, 29 Jun 2012 19:35:16 -0700
Received: from SZXEML440-HUB.china.huawei.com (10.72.61.75) by dfweml406-hub.china.huawei.com (10.193.5.131) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 29 Jun 2012 19:35:11 -0700
Received: from SZXEML534-MBS.china.huawei.com ([169.254.6.60]) by SZXEML440-HUB.china.huawei.com ([10.72.61.75]) with mapi id 14.01.0323.003; Sat, 30 Jun 2012 10:35:07 +0800
From: Songhaibin <haibin.song@huawei.com>
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
Thread-Topic: [alto] ALTO discovery in roaming scenario
Thread-Index: Ac0Fw01LNWVAmHe9T920S4QOtl0VRwG9ShOAADD7c2X//8qrgIAAjJtG/4DH49D+/mR/0P37yYCw+/c7DDD34dq8AO/DUJpA34XcZvA=
Date: Sat, 30 Jun 2012 02:35:06 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F23AC8D73@szxeml534-mbs.china.huawei.com>
References: <E33E01DFD5BEA24B9F3F18671078951F15864255@szxeml534-mbx.china.huawei.com> <CA+cvDabLFKH_Pi0z7vhyXjOhcx3ya-YcJLOR8aMKvx-RN2wxaw@mail.gmail.com> <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>
In-Reply-To: <2A886F9088894347A3BE0CC5B7A85F3E891A9BB830@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: Sat, 30 Jun 2012 02:35:15 -0000

I'm very glad that you understand my proposal. If the text missed some tech=
nical 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?

Thanks a lot,
-Haibin

> -----Original Message-----
> From: Scharf, Michael (Michael) [mailto:michael.scharf@alcatel-lucent.com=
]
> Sent: Friday, June 29, 2012 10:58 PM
> To: Songhaibin
> Cc: alto@ietf.org
> Subject: RE: [alto] ALTO discovery in roaming scenario
>=20
> I might be wrong, but I think that this description is specific to a netw=
ork that
> uses "mobile IP". It misses the differences between "mobile IPv4" and "mo=
bile
> IPv6" (different realization of triangular routing, foreign agent, etc.).
>=20
> I don't think that adding text specific to selected mobility mechanisms i=
s the right
> approach for this draft. For instance, mobile networks can instead use "p=
roxy
> mobile IP". In that case, a mobile node has no two addresses as described=
 in your
> text. And there are many other existing proposals for mobility mechanisms=
 for IP
> (hierarchical mobility, network mobility, etc.). We should not start to d=
iscuss
> technical details of proposed IP mobility solutions in an ALTO draft, imh=
o.
>=20
> I think that all those use cases can simply be summarized by:  "In genera=
l, the
> ALTO server discovery should be based on the IP address that is used to
> communicate with other peers".
>=20
> Right?
>=20
> Michael
>=20
>=20
> > -----Original Message-----
> > From: Songhaibin [mailto:haibin.song@huawei.com]
> > Sent: Friday, June 29, 2012 11:28 AM
> > To: Scharf, Michael (Michael)
> > Cc: alto@ietf.org
> > Subject: RE: [alto] ALTO discovery in roaming scenario
> >
> > Sorry for the late reply.
> >
> > Here is a little text I proposed to add:
> >
> > " A mobile node has two addresses - a permanent home address
> > and a care-of address (CoA), which is associated with the
> > network the mobile node is visiting. When acting as
> > transmitter, a mobile node sends packets directly to the
> > other communicating node, without sending the packets through
> > the home agent, using its permanent home address as the
> > source address for the IP packets. This is known as
> > triangular routing. In this case, the ALTO server discovered
> > by the CoA would be used to get the transmission guidance.
> > However, it still uses the ALTO server discovered by its home
> > address or home agent address to get guidance to retrieve
> > content from content sources in the network.
> >
> > The foreign agent could also employ reverse tunneling by
> > tunneling the mobile node's packets to the home agent, which
> > in turn forwards them to the communicating node. This is
> > needed in networks whose gateway routers check that the
> > source IP address of the mobile host belongs to their subnet
> > or discard the packet otherwise. In this case, the ALTO
> > server discovered by the mobile node's home address or home
> > agent address would always be the right choice.
> >
> > If an end host uses proxy to access the network, such as in a
> > company which uses VPN tunnels to connect different
> > sub-divisions in different locations, the proxy IP address
> > should be used for the ALTO server discovery instead of the
> > end host's IP address.
> >
> > In general, according to the data path, the client's IP
> > address/agent's IP address which directly connect and route
> > the client's data to/from Internet should be used for the
> > correspondence ALTO server discovery."
> >
> > Does this make sense?
> >
> > -Haibin
> >
> > > -----Original Message-----
> > > From: Scharf, Michael (Michael)
> > > [mailto:michael.scharf@alcatel-lucent.com]
> > > Sent: Thursday, June 21, 2012 4:18 PM
> > > To: Songhaibin
> > > Cc: alto@ietf.org
> > > Subject: RE: [alto] ALTO discovery in roaming scenario
> > >
> > > Haibin,
> > >
> > > Can you please explain how the scenario you describe is
> > different to a
> > > normal NAT middlebox?
> > >
> > > Regarding NAT, the draft right now states that there are various
> > > methods to find out the right IP address:
> > >
> > >    A client can have several candidate IP addresses that it
> > may use for
> > >    the discovery process.  For example if it is located
> > behind a NAT, a
> > >    private and a public IP address may be used for the discovery
> > >    process.  It depends on the deployment scenario which of the IP
> > >    addresses is the correct one.  Thus it is out-of-scope of this
> > >    document to specify how exactly the client finds the right IP
> > >    address.  However in the following we list methods that
> > may be used
> > >    in order to determine these candidate IP addresses.
> > Generally in P2P
> > >    environments peers already have implemented mechanisms for NAT-
> > >    traversal.  This includes proprietary solutions to
> > determine a peer's
> > >    public IP address, for example by asking a neighbour
> > peer about its
> > >    record of the own IP address.  Non-proprietary solutions that are
> > >    favorable include the Session Traversal Utilities for NAT (STUN)
> > >    [RFC5986] protocol to determine the public address.  If
> > the client is
> > >    behind a residential gateway another option may be to
> > use Universal
> > >    Plug and Play (UPnP) [UPnP-IGD-WANIPConnection1] or the NAT Port
> > >    Mapping Protocol (NAT-PMP) [I-D.cheshire-nat-pmp].
> > >
> > >
> > > What text do you suggest to add to that?
> > >
> > > Thanks,
> > >
> > > Michael
> > >
> > >
> > > > -----Original Message-----
> > > > From: Songhaibin [mailto:haibin.song@huawei.com]
> > > > Sent: Thursday, June 21, 2012 5:02 AM
> > > > To: Scharf, Michael (Michael)
> > > > Cc: alto@ietf.org
> > > > Subject: RE: [alto] ALTO discovery in roaming scenario
> > > >
> > > > Please imagine a gateway/proxy based network access, the
> > ALTO client
> > > > is the end host, but actually the IP address for
> > gateway/proxy which
> > > > connect the end host to the network should be used for
> > ALTO server
> > > > discovery. The change of end-host IP and gateway/proxy IP is
> > > > independent somehow. I hope this clarification helps.
> > > >
> > > > BR,
> > > > -Haibin
> > > >
> > > > > -----Original Message-----
> > > > > From: Scharf, Michael (Michael)
> > > > > [mailto:michael.scharf@alcatel-lucent.com]
> > > > > Sent: Wednesday, June 20, 2012 8:07 PM
> > > > > To: Songhaibin
> > > > > Cc: alto@ietf.org
> > > > > Subject: RE: [alto] ALTO discovery in roaming scenario
> > > > >
> > > > > Haibin,
> > > > >
> > > > > The draft already states:
> > > > >
> > > > >    o  A change of the IP address at an interface
> > > > invalidates the result
> > > > >       of the ALTO server discovery procedure.  For
> > > > instance, if the IP
> > > > >       address assigned to a mobile host changes due to host
> > > > mobility, it
> > > > >       is required to run the ALTO server discovery
> > > > procedure for the new
> > > > >       IP address without relying on earlier gained information.
> > > > >
> > > > > Could you please explain what text is missing in the draft,
> > > > and what
> > > > > technical solution you suggest? For instance, if the mobile
> > > > > network uses "Proxy Mobile IP"?
> > > > >
> > > > > My understanding is that in reality roaming/normadic
> > use results
> > > > > in either of two
> > > > > possibilities:
> > > > >
> > > > > (1) There is a change of the IP address of the mobile host.
> > > > This case
> > > > > is already explained in the draft.
> > > > >
> > > > > (2) The IP address of the mobile host does not change.
> > > > Then, the host
> > > > > remains in the same IP subnet, and thus the ALTO discovery
> > > > result is still valid.
> > > > >
> > > > > In both cases, the current text in the discovery draft
> > > > seems to be just fine, right?
> > > > >
> > > > > Thanks
> > > > >
> > > > > Michael
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: alto-bounces@ietf.org
> > > > [mailto:alto-bounces@ietf.org] On Behalf
> > > > > > Of Songhaibin
> > > > > > Sent: Monday, June 18, 2012 1:22 PM
> > > > > > To: Songhaibin; Richard Alimi
> > > > > > Cc: alto@ietf.org
> > > > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > > > >
> > > > > > I would like to dig this from the tomb and see how the WG
> > > > would like
> > > > > > to solve the ALTO discovery in the roaming/nomadic
> > > > scenario. I would
> > > > > > also like to see it in the ALTO server discovery document.
> > > > > >
> > > > > > -Haibin
> > > > > >
> > > > > >
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org]
> > > > > > On Behalf
> > > > > > > Of Songhaibin
> > > > > > > Sent: Thursday, March 29, 2012 8:34 PM
> > > > > > > To: Richard Alimi
> > > > > > > Cc: alto@ietf.org
> > > > > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > > > > >
> > > > > > > Hi Rich,
> > > > > > >
> > > > > > > I think your proposal makes sense. The wikipedia document
> > > > > > > http://en.wikipedia.org/wiki/Mobile_IP provides some links
> > > > > > to relative
> > > > > > > RFCs. We may find details in these RFCs. I will also try to
> > > > > > read them.
> > > > > > >
> > > > > > > BR,
> > > > > > > -Haibin
> > > > > > >
> > > > > > > ________________________________________
> > > > > > > From: richard.alimi@gmail.com [richard.alimi@gmail.com] on
> > > > > > behalf of
> > > > > > > Richard Alimi [rich@velvetsea.net]
> > > > > > > Sent: Thursday, March 29, 2012 8:09 PM
> > > > > > > To: Songhaibin
> > > > > > > Cc: alto@ietf.org
> > > > > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > > > > >
> > > > > > > On Thu, Mar 29, 2012 at 12:26 AM, Songhaibin
> > > > > > <haibin.song@huawei.com>
> > > > > > > wrote:
> > > > > > > > Hi Rich,
> > > > > > > >
> > > > > > > > Thank you for the discussion. See inline.
> > > > > > > >
> > > > > > > > ________________________________________
> > > > > > > > From: richard.alimi@gmail.com [richard.alimi@gmail.com]
> > > > > > on behalf of
> > > > > > > > Richard
> > > > > > > Alimi [rich@velvetsea.net]
> > > > > > > > Sent: Wednesday, March 28, 2012 11:57 PM
> > > > > > > > To: Songhaibin
> > > > > > > > Cc: alto@ietf.org
> > > > > > > > Subject: Re: [alto] ALTO discovery in roaming scenario
> > > > > > > >
> > > > > > > > On Mon, Mar 19, 2012 at 4:28 AM, Songhaibin
> > > > > > <haibin.song@huawei.com>
> > > > > > > wrote:
> > > > > > > >> Hi,
> > > > > > > >>
> > > > > > > >> The indicated by the subject, which is perhaps not fully
> > > > > > solved in
> > > > > > > >> the discovery
> > > > > > > draft, I guess at least the following scenarios should be
> > > > > > considered.
> > > > > > > As I'm not an expert on roaming technology, please correct
> > > > > > me if you find I am wrong.
> > > > > > > >>
> > > > > > > >> (1) The ALTO client has left its home network, and its
> > > > > > IP address
> > > > > > > >> is dynamically
> > > > > > > assigned by the current network provider (through
> > DHCP or any
> > > > > > > other method), but the ALTO client still uses its
> > home agent
> > > > > > > to
> > > > > > access the
> > > > > > > Internet. In this case, the ALTO server resided in its home
> > > > > > > network should be the right ALTO server to be discovered.
> > > > > > > >>
> > > > > > > >> (2) The ALTO client has left its home network, and its
> > > > > > IP address
> > > > > > > >> is dynamically
> > > > > > > assigned by the current network provider, and the ALTO
> > > > > > client uses the
> > > > > > > foreign agent to access Internet or uses its IP address
> > > > directly
> > > > > > > to access Internet. In this scenario, the ALTO
> > server resided
> > > > > > in the current network should be the right one.
> > > > > > > And the existing discovery mechanism works in this scenario.
> > > > > > > >>
> > > > > > > >> (3) If the ALTO client has a persistent IP address when
> > > > > > > >> roaming, and it uses
> > > > > > > home agent to access Internet, but make large data route to
> > > > > > > the foreign agent directly (optimized routing mode). In this
> > > > > > scenario, the
> > > > > > > ALTO server resided in the current network should be the
> > > > > > right one to
> > > > > > > be discovered. However, if it does not adopt the
> > > > optimized routing
> > > > > > > mode, the ALTO server in the home network should be the
> > > > right one.
> > > > > > > >>
> > > > > > > >
> > > > > > > > I'm not familiar with the technologies backing this, but
> > > > > > what entity
> > > > > > > > decides the route that a particular packet will take? Is
> > > > > > > > this DPI living in the network where the client is
> > > > roaming?  Or is it
> > > > > > > > some entity on the client itself?
> > > > > > > >
> > > > > > > > [Haibin] No, it is not DPI based. Although I'm not an
> > > > > > expert on this
> > > > > > > > either, but I
> > > > > > > think in the mobile IPv6 scenario, the decision is made
> > > > > > > through the negotiation among the mobile node, home
> > agent, and
> > > > > > > other
> > > > > > correspondent nodes.
> > > > > > > >
> > > > > > >
> > > > > > > Thinking about this at the high level, If the mobile node
> > > > > > is involved
> > > > > > > in the negotiation, then it seems like it could
> > work like the
> > > > > > > following for this case:
> > > > > > > (1) Discover an ALTO Server using the home agent
> > (same as case
> > > > > > > 1
> > > > > > > above)
> > > > > > > (2) Discover an ALTO Server using the current network (same
> > > > > > as case 2
> > > > > > > above)
> > > > > > > (3) When it comes time to apply the ALTO information, apply
> > > > > > > the correct set depending on the routing for that
> > > > particular request.
> > > > > > >
> > > > > > > Is that compatible with whatever technologies are used for
> > > > > > these scenarios?
> > > > > > >
> > > > > > > Details on how this works and the negotiation actually
> > > > takes place
> > > > > > > would be useful.
> > > > > > >
> > > > > > > Rich
> > > > > > >
> > > > > > > > BR,
> > > > > > > > -Haibin
> > > > > > > >
> > > > > > > >> (4) (this one is not about roaming) Assume in a big
> > > > > > company which
> > > > > > > >> has a few
> > > > > > > branch offices in different locations, and VPN tunnels
> > > > are used to
> > > > > > > connect these branch offices, employees use one proxy to
> > > > > > > access Internet. Then the ALTO server discovery should be
> > > > > > > based on the proxy's IP address instead of the user's IP
> > > > > > > address.  It
> > > > > > also applies
> > > > > > > to other similar scenarios when end-hosts using proxies.
> > > > > > > >>
> > > > > > > >> It might not be a problem when doing third party
> > > > discovery, but
> > > > > > > >> have to
> > > > > > > consider when doing the discovery by the end-host itself.
> > > > > > > >>
> > > > > > > >> BR,
> > > > > > > >> -Haibin
> > > > > > > >> _______________________________________________
> > > > > > > >> 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
> > > > > > _______________________________________________
> > > > > > alto mailing list
> > > > > > alto@ietf.org
> > > > > > https://www.ietf.org/mailman/listinfo/alto
> > > > > >
> > > >
> >

From sebi@gw01.ehlo.wurstkaes.de  Sat Jun 30 11:49:46 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 3A76021F863D for <alto@ietfa.amsl.com>; Sat, 30 Jun 2012 11:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[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 ahRQHPceVxkj for <alto@ietfa.amsl.com>; Sat, 30 Jun 2012 11:49: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 5BF9B21F861A for <alto@ietf.org>; Sat, 30 Jun 2012 11:49:44 -0700 (PDT)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1Sl2jU-00026d-35; Sat, 30 Jun 2012 20:49:24 +0200
Date: Sat, 30 Jun 2012 20:49:24 +0200
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: Songhaibin <haibin.song@huawei.com>
Message-ID: <20120630184923.GS5342@gw01.ehlo.wurstkaes.de>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F23AC8D73@szxeml534-mbs.china.huawei.com>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: 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: Sat, 30 Jun 2012 18:49:46 -0000

Haibin, all,

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?

I like Michael's proposal ...

> > "In general, the ALTO server discovery should be based on the IP
> > address that is used to communicate with other peers".

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


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.

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




May I ask you and the other folks here three questions:


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

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


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

Personally, I would answer three times with "no" ...



Thanks
   Sebastian
