[Netext] next steps for netext

rkoodli at starentnetworks.com (Koodli, Rajeev) Mon, 06 April 2009 17:24 UTC

From: "rkoodli at starentnetworks.com"
Date: Mon, 06 Apr 2009 13:24:27 -0400
Subject: [Netext] next steps for netext
References: <C5FF8EA2.2636C%basavaraj.patil@nokia.com><Pine.GSO.4.63.0904060903000.22326@irp-view13.cisco.com><18034D4D7FE9AE48BF19AB1B0EF2729F27F29D55A8@NOK-EUMSG-01.mgdnok.nokia.com> <Pine.GSO.4.63.0904061006170.2863@sgundave-sb100.cisco.com>
Message-ID: <4D35478224365146822AE9E3AD4A2666035AAA8D@exchtewks3.starentnetworks.com>

 
I tend to agree that host configurations cannot be ruled out. Case in point: if IPv6 is disabled by default, does enabling it count as host change here? It should not be. Similarly, if folks use a particular technique (e.g., virtual i/f support) provided by host OS, that should be acceptable. If the mechanism is not supported, the feature will not be available, and this can be stated in a 'Requirement' section of the appropriate document.
 
-Rajeev
 

________________________________