Templin, Fred L wrote:
Not necessarily, as IPv4 can take care of itself and IPv6
is hopeless.
IPv4 can take care of it how - with broken PMTUD or
As you know, RFC1191 style PMTUD is broken both for IPv4
and IPv6.
with broken fragmentation/reassembly?
Fragmentation is fine, especially
valdis.kletni...@vt.edu wrote:
And you tell the rest of the world that customer A's SMTP port is on
125, and B's is on 225, and Z's is up at 2097, how?
How? In draft-ohta-e2e-nat-00.txt, I already wrote:
A server port number different from well known ones may be specified
through
Owen DeLong wrote:
Showing that you don't actually understand what everyone else means when
they say end-to-end.
Where is your point only to demonstrate that you don't understand
whatend to end means?
No carrier is going to implement that for obvious reasons.
Besides, that's not
I think, the length of Interface ID be 64 is so mostly because IEEE
works now with 64bit EUI identifiers (instead of older 48bit MAC
addresses). I.e. compatibility between IEEE and IETF IPv6 would be the
main reason for this Interface ID to be 64.
And this is so, even though there are IEEE
Le 07/06/2012 22:27, Ricky Beam a écrit :
On Wed, 06 Jun 2012 10:58:05 -0400, Chuck Church
chuckchu...@gmail.com wrote:
Does anyone know the reason /64 was proposed as the size for all L2
domains?
There is one, and only one, reason for the ::/64 split: SLAAC. IPv6
is a classless addressing
-Original Message-
From: Masataka Ohta [mailto:mo...@necom830.hpcl.titech.ac.jp]
Sent: Tuesday, June 19, 2012 6:10 AM
To: Templin, Fred L
Cc: Owen DeLong; nanog@nanog.org
Subject: Re: IPv6 day and tunnels
Templin, Fred L wrote:
Not necessarily, as IPv4 can take care of itself
Paul,
Circling back here, you all set here? Should see the following over IPv6 and
IPv4:
xfinity.comcast.net
xfinitytv.comcast.net
John
=
John Jason Brzozowski
Comcast Cable
m) +1-609-377-6594
e) mailto:john_brzozow...@cable.comcast.com
o)
Hello everyone,
I was trying to understand reason for high latency between my BSNL (AS9829)
connection and a specific Germany based server on M-Online.
I can see forward path is correct but reverse path is:
traceroute to 117.200.57.47 (117.200.57.X), 30 hops max, 60 byte packets
1
On Tue, Jun 19, 2012 at 4:15 PM, Anurag Bhatia m...@anuragbhatia.com wrote:
I wonder what exactly is different/wrong in case of BSNL block
117.200.48.0/20? Is BSNL selectively announcing it only from Reliance's
California based router and not any other router in Europe?
there's a fiber cut in
Hello Christopher
Thanks for pointing out SMW4 cut as reported here -
http://www.renesys.com/blog/2012/06/smw4-break-on-south-asia.shtml
As far as I see it is likely not linked to issue. I guess it is still some
bad routing issue rather then impact of cable cut since I have seen similar
On Tue, 2012-06-19 at 22:28 +0900, Masataka Ohta wrote:
It is trivially:
host - home UPnP NAT - Carrier UPnP NAT - Internet
- Carrier UPnP NAT - home UPnP NAT - host
Trivially? I think this looks much nicer:
host - Internet - host
The way it used to be before
I have also noticed that traffic sourced in NYC destined for Qatar across NTT
seems to now go from NYC - SJC - SNG and ends up being about 180+ms longer
than just going over the atlantic.
I've seen this a few times (only with NTT routes).
Thanks,
-Drew
-Original Message-
From: Anurag
On Jun 19, 2012, at 8:44 AM, Alexandru Petrescu wrote:
I think, the length of Interface ID be 64 is so mostly because IEEE
works now with 64bit EUI identifiers (instead of older 48bit MAC
addresses). I.e. compatibility between IEEE and IETF IPv6 would be the
main reason for this Interface
On Tue, Jun 19, 2012 at 06:42:33PM -0400, Drew Weaver wrote:
I have also noticed that traffic sourced in NYC destined for Qatar across NTT
seems to now go from NYC - SJC - SNG and ends up being about 180+ms longer
than just going over the atlantic.
I've seen some people in the middle
Circling back here, you all set here? Should see the following over IPv6 and
IPv4:
xfinity.comcast.net
xfinitytv.comcast.net
from tokyo
rair.psg.com:/Users/randy ping6 xfinity.comcast.net
PING6(56=40+8+8 bytes) 2001:240:6a8::4034:839d:25d9:2418 --
2001:240:bb8f:8000::d295:8725
16 bytes
Karl Auer wrote:
host - home UPnP NAT - Carrier UPnP NAT - Internet
- Carrier UPnP NAT - home UPnP NAT - host
Trivially? I think this looks much nicer:
host - Internet - host
Yes, if only the Internet were uniform.
However, compared to
anyone have any opinions on the two subject vendors, with general
regard to 10GE transceivers? SR multi-mode data center stuff for my
application.
appreciate on/off list replies!
ryanL
Nope.
I signed up for the beta a long time ago, and have never heard anything about
IPv6 on the residential network. My company is one of the first (if not *the*
first) direct connect commercial customers that got IPv6 connectivity in Ohio.
I only see a few other ASNs that are directly
On Tue, 19 Jun 2012 22:21:11 +0900, Masataka Ohta said:
Or, a NAT gateway may receive packets to certain ports and behave as
an application gateway to end hosts, if request messages to the
server contains information, such as domain names, which is the case
with DNS, SMTP and
Can someone from Road Runner HoldCo LLC ( AS7843
http://bgp.he.net/AS7843 ) Please
contact me offline?
NOC Ticket #1718425 not getting any progress, packetloss to AS32421
affecting multiple mutual customers.
Thank you,
--
Shawn Marck
shawn.ma...@blacklotus.net | http://www.blacklotus.net
Black
Can anyone comment on Cisco 6509E Smartnet chassis coverage? In the past,
chassis has always meant, not just the passive chassis itself, but all of
the components including supervisor cards, line cards, power supplies, fan
trays, etc. Now it appears that Cisco is requiring Smartnet coverage on
I'd say hardware replacement is only a small benefit of smartnet, or I
would have found it more economical to just stock spares a long time ago.
You also received technical support in addition to software updates.
In fact, IMHO, the greatest benefit is the access to Cisco development
resources
22 matches
Mail list logo
