[cin] Random Notes

Eric Burger <eburger@standardstrack.com> Wed, 01 August 2012 22:38 UTC

Return-Path: <eburger@standardstrack.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 3A2A621F88AA for <cin@ietfa.amsl.com>; Wed, 1 Aug 2012 15:38:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.932
X-Spam-Level:
X-Spam-Status: No, score=-101.932 tagged_above=-999 required=5 tests=[AWL=0.666, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 zxplZxcq5lmw for <cin@ietfa.amsl.com>; Wed, 1 Aug 2012 15:38:32 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.250.112]) by ietfa.amsl.com (Postfix) with ESMTP id 7175621F889F for <cin@ietf.org>; Wed, 1 Aug 2012 15:38:32 -0700 (PDT)
Received: from dhcp-63da.meeting.ietf.org ([130.129.99.218]:58759) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1SwhYh-0005rs-EM for cin@ietf.org; Wed, 01 Aug 2012 15:38:27 -0700
From: Eric Burger <eburger@standardstrack.com>
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-92-481285379"
Date: Wed, 1 Aug 2012 15:38:25 -0700
Message-Id: <CFF58B69-0E14-4B4D-8EAC-CF08026AA01B@standardstrack.com>
To: cin@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Transfer-Encoding: 7bit
X-Pgp-Agent: GPGMail 1.3.3
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: [cin] Random Notes
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: Wed, 01 Aug 2012 22:38:33 -0000

These are NOT minutes from the meeting. They are random notes. They don't even capture who was there. It would be nice if someone who took copious notes could consolidate things.

The main action item is for Terry Davis and Bob Moskowitz to get together and write a problem statement draft in the next six weeks. For the calendar challenged, that would be by September 14.


CIN Bar BOF
Ron Bonica - sponsoring AD
Terry  Davis - iJET
Merike Kaeo - ISC
Robert Moskowitz

Eric Burger taking bad notes, not minutes

SIPRNET example

Scope:
Air transport
Trains (international, too: US, Canada, Mexico)
Power Grid
Enterprise SCADA
Medical - legacy infrastructure, different levels of access, etc.

Airplanes have 8+ networks: today multiple VPNs

Airplane has multiple prefixes. Airplane is multi-homed, and mobile.
How to run secure dynamic DNS?

First WG: Work on problem statement and issues with current solutions

Medical: Body area network
body contact, broadband, narrowband PHYs
802.15.4 (j - narrowband) 802.15.6 (FCC allocated)
In-hospital systems, or prescribed home systems
Hospital: break bottleneck of FDA approval of system, e.g., integrated system has to be approved, not just the components

Wireless devices get attached to patient. Patient moves from prep to OR to recovery to ...; different local controllers. Spectrum is secondary; WS-like sharing of frequency. 

Device needs to prove its identity. Easy for an airplane, but harder for a 20 micro-amp 8-bit CPU. HIP issues and solutions (smart endpoints), LISP issues and solutions (smart network).

Entity mobility
- class of solution: give entities permanent identifiers independent of connectivity
Cost of losing connectivity is exhorbitant

Problem statement: secure reliable mobility