Hi Uwe,
It would be interesting indeed to see whether the editors of this draft have an interest in “Map Examples for Different Types of ISPs” with cellular/wireless networks. Best regards Sabine De : Rauschenbach, Uwe (NSN - DE/Munich) [mailto:[email protected]] Envoyé : vendredi 14 novembre 2014 01:06 À : RANDRIAMASY, SABINE (SABINE); Xiao SHI Cc : IETF ALTO Objet : 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:[email protected]] 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 : [email protected]<mailto:[email protected]> [mailto:[email protected]] 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) <[email protected]<mailto:[email protected]>> 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:[email protected]<mailto:[email protected]>] 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 [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/alto
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
