RFC 7021 on Assessing the Impact of Carrier-Grade NAT on Network Applications
rfc-editor@rfc-editor.org Thu, 19 September 2013 23:47 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62DE621F859A for <ietf-announce@ietfa.amsl.com>; Thu, 19 Sep 2013 16:47:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.297
X-Spam-Level:
X-Spam-Status: No, score=-102.297 tagged_above=-999 required=5 tests=[AWL=0.303, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HPFpgsbvhzw8 for <ietf-announce@ietfa.amsl.com>; Thu, 19 Sep 2013 16:47:52 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 78D4721F85E3 for <ietf-announce@ietf.org>; Thu, 19 Sep 2013 16:47:52 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 89AB58E01A; Thu, 19 Sep 2013 16:41:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7021 on Assessing the Impact of Carrier-Grade NAT on Network Applications
From: rfc-editor@rfc-editor.org
Message-Id: <20130919234119.89AB58E01A@rfc-editor.org>
Date: Thu, 19 Sep 2013 16:41:19 -0700
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Sep 2013 23:47:53 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7021
Title: Assessing the Impact of Carrier-Grade NAT
on Network Applications
Author: C. Donley, Ed.,
L. Howard, V. Kuarsingh,
J. Berg, J. Doshi
Status: Informational
Stream: Independent
Date: September 2013
Mailbox: c.donley@cablelabs.com,
william.howard@twcable.com,
victor@jvknet.com,
j.berg@cablelabs.com,
jineshd@juniper.net
Pages: 29
Characters: 66150
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-donley-nat444-impacts-06.txt
URL: http://www.rfc-editor.org/rfc/rfc7021.txt
NAT444 is an IPv4 extension technology being considered by Service
Providers as a means to continue offering IPv4 service to customers
while transitioning to IPv6. This technology adds an extra Carrier-
Grade NAT (CGN) in the Service Provider network, often resulting in
two NATs. CableLabs, Time Warner Cable, and Rogers Communications
independently tested the impacts of NAT444 on many popular Internet
services using a variety of test scenarios, network topologies, and
vendor equipment. This document identifies areas where adding a
second layer of NAT disrupts the communication channel for common
Internet applications. This document was updated to include the
Dual-Stack Lite (DS-Lite) impacts also.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC