Re: [Anima] Whether IPv6 only for ACP? //RE: I-D Action: draft-behringer-anima-autonomic-addressing-01.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 26 June 2015 20:45 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 C8B501ACD1C for <anima@ietfa.amsl.com>; Fri, 26 Jun 2015 13:45:29 -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=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 8LuRRXk-58f5 for <anima@ietfa.amsl.com>; Fri, 26 Jun 2015 13:45:27 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70E631A8900 for <anima@ietf.org>; Fri, 26 Jun 2015 13:45:27 -0700 (PDT)
Received: by pdbci14 with SMTP id ci14so81004513pdb.2 for <anima@ietf.org>; Fri, 26 Jun 2015 13:45:27 -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 :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Qf6rjfXq63/OKhhd9j64f/wIfKB3prlFNHYABGNE1vc=; b=WHj+Tf0/CC/8ZLc+dldBg1pg0ZVTmhX4hCSk5Zo9Me3009YCtxK5hMHbpDNmhwiaZw Gq0yWWGTWucdtEVWTxzEZyV5hp0S8WG6A6V8gSyLmrkSJ0YPRt8RRrExmxLfxYErHnFo 1zANyULW7CMjg4SQwynZlnEBhU3K3Fk+6lzn6AUt+TXmGZ3TKJClL6wdvtY8S+HQuZy9 IknjMKnmv7RJSr8V7WNgMeFOOSDfgWEN8+lZ+FfVkty6wW9cYhEISY5n6WbtK3rob9zf vlNC6+UlrBzzq96Nal9cpBxzhkKGVCqwY2fqGo5I2wyIHJB2E31p0QZqEnyIckQ0pEOf 0TwQ==
X-Received: by 10.68.185.37 with SMTP id ez5mr6984207pbc.74.1435351527192; Fri, 26 Jun 2015 13:45:27 -0700 (PDT)
Received: from ?IPv6:2406:e007:4e59:1:28cc:dc4c:9703:6781? ([2406:e007:4e59:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id pb6sm10475998pbc.75.2015.06.26.13.45.24 for <anima@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 26 Jun 2015 13:45:25 -0700 (PDT)
Message-ID: <558DB9ED.3040207@gmail.com>
Date: Sat, 27 Jun 2015 08:45:33 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: anima@ietf.org
References: <bccb22c0965b4828b52221c73eacf49e52eeb8c3@webmail.hansfords.net>
In-Reply-To: <bccb22c0965b4828b52221c73eacf49e52eeb8c3@webmail.hansfords.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/anima/ChXFicf8irFY1NLQAURcOBATXiU>
Subject: Re: [Anima] Whether IPv6 only for ACP? //RE: I-D Action: draft-behringer-anima-autonomic-addressing-01.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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 26 Jun 2015 20:45:29 -0000

On 26/06/2015 20:36, Jonathan Hansford wrote:
> There are some systems outside the Internet that have no urgent need
> to move to IPv6 and developers would rather focus on more urgent
> needs.  Autonomic networking could well be one of those more urgent
> needs.

What is the harm if the AN products that they install happen to configure
themselves to use IPv6? Since any router that acts as an autonomic node
will be modern enough to support an IPv6 ACP with no manual intervention,
why would the operator even know or care?

    Brian


> Jonathan
> 
> ----- Original Message -----
> From: "Michael Behringer (mbehring)" 
> To:"Duzongpeng" , "Michael Richardson" 
> Cc:"Anima WG" 
> Sent:Thu, 25 Jun 2015 11:56:19 +0000
> Subject:Re: [Anima] Whether IPv6 only for ACP? //RE: I-D Action:
> draft-behringer-anima-autonomic-addressing-01.txt
> 
>  For something new like AN, where the standardised specs will take at
> least a couple of years to appear in anyone's products, where we do
> NOT have backward compatibility issues, where we do not address end
> systems for some years to come, I personally think it is insane to
> even consider IPv4. 
> 
>  But I think we do have agreement that we start with IPv6 only, and
> just keep the door open, in case we need to support it. If the working
> group wants to do that, I'll change the text accordingly. Maybe a
> discussion for Prague? 
> 
>  Michael
> 
>  > -----Original Message-----
>  > From: Duzongpeng [mailto:duzongpeng@huawei.com]
>  > Sent: 25 June 2015 10:24
>  > To: Michael Behringer (mbehring); Michael Richardson
>  > Cc: Anima WG
>  > Subject: RE: [Anima] Whether IPv6 only for ACP? //RE: I-D Action:
> draft-
>  > behringer-anima-autonomic-addressing-01.txt
>  > 
>  > Hi, Michael Behringer
>  > 
>  > I agree that the default setting of the ACP could be IPv6-based,
> which may
>  > make the communication across autonomic domains easier to
> implement.
>  > 
>  > What I suggested is that we first have an IPv6-based ACP ready, and
> define
>  > an IPv4-based one as an alternative option.
>  > 
>  > Best regards
>  > Zongpeng Du
>  > 
>  > -----Original Message-----
>  > From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Michael
>  > Behringer (mbehring)
>  > Sent: Thursday, June 25, 2015 3:31 PM
>  > To: Duzongpeng; Michael Richardson
>  > Cc: Anima WG
>  > Subject: Re: [Anima] Whether IPv6 only for ACP? //RE: I-D Action:
> draft-
>  > behringer-anima-autonomic-addressing-01.txt
>  > 
>  > Re-reading my own message, one thing to add: Brian has already
> stated that
>  > GDNP is protocol independent, and it should be. Of course we want
> to
>  > develop everything IP version independent wherever possible.
>  > 
>  > But there has to be some default autonomic addressing, routing, and
> for
>  > THAT we want to look at IPv6 only at this point.
>  > 
>  > Michael
>  > 
>  > > -----Original Message-----
>  > > From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Michael
>  > > Behringer (mbehring)
>  > > Sent: 25 June 2015 09:25
>  > > To: Duzongpeng; Michael Richardson
>  > > Cc: Anima WG
>  > > Subject: Re: [Anima] Whether IPv6 only for ACP? //RE: I-D Action:
>  > > draft- behringer-anima-autonomic-addressing-01.txt
>  > >
>  > > OK, I think there is some confusion around this topic.
>  > >
>  > > A network with autonomic functions (we all agree that a fully
>  > > autonomic network is not our main target for now) can support on
> the
>  > > *data plane* any protocol the operator wants to use, including
> IPv4,
>  > > appletalk and IPv8 (when it comes).
>  > >
>  > > The statement is for the signalling, messaging and other
> protocols
>  > > INSIDE the ACP, used by Autonomic Service Agents.
>  > >
>  > > Autonomic Service Agents will be exposed to a developer
> community, and
>  > > the vendors implementing the ACP. There is absolutely no reason
> to
>  > > standardise more than one protocol for this purpose.
>  > >
>  > > MichaelR is right: You don't need to actively deploy IPv6 to use
> the
>  > > ACP. It just happens. With one caveat: If you connect an NMS
> system
>  > > into the ACP for "virtual out of band" usage, then that system
> needs
>  > > to support IPv6. But that is typically not a problem, in our
> experience.
>  > >
>  > > In other words: We're saying that *autonomic functions* (which
> the end
>  > > user isn't exposed to at all) are exclusively IPv6, but the
> network
>  > > can provide any service the operator wants. Specifically, an
> autonomic
>  > > function (running on an IPv6 control plane) may well negotiate
>  > > addressing for IPv4 services.
>  > >
>  > > Michael
>  > >
>  > > > -----Original Message-----
>  > > > From: Duzongpeng [mailto:duzongpeng@huawei.com]
>  > > > Sent: 25 June 2015 04:06
>  > > > To: Michael Richardson; Michael Behringer (mbehring)
>  > > > Cc: Anima WG
>  > > > Subject: Whether IPv6 only for ACP? //RE: [Anima] I-D Action:
> draft-
>  > > > behringer-anima-autonomic-addressing-01.txt
>  > > >
>  > > > Hi, Michael Richardson:
>  > > >
>  > > > I agree with your option. Perhaps ACP is not needed to be IPv6
> only.
>  > > >
>  > > > Of course, an IPv6 only autonomic control plane is ok for all
> the
>  > > > services in autonomic network, and the solution has the
> advantage of
>  > > > simplicity as mentioned by Michael Behringer.
>  > > >
>  > > > However, the network operator may be more familiar with the
> IPv4-
>  > > > base management.
>  > > > In the beginning of the ACP deployment, the network operator
> may
>  > > not
>  > > > be very confident about the decisions made by the autonomic
> network.
>  > > > Some kinds of monitoring jobs may be desired by the network
> operators.
>  > > > At this time, the operator may want to see some IPv4 addresses.
> So,
>  > > > perhaps we need to provide IPv4-based ACP as an option for
> these
>  > > > parts of operators. Otherwise, we can only answer them "sorry,
> we
>  > > > only support
>  > > > IPv6 here".
>  > > >
>  > > > As IPv4 has been widely deployed, perhaps an IPv4-based
>  > > autonomic
>  > > > network will be accepted by more network managers at the
> beginning.
>  > > >
>  > > > Indeed, at this time, an IPv4-based ACP is not as mature as the
>  > > > IPv6 one. Thus, perhaps some work needs to be done at this
>  > > > direction. For example, as you mentioned, how can we get an
> address
>  > > > instead of the ULA in IPv6.
>  > > >
>  > > > Best regards
>  > > > Zongpeng Du
>  > > >
>  > > > -----Original Message-----
>  > > > From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of
> Michael
>  > > > Richardson
>  > > > Sent: Thursday, June 25, 2015 1:12 AM
>  > > > To: Michael Behringer (mbehring)
>  > > > Cc: Anima WG
>  > > > Subject: Re: [Anima] I-D Action:
> draft-behringer-anima-autonomic-
>  > > > addressing-01.txt
>  > > >
>  > > >
>  > > > Michael Behringer (mbehring)  wrote:
>  > > > >> > IPv6 only: Autonomic processes should use exclusively
> IPv6, for
>  > > > >> > simplicity reasons.
>  > > > >>
>  > > > >> I agree with this as long as it's an RFC 2119 SHOULD, i.e.
>  > > > IPv4 could be used in
>  > > > >> extraordinary circumstances. The GDNP design is
> fundamentally
>  > > > IP- version
>  > > > >> independent.
>  > > >
>  > > > > Yes, as long as it's really "extraordinary" ;-) That 2119
> says
>  > > > > "SHOULD" means like you need a really good reason to not do
> it.
>  > What
>  > > > > would such a good reason be? Just saying, in our
> implementation we
>  > > > > often get the requirement "we want IPv4", and when you dig,
>  > > > the reason
>  > > > > is that they don't want to deploy IPv6, and that's the only
>  > > > > reason. Slippery slope...
>  &gt
> 
> 
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima
>