In Part 1 he discusses the need to create SOA-specific operations groups. He also goes into the differences between network agents and network appliances and what their functions are.
You really want to move threat-based security away from the platform so you've created a protective shield around the servers who are actually dealing with these services. For a whole host of reasons dealing with these things with network intermediaries is a much smarter thing to do than with anything that runs on the platform itself, bearing in mind that there are always a class of problems that you'll want to solve on the platform.In Part 2 he talks about how Binary XML would make the world a better place [Editor's note: Really? I'm all for it, then.], the need for transferrable policies between SOA/Web services tools and the scale problems presented by a glut of new clients ready to consume Web services.
The most interesting thing I wish the software guys would get their act together on is Binary XML. At the XML2005 conference I saw a roundtable which had Microsoft, IBM, Sun, Oracle and two other vendors talking about Binary XML and basically what they said is, "We're not going to do it." It's too hard. There's too many issues. We can't work out how to make it backwards compatible
Yet the reason why I think it would be incredibly valuable is the piece I would most like to add to our appliance is, with the processing that we currently do, I would like to be able to handle it all and ensure that what was passed back to the application was a small-piped, pre-processed sort of structure that you could open without all this SOAP and XML-parsing that you need to handle it at the moment.