Pete, Correct And everyonce in a while x.y+1(1) has an additional feature that x.y(last)T didn't get. There is a real scary chart on the website about this.
David -- http://dcp.dcptech.com > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Pete Templin > Sent: Monday, February 04, 2008 8:58 PM > To: Ben Steele > Cc: [email protected] > Subject: Re: [c-nsp] dead WIC-1ADSL? > > Ben Steele wrote: > > Oh and in regards to actaully getting it show up, you need > a T train > > IOS, 12.3(8)T and on.. > > Ok, I'm going to throw the "huh?" flag here. It's been my > understanding > for years that x.yT becomes x.(y+1) mainline, and on that date the > following things happen: > > x.(y+1) inherits all of the features of x.yT at that moment > x.(y+1) moves forward with ONLY that list of features > x.yT stops receiving (most) new features at that moment > x.(y+1)T is created and begins receiving new features > > As such, if a feature came out in 12.3(8)T, one could find it in 12.4 > (and wouldn't HAVE to go to 12.4T just to keep the feature). > Am I wrong > (for the most part...let's not nitpick over exceptions)? > > (Obviously, every now and then Cisco chooses to use (x+1).0 > instead of > x.(y+1), but that's immaterial for this discussion.) > > pt > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
