rfc.dk

Cited by: RFC 4966

12 RFCs whose text mentions RFC 4966 (Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status), newest first

RFCTitleStatusDate
7873Domain Name System (DNS) CookiesD. Eastlake 3rd, M. AndrewsProposed StandardMay 2016
6889Analysis of Stateful 64 TranslationR. Penno, T. Saxena, M. Boucadair, S. SivakumarInformationalApril 2013
6586Experiences from an IPv6-Only NetworkJ. Arkko, A. KeranenInformationalApril 2012
6219The China Education and Research Network (CERNET) IVI Translation Design and Deployment for the IPv4/IPv6 Coexistence and TransitionX. Li, C. Bao, M. Chen, H. Zhang, J. WuInformationalMay 2011
6180Guidelines for Using IPv6 Transition Mechanisms during IPv6 DeploymentJ. Arkko, F. BakerInformationalMay 2011
6145IP/ICMP Translation AlgorithmX. Li, C. Bao, F. Baker · obsoleted by RFC 7915Proposed StandardApril 2011
6144Framework for IPv4/IPv6 TranslationF. Baker, X. Li, C. Bao, K. YinInformationalApril 2011
6127IPv4 Run-Out and IPv4-IPv6 Co-Existence ScenariosJ. Arkko, M. TownsleyInformationalMay 2011
5971GIST: General Internet Signalling TransportH. Schulzrinne, R. HancockExperimentalOctober 2010
5128State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)P. Srisuresh, B. Ford, D. KegelInformationalMarch 2008
4942IPv6 Transition/Co-existence Security ConsiderationsE. Davies, S. Krishnan, P. SavolaInformationalSeptember 2007
4924Reflections on Internet TransparencyB. Aboba, Ed., E. DaviesInformationalJuly 2007