[Netext] next steps for netext

teemu.savolainen at nokia.com (teemu.savolainen at nokia.com) Mon, 06 April 2009 16:21 UTC

From: "teemu.savolainen at nokia.com"
Date: Mon, 06 Apr 2009 18:21:52 +0200
Subject: [Netext] next steps for netext
In-Reply-To: <Pine.GSO.4.63.0904060903000.22326@irp-view13.cisco.com>
References: <C5FF8EA2.2636C%basavaraj.patil@nokia.com> <Pine.GSO.4.63.0904060903000.22326@irp-view13.cisco.com>
Message-ID: <18034D4D7FE9AE48BF19AB1B0EF2729F27F29D55A8@NOK-EUMSG-01.mgdnok.nokia.com>

Hi Sri,  

>-----Original Message-----
>From: netext-bounces at mail.mobileip.jp 
>[mailto:netext-bounces at mail.mobileip.jp] On Behalf Of ext Sri 
>Gundavelli
>Sent: 06 April, 2009 19:11
>"unmodified host" can leverage that feature. As we discussed 
>earlier, we have a major terminology problem, on what is 
>"modified" vs "un modified". If I use Windows SDK and 
>implement a virtual interface, no one can claim the host is 
>now modified. Its an application, or a configuration such as 
>using bridge ctl utuility in Linux. Its not changing any of 

At least in my vocabulary that counts as modified host - things are changed in a host to make it behave differently. 

Best regards,

	Teemu