Re: [alto] ALTO Cost calendars in wireless access networks

"Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com> Fri, 14 November 2014 15:37 UTC

Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBADB1A00E7 for <alto@ietfa.amsl.com>; Fri, 14 Nov 2014 07:37:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.493
X-Spam-Level:
X-Spam-Status: No, score=-7.493 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E_za-aOF7mik for <alto@ietfa.amsl.com>; Fri, 14 Nov 2014 07:36:59 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0D4C1A00E1 for <alto@ietf.org>; Fri, 14 Nov 2014 07:36:58 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id 6C9A56EB84312; Fri, 14 Nov 2014 15:36:54 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id sAEFalQD029522 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 14 Nov 2014 16:36:56 +0100
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.81]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Fri, 14 Nov 2014 16:36:42 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "Rauschenbach, Uwe (NSN - DE/Munich)" <uwe.rauschenbach@nsn.com>, "RANDRIAMASY, SABINE (SABINE)" <sabine.randriamasy@alcatel-lucent.com>, Xiao SHI <xiao.shi@yale.edu>
Thread-Topic: [alto] ALTO Cost calendars in wireless access networks
Thread-Index: Ac/93kl5HUYbpH9cQXahMNNsozCXTQASC3GgAAUWg4AAFMpFAABEDNIgACBs7MA=
Date: Fri, 14 Nov 2014 15:36:41 +0000
Message-ID: <655C07320163294895BBADA28372AF5D1669EC85@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <A7A5844EB93EB94AB22C2068B10AD65A6ADEBFF9@FR712WXCHMBA12.zeu.alcatel-lucent.com> <56C2F665D49E0341B9DF5938005ACDF81951CA69@DEMUMBX005.nsn-intra.net> <CAFwJzZkQ+2jTD7=1D-t7qwrmVnfPR7N_aQP8f35=+d4N66qnYw@mail.gmail.com> <A7A5844EB93EB94AB22C2068B10AD65A6ADEC65E@FR712WXCHMBA12.zeu.alcatel-lucent.com> <56C2F665D49E0341B9DF5938005ACDF81951EE62@DEMUMBX005.nsn-intra.net>
In-Reply-To: <56C2F665D49E0341B9DF5938005ACDF81951EE62@DEMUMBX005.nsn-intra.net>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: multipart/alternative; boundary="_000_655C07320163294895BBADA28372AF5D1669EC85FR712WXCHMBA15z_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/alto/S8Xaf3DaXDl6y5U3HeYVdh6v7ZQ
Cc: IETF ALTO <alto@ietf.org>
Subject: Re: [alto] ALTO Cost calendars in wireless access networks
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.15
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, 14 Nov 2014 15:37:05 -0000

Hi Uwe, all,

Personally, I am not sure whether a single RAN cell is indeed the right granularity for PIDs.

But draft-ietf-alto-deployments is a WG document and in general the editors have been open to suggestions for further realistic deployment cases of ALTO. draft-ietf-alto-deployments has some text already on mobile access networks, albeit at a much larger granularity of PIDs.

As usual in the IETF: Propose specific text ;)

Best regards

Michael



From: alto [mailto:alto-bounces@ietf.org] On Behalf Of Rauschenbach, Uwe (NSN - DE/Munich)
Sent: Friday, November 14, 2014 1:06 AM
To: RANDRIAMASY, SABINE (SABINE); Xiao SHI
Cc: IETF ALTO
Subject: Re: [alto] ALTO Cost calendars in wireless access networks

Hi Sabine,

Is http://tools.ietf.org/html/draft-ietf-alto-deployments-10 the appropriate place to add these?

Kind regards,
Uwe

From: ext RANDRIAMASY, SABINE (SABINE) [mailto:sabine.randriamasy@alcatel-lucent.com]
Sent: Wednesday, November 12, 2014 5:40 AM
To: Xiao SHI; Rauschenbach, Uwe (NSN - DE/Munich)
Cc: IETF ALTO
Subject: RE: [alto] ALTO Cost calendars in wireless access networks

Hi Xiao and Uwe,

The cellular or other access use case also calls I think for looking at related ALTO Service deployment cases.
Best,
Sabine


De : boxs.jq@gmail.com<mailto:boxs.jq@gmail.com> [mailto:boxs.jq@gmail.com] De la part de Xiao SHI
Envoyé : mercredi 12 novembre 2014 07:38
À : Rauschenbach, Uwe (NSN - DE/Munich)
Cc : RANDRIAMASY, SABINE (SABINE); IETF ALTO
Objet : Re: [alto] ALTO Cost calendars in wireless access networks

Hi Uwe,

Your document sounds like a very reasonable and useful extension. Just have two related thoughts:

1. Have you considered your cells extension using PID properties? The relevant draft is here: http://tools.ietf.org/html/draft-roome-alto-pid-properties-02#section-4.2 I believe the PID property document provides a solution to both requirements in your document (via Solution B).

2. Since the nodes change cells frequently, do you think this extension would benefit from incremental updates? The incr update document (http://datatracker.ietf.org/doc/draft-roome-alto-incr-update-sse/) provides the SSE framework, but I am not sure how convenient SSE is to mobile networks.

Best,
Xiao

On Tue, Nov 11, 2014 at 10:23 PM, Rauschenbach, Uwe (NSN - DE/Munich) <uwe.rauschenbach@nsn.com<mailto:uwe.rauschenbach@nsn.com>> wrote:
Hi Sabine,

Thanks for the pointer. Yes, I think your proposal will meet the expectations of the sketched use cases.
In fact, our proposal is orthogonal and tries to address the problem that in mobile networks, the network attachment
point can be one additional important parameter that should be addressed in ALTO.

So far, ALTO helps to decide “where to connect to” (where: the endpoint that provides the service).
The cost calendar enhances this to become “when and where to connect to”.
In mobile, the whole picture would become “via which cell/access, when and where to connect to”.

Kind regards,
Uwe


From: ext RANDRIAMASY, SABINE (SABINE) [mailto:sabine.randriamasy@alcatel-lucent.com<mailto:sabine.randriamasy@alcatel-lucent.com>]
Sent: Tuesday, November 11, 2014 8:36 AM
To: Rauschenbach, Uwe (NSN - DE/Munich)
Cc: IETF ALTO
Subject: ALTO Cost calendars in wireless access networks

Hi Uwe,

I see that your draft http://tools.ietf.org/id/draft-rauschenbach-alto-wireless-access-00.txt will be presented in the next ALTO WG session.

Given that your draft poses the need for a calendar in its following sections 3.2.1.  Cost calendar to extend battery life for background tasks and section 3.2.2.  Cost calendar to optimize application sessions, you may want to look at http://tools.ietf.org/id/draft-randriamasy-alto-cost-calendar-02.txt, that proposes ALTO cost calendars and will be presented during the ALTO WG session as well, as it would be interesting to see how this proposal may meet your expectations.

Best regards,
Sabine


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