GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Internet Engineering Task Force
  • System Status
  • Report a Bug
  • IRTF.org
  • IAB.org
  • Datatracker
  • Author Resources
  • RFC Editor
  • rfc-dist Info Page
  • rfc-interest Info Page

This view

  • Original page
  • New address

GeezerVison is showing www.rfc-editor.org — BCP 127 subseries contains 3 RFCs | RFC Editor

BCP 127

Subscribe to BCP 127

Get notified when:

  • An RFC is added to or removed from this BCP
  • A RFC within the collection changes status, obsoleted by, updates, updated by, or subseries.

BCPs are stable identifiers for Best Current Practices. A BCP may consist of a single RFC or a group of RFCs related to a specific IETF process or recommended guidelines. The collection may become empty as the BCP evolves.

RFC 7857: BCP 127: Updates to Network Address Translation (NAT) Behavioral Requirements

Best Current Practice
  • R. Penno
  • S. Perreault
  • M. Boucadair, Ed.
  • S. Sivakumar
  • K. Naito
  • April 2016
  • IETF publication
  • Web and Internet Transport

Abstract

This document clarifies and updates several requirements of RFCs 4787, 5382, and 5508 based on operational and development experience. The focus of this document is Network Address Translation from IPv4 to IPv4 (NAT44).

This document updates RFCs 4787, 5382, and 5508.

Abstract

This document clarifies and updates several requirements of RFCs 4787, 5382, and 5508 based on operational and development experience. The focus of this document is Network Address Translation from IPv4 to IPv4 (NAT44).

This document updates RFCs 4787, 5382, and 5508.

RFC 6888: BCP 127: Common Requirements for Carrier-Grade NATs (CGNs)

Best Current Practice
  • S. Perreault, Ed.
  • I. Yamagata
  • S. Miyakawa
  • A. Nakagawa
  • H. Ashida
  • April 2013
  • IETF publication
  • Transport Area

Abstract

This document defines common requirements for Carrier-Grade NATs (CGNs). It updates RFC 4787.

Abstract

This document defines common requirements for Carrier-Grade NATs (CGNs). It updates RFC 4787.

RFC 4787: BCP 127: Network Address Translation (NAT) Behavioral Requirements for Unicast UDP

Best Current Practice
  • F. Audet, Ed.
  • C. Jennings
  • January 2007
  • IETF publication
  • Transport Area

Abstract

This document defines basic terminology for describing different types of Network Address Translation (NAT) behavior when handling Unicast UDP and also defines a set of requirements that would allow many applications, such as multimedia communications or online gaming, to work consistently. Developing NATs that meet this set of requirements will greatly increase the likelihood that these applications will function properly. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

Abstract

This document defines basic terminology for describing different types of Network Address Translation (NAT) behavior when handling Unicast UDP and also defines a set of requirements that would allow many applications, such as multimedia communications or online gaming, to work consistently. Developing NATs that meet this set of requirements will greatly increase the likelihood that these applications will function properly. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.