The MPLS WG Archive

["alok" <alok.dube@apara.com>]

hi Nitin,

just curious...
your IP result says "0.023" end to end..
can u share "IP across what was your ingress LER" 
IP across your Egress LER 
and IP across your core too for a given packet?

-rgds
alok
----- Original Message ----- 
From: nitin p <nitin_panj@yahoo.com>
To: <GAlmaalouf@aol.com>; <eosborne@cisco.com>; <jshen@cad.zju.edu.cn>
Cc: <rameshbabu_j@infosys.com>; <mpls-ops@mplsrc.com>; <mpls@UU.NET>
Sent: Monday, December 09, 2002 7:54 PM
Subject: Re: [MPLS-OPS]: Jitter and MPLS


> Hi George,
> I have posted my results in of the mails, but here
> they are again:
> 
> Ingress: 3.665 milli seconds
> Egress: 0.035 milliseconds
> core:    0.018 milliseconds
>  
> IP: 0.023 milliseconds.
> 
> For my measurements I have attached a sniffer at both
> incomming and outgoing interface (same sniffer for
> both so no clocking issue). I did the same thing for
> boths LSR and LERs. Question of number of LSRs should
> not affect the results, considering my measuring
> technique.
> Jing said He is also getting similar results, I am not
> sure how he has done his measurement.
> 
> Thanks,
> Nitin
>  
>  
> 
> --- GAlmaalouf@aol.com wrote:
> > Nitin-
> > 
> > It would be much helpful if you can specify the
> > delay in a quantitative 
> > manner. This way we can really understand what are
> > you talking about in term 
> > of delays.  Also, the specific number of Hops or LPS
> > router, how many egress 
> > and ingress steps involved in the calculation. A
> > general observation would 
> > not  be very accurate, since the implementation
> > would be very different from 
> > one application versus the other, and from one type
> > of services versus 
> > another.
> > 
> > Thanks-
> > 
> > George
> > 
> > 
> > 
> 
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
> 
> -------
> The MPLS-OPS Mailing List
> Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
> Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
>