IETF Logo Mail Archive

Re: [dhcwg] draft-ietf-6man-default-iids Section 4 & 6.9 (DHCPv6)

Alissa Cooper <alissa@cooperw.in> Tue, 09 August 2016 18:49 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF02F12D189; Tue, 9 Aug 2016 11:49:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level:
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=eadqU+2F; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=NmHcVdQ9
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Z6tr2wVdXFk; Tue, 9 Aug 2016 11:49:18 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11AFC12D50C; Tue, 9 Aug 2016 11:49:18 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 42A26200E5; Tue, 9 Aug 2016 14:49:17 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 09 Aug 2016 14:49:17 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=axUZA 81MzLJT5/PgxL+HqqB9LCM=; b=eadqU+2FRV/LrmEuLNct8xGBgwC1R4IsKXjX5 h4asBCNesk4kifkrWMgvSiNnY+BolCQW5mhLUND50XZLBcacVpRWgJYRuD/zBffs 13vJDuDsTLvrfGPmv0RCUDoATiceWHcbSGZ4M02eJuk4Zk5i0kVSTFgjmm6Xn7Tq 7V9DsE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=axUZA81MzLJT5/PgxL+HqqB9LCM=; b=NmHcV dQ99HlXAlIPBLN882+3qv3SlDkRJNe/aDLZfxGiZ+FB/1rDYkdBp8OLjZfyAMF+w TO6tbmnFEfluuI4S1NeEfju3qkDvfJ0kcFWR+7vWPgCnYnoLO/+UVFfDO41OcXrm 7EYL5tTSx0M4IOVwrh7+fgUFvx92odLj9/6mCg=
X-Sasl-enc: +zq5Kn1eSSb7tAuujxhH5K8dFSX7uhyGBkNYDoUWvWaP 1470768556
Received: from dhcp-171-68-20-114.cisco.com (dhcp-171-68-20-114.cisco.com [171.68.20.114]) by mail.messagingengine.com (Postfix) with ESMTPA id E9842F2983; Tue, 9 Aug 2016 14:49:15 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_849263CB-A4FA-4ABA-80BD-981C40CB278A"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CAO42Z2z55B5WHR=Oaa=WF1tM4i4LFmFxWC5pe1opqQ46ZOWdtA@mail.gmail.com>
Date: Tue, 09 Aug 2016 11:49:14 -0700
Message-Id: <362684CB-570E-42F2-A8AE-C976EE537878@cooperw.in>
References: <D3B60069.31262%volz@cisco.com> <43CE5CAD-2D98-4A75-BF33-E5B415B1013C@employees.org> <D3B605F6.31290%volz@cisco.com> <4FA70E3F-1AED-4662-AEA9-1BCA107F87AD@cooperw.in> <9fb468f9-7f8f-0c0f-ad3e-6d6ff31f3521@si6networks.com> <CAO42Z2z55B5WHR=Oaa=WF1tM4i4LFmFxWC5pe1opqQ46ZOWdtA@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/wnNBCUv_Yezp9ldkpxoDyRm2w8Y>
Cc: 6man WG <ipv6@ietf.org>, "Bernie Volz (volz)" <volz@cisco.com>, "draft-ietf-6man-default-iids@ietf.org" <draft-ietf-6man-default-iids@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "dhcpv6bis@ietf.org" <dhcpv6bis@ietf.org>
Subject: Re: [dhcwg] draft-ietf-6man-default-iids Section 4 & 6.9 (DHCPv6)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 18:49:20 -0000

> On Aug 5, 2016, at 6:17 PM, Mark Smith <markzzzsmith@gmail.com> wrote:
> 
> 
> On 5 Aug 2016 22:42, "Fernando Gont" <fgont@si6networks.com <mailto:fgont@si6networks.com>> wrote:
> >
> > On 08/04/2016 10:23 PM, Alissa Cooper wrote:
> > >
> > >> On Jul 21, 2016, at 1:58 AM, Bernie Volz (volz) <volz@cisco.com <mailto:volz@cisco.com>> wrote:
> > >>
> > >> Ole:
> > >>
> > >> (I fixed 6man mailing list address.)
> > >>
> > >> That is probably the best solution and I would support that.
> > >>
> > >> We can still discuss changing some of the text in 3315bis, but that can
> > >> then be done without 6man involvement. (We do still have the older text in
> > >> what is now Section 12.1 of draft-ietf-dhc-rfc3315bis-05, so should really
> > >> clean that up.)
> > >
> > > I am fine with this solution and it seems cleaner.
> >
> > Background: At some point folks argued that this document should cover
> > SLAAC, DHCPv6, and manual configuration. And hence this text was added.
> >
> > I don't mind removing the DHCPv6 text. However, if we do, we should
> > probably also remove the text about manual configuration. Otherwise it
> > is not clear why some forms of configuration are covered, but others are
> > not.
> >
> 
> I argued for that because I think privacy is a primary property of an address, not the method used to configure it. However, since the different methods of configuring the address can effect the resulting address's privacy properties, I think it is necessary to discuss how to achieve privacy for the three different configuration methods we have in the one place.
> 
> 

As far as what the resulting privacy properties of an address are, I can see one overview document being useful. But I could see value in the scope of that being broader (to also cover, say, temporary addresses) and writing that after the separate specs about how to do configuration have stabilized, assuming the DHCP bit moves into 3315bis.

Alissa
> Regards,
> Mark.
> 
> > Thanks,
> > --
> > Fernando Gont
> > SI6 Networks
> > e-mail: fgont@si6networks.com <mailto:fgont@si6networks.com>
> > PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
> >
> >
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org <mailto:ipv6@ietf.org>
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 <https://www.ietf.org/mailman/listinfo/ipv6>
> > --------------------------------------------------------------------
>

v2.23.0 | Report a Bug | By Email