Anyone have a contact at www.rt.com that can encourage them to to delete
their bad aaaa ?
Some users on some devices fail to reach www.rt.com due to this dns
failure. I know about various work arounds, looking for RT.com to fix this
by deleting the bad aaaa record.
http://[::ffff:37.48.108.112] loads fine in my browsers.
Spencer,
It may be legit on your network, but people generally don't do that.... If
they publish a aaaa record, it usually has a legit v6 address in it.
That said, what they have done breaks in dns64 networks. This could be a
real downer for them in the near future if they dont remove this aaaa. I am
sending this mail in attempt to head of impending disruptions for www.rt.com
for some subset of users.
And www.rt.com is one of only two sites in the alexa top 25,000 websites to
do this thing.
Anyone have a contact at www.rt.com that can encourage them to to delete
their bad aaaa ?
Some users on some devices fail to reach www.rt.com due to this dns
failure. I know about various work arounds, looking for RT.com to fix this
by deleting the bad aaaa record.
That is a legit IPv6 address. That it won't work on a host that is IPv6-only
is a different issue, and one I agree is probably an unexpected and unwanted
side effect.
The new undersea cable systems are now capable of 18 terabits per fiber pair. It is interesting how combinations of bits are being represented by combinations of optical features.
No it is not. It is a format intended to be used only within a process to store IPv4 addresses in a single common data structure for IPv4/IPv6 or for use in a socket API so a combined IPv4/IPv6 interface can be provided. There is no requirement that other processes understand it. There is no requirement that IPv4-mapped addressing is not disabled on a system supporting IPv6 (RFC4291 section 8 security considerations).
::FFFF:0:0/96 are the IPv4-mapped addresses [RFC4291 <https://tools.ietf.org/html/rfc4291>]. Addresses
within this block should not appear on the public Internet.
You can put it in a AAAA record just as you can configure a 10.0.0.0/8 address there, but there can be no expectation that it will do anything useful outside your own environment.
>
> > Dotted-quad notation is completely valid, and works fine.
> >
> > IPv6 address - Wikipedia
> >
> > http://[::ffff:37.48.108.112] loads fine in my browsers.
>
> It may be legit on your network, but people generally don't do
> that.... If they publish a aaaa record, it usually has a legit v6
address in it.
That is a legit IPv6 address. That it won't work on a host that is
IPv6-only is a
different issue, and one I agree is probably an unexpected and unwanted
side effect.
This doesn't sound like a host issue, but a broken dns64 implementation. If
it checked the content of the aaaa response for an ::ffff... answer and
treated that as an A-only response, the host would never be involved.
Essentially the transceiver optics are applying the same modulation and
coding that have been used in point-to-point microwave for a long time...
Starting from OOK, up to BPSK and then on to QPSK, 16QAM and possibly 64QAM
with varying levels of FEC.
A singlemode fiber is just an extremely narrow diameter waveguide. Big
difference in frequency between a 71-86 GHz FDD radio pair and optical at
191 to 196 THz.
Apparently 40 gigs is the limit of simple laser flash equals 1, no flash equals 0. Above that threshold the signal becomes larger than an ITU 50 gigahertz channel. Most new undersea cables are using QPSK or 8 QAM and talking about 16 QAM.
Not just "talking about" 16QAM is in active use for subsea high capacity
channels... Both Xtera and Infinera are shipping DWDM terminals for
installation at cable landing stations that use 16QAM for 100/200/400 Gbps
superchannels.
I don't see wide spread deployment. The most recently built TransAtlantic cable is Aquacomms It is QPSK and 130 100 gig waves per pair. Does one really need more? C-Lion, the new Finland/Germany cable is 18 terabits per fiber pair. I think that is 8 QAM. Is that a representative sample? I don't know. It is certainly a small sample and hence could be highly contained by random error. Since so many ISPs dropped their Layer 2 networks in favor of buying cheap transit, the market for 100 gig waves is limited to Tier 1 ISPs, a few huge hosting companies, and the public Web giants in shopping, social media. I have been told that the video streaming guys like Netflix are more similar to Akamai than Telia. Dense local footprints.
Bottom line. I don't think the demand is sufficient or the interface costs on the customer side sufficiently low. Could be wrong about both.