RE: [dhcwg] Review of draft-ietf-v6ops-scanning-implications

"Bernie Volz \(volz\)" <volz@cisco.com> Mon, 27 November 2006 15:15 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GoiCI-000239-Pk; Mon, 27 Nov 2006 10:15:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GoiCG-00022Y-TT for dhcwg@ietf.org; Mon, 27 Nov 2006 10:15:04 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GoiBy-0007n6-4L for dhcwg@ietf.org; Mon, 27 Nov 2006 10:14:47 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by sj-iport-6.cisco.com with ESMTP; 27 Nov 2006 07:14:45 -0800
X-IronPort-AV: i="4.09,464,1157353200"; d="scan'208"; a="88999067:sNHT52958007"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id kARFEi4L006532; Mon, 27 Nov 2006 10:14:44 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kARFEiYJ026998; Mon, 27 Nov 2006 10:14:44 -0500 (EST)
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 27 Nov 2006 10:14:44 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Review of draft-ietf-v6ops-scanning-implications
Date: Mon, 27 Nov 2006 10:14:43 -0500
Message-ID: <8E296595B6471A4689555D5D725EBB2102A2B1AA@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] Review of draft-ietf-v6ops-scanning-implications
Thread-Index: AccPSGK9RGS0xHzUQT+J3qRw2ibHVQC7WT2Q
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Stig Venaas <stig.venaas@uninett.no>, dhcwg@ietf.org
X-OriginalArrivalTime: 27 Nov 2006 15:14:44.0098 (UTC) FILETIME=[C4B37E20:01C71236]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1782; t=1164640484; x=1165504484; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com> |Subject:=20RE=3A=20[dhcwg]=20Review=20of=20draft-ietf-v6ops-scanning-imp lications |Sender:=20 |To:=20=22Stig=20Venaas=22=20<stig.venaas@uninett.no>,=20<dhcwg@ietf.org>; bh=TyxWjXb0zwv6+q4ch1rCK97iZNyWd75jKwdQq90N6g8=; b=UCyD2etXVwtQ+Ywpze2FdEEuxKfhcYYNiuvb8yjCBipYGNY15SOiZQE0WT+B0oC6aJe3mkQo Cl9RDMgy1hVdORkwX2HH7CmMLzu8XBqGf3oV8Zx0pE+OwZCQecgh3sBw;
Authentication-Results: rtp-dkim-2; header.From=volz@cisco.com; dkim=pass (s ig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: v6ops@ops.ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

I fully agree with and support this text.

- Bernie

-----Original Message-----
From: Stig Venaas [mailto:stig.venaas@uninett.no] 
Sent: Thursday, November 23, 2006 4:40 PM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Review of draft-ietf-v6ops-scanning-implications

Per Fred's request, please let v6ops and/or authors know if you have
any thoughts regarding this draft. In particular there is the following
section:

4.2.  DHCP Service Configuration Options

    The administrator should configure DHCPv6 so that the first
addresses
    allocated from the pool begins much higher in the address space than
    at [prefix]::1.  DHCPv6 also includes an option to use Privacy
    Extension [2] addresses, i.e. temporary addresses, as described in
    Section 12 of the DHCPv6 [5] specification.  It is desirable that
    allocated addresses are not sequential, nor have any predictable
    pattern to them.

Stig

Fred Baker wrote:
> The v6ops working group is approaching a working group last call on  
> draft-ietf-v6ops-scanning-implications within the coming few weeks.
We 
> would appreciate a review from your working group of this document  
> before we do so. How that is done is up to you; you may designate one

> or more reviewers, or simply conduct the review on your mailing list,

> or whatever else suits you. But please respond to the authors copying

> v6ops within the coming four weeks if you would.
> 
> Thank you for your help in this.
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg