IETF Logo Mail Archive

Re: [nat66] [Fwd: I-D Action: draft-blake-nptv6-icmp-01.txt]

Steven Blake <slblake@petri-meat.com> Tue, 31 January 2012 05:38 UTC

Return-Path: <slblake@petri-meat.com>
X-Original-To: nat66@ietfa.amsl.com
Delivered-To: nat66@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9D7B21F86B2 for <nat66@ietfa.amsl.com>; Mon, 30 Jan 2012 21:38:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.648
X-Spam-Level:
X-Spam-Status: No, score=-101.648 tagged_above=-999 required=5 tests=[AWL=0.951, BAYES_00=-2.599, 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 29emv89b2ntU for <nat66@ietfa.amsl.com>; Mon, 30 Jan 2012 21:38:54 -0800 (PST)
Received: from elom.tchmachines.com (elom.tchmachines.com [208.76.80.198]) by ietfa.amsl.com (Postfix) with ESMTP id E434D21F86AA for <nat66@ietf.org>; Mon, 30 Jan 2012 21:38:53 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=petri-meat.com; h=Received:Subject:From:To:Cc:Date:In-Reply-To:References:Content-Type:X-Mailer:Content-Transfer-Encoding:Message-ID:Mime-Version; b=DOeoQdfV9hxg43M+5MlzvYpw1Khh7fnmfRNg7iKVJ1T+WEBERA3yijHZhvV6jjo1D9PkO5MFq6IpEb7Yx5xYONzMK0ZalHvnZJRv6hzM1XNnQs5lD777voh8BSNabEKx;
Received: from cpe-174-097-234-146.nc.res.rr.com ([174.97.234.146]) by elom.tchmachines.com with esmtpa (Exim 4.69) (envelope-from <slblake@petri-meat.com>) id 1Rs6Qd-0001mA-Q3; Tue, 31 Jan 2012 00:38:51 -0500
From: Steven Blake <slblake@petri-meat.com>
To: Dan Wing <dwing@cisco.com>
Date: Tue, 31 Jan 2012 00:38:52 -0500
In-Reply-To: <06eb01ccdfb3$672a0990$357e1cb0$@com>
References: <1327808934.3467.8.camel@tachyon> <06eb01ccdfb3$672a0990$357e1cb0$@com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.0.3 (3.0.3-1.fc15)
Content-Transfer-Encoding: 7bit
Message-ID: <1327988333.24407.7.camel@tachyon>
Mime-Version: 1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - elom.tchmachines.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - petri-meat.com
Cc: 'nat66' <nat66@ietf.org>
Subject: Re: [nat66] [Fwd: I-D Action: draft-blake-nptv6-icmp-01.txt]
X-BeenThere: nat66@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "List for discussion of IPv6-to-IPv6 NAT." <nat66.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nat66>, <mailto:nat66-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nat66>
List-Post: <mailto:nat66@ietf.org>
List-Help: <mailto:nat66-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nat66>, <mailto:nat66-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2012 05:38:54 -0000

On Mon, 2012-01-30 at 16:58 -0800, Dan Wing wrote:

> Thanks for forwarding a pointer to that document.
> 
> You might also see RFC5508, "NAT Behavioral Requirements for ICMP".
> RFC5508 includes a reference to ICMP Extensions (RFC4884) which, while
> rare in the wild, are probably worth describing so they are handled
> properly.  Hairpinning of ICMP messages may also be worth pointing out
> to implementers (so that pinging the 'external' address works, among
> other things).  It might be worth also pointing out that ICMP echo
> request/reply doesn't require special handling.  

Thanks for the pointers Dan.  I was unaware of RFCs 5508 and 4884.  We
will take a look and revise as you suggest.


Regards,

// Steve

v2.23.0 | Report a Bug | By Email