Re: [v6ops] DHCPv6/SLAAC Interaction Operational Guidance-//RE: new draft: draft-liu-v6ops-dhcpv6-slaac-guidance

"Liubing (Leo)" <leo.liubing@huawei.com> Wed, 08 January 2014 01:40 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 A71C81AE285 for <v6ops@ietfa.amsl.com>; Tue, 7 Jan 2014 17:40:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.738
X-Spam-Level:
X-Spam-Status: No, score=-4.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, 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 81FSyRRaLhmQ for <v6ops@ietfa.amsl.com>; Tue, 7 Jan 2014 17:40:39 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 57C261AE284 for <v6ops@ietf.org>; Tue, 7 Jan 2014 17:40:38 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AZS52842; Wed, 08 Jan 2014 01:40:21 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 8 Jan 2014 01:39:57 +0000
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 8 Jan 2014 01:40:20 +0000
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.72]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Wed, 8 Jan 2014 09:40:14 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Karsten Thomann <karsten_thomann@linfre.de>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] DHCPv6/SLAAC Interaction Operational Guidance-//RE: new draft: draft-liu-v6ops-dhcpv6-slaac-guidance
Thread-Index: AQHPC69aFuMwL0u35UivZdi86dE6hZp6DBWQ
Date: Wed, 08 Jan 2014 01:40:13 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D828258@nkgeml506-mbx.china.huawei.com>
References: <201312251345.rBPDj1u26004@ftpeng-update.cisco.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D827CF1@nkgeml506-mbx.china.huawei.com> <1847363.xquTMZ8SQy@linne>
In-Reply-To: <1847363.xquTMZ8SQy@linne>
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: multipart/alternative; boundary="_000_8AE0F17B87264D4CAC7DE0AA6C406F453D828258nkgeml506mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [v6ops] DHCPv6/SLAAC Interaction Operational Guidance-//RE: new draft: draft-liu-v6ops-dhcpv6-slaac-guidance
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: Wed, 08 Jan 2014 01:40:41 -0000

Hi Karsten,

Thanks a lot for your review and comment.
I think your suggestion is good, we'll revise accordingly in the next version.

Best regards,
Bing

From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Karsten Thomann
Sent: Tuesday, January 07, 2014 9:49 PM
To: v6ops@ietf.org
Subject: Re: [v6ops] DHCPv6/SLAAC Interaction Operational Guidance-//RE: new draft: draft-liu-v6ops-dhcpv6-slaac-guidance


Hi,



I think the draft is useful for everyone who is starting an ipv6 deployment and doesn't know how to handle the flags in the right way.



Notes:

Section 3.1

In my opinion there should be an addional note that DHCPv6 is not anymore a requirement for hosts (RFC6434).

I know it is covered in section 3.2, to make sure all hosts support DHCPv6 but should be also covered as a note at the SLAAC section.





Section 3.3

s/Window 8/ Windows 8/



Best regards

Karsten



Am Montag, 6. Januar 2014, 07:59:39 schrieb Liubing:

> Hi Dear All,

>

> In ietf88 meeting, we discussed draft-liu-bonica-dhcpv6-slaac-problem which

> indicated the hosts' behavior might varied on DHCPv6/SLAAC interaction

> caused by ambiguous standard definition. (The draft was adopted as

> ietf-v6ops-dhcpv6-slaac-problem after the meeting.)

>

> Since the above draft is only filed as a Problem Statement document, as

> discussed in the meeting, the WG decided to initiate another draft to

> provide some operational guidance of what the administrators should do

> given the fact that the host behavior might varied in some situations.

>

> So this is the 00 version. Hope you can read it and comment.

> Your review and comments would be appreciated very much.

>

> And a late happy new year to you all.

>

> Best regards

> Bing

>

> > -----Original Message-----

> > From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of fred@cisco.com<mailto:fred@cisco.com>

> > Sent: Wednesday, December 25, 2013 9:45 PM

> > To: v6ops@ietf.org<mailto:v6ops@ietf.org>

> > Cc: draft-liu-v6ops-dhcpv6-slaac-guidance@tools.ietf.org<mailto:draft-liu-v6ops-dhcpv6-slaac-guidance@tools.ietf.org>

> > Subject: [v6ops] new draft: draft-liu-v6ops-dhcpv6-slaac-guidance

> >

> >

> > A new draft has been posted, at

> > http://tools.ietf.org/html/draft-liu-v6ops-dhcpv6-slaac-guidance. Please

> > take a look at it and comment.

> > _______________________________________________

> > v6ops mailing list

> > v6ops@ietf.org<mailto:v6ops@ietf.org>

> > https://www.ietf.org/mailman/listinfo/v6ops

>

> _______________________________________________

> v6ops mailing list

> v6ops@ietf.org<mailto:v6ops@ietf.org>

> https://www.ietf.org/mailman/listinfo/v6ops