
From terry.davis@ijetonboard.com  Tue Nov  6 08:02:15 2012
Return-Path: <terry.davis@ijetonboard.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 B75D021F8A25 for <cin@ietfa.amsl.com>; Tue,  6 Nov 2012 08:02:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EszAxBrmMJAK for <cin@ietfa.amsl.com>; Tue,  6 Nov 2012 08:02:14 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) by ietfa.amsl.com (Postfix) with ESMTP id 8EBAD21F8A45 for <cin@ietf.org>; Tue,  6 Nov 2012 08:02:14 -0800 (PST)
Received: from mail55-va3-R.bigfish.com (10.7.14.241) by VA3EHSOBE008.bigfish.com (10.7.40.28) with Microsoft SMTP Server id 14.1.225.23; Tue, 6 Nov 2012 16:02:13 +0000
Received: from mail55-va3 (localhost [127.0.0.1])	by mail55-va3-R.bigfish.com (Postfix) with ESMTP id 474C42600B6	for <cin@ietf.org>; Tue,  6 Nov 2012 16:02:13 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.232.53; KIP:(null); UIP:(null); IPV:NLI; H:BLUPRD0811HT003.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -32
X-BigFish: VPS-32(z4c5Iz9371Ie6eL1102I542Mzz1de0h1202h1d1ah1d2ahzz1033IL172cfch17326ah8275bh8275dh18602ehz2fh2a8h668h839hd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h)
Received-SPF: pass (mail55-va3: domain of ijetonboard.com designates 157.56.232.53 as permitted sender) client-ip=157.56.232.53; envelope-from=terry.davis@ijetonboard.com; helo=BLUPRD0811HT003.namprd08.prod.outlook.com ; .outlook.com ; 
Received: from mail55-va3 (localhost.localdomain [127.0.0.1]) by mail55-va3 (MessageSwitch) id 1352217730296175_28745; Tue,  6 Nov 2012 16:02:10 +0000 (UTC)
Received: from VA3EHSMHS015.bigfish.com (unknown [10.7.14.235])	by mail55-va3.bigfish.com (Postfix) with ESMTP id 3C15A4E0048	for <cin@ietf.org>; Tue,  6 Nov 2012 16:02:10 +0000 (UTC)
Received: from BLUPRD0811HT003.namprd08.prod.outlook.com (157.56.232.53) by VA3EHSMHS015.bigfish.com (10.7.99.25) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 6 Nov 2012 16:02:09 +0000
Received: from BLUPRD0811MB425.namprd08.prod.outlook.com ([169.254.2.184]) by BLUPRD0811HT003.namprd08.prod.outlook.com ([10.255.123.38]) with mapi id 14.16.0233.002; Tue, 6 Nov 2012 16:02:09 +0000
From: Terry Davis <terry.davis@ijetonboard.com>
To: "cin@ietf.org" <cin@ietf.org>
Thread-Topic: Gentle Reminder
Thread-Index: Ac2PZd5BPWx60BQZTuOTa0bOTp+uVgsycAuQ
Date: Tue, 6 Nov 2012 16:02:09 +0000
Message-ID: <C8092F050778464AB435B2AB453E73FF44A8DF2C@BLUPRD0811MB425.namprd08.prod.outlook.com>
References: <13205C286662DE4387D9AF3AC30EF456D7830D79E4@EMBX01-WF.jnpr.net>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D7830D79E4@EMBX01-WF.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [63.133.204.34]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ijetonboard.com
Subject: Re: [cin] Gentle Reminder
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: Tue, 06 Nov 2012 16:02:15 -0000

All

Apologies that we didn't get this setup for this meeting here in Atlanta; w=
e plan to be ready for the spring meeting in Orlando.  A couple of us have =
begun to draft the problem statement and charter which we hope to post in t=
he near future.

For the aviation members of the group, we do have a working paper on aviati=
on cyber security going to the ICAO Air Navigation Commission for presentat=
ion at their session later this month.  We seem to have broad support for i=
t from the aviation community:  regulatory bodies, standards bodies, and th=
e major commercial entities.  It is available on their website at:
http://www.icao.int/Meetings/anconf12/WorkingPapers/Forms/AllItems.aspx    =
(Search the page for "cyber" to find our paper.)

For those of you that didn't hear or see Panetta's warning on cyber war las=
t month, I encourage you to read it:
http://www.nytimes.com/2012/10/12/world/panetta-warns-of-dire-threat-of-cyb=
erattack.html?pagewanted=3Dall&_r=3D0

If anything he may have understated the threats to critical infrastructure =
around the globe; every nation faces this problem in today's world.

We designed the Internet to be open and usable by everyone.  It has worked =
so well that our governments and commercial entities have also used it to s=
upport the critical infrastructure systems that control besides on communic=
ations; our power, our water, our food and medical distribution, hospitals,=
 vehicles, etc.  And now within a few years, the communications to the airc=
raft that you will be on flying to attend future IETF meetings.

The problem is that we have not created the standards needed for these type=
s of critical services to be placed on the Internet with truly enough secur=
ity to allow them to be adequately defended from cyber-attacks.

Or even to protect the Internet itself from some of the ways these groups m=
ay use it.  During the short life of Connexion by Boeing, we developed rout=
ing techniques that allowed passengers to maintain their VPN's without drop=
ping on trans-continental flights handing off between both different satell=
ites and ground stations on different continents.  This worked great for th=
e passengers but with just a 150 aircraft in service; it created routing st=
orms that were responsible for 20% of the churn in the global BGP tables.

There are agreements in place to work on solutions to this problem between =
the Internet community and the aviation community.  Routing remains a core =
concern.  Aviation could use different routing protocols but all these come=
 with BGP re-distributors.  Aviation could use only private networks or spe=
cial routing techniques.  The problem is that this is global service.  Anyo=
ne that has ever been involved with large global networks knows that "they =
are always cross-linked somewhere", someone always violates the approved de=
signs, re-distributed the wrong routing tree, etc.  ICAO has 140+ independe=
nt nation/states as members; 140+ independent operators of aviation communi=
cations within their borders!   With the current set of standards, can we s=
afely integrated aviation's use of the Internet without risking disruption =
to the Internet itself?

I remain unconvinced.  And for aviation and these critical infrastructure n=
etworks that our lives and our families truly depend on, do we really inten=
d to give them standards to operate with that are "naturally open" to anyon=
e on the globe to try to communicate with?

Look for more soon on the problem statement and charter.


Take care

Terry Davis, P.E.   |   Chief Scientist
terry.davis@ijetonboard.com
o. 206. 805. 6263 c. 425. 503. 5511
iJet Onboard   |  www.ijetonboard.com



-----Original Message-----
From: cin-bounces@ietf.org [mailto:cin-bounces@ietf.org] On Behalf Of Ronal=
d Bonica
Sent: Monday, September 10, 2012 8:07 AM
To: cin@ietf.org
Subject: [cin] Gentle Reminder

Folks,

Does this group still intend to hold a BoF at IETF 85? If so, the cut-off d=
ate for a BoF request is September 24.

Generally, a BoF request includes:

- a proposed charter
- a problem statement (which should be posted as an Internet Draft)

The deadline for posting version-00 IDs is October 15. However, it would be=
 great if the problem statement were posted by September 24.

--------------------------
Ron Bonica
vcard:       www.bonica.org/ron/ronbonica.vcf

_______________________________________________
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 th=
eir appointed delegates. This email may contain information that is confide=
ntial. If you are not the intended recipient, you are prohibited from print=
ing, copying, forwarding or saving any portion of the message or attachment=
s. Please delete the message and attachments and notify the sender immediat=
ely. Thank you for your cooperation.

