RFC 7422 on Deterministic Address Mapping to Reduce Logging in Carrier-Grade NAT Deployments

rfc-editor@rfc-editor.org Wed, 24 December 2014 05:00 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 (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 5482E1AC44C for <ietf-announce@ietfa.amsl.com>; Tue, 23 Dec 2014 21:00:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id WNty1eNtoePA for <ietf-announce@ietfa.amsl.com>; Tue, 23 Dec 2014 20:59:59 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id E889F1ACC8F for <ietf-announce@ietf.org>; Tue, 23 Dec 2014 20:59:58 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id AD016181CDA; Tue, 23 Dec 2014 20:59:18 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7422 on Deterministic Address Mapping to Reduce Logging in Carrier-Grade NAT Deployments
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20141224045918.AD016181CDA@rfc-editor.org>
Date: Tue, 23 Dec 2014 20:59:18 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/yszLfKgBInJyvXiDS-T7QO0OnQY
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 24 Dec 2014 05:00:02 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7422

        Title:      Deterministic Address Mapping to Reduce 
                    Logging in Carrier-Grade NAT Deployments 
        Author:     C. Donley, C. Grundemann,
                    V. Sarawat, K. Sundaresan, O. Vautrin
        Status:     Informational
        Stream:     Independent
        Date:       December 2014
        Mailbox:    c.donley@cablelabs.com, 
        Pages:      14
        Characters: 33575
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-donley-behave-deterministic-cgn-08.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7422.txt

In some instances, Service Providers (SPs) have a legal logging
requirement to be able to map a subscriber's inside address with the
address used on the public Internet (e.g., for abuse response).
Unfortunately, many logging solutions for Carrier-Grade NATs (CGNs)
require active logging of dynamic translations.  CGN port assignments
are often per connection, but they could optionally use port ranges.
Research indicates that per-connection logging is not scalable in
many residential broadband services.  This document suggests a way to
manage CGN translations in such a way as to significantly reduce the
amount of logging required while providing traceability for abuse
response.  IPv6 is, of course, the preferred solution.  While
deployment is in progress, SPs are forced by business imperatives to
maintain support for IPv4.  This note addresses the IPv4 part of the
network when a CGN solution is in use.

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

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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