2015
DOI: 10.17487/rfc7600
|View full text |Cite
|
Sign up to set email alerts
|

IPv4 Residual Deployment via IPv6 - A Stateless Solution (4rd)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2017
2017
2020
2020

Publication Types

Select...
4
2

Relationship

0
6

Authors

Journals

citations
Cited by 7 publications
(6 citation statements)
references
References 7 publications
0
6
0
Order By: Relevance
“…Internet engineering task force (IETF) [18] recommends to utilize 6rd. 6to4 environment still remains, to a large extent, the 6rd and the 4rd [19] for communication between IPv4 nodes through IPv6 and are applied with tunneling technology as 6to4 does, which shares features such as MTU degradation, and hence the results obtained in this experiment can be applied to these new protocols. Considering those described, 6to4 is applied in this paper.…”
Section: To4mentioning
confidence: 99%
“…Internet engineering task force (IETF) [18] recommends to utilize 6rd. 6to4 environment still remains, to a large extent, the 6rd and the 4rd [19] for communication between IPv4 nodes through IPv6 and are applied with tunneling technology as 6to4 does, which shares features such as MTU degradation, and hence the results obtained in this experiment can be applied to these new protocols. Considering those described, 6to4 is applied in this paper.…”
Section: To4mentioning
confidence: 99%
“…The IPv4-in-IPv6 mechanisms aim to provide continuous network communication to the IPv4-only devices. The most common tunnel techniques used to connect isolated IPv4 networks are MAP, and 4rd [43]. The Mapping Address and Port (MAP) refers to two related technologies: MAP-Encapsulation (MAP-E) [137] and MAP-Translation (MAP-T) [81].…”
Section: Tunnel Technologymentioning
confidence: 99%
“…4rd [69] is a well-defined stateless solution to provide residual IPv4 deployment to the users over IPv6 networks. Depending on the actual scarcity of the public IPv4 addresses, it is possible with 4rd to share a single public IPv4 address among multiple customers in a way that the users get only a limited port set, or to assign one or even more than one public IPv4 addresses to a customer.…”
Section: Rdmentioning
confidence: 99%
“…The solution is similar to MAP-T in the sense that it also uses multiple translations and port restriction. Its distinguishing features are "that TCP/UDP IPv4 packets are valid TCP/UDP IPv6 packets during domain traversal and that IPv4 fragmentation rules are fully preserved end to end" [69]. Although the scenario is relevant, but as there are much more well-known and significantly deployed IPv4aaS solutions exist, and as 4rd is rather complex and we do not know of any deployment, we consider its analysis as optional.…”
Section: Rdmentioning
confidence: 99%