Re: [v6ops] draft-ietf-v6ops-ula-usage-recommendations - work or abandon?

Owen DeLong <owen@delong.com> Tue, 03 November 2015 13:37 UTC

Return-Path: <owen@delong.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 092C11B3398 for <v6ops@ietfa.amsl.com>; Tue, 3 Nov 2015 05:37:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.11
X-Spam-Level:
X-Spam-Status: No, score=-6.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_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 LEoXe-6VlMzC for <v6ops@ietfa.amsl.com>; Tue, 3 Nov 2015 05:37:23 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [192.159.10.2]) by ietfa.amsl.com (Postfix) with ESMTP id 67B751B338E for <v6ops@ietf.org>; Tue, 3 Nov 2015 05:37:23 -0800 (PST)
Received: from [192.168.88.235] (host226-63.122-190.riotel.com.ar [190.122.63.226] (may be forged)) (authenticated bits=0) by owen.delong.com (8.14.5/8.14.5) with ESMTP id tA3DbG2P002596 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 3 Nov 2015 05:37:20 -0800
Content-Type: multipart/alternative; boundary="Apple-Mail=_FF6C8066-2DA6-4B5B-8882-8C26F9703BC0"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <CAKD1Yr1VvzkSmJo3hu6t_3CUguLN_UkNZjRUqvU_ygPBTyb+8g@mail.gmail.com>
Date: Tue, 03 Nov 2015 08:37:15 -0500
Message-Id: <6A7DF8AE-4307-43E4-B9F1-282BB63F2271@delong.com>
References: <D25D5920.C914E%Lee.Howard@twcable.com> <5637FDD0.70300@jvknet.com> <D25E32F1.C9507%Lee.Howard@twcable.com> <CAKD1Yr1VvzkSmJo3hu6t_3CUguLN_UkNZjRUqvU_ygPBTyb+8g@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/2j5qea5syNClFzpKz0S7WFRsMb0>
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-ula-usage-recommendations - work or abandon?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Nov 2015 13:37:26 -0000

+1 to everything Lorenzo says below.

> On Nov 2, 2015, at 11:55 PM, Lorenzo Colitti <lorenzo@google.com> wrote:
> 
> My recollection is that we never got around to publishing this document because we never managed to agree on what to say in the recommendations. I think that because the working group does not actually have consensus on what ULAs should be used for. 
> 
> Generalizing and handwaving a bit, I think that the major disagreement is between:
> Some proponents of ULAs are suggesting that ULAs (are being | can be | should be) used in similar ways to RFC 1918, including using them behind NPT66 or in the absence of global addresses, and say that the document should list those as use cases.
> A fair number of WG members are vehemently opposed to such uses, and say that WG documents should explicitly call out such practices as harmful. We heard a few of those members at the mike yesterday during the discussion of the design choices draft.
> For as long as that disagreement exists, it will be hard to make a recommendation, which is likely to make it hard to get consensus on this draft. We can go through that disagreement again, but I don't personally think the outcome will be any different from the one we had last time around.
> 
> I happen to be in camp #2 and would be happy to support this draft if it said that ULA-only deployments, NPT66 and NAT66 are harmful and should be avoided. But I'm sure a fair number of people disagree with me.
> 
> On Tue, Nov 3, 2015 at 9:49 AM, Howard, Lee <lee.howard@twcable.com <mailto:lee.howard@twcable.com>> wrote:
> I see interest from Victor Kuarsingh, David Farmer, Alexandre Petrescu, and
> Brian Carpenter. Can I ask each of you to do a review of the current
> document, and send comments to the mailing list?  That will give the
> authors
> and the WG something to work from.
> 
> Following that, we can discuss whether we need additional discussion at a
> meeting, or WGLC.
> 
> Thanks,
> 
> Lee
> 
> 
> On 11/3/15, 9:20 AM, "Victor Kuarsingh" <victor@jvknet.com <mailto:victor@jvknet.com>> wrote:
> 
> >WG,
> >
> >My input is that we should continue this work.  Given ULAs are already
> >in use, having a document which outlines those use cases is, in my mind,
> >operationally beneficial.
> >
> >Perhaps we should be more clear that we would not be recommending the
> >use of ULAs, but keep to a unbiased document which outlines how they
> >have been used (just a use case discussion).  We can also include
> >objective technical points as to the pros/cons related to each use case.
> >
> >It was also noted in another email (based on WG v6ops discussion
> >yesterday), that one such valid example was Cable Modem management IPs
> >assigned ULA based addressing.  This is a valid technical use case.
> >
> >I am willing to help if required on this document.
> >
> >regards,
> >
> >Victor K
> >
> >On 2015-11-02 6:17 PM, Howard, Lee wrote:
> >> This document hasn¹t had any revisions or discussion in a while.
> >> Is there anyone interested in working on it?
> >>
> >> If we do not hear any interest, we will abandon this draft.
> >>
> >> Thanks,
> >> Lee
> >>
> >>
> >> ________________________________
> >>
> >> This E-mail and any of its attachments 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 are not the intended recipient of this E-mail, you are hereby
> >>notified that any dissemination, distribution, copying, or action taken
> >>in relation to the contents of and attachments to this E-mail is
> >>strictly prohibited and may be unlawful. If you have received this
> >>E-mail in error, please notify the sender immediately and permanently
> >>delete the original and any copy of this E-mail and any printout.
> >>
> >> _______________________________________________
> >> v6ops mailing list
> >> v6ops@ietf.org <mailto:v6ops@ietf.org>
> >> https://www.ietf.org/mailman/listinfo/v6ops <https://www.ietf.org/mailman/listinfo/v6ops>
> >
> 
> 
> ________________________________
> 
> This E-mail and any of its attachments 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 are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org <mailto:v6ops@ietf.org>
> https://www.ietf.org/mailman/listinfo/v6ops <https://www.ietf.org/mailman/listinfo/v6ops>
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops