Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-stable-privacy-addresses (Respond by Aug 11, 2015)
Chuck Anderson <cra@WPI.EDU> Tue, 11 August 2015 14:16 UTC
Return-Path: <cra@WPI.EDU>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19B171A8A99 for <dhcwg@ietfa.amsl.com>; Tue, 11 Aug 2015 07:16:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 7j40XnQ9o9-2 for <dhcwg@ietfa.amsl.com>; Tue, 11 Aug 2015 07:16:01 -0700 (PDT)
Received: from MAIL1.WPI.EDU (MAIL1.WPI.EDU [130.215.36.91]) by ietfa.amsl.com (Postfix) with ESMTP id 54A5D1A8AF2 for <dhcwg@ietf.org>; Tue, 11 Aug 2015 07:16:00 -0700 (PDT)
Received: from MAIL1.WPI.EDU (MAIL1.WPI.EDU [130.215.36.91]) by MAIL1.WPI.EDU (8.15.1/8.15.1) with ESMTP id t7BEG0ea001816 for <dhcwg@ietf.org>; Tue, 11 Aug 2015 10:16:00 -0400
X-DKIM: Sendmail DKIM Filter v2.8.3 MAIL1.WPI.EDU t7BEG0ea001816
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wpi.edu; s=_dkim; t=1439302560; bh=Xz0U8/rlnrCvwoofFJOjcvD0yvNBPDhtY/g3JTedxxY=; h=Date:From:To:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=NHZR2qmgfpK9tgpchJp7CnxafrrDFqKteCqS0VpdQjBvsm2a5msSeotAyG2wzHBaR fup4SMnsN9aHxwdOKpNBlgpF4vSq4Kxu2q7b5Y4QXyAtxAaReL4QB1sRR5Z/30xf3/ l+c6tB6BaEVLIYmgxkN2AN1PMt0AV8fG3Q7COwPs=
Received: from MX1.WPI.EDU (mx1.wpi.edu [130.215.36.141]) by MAIL1.WPI.EDU (8.15.1/8.15.1) with ESMTP id t7BEG0Vd001813 for <dhcwg@ietf.org>; Tue, 11 Aug 2015 10:16:00 -0400
Received: from angus.ind.WPI.EDU (ANGUS.IND.WPI.EDU [130.215.130.21]) by MX1.WPI.EDU (8.14.4/8.14.4) with ESMTP id t7BEFw1r016587 for <dhcwg@ietf.org>; Tue, 11 Aug 2015 10:15:59 -0400 (envelope-from cra@WPI.EDU)
Received: from angus.ind.WPI.EDU (localhost [127.0.0.1]) by angus.ind.WPI.EDU (8.14.4/8.14.4) with ESMTP id t7BEFwqD010374 for <dhcwg@ietf.org>; Tue, 11 Aug 2015 10:15:58 -0400
Received: (from cra@localhost) by angus.ind.WPI.EDU (8.14.4/8.14.4/Submit) id t7BEFw2J010373 for dhcwg@ietf.org; Tue, 11 Aug 2015 10:15:58 -0400
X-Authentication-Warning: angus.ind.WPI.EDU: cra set sender to cra@WPI.EDU using -f
Date: Tue, 11 Aug 2015 10:15:58 -0400
From: Chuck Anderson <cra@WPI.EDU>
To: dhcwg@ietf.org
Message-ID: <20150811141557.GG23262@angus.ind.WPI.EDU>
Mail-Followup-To: dhcwg@ietf.org
References: <489D13FBFA9B3E41812EA89F188F018E1CB90384@xmb-rcd-x04.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1CB90384@xmb-rcd-x04.cisco.com>
User-Agent: Mutt/1.5.20 (2009-12-10)
X-PerlMx-Spam: Gauge=X, Probability=10%, Report=' TO_IN_SUBJECT 0.5, HTML_00_01 0.05, HTML_00_10 0.05, SUPERLONG_LINE 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1900_1999 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, FROM_EDU_TLD 0, REFERENCES 0, SINGLE_URI_IN_BODY 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CD 0, __CT 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_MSGID 0, __HTTPS_URI 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __PHISH_SPEAR_STRUCTURE_1 0, __REFERENCES 0, __SANE_MSGID 0, __SINGLE_URI_TEXT 0, __SUBJ_ALPHA_NEGATE 0, __TO_IN_SUBJECT 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __URI_IN_BODY 0, __URI_NO_MAILTO 0, __URI_NO_PATH 0, __URI_NO_WWW 0, __URI_NS , __USER_AGENT 0'
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/KbhlYPX6M4zNeord7xboplLSZZc>
Subject: Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-stable-privacy-addresses (Respond by Aug 11, 2015)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Aug 2015 14:16:03 -0000
I support keeping this document alive as Standards Track because it offers a useful way to implement DHCPv6 Failover using a calculated technique rather than state-sharing, and because I value the ability for enterprises to correlate activities of a host within a single IPv6 link while still allowing for privacy and non-correlation across different IPv6 links. On Wed, Jul 29, 2015 at 05:25:42PM +0000, Bernie Volz (volz) wrote: > Hi: > > At the DHC WG session at IETF-93 (Prague), we had a discussion about next steps for draft-ietf-dhc-stable-privacy-addresses. In particular, I (Bernie Volz) proposed we consider it a "dead WG" document (or possibly continue it as Informational). The consensus (hum) in the room was as follows: > > - Most felt (loudest hum) we should consider it a "dead WG" document. > > - A few (minor hum) were in favor of continuing work on it as an Information draft. > > - None (silent) were in favor of continuing work as is (standards track). > I had also asked this question to the mailing list a while back, and there was some discussion though no conclusive action as only a few people voiced an opinion. > > While we don't yet have official minutes for the meeting, you can view the Etherpad notes and audio track by visiting https://tools.ietf.org/agenda/93/ and scrolling down to the DHC session (on Thursday afternoon) and clicking the appropriate links. > > The WG chairs are required to confirm any consensus obtained from a session on the WG mailing list and that is the purpose of this email. > > Thus, if you do NOT agree with the intended action to mark the document as "dead", please indicate so and specify why you feel this document is needed and whether to continue as Standards Track or Informational. Please respond on or before August 11th, 2015. > > Thanks! > > > - Bernie (& Tomek)
- [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-stable… Bernie Volz (volz)
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Tomek Mrugalski
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Fernando Gont
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Fernando Gont
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Bernie Volz (volz)
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… 神明達哉
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Christian Huitema
- [dhcwg] Security/Privacy & Addressing (was: Re: I… Fernando Gont
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Loganaden Velvindron
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Tomek Mrugalski
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Liushucheng (Will)
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Lorenzo Colitti
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Bernie Volz (volz)
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Fernando Gont
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Fernando Gont
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Fernando Gont
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Fernando Gont
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Linhui Sun
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Lorenzo Colitti
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Fernando Gont
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Lorenzo Colitti
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… 神明達哉
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Linhui Sun
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Fernando Gont
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Chuck Anderson
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Lorenzo Colitti
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Fernando Gont
- Re: [dhcwg] IETF-93 Follow Up - draft-ietf-dhc-st… Lorenzo Colitti