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

Xiao SHI <xiao.shi@yale.edu> Wed, 12 November 2014 06:38 UTC

Return-Path: <boxs.jq@gmail.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 0BDFE1A9251 for <alto@ietfa.amsl.com>; Tue, 11 Nov 2014 22:38:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level:
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 h3g7obOBqiHS for <alto@ietfa.amsl.com>; Tue, 11 Nov 2014 22:38:21 -0800 (PST)
Received: from mail-yh0-x234.google.com (mail-yh0-x234.google.com [IPv6:2607:f8b0:4002:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C7021A90F4 for <alto@ietf.org>; Tue, 11 Nov 2014 22:38:21 -0800 (PST)
Received: by mail-yh0-f52.google.com with SMTP id f73so780260yha.25 for <alto@ietf.org>; Tue, 11 Nov 2014 22:38:20 -0800 (PST)
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:message-id :subject:to:cc:content-type; bh=PJPlrxTfuLsKN21UmrNxB0C1AYNnxsu8JMQqHZ2CVuA=; b=lcudn40iVHEPsh2kePtM+ARTuzKqqDIQEWhlAITG1uBzxcahq4LfFCjTa5HWS7M9tL gv27TsUV/rUaVARr//TSzIHZomprKDHui5JW+U0HUr7TJwni/P3tW2DDuAkq87f1eYeg cR3SRcF/BMH2Ucy+9O+GkXHkxynx76Zc1jY5n/KUJNEpzHpNIETcNQtcT9I7RmB0GXnk 0FytAVF1D1n3xfD0owVMGhEcpPKlVvF+fU054slwTvsKmK+9qcqdq3Gk7bTTQZHnRSwM HPEAAPwI+QCEYp4OVp/9iX2mQ+u2/Ftt7qMM3zvB+bMG5wAVChQ5XLyQE9a7DPviQYU0 NwsQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=googleprd; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=PJPlrxTfuLsKN21UmrNxB0C1AYNnxsu8JMQqHZ2CVuA=; b=pbR4ZOQStNbQEjRMnwiEf48YQxT/8+GOGqwfXsgi78PUU7MClnjl/bgYjAG4vvbeeK 4c+OSZQaQoYXq0T18EkyBTWahckQi88+xu9bZ6AmRHFaJn4Y+XwmKZY8pBk+eFysVAkC k4gHXq2PJcBzCuqfqVF+51vXjWVDcj5HCT5lc=
X-Received: by 10.236.202.232 with SMTP id d68mr681955yho.113.1415774300255; Tue, 11 Nov 2014 22:38:20 -0800 (PST)
MIME-Version: 1.0
Sender: boxs.jq@gmail.com
Received: by 10.170.221.193 with HTTP; Tue, 11 Nov 2014 22:37:59 -0800 (PST)
In-Reply-To: <56C2F665D49E0341B9DF5938005ACDF81951CA69@DEMUMBX005.nsn-intra.net>
References: <A7A5844EB93EB94AB22C2068B10AD65A6ADEBFF9@FR712WXCHMBA12.zeu.alcatel-lucent.com> <56C2F665D49E0341B9DF5938005ACDF81951CA69@DEMUMBX005.nsn-intra.net>
From: Xiao SHI <xiao.shi@yale.edu>
Date: Wed, 12 Nov 2014 01:37:59 -0500
X-Google-Sender-Auth: Rj8o_jQK89oRqrPKKQi_Gl_u1lo
Message-ID: <CAFwJzZkQ+2jTD7=1D-t7qwrmVnfPR7N_aQP8f35=+d4N66qnYw@mail.gmail.com>
To: "Rauschenbach, Uwe (NSN - DE/Munich)" <uwe.rauschenbach@nsn.com>
Content-Type: multipart/alternative; boundary="089e0158b6003fbe980507a3a465"
Archived-At: http://mailarchive.ietf.org/arch/msg/alto/jCaYTF-xewy41kdLVr021LUwbWI
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: Wed, 12 Nov 2014 06:38:23 -0000

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> 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]
> *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
> https://www.ietf.org/mailman/listinfo/alto
>
>