Synchronization of hosts' periodical communications

Teemu Savolainen <tsavo.stds@gmail.com> Mon, 18 June 2012 11:39 UTC

Return-Path: <tsavo.stds@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDCB321F85A2 for <ipv6@ietfa.amsl.com>; Mon, 18 Jun 2012 04:39:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 wZENiKN1Ed7W for <ipv6@ietfa.amsl.com>; Mon, 18 Jun 2012 04:39:09 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0265921F85A1 for <6man@ietf.org>; Mon, 18 Jun 2012 04:39:08 -0700 (PDT)
Received: by dacx6 with SMTP id x6so6876603dac.31 for <6man@ietf.org>; Mon, 18 Jun 2012 04:39:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=lEmfSMyuwb50clwzSfy5BBvt0KVDGWn0soEbDXV3QYs=; b=hvhKQHYRirVqkSzt9QSgnapC7fpseCRP6TZp27UhYg3uabT4d78Y/w5jClsoRpj1Cr /IAIJshLkZaUcpzkd70a/mnvQkd4XPOGx25TheTyQjiiXt49v8zSkd1LkgVe6QAsboe7 MNXLDXOTMr1WUQIwVSlgnols75DB8MqKYfH9vE95Aj9QWxV+6gB2UZrdJcALdVSghJu+ mPfHQ2IezdV9W4v/grPhFHDxC5n12lWar7MV5PiAWIv3TRbfZToEjbacP4OcZLW+AJ/O A5J0t5SpiSKew3n7jcFnLfkwcBH/ntCF4xUBSWZKljdApvyWO2co06fKbwJKnKIe8TrM NjTg==
MIME-Version: 1.0
Received: by 10.68.221.74 with SMTP id qc10mr8650583pbc.31.1340019548747; Mon, 18 Jun 2012 04:39:08 -0700 (PDT)
Received: by 10.68.54.138 with HTTP; Mon, 18 Jun 2012 04:39:08 -0700 (PDT)
Date: Mon, 18 Jun 2012 14:39:08 +0300
Message-ID: <CABmgDzRN8hsduhHw-79n70TyeF-4kQbFLSw0VMXFpC5WSK+AiQ@mail.gmail.com>
Subject: Synchronization of hosts' periodical communications
From: Teemu Savolainen <tsavo.stds@gmail.com>
To: 6man@ietf.org
Content-Type: multipart/alternative; boundary="e89a8ff2432b31f7bb04c2bd9d59"
X-Mailman-Approved-At: Mon, 18 Jun 2012 07:16:56 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2012 11:39:09 -0000

Greetings 6man WG,

We have just published a draft about:"Optimal Transmission Window
Configuration Option for ICMPv6 Router Advertisement"

http://tools.ietf.org/internet-drafts/draft-savolainen-6man-optimal-transmission-window-00.txt

Abstract:
---
   This specification describes an ICMPv6 Router Advertisement option
   for a router to configure optimal transmission window for hosts
   transmitting packets through the router.
---

The RA already contains information host needs to address itself ("what")
and for selecting default and more specific routers ("where"). The intent
of this draft is to describe "when" would be the most appropriate time for
hosts to transmit, if they can choose (i.e. this is not to be used to slow
down active user experience or necessarily affect to real-time apps).

The intent is to synchronize periodical "idle-mode" communications of
several hosts behind a resource constrained gateway/router. For example, if
a low-power sensor network is provided Internet connectivity through a
battery powered gateway (e.g. a handset), it is beneficial to minimize
number of times the gateway's radio needs to be activated. For example, if
there were two nodes behind such a gateway sending messages out every two
minutes, the number of gateway's radio activation times can be halved by
ensuring the two nodes send periodical message about (but not exactly) at
the same time. In this case, as the second radio activation can be avoided,
the gateway's uplink radio power consumption can be about halved.

We would like to present this draft and some measurements in the Vancouver
IETF meeting.

However, we would also like to hear some comments from 6man WG prior the
IETF - especially if there is interest/objection for this piece of work.

Best regards,

Teemu