Re: NAT behavior for IP ID field

Joe Touch <touch@isi.edu> Thu, 06 January 2011 18:06 UTC

Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 81AA53A6E28 for <ietf@core3.amsl.com>; Thu, 6 Jan 2011 10:06:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.473
X-Spam-Level:
X-Spam-Status: No, score=-102.473 tagged_above=-999 required=5 tests=[AWL=0.126, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BmafhYk19OLK for <ietf@core3.amsl.com>; Thu, 6 Jan 2011 10:05:59 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id B590D3A6C9B for <ietf@ietf.org>; Thu, 6 Jan 2011 10:05:59 -0800 (PST)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p06I7f53026327 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 6 Jan 2011 10:07:41 -0800 (PST)
Message-ID: <4D2604ED.8080709@isi.edu>
Date: Thu, 06 Jan 2011 10:07:41 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: John Kristoff <jtk@cymru.com>
Subject: Re: NAT behavior for IP ID field
References: <20100831150444.22bd579e@t61p>
In-Reply-To: <20100831150444.22bd579e@t61p>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jan 2011 18:06:00 -0000

Although this is a fairly old thread, I didn't see mention of the IPv4 
ID draft we've been working on in INTAREA that addresses this:

https://datatracker.ietf.org/doc/draft-ietf-intarea-ipv4-id-update/

It was updated last Oct.

See esp. Sec 9.

Joe

On 8/31/2010 1:04 PM, John Kristoff wrote:
> I'm trying to locate an RFC that spells out the behavioral
> requirements, expectations or guidelines for NAT handling of the IP ID
> field, particularly for UDP messages.  Section 3.2.5 in RFC 3235
> briefly mentions issues surrounding IP fragmentation and reassembly,
> but  it doesn't specifically say if NATs should re-write IDs as a
> general rule.
>
> RFC 4787 doesn't seem to address this either.
>
> If this is not written down anywhere, do NATs generally rewrite the ID
> field with or without the MF bit set?
>
> For background and reference, I refer you to Steve Bellovin's 'A
> Technique for Counting NATted Hosts', particularly section IV.
>
> Thanks for any pointers,
>
> John
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf