Re: [tcmtf] BoF proposal for Berlin. Possible scheme

gorry@erg.abdn.ac.uk Wed, 15 May 2013 09:10 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tcmtf@ietfa.amsl.com
Delivered-To: tcmtf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A4B821F874A for <tcmtf@ietfa.amsl.com>; Wed, 15 May 2013 02:10:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hLqPxFa1SJI2 for <tcmtf@ietfa.amsl.com>; Wed, 15 May 2013 02:09:58 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 9DF9721F8CEC for <tcmtf@ietf.org>; Wed, 15 May 2013 02:09:58 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 9E5DB2B42D4; Wed, 15 May 2013 10:09:57 +0100 (BST)
Received: from 139.133.204.42 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Wed, 15 May 2013 10:09:57 +0100
Message-ID: <4df6cd099df67aa699d7956a56e89ad0.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <005101ce514a$3e41ea20$bac5be60$@unizar.es>
References: <008201ce4fc4$22b8e510$682aaf30$@unizar.es> <E004A7C54DE04F4BB87DB9F32308DA5C01CFFE@MAIL4.fer.hr> <005101ce514a$3e41ea20$bac5be60$@unizar.es>
Date: Wed, 15 May 2013 10:09:57 +0100
From: gorry@erg.abdn.ac.uk
To: jsaldana@unizar.es
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: tcmtf@ietf.org, =?iso-8859-1?Q?=22'Mirko_Su=BEnjevi=E6'=22?= <mirko.suznjevic@fer.hr>
Subject: Re: [tcmtf] BoF proposal for Berlin. Possible scheme
X-BeenThere: tcmtf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Tunneling Compressed Multiplexed Traffic Flows \(TCMTF\) discussion list" <tcmtf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcmtf>
List-Post: <mailto:tcmtf@ietf.org>
List-Help: <mailto:tcmtf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcmtf>, <mailto:tcmtf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 09:10:03 -0000

My guess is that many people at the IETF would "like" to see people say
they plan to implement for a product, or that they plan to devote
significant effort to seeing the standard matches their need for a
particular use case (e.g. operators or equipment vendors). This can be a
strong indication that there is a need for a standard.  This can be in a
slide, or at the Mic or on the list, slides, etc...

If it's just researchers wanting toi agree a spec that may also be OK, but
then it could be an IRTF activity that comes up with an experimental spec
for people to evaluate.

Gorry

> Hi, Mirko.
>
>
>
> The idea of energy savings is also interesting. People are getting more
> and
> more concerned with the energy consumption. Not only European Commission,
> but also smartphone and tablet manufacturers: the duration of the battery
> is
> critical there.
>
>
>
> For example, "Qualcomm has developed a solution called Network Socket
> Request Manager (NSRM) for efficient application management. NSRM reduces
> smart phone signaling traffic by bundling application requests and
> intelligently delaying them. NSRM provides significant signaling reduction
> and also improves stand-by time."
>
>
> <http://www.qualcomm.com/media/documents/qualcomm-research-managing-backgrou
> nd-data-traffic-mobile-devices>
> http://www.qualcomm.com/media/documents/qualcomm-research-managing-backgroun
> d-data-traffic-mobile-devices
>
>
>
> Perhaps we could also include this idea in the presentations. The benefits
> of packet grouping are 3 instead of 2:
>
>
>
> 1- Bandwidth saving
>
> 2- PPS reduction
>
> 3- Energy savings
>
>
>
> What do you think? Will people at the IETF like energy savings?
>
>
>
> Best regards,
>
>
>
> Jose
>
>
>
> De: tcmtf-bounces@ietf.org [mailto:tcmtf-bounces@ietf.org] En nombre de
> Mirko Su¾njevic
> Enviado el: martes, 14 de mayo de 2013 10:08
> Para: tcmtf@ietf.org
> Asunto: Re: [tcmtf] BoF proposal for Berlin. Possible scheme
>
>
>
> Hello everybody,
>
> Well I concur with the structure. I believe that the main thing is to do
> is
> to well formulate and explain the problem. We must prove in a coherent way
> that the problem we are addressing here is a problem worth putting effort
> to
> and worth solving. In short we must present all the benefits the  solving
> of
> our problem might bring. We more or less covered the network aspects of
> the
> TCMTF. Maybe one of the previously not emphasized things is the notion of
> energy savings which TCMTF implementation might bring.  I am not certain
> would such topics be interesting in the IETF, but it was interesting for
> the
> European Commission.
>
> Ofcourse I will create the presentation regarding my part.
>
>
> Cheers!
>
> Mirko Suznjevic
>
>
>
>
>
> From: Jose Saldana [mailto:jsaldana@unizar.es]
> Sent: Monday, May 13, 2013 12:25 PM
> To: tcmtf@ietf.org
> Cc: Martin Stiemerling; Dan Wing; Mirko Su¾njeviæ
> Subject: BoF proposal for Berlin. Possible scheme
>
>
>
> Hi all.
>
>
>
> According to http://www.ietf.org/meeting/cutoff-dates-2013.html#IETF87,
> 2013-06-17 (Monday) is the cutoff date for BOF proposal requests to Area
> Directors. So we still have a month.
>
>
>
> we could discuss a bit the possible scheme for the BoF proposal.
>
>
>
> According to Martin's suggestion, we could begin the session with a teaser
> presentation describing what the exact issues are and what is the need for
> standardization.
>
>
>
> So we could follow this structure:
>
>
>
> 1- Teaser presentation: describing the problem and the need for
> standardization
>
>
>
> 2- Charter: Documents to be generated within this potential WG
>
>
>
> 3- Draft A: Explaining the current TCMTF proposal
>
>
>
> 4- Draft B: Explaining the content of the draft about delay requirements,
> classification methods, etc.
>
>
>
>
>
> Dan Wing could be in charge of (1). This would be good, since he is one of
> the authors of RFC4170 (the RFC we should "update" with TCMTF), so he
> knows
> the whole story. In addition, he has been in the TCMTF draft from the very
> beginning.
>
>
>
> I could be in charge of (2), mainly explaining the charter.
>
>
>
> Perhaps someone from Telefonica could be in charge of (3).
>
>
>
> Mirko Suznjevic could present (4), since he is the first author.
>
>
>
>
>
>
>
> What do you think? Any ideas?
>
>
>
> Thanks a lot and best regards!,
>
>
>
> Jose
>
>
>
> _______________________________________________
> tcmtf mailing list
> tcmtf@ietf.org
> https://www.ietf.org/mailman/listinfo/tcmtf
>