Re: [nmrg] Control plane [was Next version of draft-irtf-nmrg-autonomic-network-definitions]

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 30 July 2014 20:07 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: nmrg@ietfa.amsl.com
Delivered-To: nmrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 269C31A0395 for <nmrg@ietfa.amsl.com>; Wed, 30 Jul 2014 13:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wPBlAD83u0AJ for <nmrg@ietfa.amsl.com>; Wed, 30 Jul 2014 13:07:43 -0700 (PDT)
Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B563F1A032D for <nmrg@irtf.org>; Wed, 30 Jul 2014 13:07:42 -0700 (PDT)
Received: by mail-pa0-f48.google.com with SMTP id et14so2129654pad.21 for <nmrg@irtf.org>; Wed, 30 Jul 2014 13:07:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=fy+PJ7iRDA6OdKexGZkCBjjBfm+2yAGd8eYXCzMMM88=; b=0yf+GoeiJ+/IruKGl/aZubuhEl33lLwsoxajU7DUSw03YtxK5V0qAeaptLFkmTUZvS KwkS31adsl64lTBeZT5OaZ5OVcYDF7iVKCacy4SSJfzn+uVqWjn72o9XdlstPDzpGk0g eNqvEOY3R/iAHPmfe2bI9pirWMzK3QFQK2cs4wf7/rP8WmUFVUSmm2oswLLgXgZ1YPER U1EQ1bmfVgCrL23oxXIqm7W1U9LCGE/F3Frp9rMUub7JpVinIRqmEYIMAC4dCuay0J6q wvSrBu+Ab/gCPzf+tk5KRJ/3b6iBNJoVF5Rcbyzd8MyIoHPBuEYyVnWP0+rHwudvJ7Rl MDTQ==
X-Received: by 10.70.55.227 with SMTP id v3mr6592509pdp.82.1406750861392; Wed, 30 Jul 2014 13:07:41 -0700 (PDT)
Received: from [192.168.178.23] (147.199.69.111.dynamic.snap.net.nz. [111.69.199.147]) by mx.google.com with ESMTPSA id z4sm4785222pda.84.2014.07.30.13.07.38 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 30 Jul 2014 13:07:40 -0700 (PDT)
Message-ID: <53D95090.2090904@gmail.com>
Date: Thu, 31 Jul 2014 08:07:44 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Michael Behringer (mbehring)" <mbehring@cisco.com>
References: <3AA7118E69D7CD4BA3ECD5716BAF28DF21BF933F@xmb-rcd-x14.cisco.com> <53D7C297.3080700@alcatel-lucent.com> <53D80265.8070404@gmail.com> <3AA7118E69D7CD4BA3ECD5716BAF28DF21BFA22A@xmb-rcd-x14.cisco.com>
In-Reply-To: <3AA7118E69D7CD4BA3ECD5716BAF28DF21BFA22A@xmb-rcd-x14.cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/7ajq1JVVNs6TqA6Gf2icrnWD5so
Cc: "draft-irtf-nmrg-autonomic-network-definitions@tools.ietf.org" <draft-irtf-nmrg-autonomic-network-definitions@tools.ietf.org>, "nmrg@irtf.org" <nmrg@irtf.org>, "anima@ietf.org" <anima@ietf.org>
Subject: Re: [nmrg] Control plane [was Next version of draft-irtf-nmrg-autonomic-network-definitions]
X-BeenThere: nmrg@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Management Research Group discussion list <nmrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nmrg>, <mailto:nmrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/nmrg/>
List-Post: <mailto:nmrg@irtf.org>
List-Help: <mailto:nmrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nmrg>, <mailto:nmrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jul 2014 20:07:46 -0000

On 30/07/2014 20:45, Michael Behringer (mbehring) wrote:
>> -----Original Message-----
>> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
>> Sent: 29 July 2014 22:22
>> To: Laurent Ciavaglia
>> Cc: Michael Behringer (mbehring); nmrg@irtf.org; anima@ietf.org; draft-
>> irtf-nmrg-autonomic-network-definitions@tools.ietf.org
>> Subject: Control plane [was Next version of draft-irtf-nmrg-autonomic-
>> network-definitions]
>>
>> Just commenting on one point from Laurent. I'll stick to cross-posting for
>> this point. In due course I think we should avoid it, but OK for now.
>>
>>> -It is not clear/straightforward what "in the global context of each device"
>> means. If we want to say that the control protocols can run in-band/out-
>> band, let's just say that.
>>
>> Yes, I think we have to be more explicit. One approach is to have an explicit
>> autonomic control plane which is an in-band overlay on the physical
>> network. Another approach is to make this implicit - just use the existing
>> L2/L3 network but without considering it to be a control plane at all (that's
>> what most routing protocols do). A third approach would be a truly separate
>> control plane such as a dedicated L2VPN. The point is that they could all
>> support autonomic behaviour; it's a design choice.
> 
> Suggestions for better wording is welcome. For a L3 device it's relatively clear: It's either the global routing table or a virtual routing table, such as a VRF, or a virtual router. Problem is that the concept of the Autonomic Control Plane as described in draft-behringer-autonomic-control-plane applies also to non-L3 devices, for example to switches or NMS systems, or .... 
> 
> So, what is the generic term for "global routing table" and "virtual routing table" which is valid also for non-L3 devices? 
> 
> So, the full range of options is: 
> - inband, as we run for example IGPs today
> - Over a configured VPN ("management VPN")
> - Over the self-managing Autonomic Control Plane (See above mentioned draft)
> - Over a "real" out of band network. 
> 
> Should we list those, 

IMHO, we should definitely list them.

> and explain what they do in a bit more detail? Maybe that would make things clearer... 

I'm not sure that is needed in the definitions draft; it might get a bit
complicated. But I certainly have no objection to one or two sentences
for each one. We should probably avoid pros and cons, since that is
not the job of a definition.

   Brian