On 9/Mar/19 11:18, Saku Ytti wrote: > So Gert's question 'y tho?' is very much valid, and the most obvious > reasons is because Juniper doesn't want to increase the product cost > to cover lab testing from any-to-any, as it would mean ever increase > money and time cost to release. By setting some fixed rules, they have > fixed amount of work to test the upgrade. I doubt Cisco has actually > formally supported any-to-any on classic IOS either. You may be right. I have a dinner planned with some Juniper folk that seem to have clue. I'll definitely ask this question and see what lands. Mark. _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
- [j-nsp] Old JunOS upgrade path Robert Hass
- Re: [j-nsp] Old JunOS upgrade path Rolf Hanßen
- Re: [j-nsp] Old JunOS upgrade path Gert Doering
- Re: [j-nsp] Old JunOS upgrade pa... Eldon Koyle
- Re: [j-nsp] Old JunOS upgrad... Gert Doering
- Re: [j-nsp] Old JunOS u... Sander Steffann
- Re: [j-nsp] Old JunOS u... Mark Tinka
- Re: [j-nsp] Old Jun... Saku Ytti
- Re: [j-nsp] Old... Gert Doering
- Re: [j-nsp] Old... Mark Tinka
- Re: [j-nsp] Old Jun... Gert Doering
- Re: [j-nsp] Old JunOS u... Tom Beecher
- Re: [j-nsp] Old Jun... Saku Ytti
- Re: [j-nsp] Old... adamv0025
- Re: [j-nsp] Old... Timur Maryin via juniper-nsp
- Re: [j-nsp] Old JunOS upgrade path Aaron Gould
- Re: [j-nsp] Old JunOS upgrade pa... Ola Thoresen
- Re: [j-nsp] Old JunOS upgrade path Ola Thoresen
- Re: [j-nsp] Old JunOS upgrade path Niall Donaghy
- Re: [j-nsp] Old JunOS upgrade path Pierre Emeriaud
