Re: [cin] Bar BoF at IETF 84

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