rfc.dk

Cited in: RFC 4966

14 RFCs mentioned in the text of RFC 4966 (Reasons to Move the Network Address Translator - Protocol Translator (NAT-PT) to Historic Status)

RFCTitleStatusDate
1035Domain names - implementation and specificationP. MockapetrisInternet StandardNovember 1987
1858Security Considerations for IP Fragment FilteringG. Ziemba, D. Reed, P. TrainaInformationalOctober 1995
2663IP Network Address Translator (NAT) Terminology and ConsiderationsP. Srisuresh, M. HoldregeInformationalAugust 1999
2765Stateless IP/ICMP Translation Algorithm (SIIT)E. Nordmark · obsoleted by RFC 6145Proposed StandardFebruary 2000
2766Network Address Translation - Protocol Translation (NAT-PT)G. Tsirtsis, P. Srisuresh · obsoleted by RFC 4966HistoricFebruary 2000
2960Stream Control Transmission ProtocolR. Stewart, Q. Xie, K. Morneault, C. Sharp, H. Schwarzbauer, T. Taylor, I. Rytina, M. Kalla, L. Zhang, V. Paxson · obsoleted by RFC 4960Proposed StandardOctober 2000
3027Protocol Complications with the IP Network Address TranslatorM. Holdrege, P. SrisureshInformationalJanuary 2001
3128Protection Against a Variant of the Tiny Fragment Attack (RFC 1858)I. MillerInformationalJune 2001
3314Recommendations for IPv6 in Third Generation Partnership Project (3GPP) StandardsM. Wasserman, Ed.InformationalSeptember 2002
3484Default Address Selection for Internet Protocol version 6 (IPv6)R. Draves · obsoleted by RFC 6724Proposed StandardMarch 2003
3498Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) ArchitecturesJ. Kuhfeld, J. Johnson, M. ThatcherProposed StandardMarch 2003
4033DNS Security Introduction and RequirementsR. Arends, R. Austein, M. Larson, D. Massey, S. RoseProposed StandardMarch 2005
4215Analysis on IPv6 Transition in Third Generation Partnership Project (3GPP) NetworksJ. Wiljakka, Ed.InformationalOctober 2005
4294IPv6 Node RequirementsJ. Loughney, Ed. · obsoleted by RFC 6434InformationalApril 2006