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

DY Kim <dykim6@gmail.com> Fri, 04 August 2017 02:04 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 B326F129ADD for <v6ops@ietfa.amsl.com>; Thu, 3 Aug 2017 19:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 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, HTML_MESSAGE=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 oMv3qaanm94Y for <v6ops@ietfa.amsl.com>; Thu, 3 Aug 2017 19:04:26 -0700 (PDT)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (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 0CFEF1277BB for <v6ops@ietf.org>; Thu, 3 Aug 2017 19:04:26 -0700 (PDT)
Received: by mail-pf0-x236.google.com with SMTP id t86so1930525pfe.2 for <v6ops@ietf.org>; Thu, 03 Aug 2017 19:04:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:message-id:references:to:date; bh=409bR96q4KO0bkZM9etBM2rLoVQveYEtcPR5cM5r7gI=; b=sRcjYBIlqls33IOOf9ilh1/ZuaWXImhA0NuZmbO+Dojh4JzrT950swwA+lfQv7NbTw ATTsl18LCDcGGnRLGSEnBYpBsFJYey9p60qpkfyT9sKKmczyDA1hQFzCsTrzNwnSIdG5 OtaHieNj+qCW2AyZsGL657CNgywpBOpHjwEic2gPvwre/PlfClg0fYTERYpAJLlHlsCK nhb/d+HDJxZIrsmssR/y6cDlLhOD1TLC+YpQFBP9tl5FFucVFDvBZ7g5VQFUNwcKjYDq Iy6rqYdqRAF4gvy7aFsKhOuCJ84o/3zVzN/cmx8dcBa4MOwhI7xKlje/KzJGXHQxaVgP Vqcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:references :to:date; bh=409bR96q4KO0bkZM9etBM2rLoVQveYEtcPR5cM5r7gI=; b=Uvw9A4162R3HG6got8j0szicv7Zy4uFAxhaAnQ7x0EZFGcHc4RLtApfxpDR7GgZgvt L1CTs+P6VGW7Rekqb+4AUnFvLYQxw4EVtDrm2nr9AvNUd9vaON6XdzV0NaPFg51zEiZF hrvGFaFvWv9eV89ngxYXi912NZdVlgEaKg19ZZx4KaAqmBHQN94bCEYjWWzQ/b6VymUu qqGP6RrgaQjBQs9cepNk8E0x7m/jDPpbJqxYKr/BOm2ek/ebyR/5kwq41CBAwiTtHcQC fnWs3wqVyOeBpTXzK5KOGiEEoCFA7+S/nZZZgl6NygisqwKDiA+Il8WBaGBy6BcbPhVP gXeQ==
X-Gm-Message-State: AIVw113TeIo/r0JoQK+MYbuJHQiS4FW1xXzaHWyE9uIatC2tNqRUGGdr cakRb3LpQyGGp5xHkrI=
X-Received: by 10.84.232.135 with SMTP id i7mr843914plk.193.1501812265315; Thu, 03 Aug 2017 19:04:25 -0700 (PDT)
Received: from [112.167.24.200] ([112.167.24.200]) by smtp.gmail.com with ESMTPSA id n129sm391635pfn.27.2017.08.03.19.04.24 for <v6ops@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Aug 2017 19:04:24 -0700 (PDT)
From: DY Kim <dykim6@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D813C194-FAA3-446A-9B69-9C008B8BFABB"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <148E758F-1B18-4E8F-95AB-0E713F711684@gmail.com>
References: <B6FEFEC2-F694-4495-91AB-BC3F8DA7F478@gmail.com>
To: v6ops@ietf.org
Date: Fri, 04 Aug 2017 11:04:22 +0900
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/30lMWM2Pj1SUzkj6Iw90KjCH9IM>
Subject: [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 02:04:28 -0000

In regards to the wording "provider managed shared network”.

Does ‘provider’ here mean exclusively any commercial ISPs or the kind? Can it also be interpreted as ‘site managed shared network’ where site could be any AS?

---
DY






> Begin forwarded message:
> 
> Subject: [v6ops] I-D Action: draft-ietf-v6ops-unique-ipv6-prefix-per-host-07.txt
> Date: 4 August 2017 at 10:20:53 GMT+9
> To: v6ops@ietf.org
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the IPv6 Operations WG of the IETF.
> 
>        Title           : Unique IPv6 Prefix Per Host
>        Authors         : John Jason Brzozowski
>                          Gunter Van De Velde
> 	Filename        : draft-ietf-v6ops-unique-ipv6-prefix-per-host-07.txt
> 	Pages           : 8
> 	Date            : 2017-07-31
> 
> Abstract:
>   In some IPv6 environments, the need has arisen for hosts to be able
>   to utilize a unique IPv6 prefix, even though the link or media may be
>   shared.  Typically hosts (subscribers) on a shared network, either
>   wired or wireless, such as Ethernet, WiFi, etc., will acquire unique
>   IPv6 addresses from a common IPv6 prefix that is allocated or
>   assigned for use on a specific link.
> 
>   In most deployments today, IPv6 address assignment from a single IPv6
>   prefix on a shared network is done by either using IPv6 stateless
>   address auto-configuration (SLAAC) and/or stateful DHCPv6.  While
>   this is still viable and operates as designed, there are some large
>   scale environments where this concept introduces significant
>   performance challenges and implications, specifically related to IPv6
>   router and neighbor discovery.
> 
>   This document outlines an approach utilising existing IPv6 protocols
>   to allow hosts to be assigned a unique IPv6 prefix (instead of a
>   unique IPv6 address from a shared IPv6 prefix).  Benefits of unique
>   IPv6 prefix over a unique IPv6 address from the service provider
>   include improved subscriber isolation and enhanced subscriber
>   management.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-v6ops-unique-ipv6-prefix-per-host/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-v6ops-unique-ipv6-prefix-per-host-07
> https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-unique-ipv6-prefix-per-host-07
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-unique-ipv6-prefix-per-host-07
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops