rfc.dk

Cited in: RFC 6619

13 RFCs mentioned in the text of RFC 6619 (Scalable Operation of Address Translators with Per-Interface Bindings)

RFCTitleStatusDate
1661The Point-to-Point Protocol (PPP)W. Simpson, Ed.Internet StandardJuly 1994
1918Address Allocation for Private InternetsY. Rekhter, B. Moskowitz, D. Karrenberg, G. J. de Groot, E. LearBest Current PracticeFebruary 1996
2119Key words for use in RFCs to Indicate Requirement LevelsS. BradnerBest Current PracticeMarch 1997
2516A Method for Transmitting PPP Over Ethernet (PPPoE)L. Mamakos, K. Lidl, J. Evarts, D. Carrel, D. Simone, R. WheelerInformationalFebruary 1999
2663IP Network Address Translator (NAT) Terminology and ConsiderationsP. Srisuresh, M. HoldregeInformationalAugust 1999
2993Architectural Implications of NATT. HainInformationalNovember 2000
4213Basic Transition Mechanisms for IPv6 Hosts and RoutersE. Nordmark, R. GilliganProposed StandardOctober 2005
4787Network Address Translation (NAT) Behavioral Requirements for Unicast UDPF. Audet, Ed., C. JenningsBest Current PracticeJanuary 2007
5382NAT Behavioral Requirements for TCPS. Guha, Ed., K. Biswas, B. Ford, S. Sivakumar, P. SrisureshBest Current PracticeOctober 2008
5741RFC Streams, Headers, and BoilerplatesL. Daigle, Ed., O. Kolkman, Ed., IAB · obsoleted by RFC 7841InformationalDecember 2009
6127IPv4 Run-Out and IPv4-IPv6 Co-Existence ScenariosJ. Arkko, M. TownsleyInformationalMay 2011
6146Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 ServersM. Bagnulo, P. Matthews, I. van BeijnumProposed StandardApril 2011
6333Dual-Stack Lite Broadband Deployments Following IPv4 ExhaustionA. Durand, R. Droms, J. Woodyatt, Y. LeeProposed StandardAugust 2011