Clearing the ambiguity in DHCPv6/SLAAC interaction-//FW: New Version Notification for draft-liu-6man-dhcpv6-slaac-implementation-guide-00.txt

"Liubing (Leo)" <leo.liubing@huawei.com> Mon, 24 February 2014 09:57 UTC

From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: IPv6 IPv6 List <ipv6@ietf.org>
Subject: Clearing the ambiguity in DHCPv6/SLAAC interaction-//FW: New Version Notification for draft-liu-6man-dhcpv6-slaac-implementation-guide-00.txt
Thread-Topic: Clearing the ambiguity in DHCPv6/SLAAC interaction-//FW: New Version Notification for draft-liu-6man-dhcpv6-slaac-implementation-guide-00.txt
Thread-Index: AQHPKWzOhXnu5rFIOU+zjAYPxfhpwJrEKvzQ
Date: Mon, 24 Feb 2014 09:57:20 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D8535C2@nkgeml506-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/AzpVOzM87rLQ-e4_sqxvSVtNR8s
Precedence: list

Hi Dear all,

We've discussed the DHCPv6/SLAAC address-config problems in 6man a couple of times before. 
In summary, the problem is regarding with the ambiguity on interpreting the M flag and O flag in ND messages. Different operating systems' behavior has varied on interpreting the flags, especially when flags are in transition.

In last ietf, the draft discussing the issues was adopted by v6ops to be a problem statement document (draft-ietf-v6ops-dhcpv6-slaac-problem).
People from OPS area agreed that the problems need to be solved, and suggested us to initial another work in 6man to discuss how to deal with the issues. 

So below is just the draft, it is to specify the proper behavior when the hosts interpreting the relevant flags (A flag, M flag and O flag) in different states.

Please have a review, and comment whether you agree the approaches.
And we're open to discussing other proposals to clear the ambiguity (e.g. revising the relevant specification in RFC4861/4862), so please feel free to comment.

Many thanks!

Best regards,
Bing


-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Friday, February 14, 2014 6:09 PM
To: Liubing (Leo); Ron Bonica; Liubing (Leo); Ron Bonica
Subject: New Version Notification for draft-liu-6man-dhcpv6-slaac-implementation-guide-00.txt


A new version of I-D, draft-liu-6man-dhcpv6-slaac-implementation-guide-00.txt
has been successfully submitted by Bing Liu and posted to the IETF repository.

Name:		draft-liu-6man-dhcpv6-slaac-implementation-guide
Revision:	00
Title:		DHCPv6/SLAAC Interaction Implementation Guidance
Document date:	2014-02-14
Group:		Individual Submission
Pages:		6
URL:            http://www.ietf.org/internet-drafts/draft-liu-6man-dhcpv6-slaac-implementation-guide-00.txt
Status:         https://datatracker.ietf.org/doc/draft-liu-6man-dhcpv6-slaac-implementation-guide/
Htmlized:       http://tools.ietf.org/html/draft-liu-6man-dhcpv6-slaac-implementation-guide-00


Abstract:
   ND and DHCPv6 protocols could have some interaction on address
   provisioning with the A, M, and O flags defined in ND protocol. But
   the relevant standard definitions of the flags contain ambiguity, so
   that current implementations in operating systems have varied on
   interpreting the flags. The variation might impact real network
   operations, so this document aims to provide some guidance on what
   should be the proper implementation on the interaction behavior.



                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

Clearing the ambiguity in DHCPv6/SLAAC interactio… Liubing (Leo)
Re: Clearing the ambiguity in DHCPv6/SLAAC intera… Mark ZZZ Smith
Re: Clearing the ambiguity in DHCPv6/SLAAC intera… Erik Nordmark