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