randy/draft-classless6
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

a para from nick. some cleanups. authots' addresses.

Browse source
This commit is contained in:
Randy Bush 2017-07-25 16:10:10 +09:00
parent dd4ba9e8d1
commit 2b9611d6db
1 changed files with 24 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

43
draft-nbourbaki-6man-classless-ipv6.xml
View file

@ -125,7 +125,7 @@ rate is low enough.
</section> </section>
<section anchor="Problem" title="Problem reinforced by classful addressing"> <section anchor="Problem" title="Problems Reinforced by Classful Addressing">
<t>For host computers on local area networks, generation of interface <t>For host computers on local area networks, generation of interface
identifiers is no longer necessarily bound to layer 2 addresses identifiers is no longer necessarily bound to layer 2 addresses
@ -147,11 +147,10 @@ rate is low enough.
</list> </list>
</t> </t>
<t>As IPv6 usage has evolved and grown over in recent years, it has <t>As IPv6 use has evolved and grown, it has become evident that it
become evident that it faces several scaling and coordination faces several scaling and coordination problems. These problems are
problems. These problems are analogous to allocation and analogous to allocation and coordination problems that motivated IPv4
coordination problems that motivated IPv4 CIDR allocation and later CIDR allocation and later abundant IPv4 PAT, they include:
abundant IPv4 PAT, they include:
<list> <list>
@ -163,17 +162,23 @@ rate is low enough.
<t>Hierarchical allocation of fixed-length subnets requires <t>Hierarchical allocation of fixed-length subnets requires
coordination between lower / intermediate / upper network coordination between lower / intermediate / upper network
elements. It has implicit assumption that policies and size elements. It has implicit assumption that policies and size
allocation allowed the top of the hierarchy will accommodate allocation allowed at the top of the hierarchy will accommodate
present and future use cases with fixed length subnet present and future use cases with fixed length subnet
allocation.</t> allocation.</t>
<t>Coordination with upstream networks across administrative <t>Coordination with upstream networks across administrative
domains for the allocation of fixed length subnets reveals domains for the allocation of fixed length subnets reveals topology
topology and intent that may be private in scope. Policies for and intent that may be private in scope, allowing the upstream
networks to restrict the topology that may be built. Policies for
hierarchical allocation are applied top-down and amount to hierarchical allocation are applied top-down and amount to
permission to build a particular topology (for example mobile permission to build a particular topology (for example mobile
device tethering, virtual machine instantiation, containers and device tethering, virtual machine instantiation, containers and so
so on).</t> on).</t>
<t>In the case where a device is given a /64 (e.g. mobile phone
running SLAAC only, not DHCP), there is no protocol allowing them
to provide downstream routed layer 3 subnets, because all they have
is a /64. This applies more to nodes which do not have DHCPv6.</t>
</list> </list>
</t> </t>
@ -269,14 +274,14 @@ rate is low enough.
<section anchor="authors" title="Authors"> <section anchor="authors" title="Authors">
<t>The authors of this document are as follows: <t>The authors of this document are as follows:
<list> <list>
<t> Randy Bush, Internet Initiative Japan</t> <t> Randy Bush &lt;randy@psg.com&gt;, Internet Initiative Japan</t>
<t> Brian Carpenter, University of Auckland</t> <t> Brian Carpenter &lt;brian.e.carpenter@gmail.com&gt;, University of Auckland</t>
<t> Fernando Gont, SI6 Networks / UTN-FRH</t> <t> Fernando Gont &lt;fgont@si6networks.com&gt;, SI6 Networks / UTN-FRH</t>
<t> Nick Hilliard, INEX</t> <t> Nick Hilliard &lt;nick@netability.ie&gt;, INEX</t>
<t> Joel Jaeggli, Fastly</t> <t> Joel Jaeggli &lt;joelja@bogus.com&gt;, Fastly</t>
<t> Geoff Huston, APNIC</t> <t> Geoff Huston &lt;gih@apnic.net&gt;, APNIC</t>
<t> Chris Morrow, Google, Inc.</t> <t> Chris Morrow &lt;morrowc@ops-netman.net&gt;, Google, Inc.</t>
<t> Job Snijders, NTT Communications</t> <t> Job Snijders &lt;morrowc@ops-netman.net&gt;, NTT Communications</t>
</list> </list>
</t> </t>