Re: [v6ops] [*SPAM* Score/Req: 3.5/3.3] possible path forward with RFC7084 and transition/other stuff

Ted Lemon <mellon@fugue.com> Fri, 21 July 2017 08:00 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9615C129B34 for <v6ops@ietfa.amsl.com>; Fri, 21 Jul 2017 01:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 pycTpRRIeTfx for <v6ops@ietfa.amsl.com>; Fri, 21 Jul 2017 01:00:13 -0700 (PDT)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6CE9131AA9 for <v6ops@ietf.org>; Fri, 21 Jul 2017 01:00:05 -0700 (PDT)
Received: by mail-pf0-x22f.google.com with SMTP id q85so21443360pfq.1 for <v6ops@ietf.org>; Fri, 21 Jul 2017 01:00:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dN9cPwd6Ol6bxhP8gqs6ehhkxYLdzmq/rEpNqDw3Rbs=; b=dXiSlwJ+5XtKPrnTWzmW1GcFUB8CstI2jAnSuSDzritS9dat+RCmOSAmDRj3ugfCSb 0glyvlhM7W5QnnLIz3+h9NTyuRevdW1zWOyEGJHr/3m6QOpKOEcJh+TMO62pWFk9IPJI gFSA3PzEZRsVqqAQEQ7IrBpI+yyAoAheEaBLenJyq0+UwRoU0QMdEhKY+ICbi3TZZfIB Stt0QKaO+OYmSwAEi6LoK5dV0YdaJ4iFZwCYJ1/6Z7PW0AEcewLVez8jQPveCt2RH77g E/xwMspfVcYqtqdTtJvSlz0wFalll68BX3lyF+O6heb5LpXF6KbYCOLbghjpMv8fHZZt Pw/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dN9cPwd6Ol6bxhP8gqs6ehhkxYLdzmq/rEpNqDw3Rbs=; b=BmXV1EqtdS/c6j63pg8UcyocVsoDd2EyORdK7uzO6A7JwN3k0AxOBs/9IL0VK2ifgd UxEoDivZrZYrvIjM6k3Ttq6la5lk/LxFSXnKmrPv6emGCLgiavI2OEg9bHYP08O1w14o KjuzIFDs/cC/hcJwiW9ul1ha0Dve2XgOBVz+5q9UyhZ3XY1h8watpTZ9xWHYPOvELhOh 6gOhHGPQO0Jk2fxHD6dCzRQ6vuBti1dCAEnNCBgjOxhck8mIgOb+SyfWKg0wp22mzdP+ iLJuN8OxKrcxMdgb5ee3ssEskz9L60DIpWq1vgoXERo7LyCEK5nrR7w+GiT+G/P9y2jj YCbA==
X-Gm-Message-State: AIVw110oW3Ko9Ldk6Ypd3BPSQThjnMiRbqLxu509ry+/NPkq1kHURZAq grNBPf7Et9Ho+XGCtO6c4eomoPoF4T3K
X-Received: by 10.99.56.68 with SMTP id h4mr6601605pgn.52.1500624005521; Fri, 21 Jul 2017 01:00:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.181.130 with HTTP; Fri, 21 Jul 2017 00:59:25 -0700 (PDT)
In-Reply-To: <1AE6D99E-DA24-486E-9735-5E42F60CE5A0@consulintel.es>
References: <1AE6D99E-DA24-486E-9735-5E42F60CE5A0@consulintel.es>
From: Ted Lemon <mellon@fugue.com>
Date: Fri, 21 Jul 2017 09:59:25 +0200
Message-ID: <CAPt1N1mEUJv=PeehopUW-KKdTeNHM9sUefWvvNPRwkTSqi=rZQ@mail.gmail.com>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Cc: IPv6 Ops WG <v6ops@ietf.org>, james woodyatt <jhw@google.com>
Content-Type: multipart/alternative; boundary="f403045d33f2ca7ca20554cf40a8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/hd8sCYDC9_sEre19y3YxTu6x04E>
Subject: Re: [v6ops] [*SPAM* Score/Req: 3.5/3.3] possible path forward with RFC7084 and transition/other stuff
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 21 Jul 2017 08:00:20 -0000

I am not enthusiastic about making changes at this time, first because I
think there's no urgency, and second because I do not know what "require
HNCP" means.   Can you elaborate?

On Fri, Jul 21, 2017 at 9:48 AM, JORDI PALET MARTINEZ <
jordi.palet@consulintel.es> wrote:

> Hi all,
>
> We will like to know the WG opinions on this.
>
> (I’m sending this email after checking with the WG chairs if they agree on
> it)
>
> Yesterday during the bits-N-bytes here in Prague, a few of us (in copy),
> have a chat about a possible path forward with the RFC7084-bis and related
> docs.
>
> If I understood correctly, we somehow agreed that a possible path is
> (let’s call this CHOICE 1):
> 1) Not change/update the existing RFC7084.
> 2) Use my “Transition Requirements for IPv6 Customer Edge Routers”
> document (draft-palet-v6ops-rfc7084-bis-transition-00) as a starting
> point, which “extend” the requirements of RFC7084 towards supporting actual
> world transition requirements.
> 3) In this updated document, the transition requirements can then be a
> MUST, so vendors take it seriously.
> 4) I will include the reference to RFC8026 (some more text, as this
> reference is already in all my docs regarding this topic), so there is a
> “flow” of how the pair “ISP-CE” can get working IPv6 and then IPv4 if it is
> available from the ISP “as a service”. I think this can have also what Fred
> was suggesting as “IPv6 must be on by default”, right?
>
> CHOICE 2 (to make it clear, my own toughs after waking up this morning,
> not discussed with the other folks yesterday):
> Same as choice 1 above, but include also support for HNCP and may be
> something else if we believe it is required during the development of this
> document (for example it seems clear that if we offer IPv4 as a service,
> because actual multicast-based IPTV services run on IPv4, we need to keep
> supporting that on top of an IPv6-only access).
> So then the document will be renamed to something such as “Transition and
> extended requirements for IPv6 CE routers”.
>
> Tim, Barbara, James, can you confirm if I got right choice 1, or
> misunderstood/missed anything?
>
> WG participants, could you provide your view on those two options?
>
> Tim (Winters), could you tell from the perspective of the IPv6 Ready Logo
> Program your view on those two approaches?
>
> It will be nice to be able to double check all the inputs from yesterday
> v6ops sessions, but looking at the etherpad I can’t see them, so may be the
> note takers were using something else. It is possible to access the minutes
> already someway? I will like to start working on this immediately …
>
> Thanks!
>
> Regards,
> Jordi
>
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>
> This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the use of the
> individual(s) named above. If you are not the intended recipient be aware
> that any disclosure, copying, distribution or use of the contents of this
> information, including attached files, is prohibited.
>
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>