IETF Logo Mail Archive

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

DY Kim <dykim6@gmail.com> Fri, 04 August 2017 10:51 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 298B5131B3F for <v6ops@ietfa.amsl.com>; Fri, 4 Aug 2017 03:51:42 -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 nklycKz1daZZ for <v6ops@ietfa.amsl.com>; Fri, 4 Aug 2017 03:51:41 -0700 (PDT)
Received: from mail-pg0-x22d.google.com (mail-pg0-x22d.google.com [IPv6:2607:f8b0:400e:c05::22d]) (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 01EA3131CE8 for <v6ops@ietf.org>; Fri, 4 Aug 2017 03:51:41 -0700 (PDT)
Received: by mail-pg0-x22d.google.com with SMTP id v189so6608521pgd.2 for <v6ops@ietf.org>; Fri, 04 Aug 2017 03:51:40 -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=UKk+CfTiIgoMDoXghTQmm2luUFZwsnvBJSOwGEu1K90=; b=Ka+WptaK0B1zqbzdvDWd5IWotjzfl/iakWkJkfZKO0c0rQMssrjpqBtzacbtHDsdfK vAAOFvnLHs+GGGey3BNsSm/dItOV1FoUizNT3w1hwVXQegZWX1D/MDAiPR9OO++W63ul WJAgdOgBmxoOuKQAEdl2LzdgA0MuXdd2leZL8u9cFw8ixBLXTAYMTF74eMJXGJvGsAab GR3lPFcqbDd+xojFQPA4C4TFpEC4Kkkkx9Xi5Bsm2h6wQhhmWaKSFuaxzXfDUvF6gRKF G3lQISnahdxfk12xYW4mDgiYu+dAMM+MpP1Nd0HoKmIvEEIvpcw1X8zh2UDME3bNJGl1 UnUQ==
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=UKk+CfTiIgoMDoXghTQmm2luUFZwsnvBJSOwGEu1K90=; b=Q2+Uo5camaxuQH39MyleVL2aYL65uKTA9q95BtxtbIftt8Qj7X+7IApx6Y9/9DEslS x+qy4aWHBuNCv3dUTw9Fv2EcHZFGVSLS+zjpSalQl3k/y9EMU2qdiFzA435xPnuz6b2H XLn/Tuv1yydZRivoK85hh3/zs6U5mJEqSyxtGmnKRi+uX84dW69ptwOiLxqC1ea8UXEk L9d1apVdPJ3zvpFmuT89pIW6d1PJEQ+Qa1lfYs8rEm8v+spJApJVsWS1x8WmaHpfsM4z 8Ojw63m/rres+Aqts/JMBZYmdg8cQubJm8qo20xbLnmTr+Yiws/yD+Xah9WBKzWLWLMV JADA==
X-Gm-Message-State: AIVw113SjVxwT4hT6jwv38nHeYzbZ05dcgtAN/pu5L2MvZoAhp8ikqyF cyEPtWGBdIyVmHcopM8=
X-Received: by 10.84.232.7 with SMTP id h7mr2231718plk.360.1501843900565; Fri, 04 Aug 2017 03:51:40 -0700 (PDT)
Received: from [112.167.24.200] ([112.167.24.200]) by smtp.gmail.com with ESMTPSA id d86sm2604871pfk.43.2017.08.04.03.51.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 Aug 2017 03:51:40 -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: <216C3622-A9B5-40BC-814A-2575EDC58B1E@cable.comcast.com>
Date: Fri, 04 Aug 2017 19:51:37 +0900
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <169B45EE-358F-4875-8953-F7EF7BA86DF7@gmail.com>
References: <150148445751.17707.15424999122129322815@ietfa.amsl.com> <8737A9C8-F798-4503-99C7-ADBD5B220759@gmail.com> <216C3622-A9B5-40BC-814A-2575EDC58B1E@cable.comcast.com>
To: "Brzozowski, John" <John_Brzozowski@comcast.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/1DXflp2CIEnQS82RHLbl8-t9G80>
Subject: Re: [v6ops] Fwd: 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 10:51:42 -0000

Thanks.

--------
Regards,
DY








> On 4 Aug 2017, at 19:25, Brzozowski, John <John_Brzozowski@comcast.com> wrote:
> 
> As long as the router facing the end points is able to transmit a unique prefix per host in the RA then both of the cases below will work.
>  
> John
> +1-484-962-0060
>  
> From: v6ops <v6ops-bounces@ietf.org> on behalf of DY Kim <dykim6@gmail.com>
> Date: Thursday, August 3, 2017 at 21:39
> To: v6ops <v6ops@ietf.org>
> Subject: [v6ops] Fwd: I-D Action: draft-ietf-v6ops-unique-ipv6-prefix-per-host-07.txt
>  
> In the 2nd para of Sec. 4, it reads:
>  
> "The Unique IPv6 prefix can be derived from a locally managed
>    pool or aggregate IPv6 block assigned to the First Hop Provider
>    Router or from a centrally allocated pool.”
>  
> In the case the prefix is assigned from a centrally allocated pool, does this scenario include the following cases?:
>  
> o all prefixes assigned to devices on the same shared network may not be aggregatable into a single shorter prefix.
> o /64 prefixes may be assigned randomly to different devices on different share network.
>  
> ---
> DY

v2.23.0 | Report a Bug | By Email