
From tjc@ecs.soton.ac.uk  Wed Feb 13 06:43:48 2013
Return-Path: <tjc@ecs.soton.ac.uk>
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 1EFA121F8721 for <renum@ietfa.amsl.com>; Wed, 13 Feb 2013 06:43:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PGtrtWN3J2tG for <renum@ietfa.amsl.com>; Wed, 13 Feb 2013 06:43:47 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 22B1F21F8753 for <renum@ietf.org>; Wed, 13 Feb 2013 06:43:43 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r1DEhe84018938 for <renum@ietf.org>; Wed, 13 Feb 2013 14:43:40 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r1DEhe84018938
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1360766620; bh=KC5T8tuQYLlhYZAI+bIFdvr7FS8=; h=From:Subject:Date:To:Mime-Version:References; b=eDIAUptQBU6vx7PExOyR+Q95R3qvUTl37wtQzxGJHY5s3UTuq60FkRP7jiEw+Bpcs mLkRfD33sJItG7Vk+Q6MVJI1dhx8YoFRW6h8he6w4J37mc7zNHnQ0aFKAD8RjgfLUS KVt+HG1Wa1t7onwnqS/424d3KiZdyxPzz7Q9Ju60=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p1CEhe0430629412Bw ret-id none; Wed, 13 Feb 2013 14:43:40 +0000
Received: from tjc-vpn.ecs.soton.ac.uk (tjc-vpn.ecs.soton.ac.uk [152.78.236.241]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r1DEhbM3032538 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <renum@ietf.org>; Wed, 13 Feb 2013 14:43:37 GMT
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_75ADFF90-8125-4AEE-8130-66F2182825EF"
Message-ID: <EMEW3|dbee3b74fab574478935d154a82ee4e3p1CEhe03tjc|ecs.soton.ac.uk|22BA65D5-0785-4516-8980-7AD082DC689E@ecs.soton.ac.uk>
Date: Wed, 13 Feb 2013 14:43:36 +0000
To: "renum@ietf.org" <renum@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p1CEhe043062941200; tid=p1CEhe0430629412Bw; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
References: <22BA65D5-0785-4516-8980-7AD082DC689E@ecs.soton.ac.uk>
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r1DEhe84018938
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: [renum] 6renum status
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, 13 Feb 2013 14:43:48 -0000

--Apple-Mail=_75ADFF90-8125-4AEE-8130-66F2182825EF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

Just a quick email to confirm there is no 6renum meeting in Orlando.

The three WG drafts are passing through the IESG. I believe the status =
is that=20
http://tools.ietf.org/html/draft-ietf-6renum-enterprise-06
and
http://tools.ietf.org/html/draft-ietf-6renum-static-problem-03
are now with the RFC Editor, though the tracker shows the latter as with =
the IESG.

The third document=20
http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-05
is currently under IESG review.

Brian's notes on the next steps remain documented in
http://tools.ietf.org/html/draft-carpenter-6renum-next-steps-00

It's important that some momentum continues with the items in the next =
steps text.

Tim=

--Apple-Mail=_75ADFF90-8125-4AEE-8130-66F2182825EF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Hi,<div><br></div><div>Just a quick email to confirm there is no =
6renum meeting in Orlando.</div><div><br></div><div>The three WG drafts =
are passing through the IESG. I believe the status is =
that&nbsp;</div><div><a =
href=3D"http://tools.ietf.org/html/draft-ietf-6renum-enterprise-06">http:/=
/tools.ietf.org/html/draft-ietf-6renum-enterprise-06</a></div><div>and</di=
v><div><a =
href=3D"http://tools.ietf.org/html/draft-ietf-6renum-static-problem-03">ht=
tp://tools.ietf.org/html/draft-ietf-6renum-static-problem-03</a></div><div=
>are now with the RFC Editor, though the tracker shows the latter as =
with the IESG.</div><div><br></div><div>The third =
document&nbsp;</div><div><a =
href=3D"http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-05">http=
://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-05</a></div><div>is =
currently under IESG review.</div><div><br></div><div>Brian's notes on =
the next steps remain documented in</div><div><a =
href=3D"http://tools.ietf.org/html/draft-carpenter-6renum-next-steps-00">h=
ttp://tools.ietf.org/html/draft-carpenter-6renum-next-steps-00</a></div><d=
iv><br></div><div>It's important that some momentum continues with the =
items in the next steps =
text.</div><div><br></div><div>Tim</div></body></html>=

--Apple-Mail=_75ADFF90-8125-4AEE-8130-66F2182825EF--

From joelja@bogus.com  Thu Feb 21 21:01:56 2013
Return-Path: <joelja@bogus.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 36CE521F8ECD for <renum@ietfa.amsl.com>; Thu, 21 Feb 2013 21:01:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.485
X-Spam-Level: 
X-Spam-Status: No, score=-102.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 r9CQXsm4ceHH for <renum@ietfa.amsl.com>; Thu, 21 Feb 2013 21:01:55 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id AA84E21F8ECC for <renum@ietf.org>; Thu, 21 Feb 2013 21:01:55 -0800 (PST)
Received: from joels-MacBook-Air.local (c-24-5-127-59.hsd1.ca.comcast.net [24.5.127.59]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r1M51r02049533 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for <renum@ietf.org>; Fri, 22 Feb 2013 05:01:54 GMT (envelope-from joelja@bogus.com)
Message-ID: <5126FBBC.2000704@bogus.com>
Date: Thu, 21 Feb 2013 21:01:48 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: renum@ietf.org
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DA094@nkgeml506-mbx.china.huawei.com> <2CF4CB03E2AA464BA0982EC92A02CE2501EF60E0@BY2PRD0512MB653.namprd05.prod.outlook.com>
In-Reply-To: <2CF4CB03E2AA464BA0982EC92A02CE2501EF60E0@BY2PRD0512MB653.namprd05.prod.outlook.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 22 Feb 2013 05:01:54 +0000 (UTC)
Subject: [renum] AD review draft-ietf-6renum-gap-analysis-05
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: Fri, 22 Feb 2013 05:01:56 -0000

Folks,

I took a look at

http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-05

overall I think it's fairly well put-together document.

A couple things,

While it's certainly readable, a proofreader would probably tighten up 
the language a bit. There are several sentences in in 5.2 for example 
that would benefit from the addition of a preposition in strategic 
locations.

While multihoming is mentioned several times, the necessity of engaging 
in source routing or some other mechanism, e.g. logical VRFs per PA 
prefix in order to preclude black-holing of traffic while multihoming or 
while both prefixes are valid is not as far as I can tell and that seems 
to be a missing piece of the router renumbering gap analysis.

I see some discussion on the list that post-dates the latest revision 
titled Late gap in the gap analysis. Has that been resolved to the 
satisfaction of the WG?

Thanks
Joel

From brian.e.carpenter@gmail.com  Fri Feb 22 00:08:21 2013
Return-Path: <brian.e.carpenter@gmail.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 47AED21F8F5A for <renum@ietfa.amsl.com>; Fri, 22 Feb 2013 00:08:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.14
X-Spam-Level: 
X-Spam-Status: No, score=-101.14 tagged_above=-999 required=5 tests=[AWL=0.551, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 Kg0ZTBr7dlUT for <renum@ietfa.amsl.com>; Fri, 22 Feb 2013 00:08:20 -0800 (PST)
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by ietfa.amsl.com (Postfix) with ESMTP id 8EDC221F8F59 for <renum@ietf.org>; Fri, 22 Feb 2013 00:08:20 -0800 (PST)
Received: by mail-wi0-f180.google.com with SMTP id hi8so379935wib.7 for <renum@ietf.org>; Fri, 22 Feb 2013 00:08:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=nN/uqgY+rEEuX8GKpNaTw4gWWSoZO9xICrV4MNDbNOA=; b=dlBcmj4toxqCcJj6Xoy7B7JsFAgTTo/rdehXZ4L82qi7zxhlYoeVzObggLezt5sIQB BTsELYxmisO7PbVaQ3kzeGMGUMf5G++e0wwQ4zQXFrs7Kr5c/jqd5wrXCBQFxKYnU7yf GsOTZMYGeZDdaHxYqXnOPThJsjOoxw9KqMO6nrOcnEVq9LSbk7Pc/gCWzGIVezz9nfjm ucjyRk6uiHtMcYoiLtg1YWY7gr2jalspgHA8uNyjJm/S/xke8+i0J983HHJW6XuV2v8B bHt3+x4imLu/TaSpM2jtuuk+8f7SlhagH+TFHJHgvXKC/LnngYAUKAqLpTqlCa4MRwdR lq9A==
X-Received: by 10.180.79.133 with SMTP id j5mr1474936wix.27.1361520499409; Fri, 22 Feb 2013 00:08:19 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-217-222.as13285.net. [2.102.217.222]) by mx.google.com with ESMTPS id bs6sm1980324wib.4.2013.02.22.00.08.18 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 22 Feb 2013 00:08:18 -0800 (PST)
Message-ID: <51272780.1050701@gmail.com>
Date: Fri, 22 Feb 2013 08:08:32 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DA094@nkgeml506-mbx.china.huawei.com>	<2CF4CB03E2AA464BA0982EC92A02CE2501EF60E0@BY2PRD0512MB653.namprd05.prod.outlook.com> <5126FBBC.2000704@bogus.com>
In-Reply-To: <5126FBBC.2000704@bogus.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: renum@ietf.org
Subject: Re: [renum] AD review draft-ietf-6renum-gap-analysis-05
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: Fri, 22 Feb 2013 08:08:21 -0000

Hi Joel,

Thanks for the review.

On 22/02/2013 05:01, joel jaeggli wrote:
> Folks,
> 
> I took a look at
> 
> http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-05
> 
> overall I think it's fairly well put-together document.
> 
> A couple things,
> 
> While it's certainly readable, a proofreader would probably tighten up
> the language a bit. There are several sentences in in 5.2 for example
> that would benefit from the addition of a preposition in strategic
> locations.

Yes, or we could do that after IETF Last Call, as you prefer.

> While multihoming is mentioned several times, the necessity of engaging
> in source routing or some other mechanism, e.g. logical VRFs per PA
> prefix in order to preclude black-holing of traffic while multihoming or
> while both prefixes are valid is not as far as I can tell and that seems
> to be a missing piece of the router renumbering gap analysis.
> 
> I see some discussion on the list that post-dates the latest revision
> titled Late gap in the gap analysis. Has that been resolved to the
> satisfaction of the WG?

The concrete suggestion was s/may/will/ in the following:

>    7.3. Renumbering Monitoring
>    While treating renumbering as a network event, mechanisms to monitor
>    the renumbering process may be needed.

    Brian

From joelja@bogus.com  Fri Feb 22 00:24:20 2013
Return-Path: <joelja@bogus.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 0A3E321F8F45 for <renum@ietfa.amsl.com>; Fri, 22 Feb 2013 00:24:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.491
X-Spam-Level: 
X-Spam-Status: No, score=-102.491 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 EXOb3A7I7f0v for <renum@ietfa.amsl.com>; Fri, 22 Feb 2013 00:24:19 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 85AE321F87A5 for <renum@ietf.org>; Fri, 22 Feb 2013 00:24:19 -0800 (PST)
Received: from joels-MacBook-Air.local (c-24-5-127-59.hsd1.ca.comcast.net [24.5.127.59]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r1M8ODwo052131 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 22 Feb 2013 08:24:14 GMT (envelope-from joelja@bogus.com)
Message-ID: <51272B28.3050807@bogus.com>
Date: Fri, 22 Feb 2013 00:24:08 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DA094@nkgeml506-mbx.china.huawei.com>	<2CF4CB03E2AA464BA0982EC92A02CE2501EF60E0@BY2PRD0512MB653.namprd05.prod.outlook.com> <5126FBBC.2000704@bogus.com> <51272780.1050701@gmail.com>
In-Reply-To: <51272780.1050701@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 22 Feb 2013 08:24:14 +0000 (UTC)
Cc: renum@ietf.org
Subject: Re: [renum] AD review draft-ietf-6renum-gap-analysis-05
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: Fri, 22 Feb 2013 08:24:20 -0000

Got it, thanks.

On 2/22/13 12:08 AM, Brian E Carpenter wrote:
> Hi Joel,
>
> Thanks for the review.
>
> On 22/02/2013 05:01, joel jaeggli wrote:
>> Folks,
>>
>> I took a look at
>>
>> http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-05
>>
>> overall I think it's fairly well put-together document.
>>
>> A couple things,
>>
>> While it's certainly readable, a proofreader would probably tighten up
>> the language a bit. There are several sentences in in 5.2 for example
>> that would benefit from the addition of a preposition in strategic
>> locations.
> Yes, or we could do that after IETF Last Call, as you prefer.
>
>> While multihoming is mentioned several times, the necessity of engaging
>> in source routing or some other mechanism, e.g. logical VRFs per PA
>> prefix in order to preclude black-holing of traffic while multihoming or
>> while both prefixes are valid is not as far as I can tell and that seems
>> to be a missing piece of the router renumbering gap analysis.
>>
>> I see some discussion on the list that post-dates the latest revision
>> titled Late gap in the gap analysis. Has that been resolved to the
>> satisfaction of the WG?
> The concrete suggestion was s/may/will/ in the following:
>
>>     7.3. Renumbering Monitoring
>>     While treating renumbering as a network event, mechanisms to monitor
>>     the renumbering process may be needed.
>      Brian
>


From joelja@bogus.com  Mon Feb 25 15:06:18 2013
Return-Path: <joelja@bogus.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 D4C9A21E8119 for <renum@ietfa.amsl.com>; Mon, 25 Feb 2013 15:06:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 t9F9JZ6LbbaQ for <renum@ietfa.amsl.com>; Mon, 25 Feb 2013 15:06:18 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 6916021E80FE for <renum@ietf.org>; Mon, 25 Feb 2013 15:06:18 -0800 (PST)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r1PN6FD0008528 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 25 Feb 2013 23:06:16 GMT (envelope-from joelja@bogus.com)
Message-ID: <512BEE6D.3040305@bogus.com>
Date: Mon, 25 Feb 2013 15:06:21 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DA094@nkgeml506-mbx.china.huawei.com>	<2CF4CB03E2AA464BA0982EC92A02CE2501EF60E0@BY2PRD0512MB653.namprd05.prod.outlook.com> <5126FBBC.2000704@bogus.com> <51272780.1050701@gmail.com> <51272B28.3050807@bogus.com>
In-Reply-To: <51272B28.3050807@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 25 Feb 2013 23:06:16 +0000 (UTC)
Cc: renum@ietf.org
Subject: Re: [renum] AD review draft-ietf-6renum-gap-analysis-05
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: Mon, 25 Feb 2013 23:06:19 -0000

Given that I don't have control yet, and we're 12 days from the meeting 
I'll initiate IETF LC on this after the coming meeting.

thanks
joel

On 2/22/13 12:24 AM, joel jaeggli wrote:
> Got it, thanks.
>
> On 2/22/13 12:08 AM, Brian E Carpenter wrote:
>> Hi Joel,
>>
>> Thanks for the review.
>>
>> On 22/02/2013 05:01, joel jaeggli wrote:
>>> Folks,
>>>
>>> I took a look at
>>>
>>> http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-05
>>>
>>> overall I think it's fairly well put-together document.
>>>
>>> A couple things,
>>>
>>> While it's certainly readable, a proofreader would probably tighten up
>>> the language a bit. There are several sentences in in 5.2 for example
>>> that would benefit from the addition of a preposition in strategic
>>> locations.
>> Yes, or we could do that after IETF Last Call, as you prefer.
>>
>>> While multihoming is mentioned several times, the necessity of engaging
>>> in source routing or some other mechanism, e.g. logical VRFs per PA
>>> prefix in order to preclude black-holing of traffic while 
>>> multihoming or
>>> while both prefixes are valid is not as far as I can tell and that 
>>> seems
>>> to be a missing piece of the router renumbering gap analysis.
>>>
>>> I see some discussion on the list that post-dates the latest revision
>>> titled Late gap in the gap analysis. Has that been resolved to the
>>> satisfaction of the WG?
>> The concrete suggestion was s/may/will/ in the following:
>>
>>>     7.3. Renumbering Monitoring
>>>     While treating renumbering as a network event, mechanisms to 
>>> monitor
>>>     the renumbering process may be needed.
>>      Brian
>>
>
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum
>


From leo.liubing@huawei.com  Mon Feb 25 23:14:44 2013
Return-Path: <leo.liubing@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 0C46621F9668; Mon, 25 Feb 2013 23:14:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.17
X-Spam-Level: 
X-Spam-Status: No, score=-6.17 tagged_above=-999 required=5 tests=[AWL=-0.171,  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 8JcVsdbBpbf1; Mon, 25 Feb 2013 23:14:42 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1169E21F960B; Mon, 25 Feb 2013 23:14:41 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQB42294; Tue, 26 Feb 2013 07:14:31 +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; Tue, 26 Feb 2013 07:13:38 +0000
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 26 Feb 2013 07:14:30 +0000
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.101]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.01.0323.007; Tue, 26 Feb 2013 15:14:27 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: SLAAC/DHCPv6 addr-conf operational gaps
Thread-Index: AQHOE/Dp7oY45oFpuUWdZ8xgw4l8cA==
Date: Tue, 26 Feb 2013 07:14:27 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC03C@nkgeml506-mbx.china.huawei.com>
References: <20130225095210.8863.75094.idtracker@ietfa.amsl.com>
In-Reply-To: <20130225095210.8863.75094.idtracker@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
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: [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: Tue, 26 Feb 2013 07:14:44 -0000

SGksIDZtYW4gJiB2Nm9wcw0KDQpXZSBzdWJtaXR0ZWQgYSBuZXcgZHJhZnQgdG8gZGlzY3VzcyB0
aGUgU0xBQUMvREhDUHY2IGludGVyYWN0aW9uIGdhcHMuDQoNCkFzIHdlIGtub3cgdGhlcmUgYXJl
IHNldmVyYWwgZmxhZ3MgaW4gUkEgbWVzc2FnZXMgcmVnYXJkaW5nIHdpdGggdGhlIGhvc3QgY29u
ZmlndXJhdGlvbiBiZWhhdmlvciwgd2hpY2ggYXJlIEEgKEF1dG9ub21vdXMpIGZsYWcsIE0gKE1h
bmFnZWQpIGZsYWcsIGFuZCBPIChPdGhlcmNvbmZpZykgZmxhZy4NCkZvciBzb21lIHJlYXNvbiwg
dGhlIGhvc3QgYmVoYXZpb3Igb2YgaW50ZXJwcmV0aW5nIHRoZSBmbGFncyBpcyBhbWJpZ3VvdXMg
aW4gdGhlIHN0YW5kYXJkIChtYWlubHkgUkZDNDg2MikuIEkgcHJlc2VudGVkIGEgZHJhZnQgZGlz
Y3Vzc2luZyBNIGZsYWcgYmVoYXZpb3IgaW4gNm1hbiBAaWV0Zjg0LCBhbmQgdGhlcmUgd2VyZSBz
b21lIGZlZWRiYWNrcyBhcmd1aW5nIHRoZSBzYW1lIGlzc3VlLiBUaGlzIGRyYWZ0IGFuYWx5emVk
IGFsbCB0aGUgdGhyZWUgZmxhZ3MsIGFuZCBwcm92aWRlZCB0ZXN0IHJlc3VsdCBvZiBjdXJyZW50
IGltcGxlbWVudGF0aW9ucywgaXQgc2hvd2VkIHRoZSBiZWhhdmlvciBvZiBkaWZmZXJlbnQgbWFp
bnN0cmVhbSBkZXNrdG9wIE9TZXMgaGF2ZSB2YXJpZWQuIFRoZSBhbWJpZ3VvdXMgYW5kIHZhcmlh
dGlvbiBtaWdodCBjYXVzZSBvcGVyYXRpb25hbCBwcm9ibGVtcywgc3VjaCBhcyByZW51bWJlcmlu
ZyAodXNlZCB0byBkaXNjdXNzIGluIDZyZW51bSBXRyBhbmQgYmVlbiBkb2N1bWVudGVkIGluIHRo
ZSBXRyBkcmFmdHMpLCBjb2xkIHN0YXJ0IHByb2JsZW0sIGFuZCBtYW5hZ2VtZW50IGdhcHMgLmV0
Yy4NCg0KWW91ciByZXZpZXcgYW5kIGNvbW1lbnRzIHdvdWxkIGJlIGFwcHJlY2lhdGVkIHZlcnkg
bXVjaC4gDQoNCkFsbCB0aGUgYmVzdCwNCkJpbmcNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KPiBGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5ldC1k
cmFmdHNAaWV0Zi5vcmddDQo+IFNlbnQ6IE1vbmRheSwgRmVicnVhcnkgMjUsIDIwMTMgNTo1MiBQ
TQ0KPiBUbzogTGl1YmluZyAoTGVvKQ0KPiBDYzogcmJvbmljYUBqdW5pcGVyLm5ldA0KPiBTdWJq
ZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yDQo+IGRyYWZ0LWxpdS1ib25pY2EtZGhj
cHY2LXNsYWFjLXByb2JsZW0tMDEudHh0DQo+IA0KPiANCj4gQSBuZXcgdmVyc2lvbiBvZiBJLUQs
IGRyYWZ0LWxpdS1ib25pY2EtZGhjcHY2LXNsYWFjLXByb2JsZW0tMDEudHh0DQo+IGhhcyBiZWVu
IHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgQmluZyBMaXUgYW5kIHBvc3RlZCB0byB0aGUNCj4g
SUVURiByZXBvc2l0b3J5Lg0KPiANCj4gRmlsZW5hbWU6CSBkcmFmdC1saXUtYm9uaWNhLWRoY3B2
Ni1zbGFhYy1wcm9ibGVtDQo+IFJldmlzaW9uOgkgMDENCj4gVGl0bGU6CQkgREhDUHY2L1NMQUFD
IEFkZHJlc3MgQ29uZmlndXJhdGlvbiBJbnRlcmFjdGlvbiBQcm9ibGVtDQo+IFN0YXRlbWVudA0K
PiBDcmVhdGlvbiBkYXRlOgkgMjAxMy0wMi0yNQ0KPiBHcm91cDoJCSBJbmRpdmlkdWFsIFN1Ym1p
c3Npb24NCj4gTnVtYmVyIG9mIHBhZ2VzOiAxMg0KPiBVUkw6DQo+IGh0dHA6Ly93d3cuaWV0Zi5v
cmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWxpdS1ib25pY2EtZGhjcHY2LXNsYWFjLXByb2JsZW0t
DQo+IDAxLnR4dA0KPiBTdGF0dXM6DQo+IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2Mv
ZHJhZnQtbGl1LWJvbmljYS1kaGNwdjYtc2xhYWMtcHJvYmxlbQ0KPiBIdG1saXplZDoNCj4gaHR0
cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtbGl1LWJvbmljYS1kaGNwdjYtc2xhYWMtcHJv
YmxlbS0wMQ0KPiBEaWZmOg0KPiBodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFm
dC1saXUtYm9uaWNhLWRoY3B2Ni1zbGFhYy1wcm9ibGVtLTAxDQo+IA0KPiBBYnN0cmFjdDoNCj4g
ICAgVGhpcyBkb2N1bWVudCBhbmFseXplcyB0aGUgaG9zdCBiZWhhdmlvciBvZiBESENQdjYvU0xB
QUMgaW50ZXJhY3Rpb24NCj4gICAgaXNzdWUuIEl0IHJldmlld3MgdGhlIHN0YW5kYXJkIGRlZmlu
aXRpb24gb2YgdGhlIGhvc3QgYmVoYXZpb3JzIGFuZA0KPiAgICBwcm92aWRlcyB0aGUgdGVzdCBy
ZXN1bHRzIG9mIGN1cnJlbnQgbWFpbnN0cmVhbSBpbXBsZW1lbnRhdGlvbnMuIFNvbWUNCj4gICAg
cG90ZW50aWFsIG9wZXJhdGlvbmFsIGdhcHMgb2YgdGhlIGludGVyYWN0aW9uIGFyZSBhbHNvIGRl
c2NyaWJlZC4NCj4gDQo+IA0KPiANCj4gDQo+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQoNCg==

From victor.kuarsingh@gmail.com  Tue Feb 26 05:28:30 2013
Return-Path: <victor.kuarsingh@gmail.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 EE24821F8942; Tue, 26 Feb 2013 05:28:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.164
X-Spam-Level: 
X-Spam-Status: No, score=-0.164 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1]
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 Newtwd06mdXF; Tue, 26 Feb 2013 05:28:29 -0800 (PST)
Received: from mail-ia0-x231.google.com (mail-ia0-x231.google.com [IPv6:2607:f8b0:4001:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 3B56E21F89A5; Tue, 26 Feb 2013 05:28:29 -0800 (PST)
Received: by mail-ia0-f177.google.com with SMTP id o25so3461359iad.22 for <multiple recipients>; Tue, 26 Feb 2013 05:28:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:user-agent:date:subject:from:to:cc:message-id :thread-topic:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=iae8H5wdyiqptN1wbjXJHXdtE3oScMSMnXurp5fvnW8=; b=z/oNzNGI/y9cEc//QTyHAfAvyOfuWFmsMmBBv+hdp75reyIZnIdmpcLLLGZKbE6Ucm +ZT0nL7rEmNcaOk/j35tZj7uh8CSURkBAy+BP+sWEngEd/Yct3lik7k6EZSiNL61WGs5 NVOEbq7QK2E7FFCnyWbFHQ8hmBzaaGzoxa/Dj2kOsf33vDUqW5K1AXBs+KfEfvoCJELH JLYxer+jWt+Pe3r9jCvGUGHIvx/VYaY8IpRVY7sRvlE1bXp2KCXXTuZ4lSTAWmVKxi6W 7rsGd7B7QG5iVLCa+uhlwkzGQ9XhCVAlIvM92NCwhjc3r1CrPrzp8VCH66EXXr2vK8em DBXg==
X-Received: by 10.50.42.168 with SMTP id p8mr5446698igl.106.1361885308791; Tue, 26 Feb 2013 05:28:28 -0800 (PST)
Received: from [192.168.100.33] ([67.224.83.162]) by mx.google.com with ESMTPS id ur12sm334146igb.8.2013.02.26.05.28.26 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 26 Feb 2013 05:28:27 -0800 (PST)
User-Agent: Microsoft-MacOutlook/14.10.0.110310
Date: Tue, 26 Feb 2013 08:28:22 -0500
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: "Liubing (Leo)" <leo.liubing@huawei.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <CD522107.408ED%victor.kuarsingh@gmail.com>
Thread-Topic: SLAAC/DHCPv6 addr-conf operational gaps
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC03C@nkgeml506-mbx.china.huawei.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
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: Tue, 26 Feb 2013 13:28:30 -0000

Bing,

I as able to review the draft and agree this needs to be documented and
discussed.  I have had many frustrating nights dealing with my multiple
OSs at home and figuring out what behaviour I was trying to expect when
changing the upstream router's settings (M/O/A).

I think the problem space discussion within the draft should be enough to
have a preliminary discussion in the WG.  I know there have been issues in
the past with various opinions on what the M/O bits (for example) should
or should not be used for - or how authoritative they should be.

If the groups can agree that there is in fact a problem, then I would
agree with Arturo that we can have a constructive follow-up
draft/discussion on the corrective action.

Lets get past step 1 and agree there is an issue (or not); then go down
the more sensitive path of agreeing to the corrective action.

Thanks for putting this together.

Regards,

Victor Kuarsingh



On 2013-02-26 2:14 AM, "Liubing (Leo)" <leo.liubing@huawei.com> wrote:

>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
>
>--------------------------------------------------------------------
>IETF IPv6 working group mailing list
>ipv6@ietf.org
>Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>--------------------------------------------------------------------



From bs7652@att.com  Tue Feb 26 10:06:43 2013
Return-Path: <bs7652@att.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 A947B21F8A54; Tue, 26 Feb 2013 10:06:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.099
X-Spam-Level: 
X-Spam-Status: No, score=-105.099 tagged_above=-999 required=5 tests=[AWL=-1.400, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MANGLED_PRBLMS=2.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 SxrMPFkOp46H; Tue, 26 Feb 2013 10:06:42 -0800 (PST)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) by ietfa.amsl.com (Postfix) with ESMTP id 1747821F886B; Tue, 26 Feb 2013 10:06:42 -0800 (PST)
Received: from unknown [144.160.20.146] (EHLO nbfkord-smmo07.seg.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.15.0-1) with ESMTP id 2b9fc215.53c06940.4288268.00-533.11847790.nbfkord-smmo07.seg.att.com (envelope-from <bs7652@att.com>);  Tue, 26 Feb 2013 18:06:42 +0000 (UTC)
X-MXL-Hash: 512cf9b24a1a8ee4-7de3abe4ef9469d00e2360082cd6e3c605c42217
Received: from unknown [144.160.20.146] (EHLO mlpd194.enaf.sfdc.sbc.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id ea9fc215.0.4288249.00-496.11847726.nbfkord-smmo07.seg.att.com (envelope-from <bs7652@att.com>);  Tue, 26 Feb 2013 18:06:40 +0000 (UTC)
X-MXL-Hash: 512cf9b022ec96b0-34130cba56638fea4099aab599ab43fa530cfdd5
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r1QI6c7i028467; Tue, 26 Feb 2013 13:06:38 -0500
Received: from sflint03.pst.cso.att.com (sflint03.pst.cso.att.com [144.154.234.230]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r1QI6Tnk028206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Feb 2013 13:06:33 -0500
Received: from GAALPA1MSGHUB9E.ITServices.sbc.com (gaalpa1msghub9e.itservices.sbc.com [130.8.36.91]) by sflint03.pst.cso.att.com (RSA Interceptor); Tue, 26 Feb 2013 13:02:16 -0500
Received: from GAALPA1MSGUSR9L.ITServices.sbc.com ([130.8.36.69]) by GAALPA1MSGHUB9E.ITServices.sbc.com ([130.8.36.91]) with mapi id 14.02.0328.009; Tue, 26 Feb 2013 13:02:05 -0500
From: "STARK, BARBARA H" <bs7652@att.com>
To: "Liubing (Leo)" <leo.liubing@huawei.com>, "ipv6@ietf.org" <ipv6@ietf.org>,  "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: SLAAC/DHCPv6 addr-conf operational gaps
Thread-Index: AQHOE/Dp7oY45oFpuUWdZ8xgw4l8cJiMZZ8g
Date: Tue, 26 Feb 2013 18:02:04 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E61130255AE0@GAALPA1MSGUSR9L.ITServices.sbc.com>
References: <20130225095210.8863.75094.idtracker@ietfa.amsl.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC03C@nkgeml506-mbx.china.huawei.com>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC03C@nkgeml506-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.70.174.97]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <bs7652@att.com>
X-SOURCE-IP: [144.160.20.146]
X-AnalysisOut: [v=2.0 cv=Ob0v+GvY c=1 sm=0 a=Qs8R1XBwmid1qBFB/a8mmA==:17 a]
X-AnalysisOut: [=SawaiHsxiTQA:10 a=mjfWdd7OfzUA:10 a=ofMgfj31e3cA:10 a=BLc]
X-AnalysisOut: [eEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP7CpKOAAAA:8 a=XIqpo32R]
X-AnalysisOut: [AAAA:8 a=qIRfQioSgDsA:10 a=48vgC7mUAAAA:8 a=OUXY8nFuAAAA:8]
X-AnalysisOut: [ a=IrhkzyA9JQ-jOgXrGygA:9 a=CjuIK1q_8ugA:10 a=lZB815dzVvQA]
X-AnalysisOut: [:10 a=peF9eE_zjQwA:10 a=_nbaV8ywFon7Z7Y3:21 a=l_Yy1O5uc6Fl]
X-AnalysisOut: [zOYM:21]
X-Mailman-Approved-At: Tue, 26 Feb 2013 10:31:11 -0800
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: Tue, 26 Feb 2013 18:06:43 -0000

This is interesting. Thanks for doing these tests and submitting the result=
s.

When testing the switching behavior, I'm curious for the " SLAAC-only host =
receiving A=3D0&M=3D1 " case as to what you set the Preferred Lifetime to, =
when you set A=3D0. I'm guessing Preferred Lifetime > 0?
Since RFC 4862 states "A preferred address becomes deprecated when its pref=
erred lifetime expires", I would only have expected a host to deprecate a S=
LAAC-obtained address if the RA message set Preferred Lifetime to zero. It =
sounds like the case where the RA is changed from A=3D1 and Preferred Lifet=
ime > 0 to A=3D0 and Preferred Lifetime > 0 is ambiguous. I'm not quite sur=
e what the use case is for separating the A flag and Preferred Lifetime set=
tings. Did you also run the test by changing to A=3D0 and Preferred Lifetim=
e =3D 0? I would hope that there would be consistent behavior in that case.

For the "DHCPv6-only host receiving A=3D1&M=3D0" case, I'm curious as to wh=
ether you also tried sending a DHCPv6 Reconfigure message and forcing the h=
ost to release the DHCPv6-assigned address; and send A=3D1&M=3D0 in an RA d=
irectly after sending the Reconfigure. I'm not sure what the use case is fo=
r trying to force the release or deprecation of a DHCPv6 address via flags =
in an RA message. Once a host has a DHCPv6 address, I would have expected i=
ts subsequent behavior relating to that address and that DHCPv6 server to b=
e governed by RFC 3315. The Linux/MAC behavior appears consistent with what=
 I would have expected. The Windows 7 does not. I'm unaware of even a "hint=
" that suggests RA flags have a role in governing DHCPv6 behavior once RFC =
3315 is in play.
Barbara

> -----Original Message-----
> From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> Liubing (Leo)
> Sent: Tuesday, February 26, 2013 2:14 AM
> To: ipv6@ietf.org; v6ops@ietf.org
> Cc: renum@ietf.org
> Subject: SLAAC/DHCPv6 addr-conf operational gaps
>=20
> Hi, 6man & v6ops
>=20
> We submitted a new draft to discuss the SLAAC/DHCPv6 interaction gaps.
>=20
> 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 beha=
vior
> in 6man @ietf84, and there were some feedbacks arguing the same issue.
> This draft analyzed all the three flags, and provided test result of curr=
ent
> 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.
>=20
> Your review and comments would be appreciated very much.
>=20
> All the best,
> Bing
>=20
> > -----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-prob
> > lem-
> > 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=3Ddraft-liu-bonica-dhcpv6-slaac-proble=
m
> > -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. Som=
e
> >    potential operational gaps of the interaction are also described.
> >
> >
> >
> >
> > The IETF Secretariat
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

From markzzzsmith@yahoo.com.au  Tue Feb 26 12:34:37 2013
Return-Path: <markzzzsmith@yahoo.com.au>
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 60EB121F8920 for <renum@ietfa.amsl.com>; Tue, 26 Feb 2013 12:34:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.349
X-Spam-Level: 
X-Spam-Status: No, score=-1.349 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, J_CHICKENPOX_13=0.6]
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 PpiM72CIkIqc for <renum@ietfa.amsl.com>; Tue, 26 Feb 2013 12:34:34 -0800 (PST)
Received: from nm7-vm1.bullet.mail.bf1.yahoo.com (nm7-vm1.bullet.mail.bf1.yahoo.com [98.139.213.142]) by ietfa.amsl.com (Postfix) with SMTP id 4ADB921F889C for <renum@ietf.org>; Tue, 26 Feb 2013 12:34:34 -0800 (PST)
Received: from [98.139.212.149] by nm7.bullet.mail.bf1.yahoo.com with NNFMP; 26 Feb 2013 20:34:33 -0000
Received: from [98.139.212.249] by tm6.bullet.mail.bf1.yahoo.com with NNFMP; 26 Feb 2013 20:34:33 -0000
Received: from [127.0.0.1] by omp1058.mail.bf1.yahoo.com with NNFMP; 26 Feb 2013 20:34:33 -0000
X-Yahoo-Newman-Property: ymail-5
X-Yahoo-Newman-Id: 734705.225.bm@omp1058.mail.bf1.yahoo.com
Received: (qmail 79426 invoked by uid 60001); 26 Feb 2013 20:34:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1361910873; bh=y6gH6gNPjZdYi+d8xQFSX48JcT3R04YZd4dbpDBnytA=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=19sfM13tdRNw/DhE3RJeK02PIKUvHNIHfTZF/yUCX3hpbNle19/n440hJk8C6u7oiJZgbLFAPZBZ/wrKSD1C0uoCFdudnPkuEtLilxgxz/wDTfLUoGB3ChJHWHcR1ObPZ7DrUsJMsuDoBViWmUaTQCN63P1N7s4tPMyr4I+zDDI=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=LDmFVUuiRsA0/a3S4HrrQryt/SPb9Ac/3cmtGq1WXO3kj+9o2lR9NeMsY9Bs90UY+IjcdcZNc5FXNqC/7ws6vCN0HX6yAM1TUpxaaliXHntTnJnVaRXOFrBWuaQHzXDyIlyNDVfJ4hol9EtCiz3p/KHwU9XW1qE7v1EQ+sGZZBw=;
X-YMail-OSG: BO43t_QVM1mM5KX2avIH5Y.WJ3tCS9ay0Zms5nY0c7aAncp xoe12iQHGKXLAJx4WEzAFX6N4P2pbAN7scj2lCGh1faPZN8Bn1PUSG8.AD78 CzZuKpkthHoXuPKyu3bL8J2kgQEoqkjgtVgCAwveeSi60u7sVk5IieO0nFce Nb2ND3oMDaweJnH.iPCbse8xRn_V.Yn9ZI9MJTSGBNXX3_PpJIAlvAQzssM5 q0vEHxwsMsh.lLoJypL4IL.4Wg9gBgckZXjKtadO9mr58pIiJMSKL89JNokT cySQmyjgDwFeHXSeFudiCm3YcB6Exl1TXbENfncoKBk52VpzPib1taSuAu7t DW3l91VDkX946fOl5fNzzPHzvHFXkM0AEurIAccKbyN.TU8..3wYuf9fOhMi oR6pRnZsfHgFqTyYWcfI4WPkdPbv4Vfm1T_X7lZFmhkJbgCTTGL14I0uBSLW Vb6np.IpknccnLfnv.ywM6C3W2JH0IvebrUn8VdU9oo8XKgeaCcxbmRbZoSo GQd6o7etlWfme8DmQkhp7A23HCooC
Received: from [150.101.221.237] by web142503.mail.bf1.yahoo.com via HTTP; Tue, 26 Feb 2013 12:34:33 PST
X-Rocket-MIMEInfo: 001.001, SGksCgpJJ3ZlIGhhZCBhIHF1aWNrIHJlYWQgdGhvdWdoLCBJJ2xsIHRyeSB0byBkbyBhIHRob3JvdWdoIG9uZSBpbiB0aGUgbmV4dCB3ZWVrIG9yIHNvLgoKVGhhbmtzIGZvciB3cml0aW5nIHRoaXMsIEkndmUgYmVlbiB0aGlua2luZyBhYm91dCBkb2luZyBzb21ldGhpbmcgc2ltaWxhciBvdmVyIHRoZSBsYXN0IGZldyBtb250aHMgc2luY2UsIElJUkMsIEkgaGVhcmQgYWJvdXQgV2luZG93cyA3IGludmFsaWRhdGluZyBJUHY2IGFkZHJlc3NlcyBsZWFybmVkIHZpYSBESENQdjYgd2hlbiBTTEFBQyB3YXMgZW4BMAEBAQE-
X-Mailer: YahooMailWebService/0.8.135.514
References: <20130225095210.8863.75094.idtracker@ietfa.amsl.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC03C@nkgeml506-mbx.china.huawei.com>
Message-ID: <1361910873.78397.YahooMailNeo@web142503.mail.bf1.yahoo.com>
Date: Tue, 26 Feb 2013 12:34:33 -0800 (PST)
From: Mark Smith <markzzzsmith@yahoo.com.au>
To: "Liubing \(Leo\)" <leo.liubing@huawei.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC03C@nkgeml506-mbx.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 26 Feb 2013 12:35:38 -0800
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
Reply-To: Mark Smith <markzzzsmith@yahoo.com.au>
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: Tue, 26 Feb 2013 20:34:37 -0000

Hi,=0A=0AI've had a quick read though, I'll try to do a thorough one in the=
 next week or so.=0A=0AThanks for writing this, I've been thinking about do=
ing something similar over the last few months since, IIRC, I heard about W=
indows 7 invalidating IPv6 addresses learned via DHCPv6 when SLAAC was enab=
led and DHCPv6 was disabled on a link.=0A=0AA few thoughts I've had which m=
ay be useful -=0A=0AFirstly, I came to realise that the mistake being made =
by Windows 7 was the assumption that the aging of the assigned IPv6 address=
es was tightly coupled to the DHCPv6 session state, meaning that if DHCPv6 =
went away, so would the assigned addresses. This is generally the way DHCPv=
4 has worked. However, in IPv6/DHCPv6, it seems the address lifetime values=
 in the IA_NA are not coupled to the T1 and T2 times, so if DHCPv6 goes awa=
y (perhaps because the M bit was switched off in a latter RA), the configur=
ed IPv6 addresses should be left to age out as per their preferred and vali=
d lifetimes.=0A=0AThe other thing I noticed was that the M RA flag and the =
PIO A flags aren't mutually exclusive - I couldn't find any text in RFC4861=
 that says if the M bit is switched on, the PIO A flags must be switched of=
f and vice-versa. So that suggests that the DHCPv6 and SLAAC can co-exist, =
and I think that is quite reasonable if you're transitioning a link from DH=
CPv6 to SLAAC address configuration or vice-versa.=0A=0AThinking about it m=
ore, I came realise that DHCPv6 and SLAAC are _address configuration_ metho=
ds, but are not address aging methods - IPv6 takes care of address aging vi=
a it's preferred and valid aging mechanisms, regardless of the address conf=
iguration method. Static assignment is also just an address configuration m=
ethod, although typically the addresses don't age out, but only because the=
y're normally set to infinity. Perhaps in the future there might be other a=
ddress configuration methods.=0A=0AI didn't seem to be able to find an RFC =
that made it clear that address configuration and address aging are quite s=
eparate, so perhaps this ID could be the one.=0A=0ARegarding this text:=0A=
=0A'For the host behavior, there is an explicit rule in the SLAAC specifica=
tion [RFC4862]: "If the Autonomous flag is not set, silently ignore the Pre=
fix Information option."'=0A=0AI think RFC5942, "IPv6 Subnet Model: The Rel=
ationship between Links and Subnet Prefixes." updates that advice, as the P=
IO option is used to indicates which prefix/range of addresses are on-link,=
 via the PIO O bit, even if the PIO A bit is switched off.=0A=0ABest regard=
s,=0AMark.=0A=0A>________________________________=0A> From: Liubing (Leo) <=
leo.liubing@huawei.com>=0A>To: "ipv6@ietf.org" <ipv6@ietf.org>; "v6ops@ietf=
.org" <v6ops@ietf.org> =0A>Cc: "renum@ietf.org" <renum@ietf.org> =0A>Sent: =
Tuesday, 26 February 2013 6:14 PM=0A>Subject: SLAAC/DHCPv6 addr-conf operat=
ional gaps=0A> =0A>Hi, 6man & v6ops=0A>=0A>We submitted a new draft to disc=
uss the SLAAC/DHCPv6 interaction gaps.=0A>=0A>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.=0A>For=
 some reason, the host behavior of interpreting the flags is ambiguous in t=
he standard (mainly RFC4862). I presented a draft discussing M flag behavio=
r in 6man @ietf84, and there were some feedbacks arguing the same issue. Th=
is draft analyzed all the three flags, and provided test result of current =
implementations, it showed the behavior of different mainstream desktop OSe=
s 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.=0A>=0A>Your r=
eview and comments would be appreciated very much. =0A>=0A>All the best,=0A=
>Bing=0A>=0A>> -----Original Message-----=0A>> From: internet-drafts@ietf.o=
rg [mailto:internet-drafts@ietf.org]=0A>> Sent: Monday, February 25, 2013 5=
:52 PM=0A>> To: Liubing (Leo)=0A>> Cc: rbonica@juniper.net=0A>> Subject: Ne=
w Version Notification for=0A>> draft-liu-bonica-dhcpv6-slaac-problem-01.tx=
t=0A>> =0A>> =0A>> A new version of I-D, draft-liu-bonica-dhcpv6-slaac-prob=
lem-01.txt=0A>> has been successfully submitted by Bing Liu and posted to t=
he=0A>> IETF repository.=0A>> =0A>> Filename:=A0=A0=A0=A0=A0draft-liu-bonic=
a-dhcpv6-slaac-problem=0A>> Revision:=A0=A0=A0=A0=A001=0A>> Title:=A0=A0=A0=
 =A0=A0=A0=A0=A0DHCPv6/SLAAC Address Configuration Interaction Problem=0A>>=
 Statement=0A>> Creation date:=A0=A0=A0=A0=A02013-02-25=0A>> Group:=A0=A0=
=A0 =A0=A0=A0=A0=A0Individual Submission=0A>> Number of pages: 12=0A>> URL:=
=0A>> http://www.ietf.org/internet-drafts/draft-liu-bonica-dhcpv6-slaac-pro=
blem-=0A>> 01.txt=0A>> Status:=0A>> http://datatracker.ietf.org/doc/draft-l=
iu-bonica-dhcpv6-slaac-problem=0A>> Htmlized:=0A>> http://tools.ietf.org/ht=
ml/draft-liu-bonica-dhcpv6-slaac-problem-01=0A>> Diff:=0A>> http://www.ietf=
.org/rfcdiff?url2=3Ddraft-liu-bonica-dhcpv6-slaac-problem-01=0A>> =0A>> Abs=
tract:=0A>>=A0 =A0 This document analyzes the host behavior of DHCPv6/SLAAC=
 interaction=0A>>=A0 =A0 issue. It reviews the standard definition of the h=
ost behaviors and=0A>>=A0 =A0 provides the test results of current mainstre=
am implementations. Some=0A>>=A0 =A0 potential operational gaps of the inte=
raction are also described.=0A>> =0A>> =0A>> =0A>> =0A>> The IETF Secretari=
at=0A>=0A>-----------------------------------------------------------------=
---=0A>IETF IPv6 working group mailing list=0A>ipv6@ietf.org=0A>Administrat=
ive Requests: https://www.ietf.org/mailman/listinfo/ipv6=0A>---------------=
-----------------------------------------------------=0A>=0A>=0A>

From leo.liubing@huawei.com  Tue Feb 26 19:07:12 2013
Return-Path: <leo.liubing@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 ED03E21F8673; Tue, 26 Feb 2013 19:07:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.982
X-Spam-Level: 
X-Spam-Status: No, score=-4.982 tagged_above=-999 required=5 tests=[AWL=-1.283, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MANGLED_PRBLMS=2.3, 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 rQuSdv6j77QQ; Tue, 26 Feb 2013 19:07:10 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1A31121F8602; Tue, 26 Feb 2013 19:07:09 -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 AOV20200; Wed, 27 Feb 2013 03:07:08 +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 03:06:13 +0000
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 27 Feb 2013 03:07:07 +0000
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.101]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.01.0323.007; Wed, 27 Feb 2013 11:07:02 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>, "arturo.servin@gmail.com" <arturo.servin@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: SLAAC/DHCPv6 addr-conf operational gaps
Thread-Index: AQHOE/Dp7oY45oFpuUWdZ8xgw4l8cJiLnE0AgAFog0A=
Date: Wed, 27 Feb 2013 03:07:02 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC74E@nkgeml506-mbx.china.huawei.com>
References: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC03C@nkgeml506-mbx.china.huawei.com> <CD522107.408ED%victor.kuarsingh@gmail.com>
In-Reply-To: <CD522107.408ED%victor.kuarsingh@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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 03:07:12 -0000

Hi, Victor & Arturo

Thanks for the comments.
We do plan to write a draft of subsequence solution. But as Victor said, st=
ep 1 is to see if the groups agree there are problems. So hope more people =
could feed back on this.

Many thanks.

B.R.
Bing

> -----Original Message-----
> From: Victor Kuarsingh [mailto:victor.kuarsingh@gmail.com]
> Sent: Tuesday, February 26, 2013 9:28 PM
> To: Liubing (Leo); ipv6@ietf.org; v6ops@ietf.org
> Cc: renum@ietf.org
> Subject: Re: SLAAC/DHCPv6 addr-conf operational gaps
>=20
> Bing,
>=20
> I as able to review the draft and agree this needs to be documented and
> discussed.  I have had many frustrating nights dealing with my multiple
> OSs at home and figuring out what behaviour I was trying to expect when
> changing the upstream router's settings (M/O/A).
>=20
> I think the problem space discussion within the draft should be enough to
> have a preliminary discussion in the WG.  I know there have been issues i=
n
> the past with various opinions on what the M/O bits (for example) should
> or should not be used for - or how authoritative they should be.
>=20
> If the groups can agree that there is in fact a problem, then I would
> agree with Arturo that we can have a constructive follow-up
> draft/discussion on the corrective action.
>=20
> Lets get past step 1 and agree there is an issue (or not); then go down
> the more sensitive path of agreeing to the corrective action.
>=20
> Thanks for putting this together.
>=20
> Regards,
>=20
> Victor Kuarsingh
>=20
>=20
>=20
> On 2013-02-26 2:14 AM, "Liubing (Leo)" <leo.liubing@huawei.com> wrote:
>=20
> >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 hos=
t
> >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 ambiguou=
s
> >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-probl=
e
> m
> >>-
> >> 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=3Ddraft-liu-bonica-dhcpv6-slaac-proble=
m-0
> 1
> >>
> >> 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
> >
> >--------------------------------------------------------------------
> >IETF IPv6 working group mailing list
> >ipv6@ietf.org
> >Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >--------------------------------------------------------------------
>=20


From jiangsheng@huawei.com  Tue Feb 26 19:36:42 2013
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 9F40D21F85CB; Tue, 26 Feb 2013 19:36:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.111
X-Spam-Level: 
X-Spam-Status: No, score=-6.111 tagged_above=-999 required=5 tests=[AWL=-0.112, 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 0DA59Rs9cBrw; Tue, 26 Feb 2013 19:36:42 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1486E21F863C; Tue, 26 Feb 2013 19:36:40 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AOV21817; Wed, 27 Feb 2013 03:36:39 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 27 Feb 2013 03:36:34 +0000
Received: from SZXEML458-HUB.china.huawei.com (10.82.67.201) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 27 Feb 2013 03:36:39 +0000
Received: from szxeml545-mbx.china.huawei.com ([169.254.1.45]) by SZXEML458-HUB.china.huawei.com ([10.82.67.201]) with mapi id 14.01.0323.007; Wed, 27 Feb 2013 11:36:31 +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/Dp7oY45oFpuUWdZ8xgw4l8cJiNDEUQ
Date: Wed, 27 Feb 2013 03:36:30 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923A00E022@szxeml545-mbx.china.huawei.com>
References: <20130225095210.8863.75094.idtracker@ietfa.amsl.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC03C@nkgeml506-mbx.china.huawei.com>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC03C@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 03:36:42 -0000

VGhpcyBoYXMgYmVlbiBhIGhpc3RvcmljIGlzc3VlLiBBbHRob3VnaCB0aGVyZSB3YXMgZGlzY3Vz
c2lvbnMgc2V2ZXJhbCB0aW1lcywgdGhlIHNwZWNpZmljYXRpb24gc3RpbGwgcmVtYWluIGFtYmln
dW91cy4gVGhlIGRpZmZlcmVuY2VzIGluIE9TIGltcGxlbWVudGF0aW9ucyBhcmUgZ29vZCBwcm9v
ZiB0aGF0IHdlIG5lZWQgdG8gZG8gc29tZXRoaW5nIGluIElFVEYuDQoNClRoaXMgZG9jdW1lbnQg
aGFzIHdlbGwgZGVzY3JpYmVkIHRoZSBjdXJyZW50IHN0YW5kYXJkIHN0YXR1cyBhbmQgcmVhbGl0
eSBvcGVyYXRpb25hbCBpc3N1ZXMuIEhvd2V2ZXIsIGZvciBtZSwgdGhpcyBkb2N1bWVudCBmYWls
cyB0byBzdWdnZXN0IHdoYXQgd2UgbWF5IGRvIHRvIGZpeCB0aGlzIGlzc3VlLCBuZWl0aGVyIGlu
IHRoZSBnYXAgc2VjdGlvbiBvciBhcyBjb25jbHVzaW9uLiBJdCBpcyBjbGVhciB0aGF0IHBhcnQg
b2YgUkZDNDg2MiBuZWVkcyB0byBiZSB1cGRhdGVkIHRvIG1ha2UgdGhlIGNvbmZpZ3VyYXRpb24g
YmVoYXZpb3IgY2xlYXIgYW5kIGNvbnNpc3RlbnQuIEZvciB0aGF0LCB0aGlzIGRvY3VtZW50IGZh
aWxzIHRvIGdpdmUgYSBmZWFzaWJsZSBwcm9wb3NhbC4gTWF5YmUsIHRoZSBhdXRob3JzIGhhcyBz
YXZlZCB0aGF0IGZvciBhbm90aGVyIGZvbGxvdyB1cCBzdGFuZGFyZCB0cmFjayBkb2N1bWVudC4N
Cg0KQmVzdCByZWdhcmRzLA0KDQpTaGVuZw0KDQo+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N
Cj5Gcm9tOiByZW51bS1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86cmVudW0tYm91bmNlc0BpZXRm
Lm9yZ10gT24gQmVoYWxmDQo+T2YgTGl1YmluZyAoTGVvKQ0KPlNlbnQ6IFR1ZXNkYXksIEZlYnJ1
YXJ5IDI2LCAyMDEzIDM6MTQgUE0NCj5UbzogaXB2NkBpZXRmLm9yZzsgdjZvcHNAaWV0Zi5vcmcN
Cj5DYzogcmVudW1AaWV0Zi5vcmcNCj5TdWJqZWN0OiBbcmVudW1dIFNMQUFDL0RIQ1B2NiBhZGRy
LWNvbmYgb3BlcmF0aW9uYWwgZ2Fwcw0KPg0KPkhpLCA2bWFuICYgdjZvcHMNCj4NCj5XZSBzdWJt
aXR0ZWQgYSBuZXcgZHJhZnQgdG8gZGlzY3VzcyB0aGUgU0xBQUMvREhDUHY2IGludGVyYWN0aW9u
IGdhcHMuDQo+DQo+QXMgd2Uga25vdyB0aGVyZSBhcmUgc2V2ZXJhbCBmbGFncyBpbiBSQSBtZXNz
YWdlcyByZWdhcmRpbmcgd2l0aCB0aGUgaG9zdA0KPmNvbmZpZ3VyYXRpb24gYmVoYXZpb3IsIHdo
aWNoIGFyZSBBIChBdXRvbm9tb3VzKSBmbGFnLCBNIChNYW5hZ2VkKSBmbGFnLA0KPmFuZCBPIChP
dGhlcmNvbmZpZykgZmxhZy4NCj5Gb3Igc29tZSByZWFzb24sIHRoZSBob3N0IGJlaGF2aW9yIG9m
IGludGVycHJldGluZyB0aGUgZmxhZ3MgaXMgYW1iaWd1b3VzIGluDQo+dGhlIHN0YW5kYXJkICht
YWlubHkgUkZDNDg2MikuIEkgcHJlc2VudGVkIGEgZHJhZnQgZGlzY3Vzc2luZyBNIGZsYWcgYmVo
YXZpb3INCj5pbiA2bWFuIEBpZXRmODQsIGFuZCB0aGVyZSB3ZXJlIHNvbWUgZmVlZGJhY2tzIGFy
Z3VpbmcgdGhlIHNhbWUgaXNzdWUuDQo+VGhpcyBkcmFmdCBhbmFseXplZCBhbGwgdGhlIHRocmVl
IGZsYWdzLCBhbmQgcHJvdmlkZWQgdGVzdCByZXN1bHQgb2YgY3VycmVudA0KPmltcGxlbWVudGF0
aW9ucywgaXQgc2hvd2VkIHRoZSBiZWhhdmlvciBvZiBkaWZmZXJlbnQgbWFpbnN0cmVhbSBkZXNr
dG9wDQo+T1NlcyBoYXZlIHZhcmllZC4gVGhlIGFtYmlndW91cyBhbmQgdmFyaWF0aW9uIG1pZ2h0
IGNhdXNlIG9wZXJhdGlvbmFsDQo+cHJvYmxlbXMsIHN1Y2ggYXMgcmVudW1iZXJpbmcgKHVzZWQg
dG8gZGlzY3VzcyBpbiA2cmVudW0gV0cgYW5kIGJlZW4NCj5kb2N1bWVudGVkIGluIHRoZSBXRyBk
cmFmdHMpLCBjb2xkIHN0YXJ0IHByb2JsZW0sIGFuZCBtYW5hZ2VtZW50DQo+Z2FwcyAuZXRjLg0K
Pg0KPllvdXIgcmV2aWV3IGFuZCBjb21tZW50cyB3b3VsZCBiZSBhcHByZWNpYXRlZCB2ZXJ5IG11
Y2guDQo+DQo+QWxsIHRoZSBiZXN0LA0KPkJpbmcNCj4NCj4+IC0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQo+PiBGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzppbnRlcm5l
dC1kcmFmdHNAaWV0Zi5vcmddDQo+PiBTZW50OiBNb25kYXksIEZlYnJ1YXJ5IDI1LCAyMDEzIDU6
NTIgUE0NCj4+IFRvOiBMaXViaW5nIChMZW8pDQo+PiBDYzogcmJvbmljYUBqdW5pcGVyLm5ldA0K
Pj4gU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvcg0KPj4gZHJhZnQtbGl1LWJv
bmljYS1kaGNwdjYtc2xhYWMtcHJvYmxlbS0wMS50eHQNCj4+DQo+Pg0KPj4gQSBuZXcgdmVyc2lv
biBvZiBJLUQsIGRyYWZ0LWxpdS1ib25pY2EtZGhjcHY2LXNsYWFjLXByb2JsZW0tMDEudHh0DQo+
PiBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IEJpbmcgTGl1IGFuZCBwb3N0ZWQg
dG8gdGhlDQo+PiBJRVRGIHJlcG9zaXRvcnkuDQo+Pg0KPj4gRmlsZW5hbWU6CSBkcmFmdC1saXUt
Ym9uaWNhLWRoY3B2Ni1zbGFhYy1wcm9ibGVtDQo+PiBSZXZpc2lvbjoJIDAxDQo+PiBUaXRsZToJ
CSBESENQdjYvU0xBQUMgQWRkcmVzcyBDb25maWd1cmF0aW9uIEludGVyYWN0aW9uIFByb2JsZW0N
Cj4+IFN0YXRlbWVudA0KPj4gQ3JlYXRpb24gZGF0ZToJIDIwMTMtMDItMjUNCj4+IEdyb3VwOgkJ
IEluZGl2aWR1YWwgU3VibWlzc2lvbg0KPj4gTnVtYmVyIG9mIHBhZ2VzOiAxMg0KPj4gVVJMOg0K
Pj4gaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtbGl1LWJvbmljYS1k
aGNwdjYtc2xhYWMtcHJvYmxlbS0NCj4+IDAxLnR4dA0KPj4gU3RhdHVzOg0KPj4gaHR0cDovL2Rh
dGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1saXUtYm9uaWNhLWRoY3B2Ni1zbGFhYy1wcm9i
bGVtDQo+PiBIdG1saXplZDoNCj4+IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWxp
dS1ib25pY2EtZGhjcHY2LXNsYWFjLXByb2JsZW0tMDENCj4+IERpZmY6DQo+PiBodHRwOi8vd3d3
LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1saXUtYm9uaWNhLWRoY3B2Ni1zbGFhYy1wcm9i
bGVtLTAxDQo+Pg0KPj4gQWJzdHJhY3Q6DQo+PiAgICBUaGlzIGRvY3VtZW50IGFuYWx5emVzIHRo
ZSBob3N0IGJlaGF2aW9yIG9mIERIQ1B2Ni9TTEFBQyBpbnRlcmFjdGlvbg0KPj4gICAgaXNzdWUu
IEl0IHJldmlld3MgdGhlIHN0YW5kYXJkIGRlZmluaXRpb24gb2YgdGhlIGhvc3QgYmVoYXZpb3Jz
IGFuZA0KPj4gICAgcHJvdmlkZXMgdGhlIHRlc3QgcmVzdWx0cyBvZiBjdXJyZW50IG1haW5zdHJl
YW0gaW1wbGVtZW50YXRpb25zLiBTb21lDQo+PiAgICBwb3RlbnRpYWwgb3BlcmF0aW9uYWwgZ2Fw
cyBvZiB0aGUgaW50ZXJhY3Rpb24gYXJlIGFsc28gZGVzY3JpYmVkLg0KPj4NCj4+DQo+Pg0KPj4N
Cj4+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQo+DQo+X19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCj5yZW51bSBtYWlsaW5nIGxpc3QNCj5yZW51bUBpZXRmLm9y
Zw0KPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcmVudW0NCg==

From leo.liubing@huawei.com  Tue Feb 26 20:01:32 2013
Return-Path: <leo.liubing@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 7831B21F86D5; Tue, 26 Feb 2013 20:01:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.004
X-Spam-Level: 
X-Spam-Status: No, score=-6.004 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 6b8bfnf6D-ST; Tue, 26 Feb 2013 20:01:31 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 89ECD21F86A8; Tue, 26 Feb 2013 20:01:30 -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 AOV23270; Wed, 27 Feb 2013 04:01:28 +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 04:00:33 +0000
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 27 Feb 2013 04:01:27 +0000
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.101]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.01.0323.007; Wed, 27 Feb 2013 12:01:20 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "STARK, BARBARA H" <bs7652@att.com>, "ipv6@ietf.org" <ipv6@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: SLAAC/DHCPv6 addr-conf operational gaps
Thread-Index: AQHOE/Dp7oY45oFpuUWdZ8xgw4l8cJiMZZ8ggACi1xA=
Date: Wed, 27 Feb 2013 04:01:19 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC7D7@nkgeml506-mbx.china.huawei.com>
References: <20130225095210.8863.75094.idtracker@ietfa.amsl.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC03C@nkgeml506-mbx.china.huawei.com> <2D09D61DDFA73D4C884805CC7865E61130255AE0@GAALPA1MSGUSR9L.ITServices.sbc.com>
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E61130255AE0@GAALPA1MSGUSR9L.ITServices.sbc.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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 04:01:32 -0000

Hi, Barbara

Thanks for your comments. Please see replies inline.

> -----Original Message-----
> From: STARK, BARBARA H [mailto:bs7652@att.com]
> Sent: Wednesday, February 27, 2013 2:02 AM
> To: Liubing (Leo); ipv6@ietf.org; v6ops@ietf.org
> Cc: renum@ietf.org
> Subject: RE: SLAAC/DHCPv6 addr-conf operational gaps
>=20
> This is interesting. Thanks for doing these tests and submitting the resu=
lts.
>=20
> When testing the switching behavior, I'm curious for the " SLAAC-only hos=
t
> receiving A=3D0&M=3D1 " case as to what you set the Preferred Lifetime to=
,
> when you set A=3D0. I'm guessing Preferred Lifetime > 0?

[Bing] Yes, we just leave the Preferred Lifetime as default, it should be >=
 0

> Since RFC 4862 states "A preferred address becomes deprecated when its
> preferred lifetime expires", I would only have expected a host to depreca=
te a
> SLAAC-obtained address if the RA message set Preferred Lifetime to zero. =
It
> sounds like the case where the RA is changed from A=3D1 and Preferred
> Lifetime > 0 to A=3D0 and Preferred Lifetime > 0 is ambiguous.=20

[Bing] As I learned from RFC4862, it is ambiguous.

>I'm not quite
> sure what the use case is for separating the A flag and Preferred Lifetim=
e
> settings. Did you also run the test by changing to A=3D0 and Preferred Li=
fetime
> =3D 0? I would hope that there would be consistent behavior in that case.

[Bing] We haven't run that, but could do it later. Thanks for the remind.
For separating A flag and Preferred Lifetime, it is just the concept of sep=
arating "_address configuration_ methods" and "address aging" raised by Mar=
k Smith in another mail on this thread. I think it is a good point of view,=
 and if we can initiate subsequence revision of host behavior, we should co=
nsider it.

> For the "DHCPv6-only host receiving A=3D1&M=3D0" case, I'm curious as to
> whether you also tried sending a DHCPv6 Reconfigure message and forcing
> the host to release the DHCPv6-assigned address; and send A=3D1&M=3D0 in =
an
> RA directly after sending the Reconfigure. I'm not sure what the use case=
 is
> for trying to force the release or deprecation of a DHCPv6 address via fl=
ags
> in an RA message. Once a host has a DHCPv6 address, I would have expected
> its subsequent behavior relating to that address and that DHCPv6 server t=
o
> be governed by RFC 3315.=20

[Bing] We haven't tried this, could do later. But we used to talk about it =
in 6renum WG. DHCPv6-Reconfiguration is considered not suitable for bulk us=
age, since it is stateful and unicast, might cause heavy load for the DHCPv=
6 server, this has been documented in [draft-ietf-6renum-gap-analysis]. Mor=
eover, it is more difficult for administration to simultaneously operate DH=
CPv6 and ND together. =20

The Linux/MAC behavior appears consistent with
> what I would have expected. The Windows 7 does not. I'm unaware of even
> a "hint" that suggests RA flags have a role in governing DHCPv6 behavior
> once RFC 3315 is in play.

[Bing] That is just the ambiguous of the RA flags behavior. IMHO, we need t=
o specify it clear in the standard. Whether the RA flags should govern DHCP=
v6 behavior or not, we can discuss it in the next step if the groups agree =
we should deal with the ambiguous problem firstly.

B.R.
Bing


> Barbara
>=20
> > -----Original Message-----
> > From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of
> > Liubing (Leo)
> > Sent: Tuesday, February 26, 2013 2:14 AM
> > To: ipv6@ietf.org; v6ops@ietf.org
> > Cc: renum@ietf.org
> > Subject: 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 ho=
st
> > 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 ambiguo=
us
> 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 cu=
rrent
> > 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-pro=
b
> > > lem-
> > > 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=3Ddraft-liu-bonica-dhcpv6-slaac-prob=
lem
> > > -01
> > >
> > > Abstract:
> > >    This document analyzes the host behavior of DHCPv6/SLAAC
> interaction
> > >    issue. It reviews the standard definition of the host behaviors an=
d
> > >    provides the test results of current mainstream implementations.
> Some
> > >    potential operational gaps of the interaction are also described.
> > >
> > >
> > >
> > >
> > > The IETF Secretariat
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------

From leo.liubing@huawei.com  Tue Feb 26 21:56:23 2013
Return-Path: <leo.liubing@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 E2B0721F86E3; Tue, 26 Feb 2013 21:56:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.004
X-Spam-Level: 
X-Spam-Status: No, score=-6.004 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 Lj8B2Y-xL30p; Tue, 26 Feb 2013 21:56:18 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1BC7821F85D7; Tue, 26 Feb 2013 21:56:15 -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 AOV29444; Wed, 27 Feb 2013 05:56:13 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 27 Feb 2013 05:55:17 +0000
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 27 Feb 2013 05:56:12 +0000
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.101]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.01.0323.007; Wed, 27 Feb 2013 13:56:04 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Mark Smith <markzzzsmith@yahoo.com.au>, "ipv6@ietf.org" <ipv6@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: SLAAC/DHCPv6 addr-conf operational gaps
Thread-Index: AQHOE/Dp7oY45oFpuUWdZ8xgw4l8cJiME2CAgAEfplA=
Date: Wed, 27 Feb 2013 05:56:03 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC83E@nkgeml506-mbx.china.huawei.com>
References: <20130225095210.8863.75094.idtracker@ietfa.amsl.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC03C@nkgeml506-mbx.china.huawei.com> <1361910873.78397.YahooMailNeo@web142503.mail.bf1.yahoo.com>
In-Reply-To: <1361910873.78397.YahooMailNeo@web142503.mail.bf1.yahoo.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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 05:56:23 -0000

Hi, Mark

Thanks for your comment.=20
I like the concept of separating "_address configuration_ methods" and "add=
ress aging methods", if we could initiate the subsequence work, it should b=
e considered.

All the best
Bing

> -----Original Message-----
> From: Mark Smith [mailto:markzzzsmith@yahoo.com.au]
> Sent: Wednesday, February 27, 2013 4:35 AM
> To: Liubing (Leo); ipv6@ietf.org; v6ops@ietf.org
> Cc: renum@ietf.org
> Subject: Re: SLAAC/DHCPv6 addr-conf operational gaps
>=20
> Hi,
>=20
> I've had a quick read though, I'll try to do a thorough one in the next w=
eek or
> so.
>=20
> Thanks for writing this, I've been thinking about doing something similar=
 over
> the last few months since, IIRC, I heard about Windows 7 invalidating IPv=
6
> addresses learned via DHCPv6 when SLAAC was enabled and DHCPv6 was
> disabled on a link.
>=20
> A few thoughts I've had which may be useful -
>=20
> Firstly, I came to realise that the mistake being made by Windows 7 was t=
he
> assumption that the aging of the assigned IPv6 addresses was tightly coup=
led
> to the DHCPv6 session state, meaning that if DHCPv6 went away, so would
> the assigned addresses. This is generally the way DHCPv4 has worked.
> However, in IPv6/DHCPv6, it seems the address lifetime values in the IA_N=
A
> are not coupled to the T1 and T2 times, so if DHCPv6 goes away (perhaps
> because the M bit was switched off in a latter RA), the configured IPv6
> addresses should be left to age out as per their preferred and valid life=
times.
>=20
> The other thing I noticed was that the M RA flag and the PIO A flags aren=
't
> mutually exclusive - I couldn't find any text in RFC4861 that says if the=
 M bit
> is switched on, the PIO A flags must be switched off and vice-versa. So t=
hat
> suggests that the DHCPv6 and SLAAC can co-exist, and I think that is quit=
e
> reasonable if you're transitioning a link from DHCPv6 to SLAAC address
> configuration or vice-versa.
>=20
> Thinking about it more, I came realise that DHCPv6 and SLAAC are _address
> configuration_ methods, but are not address aging methods - IPv6 takes ca=
re
> of address aging via it's preferred and valid aging mechanisms, regardles=
s of
> the address configuration method. Static assignment is also just an addre=
ss
> configuration method, although typically the addresses don't age out, but
> only because they're normally set to infinity. Perhaps in the future ther=
e
> might be other address configuration methods.
>=20
> I didn't seem to be able to find an RFC that made it clear that address
> configuration and address aging are quite separate, so perhaps this ID co=
uld
> be the one.
>=20
> Regarding this text:
>=20
> 'For the host behavior, there is an explicit rule in the SLAAC specificat=
ion
> [RFC4862]: "If the Autonomous flag is not set, silently ignore the Prefix
> Information option."'
>=20
> I think RFC5942, "IPv6 Subnet Model: The Relationship between Links and
> Subnet Prefixes." updates that advice, as the PIO option is used to indic=
ates
> which prefix/range of addresses are on-link, via the PIO O bit, even if t=
he PIO
> A bit is switched off.
>=20
> Best regards,
> Mark.
>=20
> >________________________________
> > From: Liubing (Leo) <leo.liubing@huawei.com>
> >To: "ipv6@ietf.org" <ipv6@ietf.org>; "v6ops@ietf.org" <v6ops@ietf.org>
> >Cc: "renum@ietf.org" <renum@ietf.org>
> >Sent: Tuesday, 26 February 2013 6:14 PM
> >Subject: 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 hos=
t
> 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 ambiguou=
s 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:=A0=A0=A0=A0=A0draft-liu-bonica-dhcpv6-slaac-problem
> >> Revision:=A0=A0=A0=A0=A001
> >> Title:=A0=A0=A0 =A0=A0=A0=A0=A0DHCPv6/SLAAC Address Configuration Inte=
raction
> Problem
> >> Statement
> >> Creation date:=A0=A0=A0=A0=A02013-02-25
> >> Group:=A0=A0=A0 =A0=A0=A0=A0=A0Individual 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=3Ddraft-liu-bonica-dhcpv6-slaac-problem-=
01
> >>
> >> Abstract:
> >>=A0 =A0 This document analyzes the host behavior of DHCPv6/SLAAC
> interaction
> >>=A0 =A0 issue. It reviews the standard definition of the host behaviors=
 and
> >>=A0 =A0 provides the test results of current mainstream implementations=
.
> Some
> >>=A0 =A0 potential operational gaps of the interaction are also describe=
d.
> >>
> >>
> >>
> >>
> >> The IETF Secretariat
> >
> >--------------------------------------------------------------------
> >IETF IPv6 working group mailing list
> >ipv6@ietf.org
> >Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >--------------------------------------------------------------------
> >
> >
> >

From leo.liubing@huawei.com  Tue Feb 26 22:16:48 2013
Return-Path: <leo.liubing@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 DDECF21F87B3; Tue, 26 Feb 2013 22:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.003
X-Spam-Level: 
X-Spam-Status: No, score=-6.003 tagged_above=-999 required=5 tests=[AWL=-0.004, 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 5SjaqQ-J2xLt; Tue, 26 Feb 2013 22:16:48 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 81EE621F8722; Tue, 26 Feb 2013 22:16:47 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQC30124; Wed, 27 Feb 2013 06:16:46 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) 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:15:50 +0000
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 27 Feb 2013 06:16:45 +0000
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.101]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.01.0323.007; Wed, 27 Feb 2013 14:16:36 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Sheng Jiang <jiangsheng@huawei.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Thread-Topic: SLAAC/DHCPv6 addr-conf operational gaps
Thread-Index: AQHOE/Dp7oY45oFpuUWdZ8xgw4l8cJiNDEUQgAAsV0A=
Date: Wed, 27 Feb 2013 06:16:35 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC86A@nkgeml506-mbx.china.huawei.com>
References: <20130225095210.8863.75094.idtracker@ietfa.amsl.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC03C@nkgeml506-mbx.china.huawei.com> <5D36713D8A4E7348A7E10DF7437A4B923A00E022@szxeml545-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923A00E022@szxeml545-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
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:16:49 -0000

SGksIFNoZW5nDQoNClRoYW5rcyBmb3IgeW91ciBjb21tZW50cy4NClRoaXMgaXMgdGhlIGZpcnN0
IHN0ZXAsIHRvIHNlZSBpZiB0aGVyZSBpcyBjb25zZW5zdXMgb2YgYWdyZWVpbmcgdGhlIHByb2Js
ZW1zIHNob3VsZCBiZSBmaXhlZCBpbiBjdXJyZW50IHN0YW5kYXJkLiBJZiBzbywgd2UnbGwgc3Vi
bWl0IGEgZHJhZnQgdG8gZml4IHRoZSBhbWJpZ3VvdXMgaXNzdWUuDQoNCkIuUi4NCkJpbmcNCg0K
DQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IFNoZW5nIEppYW5nDQo+IFNl
bnQ6IFdlZG5lc2RheSwgRmVicnVhcnkgMjcsIDIwMTMgMTE6MzcgQU0NCj4gVG86IExpdWJpbmcg
KExlbyk7IGlwdjZAaWV0Zi5vcmcNCj4gQ2M6IHJlbnVtQGlldGYub3JnDQo+IFN1YmplY3Q6IFJF
OiBTTEFBQy9ESENQdjYgYWRkci1jb25mIG9wZXJhdGlvbmFsIGdhcHMNCj4gDQo+IFRoaXMgaGFz
IGJlZW4gYSBoaXN0b3JpYyBpc3N1ZS4gQWx0aG91Z2ggdGhlcmUgd2FzIGRpc2N1c3Npb25zIHNl
dmVyYWwgdGltZXMsDQo+IHRoZSBzcGVjaWZpY2F0aW9uIHN0aWxsIHJlbWFpbiBhbWJpZ3VvdXMu
IFRoZSBkaWZmZXJlbmNlcyBpbiBPUw0KPiBpbXBsZW1lbnRhdGlvbnMgYXJlIGdvb2QgcHJvb2Yg
dGhhdCB3ZSBuZWVkIHRvIGRvIHNvbWV0aGluZyBpbiBJRVRGLg0KPiANCj4gVGhpcyBkb2N1bWVu
dCBoYXMgd2VsbCBkZXNjcmliZWQgdGhlIGN1cnJlbnQgc3RhbmRhcmQgc3RhdHVzIGFuZCByZWFs
aXR5DQo+IG9wZXJhdGlvbmFsIGlzc3Vlcy4gSG93ZXZlciwgZm9yIG1lLCB0aGlzIGRvY3VtZW50
IGZhaWxzIHRvIHN1Z2dlc3Qgd2hhdCB3ZQ0KPiBtYXkgZG8gdG8gZml4IHRoaXMgaXNzdWUsIG5l
aXRoZXIgaW4gdGhlIGdhcCBzZWN0aW9uIG9yIGFzIGNvbmNsdXNpb24uIEl0IGlzIGNsZWFyDQo+
IHRoYXQgcGFydCBvZiBSRkM0ODYyIG5lZWRzIHRvIGJlIHVwZGF0ZWQgdG8gbWFrZSB0aGUgY29u
ZmlndXJhdGlvbg0KPiBiZWhhdmlvciBjbGVhciBhbmQgY29uc2lzdGVudC4gRm9yIHRoYXQsIHRo
aXMgZG9jdW1lbnQgZmFpbHMgdG8gZ2l2ZSBhIGZlYXNpYmxlDQo+IHByb3Bvc2FsLiBNYXliZSwg
dGhlIGF1dGhvcnMgaGFzIHNhdmVkIHRoYXQgZm9yIGFub3RoZXIgZm9sbG93IHVwIHN0YW5kYXJk
DQo+IHRyYWNrIGRvY3VtZW50Lg0KPiANCj4gQmVzdCByZWdhcmRzLA0KPiANCj4gU2hlbmcNCj4g
DQo+ID4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+RnJvbTogcmVudW0tYm91bmNlc0Bp
ZXRmLm9yZyBbbWFpbHRvOnJlbnVtLWJvdW5jZXNAaWV0Zi5vcmddIE9uDQo+IEJlaGFsZg0KPiA+
T2YgTGl1YmluZyAoTGVvKQ0KPiA+U2VudDogVHVlc2RheSwgRmVicnVhcnkgMjYsIDIwMTMgMzox
NCBQTQ0KPiA+VG86IGlwdjZAaWV0Zi5vcmc7IHY2b3BzQGlldGYub3JnDQo+ID5DYzogcmVudW1A
aWV0Zi5vcmcNCj4gPlN1YmplY3Q6IFtyZW51bV0gU0xBQUMvREhDUHY2IGFkZHItY29uZiBvcGVy
YXRpb25hbCBnYXBzDQo+ID4NCj4gPkhpLCA2bWFuICYgdjZvcHMNCj4gPg0KPiA+V2Ugc3VibWl0
dGVkIGEgbmV3IGRyYWZ0IHRvIGRpc2N1c3MgdGhlIFNMQUFDL0RIQ1B2NiBpbnRlcmFjdGlvbiBn
YXBzLg0KPiA+DQo+ID5BcyB3ZSBrbm93IHRoZXJlIGFyZSBzZXZlcmFsIGZsYWdzIGluIFJBIG1l
c3NhZ2VzIHJlZ2FyZGluZyB3aXRoIHRoZSBob3N0DQo+ID5jb25maWd1cmF0aW9uIGJlaGF2aW9y
LCB3aGljaCBhcmUgQSAoQXV0b25vbW91cykgZmxhZywgTSAoTWFuYWdlZCkgZmxhZywNCj4gPmFu
ZCBPIChPdGhlcmNvbmZpZykgZmxhZy4NCj4gPkZvciBzb21lIHJlYXNvbiwgdGhlIGhvc3QgYmVo
YXZpb3Igb2YgaW50ZXJwcmV0aW5nIHRoZSBmbGFncyBpcyBhbWJpZ3VvdXMgaW4NCj4gPnRoZSBz
dGFuZGFyZCAobWFpbmx5IFJGQzQ4NjIpLiBJIHByZXNlbnRlZCBhIGRyYWZ0IGRpc2N1c3Npbmcg
TSBmbGFnDQo+IGJlaGF2aW9yDQo+ID5pbiA2bWFuIEBpZXRmODQsIGFuZCB0aGVyZSB3ZXJlIHNv
bWUgZmVlZGJhY2tzIGFyZ3VpbmcgdGhlIHNhbWUgaXNzdWUuDQo+ID5UaGlzIGRyYWZ0IGFuYWx5
emVkIGFsbCB0aGUgdGhyZWUgZmxhZ3MsIGFuZCBwcm92aWRlZCB0ZXN0IHJlc3VsdCBvZiBjdXJy
ZW50DQo+ID5pbXBsZW1lbnRhdGlvbnMsIGl0IHNob3dlZCB0aGUgYmVoYXZpb3Igb2YgZGlmZmVy
ZW50IG1haW5zdHJlYW0gZGVza3RvcA0KPiA+T1NlcyBoYXZlIHZhcmllZC4gVGhlIGFtYmlndW91
cyBhbmQgdmFyaWF0aW9uIG1pZ2h0IGNhdXNlIG9wZXJhdGlvbmFsDQo+ID5wcm9ibGVtcywgc3Vj
aCBhcyByZW51bWJlcmluZyAodXNlZCB0byBkaXNjdXNzIGluIDZyZW51bSBXRyBhbmQgYmVlbg0K
PiA+ZG9jdW1lbnRlZCBpbiB0aGUgV0cgZHJhZnRzKSwgY29sZCBzdGFydCBwcm9ibGVtLCBhbmQg
bWFuYWdlbWVudA0KPiA+Z2FwcyAuZXRjLg0KPiA+DQo+ID5Zb3VyIHJldmlldyBhbmQgY29tbWVu
dHMgd291bGQgYmUgYXBwcmVjaWF0ZWQgdmVyeSBtdWNoLg0KPiA+DQo+ID5BbGwgdGhlIGJlc3Qs
DQo+ID5CaW5nDQo+ID4NCj4gPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPj4gRnJv
bTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYu
b3JnXQ0KPiA+PiBTZW50OiBNb25kYXksIEZlYnJ1YXJ5IDI1LCAyMDEzIDU6NTIgUE0NCj4gPj4g
VG86IExpdWJpbmcgKExlbykNCj4gPj4gQ2M6IHJib25pY2FAanVuaXBlci5uZXQNCj4gPj4gU3Vi
amVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvcg0KPiA+PiBkcmFmdC1saXUtYm9uaWNh
LWRoY3B2Ni1zbGFhYy1wcm9ibGVtLTAxLnR4dA0KPiA+Pg0KPiA+Pg0KPiA+PiBBIG5ldyB2ZXJz
aW9uIG9mIEktRCwgZHJhZnQtbGl1LWJvbmljYS1kaGNwdjYtc2xhYWMtcHJvYmxlbS0wMS50eHQN
Cj4gPj4gaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBCaW5nIExpdSBhbmQgcG9z
dGVkIHRvIHRoZQ0KPiA+PiBJRVRGIHJlcG9zaXRvcnkuDQo+ID4+DQo+ID4+IEZpbGVuYW1lOgkg
ZHJhZnQtbGl1LWJvbmljYS1kaGNwdjYtc2xhYWMtcHJvYmxlbQ0KPiA+PiBSZXZpc2lvbjoJIDAx
DQo+ID4+IFRpdGxlOgkJIERIQ1B2Ni9TTEFBQyBBZGRyZXNzIENvbmZpZ3VyYXRpb24gSW50ZXJh
Y3Rpb24gUHJvYmxlbQ0KPiA+PiBTdGF0ZW1lbnQNCj4gPj4gQ3JlYXRpb24gZGF0ZToJIDIwMTMt
MDItMjUNCj4gPj4gR3JvdXA6CQkgSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQo+ID4+IE51bWJlciBv
ZiBwYWdlczogMTINCj4gPj4gVVJMOg0KPiA+Pg0KPiBodHRwOi8vd3d3LmlldGYub3JnL2ludGVy
bmV0LWRyYWZ0cy9kcmFmdC1saXUtYm9uaWNhLWRoY3B2Ni1zbGFhYy1wcm9ibGVtLQ0KPiA+PiAw
MS50eHQNCj4gPj4gU3RhdHVzOg0KPiA+PiBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9j
L2RyYWZ0LWxpdS1ib25pY2EtZGhjcHY2LXNsYWFjLXByb2JsZW0NCj4gPj4gSHRtbGl6ZWQ6DQo+
ID4+IGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWxpdS1ib25pY2EtZGhjcHY2LXNs
YWFjLXByb2JsZW0tMDENCj4gPj4gRGlmZjoNCj4gPj4NCj4gaHR0cDovL3d3dy5pZXRmLm9yZy9y
ZmNkaWZmP3VybDI9ZHJhZnQtbGl1LWJvbmljYS1kaGNwdjYtc2xhYWMtcHJvYmxlbS0wMQ0KPiA+
Pg0KPiA+PiBBYnN0cmFjdDoNCj4gPj4gICAgVGhpcyBkb2N1bWVudCBhbmFseXplcyB0aGUgaG9z
dCBiZWhhdmlvciBvZiBESENQdjYvU0xBQUMNCj4gaW50ZXJhY3Rpb24NCj4gPj4gICAgaXNzdWUu
IEl0IHJldmlld3MgdGhlIHN0YW5kYXJkIGRlZmluaXRpb24gb2YgdGhlIGhvc3QgYmVoYXZpb3Jz
IGFuZA0KPiA+PiAgICBwcm92aWRlcyB0aGUgdGVzdCByZXN1bHRzIG9mIGN1cnJlbnQgbWFpbnN0
cmVhbSBpbXBsZW1lbnRhdGlvbnMuDQo+IFNvbWUNCj4gPj4gICAgcG90ZW50aWFsIG9wZXJhdGlv
bmFsIGdhcHMgb2YgdGhlIGludGVyYWN0aW9uIGFyZSBhbHNvIGRlc2NyaWJlZC4NCj4gPj4NCj4g
Pj4NCj4gPj4NCj4gPj4NCj4gPj4gVGhlIElFVEYgU2VjcmV0YXJpYXQNCj4gPg0KPiA+X19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPnJlbnVtIG1haWxp
bmcgbGlzdA0KPiA+cmVudW1AaWV0Zi5vcmcNCj4gPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vcmVudW0NCg==

From jiangsheng@huawei.com  Tue Feb 26 22:45:12 2013
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

SGksIEJpbmcsDQoNCkl0IGlzIGJldHRlciB0byBhdCBsZWFzdCBtZW50aW9uIHRoZSBkaXJlY3Rp
b24gb2YgbmV4dCBzdGVwIC0gY2xlYXJseSByZWRlZmluZSB0aGUgZmxhZyBjb3JyZXNwb25kZW50
IGhvc3QgYmVoYXZpb3IgaW4gc3RhbmRhcmRzLg0KDQpBIGNvdXBsZSBvZiBtb3JlIGRldGFpbGVk
IGNvbW1lbnRzOiB5b3UgaGF2ZSB1c2VkIHdvcmQgImdhcCIgc2V2ZXJhbCB0aW1lcywgd2hpbGUg
eW91IGRpZCBub3QgY2xlYXIgZGVzY3JpYmUgd2hhdCBnYXAgaXQgaXMuIFlvdSBoYXZlIG9ubHkg
ZGVzY3JpYmVkIGlzc3Vlcy9wcm9ibGVtcy4gR2FwcyBzaG91bGQgYmUgc29tZXRoaW5nIHRoYXQg
aXNzdWUgc29sdmVkIGlmIHlvdSBjb3VsZCBmaWxsIHRoZW0uIFN1YnNlY3Rpb25zIG9mIFNlY3Rp
b24gMyBhcmUgcHJvYmxlbSBzY2VuYXJpb3MuIEJ1dCB5b3VyIHN1YnNlY3Rpb24gdGl0bGVzIGRv
IG5vdCBjbGVhciBleHByZXNzIHRoZSBtZWFuaW5nLg0KDQpDaGVlcnMsDQoNClNoZW5nDQoNCj4t
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPkZyb206IExpdWJpbmcgKExlbykNCj5TZW50OiBX
ZWRuZXNkYXksIEZlYnJ1YXJ5IDI3LCAyMDEzIDI6MTcgUE0NCj5UbzogU2hlbmcgSmlhbmc7IGlw
djZAaWV0Zi5vcmcNCj5DYzogcmVudW1AaWV0Zi5vcmcNCj5TdWJqZWN0OiBSRTogU0xBQUMvREhD
UHY2IGFkZHItY29uZiBvcGVyYXRpb25hbCBnYXBzDQo+DQo+SGksIFNoZW5nDQo+DQo+VGhhbmtz
IGZvciB5b3VyIGNvbW1lbnRzLg0KPlRoaXMgaXMgdGhlIGZpcnN0IHN0ZXAsIHRvIHNlZSBpZiB0
aGVyZSBpcyBjb25zZW5zdXMgb2YgYWdyZWVpbmcgdGhlIHByb2JsZW1zDQo+c2hvdWxkIGJlIGZp
eGVkIGluIGN1cnJlbnQgc3RhbmRhcmQuIElmIHNvLCB3ZSdsbCBzdWJtaXQgYSBkcmFmdCB0byBm
aXggdGhlDQo+YW1iaWd1b3VzIGlzc3VlLg0KPg0KPkIuUi4NCj5CaW5nDQo+DQo+DQo+PiAtLS0t
LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4gRnJvbTogU2hlbmcgSmlhbmcNCj4+IFNlbnQ6IFdl
ZG5lc2RheSwgRmVicnVhcnkgMjcsIDIwMTMgMTE6MzcgQU0NCj4+IFRvOiBMaXViaW5nIChMZW8p
OyBpcHY2QGlldGYub3JnDQo+PiBDYzogcmVudW1AaWV0Zi5vcmcNCj4+IFN1YmplY3Q6IFJFOiBT
TEFBQy9ESENQdjYgYWRkci1jb25mIG9wZXJhdGlvbmFsIGdhcHMNCj4+DQo+PiBUaGlzIGhhcyBi
ZWVuIGEgaGlzdG9yaWMgaXNzdWUuIEFsdGhvdWdoIHRoZXJlIHdhcyBkaXNjdXNzaW9ucyBzZXZl
cmFsIHRpbWVzLA0KPj4gdGhlIHNwZWNpZmljYXRpb24gc3RpbGwgcmVtYWluIGFtYmlndW91cy4g
VGhlIGRpZmZlcmVuY2VzIGluIE9TDQo+PiBpbXBsZW1lbnRhdGlvbnMgYXJlIGdvb2QgcHJvb2Yg
dGhhdCB3ZSBuZWVkIHRvIGRvIHNvbWV0aGluZyBpbiBJRVRGLg0KPj4NCj4+IFRoaXMgZG9jdW1l
bnQgaGFzIHdlbGwgZGVzY3JpYmVkIHRoZSBjdXJyZW50IHN0YW5kYXJkIHN0YXR1cyBhbmQgcmVh
bGl0eQ0KPj4gb3BlcmF0aW9uYWwgaXNzdWVzLiBIb3dldmVyLCBmb3IgbWUsIHRoaXMgZG9jdW1l
bnQgZmFpbHMgdG8gc3VnZ2VzdCB3aGF0DQo+d2UNCj4+IG1heSBkbyB0byBmaXggdGhpcyBpc3N1
ZSwgbmVpdGhlciBpbiB0aGUgZ2FwIHNlY3Rpb24gb3IgYXMgY29uY2x1c2lvbi4gSXQgaXMNCj5j
bGVhcg0KPj4gdGhhdCBwYXJ0IG9mIFJGQzQ4NjIgbmVlZHMgdG8gYmUgdXBkYXRlZCB0byBtYWtl
IHRoZSBjb25maWd1cmF0aW9uDQo+PiBiZWhhdmlvciBjbGVhciBhbmQgY29uc2lzdGVudC4gRm9y
IHRoYXQsIHRoaXMgZG9jdW1lbnQgZmFpbHMgdG8gZ2l2ZSBhIGZlYXNpYmxlDQo+PiBwcm9wb3Nh
bC4gTWF5YmUsIHRoZSBhdXRob3JzIGhhcyBzYXZlZCB0aGF0IGZvciBhbm90aGVyIGZvbGxvdyB1
cCBzdGFuZGFyZA0KPj4gdHJhY2sgZG9jdW1lbnQuDQo+Pg0KPj4gQmVzdCByZWdhcmRzLA0KPj4N
Cj4+IFNoZW5nDQo+Pg0KPj4gPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PiA+RnJvbTog
cmVudW0tYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOnJlbnVtLWJvdW5jZXNAaWV0Zi5vcmddIE9u
DQo+PiBCZWhhbGYNCj4+ID5PZiBMaXViaW5nIChMZW8pDQo+PiA+U2VudDogVHVlc2RheSwgRmVi
cnVhcnkgMjYsIDIwMTMgMzoxNCBQTQ0KPj4gPlRvOiBpcHY2QGlldGYub3JnOyB2Nm9wc0BpZXRm
Lm9yZw0KPj4gPkNjOiByZW51bUBpZXRmLm9yZw0KPj4gPlN1YmplY3Q6IFtyZW51bV0gU0xBQUMv
REhDUHY2IGFkZHItY29uZiBvcGVyYXRpb25hbCBnYXBzDQo+PiA+DQo+PiA+SGksIDZtYW4gJiB2
Nm9wcw0KPj4gPg0KPj4gPldlIHN1Ym1pdHRlZCBhIG5ldyBkcmFmdCB0byBkaXNjdXNzIHRoZSBT
TEFBQy9ESENQdjYgaW50ZXJhY3Rpb24gZ2Fwcy4NCj4+ID4NCj4+ID5BcyB3ZSBrbm93IHRoZXJl
IGFyZSBzZXZlcmFsIGZsYWdzIGluIFJBIG1lc3NhZ2VzIHJlZ2FyZGluZyB3aXRoIHRoZSBob3N0
DQo+PiA+Y29uZmlndXJhdGlvbiBiZWhhdmlvciwgd2hpY2ggYXJlIEEgKEF1dG9ub21vdXMpIGZs
YWcsIE0gKE1hbmFnZWQpIGZsYWcsDQo+PiA+YW5kIE8gKE90aGVyY29uZmlnKSBmbGFnLg0KPj4g
PkZvciBzb21lIHJlYXNvbiwgdGhlIGhvc3QgYmVoYXZpb3Igb2YgaW50ZXJwcmV0aW5nIHRoZSBm
bGFncyBpcyBhbWJpZ3VvdXMNCj5pbg0KPj4gPnRoZSBzdGFuZGFyZCAobWFpbmx5IFJGQzQ4NjIp
LiBJIHByZXNlbnRlZCBhIGRyYWZ0IGRpc2N1c3NpbmcgTSBmbGFnDQo+PiBiZWhhdmlvcg0KPj4g
PmluIDZtYW4gQGlldGY4NCwgYW5kIHRoZXJlIHdlcmUgc29tZSBmZWVkYmFja3MgYXJndWluZyB0
aGUgc2FtZSBpc3N1ZS4NCj4+ID5UaGlzIGRyYWZ0IGFuYWx5emVkIGFsbCB0aGUgdGhyZWUgZmxh
Z3MsIGFuZCBwcm92aWRlZCB0ZXN0IHJlc3VsdCBvZiBjdXJyZW50DQo+PiA+aW1wbGVtZW50YXRp
b25zLCBpdCBzaG93ZWQgdGhlIGJlaGF2aW9yIG9mIGRpZmZlcmVudCBtYWluc3RyZWFtIGRlc2t0
b3ANCj4+ID5PU2VzIGhhdmUgdmFyaWVkLiBUaGUgYW1iaWd1b3VzIGFuZCB2YXJpYXRpb24gbWln
aHQgY2F1c2Ugb3BlcmF0aW9uYWwNCj4+ID5wcm9ibGVtcywgc3VjaCBhcyByZW51bWJlcmluZyAo
dXNlZCB0byBkaXNjdXNzIGluIDZyZW51bSBXRyBhbmQgYmVlbg0KPj4gPmRvY3VtZW50ZWQgaW4g
dGhlIFdHIGRyYWZ0cyksIGNvbGQgc3RhcnQgcHJvYmxlbSwgYW5kIG1hbmFnZW1lbnQNCj4+ID5n
YXBzIC5ldGMuDQo+PiA+DQo+PiA+WW91ciByZXZpZXcgYW5kIGNvbW1lbnRzIHdvdWxkIGJlIGFw
cHJlY2lhdGVkIHZlcnkgbXVjaC4NCj4+ID4NCj4+ID5BbGwgdGhlIGJlc3QsDQo+PiA+QmluZw0K
Pj4gPg0KPj4gPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+ID4+IEZyb206IGludGVy
bmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10NCj4+
ID4+IFNlbnQ6IE1vbmRheSwgRmVicnVhcnkgMjUsIDIwMTMgNTo1MiBQTQ0KPj4gPj4gVG86IExp
dWJpbmcgKExlbykNCj4+ID4+IENjOiByYm9uaWNhQGp1bmlwZXIubmV0DQo+PiA+PiBTdWJqZWN0
OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yDQo+PiA+PiBkcmFmdC1saXUtYm9uaWNhLWRo
Y3B2Ni1zbGFhYy1wcm9ibGVtLTAxLnR4dA0KPj4gPj4NCj4+ID4+DQo+PiA+PiBBIG5ldyB2ZXJz
aW9uIG9mIEktRCwgZHJhZnQtbGl1LWJvbmljYS1kaGNwdjYtc2xhYWMtcHJvYmxlbS0wMS50eHQN
Cj4+ID4+IGhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgQmluZyBMaXUgYW5kIHBv
c3RlZCB0byB0aGUNCj4+ID4+IElFVEYgcmVwb3NpdG9yeS4NCj4+ID4+DQo+PiA+PiBGaWxlbmFt
ZToJIGRyYWZ0LWxpdS1ib25pY2EtZGhjcHY2LXNsYWFjLXByb2JsZW0NCj4+ID4+IFJldmlzaW9u
OgkgMDENCj4+ID4+IFRpdGxlOgkJIERIQ1B2Ni9TTEFBQyBBZGRyZXNzIENvbmZpZ3VyYXRpb24g
SW50ZXJhY3Rpb24NCj5Qcm9ibGVtDQo+PiA+PiBTdGF0ZW1lbnQNCj4+ID4+IENyZWF0aW9uIGRh
dGU6CSAyMDEzLTAyLTI1DQo+PiA+PiBHcm91cDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCj4+
ID4+IE51bWJlciBvZiBwYWdlczogMTINCj4+ID4+IFVSTDoNCj4+ID4+DQo+PiBodHRwOi8vd3d3
LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1saXUtYm9uaWNhLWRoY3B2Ni1zbGFhYy1w
cm9ibGVtLQ0KPj4gPj4gMDEudHh0DQo+PiA+PiBTdGF0dXM6DQo+PiA+PiBodHRwOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWxpdS1ib25pY2EtZGhjcHY2LXNsYWFjLXByb2JsZW0N
Cj4+ID4+IEh0bWxpemVkOg0KPj4gPj4gaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQt
bGl1LWJvbmljYS1kaGNwdjYtc2xhYWMtcHJvYmxlbS0wMQ0KPj4gPj4gRGlmZjoNCj4+ID4+DQo+
PiBodHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1saXUtYm9uaWNhLWRoY3B2
Ni1zbGFhYy1wcm9ibGVtLTAxDQo+PiA+Pg0KPj4gPj4gQWJzdHJhY3Q6DQo+PiA+PiAgICBUaGlz
IGRvY3VtZW50IGFuYWx5emVzIHRoZSBob3N0IGJlaGF2aW9yIG9mIERIQ1B2Ni9TTEFBQw0KPj4g
aW50ZXJhY3Rpb24NCj4+ID4+ICAgIGlzc3VlLiBJdCByZXZpZXdzIHRoZSBzdGFuZGFyZCBkZWZp
bml0aW9uIG9mIHRoZSBob3N0IGJlaGF2aW9ycyBhbmQNCj4+ID4+ICAgIHByb3ZpZGVzIHRoZSB0
ZXN0IHJlc3VsdHMgb2YgY3VycmVudCBtYWluc3RyZWFtIGltcGxlbWVudGF0aW9ucy4NCj4+IFNv
bWUNCj4+ID4+ICAgIHBvdGVudGlhbCBvcGVyYXRpb25hbCBnYXBzIG9mIHRoZSBpbnRlcmFjdGlv
biBhcmUgYWxzbyBkZXNjcmliZWQuDQo+PiA+Pg0KPj4gPj4NCj4+ID4+DQo+PiA+Pg0KPj4gPj4g
VGhlIElFVEYgU2VjcmV0YXJpYXQNCj4+ID4NCj4+ID5fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KPj4gPnJlbnVtIG1haWxpbmcgbGlzdA0KPj4gPnJlbnVt
QGlldGYub3JnDQo+PiA+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yZW51
bQ0K

From leo.liubing@huawei.com  Tue Feb 26 23:17:47 2013
Return-Path: <leo.liubing@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 8D59221F8814; Tue, 26 Feb 2013 23:17:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.003
X-Spam-Level: 
X-Spam-Status: No, score=-6.003 tagged_above=-999 required=5 tests=[AWL=-0.004, 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 AsLa9Wo3J95p; Tue, 26 Feb 2013 23:17:46 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1516E21F87FB; Tue, 26 Feb 2013 23:17:45 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AOV35449; Wed, 27 Feb 2013 07:17:44 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 27 Feb 2013 07:17:37 +0000
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 27 Feb 2013 07:17:42 +0000
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.101]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.01.0323.007; Wed, 27 Feb 2013 15:17:34 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Sheng Jiang <jiangsheng@huawei.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Thread-Topic: SLAAC/DHCPv6 addr-conf operational gaps
Thread-Index: AQHOE/Dp7oY45oFpuUWdZ8xgw4l8cJiNDEUQgAAsV0CAAAivUIAACN5A
Date: Wed, 27 Feb 2013 07:17:33 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D6DC914@nkgeml506-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> <5D36713D8A4E7348A7E10DF7437A4B923A00E1D3@szxeml545-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923A00E1D3@szxeml545-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
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 07:17:47 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBTaGVuZyBKaWFuZw0KPiBTZW50
OiBXZWRuZXNkYXksIEZlYnJ1YXJ5IDI3LCAyMDEzIDI6NDUgUE0NCj4gVG86IExpdWJpbmcgKExl
byk7IGlwdjZAaWV0Zi5vcmcNCj4gQ2M6IHJlbnVtQGlldGYub3JnDQo+IFN1YmplY3Q6IFJFOiBT
TEFBQy9ESENQdjYgYWRkci1jb25mIG9wZXJhdGlvbmFsIGdhcHMNCj4gDQo+IEhpLCBCaW5nLA0K
PiANCj4gSXQgaXMgYmV0dGVyIHRvIGF0IGxlYXN0IG1lbnRpb24gdGhlIGRpcmVjdGlvbiBvZiBu
ZXh0IHN0ZXAgLSBjbGVhcmx5IHJlZGVmaW5lIHRoZQ0KPiBmbGFnIGNvcnJlc3BvbmRlbnQgaG9z
dCBiZWhhdmlvciBpbiBzdGFuZGFyZHMuDQoNCltCaW5nXSBBZ3JlZS4gVGhhbmtzIGZvciB5b3Vy
IGNsYXJpZmljYXRpb24uDQoNCj4gDQo+IEEgY291cGxlIG9mIG1vcmUgZGV0YWlsZWQgY29tbWVu
dHM6IHlvdSBoYXZlIHVzZWQgd29yZCAiZ2FwIiBzZXZlcmFsDQo+IHRpbWVzLCB3aGlsZSB5b3Ug
ZGlkIG5vdCBjbGVhciBkZXNjcmliZSB3aGF0IGdhcCBpdCBpcy4gWW91IGhhdmUgb25seQ0KPiBk
ZXNjcmliZWQgaXNzdWVzL3Byb2JsZW1zLiBHYXBzIHNob3VsZCBiZSBzb21ldGhpbmcgdGhhdCBp
c3N1ZSBzb2x2ZWQgaWYNCj4geW91IGNvdWxkIGZpbGwgdGhlbS4gU3Vic2VjdGlvbnMgb2YgU2Vj
dGlvbiAzIGFyZSBwcm9ibGVtIHNjZW5hcmlvcy4gQnV0IHlvdXINCj4gc3Vic2VjdGlvbiB0aXRs
ZXMgZG8gbm90IGNsZWFyIGV4cHJlc3MgdGhlIG1lYW5pbmcuDQoNCltCaW5nXSBPSywgSSBjYW4g
bWFrZSBpdCBtb3JlIGNsZWFyIGluIHRoZSBuZXh0IHZlcnNpb24gb3IgaW4gdGhlIG5ldyBzb2x1
dGlvbiBkcmFmdC4gVGhhbmtzIGZvciB5b3VyIGNhcmVmdWwgcmV2aWV3Lg0KDQpCLlIuDQpCaW5n
DQoNCj4gDQo+IENoZWVycywNCj4gDQo+IFNoZW5nDQo+IA0KPiA+LS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj4gPkZyb206IExpdWJpbmcgKExlbykNCj4gPlNlbnQ6IFdlZG5lc2RheSwgRmVi
cnVhcnkgMjcsIDIwMTMgMjoxNyBQTQ0KPiA+VG86IFNoZW5nIEppYW5nOyBpcHY2QGlldGYub3Jn
DQo+ID5DYzogcmVudW1AaWV0Zi5vcmcNCj4gPlN1YmplY3Q6IFJFOiBTTEFBQy9ESENQdjYgYWRk
ci1jb25mIG9wZXJhdGlvbmFsIGdhcHMNCj4gPg0KPiA+SGksIFNoZW5nDQo+ID4NCj4gPlRoYW5r
cyBmb3IgeW91ciBjb21tZW50cy4NCj4gPlRoaXMgaXMgdGhlIGZpcnN0IHN0ZXAsIHRvIHNlZSBp
ZiB0aGVyZSBpcyBjb25zZW5zdXMgb2YgYWdyZWVpbmcgdGhlIHByb2JsZW1zDQo+ID5zaG91bGQg
YmUgZml4ZWQgaW4gY3VycmVudCBzdGFuZGFyZC4gSWYgc28sIHdlJ2xsIHN1Ym1pdCBhIGRyYWZ0
IHRvIGZpeCB0aGUNCj4gPmFtYmlndW91cyBpc3N1ZS4NCj4gPg0KPiA+Qi5SLg0KPiA+QmluZw0K
PiA+DQo+ID4NCj4gPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPj4gRnJvbTogU2hl
bmcgSmlhbmcNCj4gPj4gU2VudDogV2VkbmVzZGF5LCBGZWJydWFyeSAyNywgMjAxMyAxMTozNyBB
TQ0KPiA+PiBUbzogTGl1YmluZyAoTGVvKTsgaXB2NkBpZXRmLm9yZw0KPiA+PiBDYzogcmVudW1A
aWV0Zi5vcmcNCj4gPj4gU3ViamVjdDogUkU6IFNMQUFDL0RIQ1B2NiBhZGRyLWNvbmYgb3BlcmF0
aW9uYWwgZ2Fwcw0KPiA+Pg0KPiA+PiBUaGlzIGhhcyBiZWVuIGEgaGlzdG9yaWMgaXNzdWUuIEFs
dGhvdWdoIHRoZXJlIHdhcyBkaXNjdXNzaW9ucyBzZXZlcmFsDQo+IHRpbWVzLA0KPiA+PiB0aGUg
c3BlY2lmaWNhdGlvbiBzdGlsbCByZW1haW4gYW1iaWd1b3VzLiBUaGUgZGlmZmVyZW5jZXMgaW4g
T1MNCj4gPj4gaW1wbGVtZW50YXRpb25zIGFyZSBnb29kIHByb29mIHRoYXQgd2UgbmVlZCB0byBk
byBzb21ldGhpbmcgaW4gSUVURi4NCj4gPj4NCj4gPj4gVGhpcyBkb2N1bWVudCBoYXMgd2VsbCBk
ZXNjcmliZWQgdGhlIGN1cnJlbnQgc3RhbmRhcmQgc3RhdHVzIGFuZCByZWFsaXR5DQo+ID4+IG9w
ZXJhdGlvbmFsIGlzc3Vlcy4gSG93ZXZlciwgZm9yIG1lLCB0aGlzIGRvY3VtZW50IGZhaWxzIHRv
IHN1Z2dlc3Qgd2hhdA0KPiA+d2UNCj4gPj4gbWF5IGRvIHRvIGZpeCB0aGlzIGlzc3VlLCBuZWl0
aGVyIGluIHRoZSBnYXAgc2VjdGlvbiBvciBhcyBjb25jbHVzaW9uLiBJdCBpcw0KPiA+Y2xlYXIN
Cj4gPj4gdGhhdCBwYXJ0IG9mIFJGQzQ4NjIgbmVlZHMgdG8gYmUgdXBkYXRlZCB0byBtYWtlIHRo
ZSBjb25maWd1cmF0aW9uDQo+ID4+IGJlaGF2aW9yIGNsZWFyIGFuZCBjb25zaXN0ZW50LiBGb3Ig
dGhhdCwgdGhpcyBkb2N1bWVudCBmYWlscyB0byBnaXZlIGENCj4gZmVhc2libGUNCj4gPj4gcHJv
cG9zYWwuIE1heWJlLCB0aGUgYXV0aG9ycyBoYXMgc2F2ZWQgdGhhdCBmb3IgYW5vdGhlciBmb2xs
b3cgdXANCj4gc3RhbmRhcmQNCj4gPj4gdHJhY2sgZG9jdW1lbnQuDQo+ID4+DQo+ID4+IEJlc3Qg
cmVnYXJkcywNCj4gPj4NCj4gPj4gU2hlbmcNCj4gPj4NCj4gPj4gPi0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQo+ID4+ID5Gcm9tOiByZW51bS1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86cmVu
dW0tYm91bmNlc0BpZXRmLm9yZ10gT24NCj4gPj4gQmVoYWxmDQo+ID4+ID5PZiBMaXViaW5nIChM
ZW8pDQo+ID4+ID5TZW50OiBUdWVzZGF5LCBGZWJydWFyeSAyNiwgMjAxMyAzOjE0IFBNDQo+ID4+
ID5UbzogaXB2NkBpZXRmLm9yZzsgdjZvcHNAaWV0Zi5vcmcNCj4gPj4gPkNjOiByZW51bUBpZXRm
Lm9yZw0KPiA+PiA+U3ViamVjdDogW3JlbnVtXSBTTEFBQy9ESENQdjYgYWRkci1jb25mIG9wZXJh
dGlvbmFsIGdhcHMNCj4gPj4gPg0KPiA+PiA+SGksIDZtYW4gJiB2Nm9wcw0KPiA+PiA+DQo+ID4+
ID5XZSBzdWJtaXR0ZWQgYSBuZXcgZHJhZnQgdG8gZGlzY3VzcyB0aGUgU0xBQUMvREhDUHY2IGlu
dGVyYWN0aW9uDQo+IGdhcHMuDQo+ID4+ID4NCj4gPj4gPkFzIHdlIGtub3cgdGhlcmUgYXJlIHNl
dmVyYWwgZmxhZ3MgaW4gUkEgbWVzc2FnZXMgcmVnYXJkaW5nIHdpdGggdGhlDQo+IGhvc3QNCj4g
Pj4gPmNvbmZpZ3VyYXRpb24gYmVoYXZpb3IsIHdoaWNoIGFyZSBBIChBdXRvbm9tb3VzKSBmbGFn
LCBNIChNYW5hZ2VkKQ0KPiBmbGFnLA0KPiA+PiA+YW5kIE8gKE90aGVyY29uZmlnKSBmbGFnLg0K
PiA+PiA+Rm9yIHNvbWUgcmVhc29uLCB0aGUgaG9zdCBiZWhhdmlvciBvZiBpbnRlcnByZXRpbmcg
dGhlIGZsYWdzIGlzDQo+IGFtYmlndW91cw0KPiA+aW4NCj4gPj4gPnRoZSBzdGFuZGFyZCAobWFp
bmx5IFJGQzQ4NjIpLiBJIHByZXNlbnRlZCBhIGRyYWZ0IGRpc2N1c3NpbmcgTSBmbGFnDQo+ID4+
IGJlaGF2aW9yDQo+ID4+ID5pbiA2bWFuIEBpZXRmODQsIGFuZCB0aGVyZSB3ZXJlIHNvbWUgZmVl
ZGJhY2tzIGFyZ3VpbmcgdGhlIHNhbWUNCj4gaXNzdWUuDQo+ID4+ID5UaGlzIGRyYWZ0IGFuYWx5
emVkIGFsbCB0aGUgdGhyZWUgZmxhZ3MsIGFuZCBwcm92aWRlZCB0ZXN0IHJlc3VsdCBvZiBjdXJy
ZW50DQo+ID4+ID5pbXBsZW1lbnRhdGlvbnMsIGl0IHNob3dlZCB0aGUgYmVoYXZpb3Igb2YgZGlm
ZmVyZW50IG1haW5zdHJlYW0NCj4gZGVza3RvcA0KPiA+PiA+T1NlcyBoYXZlIHZhcmllZC4gVGhl
IGFtYmlndW91cyBhbmQgdmFyaWF0aW9uIG1pZ2h0IGNhdXNlIG9wZXJhdGlvbmFsDQo+ID4+ID5w
cm9ibGVtcywgc3VjaCBhcyByZW51bWJlcmluZyAodXNlZCB0byBkaXNjdXNzIGluIDZyZW51bSBX
RyBhbmQgYmVlbg0KPiA+PiA+ZG9jdW1lbnRlZCBpbiB0aGUgV0cgZHJhZnRzKSwgY29sZCBzdGFy
dCBwcm9ibGVtLCBhbmQgbWFuYWdlbWVudA0KPiA+PiA+Z2FwcyAuZXRjLg0KPiA+PiA+DQo+ID4+
ID5Zb3VyIHJldmlldyBhbmQgY29tbWVudHMgd291bGQgYmUgYXBwcmVjaWF0ZWQgdmVyeSBtdWNo
Lg0KPiA+PiA+DQo+ID4+ID5BbGwgdGhlIGJlc3QsDQo+ID4+ID5CaW5nDQo+ID4+ID4NCj4gPj4g
Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPj4gPj4gRnJvbTogaW50ZXJuZXQtZHJh
ZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXQ0KPiA+PiA+PiBT
ZW50OiBNb25kYXksIEZlYnJ1YXJ5IDI1LCAyMDEzIDU6NTIgUE0NCj4gPj4gPj4gVG86IExpdWJp
bmcgKExlbykNCj4gPj4gPj4gQ2M6IHJib25pY2FAanVuaXBlci5uZXQNCj4gPj4gPj4gU3ViamVj
dDogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvcg0KPiA+PiA+PiBkcmFmdC1saXUtYm9uaWNh
LWRoY3B2Ni1zbGFhYy1wcm9ibGVtLTAxLnR4dA0KPiA+PiA+Pg0KPiA+PiA+Pg0KPiA+PiA+PiBB
IG5ldyB2ZXJzaW9uIG9mIEktRCwgZHJhZnQtbGl1LWJvbmljYS1kaGNwdjYtc2xhYWMtcHJvYmxl
bS0wMS50eHQNCj4gPj4gPj4gaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBCaW5n
IExpdSBhbmQgcG9zdGVkIHRvIHRoZQ0KPiA+PiA+PiBJRVRGIHJlcG9zaXRvcnkuDQo+ID4+ID4+
DQo+ID4+ID4+IEZpbGVuYW1lOgkgZHJhZnQtbGl1LWJvbmljYS1kaGNwdjYtc2xhYWMtcHJvYmxl
bQ0KPiA+PiA+PiBSZXZpc2lvbjoJIDAxDQo+ID4+ID4+IFRpdGxlOgkJIERIQ1B2Ni9TTEFBQyBB
ZGRyZXNzIENvbmZpZ3VyYXRpb24gSW50ZXJhY3Rpb24NCj4gPlByb2JsZW0NCj4gPj4gPj4gU3Rh
dGVtZW50DQo+ID4+ID4+IENyZWF0aW9uIGRhdGU6CSAyMDEzLTAyLTI1DQo+ID4+ID4+IEdyb3Vw
OgkJIEluZGl2aWR1YWwgU3VibWlzc2lvbg0KPiA+PiA+PiBOdW1iZXIgb2YgcGFnZXM6IDEyDQo+
ID4+ID4+IFVSTDoNCj4gPj4gPj4NCj4gPj4NCj4gaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5l
dC1kcmFmdHMvZHJhZnQtbGl1LWJvbmljYS1kaGNwdjYtc2xhYWMtcHJvYmxlbS0NCj4gPj4gPj4g
MDEudHh0DQo+ID4+ID4+IFN0YXR1czoNCj4gPj4gPj4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYu
b3JnL2RvYy9kcmFmdC1saXUtYm9uaWNhLWRoY3B2Ni1zbGFhYy1wcm9ibGVtDQo+ID4+ID4+IEh0
bWxpemVkOg0KPiA+PiA+PiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1saXUtYm9u
aWNhLWRoY3B2Ni1zbGFhYy1wcm9ibGVtLTAxDQo+ID4+ID4+IERpZmY6DQo+ID4+ID4+DQo+ID4+
DQo+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWxpdS1ib25pY2EtZGhj
cHY2LXNsYWFjLXByb2JsZW0tMDENCj4gPj4gPj4NCj4gPj4gPj4gQWJzdHJhY3Q6DQo+ID4+ID4+
ICAgIFRoaXMgZG9jdW1lbnQgYW5hbHl6ZXMgdGhlIGhvc3QgYmVoYXZpb3Igb2YgREhDUHY2L1NM
QUFDDQo+ID4+IGludGVyYWN0aW9uDQo+ID4+ID4+ICAgIGlzc3VlLiBJdCByZXZpZXdzIHRoZSBz
dGFuZGFyZCBkZWZpbml0aW9uIG9mIHRoZSBob3N0IGJlaGF2aW9ycyBhbmQNCj4gPj4gPj4gICAg
cHJvdmlkZXMgdGhlIHRlc3QgcmVzdWx0cyBvZiBjdXJyZW50IG1haW5zdHJlYW0gaW1wbGVtZW50
YXRpb25zLg0KPiA+PiBTb21lDQo+ID4+ID4+ICAgIHBvdGVudGlhbCBvcGVyYXRpb25hbCBnYXBz
IG9mIHRoZSBpbnRlcmFjdGlvbiBhcmUgYWxzbyBkZXNjcmliZWQuDQo+ID4+ID4+DQo+ID4+ID4+
DQo+ID4+ID4+DQo+ID4+ID4+DQo+ID4+ID4+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQo+ID4+ID4N
Cj4gPj4gPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
ID4+ID5yZW51bSBtYWlsaW5nIGxpc3QNCj4gPj4gPnJlbnVtQGlldGYub3JnDQo+ID4+ID5odHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JlbnVtDQo=

From wwwrun@rfc-editor.org  Wed Feb 27 11:35:39 2013
Return-Path: <wwwrun@rfc-editor.org>
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 A3CBA21F8ACE; Wed, 27 Feb 2013 11:35:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.328
X-Spam-Level: 
X-Spam-Status: No, score=-102.328 tagged_above=-999 required=5 tests=[AWL=0.272, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 3qhzXu1DrIIi; Wed, 27 Feb 2013 11:35:39 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:126c::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 3C8BF21F8ABD; Wed, 27 Feb 2013 11:35:39 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8457172E14D; Wed, 27 Feb 2013 11:34:22 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130227193422.8457172E14D@rfc-editor.org>
Date: Wed, 27 Feb 2013 11:34:22 -0800 (PST)
Cc: renum@ietf.org, rfc-editor@rfc-editor.org
Subject: [renum] RFC 6866 on Problem Statement for Renumbering IPv6 Hosts with Static Addresses in Enterprise Networks
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 19:35:39 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6866

        Title:      Problem Statement for Renumbering IPv6 
                    Hosts with Static Addresses in Enterprise 
                    Networks 
        Author:     B. Carpenter, S. Jiang
        Status:     Informational
        Stream:     IETF
        Date:       February 2013
        Mailbox:    brian.e.carpenter@gmail.com, 
                    jiangsheng@huawei.com
        Pages:      11
        Characters: 26524
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-6renum-static-problem-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6866.txt

This document analyses the problems of updating the IPv6 addresses of
hosts in enterprise networks that, for operational reasons, require
static addresses.

This document is a product of the IPv6 Site Renumbering Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From wwwrun@rfc-editor.org  Wed Feb 27 11:36:41 2013
Return-Path: <wwwrun@rfc-editor.org>
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 9238A21F8B64; Wed, 27 Feb 2013 11:36:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.33
X-Spam-Level: 
X-Spam-Status: No, score=-102.33 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 Nr9N0IxT9HvB; Wed, 27 Feb 2013 11:36:41 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:126c::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 3E8C621F8B37; Wed, 27 Feb 2013 11:36:39 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id F1C1672E14E; Wed, 27 Feb 2013 11:35:15 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130227193515.F1C1672E14E@rfc-editor.org>
Date: Wed, 27 Feb 2013 11:35:15 -0800 (PST)
Cc: renum@ietf.org, rfc-editor@rfc-editor.org
Subject: [renum] RFC 6879 on IPv6 Enterprise Network Renumbering Scenarios, Considerations, and Methods
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 19:36:41 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6879

        Title:      IPv6 Enterprise Network Renumbering Scenarios, 
                    Considerations, and Methods 
        Author:     S. Jiang, B. Liu,
                    B. Carpenter
        Status:     Informational
        Stream:     IETF
        Date:       February 2013
        Mailbox:    jiangsheng@huawei.com, 
                    leo.liubing@huawei.com, 
                    brian.e.carpenter@gmail.com
        Pages:      17
        Characters: 38833
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-6renum-enterprise-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6879.txt

This document analyzes events that cause renumbering and describes
the current renumbering methods.  These are described in three
categories: those applicable during network design, those applicable
during preparation for renumbering, and those applicable during the
renumbering operation.

This document is a product of the IPv6 Site Renumbering Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


