
From leo.liubing@huawei.com  Wed Aug  1 13:37:25 2012
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 0260911E81B6; Wed,  1 Aug 2012 13:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.211
X-Spam-Level: 
X-Spam-Status: No, score=-6.211 tagged_above=-999 required=5 tests=[AWL=0.388,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 CI7qyCgjQVv4; Wed,  1 Aug 2012 13:37:24 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 0F62511E819B; Wed,  1 Aug 2012 13:37:24 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AIP49853; Wed, 01 Aug 2012 12:37:23 -0800 (PST)
Received: from DFWEML403-HUB.china.huawei.com (10.193.5.151) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 1 Aug 2012 13:35:57 -0700
Received: from SZXEML411-HUB.china.huawei.com (10.82.67.138) by dfweml403-hub.china.huawei.com (10.193.5.151) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 1 Aug 2012 13:35:55 -0700
Received: from SZXEML509-MBS.china.huawei.com ([10.82.67.53]) by szxeml411-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Thu, 2 Aug 2012 04:35:49 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Karl Auer <kauer@biplane.com.au>, IETF IPv6 <ipv6@ietf.org>, "renum@ietf.org" <renum@ietf.org>
Thread-Topic: about DHCPv6/SLAAC interaction
Thread-Index: Ac1vfdpTtZ0CYGh1QuaTQPkL4ATaQwADX/+AACQkRMs=
Date: Wed, 1 Aug 2012 20:35:48 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F452932BC36@szxeml509-mbs>
References: <8AE0F17B87264D4CAC7DE0AA6C406F452932B863@szxeml509-mbs>, <1343816057.26898.384.camel@karl>
In-Reply-To: <1343816057.26898.384.camel@karl>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.24.1.68]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [renum] about DHCPv6/SLAAC interaction
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, 01 Aug 2012 20:37:25 -0000

Hi, all

Firstly, thanks for Karl's elaborate analysis and solution proposal for the=
 M/O issue. I think that's definitely reasonable reference if we want to fi=
x the issue.

But as some comments showed in this morning's 6man meeting, some people tho=
ught it is not necessary to fix the M/O issue in standard, because it used =
to be long discussions about it, and current SLAAC standard (RFC4862) was j=
ust based on the discussion result at that time.
May I venture to argue that, "had been discussed before" might not be reaso=
nable enough to deal with current problems. I think the situation has chang=
ed since the RFC4862 published, more and more real IPv6 deployments are eme=
rging, then people find it is quite confusing of the ambiguous M/O definiti=
on, this real-network problem may be much more sensitive than we imagined/d=
iscussed to be when writing RFC4862.

We have two address autoconfiguration modes (SLAAC/DHCPv6)  in IPv6, which =
is one of the most significant differences between IPv4, people who have re=
ally deployed IPv6 may notice more importance of SLAAC/DHCPv6 interaction t=
han we discussed before, at least I've learned the requirements from both o=
ffline and on the mics, maybe it is not comprehensive enough, but at least =
it's considerable.

So, my personal preference is similar with Karl's, we might need additional=
 flags to cover the SLAAC/DHCPv6 interaction semantics. And in 6renum, we a=
lso discussed some new semantics requirements (see in the draft, and the se=
ction 5.1 in 6renum WG item: http://tools.ietf.org/html/draft-ietf-6renum-g=
ap-analysis-02 ), I think they are also considerable.

Regards,
Bing

________________________________________
From: ipv6-bounces@ietf.org [ipv6-bounces@ietf.org] on behalf of Karl Auer =
[kauer@biplane.com.au]
Sent: Wednesday, August 01, 2012 03:14
To: IETF IPv6
Subject: Re: about DHCPv6/SLAAC interaction

On Wed, 2012-08-01 at 01:06 +0000, Liubing (Leo) wrote:
> You mentioned the ambiguous M flag in RA, indeed this is a problem,
> and it has been disscussed in 6renum WG.
>
> So if you're still consern about the issue, looking forward to hear
> some comments from you, either on the mics or in the mail.

[Leo sent me the above off list, but I post my reply here with his
permission]

Thanks!

A host should always be allowed to do DHCPv6 in the *absence* of
information to the contrary; this is no different to NOT doing DHCPv6 in
the absence of information. Also, a host may be in a self-contained or
isolated network, i.e., one without a router, but with a DHCP server. So
NOT receiving RAs is no reason NOT to do DHCPv6. Nor is it a reason to
do it either, of course - i.e., it's up to the host :-)

I'll preface all this my saying that I think the M and O flags as
generally implemented and used are pretty much useless. The best thing
to do with them would be to deprecate them altogether.

If they must be retained, then I feel that the semantics should be as
follows, and as far as I can tell from the RFC, this is all allowed:

......=

