Re: [cin] Bar BoF at IETF 84

Terry Davis <terry.davis@ijetonboard.com> Mon, 09 July 2012 18:43 UTC

Return-Path: <terry.davis@ijetonboard.com>
X-Original-To: cin@ietfa.amsl.com
Delivered-To: cin@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1508B11E80B7 for <cin@ietfa.amsl.com>; Mon, 9 Jul 2012 11:43:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 W+7JYMBVpq3N for <cin@ietfa.amsl.com>; Mon, 9 Jul 2012 11:43:16 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) by ietfa.amsl.com (Postfix) with ESMTP id 95F6F21F84AE for <cin@ietf.org>; Mon, 9 Jul 2012 11:43:15 -0700 (PDT)
Received: from mail40-va3-R.bigfish.com (10.7.14.252) by VA3EHSOBE010.bigfish.com (10.7.40.12) with Microsoft SMTP Server id 14.1.225.22; Mon, 9 Jul 2012 18:41:23 +0000
Received: from mail40-va3 (localhost [127.0.0.1]) by mail40-va3-R.bigfish.com (Postfix) with ESMTP id 8D1452C02B1; Mon, 9 Jul 2012 18:41:23 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.241.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0810HT003.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -30
X-BigFish: VPS-30(zzbb2dI98dI9371I1102I542M1432Izz1202hzz1033IL8275dhz2fh2a8h668h839h944hd25hf0ah107ah)
Received-SPF: pass (mail40-va3: domain of ijetonboard.com designates 157.56.241.101 as permitted sender) client-ip=157.56.241.101; envelope-from=terry.davis@ijetonboard.com; helo=BL2PRD0810HT003.namprd08.prod.outlook.com ; .outlook.com ;
Received: from mail40-va3 (localhost.localdomain [127.0.0.1]) by mail40-va3 (MessageSwitch) id 1341859282186351_26760; Mon, 9 Jul 2012 18:41:22 +0000 (UTC)
Received: from VA3EHSMHS042.bigfish.com (unknown [10.7.14.242]) by mail40-va3.bigfish.com (Postfix) with ESMTP id 2A4AE40076; Mon, 9 Jul 2012 18:41:22 +0000 (UTC)
Received: from BL2PRD0810HT003.namprd08.prod.outlook.com (157.56.241.101) by VA3EHSMHS042.bigfish.com (10.7.99.52) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 9 Jul 2012 18:41:21 +0000
Received: from BL2PRD0810MB349.namprd08.prod.outlook.com ([169.254.2.108]) by BL2PRD0810HT003.namprd08.prod.outlook.com ([10.255.110.38]) with mapi id 14.16.0164.004; Mon, 9 Jul 2012 18:43:38 +0000
From: Terry Davis <terry.davis@ijetonboard.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, Wesley Eddy <wes@mti-systems.com>
Thread-Topic: [cin] Bar BoF at IETF 84
Thread-Index: Ac1bfVAJdF9Q/5LORiqK2S6YRIA4AAAIYroAADGlzgAAE7X5gABSKTcQAAEN0KAAABycAA==
Date: Mon, 9 Jul 2012 18:43:38 +0000
Message-ID: <C8092F050778464AB435B2AB453E73FF41E8F9B0@BL2PRD0810MB349.namprd08.prod.outlook.com>
References: <13205C286662DE4387D9AF3AC30EF456D76FAE16AE@EMBX01-WF.jnpr.net><4FF723C2.7080506@gmail.com><C8092F050778464AB435B2AB453E73FF41E8C757@CH1PRD0810MB360.namprd08.prod.outlook.com><4FF8F537.4000502@mti-systems.com> <C8092F050778464AB435B2AB453E73FF41E8F8FC@BL2PRD0810MB349.namprd08.prod.outlook.com> <EDC652A26FB23C4EB6384A4584434A0407CC36CB@307622ANEX5.global.avaya.com>
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0407CC36CB@307622ANEX5.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [207.173.123.203]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ijetonboard.com
Cc: Melinda Shore <melinda.shore@gmail.com>, "cin@ietf.org" <cin@ietf.org>
Subject: Re: [cin] Bar BoF at IETF 84
X-BeenThere: cin@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <cin.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cin>, <mailto:cin-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/cin>
List-Post: <mailto:cin@ietf.org>
List-Help: <mailto:cin-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cin>, <mailto:cin-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 18:43:17 -0000

