Re: [cin] Bar BoF at IETF 84

"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 09 July 2012 19:44 UTC

Return-Path: <Fred.L.Templin@boeing.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 B7DC211E820F for <cin@ietfa.amsl.com>; Mon, 9 Jul 2012 12:44:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.406
X-Spam-Level:
X-Spam-Status: No, score=-2.406 tagged_above=-999 required=5 tests=[AWL=0.193, BAYES_00=-2.599]
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 QS4MXGubBx5V for <cin@ietfa.amsl.com>; Mon, 9 Jul 2012 12:44:36 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) by ietfa.amsl.com (Postfix) with ESMTP id B77B411E8210 for <cin@ietf.org>; Mon, 9 Jul 2012 12:44:35 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (localhost.localdomain [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id q69Jj091000618 for <cin@ietf.org>; Mon, 9 Jul 2012 14:45:00 -0500
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.128.218]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id q69Jiwcf000603 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 9 Jul 2012 14:44:59 -0500
Received: from slb-av-01.boeing.com (localhost.localdomain [127.0.0.1]) by slb-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id q69Jiwku001185; Mon, 9 Jul 2012 12:44:58 -0700
Received: from XCH-NWHT-05.nw.nos.boeing.com (xch-nwht-05.nw.nos.boeing.com [130.247.25.109]) by slb-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id q69JivDQ001139 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Mon, 9 Jul 2012 12:44:57 -0700
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-05.nw.nos.boeing.com ([130.247.25.109]) with mapi; Mon, 9 Jul 2012 12:44:57 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Terry Davis <terry.davis@ijetonboard.com>, "Romascanu, Dan (Dan)" <dromasca@avaya.com>, Wesley Eddy <wes@mti-systems.com>
Date: Mon, 9 Jul 2012 12:44:54 -0700
Thread-Topic: [cin] Bar BoF at IETF 84
Thread-Index: Ac1bfVAJdF9Q/5LORiqK2S6YRIA4AAAIYroAADGlzgAAE7X5gABSKTcQAAEN0KAAABycAAACLEkQ
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65D8F24CD1B@XCH-NW-01V.nw.nos.boeing.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> <C8092F050778464AB435B2AB453E73FF41E8F9B0@BL2PRD0810MB349.namprd08.prod.outlook.com>
In-Reply-To: <C8092F050778464AB435B2AB453E73FF41E8F9B0@BL2PRD0810MB349.namprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: No
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 19:44:36 -0000

Use-case documents are often good starting points. We did
one for RANGER Scenarios (RFC6139) that discusses a number
of use cases that overlap with the ones this group is
targeting. Tony Hain and I also did one during the early
days of the IPv6 Unique Local Address (ULA) standards
development (draft-hain-templin-ipv6-localcomm) and,
although it was never published, it gave useful leverage
to help the ULA stuff along. I'd be up for participating
in a use case development effort, which I guess could be
subject matter for the Bar BoF?

Thanks - Fred


> -----Original Message-----
> From: cin-bounces@ietf.org [mailto:cin-bounces@ietf.org] On Behalf Of
> Terry Davis
> Sent: Monday, July 09, 2012 11:44 AM
> To: Romascanu, Dan (Dan); Wesley Eddy
> Cc: Melinda Shore; cin@ietf.org
> Subject: Re: [cin] Bar BoF at IETF 84
> 
> 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.
> 
> _______________________________________________
> cin mailing list
> cin@ietf.org
> https://www.ietf.org/mailman/listinfo/cin