From leo.liubing@huawei.com  Wed Aug  1 21:27:38 2012
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 56E0411E8122; Wed,  1 Aug 2012 21:27:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.966
X-Spam-Level: 
X-Spam-Status: No, score=-5.966 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_MED=-4]
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 2Rfr3wqArewP; Wed,  1 Aug 2012 21:27:37 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id E013711E8109; Wed,  1 Aug 2012 21:27:36 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AII75950; Wed, 01 Aug 2012 20:27:36 -0800 (PST)
Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 1 Aug 2012 21:24:03 -0700
Received: from SZXEML420-HUB.china.huawei.com (10.82.67.159) by dfweml404-hub.china.huawei.com (10.193.5.203) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 1 Aug 2012 21:24:07 -0700
Received: from SZXEML509-MBS.china.huawei.com ([10.82.67.53]) by szxeml420-hub.china.huawei.com ([10.82.67.159]) with mapi id 14.01.0323.003; Thu, 2 Aug 2012 12:23:11 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Karl Auer <kauer@biplane.com.au>, IETF IPv6 <ipv6@ietf.org>, "renum@ietf.org" <renum@ietf.org>
Thread-Topic: about DHCPv6/SLAAC interaction
Thread-Index: Ac1vfdpTtZ0CYGh1QuaTQPkL4ATaQwADX/+AACQkRMv//8fwgIAAr5Oc
Date: Thu, 2 Aug 2012 04:23:09 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F452932BF44@szxeml509-mbs>
References: <8AE0F17B87264D4CAC7DE0AA6C406F452932B863@szxeml509-mbs> ,<1343816057.26898.384.camel@karl> <8AE0F17B87264D4CAC7DE0AA6C406F452932BC36@szxeml509-mbs>, <1343866109.26898.507.camel@karl>
In-Reply-To: <1343866109.26898.507.camel@karl>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.24.1.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "Alexandru Petrescu \[alexandru.petrescu@gmail.com\]" <alexandru.petrescu@gmail.com>
Subject: Re: [renum] about DHCPv6/SLAAC interaction
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: Thu, 02 Aug 2012 04:27:38 -0000

Hi, Karl

Thanks for your reply, now I understand your arguments clearly.=20

I think our common view is "ambiguity in not good". Then your way is just d=
eprecating them; if don't deprecate, then make it clear. But I just have th=
e opposite approach: since it's ambiguous, we need at least make them clear=
, and beyond, we need more SLAAC/DHCPv6 interaction than the original M/O f=
lags semantics.

Let me explain what are "the current problems":
[1]. Renumbering problems.=20
In RFC5887(Renumbering still needs work), section 5.1.1 says clearly:   =20
   "Until this ambiguous behaviour is clearly resolved by the IETF,
   operational problems are to be expected, since different host
   operating systems have taken different approaches.  This makes it
   difficult for a site network manager to configure systems in such a
   way that all hosts boot in a consistent way.  Hosts will start SLAAC,
   if so directed by appropriately configured RA messages.  However, if
   one operating system also starts a DHCPv6 client by default, and
   another one starts it only when it receives the M bit, systematic
   address management is impeded."
Our test had identified the host OSes have tanken different apporoaches. Fo=
r the above mentioned "systematic address management" , we already discusse=
d several instance, as I described in the draft:
    - The site manager wants the host to do DHCPv6 when online. Current pra=
ctise is sending RA M=3D1 and don't include PIO, however, how the OSes will=
 behave is not controlled by the site.
    - The site manager wants the SLAAC-configured hosts to do DHCPv6 (e.g. =
adding a multihomed uplink who uses DHCPv6 for address configuration).  For=
 some OSes, there's just no availeble method.
    - The site manager wants the DHCPv6-configured hosts switch to SLAAC. I=
f you don't interprete M=3D0 as prescriptive, the only way is either just w=
aiting for the DHCPv6 lease time expires, or initial DHCPv6-reocnfiguration=
 from the server side. But I don't think it  is an efficient way when  renu=
mbering. If the lease time is too long, the problem is more serious.  For D=
HCPv6-reocnfiguration, it is only unicast, and stateful, not proper for bul=
k use.=20

[2] Requirement from ISP
ISPs have strong requirement of strictly controlling the CPE behaving as th=
ey expect. There's an instance I learned, an ISP deployed stateless DHCPv6 =
in their IPv6 network, which means they required the CPE to=20
configure addresses through SLAAC and other parameters through DHCPv6. Sinc=
e the ambiguity in standard, they had to directly specify the requirements =
to the CPE vendor, which means, universal CPE may not be availeble in IPv6 =
networks unless we have clear definition in standard.

[3] I think Alexandru's argument of mobile nodes is another good example.

Regards,
Bing



________________________________________
From: ipv6-bounces@ietf.org [ipv6-bounces@ietf.org] on behalf of Karl Auer =
[kauer@biplane.com.au]
Sent: Wednesday, August 01, 2012 17:08
To: IETF IPv6; renum@ietf.org
Subject: RE: about DHCPv6/SLAAC interaction

On Wed, 2012-08-01 at 20:35 +0000, Liubing (Leo) wrote:
> May I venture to argue that, "had been discussed before" might not be
> reasonable enough to deal with current problems.

What exactly are "the current problems"?

It seems to me there are only two:

- it is not explicit whether M means a host "must", "should" or "may"
use DHCPv6 to obtain an address. It is fairly clear in practice that
this is a "should"

