Re: [Lwip] Ben Campbell's No Objection on draft-ietf-lwig-cellular-05: (with COMMENT)

"Ben Campbell" <ben@nostrum.com> Mon, 30 November 2015 16:23 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: lwip@ietfa.amsl.com
Delivered-To: lwip@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D9DC1ACE8C; Mon, 30 Nov 2015 08:23:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 TsGWv1QoSg4f; Mon, 30 Nov 2015 08:22:59 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 171F21ACEBA; Mon, 30 Nov 2015 08:22:53 -0800 (PST)
Received: from [10.0.1.10] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id tAUGMd8e040278 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 30 Nov 2015 10:22:39 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.10]
From: Ben Campbell <ben@nostrum.com>
To: Jari Arkko <jari.arkko@piuha.net>
Date: Mon, 30 Nov 2015 10:22:38 -0600
Message-ID: <8291D9A6-78A6-4AA4-B558-189622E70BC4@nostrum.com>
In-Reply-To: <F7AA1BAE-D714-450D-967F-CF76FB200AD8@piuha.net>
References: <20150916212734.27111.87164.idtracker@ietfa.amsl.com> <F7AA1BAE-D714-450D-967F-CF76FB200AD8@piuha.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.3r5187)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lwip/tOXmpgykLLlX8fSs-jNNDZgI6n8>
Cc: The IESG <iesg@ietf.org>, lwip@ietf.org
Subject: Re: [Lwip] Ben Campbell's No Objection on draft-ietf-lwig-cellular-05: (with COMMENT)
X-BeenThere: lwip@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Lightweight IP stack <lwip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lwip>, <mailto:lwip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lwip/>
List-Post: <mailto:lwip@ietf.org>
List-Help: <mailto:lwip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lwip>, <mailto:lwip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Nov 2015 16:23:01 -0000

On 30 Nov 2015, at 9:56, Jari Arkko wrote:

> Ben,
>
> Ari and I were preparing the final changes to the draft
> for the RFC editor today, and as a part of that I promised
> to reply to your comments, Ben. Thanks for the
> review!
>
>> -- 3, radio technology:
>> Can you elaborate on the meaning of "bundling applications together"?
>> Does it mean bundling the messages together for multiple 
>> applications?
>> Something else?
>
> Looking at this text, I think it could have been clearer:
>
>    Note that for situations where there are several applications on
>    the same device wishing to communicate with the Internet in some
>    manner, bundling those applications together at the same time can
>    be very useful.  Some guidance for these techniques in the
>    smartphone context can be found in [Android-Bundle].
>
> What we meant was timing synchronisation, so that for instance,
> if you have three apps that communicate every 10mins, they could
> all do that at the same time, rather than spaced random number of 
> minutes
> apart, leading to communications having to be up more often.
>
> Suggested edit:
>
>    Note that for situations where there are several applications on
>    the same device wishing to communicate with the Internet in some
>    manner, bundling those applications together so that they can
>    communicate at the same time can be very useful.  Some
>    guidance for these techniques in the smartphone context can
>    be found in [Android-Bundle].

That helps, thanks.

>
>
>> -- 7: "If sub-second response time is not
>> needed, a slightly more infrequent checking process may save some
>> power."
>> Perhaps more than slightly?
>
> Agree. I’d just delete the word “slightly”.

:-)

>
>> -- 7, paragraph 3:
>> Is the "device" in the 4th sentence the same as the "sensor”?
>
> Yes, the first sentence says “sensor-type devices”. But I’m ok 
> using
> either “sensor” or “device” consistently after that first 
> sentence. But
> I think “device” is consistent with the rest of the document.

On reflection, I'm okay with this as is.

Thanks!

Ben.