Dan

Yep.  I know some of the folks developing new wireless patient monitoring and drug dispensing systems.  Their view of wireless hospitals and continuous patient monitoring within ten years is amazing.

Plus UAVs, oil and gas, industrial control systems...

All places that you want don't want unexpected connections, messages, etc.

Take care
Terry

-----Original Message-----
From: Romascanu, Dan (Dan) [mailto:dromasca@avaya.com]
Sent: Monday, July 09, 2012 11:33 AM
To: Terry Davis; Wesley Eddy
Cc: Melinda Shore; cin@ietf.org
Subject: RE: [cin] Bar BoF at IETF 84

Life-support systems in hospitals, ERs and other medical environments are another use case.

Regards,

Dan




> -----Original Message-----
> From: cin-bounces@ietf.org [mailto:cin-bounces@ietf.org] On Behalf Of
> Terry Davis
> Sent: Monday, July 09, 2012 9:04 PM
> To: Wesley Eddy
> Cc: Melinda Shore; cin@ietf.org
> Subject: Re: [cin] Bar BoF at IETF 84
>
> Wes
>
> I could take a shot at one for aviation.  I think the financial
industry
> would likely also argue theirs are critical too.
>
> Take care
> Terry
>
> -----Original Message-----
> From: Wesley Eddy [mailto:wes@mti-systems.com]
> Sent: Saturday, July 07, 2012 7:49 PM
> To: Terry Davis
> Cc: Melinda Shore; cin@ietf.org
> Subject: Re: [cin] Bar BoF at IETF 84
>
> Is anyone working on a "problem statement" draft either specific to
some
> paricular critical infrastructure network, or generalized across
> multiple types?
>
> I think it would also be helpful to arrive at a more concrete
definition
> of what exactly a critical infrastructure network is, and how it
differs
> from any other network.  To me, it seems like the key difference is
that
> CINs are built to support command and control of physical systems
whose
> disruption could result in massively expensive or irreparable losses
> (e.g. the power grid, or spacecraft), or have impacts to human safety-
> of-life (e.g. civil aviation, and SCADA systems).
>
>
>
> On 7/7/2012 1:26 PM, Terry Davis wrote:
> > Melinda
> >
> > I'm sure assuming it will be in a bar and I can promise I won't
bring
> > slides (I may send some out to the list beforehand.)
> >
> > Take care
> > Terry
> >
> > -----Original Message-----
> > From: cin-bounces@ietf.org [mailto:cin-bounces@ietf.org] On Behalf
Of
> > Melinda Shore
> > Sent: Friday, July 06, 2012 10:44 AM
> > To: cin@ietf.org
> > Subject: Re: [cin] Bar BoF at IETF 84
> >
> > On 7/6/12 5:43 AM, Ronald Bonica wrote:
> >> Is there any interest in a bar BoF at IETF 84?
> >
> > Yes!  If both conditions are met:  1) it's in a bar, and 2) NO
slides.
> Discussion is almost always a very good thing.
> >
> > Melinda
> > _______________________________________________
> > cin mailing list
> > cin@ietf.org
> > https://www.ietf.org/mailman/listinfo/cin
> >
> > This message and its attachments are the property of iJet
> Technologies, Inc. and are intended solely for the use of the
designated
> recipient(s) and their appointed delegates. This email may contain
> information that is confidential. If you are not the intended
recipient,
> you are prohibited from printing, copying, forwarding or saving any
> portion of the message or attachments. Please delete the message and
> attachments and notify the sender immediately. Thank you for your
> cooperation.
> >
> > _______________________________________________
> > cin mailing list
> > cin@ietf.org
> > https://www.ietf.org/mailman/listinfo/cin
> >
> >
>
>
> --
> Wes Eddy
> MTI Systems
>
>
> _______________________________________________
> cin mailing list
> cin@ietf.org
> https://www.ietf.org/mailman/listinfo/cin

This message and its attachments are the property of iJet Technologies, Inc. and are intended solely for the use of the designated recipient(s) and their appointed delegates. This email may contain information that is confidential. If you are not the intended recipient, you are prohibited from printing, copying, forwarding or saving any portion of the message or attachments. Please delete the message and attachments and notify the sender immediately. Thank you for your cooperation.