-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sam Stickland wrote:
| Even if they are decrementing TTL inside of their MPLS core, the TTL
| expired message still has to traverse the entire MPLS LSP (tunnel), so
| the latency reported for each hop is in fact the latency of the last
| hop in the
On Thu, 26 Jun 2008, Frank Bulk - iNAME wrote:
Interestingly enough, when I trace from my Cisco router it seems to show
some MPLS labels after the hop of interest (12.88.71.13 to 12.122.112.78,
only 24 msec here!). I'm not sure how our Cisco box derives these from a
foreign network.
The ICMP
On Jun 26, 2008, at 11:36 PM, Randy Bush wrote:
Frank Bulk - iNAME wrote:
Just google tbr1.sl9mo.ip.att.net and it's clear that high
latency through
that point has occurred before. And guess what kind of customer
complained
to me about the latency? A gamer.
you can pay a lot of money
Our upstream provider has a connection to ATT (12.88.71.13) where I
relatively consistently measure with a RTT of 15 msec, but the next hop
(12.122.112.22) comes in with a RTT of 85 msec. Unless ATT is sending that
traffic over a cable modem or to Europe and back, I can't see a reason why
there
Deep Packet Inspection engine delay. G
On Jun 26, 2008, at 6:51 PM, Frank Bulk wrote:
Our upstream provider has a connection to ATT (12.88.71.13) where I
relatively consistently measure with a RTT of 15 msec, but the next
hop
(12.122.112.22) comes in with a RTT of 85 msec. Unless ATT is
When I asked ATT about the sudden latency jump I see in traceroutes,
they told me it was due to how their MPLS network is setup.
--John
Frank Bulk wrote:
Our upstream provider has a connection to ATT (12.88.71.13) where I
relatively consistently measure with a RTT of 15 msec, but the next hop
: Re: Possible explanations for a large hop in latency
When I asked ATT about the sudden latency jump I see in traceroutes,
they told me it was due to how their MPLS network is setup.
--John
Frank Bulk wrote:
Our upstream provider has a connection to ATT (12.88.71.13) where I
relatively
. Yocum [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2008 7:04 PM
To: [EMAIL PROTECTED]
Cc: nanog list
Subject: Re: Possible explanations for a large hop in latency
When I asked ATT about the sudden latency jump I see in traceroutes,
they told me it was due to how their MPLS network is setup
On Thu, 26 Jun 2008, John T. Yocum wrote:
The explanation I got, was that the latency seen at the first hop was
actually a reply from the last hop in the path across their MPLS
network. Hence, all the following hops had very similar latency.
Personally, I thought it was rather strange for
explanations for a large hop in latency
When I asked ATT about the sudden latency jump I see in traceroutes,
they told me it was due to how their MPLS network is setup.
--John
Frank Bulk wrote:
Our upstream provider has a connection to ATT (12.88.71.13) where I
relatively consistently measure
PROTECTED]
Cc: nanog list
Subject: Re: Possible explanations for a large hop in latency
The explanation I got, was that the latency seen at the first hop was
actually a reply from the last hop in the path across their MPLS
network. Hence, all the following hops had very similar latency.
Personally, I
:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2008 8:09 PM
To: [EMAIL PROTECTED]
Cc: nanog list
Subject: Re: Possible explanations for a large hop in latency
The explanation I got, was that the latency seen at the first hop was
actually a reply from the last hop in the path across their MPLS
network
PROTECTED]
Sent: Thursday, June 26, 2008 8:20 PM
To: John T. Yocum
Cc: [EMAIL PROTECTED]; nanog list
Subject: Re: Possible explanations for a large hop in latency
They probably don't propagate TTL w/in their MPLS core. Depending on how
they have MPLS implemented, you may only see 2 hops
Frank Bulk - iNAME wrote:
Just google tbr1.sl9mo.ip.att.net and it's clear that high latency through
that point has occurred before. And guess what kind of customer complained
to me about the latency? A gamer.
you can pay a lot of money for the net propagation anomaly detection
services that
14 matches
Mail list logo
