Re: [Anima] Whether IPv6 only for ACP? //RE: I-D Action: draft-behringer-anima-autonomic-addressing-01.txt
Sheng Jiang <jiangsheng@huawei.com> Thu, 25 June 2015 03:00 UTC
Return-Path: <jiangsheng@huawei.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 D3C6E1A90D3 for <anima@ietfa.amsl.com>; Wed, 24 Jun 2015 20:00:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 oIkq_Ap5_8g8 for <anima@ietfa.amsl.com>; Wed, 24 Jun 2015 20:00:51 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 705301A8FD5 for <anima@ietf.org>; Wed, 24 Jun 2015 20:00:49 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BUH90332; Thu, 25 Jun 2015 03:00:47 +0000 (GMT)
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 25 Jun 2015 04:00:46 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.152]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Thu, 25 Jun 2015 11:00:34 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Duzongpeng <duzongpeng@huawei.com>, Michael Richardson <mcr+ietf@sandelman.ca>, "Michael Behringer (mbehring)" <mbehring@cisco.com>
Thread-Topic: [Anima] Whether IPv6 only for ACP? //RE: I-D Action: draft-behringer-anima-autonomic-addressing-01.txt
Thread-Index: AQHQru7z1uF+rKGbAUuFV4RBjHzBhZ28hwvA
Date: Thu, 25 Jun 2015 03:00:33 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B925F559959@nkgeml512-mbx.china.huawei.com>
References: <20150618095520.3486.7068.idtracker@ietfa.amsl.com> <55876E20.2070508@gmail.com> <3AA7118E69D7CD4BA3ECD5716BAF28DF22FF0FDC@xmb-rcd-x14.cisco.com> <21740.1435165907@sandelman.ca> <BAFEC9523F57BC48A51C20226A5589575E931D65@nkgeml505-mbx.china.huawei.com>
In-Reply-To: <BAFEC9523F57BC48A51C20226A5589575E931D65@nkgeml505-mbx.china.huawei.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.99.197]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/anima/3kKmdpoRerJ67E6u-IG4NZGv3qw>
Cc: Anima WG <anima@ietf.org>
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: Thu, 25 Jun 2015 03:00:53 -0000
We never have a restriction said that Autonomic Network must be IPv6-based. The same for the ANIMA current charter. If there are customers want IPv4-based ACP or IPv4-based Autonomic Network, I guess we should also work on that. By saying so, I still prefer IPv6 over IPv4 because we are future network oriented, and I assume future network is more IPv6. If we could work out something IP Independent, it may be better. Best regards, Sheng >-----Original Message----- >From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Duzongpeng >Sent: Thursday, June 25, 2015 10:06 AM >To: Michael Richardson; Michael Behringer (mbehring) >Cc: Anima WG >Subject: [Anima] Whether IPv6 only for ACP? //RE: 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) <mbehring@cisco.com> 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... > >a) to respond to the immediate "we want IPv4" --- I'd just tell the customer > that it uses a custom link layer protocol that uses an ethernet type > different than 0x0800... just like CDP does :-) > (I don't think you need to "deploy" IPv6 to have an ACP...) > >b) the only thing I care about is that nobody is allowed to say, "but > mechanism XYZ does not exist in IPv4". That's all. I don't know if > we will need IPv6-only things, but maybe. > >... > > >> Use-ULA: For these overlay addresses of autonomic nodes, we use >Unique > >> Local Addresses (ULA), as specified in [RFC4193]. An alternative > >> scheme was discussed, using assigned ULA addressing. The >consensus > >> was to use standard ULA, because it was deemed to be sufficient. > >It might be that ULA is an IPv6-only feature. >I don't consider 10/8 to be the same, as it is not statistically unique inside the >AS. > >-- >Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works >-= IPv6 IoT consulting =- > > > >_______________________________________________ >Anima mailing list >Anima@ietf.org >https://www.ietf.org/mailman/listinfo/anima
- Re: [Anima] I-D Action: draft-behringer-anima-aut… Brian E Carpenter
- Re: [Anima] I-D Action: draft-behringer-anima-aut… Michael Behringer (mbehring)
- Re: [Anima] I-D Action: draft-behringer-anima-aut… Brian E Carpenter
- Re: [Anima] I-D Action: draft-behringer-anima-aut… Michael Richardson
- [Anima] Whether IPv6 only for ACP? //RE: I-D Acti… Duzongpeng
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Sheng Jiang
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Michael Behringer (mbehring)
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Michael Behringer (mbehring)
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Duzongpeng
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Duzongpeng
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Michael Behringer (mbehring)
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Brian E Carpenter
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Sheng Jiang
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Michael Behringer (mbehring)
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Sheng Jiang
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Jonathan Hansford
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Jonathan Hansford
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Duzongpeng
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Jonathan Hansford
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Paul Duffy
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Michael Richardson
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Brian E Carpenter
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Duzongpeng
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Duzongpeng
- Re: [Anima] Whether IPv6 only for ACP? //RE: I-D … Duzongpeng