Actually the firmware doesn't need to upgradable, you just need to be able to set and save the current date occasionally to non volatile memory. The device could do this itself periodically after synchronising itself. Yes, there is a small risk of spoofed GPS signals causing an anomalous date to be saved but even there the risk can be minimised. Time more that x seconds since last recording, more that y seconds of continuously synchronised signals. For mobile GPS devices more that z km's of travel as well while switched on.
A running system shouldn't fail across a GPS epoch event. Given this is not the first epoch event all of the equipment should have been able to handle this. This can be simulated in QA testing prior to releasing the firmware image.
Well our servers use DANE and TLSA records so they don't fallback if the site has published the record.
MTA-STS depends on DNSSEC working while, paradoxically, claiming it is needed to avoid DNSSEC. Go analyse the protocol.
The majority of the worlds authoritative server to recursive server DNS lookups are DNSSEC validated today though the result of that validation may be "insecure". MTA's that support DANE also validate DNS responses. There was never a need for MTA-STS. Just deploy DANE. It isn't subject to the attacks MTA-STS is.
And which calculations are those? Actual examples of where it is *needed* for real problems not theoretical examples.
For timers you calculate a timer assuming a negative leap second at the end of each month in a interval so you don't overshoot, fire the timer then reset it to fire again with the leap second adjusted time as the base. Repeat if necessary (requires intervals over ~200000 years initially).
You read them by saying each value and using the word colon. fd93:7065:ab8e:: is eff dee nine three colon seven zero six five colon...
FD00::/8 is the equivalent of RFC 1918. You pick 40 random bits (toss a coin 40 times, tails=0, heads=1) and append them to FD to give you a/48 prefix which is your site prefix. (e.g fd93:7065:ab8e::/48). You then have ~65000/64 subnets to use.
That said your ISP will delegate you a prefix using prefix delegation. Typically it will be a/56 which will give you 256/64 sized subnets which your routers will automatically assign to links as needed. The ISP is allocated IPv6 address space from the RIRs with the assumption that they will hand out/48's to customers. If the/56 is too small complain to your ISP as they have more space to give you. If your ISP only gives you a/64 find another ISP as they are not doing the correct thing.
It is and the ACCC fined large telcos and made them pay back the differences between the plan the customer was on and the plan that was achievable on the link. Customers that were affected could also cancel their contracts with no penalty for early termination.
The ACCC also drew up new advertising guidelines which require ISP's to advertise the rate achievable in peak times.
Going forward, if after connection, it is found that the rate you signed up for is not achievable on the link you can downgrade the contracted rate to what is achievable or pull out of the contract.
They announce the battery program within days of it being reported that older iPhones were running slower in benchmarks on the iOS versions that have the code that restricts the clock frequency.
Yes, it was a coincidence. You are seeing conspiracies where there are none.
No. You have to prove it was a foreseeable outcome.
Shooting a gun into the air isnâ(TM)t likely to kill someone but it is a foreseeable outcome and has happened. Thatâ(TM)s why rifle ranges have banks and restricted areas down range to stop people being killed by stray bullets.
RFC's can document a idea. There doesn't need to be a implementation before a RFC is published. To get to standard status there needs to be two interoperating implementations.
I've had RFC's published that documented ideas which I needed others to realise after the RFC was published. I've also had RFC's published that were based on years of deployment of the concept covered by the RFC.
Actually DNSSEC validation is common. Somewhere between 40% and 60% of lookups world wide are validated as the biggest resolvers farm in the world do DNSSEC validation and everyone using them has the answers validated. What isn't wide spread is domains that are signed so despite the answers being sent to the validator they come out marked as 'insecure', rather than 'secure' or in the case they are forged 'bogus'.
Every time a ISP turns on validation on their recursive servers large numbers of clients get the benefit of that.
How many shares in various manufacturers do you own? The reason that the changeover is going slowly is that people don't want to junk nearly new IPV4-only equipment and pay for IPV6-compatable replacements. Right now my ADSL ISP sells IPV6-caoable router/modems. However, I have an almost-10-year-old Thomson SpeedTouch 546 that's still going strong. I want to run it into ground. I'm not an Apple-fanboi who lines up outside the store every year or two for the latest, newest, shiney toy.
So apart from the modem/router, what equipment do you think needs to be replaced when you turn ON IPv6? The answer is NONE. Turning on IPv6 doesn't mean you have to stop using the IPv4 equipment that you have. I've had IPv6 turned on for 15 years now. The house has a mixture of dual stack equipment and IPv4 only equipment. When I have a choice when buying new equipment I've got stuff that supports both IPv6 and IPv4 vs IPv4 only. All the equipment would support IPv6 but manufactures in certain market segments have been slow to provide IPv6 capable equipment. So, no your argument is not supported by facts.
Basically you are spreading lies.
Note: there were IPv6 capable ADSL modems 10+ years ago. You could have bought one so you would have been ready when your ISP finally came into the 21st century.
Back in the 1990's I was asked if.COM and.NET should continue to accept underscore in domain registrations. This was after I added "check-names" to BIND to prevent address and MX records with non-LDH names being accidentally added to zones in contravention of RFC 952 and RFC 1123 (still the current host requirement specification). I pointed out that if underscore was permitted that people would be continually having to explain why address lookups for names like "a.label_with_underscore.com" would not work reliably. The requirements for registration were tightened to only allow LDH.
Enforcing LDH for host names allows us to use prefix labels with underscores without running the risk of colliding with valid host names. It allows software to pick out host names from free form textual contexts. When you mail client automatically creates a link that is what it is doing.
Netflix need to fix their provisioning system. Their use of underscore in a hostname is wrong.
EV's still needs servicing. Breaks pads still need replacing. Shock absorbers still need replacing. Battery packs need replacing. Wiper blades need replacing. Lights need replacing. Lots of things still need replacing because they wear out. Then there are the parts that need lubrication. If you don't lubricate them they wear out faster. They just don't have a ICE that needs servicing.
All things you purchase should continue to run well after warranty expires. They should work perfectly during the warranty period.
Computers should work for at least 10 years with the occasional battery change. This includes mobile phones.
I've still got a 32G 3GS iPhone that works fine except Apple cut it off from getting new apps by not supporting the hardware in newer iOS releases while also not having the SDK for iOS 6.1 with the latest Xcode which only supports iOS back to 8.1.
Apple should support iOS 6.1 in the current version of Xcode because they choose to not support iOS 7 on the 3GS. You either allow the latest iOS to be install on the phone or support the break point for 10 years after the last device is shipped.
They still ask you for your social media accounts with a visa waiver. It was still optional a couple of months ago when I last needs to apply for a visa wavier.
Actually they are heated. They may or may not be heated to the temperature of the passenger cabin but they are heated. What they are heated to depends on the cargo being sent. If there are live animals they will be heated to approximately same temperature as the passenger cabin, if not they it may be set to ~5C. If they weren't heated all the cargo would freeze as the outside temperature is around -55C.
IPv6 has already gained critical mass. The CDNs are all turning on IPv6. The wireless ISPs are delivering the Internet over IPv6 today translating connections to IPv4 to talk to legacy servers. Sensible fixed line ISPs are delivering IPv6 today as it cuts down the CGN costs. The biggest players on the Internet are using IPv6 only internally translating connections to IPv4 to talk to legacy servers. IPv6 is not going away. It will just grow and grow.
When a home becomes IPv6 enabled (basically replace the CPE with one that supports both IPv4 and IPv6) most of the traffic switches to IPv6.
Which is a argument for getting rid of tipping altogether. Here in Australia we don't tip taxi drivers. That doesn't stop the driver helping with the bags etc. at the end of the trip.
The only reason people can "turn it off and everything runs just fine" is that you have been paying extra to your ISP to pay for the CGN boxes to keep IPv4 limping along well past the time when everyone should have been off it.
Sane ISP's know that they don't want to run CGN boxes. They are expensive and increase they amount of logging that needs to be kept for law enforcement purposes. They also break functionality on which some of the customers depend.
Sane ISP's enable IPv6 as it takes load off the CGN boxes. A typical household with a IPv6 enabled sees around 60% of the traffic happening over IPv6 with the percentage increasing everyday as CDN's turn on IPv6 support.
Slashdot Mirror
Actually the firmware doesn't need to upgradable, you just need to be able to set and save the current date occasionally to non volatile memory. The device could do this itself periodically after synchronising itself. Yes, there is a small risk of spoofed GPS signals causing an anomalous date to be saved but even there the risk can be minimised. Time more that x seconds since last recording, more that y seconds of continuously synchronised signals. For mobile GPS devices more that z km's of travel as well while switched on.
A running system shouldn't fail across a GPS epoch event. Given this is not the first epoch event all of the equipment should have been able to handle this. This can be simulated in QA testing prior to releasing the firmware image.
Well our servers use DANE and TLSA records so they don't fallback if the site has published the record.
MTA-STS depends on DNSSEC working while, paradoxically, claiming it is needed to avoid DNSSEC. Go analyse the protocol.
The majority of the worlds authoritative server to recursive server DNS lookups are DNSSEC validated today though the result of that validation may be "insecure". MTA's that support DANE also validate DNS responses. There was never a need for MTA-STS. Just deploy DANE. It isn't subject to the attacks MTA-STS is.
And which calculations are those? Actual examples of where it is *needed* for real problems not theoretical examples.
For timers you calculate a timer assuming a negative leap second at the end of each month in a interval so you don't overshoot, fire the timer then reset it to fire again with the leap second adjusted time as the base. Repeat if necessary (requires intervals over ~200000 years initially).
You read them by saying each value and using the word colon. fd93:7065:ab8e:: is eff dee nine three colon seven zero six five colon ...
FD00::/8 is the equivalent of RFC 1918. You pick 40 random bits (toss a coin 40 times, tails=0, heads=1) and append them to FD to give you a /48 prefix which is your site prefix. (e.g fd93:7065:ab8e::/48). You then have ~65000 /64 subnets to use.
That said your ISP will delegate you a prefix using prefix delegation. Typically it will be a /56 which will give you 256 /64 sized subnets which your routers will automatically assign to links as needed. The ISP is allocated IPv6 address space from the RIRs with the assumption that they will hand out /48's to customers. If the /56 is too small complain to your ISP as they have more space to give you. If your ISP only gives you a /64 find another ISP as they are not doing the correct thing.
See RFC 6698, The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA
This is a solved problem. You just need to use the solution.
It is and the ACCC fined large telcos and made them pay back the differences between the plan the customer was on and the plan that was achievable on the link. Customers that were affected could also cancel their contracts with no penalty for early termination.
The ACCC also drew up new advertising guidelines which require ISP's to advertise the rate achievable in peak times.
Going forward, if after connection, it is found that the rate you signed up for is not achievable on the link you can downgrade the contracted rate to what is achievable or pull out of the contract.
https://www.accc.gov.au/public...
https://www.accc.gov.au/consum...
They announce the battery program within days of it being reported that older iPhones were running slower in benchmarks on the iOS versions that have the code that restricts the clock frequency.
Yes, it was a coincidence. You are seeing conspiracies where there are none.
No. You have to prove it was a foreseeable outcome.
Shooting a gun into the air isnâ(TM)t likely to kill someone but it is a foreseeable outcome and has happened. Thatâ(TM)s why rifle ranges have banks and restricted areas down range to stop people being killed by stray bullets.
There are places on the planet where you freeze at night sub zero C and overheat during the day. They are usually called deserts.
Colonel Harland David Sanders has the honour title of Kentucky Colonel. https://en.wikipedia.org/wiki/...
Car companies sell cars with lots of parts that wear out. You generally pay for new ones when the car is serviced.
Which is a real pain to re-bootstrap after a house fire.
RFC's can document a idea. There doesn't need to be a implementation before a RFC is published.
To get to standard status there needs to be two interoperating implementations.
I've had RFC's published that documented ideas which I needed others to realise after the RFC was published.
I've also had RFC's published that were based on years of deployment of the concept covered by the RFC.
Both ways happen.
Actually DNSSEC validation is common. Somewhere between 40% and 60% of lookups
world wide are validated as the biggest resolvers farm in the world do DNSSEC validation
and everyone using them has the answers validated. What isn't wide spread is domains
that are signed so despite the answers being sent to the validator they come out marked
as 'insecure', rather than 'secure' or in the case they are forged 'bogus'.
Every time a ISP turns on validation on their recursive servers large numbers of clients get
the benefit of that.
How many shares in various manufacturers do you own? The reason that the changeover is going slowly is that people don't want to junk nearly new IPV4-only equipment and pay for IPV6-compatable replacements. Right now my ADSL ISP sells IPV6-caoable router/modems. However, I have an almost-10-year-old Thomson SpeedTouch 546 that's still going strong. I want to run it into ground. I'm not an Apple-fanboi who lines up outside the store every year or two for the latest, newest, shiney toy.
So apart from the modem/router, what equipment do you think needs to be replaced when you turn ON IPv6? The answer is NONE. Turning on IPv6 doesn't mean you have to stop using the IPv4 equipment that you have. I've had IPv6 turned on for 15 years now. The house has a mixture of dual stack equipment and IPv4 only equipment. When I have a choice when buying new equipment I've got stuff that supports both IPv6 and IPv4 vs IPv4 only. All the equipment would support IPv6 but manufactures in certain market segments have been slow to provide IPv6 capable equipment. So, no your argument is not supported by facts.
Basically you are spreading lies.
Note: there were IPv6 capable ADSL modems 10+ years ago. You could have bought one so you would have been ready when your ISP finally came into the 21st century.
Back in the 1990's I was asked if .COM and .NET should continue to accept underscore in domain registrations. This was after I added "check-names" to BIND to prevent address and MX records with non-LDH names being accidentally added to zones in contravention of RFC 952 and RFC 1123 (still the current host requirement specification). I pointed out that if underscore was permitted that people would be continually having to explain why address lookups for names like "a.label_with_underscore.com" would not work reliably. The requirements for registration were tightened to only allow LDH.
Enforcing LDH for host names allows us to use prefix labels with underscores without running the risk of colliding with valid host names. It allows software to pick out host names from free form textual contexts. When you mail client automatically creates a link that is what it is doing.
Netflix need to fix their provisioning system. Their use of underscore in a hostname is wrong.
As a Australian I am legally watching GoT on FOXTEL from Optus which does a simultaneous broadcast with the US broadcast.
EV's still needs servicing. Breaks pads still need replacing. Shock absorbers still need replacing. Battery packs need replacing. Wiper blades need replacing. Lights need replacing. Lots of things still need replacing because they wear out. Then there are the parts that need lubrication. If you don't lubricate them they wear out faster. They just don't have a ICE that needs servicing.
All things you purchase should continue to run well after warranty expires. They should work perfectly during the warranty period.
Computers should work for at least 10 years with the occasional battery change. This includes mobile phones.
I've still got a 32G 3GS iPhone that works fine except Apple cut it off from getting new apps by not supporting the hardware in newer iOS releases while also not having the SDK for iOS 6.1 with the latest Xcode which only supports iOS back to 8.1.
Apple should support iOS 6.1 in the current version of Xcode because they choose to not support iOS 7 on the 3GS. You either allow the latest iOS to be install on the phone or support the break point for 10 years after the last device is shipped.
They still ask you for your social media accounts with a visa waiver. It was still optional a couple of months ago when I last needs to apply for a visa wavier.
Actually they are heated. They may or may not be heated to the temperature of the passenger cabin but they are heated. What they are heated to depends on the cargo being sent. If there are live animals they will be heated to approximately same temperature as the passenger cabin, if not they it may be set to ~5C. If they weren't heated all the cargo would freeze as the outside temperature is around -55C.
IPv6 has already gained critical mass. The CDNs are all turning on IPv6. The wireless ISPs are delivering the Internet over IPv6 today translating connections to IPv4 to talk to legacy servers. Sensible fixed line ISPs are delivering IPv6 today as it cuts down the CGN costs. The biggest players on the Internet are using IPv6 only internally translating connections to IPv4 to talk to legacy servers. IPv6 is not going away. It will just grow and grow.
When a home becomes IPv6 enabled (basically replace the CPE with one that supports both IPv4 and IPv6) most of the traffic switches to IPv6.
Which is a argument for getting rid of tipping altogether. Here in Australia we don't tip taxi drivers. That doesn't stop the driver helping with the bags etc. at the end of the trip.
The only reason people can "turn it off and everything runs just fine" is that you have been paying extra to your ISP to pay for the CGN boxes to keep IPv4 limping along well past the time when everyone should have been off it.
Sane ISP's know that they don't want to run CGN boxes. They are expensive and increase they amount of logging that needs to be kept for law enforcement purposes. They also break functionality on which some of the customers depend.
Sane ISP's enable IPv6 as it takes load off the CGN boxes. A typical household with a IPv6 enabled sees around 60% of the traffic happening over IPv6 with
the percentage increasing everyday as CDN's turn on IPv6 support.
XP supported it out of the box. You had to enable it but the code was installed on the box when it was delivered.
I've been writing and shipping applications that support IPv6 for nearly 20 years now. I've been using IPv6 from home for 15 years now.
Work has been operating servers reachable by the public over IPv6 for longer still.