RFC 7768 on Port Management to Reduce Logging in Large-Scale NATs

rfc-editor@rfc-editor.org Fri, 29 January 2016 22:36 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 1796E1A8FD7 for <ietf-announce@ietfa.amsl.com>; Fri, 29 Jan 2016 14:36:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.903
X-Spam-Status: No, score=-101.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 7adgazNuhGuZ for <ietf-announce@ietfa.amsl.com>; Fri, 29 Jan 2016 14:36:37 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0AAFD1A8F4A for <ietf-announce@ietf.org>; Fri, 29 Jan 2016 14:36:33 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 94114180094; Fri, 29 Jan 2016 14:34:52 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7768 on Port Management to Reduce Logging in Large-Scale NATs
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160129223452.94114180094@rfc-editor.org>
Date: Fri, 29 Jan 2016 14:34:52 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/tKi8UyTZA18XK572qOTRet4jmGg>
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 29 Jan 2016 22:36:39 -0000

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

        RFC 7768

        Title:      Port Management to Reduce Logging 
                    in Large-Scale NATs 
        Author:     T. Tsou, W. Li,
                    T. Taylor, J. Huang
        Status:     Informational
        Stream:     Independent
        Date:       January 2016
        Mailbox:    tina.tsou@philips.com, 
        Pages:      11
        Characters: 23442
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-tsou-behave-natx4-log-reduction-06.txt

        URL:        https://www.rfc-editor.org/info/rfc7768

        DOI:        http://dx.doi.org/10.17487/RFC7768

Various IPv6 transition strategies require the introduction of large-
scale NATs (e.g., AFTR and NAT64) to share the limited supply of IPv4
addresses available in the network until transition is complete.
There has recently been debate over how to manage the sharing of
ports between different subscribers sharing the same IPv4 address.
One factor in the discussion is the operational requirement to log
the assignment of transport addresses to subscribers.  It has been
argued that dynamic assignment of individual ports between
subscribers requires the generation of an excessive volume of logs.
This document suggests a way to achieve dynamic port sharing while
keeping log volumes low.

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