Re: [renum] SLAAC/DHCPv6 addr-conf operational gaps

Sheng Jiang <jiangsheng@huawei.com> Wed, 27 February 2013 06:45 UTC

Return-Path: <jiangsheng@huawei.com>
X-Original-To: renum@ietfa.amsl.com
Delivered-To: renum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B964C21F8733; Tue, 26 Feb 2013 22:45:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.119
X-Spam-Level:
X-Spam-Status: No, score=-6.119 tagged_above=-999 required=5 tests=[AWL=-0.120, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1cBeiONLngYC; Tue, 26 Feb 2013 22:45:11 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 21CB021F8716; Tue, 26 Feb 2013 22:45:10 -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.5-GA FastPath queued) with ESMTP id AOV32857; Wed, 27 Feb 2013 06:45:09 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 27 Feb 2013 06:44:13 +0000
Received: from SZXEML452-HUB.china.huawei.com (10.82.67.195) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 27 Feb 2013 06:45:08 +0000
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.45]) by szxeml452-hub.china.huawei.com ([10.82.67.195]) with mapi id 14.01.0323.007; Wed, 27 Feb 2013 14:44:56 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Liubing (Leo)" <leo.liubing@huawei.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Thread-Topic: SLAAC/DHCPv6 addr-conf operational gaps
Thread-Index: AQHOE/Dp7oY45oFpuUWdZ8xgw4l8cJiNDEUQgAAsV0CAAAivUA==
Date: Wed, 27 Feb 2013 06:44:55 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923A00E1D3@szxeml545-mbx.china.huawei.com>
References: <20130225095210.8863.75094.idtracker@ietfa.amsl.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC03C@nkgeml506-mbx.china.huawei.com> <5D36713D8A4E7348A7E10DF7437A4B923A00E022@szxeml545-mbx.china.huawei.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC86A@nkgeml506-mbx.china.huawei.com>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC86A@nkgeml506-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.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] SLAAC/DHCPv6 addr-conf operational gaps
X-BeenThere: renum@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Renumbering discussion mailing list." <renum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/renum>, <mailto:renum-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/renum>
List-Post: <mailto:renum@ietf.org>
List-Help: <mailto:renum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/renum>, <mailto:renum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 06:45:12 -0000

Hi, Bing,

It is better to at least mention the direction of next step - clearly redefine the flag correspondent host behavior in standards.

A couple of more detailed comments: you have used word "gap" several times, while you did not clear describe what gap it is. You have only described issues/problems. Gaps should be something that issue solved if you could fill them. Subsections of Section 3 are problem scenarios. But your subsection titles do not clear express the meaning.

Cheers,

Sheng

>-----Original Message-----
>From: Liubing (Leo)
>Sent: Wednesday, February 27, 2013 2:17 PM
>To: Sheng Jiang; ipv6@ietf.org
>Cc: renum@ietf.org
>Subject: RE: SLAAC/DHCPv6 addr-conf operational gaps
>
>Hi, Sheng
>
>Thanks for your comments.
>This is the first step, to see if there is consensus of agreeing the problems
>should be fixed in current standard. If so, we'll submit a draft to fix the
>ambiguous issue.
>
>B.R.
>Bing
>
>
>> -----Original Message-----
>> From: Sheng Jiang
>> Sent: Wednesday, February 27, 2013 11:37 AM
>> To: Liubing (Leo); ipv6@ietf.org
>> Cc: renum@ietf.org
>> Subject: RE: SLAAC/DHCPv6 addr-conf operational gaps
>>
>> This has been a historic issue. Although there was discussions several times,
>> the specification still remain ambiguous. The differences in OS
>> implementations are good proof that we need to do something in IETF.
>>
>> This document has well described the current standard status and reality
>> operational issues. However, for me, this document fails to suggest what
>we
>> may do to fix this issue, neither in the gap section or as conclusion. It is
>clear
>> that part of RFC4862 needs to be updated to make the configuration
>> behavior clear and consistent. For that, this document fails to give a feasible
>> proposal. Maybe, the authors has saved that for another follow up standard
>> track document.
>>
>> Best regards,
>>
>> Sheng
>>
>> >-----Original Message-----
>> >From: renum-bounces@ietf.org [mailto:renum-bounces@ietf.org] On
>> Behalf
>> >Of Liubing (Leo)
>> >Sent: Tuesday, February 26, 2013 3:14 PM
>> >To: ipv6@ietf.org; v6ops@ietf.org
>> >Cc: renum@ietf.org
>> >Subject: [renum] SLAAC/DHCPv6 addr-conf operational gaps
>> >
>> >Hi, 6man & v6ops
>> >
>> >We submitted a new draft to discuss the SLAAC/DHCPv6 interaction gaps.
>> >
>> >As we know there are several flags in RA messages regarding with the host
>> >configuration behavior, which are A (Autonomous) flag, M (Managed) flag,
>> >and O (Otherconfig) flag.
>> >For some reason, the host behavior of interpreting the flags is ambiguous
>in
>> >the standard (mainly RFC4862). I presented a draft discussing M flag
>> behavior
>> >in 6man @ietf84, and there were some feedbacks arguing the same issue.
>> >This draft analyzed all the three flags, and provided test result of current
>> >implementations, it showed the behavior of different mainstream desktop
>> >OSes have varied. The ambiguous and variation might cause operational
>> >problems, such as renumbering (used to discuss in 6renum WG and been
>> >documented in the WG drafts), cold start problem, and management
>> >gaps .etc.
>> >
>> >Your review and comments would be appreciated very much.
>> >
>> >All the best,
>> >Bing
>> >
>> >> -----Original Message-----
>> >> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
>> >> Sent: Monday, February 25, 2013 5:52 PM
>> >> To: Liubing (Leo)
>> >> Cc: rbonica@juniper.net
>> >> Subject: New Version Notification for
>> >> draft-liu-bonica-dhcpv6-slaac-problem-01.txt
>> >>
>> >>
>> >> A new version of I-D, draft-liu-bonica-dhcpv6-slaac-problem-01.txt
>> >> has been successfully submitted by Bing Liu and posted to the
>> >> IETF repository.
>> >>
>> >> Filename:	 draft-liu-bonica-dhcpv6-slaac-problem
>> >> Revision:	 01
>> >> Title:		 DHCPv6/SLAAC Address Configuration Interaction
>Problem
>> >> Statement
>> >> Creation date:	 2013-02-25
>> >> Group:		 Individual Submission
>> >> Number of pages: 12
>> >> URL:
>> >>
>> http://www.ietf.org/internet-drafts/draft-liu-bonica-dhcpv6-slaac-problem-
>> >> 01.txt
>> >> Status:
>> >> http://datatracker.ietf.org/doc/draft-liu-bonica-dhcpv6-slaac-problem
>> >> Htmlized:
>> >> http://tools.ietf.org/html/draft-liu-bonica-dhcpv6-slaac-problem-01
>> >> Diff:
>> >>
>> http://www.ietf.org/rfcdiff?url2=draft-liu-bonica-dhcpv6-slaac-problem-01
>> >>
>> >> Abstract:
>> >>    This document analyzes the host behavior of DHCPv6/SLAAC
>> interaction
>> >>    issue. It reviews the standard definition of the host behaviors and
>> >>    provides the test results of current mainstream implementations.
>> Some
>> >>    potential operational gaps of the interaction are also described.
>> >>
>> >>
>> >>
>> >>
>> >> The IETF Secretariat
>> >
>> >_______________________________________________
>> >renum mailing list
>> >renum@ietf.org
>> >https://www.ietf.org/mailman/listinfo/renum