Re: [cin] Aviation Networks

Ronald Bonica <rbonica@juniper.net> Wed, 11 July 2012 14:38 UTC

Return-Path: <rbonica@juniper.net>
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 1FBB821F8665 for <cin@ietfa.amsl.com>; Wed, 11 Jul 2012 07:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.421
X-Spam-Level:
X-Spam-Status: No, score=-106.421 tagged_above=-999 required=5 tests=[AWL=-0.138, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315, 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 TN17geoHWI5j for <cin@ietfa.amsl.com>; Wed, 11 Jul 2012 07:38:20 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id 7472B21F865A for <cin@ietf.org>; Wed, 11 Jul 2012 07:38:20 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKT/2P+IsS1ly5k2nXPftqRDVonN34ZKA1@postini.com; Wed, 11 Jul 2012 07:38:51 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 11 Jul 2012 07:38:41 -0700
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by p-cldfe02-hq.jnpr.net (172.24.192.60) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 11 Jul 2012 07:38:41 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Wed, 11 Jul 2012 10:38:39 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Terry Davis <terry.davis@ijetonboard.com>, "cin@ietf.org" <cin@ietf.org>
Date: Wed, 11 Jul 2012 10:38:38 -0400
Thread-Topic: Aviation Networks
Thread-Index: Ac1bkkTQElzaf7hFTCy3wRVGz7qMFQD31g2g
Message-ID: <13205C286662DE4387D9AF3AC30EF456D76FFA27A8@EMBX01-WF.jnpr.net>
References: <C8092F050778464AB435B2AB453E73FF41E8C1CB@CH1PRD0810MB360.namprd08.prod.outlook.com>
In-Reply-To: <C8092F050778464AB435B2AB453E73FF41E8C1CB@CH1PRD0810MB360.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: multipart/alternative; boundary="_000_13205C286662DE4387D9AF3AC30EF456D76FFA27A8EMBX01WFjnprn_"
MIME-Version: 1.0
Subject: Re: [cin] Aviation Networks
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, 11 Jul 2012 14:38:22 -0000

Terry,

I am not sure that I agree with your first statement. Why couldn't you build a closed network using OTS gear that implements current IETF standards?  Are there not many examples of such networks (e.g., SIPRNET )?

The second problem is more interesting. The CIN might want to standardize a BGP policy with the following characteristics:


-          Enforces a globally agreed routing policy

-          Does not fail in a catastrophic way when one node/country does something that does not comply with policy
                                                                                            Ron


From: cin-bounces@ietf.org [mailto:cin-bounces@ietf.org] On Behalf Of Terry Davis
Sent: Friday, July 06, 2012 12:13 PM
To: cin@ietf.org
Subject: [cin] Aviation Networks


Two problems immediately come up with this path:

-          Current standards don't readily support the concept of closed or isolate networks.

-          And as any of you that operate large networks, especially globally with millions of nodes, know, they are always cross-wired somewhere.  And thus defining a scheme to protect the Internet BGP tables from disruption is going to be very challenging.  And don't forgot, there will not be a single network operator; most of the 140 nations will operate their own part of it.