On Thu, Aug 01, 2002 at 04:35:03PM +0300, Rafi Sadowsky wrote:
## On 2002-07-31 10:09 +0200 Jesper Skriver typed:
JS> On Wed, Jul 31, 2002 at 12:22:30AM -0700, Randy Bush wrote: JS> > JS> > > AFAIK 12.0S only has the "service provider" feature set JS> > JS> > i fear that the joke is on us. at least one other train seems to JS> > have been merged into the ex-isp train. not sure how much. can't JS> > get a straight answer. welcome back to 1997, and bye bye what JS> > stability we had. JS> JS> It looks something like JS> JS> 12.0(21)S1----12.0(21)S2---- ... only for a limited time JS> / JS> ---12.0(x)S-----12.0(21)S +---12.0(22)S----12.0(23)S---- ... JS> / JS> ---12.0(x)ST----12.0(21)ST--+ JS> JS> So basicly 12.0(22)S is what would have been 12.0(22)ST if they hadn't JS> renumbered. JS> JS> The "old" S train will be recieving bug fixes as 12.0(21)S1 S2 S3 etc. JS> for a limited period of time. JS> JS> So be carefull when you go from 12.0(x)S, x <= 21 to 12.0(y)S, y > 21
Thanks for the info
I thought that the next evolution in the "S" series was supposed to be merger of 12.1E and 12.0S into 12.2S ? - anyone know about that ?
There is a 12.2(x)S comming - as I understand it, it's a merge of 12.0(x)ST and the service provider related features in 12.2(x)T /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Senior network engineer @ AS3292, TDC Tele Danmark One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them.