Re: IID length text [was Re: Review of draft-ietf-6man-rfc4291bis-06]

Fred Baker <fredbaker.ietf@gmail.com> Tue, 17 January 2017 20:10 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB07A1293EC for <ipv6@ietfa.amsl.com>; Tue, 17 Jan 2017 12:10:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 c7E9Vd9_ncBu for <ipv6@ietfa.amsl.com>; Tue, 17 Jan 2017 12:10:21 -0800 (PST)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (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 A91A5127077 for <ipv6@ietf.org>; Tue, 17 Jan 2017 12:10:21 -0800 (PST)
Received: by mail-pf0-x229.google.com with SMTP id e4so25944089pfg.1 for <ipv6@ietf.org>; Tue, 17 Jan 2017 12:10:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=R8IuHgEphoU/bayA4u3KCb9cDrCXxqNPGqapYoXBED4=; b=lvgq/onJ84+lYcA+QW2ibMvOGZ0OSPp5BiedVZ1FYMQWbxBn+/L7i5C1L6+2vngbVx 5llrhCL3ZTkFlNa82+SFhKk6SbaxqTrDFCO9iM44Pl3FeXWCBPtuQuwO2FFzCSX8GUvk 15fZWHG4WPNnD7j8hYo/wtiZXEWnc2iusstm+0YHq+0mt40mhhNR8dOBY1Sml7RB8a0T ZhTY9SW1Ja2qy64hhGmZIh9gK4Kd34JyCFZleU0jKBg5OEzYnXOtfZfjStrhh56poaYT c2ukVg8xWilM4NDe25HN7mHFrtCQmJSknWujPRwOanlrWE3U31aPA+UwRC628Nfti2pf XN8A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=R8IuHgEphoU/bayA4u3KCb9cDrCXxqNPGqapYoXBED4=; b=sXls/0nef/mD0oT6WmfkED8VInlAxc7N8Ijv+IPJg2fguK2VLvPETlcyRnnqkRonby u4agz8aCT8KkcLzHTkhSFOav2P78IQ00DNb0XwMPDCh0s7E8YlnNlCdCY060jmjCn4Kv K+XqSyyHnQS0dym7bysS85eWuPI6MrDliLLmKUttDX0RxtqSFpvGw2nzBK5WySPCBepM 4KK+JzxRnZkEq+sexCJ5+QfytbYabDO6VBznFIXuYRBfXWYlfVAi1pO/C1X+dwcLDMa3 XE0gqXSYTx8ygatlMcQi0f8ECSSrRwX1qm753AyMw/JYEe3BWc7hINZup3NQD3xrv/Pe jksg==
X-Gm-Message-State: AIkVDXInJNBLatZU/hxdRiIslMNCFu3PeNArGEdyFQVDS4obenC8eb7gV9Ka/iv+nN9uTg==
X-Received: by 10.84.206.37 with SMTP id f34mr61390692ple.35.1484683821301; Tue, 17 Jan 2017 12:10:21 -0800 (PST)
Received: from [192.168.1.15] (wsip-184-191-158-59.sd.sd.cox.net. [184.191.158.59]) by smtp.gmail.com with ESMTPSA id j7sm44926115pfe.84.2017.01.17.12.10.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Jan 2017 12:10:20 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: IID length text [was Re: Review of draft-ietf-6man-rfc4291bis-06]
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <CAN-Dau0OsD4RcVUN+me98g6SJ=oaAr4HoqGtP88PTbMU_-kuGQ@mail.gmail.com>
Date: Tue, 17 Jan 2017 12:10:18 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <5FCF2986-2CED-4573-B87D-7788DA5C354D@gmail.com>
References: <148406593094.22166.2894840062954191477.idtracker@ietfa.amsl.com> <m2fukqbbwv.wl-randy@psg.com> <F6953234-3F85-4E28-9861-433ADD01A490@gmail.com> <m2wpdzhncn.wl-randy@psg.com> <82245ef2-cd34-9bd6-c04e-f262e285f983@gmail.com> <m2d1frhjfn.wl-randy@psg.com> <18e6e13c-e605-48ff-4906-2d5531624d64@gmail.com> <CAKD1Yr1cvZ8Y3+bHeML=Xwqr+YgDspZGnZi=jqQj4qe2kMc4zw@mail.gmail.com> <m2lguffnco.wl-randy@psg.com> <CAKD1Yr1TrTiPRdyutobmb_77XJ7guNzLrg=H_p7qi4BfQ8V=GA@mail.gmail.com> <m2d1frfm6m.wl-randy@psg.com> <CAKD1Yr2Njjd8_Mr+6TRFF6C5pdcX4yFgpFVyEkykDuytu2B8mg@mail.gmail.com> <2A5073777007277764473D78@PSB> <4596c3d4-a337-f08e-7909-f14270b7085f@gmail.com> <CAN-Dau06R3iYRpYLADhvHox4C9qdsJCuxFsJapRhOQcWT4qk_g@mail.gmail.com> <CAO42Z2weZcoHiBzN94QAQ9WGhWR16PmMMFNg=5YLmr_dhPjjpA@mail.gmail.com> <fcf580ec-3617-ca5f-5337-37acb6e928ba@gmail.com> <CAKD1Yr25zNeQGvNJa=WzCjKMd9LaYrSwG=o4tUWn1Zc2ASZjrA@mail.gmail.com> <93700502-5d49-86ce-11b0-ab9904423961@gmail.com> <CAKD1Yr3wyza0_enWErMhmKKkA1ZOXPv5GG8dMT8HUQZsB5--UQ@mail.gmail.com> <CAAedzxppi5g_S05-m+B2jKMYePapPM0_wMA4XioYgwipwbKVHQ@mail.gmail.com> <CAAedzxoY6MGyvzDvUcZ44ka=5RcGwQ16fzRp29445Pa7mQYNHA@mail.gmail.com> <CAN-Dau36r2UgXPfdcdEAJ914QqvVvjGJK+=mgE9Y2tpBiDSRig@mail.gmail.com> <CAKD1Yr3RpUaNKkyTPHPWWew80cyGkiT1p7vYwfejESP4tQw31A@mail.gmail.com> <CAN-Dau0OsD4RcVUN+me98g6SJ=oaAr4HoqGtP88PTbMU_-kuGQ@mail.gmail.com>
To: David Farmer <farmer@umn.edu>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/xwLISsos8vO5E-K9MBNfiuLFjG0>
Cc: Erik Kline <ek@google.com>, 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2017 20:10:23 -0000

On Jan 16, 2017, at 9:35 PM, David Farmer <farmer@umn.edu> wrote:
> What breaks if all IIDs in global unicast are not 64 bits?  Especially other than SLACC?

To my knowledge, the only device that cares about the length of the IID is the device that inspects it, uses it, or supplies it. That would be, in most cases, functionality on the actual host and (perhaps) the router in front of it. There are additional services such as 802.1X or DHCP. Each of those cares about a 128 bit address, not an IID. Everything that doesn't care about a 128 bit address per se cares about a prefix, and the prefix [RFC7608] may have any length from 0 to 128 bits.

The one thing I can think of that cares about an IID separately from an address is SLAAC.