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:15 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 C9A5D132145 for <v6ops@ietfa.amsl.com>; Fri, 4 Aug 2017 00:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 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, URIBL_BLOCKED=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 ve7RQYoJlqq2 for <v6ops@ietfa.amsl.com>; Fri, 4 Aug 2017 00:15:19 -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 B4465132143 for <v6ops@ietf.org>; Fri, 4 Aug 2017 00:15:19 -0700 (PDT)
Received: by mail-pg0-x241.google.com with SMTP id 123so1003975pga.5 for <v6ops@ietf.org>; Fri, 04 Aug 2017 00:15:19 -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=tu0JcX8XfzlFafUcCu5NVAVwkv/EJvgKpWMKN6Xj/lw=; b=ZCWTteMge0rzZ+NqmCs0MHVu6uo/Sasxoqisrq7Vy210CJBC4KbioEreGN4FYOY95v b27psEHQuZagKhPJNgu4GpU0dZ2RXtNb3IeKy1/lTmZWg4poJyjtzaJCD88AeQ/Ql8m/ jdOpFOxQ/WRQKq1eZyx9SgkQAKmR3wsiq+tV5KYLsVSivyGp51vllzSdN8swHYs6RrNO st4MU66WH4TNmIOVf2SrPmxMAqflU7/a05UKxLUyK8z3GKG9IJ1WL5xs/P/NscJbfzP0 wmUhT+ZcYiRjWl2PCEByOoSRoO4MOb6fZxMJBBoLMAW2AQsCik0/KWHZReCMpl7zKcdz MaBQ==
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=tu0JcX8XfzlFafUcCu5NVAVwkv/EJvgKpWMKN6Xj/lw=; b=uDwqwOG08vGuIAl+d/VhPnG3530tzCXYieHJGkdZfs9zpPdvw0QII0a/VRMyjaL3MB g3tp6wWc+L6Fnp2L0P8UinLtioS8FXHSD9f2+M3sqyiISFC260q/svUbuKuJvnU/D6Jw NeT36a+RPZFPmhsm1CP6uqQgdXNTuKOahgUxzM4fIs0/vGUpwgKMI1McZnqtLovQZrJV ZM3aLMwtN1I+w9t9CyiVLCZzGzOaNLy1GVDbtZxrDYebqDYQkC93Sz0XvKgzHrxXLGf6 6mgjWUuYPmwZ2QRSEaIOpDS8+EyViBIOmmFpBub0FeZLXJFHYzykAOqg2wxItBVgakpS C8AQ==
X-Gm-Message-State: AIVw112JkyQ3/maitRmdagvKBUzu26Ava/yilkaPVVr9dF/MEFk6yGMz Vj77EvNn7oCGDw==
X-Received: by 10.84.142.133 with SMTP id 5mr1664387plx.148.1501830919279; Fri, 04 Aug 2017 00:15:19 -0700 (PDT)
Received: from [112.167.24.200] ([112.167.24.200]) by smtp.gmail.com with ESMTPSA id t12sm1796768pfg.12.2017.08.04.00.15.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 Aug 2017 00:15:18 -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: <alpine.DEB.2.02.1708040512220.2261@uplift.swm.pp.se>
Date: Fri, 04 Aug 2017 16:15:15 +0900
Cc: v6ops list <v6ops@ietf.org>, john_brzozowski@cable.comcast.com, gunter.van_de_velde@nokia.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <336987B8-56B0-4C59-A9B1-8B91D4D09BD1@gmail.com>
References: <150148445751.17707.15424999122129322815@ietfa.amsl.com> <2E470571-1620-4527-9489-D4D953000040@gmail.com> <alpine.DEB.2.02.1708040512220.2261@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Mn5oFCavyVQuxpisJFIaP3piOv8>
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:15:21 -0000

So, you need neither ND nor DAD with the proposed BCP…?

--------
Regards,
DY








> On 4 Aug 2017, at 12:12, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> 
> On Fri, 4 Aug 2017, DY Kim wrote:
> 
>> At the end of Sec. 4, it reads:
>> 
>> "After the UE/subscriber received the RA, and the associated flags, it
>>  will assign itself a 128 bit IPv6 address using SLAAC.  Since the
>>  address is composed by the UE/subscriber device itself, it will need
>>  to verify that the address is unique on the shared network.  The UE/
>>  subscriber will for that purpose, perform Duplicate Address Detection
>>  algorithm.  This will occur for each address the UE attempts to
>>  utilize on the shared provider managed network.”
>> 
>> Now the each device has a unique prefix, there’d be no chance that 128 bit addresses generated by different devices should collide. Do we need DAD here?
> 
> No, we don't.
> 
> That is what https://tools.ietf.org/html/draft-pioxfolks-6man-pio-exclusive-bit-02 is about.
> 
> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se

v2.23.0 | Report a Bug | By Email