Re: [v6ops] Please review the No IPv4 draft

Lorenzo Colitti <lorenzo@google.com> Tue, 15 April 2014 04:21 UTC

Return-Path: <lorenzo@google.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 E47D51A02FF for <v6ops@ietfa.amsl.com>; Mon, 14 Apr 2014 21:21:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=no
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 Jtc-G283KwWB for <v6ops@ietfa.amsl.com>; Mon, 14 Apr 2014 21:20:59 -0700 (PDT)
Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 7507A1A02F0 for <v6ops@ietf.org>; Mon, 14 Apr 2014 21:20:59 -0700 (PDT)
Received: by mail-oa0-f44.google.com with SMTP id n16so10284092oag.31 for <v6ops@ietf.org>; Mon, 14 Apr 2014 21:20:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=6lpxkSG5zBPtOrcUKz0jnaEHyS6fJQKUdQ6l15VQbH8=; b=fHieUjP7VLbv3PKhPYecN5CCVjd4p8ufoEDkIzyZe6cLGuHGzY3pFZesT0msDvlr0Y mJrKKWoQg9eAVC4VeLK2d6vYancZVXwdEcQyqUTKENX0PYAgjzk2xSIVcgDAmu4RaXdS d06vt3Tm3mPr1gm28PWfArSMS8tGXknEhHaPILUzk6hO6iRPZAZ0NiRImieTLvveETZN L3+HMXHh+5YhIB96W1JAmYBoAa1hnGAaPnns+YtDftk8ma+P71zFXBkZY3nA9qyVD7fA jqSyUM13AjvYiqRoHJPSDZHlm4J4BVBr6c0Ny6bdHnKX9K8zw28Wnpc090ob6JIQxqzg tfFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=6lpxkSG5zBPtOrcUKz0jnaEHyS6fJQKUdQ6l15VQbH8=; b=itIjAgTqGDUebFhP3JDRoZUX+K0xce+HjtQc3gGhHwLZtVcyUr61xHlu8b3qu3wRxf Dqo2dq17xPIOjw7D7u01bMNCsyw6jYPPgCkgIiWGy5zfdX7RZanEt3Aji3K2SI43gcNT P96L4sY2BZTbGAS0AK3wJHBkBXmS/lGrYNmhsAyFon2FNAeUhrW3s0It/SYoNwC96sMD u7/Hx1rf/dnc4kubKunJMIWbLOves4FRvwyWTE4sDn4Y3L+l8A0tcLoVU9QiDLnjMoNc AfsPe1x3QKXDZIJVhiZHuhOXghFpONJUDbkAtrjfjdHLHroFbWiaHI+mxkSvBM5i5YVS v+Cw==
X-Gm-Message-State: ALoCoQn4GADf26UmeVfoYqjJhCtIAG3tkiYQjTWowe5KgmlgO3Dv/WKs5zTJmB8fPBR6R0nzBWJcOGqQW5GldP4b+p9JCk9s5/M3eELtH1hEAsVn9UFUdBOHanR1nECtnrIZawlsP51tTRFkJ/ZK2s34EXXaSGFLNlmn+9Gz2qMirbBCbuZu59qnU0QD+90usX4m2AAGaXOD
X-Received: by 10.182.142.229 with SMTP id rz5mr38294940obb.12.1397535656487; Mon, 14 Apr 2014 21:20:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.89.229 with HTTP; Mon, 14 Apr 2014 21:20:36 -0700 (PDT)
In-Reply-To: <534BF5A5.5010609@viagenie.ca>
References: <534BF5A5.5010609@viagenie.ca>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 15 Apr 2014 13:20:36 +0900
Message-ID: <CAKD1Yr0j5+r6K8APoFageJz2RESKj5vkk10Ybom0p3Vec_G0YQ@mail.gmail.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
Content-Type: multipart/alternative; boundary="001a11c362e65ddd3c04f70d205e"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/udSvGPETo9pyIN6c2zYqSsGFxcw
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] Please review the No IPv4 draft
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: <http://www.ietf.org/mail-archive/web/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, 15 Apr 2014 04:21:04 -0000

On Mon, Apr 14, 2014 at 11:50 PM, Simon Perreault <
simon.perreault@viagenie.ca> wrote:

> In a nutshell, it defines DHCPv6 and RA options indicating to the host
> that IPv4 is not available. Reviews from operations-minded people in
> V6OPS would be of tremendous help.
>

I don't see a strong use case for this. It seems to me that the two
scenarios in the introduction can be solved by simply configuring the
DHCPv4 relay (or the server, if on-link) to drop all DHCPv4 requests.

Am I missing something?