- it is not explicit that the M and O flags are completely independent
of each other. Common practice is to treat them as independent, and I
can see no good reason to link them in the RFC or anywhere else.

- there is a question about whether a host obtaining a DHCPv6 address
should NOT perform SLAAC. Since the RFC certainly doesn't say it should,
it is a mystery to me why people think DHCPv6 excludes SLAAC. Access to
addresses via DHCPv6 can be completely controlled on a subnet by subnet
basis in the DHCP server, and SLAAC can be completely controlled on a
subnet by subnet basis using the autoconf flag in RAs.

- if I were King of the World I would deprecate both flags. They serve
no useful purpose.

> this real-network problem may be much more sensitive than we
> imagined/discussed to be when writing RFC4862.

Again, I don't see the issue(s) here.

> So, my personal preference is similar with Karl's, we might need
> additional flags to cover the SLAAC/DHCPv6 interaction semantics.

That is NOT my preference. My preference is to deprecate both flags. My
second preference is to clarify as above. All that stuff about
additional flags was thinking aloud about how M/O could be made
mandatory; it was certainly NOT a suggestion that they *should* be made
mandatory.

>  And in 6renum, we also discussed some new semantics requirements (see
> in the draft, and the section 5.1 in 6renum WG item:
> http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-02 ),

I've just read that doc and as far as DHCP and SLAAC go, it seems to be
composed mostly of questions.

I really think the draft should state what the *problems* are that it
seeks to solve.

Regards, K.

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)
http://www.biplane.com.au/kauer
http://www.biplane.com.au/blog

GPG fingerprint: AE1D 4868 6420 AD9A A698 5251 1699 7B78 4EEE 6017
Old fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------=

From kauer@biplane.com.au  Wed Aug  1 17:08:58 2012
Return-Path: <kauer@biplane.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 F212F11E809B; Wed,  1 Aug 2012 17:08:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, J_CHICKENPOX_21=0.6]
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 3fnRv-gFGedW; Wed,  1 Aug 2012 17:08:57 -0700 (PDT)
Received: from ipmail06.adl2.internode.on.net (ipmail06.adl2.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:2:6]) by ietfa.amsl.com (Postfix) with ESMTP id 6AC9111E80EC; Wed,  1 Aug 2012 17:08:54 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApMBAL7EGVCWZX+7/2dsb2JhbAANOIV7tj4BAQEDASNbCwsYAgImAgJXBgEShhGBdhGpLG6TKoEhkB+BEgOWW4l5h3GBTQ
Received: from eth4284.nsw.adsl.internode.on.net (HELO [192.168.1.200]) ([150.101.127.187]) by ipmail06.adl2.internode.on.net with ESMTP; 02 Aug 2012 09:38:45 +0930
From: Karl Auer <kauer@biplane.com.au>
To: IETF IPv6 <ipv6@ietf.org>, "renum@ietf.org" <renum@ietf.org>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F452932BC36@szxeml509-mbs>
References: <8AE0F17B87264D4CAC7DE0AA6C406F452932B863@szxeml509-mbs> ,<1343816057.26898.384.camel@karl> <8AE0F17B87264D4CAC7DE0AA6C406F452932BC36@szxeml509-mbs>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 02 Aug 2012 10:08:29 +1000
Message-ID: <1343866109.26898.507.camel@karl>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 01 Aug 2012 22:48:24 -0700
Subject: Re: [renum] about DHCPv6/SLAAC interaction
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: Thu, 02 Aug 2012 00:08:58 -0000

On Wed, 2012-08-01 at 20:35 +0000, Liubing (Leo) wrote:
> May I venture to argue that, "had been discussed before" might not be
> reasonable enough to deal with current problems.

What exactly are "the current problems"?

It seems to me there are only two:

- it is not explicit whether M means a host "must", "should" or "may"
use DHCPv6 to obtain an address. It is fairly clear in practice that
this is a "should"

- it is not explicit that the M and O flags are completely independent
of each other. Common practice is to treat them as independent, and I
can see no good reason to link them in the RFC or anywhere else.

- there is a question about whether a host obtaining a DHCPv6 address
should NOT perform SLAAC. Since the RFC certainly doesn't say it should,
it is a mystery to me why people think DHCPv6 excludes SLAAC. Access to
addresses via DHCPv6 can be completely controlled on a subnet by subnet
basis in the DHCP server, and SLAAC can be completely controlled on a
subnet by subnet basis using the autoconf flag in RAs.

- if I were King of the World I would deprecate both flags. They serve
no useful purpose.

> this real-network problem may be much more sensitive than we
> imagined/discussed to be when writing RFC4862.

Again, I don't see the issue(s) here.

> So, my personal preference is similar with Karl's, we might need
> additional flags to cover the SLAAC/DHCPv6 interaction semantics.

That is NOT my preference. My preference is to deprecate both flags. My
second preference is to clarify as above. All that stuff about
additional flags was thinking aloud about how M/O could be made
mandatory; it was certainly NOT a suggestion that they *should* be made
mandatory.

>  And in 6renum, we also discussed some new semantics requirements (see
> in the draft, and the section 5.1 in 6renum WG item:
> http://tools.ietf.org/html/draft-ietf-6renum-gap-analysis-02 ),

I've just read that doc and as far as DHCP and SLAAC go, it seems to be
composed mostly of questions.

I really think the draft should state what the *problems* are that it
seeks to solve.

Regards, K.
 
-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)
http://www.biplane.com.au/kauer
http://www.biplane.com.au/blog

GPG fingerprint: AE1D 4868 6420 AD9A A698 5251 1699 7B78 4EEE 6017
Old fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687


From tore.anderson@redpill-linpro.com  Thu Aug  2 01:20:48 2012
Return-Path: <tore.anderson@redpill-linpro.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 EEA2021F8C40; Thu,  2 Aug 2012 01:20:47 -0700 (PDT)
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=[BAYES_00=-2.599]
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 P7lLIvI60Ant; Thu,  2 Aug 2012 01:20:46 -0700 (PDT)
Received: from zimbra.redpill-linpro.com (zimbra.redpill-linpro.com [87.238.49.234]) by ietfa.amsl.com (Postfix) with ESMTP id DDF7C21F8C44; Thu,  2 Aug 2012 01:20:44 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.redpill-linpro.com (Postfix) with ESMTP id B20681820018; Thu,  2 Aug 2012 10:20:42 +0200 (CEST)
X-Virus-Scanned: amavisd-new at claudius.linpro.no
Received: from zimbra.redpill-linpro.com ([127.0.0.1]) by localhost (zimbra.redpill-linpro.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sJqE+yHI5Frw; Thu,  2 Aug 2012 10:20:42 +0200 (CEST)
Received: from echo.linpro.no (echo.linpro.no [87.238.42.42]) by zimbra.redpill-linpro.com (Postfix) with ESMTPSA id 2727D1820004; Thu,  2 Aug 2012 10:20:42 +0200 (CEST)
Message-ID: <501A3859.6080300@redpill-linpro.com>
Date: Thu, 02 Aug 2012 10:20:41 +0200
From: Tore Anderson <tore.anderson@redpill-linpro.com>
Organization: Redpill Linpro AS
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0
MIME-Version: 1.0
To: Karl Auer <kauer@biplane.com.au>
References: <8AE0F17B87264D4CAC7DE0AA6C406F452932B863@szxeml509-mbs> , <1343816057.26898.384.camel@karl> <8AE0F17B87264D4CAC7DE0AA6C406F452932BC36@szxeml509-mbs> <1343866109.26898.507.camel@karl>
In-Reply-To: <1343866109.26898.507.camel@karl>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Thu, 02 Aug 2012 02:03:14 -0700
Cc: IETF IPv6 <ipv6@ietf.org>, "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] about DHCPv6/SLAAC interaction
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: Thu, 02 Aug 2012 08:20:48 -0000

* Karl Auer

> - it is not explicit that the M and O flags are completely
> independent of each other. Common practice is to treat them as
> independent, and I can see no good reason to link them in the RFC or
> anywhere else.

RFC 4861 section 4.2 seems to me to be pretty clear about this:

«If the M flag is set, the O flag is redundant and can be ignored
because DHCPv6 will return all available configuration information.»

So the operational value of O is (M OR O), as I understand it.

Best regards,
-- 
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com

From wesley.george@twcable.com  Fri Aug 24 11:22:00 2012
Return-Path: <wesley.george@twcable.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 0FD4121F861C for <renum@ietfa.amsl.com>; Fri, 24 Aug 2012 11:21:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.333
X-Spam-Level: 
X-Spam-Status: No, score=0.333 tagged_above=-999 required=5 tests=[AWL=-0.805,  BAYES_50=0.001, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,  HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-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 OxjmrhVvyxm0 for <renum@ietfa.amsl.com>; Fri, 24 Aug 2012 11:21:56 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id AB7BF21F85F4 for <renum@ietf.org>; Fri, 24 Aug 2012 11:21:53 -0700 (PDT)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.80,304,1344225600";  d="scan'208,217";a="429218603"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 24 Aug 2012 14:21:24 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Fri, 24 Aug 2012 14:21:52 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "renum@ietf.org" <renum@ietf.org>
Date: Fri, 24 Aug 2012 14:21:51 -0400
Thread-Topic: Comment on 6renum-static-problem
Thread-Index: Ac2CJVStljA2KqEeSqCL1fMYliNoug==
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD592303AFB9E5@PRVPEXVS15.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_2671C6CDFBB59E47B64C10B3E0BD592303AFB9E5PRVPEXVS15corpt_"
MIME-Version: 1.0
Cc: "draft-ietf-6renum-static-problem@tools.ietf.org" <draft-ietf-6renum-static-problem@tools.ietf.org>
Subject: [renum] Comment on 6renum-static-problem
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, 24 Aug 2012 18:22:00 -0000

--_000_2671C6CDFBB59E47B64C10B3E0BD592303AFB9E5PRVPEXVS15corpt_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

You may want to include some references to RFC6250 (specifically section 3.=
2) when discussing the problems around the assumptions of the need or possi=
bility for static addresses. I think some of the language in that document =
reinforces the idea that the need for static addressing is often based on f=
aulty assumptions about addressing, and would complement the text in this d=
raft nicely.

Also, this draft does a reasonable job at documenting some of the historica=
l reasons for choosing to use static addresses. However, I think that it mi=
ght be useful for this document to categorize these into use cases that the=
 WG agrees still legitimately require static addressing, as distinct from t=
hose where workarounds exist that would enable things that normally use sta=
tic addressing to move to dynamically-assigned addresses.
For example, the use case about small networks without DNS resources is by =
no means an unsolvable problem, or even a particularly difficult one to res=
olve given the relative ease of setting up a DNS server, but I believe that=
 there are examples where the workaround is either unavailable or sufficien=
tly onerous as to not be commonly used. Since this is meant to be a compani=
on to the gap analysis document, identifying those gaps would be helpful, a=
s it would inform future work to resolve some of those issues or make the w=
orkarounds easier.

Thanks,

Wes George


________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

--_000_2671C6CDFBB59E47B64C10B3E0BD592303AFB9E5PRVPEXVS15corpt_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">You may want to include some references to RFC6250 (=
specifically section 3.2) when discussing the problems around the assumptio=
ns of the need or possibility for static addresses. I think some of the lan=
guage in that document reinforces
 the idea that the need for static addressing is often based on faulty assu=
mptions about addressing, and would complement the text in this draft nicel=
y.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Also, this draft does a reasonable job at documentin=
g some of the historical reasons for choosing to use static addresses. Howe=
ver, I think that it might be useful for this document to categorize these =
into use cases that the WG agrees
 still legitimately require static addressing, as distinct from those where=
 workarounds exist that would enable things that normally use static addres=
sing to move to dynamically-assigned addresses.
<o:p></o:p></p>
<p class=3D"MsoNormal">For example, the use case about small networks witho=
ut DNS resources is by no means an unsolvable problem, or even a particular=
ly difficult one to resolve given the relative ease of setting up a DNS ser=
ver, but I believe that there are
 examples where the workaround is either unavailable or sufficiently onerou=
s as to not be commonly used. Since this is meant to be a companion to the =
gap analysis document, identifying those gaps would be helpful, as it would=
 inform future work to resolve some
 of those issues or make the workarounds easier. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Wes George<span style=3D"color:#7F7F7F"><o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">This E-mail and any of its a=
ttachments may contain Time Warner Cable proprietary information, which is =
privileged, confidential, or subject to copyright belonging to Time Warner =
Cable. This E-mail is intended solely
 for the use of the individual or entity to which it is addressed. If you a=
re not the intended recipient of this E-mail, you are hereby notified that =
any dissemination, distribution, copying, or action taken in relation to th=
e contents of and attachments to
 this E-mail is strictly prohibited and may be unlawful. If you have receiv=
ed this E-mail in error, please notify the sender immediately and permanent=
ly delete the original and any copy of this E-mail and any printout.<br>
</font>
</body>
</html>

--_000_2671C6CDFBB59E47B64C10B3E0BD592303AFB9E5PRVPEXVS15corpt_--

From brian.e.carpenter@gmail.com  Fri Aug 24 23:58:29 2012
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 BB59221F8504 for <renum@ietfa.amsl.com>; Fri, 24 Aug 2012 23:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.513
X-Spam-Level: 
X-Spam-Status: No, score=-101.513 tagged_above=-999 required=5 tests=[AWL=0.178, 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 5zqMFE7e1mSR for <renum@ietfa.amsl.com>; Fri, 24 Aug 2012 23:58:29 -0700 (PDT)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by ietfa.amsl.com (Postfix) with ESMTP id B751D21F84FE for <renum@ietf.org>; Fri, 24 Aug 2012 23:58:28 -0700 (PDT)
Received: by wibhq12 with SMTP id hq12so3768779wib.1 for <renum@ietf.org>; Fri, 24 Aug 2012 23:58:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=zJlf20Ao/ZNXZDyeVJfWsQaLHBXRhvDta9nn5303BBA=; b=xPUd6cswU0w3r11A4OdNgLxdgalRL2Fwyditf5+RAkLrTL1heltgpgD0cYQvslMj/V pTYTkBQpogxFYpnZqJfzf78ZsefLDdBCbVQC9fDe+zcOj1lCE7YYJFDuCwhkftEcCF// M20LewIhxFLS0Ghe/48P/kgPHPeHMGcf7B5mfea1s9GnMwVQ0qAqn0pa3MzztdAtAbE6 ygfugRdIgQrs9hF4qVeO0YWK++9CM6vg4T+F06HO6zB65vGtM7CNdhSzJfyJleRxHIaD PQzZ+/YxHThynmphgAO8TR1nGcm1lCNx2qMB1IZ4e4Fq6rrsKdJjZanuX1qXcP76+TLc K9Og==
Received: by 10.180.97.106 with SMTP id dz10mr10742547wib.21.1345877907499; Fri, 24 Aug 2012 23:58:27 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-176.as13285.net. [2.102.217.176]) by mx.google.com with ESMTPS id l6sm1294646wiz.4.2012.08.24.23.58.25 (version=SSLv3 cipher=OTHER); Fri, 24 Aug 2012 23:58:26 -0700 (PDT)
Message-ID: <50387790.9090204@gmail.com>
Date: Sat, 25 Aug 2012 07:58:24 +0100
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: "George, Wes" <wesley.george@twcable.com>
References: <2671C6CDFBB59E47B64C10B3E0BD592303AFB9E5@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD592303AFB9E5@PRVPEXVS15.corp.twcable.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-6renum-static-problem@tools.ietf.org" <draft-ietf-6renum-static-problem@tools.ietf.org>, "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Comment on 6renum-static-problem
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: Sat, 25 Aug 2012 06:58:29 -0000

Hi Wes,

On 24/08/2012 19:21, George, Wes wrote:
> You may want to include some references to RFC6250
> (specifically section 3.2) when discussing the problems
> around the assumptions of the need or possibility for static
> addresses. I think some of the language in that document
> reinforces the idea that the need for static addressing is
> often based on faulty assumptions about addressing, and would
> complement the text in this draft nicely.

Yes, and in fact I would reverse the message of 6250 slightly:
*because* some of the "claims" in that section are widely
accepted by application layer programmers, static addresses are
(unfortunately) useful.

> 
> Also, this draft does a reasonable job at documenting some of
> the historical reasons for choosing to use static addresses.
> However, I think that it might be useful for this document to
> categorize these into use cases that the WG agrees still
> legitimately require static addressing, as distinct from
> those where workarounds exist that would enable things that
> normally use static addressing to move to
> dynamically-assigned addresses. 

True, if we can reach consensus ;-)

