Re: draft-ietf-v6ops-nat64-pb-statement-req-0: behave requirements

Pekka Savola <pekkas@netcore.fi> Sun, 27 July 2008 17:43 UTC

Return-Path: <owner-v6ops@ops.ietf.org>
X-Original-To: ietfarch-v6ops-archive@core3.amsl.com
Delivered-To: ietfarch-v6ops-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 339833A68AA for <ietfarch-v6ops-archive@core3.amsl.com>; Sun, 27 Jul 2008 10:43:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.199
X-Spam-Level:
X-Spam-Status: No, score=-102.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, 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 zcmetkPV-2uL for <ietfarch-v6ops-archive@core3.amsl.com>; Sun, 27 Jul 2008 10:43:16 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 7BA5D3A6934 for <v6ops-archive@lists.ietf.org>; Sun, 27 Jul 2008 10:43:16 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.69 (FreeBSD)) (envelope-from <owner-v6ops@ops.ietf.org>) id 1KNAGc-0005QS-DA for v6ops-data@psg.com; Sun, 27 Jul 2008 17:42:46 +0000
Received: from [2001:670:86:3001::1] (helo=netcore.fi) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from <pekkas@netcore.fi>) id 1KNAGY-0005Pk-WC for v6ops@ops.ietf.org; Sun, 27 Jul 2008 17:42:44 +0000
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id m6RHgb2e002578; Sun, 27 Jul 2008 20:42:37 +0300
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id m6RHgbga002575; Sun, 27 Jul 2008 20:42:37 +0300
Date: Sun, 27 Jul 2008 20:42:37 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
cc: 'IPv6 Operations' <v6ops@ops.ietf.org>
Subject: Re: draft-ietf-v6ops-nat64-pb-statement-req-0: behave requirements
In-Reply-To: <4889FC58.4020003@it.uc3m.es>
Message-ID: <alpine.LRH.1.10.0807272039110.2217@netcore.fi>
References: <4889FC58.4020003@it.uc3m.es>
User-Agent: Alpine 1.10 (LRH 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: ClamAV 0.93.1/7840/Sun Jul 27 03:10:52 2008 on otso.netcore.fi
X-Virus-Status: Clean
Sender: owner-v6ops@ops.ietf.org
Precedence: bulk
List-ID: <v6ops.ops.ietf.org>

On Fri, 25 Jul 2008, marcelo bagnulo braun wrote:
> R7: Behave requirements
> The translation mechanism MUST be compliant with the requirements for IPv4 
> NATs defined in [I-D.ietf-behave-tcp] and in [RFC4787] when applicable. These 
> requirements should be interpreted with the IPv6 side on the IPv6-IPv4 
> translator being the IPv4 private side of the conventional NAT.
>
> First, this heavily assumes v6 initiated communications. If we have nat46, we 
> probably don?t need this
>
> Question: should we include the behave requirements for ICMP, DCCP, SCTP?

I believe making unmodified "ping", "traceroute" and PMTUD work across 
the translator is a MUST have.  The loss of operational diagnostic 
capabilities is too big otherwise.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings