Re: [nmrg] IRSG Review of NMRG document draft-irtf-nmrg-autonomic-network-definitions-04.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 12 December 2014 18:55 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 357B91A7020 for <nmrg@ietfa.amsl.com>; Fri, 12 Dec 2014 10:55:09 -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 HDRa-F-o6Asu for <nmrg@ietfa.amsl.com>; Fri, 12 Dec 2014 10:55:07 -0800 (PST)
Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 878341A88C2 for <nmrg@irtf.org>; Fri, 12 Dec 2014 10:55:07 -0800 (PST)
Received: by mail-pd0-f174.google.com with SMTP id fp1so7622601pdb.19 for <nmrg@irtf.org>; Fri, 12 Dec 2014 10:55:06 -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:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=o6eG+eq8wfN9aDBoMMZINCpIQiMyJnqmtTf7fBYzPHA=; b=H6jICQgGrZoNkS2PmSfsP+gdJGUhOmazqJwxk3e331dJH39bD4DA1LRY94zkgxNh9l BAXBwq+5uYoqcHulEovPPkCyxQNetwjARt9TUc7HZhdl1PkII/dtcgJzpSLZ22F4uybX DijN5zLtflDp4ZunMHO9aPQDVe25E4Ps7UhI6hR7Yv3Bw6LSN7WUkXu7wH2UPtJZdqYw JJhUxcLOsDRKk4ryVcs0ajxaQa7eMe85xLUT51dgNj4H05NlorAkx886P1f2aTVMRNRw C21Aj9W1XDhfctVQXWrZjsJ7wR6/06QW+MmyK6ilGATjyoUavlRFU5Fe+tW90Nf1ywib Z5Tw==
X-Received: by 10.66.219.70 with SMTP id pm6mr29248649pac.126.1418410506821; Fri, 12 Dec 2014 10:55:06 -0800 (PST)
Received: from [192.168.178.26] (235.231.69.111.dynamic.snap.net.nz. [111.69.231.235]) by mx.google.com with ESMTPSA id lz6sm2152432pdb.88.2014.12.12.10.55.03 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Dec 2014 10:55:05 -0800 (PST)
Message-ID: <548B3A0E.8080401@gmail.com>
Date: Sat, 13 Dec 2014 07:55:10 +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: Michael Behringer <mbehring@cisco.com>
References: <E94E9E13-2A74-4A09-AD7A-CDB8C5BC8171@inf.ufrgs.br> <F245B425-D538-4B94-A5FA-0E0D27D0759D@netapp.com> <31F12CB7-2694-44EB-97AA-11FB863C173A@netapp.com> <20C63FF7-971B-4FA1-A935-CD26A50D0972@orandom.net> <548B187C.80508@cisco.com>
In-Reply-To: <548B187C.80508@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/nmrg/hnDo3nhW7IocRdQHr51dzGSOBXc
Cc: draft-irtf-nmrg-autonomic-network-definitions@tools.ietf.org, nmrg@irtf.org, David R Oran <daveoran@orandom.net>
Subject: Re: [nmrg] IRSG Review of NMRG document draft-irtf-nmrg-autonomic-network-definitions-04.txt
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: Fri, 12 Dec 2014 18:55:09 -0000

On 13/12/2014 05:31, Michael Behringer wrote:
...
>> P4
>>     • You restrict the operation of autonomic networks to work by
>> pari-wise protocols.negotiations. In particular, you say
>>         • " peer-to-peer dialogues  between the parties that make up
>> the closed loop.  Such dialogues
>> require two-way "discussion" or "negotiation" between each pair of 
>> peers involved in the loop, so they cannot readily use typical
>> top-down command-response protocols.between the parties that make up
>> the closed loop.  Such dialogues require two-way "discussion" or
>> "negotiation" between each pair peers involved in the loop, so they
>> cannot readily use typical top down command-response protocols.”
>>     • While you are quite explicit about this, I don’t see any
>> fundamental reason why the protocols and negotiations could not be
>> multi-party, or exploit consensus protocols like Paxos. It’s probably
>> OK to go ahead and not address this, but since it occurred to me it
>> might also occur to other readers well-versed in distributed algorithms.
> 
> Very good point. Clarified that.

Just a comment: multi-party protocols get very complex and in
particular, guaranteed consensus or consensus within a defined
time becomes challenging. In the context of an IETF protocol
that can be extended piecemeal by a large variety of designers,
restricting ourselves to two-party negotiation seems wise.

   Brian