> For example, the use case
> about small networks without DNS resources is by no means an
> unsolvable problem, or even a particularly difficult one to
> resolve given the relative ease of setting up a DNS server,

That's a hot topic in homenet. Strictly speaking, homenets are
out of scope for 6renum, but small enterprise networks have a
lot in common with large homenets.

> but I believe that there are examples where the workaround is
> either unavailable or sufficiently onerous as to not be
> commonly used. Since this is meant to be a companion to the
> gap analysis document, identifying those gaps would be
> helpful, as it would inform future work to resolve some of
> those issues or make the workarounds easier.

OK, can you be more specific?

Thanks!
   Brian

From wesley.george@twcable.com  Mon Aug 27 07:55:08 2012
Return-Path: <wesley.george@twcable.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 0233821F866B for <renum@ietfa.amsl.com>; Mon, 27 Aug 2012 07:55:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.441
X-Spam-Level: 
X-Spam-Status: No, score=-0.441 tagged_above=-999 required=5 tests=[AWL=0.022,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 92J1IdmcrAUG for <renum@ietfa.amsl.com>; Mon, 27 Aug 2012 07:55:07 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 6739C21F8672 for <renum@ietf.org>; Mon, 27 Aug 2012 07:55:07 -0700 (PDT)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.80,321,1344225600"; d="scan'208";a="412039479"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 27 Aug 2012 10:55:04 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Mon, 27 Aug 2012 10:55:06 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Mon, 27 Aug 2012 10:55:04 -0400
Thread-Topic: Comment on 6renum-static-problem
Thread-Index: Ac2Cjwsaj23Dv+BwQQiMNvalGFs3HAB08P/Q
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD592303AFC0A6@PRVPEXVS15.corp.twcable.com>
References: <2671C6CDFBB59E47B64C10B3E0BD592303AFB9E5@PRVPEXVS15.corp.twcable.com> <50387790.9090204@gmail.com>
In-Reply-To: <50387790.9090204@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "draft-ietf-6renum-static-problem@tools.ietf.org" <draft-ietf-6renum-static-problem@tools.ietf.org>, "renum@ietf.org" <renum@ietf.org>
Subject: Re: [renum] Comment on 6renum-static-problem
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, 27 Aug 2012 14:55:08 -0000

PiBGcm9tOiBCcmlhbiBFIENhcnBlbnRlciBbbWFpbHRvOmJyaWFuLmUuY2FycGVudGVyQGdtYWls
LmNvbV0NCj4gU2VudDogU2F0dXJkYXksIEF1Z3VzdCAyNSwgMjAxMiAyOjU4IEFNDQo+IFRvOiBH
ZW9yZ2UsIFdlcw0KPiBDYzogcmVudW1AaWV0Zi5vcmc7IGRyYWZ0LWlldGYtNnJlbnVtLXN0YXRp
Yy1wcm9ibGVtQHRvb2xzLmlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBDb21tZW50IG9uIDZyZW51
bS1zdGF0aWMtcHJvYmxlbQ0KPg0KPiA+IGJ1dCBJIGJlbGlldmUgdGhhdCB0aGVyZSBhcmUgZXhh
bXBsZXMgd2hlcmUgdGhlIHdvcmthcm91bmQgaXMgZWl0aGVyDQo+ID4gdW5hdmFpbGFibGUgb3Ig
c3VmZmljaWVudGx5IG9uZXJvdXMgYXMgdG8gbm90IGJlIGNvbW1vbmx5IHVzZWQuIFNpbmNlDQo+
ID4gdGhpcyBpcyBtZWFudCB0byBiZSBhIGNvbXBhbmlvbiB0byB0aGUgZ2FwIGFuYWx5c2lzIGRv
Y3VtZW50LA0KPiA+IGlkZW50aWZ5aW5nIHRob3NlIGdhcHMgd291bGQgYmUgaGVscGZ1bCwgYXMg
aXQgd291bGQgaW5mb3JtIGZ1dHVyZQ0KPiA+IHdvcmsgdG8gcmVzb2x2ZSBzb21lIG9mIHRob3Nl
IGlzc3VlcyBvciBtYWtlIHRoZSB3b3JrYXJvdW5kcyBlYXNpZXIuDQo+DQo+IE9LLCBjYW4geW91
IGJlIG1vcmUgc3BlY2lmaWM/DQo+DQoNCltXRUddIG5vdCBhdCB0aGUgbW9tZW50LiBJIHRyaWVk
IGJvdGggd2hlbiBvcmlnaW5hbGx5IGNvbXBvc2luZyB0aGlzIG1lc3NhZ2UgYW5kIHdoZW4gcmVw
bHlpbmcganVzdCBub3cgdG8gdGhpbmsgb2YgYSBzcGVjaWZpYyBleGFtcGxlIG9mIHRoaXMsIGFu
ZCBJJ20gY29taW5nIHVwIGVtcHR5aGFuZGVkLg0KDQpUbyBtZSB0aGF0IG1lYW5zIG9uZSBvZiB0
d28gdGhpbmdzIC0gdGhlcmUgYXJlIGZldyAoaWYgYW55KSBsZWdpdGltYXRlIHVzZXMgZm9yIHN0
YXRpYyBhZGRyZXNzZXMgb3RoZXIgdGhhbiB0byBjb21wZW5zYXRlIGZvciBsZWdhY3kgc3lzdGVt
cyB0aGF0IG1ha2UgYmFkIGFzc3VtcHRpb25zIG9yIG90aGVyd2lzZSBhcmUgaGFyZCB0byBmaXgg
LU9SLSB3ZSBuZWVkIGJldHRlciBpbnB1dCBmcm9tIHBlb3BsZSBtb3JlIGZhbWlsaWFyIHdpdGgg
dGhpcyBwcm9ibGVtIHRoYW4gbWUuDQpJZiBpdCdzIHRoZSBmb3JtZXIsIHRoYXQgd291bGQgY2Vy
dGFpbmx5IGFmZmVjdCB0aGUgdG9uZSBhbmQgY29uY2x1c2lvbiBvZiB0aGUgZG9jdW1lbnQuIElm
IGl0J3MgdGhlIGxhdHRlciwgSSdtIGhvcGluZyB0aGlzIHdpbGwgaW5jaXRlIHNvbWUgZGlzY3Vz
c2lvbiwgb3RoZXJ3aXNlIHdlIG1heSBuZWVkIHRvIHN0YXJ0IGFza2luZyBpbiBzb21lIHBsYWNl
cyBtb3JlIGxpa2VseSB0byBoYXZlIHNpZ25pZmljYW50IG9wZXJhdG9yIHByZXNlbmNlICgqTk9H
cywgZXRjKS4gc29ycnkgSSBjb3VsZG4ndCBiZSBtb3JlIGhlbHBmdWwgdGhhbiB0aGF0LCBJJ2xs
IGtlZXAgdGhpbmtpbmcgYWJvdXQgaXQuLi4NCg0KV2VzIEdlb3JnZQ0KDQpUaGlzIEUtbWFpbCBh
bmQgYW55IG9mIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBUaW1lIFdhcm5lciBDYWJsZSBw
cm9wcmlldGFyeSBpbmZvcm1hdGlvbiwgd2hpY2ggaXMgcHJpdmlsZWdlZCwgY29uZmlkZW50aWFs
LCBvciBzdWJqZWN0IHRvIGNvcHlyaWdodCBiZWxvbmdpbmcgdG8gVGltZSBXYXJuZXIgQ2FibGUu
IFRoaXMgRS1tYWlsIGlzIGludGVuZGVkIHNvbGVseSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZp
ZHVhbCBvciBlbnRpdHkgdG8gd2hpY2ggaXQgaXMgYWRkcmVzc2VkLiBJZiB5b3UgYXJlIG5vdCB0
aGUgaW50ZW5kZWQgcmVjaXBpZW50IG9mIHRoaXMgRS1tYWlsLCB5b3UgYXJlIGhlcmVieSBub3Rp
ZmllZCB0aGF0IGFueSBkaXNzZW1pbmF0aW9uLCBkaXN0cmlidXRpb24sIGNvcHlpbmcsIG9yIGFj
dGlvbiB0YWtlbiBpbiByZWxhdGlvbiB0byB0aGUgY29udGVudHMgb2YgYW5kIGF0dGFjaG1lbnRz
IHRvIHRoaXMgRS1tYWlsIGlzIHN0cmljdGx5IHByb2hpYml0ZWQgYW5kIG1heSBiZSB1bmxhd2Z1
bC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBFLW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3Rp
ZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseSBhbmQgcGVybWFuZW50bHkgZGVsZXRlIHRoZSBvcmln
aW5hbCBhbmQgYW55IGNvcHkgb2YgdGhpcyBFLW1haWwgYW5kIGFueSBwcmludG91dC4NCg==

From internet-drafts@ietf.org  Fri Aug 31 00:00:00 2012
Return-Path: <internet-drafts@ietf.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 719DA21F855D; Fri, 31 Aug 2012 00:00:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level: 
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, 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 328BzMBEHzXe; Thu, 30 Aug 2012 23:59:59 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6492621F8528; Thu, 30 Aug 2012 23:59:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20120831065959.29136.35895.idtracker@ietfa.amsl.com>
Date: Thu, 30 Aug 2012 23:59:59 -0700
Cc: renum@ietf.org
Subject: [renum] I-D Action: draft-ietf-6renum-static-problem-01.txt
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, 31 Aug 2012 07:00:00 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IPv6 Site Renumbering Working Group of th=
e IETF.

	Title           : Problem Statement for Renumbering IPv6 Hosts with Static=
 Addresses
	Author(s)       : Brian Carpenter
                          Sheng Jiang
	Filename        : draft-ietf-6renum-static-problem-01.txt
	Pages           : 12
	Date            : 2012-08-30

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


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6renum-static-problem

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6renum-static-problem-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6renum-static-problem-01


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From brian.e.carpenter@gmail.com  Fri Aug 31 00:19:11 2012
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 96C2021F84EC for <renum@ietfa.amsl.com>; Fri, 31 Aug 2012 00:19:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.523
X-Spam-Level: 
X-Spam-Status: No, score=-101.523 tagged_above=-999 required=5 tests=[AWL=0.168, 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 1I2bx+Z9Uqci for <renum@ietfa.amsl.com>; Fri, 31 Aug 2012 00:19:11 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id AC23321F8476 for <renum@ietf.org>; Fri, 31 Aug 2012 00:19:10 -0700 (PDT)
Received: by eaai11 with SMTP id i11so786959eaa.31 for <renum@ietf.org>; Fri, 31 Aug 2012 00:19:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=a69jCrS6bvBpM/DRF2tBbSa/yn6ZjJpTgBprPXqzwsk=; b=OQJ5AthxUTilsp8E4iPpbg82MLZ6QABtY6xw4MhNiVEkuOoRlM23CeHmOpODJE2t/I v61Mkij86DwLKcq4MioS7I4yVnazMNSBrzIXcqL9/AYPZ+r1mz+5zrELGvl6vdOFifz5 jbbKUc6dCms2OFan5Hy/brfjSnyVEyYrAEb6dZhhD79Fb+kd2oSS5Wnp8TcydOeYfWfx 7Bl31+9vggkmeOu/jkkaQ9qYSaYPsB4QneyzqG4lLfKKGs4X9S0iqy4vLMQhrMgT2qWS J7G9dLcMIIMEwmY3FPyNLinApqomfVuQzOl2ch2c9Y8AZtyYG7fPrqivMnTpvJz5WHak HdjA==
Received: by 10.14.204.72 with SMTP id g48mr9742266eeo.45.1346397548707; Fri, 31 Aug 2012 00:19:08 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-147.as13285.net. [2.102.216.147]) by mx.google.com with ESMTPS id e7sm10930117eep.2.2012.08.31.00.19.06 (version=SSLv3 cipher=OTHER); Fri, 31 Aug 2012 00:19:07 -0700 (PDT)
Message-ID: <50406572.2040203@gmail.com>
Date: Fri, 31 Aug 2012 08:19:14 +0100
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: renum@ietf.org
References: <20120831065959.29136.35895.idtracker@ietfa.amsl.com>
In-Reply-To: <20120831065959.29136.35895.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [renum] I-D Action: draft-ietf-6renum-static-problem-01.txt
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, 31 Aug 2012 07:19:11 -0000

This version is updated following the comments by Wes George.
Please check the end of Section 3 in particular; that is all new.

http://tools.ietf.org/html/draft-ietf-6renum-static-problem-01#section-3

Regards
   Brian + Sheng

On 31/08/2012 07:59, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the IPv6 Site Renumbering Working Group of the IETF.
> 
> 	Title           : Problem Statement for Renumbering IPv6 Hosts with Static Addresses
> 	Author(s)       : Brian Carpenter
>                           Sheng Jiang
> 	Filename        : draft-ietf-6renum-static-problem-01.txt
> 	Pages           : 12
> 	Date            : 2012-08-30
> 
> Abstract:
>    This document analyses the problems of updating the IPv6 addresses of
>    hosts in enterprise networks that for operational reasons require
>    static addresses.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6renum-static-problem
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6renum-static-problem-01
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-6renum-static-problem-01
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum
> 
