Re: [v6ops] MAC table shortage in IPv6 networks caused by multiple IPv6 prefixes/addresses//FW: New Version Notification for draft-liu-v6ops-running-multiple-prefixes-01.txt

"Liubing (Leo)" <leo.liubing@huawei.com> Mon, 14 July 2014 01:34 UTC

Return-Path: <leo.liubing@huawei.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAD5C1A023E for <v6ops@ietfa.amsl.com>; Sun, 13 Jul 2014 18:34:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 YMGNEczPr3rh for <v6ops@ietfa.amsl.com>; Sun, 13 Jul 2014 18:33:58 -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 D60F71A0218 for <v6ops@ietf.org>; Sun, 13 Jul 2014 18:33:57 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJX75092; Mon, 14 Jul 2014 01:33:56 +0000 (GMT)
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 14 Jul 2014 02:33:55 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.24]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001; Mon, 14 Jul 2014 09:33:53 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Andrew Yourtchenko <ayourtch@cisco.com>
Thread-Topic: [v6ops] MAC table shortage in IPv6 networks caused by multiple IPv6 prefixes/addresses//FW: New Version Notification for draft-liu-v6ops-running-multiple-prefixes-01.txt
Thread-Index: AQHPnP/VZpO9KrP2SUaaf9dQAO2Sl5uey65g
Date: Mon, 14 Jul 2014 01:33:52 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D8F2C89@nkgeml506-mbx.china.huawei.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D8EEA21@nkgeml506-mbx.china.huawei.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D8F1C32@nkgeml506-mbx.china.huawei.com> <alpine.DEB.2.02.1407091226000.7929@uplift.swm.pp.se> <CFE32281.2067C%evyncke@cisco.com> <alpine.DEB.2.02.1407091710020.7929@uplift.swm.pp.se> <alpine.OSX.2.00.1407091840270.99248@ayourtch-mac> <8AE0F17B87264D4CAC7DE0AA6C406F453D8F291C@nkgeml506-mbx.china.huawei.com> <alpine.OSX.2.00.1407101220310.93503@ayourtch-mac> <8AE0F17B87264D4CAC7DE0AA6C406F453D8F2AB4@nkgeml506-mbx.china.huawei.com> <alpine.OSX.2.00.1407111029250.37292@ayourtch-mac> <8AE0F17B87264D4CAC7DE0AA6C406F453D8F2AF9@nkgeml506-mbx.china.huawei.com> <alpine.OSX.2.00.1407111359480.77389@ayourtch-mac>
In-Reply-To: <alpine.OSX.2.00.1407111359480.77389@ayourtch-mac>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.132]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/bK8nz-1viGeuNsQ0rV3rYRaSm8U
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] MAC table shortage in IPv6 networks caused by multiple IPv6 prefixes/addresses//FW: New Version Notification for draft-liu-v6ops-running-multiple-prefixes-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2014 01:34:00 -0000

Hi Andrew,

> > [Bing] I can hardly say SLAAC and DHCPv6 co-existing is a
> > misconfiguration,
> 
> Note, I said "for this specific case". If you control your devices *and* devices
> are DHCPv6-capable *and* you want to minimize the number of addresses
> using SLAAC is not ideal.
[Bing] For this case, I think you're right. It might be good to add some texts regarding to the cache table problem in http://tools.ietf.org/html/draft-liu-v6ops-dhcpv6-slaac-guidance-01

Thanks.


Best regards,
Bing