Re: [Bnbsg] BnB IoT Messaging
"Brzozowski, John" <John_Brzozowski@Cable.Comcast.com> Wed, 14 May 2014 14:39 UTC
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: bnbsg@ietfa.amsl.com
Delivered-To: bnbsg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F8C61A02AF for <bnbsg@ietfa.amsl.com>; Wed, 14 May 2014 07:39:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.485
X-Spam-Level:
X-Spam-Status: No, score=-3.485 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 lE-tl60HOwY7 for <bnbsg@ietfa.amsl.com>; Wed, 14 May 2014 07:39:16 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 03FE21A02B2 for <bnbsg@ietf.org>; Wed, 14 May 2014 07:39:15 -0700 (PDT)
Received: from ([24.40.56.114]) by copdcavout01.cable.comcast.com with ESMTP id C7WM3M1.132579216; Wed, 14 May 2014 08:38:51 -0600
Received: from PACDCEXMB01.cable.comcast.com ([169.254.1.249]) by PACDCEXHUB01.cable.comcast.com ([fe80::bdc4:5b5c:ee33:b058%16]) with mapi id 14.03.0181.006; Wed, 14 May 2014 10:38:51 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Drew Dvorshak <dvorshak@isoc.org>, Ray Pelletier <rpelletier@isoc.org>
Thread-Topic: [Bnbsg] BnB IoT Messaging
Thread-Index: AQHPbshGNRukdCz8D0qUElSM8zNAwZs+/HEAgAAipQCAAUQTAP//w7aA
Date: Wed, 14 May 2014 14:38:50 +0000
Message-ID: <CF98F826.172EF6%john_brzozowski@cable.comcast.com>
References: <A2419C90-B7AD-41D5-9B82-8132E9860AA2@amsl.com> <CF97C309.17156%dvorshak@isoc.org> <C773FC8D-591D-4C58-9A2B-BB3A47D94762@isoc.org> <CF98F281.17221%dvorshak@isoc.org>
In-Reply-To: <CF98F281.17221%dvorshak@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.1.140326
x-originating-ip: [68.87.16.246]
Content-Type: text/plain; charset="utf-8"
Content-ID: <44C2430388F18F429A148C70A6C6829B@cable.comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/bnbsg/L7z8iAzzJ63rQ6iAEcYu8s-wpLM
Cc: Alexa Morris <amorris@amsl.com>, "bnbsg@ietf.org" <bnbsg@ietf.org>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [Bnbsg] BnB IoT Messaging
X-BeenThere: bnbsg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <bnbsg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bnbsg>, <mailto:bnbsg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bnbsg/>
List-Post: <mailto:bnbsg@ietf.org>
List-Help: <mailto:bnbsg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bnbsg>, <mailto:bnbsg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 May 2014 14:39:18 -0000
Did we get all the desired feedback on Pascal’s text? ========================================= John Jason Brzozowski Comcast Cable m) 609-377-6594 o) 484-962-0060 w) www.comcast6.net e) john_brzozowski@cable.comcast.com ========================================= -----Original Message----- From: 'Drew Dvorshak' <Dvorshak@ISOC.org> Date: Wednesday, May 14, 2014 at 10:14 To: Ray Pelletier <rpelletier@isoc.org> Cc: Alexa Morris <amorris@amsl.com>, "bnbsg@ietf.org" <bnbsg@ietf.org>, Jari Arkko <jari.arkko@piuha.net> Subject: Re: [Bnbsg] BnB IoT Messaging >Ack > >On 5/13/14, 2:54 PM, "Ray Pelletier" <rpelletier@isoc.org> wrote: > >> >>On May 13, 2014, at 12:50 PM, Drew Dvorshak <dvorshak@isoc.org> 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 >>>fleshed >>> 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, >>as >>well as adding to the event’s success. >> >>This is an appropriate outreach and was done with guidance from those in >>the >>know about the topic. >> >>Let’s try it. >> >>Ray >> >>> >>> On 5/13/14, 12:27 PM, "Alexa Morris" <amorris@amsl.com> wrote: >>> >>>> Hi Everyone, >>>> >>>> Alex and Pascal generously responded to my request for a ³call for >>>>demos² >>>> writeup for the upcoming IoT-themed BnB event in Toronto. Their draft >>>>is >>>> 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 bnbsg@ietf.org. The info will also go on the >>>>website >>>> (as News and under IETF 90 area) and hopefully it will assist Drew in >>>>his >>>> 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 >>>>Things >>>> for >>>> future manufacturing and Machine-to-Machine communications. As of >>>>today, >>>> 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 >>>>economically >>>> possible with wires; the collection of these measurements by widely >>>> distributed >>>> sensing devices and their processing by Big Data analytics yield the >>>>next >>>> 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 >>> Bnbsg@ietf.org >>> https://www.ietf.org/mailman/listinfo/bnbsg >> > >_______________________________________________ >Bnbsg mailing list >Bnbsg@ietf.org >https://www.ietf.org/mailman/listinfo/bnbsg
- [Bnbsg] BnB IoT Messaging Alexa Morris
- Re: [Bnbsg] BnB IoT Messaging Drew Dvorshak
- Re: [Bnbsg] BnB IoT Messaging Ray Pelletier
- Re: [Bnbsg] BnB IoT Messaging Drew Dvorshak
- Re: [Bnbsg] BnB IoT Messaging Brzozowski, John
- Re: [Bnbsg] BnB IoT Messaging Brzozowski, John