Re: [j-nsp] CoS Marking/Rewrite Theory - Update!

2010-09-01 Thread Mark Tinka
On Thursday, September 02, 2010 08:28:42 am Michel de Nostredame wrote: > I had some complex examples during the transition from > Cisco CE to Juniper CE years ago, that support engineers > from Juniper SI could not able to translate them well. > And the most frustrated thing is the JTAC even not

Re: [j-nsp] CoS Marking/Rewrite Theory - Update!

2010-09-01 Thread Mark Tinka
On Thursday, September 02, 2010 07:45:45 am Chris Evans wrote: > I asked for this years ago but was blown off. Basically > got the 'that is the way it is' statement. As stated > the current implementation is very limiting. Probably just about the most frustrating quirk on the JUNOS- based plat

Re: [j-nsp] CoS Marking/Rewrite Theory - Update!

2010-09-01 Thread Chris Evans
I think you nailed it.. Juniper still thinks that service providers are their only customers. They're bringing out enterprise level devices but not bringing all the features that enterprise companies need.. They're 6 to 12months behind Cisco, anytime they bring out a new box that has a cool feature

Re: [j-nsp] CoS Marking/Rewrite Theory - Update!

2010-09-01 Thread Michel de Nostredame
On Wed, Sep 1, 2010 at 4:45 PM, Chris Evans wrote: > I asked for this years ago but was blown off.  Basically got the 'that is > the way it is' statement.  As stated the current implementation is very > limiting. > > Cisco has had this feature since I can remember on all of their platforms. As fo

Re: [j-nsp] CoS Marking/Rewrite Theory - Update!

2010-09-01 Thread Chris Evans
I asked for this years ago but was blown off. Basically got the 'that is the way it is' statement. As stated the current implementation is very limiting. Cisco has had this feature since I can remember on all of their platforms. > On Thursday, September 02, 2010 06:44:23 am Michel de > Nostredam

Re: [j-nsp] CoS Marking/Rewrite Theory - Update!

2010-09-01 Thread Mark Tinka
On Thursday, September 02, 2010 06:44:23 am Michel de Nostredame wrote: > It looks like can only perform the TOS bit to TOS bit > translation. Not quite. My understanding (I can't test this yet) - and from my discussions with Juniper - is that the Translation tables actually rewrite the ToS f

Re: [j-nsp] CoS Marking/Rewrite Theory - Update!

2010-09-01 Thread Michel de Nostredame
It looks like can only perform the TOS bit to TOS bit translation. However the most useful function will need to leverage firewall filter to perform the "TOS bit marking" on the ingress. It is very difficult to perform all those sophisticated marking on the egress interface by only leverage lame r

Re: [j-nsp] CoS Marking/Rewrite Theory - Update!

2010-09-01 Thread Mark Tinka
So this is a very old thread (from nearly two years back): http://www.mail-archive.com/juniper- n...@puck.nether.net/msg04181.html Looks like Juniper now provide support for ingress ToS remarking/rewriting, much like Cisco do. This is as opposed to the regular way it's done in JUNOS, which is r