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:08 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 78C001320CA for <v6ops@ietfa.amsl.com>; Fri, 4 Aug 2017 00:08:34 -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 UU1JIhLtGIJP for <v6ops@ietfa.amsl.com>; Fri, 4 Aug 2017 00:08:33 -0700 (PDT)
Received: from mail-pg0-x242.google.com (mail-pg0-x242.google.com [IPv6:2607:f8b0:400e:c05::242]) (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 6B2BD1320C6 for <v6ops@ietf.org>; Fri, 4 Aug 2017 00:08:33 -0700 (PDT)
Received: by mail-pg0-x242.google.com with SMTP id y129so1002346pgy.3 for <v6ops@ietf.org>; Fri, 04 Aug 2017 00:08:33 -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=PytVcf5QPyJDSGAeG8VlItU3LKLNCEdswDKVt1gxhfo=; b=spsihcnkO5oddX0UdtcJAegq3refWEjfKWgYg1GKCrxsRi9wu7ohYigkuZNoBmF04A J+0z0R23o1Bjhoep4XmVTX/iYrQrIELbY31GL0FK/Hk0v1VCk16bQNRAN1X/I2PUSgpU Nqxc3rfRWxVBT5Shh02f6KiS37uUwVJncfyBR0c7k3mPdgwvGE2nbaSHsX8lYNBVAjZS PhwhexFXOT+QonmBwY9J7EMsq+Ha3TyLyyCFR9ur9voDbPfH7b+f4hIO8/CyXv4NjaU8 +x02PSOWZAzoo4GhLI6ai+ZAiXc9q/kpoHflCpe+sTdAUrOCbGkK0MgcqNFPdrAhTNJ4 Rv1Q==
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=PytVcf5QPyJDSGAeG8VlItU3LKLNCEdswDKVt1gxhfo=; b=q3xao09+RMGavgE7a8La2Y3NmuyX+qN5LTaNg+ZoPsLM2knivQ68R8tDxe+xF2icBZ 7wKsHf/2C/cx8yyh0Yf40ujkAYKwVFN5Ali9KLMlK+lctq9ql61FcngM0MWKcuTPJg8N ykcQNJUSzGCOrS2RMDluZJ03aBxcJmqeZO6ra6qLGBE1q34ZQDmAq/iccXnV7CDuKnLG OiSfKbn4Z/vpnO4sfT3ZmfCqteANdpbhNy9idgUlAQhmUZumn9F9KzRTb1XVFiMjBCEB 1VJH3LMK1Z77xv4wpK6B4EiBWCpTj8W6GZ98eZg3UX2vjM86xinRqNt7awJtGJ/HraAM 5WQA==
X-Gm-Message-State: AIVw113HdYhOdPscYoF0jUqvJU8WgImFzCRsrWqJq9httRa4BtohIvEX YM6aK0UZnaVsoRtpREw=
X-Received: by 10.84.209.205 with SMTP id y71mr1583538plh.85.1501830512738; Fri, 04 Aug 2017 00:08:32 -0700 (PDT)
Received: from [112.167.24.200] ([112.167.24.200]) by smtp.gmail.com with ESMTPSA id s11sm1689416pfi.24.2017.08.04.00.08.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 Aug 2017 00:08:32 -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: <FB14455C-F00E-49A4-936F-03BD44C4D42C@gmail.com>
Date: Fri, 04 Aug 2017 16:08:28 +0900
Cc: john_brzozowski@cable.comcast.com, gunter.van_de_velde@nokia.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <03DD166B-D3A9-4789-AD57-EAAF1E1F017D@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>
To: v6ops list <v6ops@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/PJaBumJbA_r46VHYdc4jSOx-sSA>
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:08:34 -0000

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