Re: [v6ops] New Version Notification for draft-palet-v6ops-ipv6-only-02.txt

George Michaelson <ggm@algebras.org> Tue, 17 October 2017 22:24 UTC

Return-Path: <ggm@algebras.org>
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 E05751330AD for <v6ops@ietfa.amsl.com>; Tue, 17 Oct 2017 15:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=algebras-org.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 khKzhw7tqPGI for <v6ops@ietfa.amsl.com>; Tue, 17 Oct 2017 15:24:25 -0700 (PDT)
Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::236]) (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 9EF5213304B for <v6ops@ietf.org>; Tue, 17 Oct 2017 15:24:25 -0700 (PDT)
Received: by mail-vk0-x236.google.com with SMTP id b5so2130521vkf.12 for <v6ops@ietf.org>; Tue, 17 Oct 2017 15:24:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=uxUSBlCvDS2b5ZczBjSEqJLW/S6Hc2eztFldFGZDYb4=; b=hH/j5vBbgjYvqVae5BOC6jSgPcCulrAyDVTaxvHq17z+Z62KzCD5/SJxMuStgIpYk9 9zugLmgjwxsqvoCUZ8vSkr/q+ets57RqFPql/SHAAvXa/5vD5yNrxqTYcviVjxB0qomx gxZL+GqhKlNd5qaon23ARO8sZfy7yi76S3Gbufz+qCJE1hBGKu0UwIHrMuTUc1ckBlPn h5/tUC6YFoon6luuZMLx+OIX6RvTHReD57fkLULK3djz2nyDqqDhSV3feIafo4ag83sD +aeMFOYjuvFDgBcKboqJaAbbQNQQKnasImuNEh8A+elq3jaD5N+O0GcrbPsg/eiCA4o4 CWNQ==
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:content-transfer-encoding; bh=uxUSBlCvDS2b5ZczBjSEqJLW/S6Hc2eztFldFGZDYb4=; b=PVs42LP9otNFIsPl2Iha9c4zLQ9VS+RCbkteA3eCM2z73tP6vnuoqPinoq7cNE3LTl ul6L8NTS3VvMCq2PhL6uLMUopg7ND3jctBjO5Om2TIdBaAjIt0AQdU7mEz/Sqti2poyD /+CYjXJM52aargEJX1frKT/rGSYmhV2wKsZlII4ue+bPd/3P6nh+FF1yoD8CkuVxhtX5 E1Lk1alMvMfMiH9pGD8cYvijljLpaRCISP0U6VRrGavv8qJYqX7NsKUn711BOO6PUekV XFCoRTs7OQRdXIkwRJxW+EgIn0qKYvM8DYK9lq4/p2wcuSEDi9rzTsdHRXcI3GLNu7FO kWmQ==
X-Gm-Message-State: AMCzsaW4ywStudMQVeJu0oDkfxcqjoN/gYk+3VocceeBizy+DM4D54i+ m4QOiBDf+/+fAT8qMLhC2zKWAiyaYBvJ3CgMp+aQoNJb
X-Google-Smtp-Source: ABhQp+Qq46xUtYHzzKYuf2vq47eJhxWWSL1Dhv+dDMdrHnpm+/iZ2l7hmi4irjoB3ZAd+QkjzB2llYBP5N3rV9Qj9ks=
X-Received: by 10.31.135.17 with SMTP id j17mr80821vkd.34.1508279064729; Tue, 17 Oct 2017 15:24:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.91.93 with HTTP; Tue, 17 Oct 2017 15:24:24 -0700 (PDT)
X-Originating-IP: [2001:dc0:2001:210:d593:69db:f0c8:8cc4]
In-Reply-To: <3E196E02-87F9-4140-BE9C-5B21F69EE7E1@gmail.com>
References: <150824269847.21561.8932178346065454678.idtracker@ietfa.amsl.com> <44FD0037-CAFC-401B-A9E4-A976CB2A35F7@consulintel.es> <alpine.LFD.2.00.1710171209110.10941@pine.servidores.unam.mx> <389AFC32-C6D5-4075-8617-E88CDF86CB01@consulintel.es> <3E196E02-87F9-4140-BE9C-5B21F69EE7E1@gmail.com>
From: George Michaelson <ggm@algebras.org>
Date: Wed, 18 Oct 2017 08:24:24 +1000
Message-ID: <CAKr6gn3cc5Vio+_eMC0TrajZRTN25tXyNbxTiVR4EGxkR2_VZA@mail.gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, "<v6ops@ietf.org>" <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/yf3DQcCB8Ot-Qb2sa9BqzZeQz64>
Subject: Re: [v6ops] New Version Notification for draft-palet-v6ops-ipv6-only-02.txt
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: Tue, 17 Oct 2017 22:24:28 -0000

Not that anyone doesn't understand this, but a 'network' could quite
possibly "not support" IPv4 and still have IPv4 packets on it. So, you
can expect to see ARP. you can expect to see DHCP requests. You can
even see half-open TCP.

Diagnostically, the state of being 'IPv6 only' doesn't mean there is
no IPv4 packet types on the wire. it just means they aren't being
supported, carried forward, responded to by deliberate deployment
choices. No router is being proffered, no DNS service is being
proferred.

But if somebody turns up an IPv4 DHCP server, responds to ARP, and
offers a default route, You are not necessarily blocking them.

An IPv4 *blocked* network would be one, which uses lower level (layer
2) switch or other methods to refuse to forward frames which carry
IPv4 and associated (ARP) traffic.

Thats different.

-G

On Wed, Oct 18, 2017 at 4:06 AM, Fred Baker <fredbaker.ietf@gmail.com> wrote:
>
>
>> On Oct 17, 2017, at 10:43 AM, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
>>
>>    - I think a short "Definition of IPv4-only" would be useful to include.
>
> A little rumination in context. Hats off.
>
> To me, an IPv4-only thing is a thing that can only communicate using IPv4. That would be true of an IPv4-only host, an IPv4-only LAN, or an IPv4-only network. In each case, there is a question of perspective: if an ISP only offers a subscriber IPv4 addresses or prefixes, then the subscriber is IPv4-only from the ISP's perspective, even though it might be using something else internally or when communicating via some other connectivity. If we are speaking from the perspective of the host itself, it might mean that it is perfectly capable of communicating using something else, but it has only been provisioned with an IPv4 address, or it can communicate with peers on its LAN using something else, but the router is IPv4-only, and so when it communicates with devices beyond the router (or they try to communicate with it), IPv4 is the only thing that works.
>
> So, suggested text:
>
> IPv4-only: only capable of or provisioned to communicate using IPv4. The description is always from a perspective, whether the perspective of a host or network seeking to communicate, or that of another host or network describing a communication peer.
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>