Re: [Bnbsg] Participate in IETF 90 Bits-N-Bites: Internet of Things (IoT)

Alexandru Petrescu <> Tue, 20 May 2014 09:31 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 6D74B1A05CB for <>; Tue, 20 May 2014 02:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.283
X-Spam-Status: No, score=-1.283 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, MANGLED_WRLDWD=2.3, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id LH0LZQICJvBB for <>; Tue, 20 May 2014 02:31:37 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D0A581A059F for <>; Tue, 20 May 2014 02:31:36 -0700 (PDT)
Received: from ( []) by (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s4K9VIOV022221; Tue, 20 May 2014 11:31:18 +0200
Received: from (localhost []) by localhost (Postfix) with SMTP id 30CC12024F9; Tue, 20 May 2014 11:32:21 +0200 (CEST)
Received: from ( []) by (Postfix) with ESMTP id 233C22024F1; Tue, 20 May 2014 11:32:21 +0200 (CEST)
Received: from [] ( []) by (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s4K9V8Km032635; Tue, 20 May 2014 11:31:17 +0200
Message-ID: <>
Date: Tue, 20 May 2014 11:31:08 +0200
From: Alexandru Petrescu <>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: Alexa Morris <>
References: <>
In-Reply-To: <>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [Bnbsg] Participate in IETF 90 Bits-N-Bites: Internet of Things (IoT)
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 20 May 2014 09:31:39 -0000

Hi Alexa,

Makes sense to me.  Please see below some comments.

Le 20/05/2014 07:03, Alexa Morris a écrit :
> Hi Everyone,
> Finally getting this out to all of you. I would like to send an
> email to the relevant working group lists tomorrow (Tuesday). The
> below is essentially the language we have on the website, which was
> taken from the text prepared by Alex and Pascal. Please send me any
> comments at your earliest convenience.


> Question: I’m not sure what the sentence at the end means when it
> says, “Things deployed on a table, relying on local connections and
> alternatively exhibiting remote access across the Internet”  — does
> that mean that it will use the local IETF network but also
> potentially access devices or things that are external to the IETF
> network?

Yes, that could be the case.  A demo on-table in Toronto may access
sensor devices across the Internet located in other country.

> If so, could we rephrase it to say, "Things deployed on a table,
> connecting via the local IETF network in Toronto and/or
> demonstrating remote access across the Internet.”

Yes, that reads better.

> Or is the sentence clear enough as is and perhaps it’s just my own
> lack of understanding that is the issue :-)
> Also, is this the complete list of WG lists that we should send the
> email to:
> - 6lo WG - 6tisch WG - RoLL WG - lwig WG - ACE BoF - Core WG

In the illustration at
I noticed a position marker up in the picture.  I think that is very 

Maybe the call for demos could be enhanced with a geographical 
networking aspect.  Maybe just a few words here and there.

I would suggest adding (the GeoNet BoF) since it focuses on 
geonet and has a side use-case for vehicular communications.  And also (the GeoPriv WG).

This covers people with geo-location experience who may be interested in 
demoing IoT geo-localization aspects.  Because typically geo-enabled 
devices are small and thus Things (e.g. GPS receiver), important in 
vehicular communications (geonet/its topic: dead-reckoning enhancements 
for enhanced GPS localization, geo-dissemination), service applications 
on smartphones (geopriv WG topics: google "geofeeds", 
IP-to-LatLong-to-CivicAddress resolution mechanisms).


> +++++++
> Bits-N-Bites at IETF 90 in Toronto will focus on the Internet of
> Things, and the IETF invites you and your organization to
> participate!
> The arrival of Things connected to the Internet in recent years has
> given life to new applications in both the consumer and industrial
> market segments. We are surrounded by products that utilize
> connectivity and a growing enthusiasm suggests imminent and
> impressive deployments: billions of new connected devices are
> expected by year 2020.  In the industrial world, wide spread
> wireless sensoring devices that collect data and measurements will
> move us into the next phase of process optimization. This will
> require the combination of the best of Information Technology (IT)
> and Operational Technology (OT), forming the IT/OT convergence.
> 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).
> IETF 90 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.
> Does your organization want to reach 1,200 Internet engineers and
> demonstrate your IoT technologies and usage of IETF protocols? This
> is your opportunity to show leading industry professionals the
> latest and greatest of what you do in a social and interactive
> setting.
> Examples of demos include, but are 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).
> There many ways to configure your demo, such as:
> • Things deployed on a table, relying on local connections and
> alternatively exhibiting remote access across the Internet; • a
> poster describing a demo; • video sequence showing a lab
> demonstration.
> For information about IETF 90 Bits-N-Bites, please see
> or send email to
> Regards, Alexa
> ---------- Alexa Morris / Executive Director / IETF 48377 Fremont
> Blvd., Suite 117, Fremont, CA  94538 Phone: +1.510.492.4089 / Fax:
> +1.510.492.4001 Email:
> Managed by Association Management Solutions (AMS) Forum Management,
> Meeting and Event Planning <>
> _______________________________________________ Bnbsg mailing list