Re: [cin] Bar BoF at IETF 84

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 09 July 2012 18:32 UTC

Return-Path: <dromasca@avaya.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 C6E4311E8102 for <cin@ietfa.amsl.com>; Mon, 9 Jul 2012 11:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.465
X-Spam-Level:
X-Spam-Status: No, score=-103.465 tagged_above=-999 required=5 tests=[AWL=0.134, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 MSVRUvkSB4DV for <cin@ietfa.amsl.com>; Mon, 9 Jul 2012 11:32:49 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 94B4C11E80D0 for <cin@ietf.org>; Mon, 9 Jul 2012 11:32:49 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAEYj+0/GmAcF/2dsb2JhbABFt3aBB4IgAQEBAQMBAQEPHgo0CwwEAgEIDQQEAQEBCgYMCwEGASYfCQgBAQQBEggRCYdrC55onRgEi0AbhRFgA5suig2CYYFUBwI
X-IronPort-AV: E=Sophos;i="4.77,554,1336363200"; d="scan'208";a="314369261"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 09 Jul 2012 14:30:04 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 09 Jul 2012 14:30:02 -0400
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 9 Jul 2012 20:33:10 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0407CC36CB@307622ANEX5.global.avaya.com>
In-Reply-To: <C8092F050778464AB435B2AB453E73FF41E8F8FC@BL2PRD0810MB349.namprd08.prod.outlook.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [cin] Bar BoF at IETF 84
Thread-Index: Ac1bfVAJdF9Q/5LORiqK2S6YRIA4AAAIYroAADGlzgAAE7X5gABSKTcQAAEN0KA=
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>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Terry Davis" <terry.davis@ijetonboard.com>, "Wesley Eddy" <wes@mti-systems.com>
Cc: Melinda Shore <melinda.shore@gmail.com>, 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:32:50 -0000

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