指導老師 吳俊興 學生 A1015532 賴逸翔 NAT64 RFC6052 1 Outline 介紹 地址格式 Prefix Suffix 參考 資料 2 介紹 3 NAT 網路 地址 轉換 ID: 425402
Download Presentation The PPT/PDF document "網路通訊協定" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
網路通訊協定
指導老師 : 吳俊興 學生: A1015532 賴逸翔
NAT64 RFC6052
1Slide2
Outline
介紹地址格式PrefixSuffix參考資料
2Slide3
介紹
3NAT : 網路地址轉換(Network Address
Translation)NAT64 (NAT 6 TO 4) : IPv6轉IPv4或IPv4
轉
IPv6
。
術語
:IPv4-converted
IPv6
addresses、 IPv4-embedded IPv6 addresses、 IPv4-translatable IPv6 addresses、 Network-Specific Prefix、 Well-Known PrefixSlide4
介紹
4IPv4-embedded IPv6 addressesIPv6 addresses in which 32 bits contain an IPv4
address.IPv4-converted IPv6 addressesIPv6 addresses used to represent IPv4 nodes in an IPv6 network.
IPv4-translatable IPv6 addresses
IPv6
addresses assigned to IPv6 nodes for use with stateless translation. Slide5
介紹
5Network-Specific Prefixan IPv6 prefix assigned by an organization for use in algorithmic mapping.
Well-Known Prefixthe IPv6 prefix defined in this document for use in an algorithmic mapping.Slide6
6
包裝IPv4 進IPv6Concatenate the prefix, the 32 bits of the IPv4 address, and the suffix to obtain a 128-bit address.
Insert the null octet "u" at the appropriate position (bits 64 to
71
),
if
the prefix length is less than 96
bits
取出
IPv4If the prefix is 96 bits long, extract the last 32 bits of theIPv6 address For the other prefix lengths, remove the "u" octet to obtain a 120-bit sequence, then extract the 32 bits following the prefix.地址格式Slide7
地址格式
7Slide8
地址格式
8Slide9
Prefix
9Well-Known Prefix The Well-Known Prefix SHOULD be used in IPv4-converted IPv6 addresses
The Well-Known Prefix SHOULD NOT be used in IPv4-
translatable IPv6 addresses
.
The Well-Known Prefix MAY appear in inter-domain routing tables
The Well-Known Prefix MUST NOT be used to represent non-global IPv4
addressesSlide10
Prefix
10Network-Specific Prefixes IPv4-translatable IPv6
addresses MUST use the selected Network-Specific Prefix.Slide11
Prefix
(Stateless、stateful mapping)11
Stateless mappingIPv4-translatable IPv6 addresses MUST use the selected Network-Specific Prefix.
Both IPv4-
translatable IPv6 addresses and IPv4-converted IPv6 addresses
SHOULD
use the same prefix
.
The stateless translation can be used for Scenario
1, Scenario 2, Scenario 5, and Scenario 6
情境一
情境二Slide12
12
ScenarioScenario 1
(IPv6 network -> IPv4 Internet)
Scenario
2
(IPv4
->
IPv6)
an
ISP holding a /32 allocation SHOULD use a /40 prefix, and a site holding a /48 allocation SHOULD use a /56 prefix.Scenario 5 (IPv6 ->
IPv4)
Scenario 6 (IPv4 -> IPv6)
the
deployment SHOULD use
a
/64 or a /96 prefix.
Prefix
(Stateless
、
stateful
mapping)Slide13
13
Both on stateful mappingThe Well-Known Prefix SHOULD be used in these scenariosAll scenarios, the translation MAY use a Network-Specific PrefixThe Well-Known Prefix MUST NOT be used for Scenario 3
as this would lead to using the Well-Known Prefix with non-global IPv4 addresses.
Prefix
(Stateless
、
stateful
mapping)Slide14
suffix
14These bits are reserved for future extensions and SHOULD be set to zero.
RFC 4291Slide15
參考資料
15RFC6052 http://tools.ietf.org/pdf/rfc6052.pdf電腦王
http://www.techbang.com/posts/15861-3-ip-introduction-to-network-architecture-concept-classification-and-the-subnet-mask?page=2維基百科
http://
zh.wikipedia.org/wiki/NAT
中國教育和科研計算機網
http
://
zh.wikipedia.org/wiki/NAT