Namespaces

We are seeing interesting changes in the namespaces that people use. No, I do not mean XML namespaces (that really would be a bit geeky to post even on my blog). I mean more generally.

On the internet we are familiar with the idea of domain names. They are used for web pages and email and so on.

Domain names have a number of challenges. The fact there are many top level domains and not just one that applies for a specific application. The original concept was to segregate the different uses, e.g. .uk for UK domains, .org for non profit organisations, etc. But the whole think has got complicated. Some countries exploit (why not?) their country code, e.g. .tv for TV shows. Some people get domains in the wrong top levels (e.g. non ISPs using .net domains). And then I even see normal companies with domains within .uk.net which is so wrong I don't know where to start.

What is also interesting is the way domain names have changed from a simple entry in a register and the associated NS record in the DNS system, to a valuable resource which comes to the attention of governments. The UK has recent legislation governing the way domains are managed so that they can, if they wish, step in to manage people like Nominet (who manage most of the .uk space).

But it is moving too quickly for governments, and in fact, government meddling just confuse things more. If the .uk name space gets tinkered with by government it will simply means people will move to other name spaces.

We are seeing them emerge already. People use twitter tags, and facebook names, and so on.

I even saw, today, a TV advert for a car. A Toyota Highlander. The obvious web site name to quote would be something like www.toyota.com/highlander. In fact, it is the right web site for details of that car (I just guessed it). On the TV advert they have youtube.com/highlander. It has a slightly amusing extended advert as a video.

So this shows that the advertisers decided the youtube namespace was the one to use for their advert not the domain name name space. Yes, you have to use domains to get to youtube.com (for now). I have also seen adverts saying to search for X or google for X rather than quoting a web site. The number of people I see typing a URL in to a google search box is scary (I bet google have stats for that).

The government has no control over all of the namespaces. They may legislate to get involved in Nominet, for example, but so what. They cannot control all of the namespaces that will be used, and become important resources for UK industry. So one wonders why they even try...

But then the government want to snoop on our internet traffic anyway and you wonder why they are bothering with that anyway.

How to get ripped off in Vegas

Always check the price...

I managed to lose the eyecup for my camera - it is the bit that fits on the viewfinder. Its a bit of plastic and slightly cushioned surround.

I did not actually look at the price, but as I needed it I paid it anyway even when they rang up $75 (about £50).

I just checked, and as I suspected, in the UK you are looking under £10 for this bit of plastic even with a Canon logo on it!

Grrr.

XML for dummies

Is there an "XML for dummies"? I must get a copy for our favourite telco.

Once again, it seems, they have a simple text substitution in an XML message they pass on where they add our company name and forget to escape the &

How does a big company make such basic errors?

Fun in Vegas

Well, it was a good start when Sandra put her first bet of $5 on 13 and won... But by 2am, after countless comp drinks, the four of us walk away from the table some $200 up between us. I think that was a good evening entertainment and good value. Viva Las Vegas!

I never had a big brother and don't want one now

As the eldest I did not have a big brother. I don't want to get one now. However the new government seem to be trying to resurrect expensive, intrusive and pointless snooping legislation in the Interception Modernisation Programme (IMP).

1. It is very costly to do what they are proposing - and will mean huge investment in equipment to snoop on normal people and to store the data. This has to be paid somehow, either by tax payers or by ISPs and hence ISP customers.

2. It is risky storing all of this data as we have seen both government and private companies finding it increasingly difficult to make data storage secure. To get it right just adds to the costs.

3. It is not just for terrorism and serious crimes - this data can be used for anything, and could be used to seriously invade peoples private lives.

4. It is totally pointless as anyone that actually wants to do bad things will be able to easily avoid the snooping. Encryption is standard on lots of systems from email to chat and criminals already know how to use overseas servers and secure encrypted access.

5. Every spam will be logged, but the content will not be so you won't be able to tell it is spam, so the data will not actually be useful in any court case as it could be spam. It will be difficult if not impossible to sort the meaningful data from the noise. And then there is the very real possibility of people generating huge amounts of fake data for the fun of it and to break the system.

As an ISP we expect to fight this. If the wording is as bad as the data retention directive it will be a doddle to legally bypass it even if that means running the break out to the internet in another country.

Really unimpressed with Bellagio now

So the wifi is broken because they appear to be allowing people to send IPv6 RAs on the LAN causing my machine to pick up an IPv6 (2002: prefix) and then having no routing.

What is really annoying is I have complained 3 days in a row now and not one reply!

How can they just ignore complaints from paying guests?

Crap service.

IPv6 vs NAT

There are many ways to make a networking protocol, and one of the key aspects of the protocol definition is the addressing. There are many ways to address the information (typically packets).

1. You can create a system where the data has a locally relevant address which defines some channel of communications. At the next hop there is a pre-set path for that channel to go to the next hop after that via some local channel. The target address in the packet changes as it goes hop to hop to get to the destination. The channel creates an end to end path. You can have many different paths across a network.

These paths could be pre-set or could be created by some other protocol. Examples of this are protocols like ATM and even TDM (phone calls). It is a separate issue of whether the data flows continuously at a pre-defined rate (like a phone call) or has some dynamic bandwidth (as ATM can do). What I am talking of here is the addressing system being used.

2. You can create a system that has some hop by hop local addresses in the original packet. This allows each hop to work out where next to send the packet. Typically the packet changes as it goes to create a reverse path allowing a reply. This has the advantage that you do not have to establish end to end pathways in advance and can send packets ad-hoc. However, it does mean that the addressing is variable length and you have to work out the path needed to make the packet address header which depends where you start from. E.g. using some other protocol to find the path needed from where you are to where you want to get to.

3. You can create a system where packets are addressed based on a globally unique ID that identifies the target. The address stays the same at each hop. Each hop uses this target address to send the packet logically closer to the designation. Usually in this case the source globally unique address is included to allow replies. This has several advantages. Protocols to look up addresses can return the same final unique destination address regardless of where the packet starts. It is a good system and how IP works.


Another key aspect of a protocol definition is the way it works with layers. You have distinct layers that are responsible for different levels of communications. E.g. a low level that gets packets to their destination. Layers above provide session management and reliable communications with retransmission and acknowledgments. Layers above provide more complex protocols like web pages and email and so on. The principle is that you have well defined interfaces between layers and a general hiding of information between layers to some extent.


Internet Protocol uses the third type of addressing I listed. It means that every IP packet contains a globally unique final endpoint destination and source address. Internet Protocol also provides means for communications at higher levels to work (e.g. ICMP, UDP, TCP).

Some people have said that IPv6 is "throwing the baby out with the bathwater". IPv6 is indeed replacing the IPv4 layer. Everyone that looks at IPv6 can find one or other thing that IPv6 could also have done. There are many small niggles and problems that could have been fixed or improved in making IPv6 which is a shame. However it does address the problem with IPv4 running out of space. It is a big change, but gives us a chance to get rid of NAT now.

The alternatives being suggested, which are basically lots more NAT are a problem for a lot of reasons.

NAT breaks the basic principle of globally unique target addresses. It changes to a sort of ad-hoc connection based addressing one side. It also interferes with higher protocols like UDP and TCP. UDP cannot work as designed via NAT! NAT has to understand UDP and TCP and ICMP and make changes to that layer. In some cases NAT has to make changes at the layers above that even. NAT has to understand the way IP is used at various levels to work at all.

NAT breaks almost all innovation in protocol development. Nobody could make a new IP protocol (along side ICMP, UDP, TCP) as it simply would not work through any existing NAT router. You would have to change the software (maybe even the hardware too) for all existing NAT routers in the world to add a new protocol. You can't even rely on UDP and TCP working as they should and make new application level protocols without assuming NAT is in the way, which restricts what you can do or means changes NAT routers. People complaining about IPv6 seem to understand that changing every router is a bad thing, but that is what NAT is forcing when ever anyone makes a new protocol.

Also, the idea you can just NAT more and more for end user connections misses the point. For a start it creates resource issues for ISPs (processing power, memory for session tracking, and limited numbers of sessions due to port number limits). It creates huge traceability issues (history of every session needed). So it will not scale indefinitely.

But also this is not the only issue. What about when hosting companies have no IPv4's left and you want to host a new web server? You can't just NAT that side. You have to create all sorts of bodges. There are ways of doing it, but they create yet new issues.

NAT is an evil bodge that should never have taken off. Are we stuck with it? Probably for IPv4, but we can make a fresh start with IPv6. NAT and RFC1918 can continue to stretch IPv4 so that devices on local networks (printers, etc) can carry on working without change. But new applications can start to rely on proper IP functionality using IPv6.

Now, what will happen is that IPv4 and IPv6 run in parallel. Machines will dual stack with no problem. IPv6 can "just work" as IP was always intended. IPv4 can be carrier grade NAT'd and bodged and get increasingly broken. But we then have the best of both worlds.

We should be concentrating on making that happen. Making it seamless for end users when they next replace their router (typically small routers go bang after a year or two anyway). We need ISPs to handle the IPv6 side too.

We need any moves to create any sort of IPv6 NAT to be stamped on as soon as they are suggested.

Look forward, not back!