Re: [Bnbsg] BnB IoT Messaging

Drew Dvorshak <> Wed, 14 May 2014 14:14 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id CE5431A0103 for <>; Wed, 14 May 2014 07:14:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ECi3VT4TWmvW for <>; Wed, 14 May 2014 07:14:48 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 99AD01A00B8 for <>; Wed, 14 May 2014 07:14:47 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.939.12; Wed, 14 May 2014 14:14:37 +0000
Received: from ([]) by ([]) with mapi id 15.00.0944.000; Wed, 14 May 2014 14:14:37 +0000
From: Drew Dvorshak <>
To: Ray Pelletier <>
Thread-Topic: [Bnbsg] BnB IoT Messaging
Thread-Index: AQHPbshHfpwcECwsXU6/PMECXJ4YdZs+dlGAgABltwCAAQEAAA==
Date: Wed, 14 May 2014 14:14:36 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
x-forefront-prvs: 0211965D06
x-forefront-antispam-report: SFV:NSPM; SFS:(10019001)(6009001)(428001)(51704005)(479174003)(377454003)(189002)(199002)(51444003)(24454002)(164054003)(53754006)(92566001)(85852003)(101416001)(83072002)(81342001)(46102001)(54356999)(74502001)(92726001)(99286001)(86362001)(21056001)(50986999)(15975445006)(77982001)(4396001)(77096999)(2656002)(76176999)(31966008)(76482001)(64706001)(19580395003)(20776003)(81542001)(66066001)(83322001)(19580405001)(79102001)(87936001)(99396002)(74662001)(80022001)(36756003); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR06MB236;; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (: does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is );
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: Alexa Morris <>, "" <>, Jari Arkko <>
Subject: Re: [Bnbsg] BnB IoT Messaging
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 14 May 2014 14:14:51 -0000


On 5/13/14, 2:54 PM, "Ray Pelletier" <> wrote:

>On May 13, 2014, at 12:50 PM, Drew Dvorshak <> wrote:
>> Hi all,
>> Are we sure we want to send this out now instead in prep. For Hawaii?  I
>> say this because we already have multiple commitments signed that may or
>> may not follow the IoT theme.  We could not wait until we had that
>> out to begin filling tables.
>We had said we were going to experiment with Themes to see if it made a
>difference in identifying, attracting and closing on possible sponsors,
>well as adding to the event’s success.
>This is an appropriate outreach and was done with guidance from those in
>know about the topic.
>Let’s try it. 
>> On 5/13/14, 12:27 PM, "Alexa Morris" <> wrote:
>>> Hi Everyone,
>>> Alex and Pascal generously responded to my request for a ³call for
>>> writeup for the upcoming IoT-themed BnB event in Toronto. Their draft
>>> attached and embedded below, please review and comment.
>>> After any tweaking, I think that we should send this information out to
>>> the appropriate WG mailing lists and to the mail IETF list as well.
>>> Potential participants will be asked to send their questions about
>>> participating to  The info will also go on the website
>>> (as News and under IETF 90 area) and hopefully it will assist Drew in
>>> participant recruitment efforts.
>>> We are under a tight timeframe, so I¹d like to send out the call for
>>> participants before the end of the week (ideally Thursday).
>>> Thanks,
>>> Alexa
>>> ‹‹
>>> 		  Bits-N-Bites - Internet of Things
>>> 		  ---------------------------------
>>> 			    Call for Demos
>>> The arrival of Things connected to the Internet in the recent years
>>> brought to life new applications.  In the consumer segment, numerous
>>> small and smart devices add new dimensions to existing domains such
>>> automatic home management, in-vehicle entertainment, eHealth, fitness
>>> and more.  A growing enthusiasm in novel market suggests
>>> imminent and impressive deployments: billions new connected devices
>>> expected by year 2020.
>>> In professional segments, examples abound of the use of connected
>>> for 
>>> future manufacturing and Machine-to-Machine communications. As of
>>> factory networks primarily rely on wired communication networks to
>>> support 
>>> Industrial Automation and Control Systems.  On the other hand, Wireless
>>> Sensor Networks have the power to extend the reach of Monitoring and
>>> Control 
>>> to gather unused measurements beyond what is physically and
>>> possible with wires; the collection of these measurements by widely
>>> distributed 
>>> sensing devices and their processing by Big Data analytics yield the
>>> degree of process optimization, a vision known as the Industrial
>>> Internet. This 
>>> will require the combination of the best of IT and OT technologies
>>> together, 
>>> forming the IT/OT convergence.
>>> Despite the word 'connected' being commonly employed in this context,
>>> the current Thing topologies do not use IP as known in the non-Things
>>> world.  Instead, intermediary albeit small Boxes translating between
>>> IP and Thing-specific protocols are in common use (for
>>> e.g. application-layer conversions, IP to non-IP address translation,
>>> IP header compression, 'mesh-under' non-IP routing and more).  This
>>> leads to typical 'multi-stage' topology such as: a temperature sensor
>>> connected to a smartwatch using a hardware communication protocol,
>>> further connected to a smartphone using a short-range non-IP protocol
>>> and finally connected to a WiFi router using a full IP link.
>>> On another hand, past experience in the development of the Internet
>>> suggests that if intermediary Boxes are less present in the path -
>>> dumb networks (thus reducing the 'multi-stage' Thing topology to a
>>> minimum of 2 stages and down to 1, ideally), the full potential of
>>> end-to-end principles may be uncovered: each Thing may be directly
>>> queried, their number may grow in a more scalable way and richer
>>> applications may offer features beyond what's talked about these days.
>>> When deploying multi-stage Thing topologies, two trends compete: IP
>>> protocols are enhanced and transformed into less end-to-end protocols
>>> (address translation, header compression, 'mesh under' routing and
>>> more) and, alternatively, existing IP protocols are reduced to their
>>> bare minimum such as to fit in reduced Things (reduced CPU frequency
>>> and number of transistors, dimensions and energy consumption).
>>> Demonstrations of these IoT concepts are called for.  The
>>> demonstrations should exhibit recent developments of IP protocols for
>>> IoT networks (6lowpan adaptation layers, MANET and RPL routing
>>> protocols, 6tsch time-constrained communications, CoAP app-layer
>>> protocols) as well as demonstrations of the tendency of bringing the
>>> known IPv6 as close as possible to the Thing - minimum set of
>>> unmodified IPv6, Neighbor Discovery, DHCP, HTTP, IKEv2.
>>> Examples of demos include and are certainly not limited to:
>>> - home automation controller using SNMP for HVAC and ambient
>>> temperature, electricity counter.
>>> - industrial-grade Wireless Sensor Network products
>>> - scalable wireless designs and existing deployments
>>> - IPv6 end-to-end and backbone interconnection
>>> - tablet summarizing status of widespread devices through
>>> heterogeneous link connections.
>>> - smart belt collecting body information with low-energy communication
>>> protocols.
>>> - vehicle interior connected designs, vehicle-to-road sensor-based
>>> communications.
>>> - sensor-assisted autonomous mobile Things (mono-, bi-, quad- wheeled
>>> or propelled devices).
>>> Demonstrations may be realized in different manners:
>>> - the Things deployed on a table, relying on local connections and
>>> alternatively exhibiting remote access across the  Internet.
>>> - poster describing demo.
>>> - video sequence showing a lab demonstration.
>>> Each demonstration must position with respect to questions such as
>>> - use of IP protocols: IPv4 or IPv6?
>>> - intermediary Box or not?
>>> - on the market now, in the prototype stage, in an idea phase?
>>> - part of a collaborative project?  gov't-funded or private?
>> _______________________________________________
>> Bnbsg mailing list