IETF Logo Mail Archive

Re: [v6ops] I-D Action: draft-ietf-v6ops-unique-ipv6-prefix-per-host-07.txt

DY Kim <dykim6@gmail.com> Fri, 04 August 2017 07:33 UTC

Return-Path: <dykim6@gmail.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 0BA4513214A for <v6ops@ietfa.amsl.com>; Fri, 4 Aug 2017 00:33:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 P_uAtoJ5QR4N for <v6ops@ietfa.amsl.com>; Fri, 4 Aug 2017 00:33:03 -0700 (PDT)
Received: from mail-pg0-x241.google.com (mail-pg0-x241.google.com [IPv6:2607:f8b0:400e:c05::241]) (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 C9231131891 for <v6ops@ietf.org>; Fri, 4 Aug 2017 00:33:03 -0700 (PDT)
Received: by mail-pg0-x241.google.com with SMTP id 123so1040011pga.5 for <v6ops@ietf.org>; Fri, 04 Aug 2017 00:33:03 -0700 (PDT)
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=ClEA2ukFbCm3pq8gwufB9c/fhfDigqr+KoHeom1cG40=; b=jr6vFMWLE1t80boTjhAkDtjR9URKdXJu3K23BL6eKbMCaixVic7qoEN8LZVQzhdQyw terEVbPa/8VAzSqyciwOQSR0LW5dZN6N7Ek6NT9Je62Uh3m4eYTmkwY+WNqW5Wxh+6aj DNggwXkrLZ0oVrDa9zuUAatsWhZ117OiN0/G619RbOkHVZG2beepflNOD+9RXyWdzcqc BN3KoqNxmY1db2ws70JD2/pbWuL8vGMYKvgeHHg3OKmdYSLt+eaXh7tKnzyCsqUp+Kvj GDV3FK+sYQcxxnCVPpazWGgMaVvda6+uEmGt7CjJYpUaES7Egj8YE4Oton14zTrSM+7l LeoA==
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=ClEA2ukFbCm3pq8gwufB9c/fhfDigqr+KoHeom1cG40=; b=nO5qE+vcqfUPB22bhgaVMAcuBSgM/v21xBFSXUFeuZZJ1BjRFKKyU4jleFpnD1vTgp ehiRc/kGjn/fvHcm8Imw+EPAIvDE/4Sa9WH54fBy1OOdI06VKKNyvWrk2eAyoi5kQcUq 0s2sPZGNHqY0kphbG6f8SsE527BPUfm8VxsJ2QsEgZzwIPl4vUzTkcx4YxEhEUC9Qe1Y Eov7x/xUB9Gccpa/R1u3thSxQCGU37Z30E1XGgOStDGesJUhU1B38rhX0+GjCxVcZw/l WrlrFwk2eo74Fr642YiAlnKGZ17iHxxpC1B13viySvPl7PlsXaSZVK5/WTnxWMFJqSSH AqLA==
X-Gm-Message-State: AIVw112zBlaB5gpUHJajR5tiViuQXd+0rJgqbmrBN39mB4ULPhLjBzlT dqTA98PJo4JamMmvIMU=
X-Received: by 10.99.56.5 with SMTP id f5mr1384996pga.162.1501831983075; Fri, 04 Aug 2017 00:33:03 -0700 (PDT)
Received: from [112.167.24.200] ([112.167.24.200]) by smtp.gmail.com with ESMTPSA id 78sm1552909pft.123.2017.08.04.00.33.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 Aug 2017 00:33:02 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: DY Kim <dykim6@gmail.com>
In-Reply-To: <03DD166B-D3A9-4789-AD57-EAAF1E1F017D@gmail.com>
Date: Fri, 04 Aug 2017 16:32:59 +0900
Cc: john_brzozowski@cable.comcast.com, gunter.van_de_velde@nokia.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <84572649-27D9-4781-8162-F01C969624EB@gmail.com>
References: <150148445751.17707.15424999122129322815@ietfa.amsl.com> <E6AC9174-3D6E-4FAD-B84B-B7E58FB149BC@gmail.com> <CAO42Z2xEs6RauD6Oo_NbqOh+FRVAu3NuveewSvRx7g1hS2-ToQ@mail.gmail.com> <94BC4E17-D490-4F50-9E99-2AAA081CD43C@gmail.com> <CAO42Z2zR_bWPqOHM7-RNsPX78np45UV=J67YD5gbpoCPUaLkAQ@mail.gmail.com> <FB14455C-F00E-49A4-936F-03BD44C4D42C@gmail.com> <03DD166B-D3A9-4789-AD57-EAAF1E1F017D@gmail.com>
To: v6ops list <v6ops@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/kfLTuYN-rydMEaKFcpei4UJU9wY>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-unique-ipv6-prefix-per-host-07.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: Fri, 04 Aug 2017 07:33:05 -0000

4291bis further states:

> Except for the knowledge of the subnet boundary discussed in the
>    previous paragraphs, nodes should not make any assumptions about the
>    structure of an IPv6 address.

This sounds to me “no structure other than subnet should be assumed.” … which could mean (local, not global) prefixes may not be assigned to network entities other than subnets.

Isn’t the I-D in conflict with this parent (to-be-)standard RFC 4291bis?

----------
Regards,
DY








> On 4 Aug 2017, at 16:08, DY Kim <dykim6@gmail.com> wrote:
> 
> Is this I-D compliant with RFC 4291bis stating..?:
> 
>   |          n bits               |           128-n bits            |
>   +-------------------------------+---------------------------------+
>   |       subnet prefix           |           interface ID          |
>   +-------------------------------+————————————————————————---------+
> 
> The prefix under discussion in the I-D should be a node prefix, whereas all RFC 4291 comments on is the subnet prefix.
> 
> Or.. is it that the subnet prefix mentioned in RFC 4291bis is just an example, and you can assign prefixes to any network entities including node, subnet, or whatever?
> 
> 
> Regards,
> DY

v2.23.0 | Report a Bug | By Email