[prev in list] [next in list] [prev in thread] [next in thread]
List: afripv6-discuss
Subject: Re: [AfrIPv6-Discuss] references and books
From: Lee Howard <lee.howard () retevia ! net>
Date: 2018-08-21 15:17:05
Message-ID: d475f75f-0f54-ceeb-3f4e-483320c6e323 () retevia ! net
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Good question. My answer last year was here:
http://www.wleecoyote.com/blog/IPv6reading.html
With less than a day of reading, you will understand enough about IPv6
to get to work. The rest will be adapting your specific configurations
and reading documentation. Updated links/notes below:
1. draft-ietf-6man-rfc4291bis
<https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/?include_text=1>,
"IPv6 Address Architecture." Sure, you could read RFC4291, but this
draft is pretty close to done, and contains all the current updates.
2. RFC4861 <https://www.ietf.org/rfc/rfc4861.txt>, "Neighbor Discovery."
It's long, at almost 100 pages, but you can probably skip most of the
packet format stuff. If you understand the stuff in this document,
including ND, DAD, RS, RA, NS, NA, then you have a solid understanding
of IPv6.
3. You need both of these in order to understand how magically hosts get
provisioned:
* RFC4862 <https://www.ietf.org/rfc/rfc4862.txt>, "IPv6 Stateless
Address Autoconfiguration" or "SLAAC", and
* RFC8106 <https://www.ietf.org/rfc/rfc8106.txt>, "The RDNSS Option in
RA".
4. RFC3315 <https://www.ietf.org/rfc/rfc3315.txt>, "DHCPv6". You should
know IA_NA and IA_PD. You should learn as much about DHCPv6 as you know
about DHCP. One of the interesting parts is how DHCPv6 options can be
used to provision transition mechanisms (but that's another post).
5. RFC8201 <https://datatracker.ietf.org/doc/rfc8201/> "Path MTU
Discovery". Understanding this will let you troubleshoot the most common
IPv6 problem.
For extra credit:RFC8200 <https://datatracker.ietf.org/doc/rfc8200/>,
"IPv6 Specification". I'm sure it sounds weird to say that the base spec
is extra credit, but other than packet structure, the important stuff
here is Extension Headers and flow labels, and there aren't many
practical uses for those yet. If you want to think of creative uses for
IPv6, then you should look into those. But if you've read the full list
up to this point, you have enough information to design, build, and
operate an IPv6 network. Advice is included in several deployment
guidelines, but AfriNIC probably has the best direct support anywhere,
and you can't beat the price.
Lee
On 08/17/2018 04:08 PM, Abdellah EL MOUDDEN wrote:
>
> Hello,
>
> I want references and books on fast moving to IPv6
>
> cordially
> ᐧ
>
>
> _______________________________________________
> AfrIPv6-Discuss mailing list
> AfrIPv6-Discuss@afrinic.net
> https://lists.afrinic.net/mailman/listinfo/afripv6-discuss
[Attachment #5 (text/html)]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Good question. My answer last year was here: <a
moz-do-not-send="true"
href="http://www.wleecoyote.com/blog/IPv6reading.html">http://www.wleecoyote.com/blog/IPv6reading.html</a></p>
<p>With less than a day of reading, you will understand enough about
IPv6 to get to work. The rest will be adapting your specific
configurations and reading documentation. Updated links/notes
below:</p>
<p>1. <a
href="https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/?include_text=1"
style="color: rgb(102, 102, 102); text-decoration: none;
border-bottom: 1px dotted;">draft-ietf-6man-rfc4291bis</a>,
"IPv6 Address Architecture." Sure, you could read RFC4291, but
this draft is pretty close to done, and contains all the current
updates.</p>
<p>2. <a href="https://www.ietf.org/rfc/rfc4861.txt" style="color:
rgb(102, 102, 102); text-decoration: none; border-bottom: 1px
dotted;">RFC4861</a>, "Neighbor Discovery." It's long, at almost
100 pages, but you can probably skip most of the packet format
stuff. If you understand the stuff in this document, including ND,
DAD, RS, RA, NS, NA, then you have a solid understanding of IPv6.<br>
</p>
3. You need both of these in order to understand how magically hosts
get provisioned:
<ul>
<li style="margin-left: 200px;"><a
href="https://www.ietf.org/rfc/rfc4862.txt" style="color:
rgb(102, 102, 102); text-decoration: none; border-bottom: 1px
dotted;">RFC4862</a>, "IPv6 Stateless Address
Autoconfiguration" or "SLAAC", and</li>
<li style="margin-left: 200px;"><a
href="https://www.ietf.org/rfc/rfc8106.txt" style="color:
rgb(102, 102, 102); text-decoration: none; border-bottom: 1px
dotted;">RFC8106</a>, "The RDNSS Option in RA".</li>
</ul>
<p>4. <a href="https://www.ietf.org/rfc/rfc3315.txt" style="color:
rgb(102, 102, 102); text-decoration: none; border-bottom: 1px
dotted;">RFC3315</a>, "DHCPv6". You should know IA_NA and IA_PD.
You should learn as much about DHCPv6 as you know about DHCP. One
of the interesting parts is how DHCPv6 options can be used to
provision transition mechanisms (but that's another post).</p>
<p>5. <a href="https://datatracker.ietf.org/doc/rfc8201/"
style="color: rgb(102, 102, 102); text-decoration: none;
border-bottom: 1px dotted;" moz-do-not-send="true">RFC8201</a>
"Path MTU Discovery". Understanding this will let you troubleshoot
the most common IPv6 problem.<br>
</p>
<br>
For extra credit:<span> <a moz-do-not-send="true"
href="https://datatracker.ietf.org/doc/rfc8200/">RFC8200</a></span>,
"IPv6 Specification". I'm sure it sounds weird to say that the base
spec is extra credit, but other than packet structure, the important
stuff here is Extension Headers and flow labels, and there aren't
many practical uses for those yet. If you want to think of creative
uses for IPv6, then you should look into those. But if you've read
the full list up to this point, you have enough information to
design, build, and operate an IPv6 network. Advice is included in
several deployment guidelines, but AfriNIC probably has the best
direct support anywhere, and you can't beat the price.<br>
<br>
Lee<br>
<br>
<br>
<div class="moz-cite-prefix">On 08/17/2018 04:08 PM, Abdellah EL
MOUDDEN wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKMex-V4ufZmkyVkH3zGO1GUxZZERD77npGeJw-htpg37N3_kQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div dir="ltr">
<div><br>
</div>
<div>Hello, <br>
</div>
<div><br>
</div>
I want references and books on fast moving to IPv6<br>
<div><br>
</div>
<div>cordially<br>
</div>
</div>
<div hspace="streak-pt-mark" style="max-height:1px"><img alt=""
style="width:0px;max-height:0px;overflow:hidden"
src="https://mailfoogae.appspot.com/t?sender=aZWxtb3VkZGVuLmFiQGdtYWlsLmNvbQ%3D%3D&type=zerocontent&guid=112593ed-890e-48c7-ba6c-5cfac1fd4dd9"
moz-do-not-send="true"><font size="1" color="#ffffff">ᐧ</font></div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
AfrIPv6-Discuss mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:AfrIPv6-Discuss@afrinic.net">AfrIPv6-Discuss@afrinic.net</a> <a \
class="moz-txt-link-freetext" \
href="https://lists.afrinic.net/mailman/listinfo/afripv6-discuss">https://lists.afrinic.net/mailman/listinfo/afripv6-discuss</a>
</pre>
</blockquote>
<br>
</body>
</html>
_______________________________________________
AfrIPv6-Discuss mailing list
AfrIPv6-Discuss@afrinic.net
https://lists.afrinic.net/mailman/listinfo/afripv6-discuss
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic