rfc.dk

Cited by: RFC 1631

15 RFCs whose text mentions RFC 1631 (The IP Network Address Translator (NAT)), newest first

RFCTitleStatusDate
9710Simple Fixes to the IP Flow Information Export (IPFIX) Entities IANA RegistryM. Boucadair, B. ClaiseProposed StandardFebruary 2025
6740Identifier-Locator Network Protocol (ILNP) Architectural DescriptionRJ Atkinson, SN BhattiExperimentalNovember 2012
3099Request for Comments Summary RFC Numbers 3000-3099S. GinozaInformationalNovember 2001
3022Traditional IP Network Address Translator (Traditional NAT)P. Srisuresh, K. EgevangInformationalJanuary 2001
3021Using 31-Bit Prefixes on IPv4 Point-to-Point LinksA. Retana, R. White, V. Fuller, D. McPhersonProposed StandardDecember 2000
2993Architectural Implications of NATT. HainInformationalNovember 2000
2767Dual Stack Hosts using the "Bump-In-the-Stack" Technique (BIS)K. Tsuchiya, H. Higuchi, Y. Atarashi · obsoleted by RFC 6535InformationalFebruary 2000
2766Network Address Translation - Protocol Translation (NAT-PT)G. Tsirtsis, P. Srisuresh · obsoleted by RFC 4966HistoricFebruary 2000
2694DNS extensions to Network Address Translators (DNS_ALG)P. Srisuresh, G. Tsirtsis, P. Akkiraju, A. HeffernanInformationalSeptember 1999
2391Load Sharing using IP Network Address Translation (LSNAT)P. Srisuresh, D. GanInformationalAugust 1998
2182Selection and Operation of Secondary DNS ServersR. Elz, R. Bush, S. Bradner, M. PattonBest Current PracticeJuly 1997
2101IPv4 Address Behaviour TodayB. Carpenter, J. Crowcroft, Y. RekhterInformationalFebruary 1997
2072Router Renumbering GuideH. BerkowitzInformationalJanuary 1997
2071Network Renumbering Overview: Why would I want it and what is it anyway?P. Ferguson, H. BerkowitzInformationalJanuary 1997
1621Pip Near-term ArchitectureP. FrancisHistoricMay 1994