Re: [Anima] I-D Action: draft-behringer-anima-autonomic-control-plane-00.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 03 November 2014 21:36 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81A181A06FD for <anima@ietfa.amsl.com>; Mon, 3 Nov 2014 13:36:43 -0800 (PST)
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=ham
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 tSHRS_rv-IQR for <anima@ietfa.amsl.com>; Mon, 3 Nov 2014 13:36:42 -0800 (PST)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 245A21A0A6A for <anima@ietf.org>; Mon, 3 Nov 2014 13:36:42 -0800 (PST)
Received: by mail-pa0-f52.google.com with SMTP id fa1so12832364pad.25 for <anima@ietf.org>; Mon, 03 Nov 2014 13:36:41 -0800 (PST)
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 :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=1pfSA/36dU7rD72P5hWHPaJ8A2CkLzs4SOTm/JQBKSA=; b=wjxlQkFN7YsaUPcz61Jb+tJkGua61dOhKWKvnPnY4RRhEtEc3AF99EN9cLysbsyd42 Xd87YVb6D8Gs/hGU3xXZXFK5xSf93/qLEyYvUoQg70l3aVQyTDj/nLdsk3EoNVC5zO4d 27olN11n+gh2sGWKdpDVmntxNJyZg1hQKnTcg6MdY9+Ybgv03vQBx6ZHk788w8D9jg3W obnmiKVC/WjaPP6aN5hRXRD9kEjlQiy+257C/g5GHkE3B6PspjYI2ftn4ZQUF0kysupN dUhTuZAPf9yY2BU8uvAMh9vHqJP+oCKiJK4HDfzf2wfC+NXkoP6Lm6E6C93fz++zuz8K OXUQ==
X-Received: by 10.68.136.137 with SMTP id qa9mr38649668pbb.8.1415050601639; Mon, 03 Nov 2014 13:36:41 -0800 (PST)
Received: from [130.216.38.108] (sc-cs-567-laptop.cs.auckland.ac.nz. [130.216.38.108]) by mx.google.com with ESMTPSA id u9sm18085760pdr.16.2014.11.03.13.36.39 for <anima@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Nov 2014 13:36:40 -0800 (PST)
Message-ID: <5457F566.4080409@gmail.com>
Date: Tue, 04 Nov 2014 10:36:38 +1300
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: anima@ietf.org
References: <20141017131337.4423.84144.idtracker@ietfa.amsl.com>
In-Reply-To: <20141017131337.4423.84144.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/anima/0Zk80ddGdHCY-tcLxrFmeQ9g5mY
Subject: Re: [Anima] I-D Action: draft-behringer-anima-autonomic-control-plane-00.txt
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Nov 2014 21:36:43 -0000

Hi,

This draft seems fairly clear to me, though I assume it will
evolve as other aspects of anima become clear. The proposal
to use a ULA prefix (section 3.7) seems good, since it
decouples the ACP from all external addressing considerations
and will work from a pure factory-reset condition. However,
it does raise a question (which also came up in homenet
recently). What happens if the network partitions? The ACP
will automatically partition too, but it will presumably keep
the same /48 ULA prefix everywhere. Does the partitioned network
retain the same domain ID in both parts? What happends in the
part that doesn't include the trust anchor? What happens if the
network recombines - will there be a risk of clashing subnets
created during the partition?

Also what happens if two previously unrelated networks combine?

   Brian