Re: [NSIS] NATFW NSLP; using REA mode for blocking data flows

Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Mon, 17 April 2006 21:35 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FVbNr-0005Vr-Nc; Mon, 17 Apr 2006 17:35:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FVbNq-0005Vl-2O for nsis@ietf.org; Mon, 17 Apr 2006 17:35:46 -0400
Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FVbNo-0006t5-LW for nsis@ietf.org; Mon, 17 Apr 2006 17:35:46 -0400
Received: (qmail invoked by alias); 17 Apr 2006 21:35:41 -0000
Received: from ip-80-226-170-244.vodafone-net.de (EHLO [10.227.144.47]) [80.226.170.244] by mail.gmx.net (mp033) with SMTP; 17 Apr 2006 23:35:41 +0200
X-Authenticated: #29516787
Message-ID: <44440A22.2080300@gmx.net>
Date: Mon, 17 Apr 2006 23:35:30 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ali Fessi <ali.fessi@uni-tuebingen.de>
Subject: Re: [NSIS] NATFW NSLP; using REA mode for blocking data flows
References: <4443F69F.9000708@uni-tuebingen.de>
In-Reply-To: <4443F69F.9000708@uni-tuebingen.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: nsis <nsis@ietf.org>
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org

Hi Ali,

it is true that there is some history about the REA name. However, we 
also want to avoid having too many configuration options: REA and BLOCK

Now, you just use one message, which is has the name REA, and the DR 
does not need to know whether he is behind a NAT, a firewall or a 
combination of both.

Ciao
Hannes

Ali Fessi wrote:
> Hi all,
> 
> the REA mode (Reserving External Address) was originally called REA mode 
> because it is used by hosts behind a NAT to reserve a publicly reachable 
> IP address (and port number).
> 
> Now, the REA mode is also used by hosts behind a firewall to signal to a 
> firewall for blocking data traffic.
> 
> Although from functionality point of view, it might be fine to use the 
> same name for these two similar functionalities; but from terminology 
> point of view, this is rather confusing to signal for blocking data 
> traffic and call it "REA mode".
> 
> So, why not use a different name that matches more the functionality, 
> something like "BLOCK mode" for example?! This would make it easier for 
> the readers to understand.
> 
> Cheers,
> Ali


_______________________________________________
nsis mailing list
nsis@ietf.org
https://www1.ietf.org/mailman/listinfo/nsis