[ncrg] SDN addresses control plane complexity, not data plane

Bob Briscoe <bob.briscoe@bt.com> Thu, 14 March 2013 14:15 UTC

Return-Path: <bob.briscoe@bt.com>
X-Original-To: ncrg@ietfa.amsl.com
Delivered-To: ncrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C452B11E8180 for <ncrg@ietfa.amsl.com>; Thu, 14 Mar 2013 07:15:56 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tHUoxx+8TFqF for <ncrg@ietfa.amsl.com>; Thu, 14 Mar 2013 07:15:52 -0700 (PDT)
Received: from hubrelay-by-04.bt.com (hubrelay-by-04.bt.com [62.7.242.140]) by ietfa.amsl.com (Postfix) with ESMTP id A792311E8183 for <ncrg@irtf.org>; Thu, 14 Mar 2013 07:15:48 -0700 (PDT)
Received: from EVMHR02-UKBR.domain1.systemhost.net (193.113.108.41) by EVMHR04-UKBR.bt.com (10.216.161.36) with Microsoft SMTP Server (TLS) id 8.3.297.1; Thu, 14 Mar 2013 14:15:47 +0000
Received: from EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) by EVMHR02-UKBR.domain1.systemhost.net (193.113.108.41) with Microsoft SMTP Server (TLS) id 8.3.297.1; Thu, 14 Mar 2013 14:15:46 +0000
Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) with Microsoft SMTP Server id 14.2.342.3; Thu, 14 Mar 2013 14:15:42 +0000
Received: from BTP075694.jungle.bt.co.uk ([10.111.51.200]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id r2EEFbkN031880; Thu, 14 Mar 2013 14:15:39 GMT
Message-ID: <201303141415.r2EEFbkN031880@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 14 Mar 2013 14:15:37 +0000
To: Dave MEYER <dmm@1-4-5.net>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <3AA7118E69D7CD4BA3ECD5716BAF28DF0F6EBB03@xmb-rcd-x14.cisco .com>
References: <3AA7118E69D7CD4BA3ECD5716BAF28DF0F6EBB03@xmb-rcd-x14.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-Mailman-Approved-At: Thu, 14 Mar 2013 07:35:19 -0700
Cc: "ncrg@irtf.org" <ncrg@irtf.org>, Rui Aguiar <ruilaa@ua.pt>
Subject: [ncrg] SDN addresses control plane complexity, not data plane
X-BeenThere: ncrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Network Complexity Research Group <ncrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/ncrg>, <mailto:ncrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/ncrg>
List-Post: <mailto:ncrg@irtf.org>
List-Help: <mailto:ncrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/ncrg>, <mailto:ncrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 14:15:56 -0000

Dave,

At one point in your talk on SDN & complexity, you pointed to just 
under the neck of the classic TCP/IP hourglass as the point that the 
originators of SDN chose to address.

The message wrt complexity is really the reverse. SDN doesn't attack 
the narrowest (least diverse) layer, it attacks the fattest (most 
diverse) layer, in an attempt to narrow it to a single standard 
(cutting out complexity).

Reason: The hour-glass represents the data plane. SDN concerns the 
control plane (specifically routing). The equivalent of the 
hour-glass in the control plane has evolved into an inverse 
hour-glass - a fatty-glass. See slide #8 or even #15 in Rui's 
presentation here:
<https://www.net.t-labs.tu-berlin.de/arcadia/talks/Aguiar.pdf>
or the paper: "Some comments on hour glasses"
<http://dl.acm.org/citation.cfm?id=1452346>

The more important a layer is for interoperability, the thinner the 
layer. All the different routing protocols make the control plane 
into a fatty-glass, because there is no /operational/ need for 
interop between routing protocols within different ASs.

SDN attempts to narrow the control fatty-glass by standardisation of 
intra-domain policy-routing at build time, which implies the industry 
is maturing from a focus on run-time conformity (between operators) 
in the data plane by adding build-time conformity (between vendors) 
in the control plane.


Bob



________________________________________________________________
Bob Briscoe,                                                  BT