Does the Skype/Mangosoft patent settlement about "dynamic directory service" bode ill for the emerging P2P landscape?

skype_logo.pngNow that we see some incredibly powerful peer-to-peer (P2P) technology models emerging in the telephony/communication space, will we see that innovation being challenged or delayed by patent lawsuits?

The New Hampshire Business Review reported this week that Skype has settled a patent lawsuit with Mangosoft for $2.3 million over a patent apparently related to "dynamic directory service". Now per the NHBR article, it would appear that Mangosoft is fading away as a company and indeed while the website appears on initial view to be there, the management team is simply the one CEO and the newest "news" on the web site dates from early 2007. Their news release about the settlement with eBay is very brief and refers now to "MangoSoft Intellectual Property, Inc." Phil Wolff over at Skype Journal notes that MangoSoft's SEC filing is also brief (but discloses the amount). Looking back at MangoSoft's 2007 annual report, they are themselves very clear on what they are doing:

BUSINESS STRATEGY

We no longer develop new software products or services. We continue to market, sell and support our software services. Our strategy also includes seeking strategic business partnerships and distribution channels to leverage our patented technology. All of our business operations are overseen by our sole officer and director, who utilizes third party contractors, as required, to implement the Company’s business strategy.

Though I had not heard of Mangosoft until this article (even though I was living in southern NH during their height), I will say that their technology sounds interesting and indeed in reading Mangosoft's patent 6,647,393 on "Dynamic Directory Service" (either at the US Patents and Trademark Office or over on Google Patents) their invention filed back in 1997 does appear to be essentially what we would call today a peer-to-peer distributed directory service, where "directory" is used in the truly generic form as referencing a list of objects of any form (ex. file descriptors, user info, any pieces of information). [Obvious HUGE caveat - I am NOT a patent lawyer, nor do I play one on TV or the Internet or anywhere else.] From what I know of Skype's architecture, it would seem that they do use a distributed directory service and so it is perhaps no surprise that they eventually settled.

The question is really - is this just the beginning of more lawsuits in the P2P space? MangoSoft's annual report for 2007 shows a debt of $89 million as of December 2006 and the NHBR articles notes that the trend in operating losses has continued with a $680,000 loss in 2008 year-to-date. There is obviously an incentive for them to continue on to try to recoup the ~$90 million that investors have sunk into the company. Beyond this patent, Mangosoft holds several other patents that are related to distributed architectures. It could very well be that this $2.3 million from Skype will be invested now in future lawsuits against other players in the space. Or perhaps not... perhaps it will simply be distributed to some of the existing investors as the operation fades away. I guess that will largely depend upon how much of a solid case to proceed MangoSoft's investors and sole employee believe they have.

While I am definitely sympathetic to inventors who pursued a new technology but were perhaps too far ahead of their time, I must say that I'm not personally excited to see more lawsuits hitting the industry as we see more and more companies (startups, typically) exploring new ways to build communications technologies based on P2P networks. We're in a fascinating time from a network technology point-of-view, as massively distributed networks are now possible and through systems like Skype and BitTorrent we've seen that they are very possible to create. I'd like to hope that this innovation will continue unimpeded by legal battles... although I realize that that's probably an idealistic dream. Even if MangoSoft does not pursue others, over time other larger players will challenge the startups in court should they become more of a competitive threat.

Ah, well, we shall have to see. In the meantime, I guess the good news for Skype is that with their one-time licensing of MangoSoft's patents, they will at least be protected from any further issues in court on these particular patents.


If you enjoyed this post, please consider either subscribing to the RSS feed or following me on Twitter or identi.ca.


Technorati Tags: , , , , , , ,

Skype and SIP interop - the two sides of the issue raised by Michael Robertson

skype_logo.pngShould Skype open up it's network to other users? to other networks? Should Skype stop preaching about "openness" when it's network remains closed?

In the middle of last week, there was quite a little storm raised in the VoIP corner of the blogosphere after Andy Abramson published a letter from Gizmo Project founder Michael Robertson critical of Skype's openness after Skype continued to call upon the FCC to open the wireless network to applications. (See also here and this Skype blog post (and this one) for background.) Being at ITEXPO last week, I didn't have the chance to blog about this at the length I felt it deserved until today.

First, for some context, here are some of the blog posts last week:

All of it makes for good reading. It's an important issue.

So I guess I'm somewhat of two minds on this issue.... while I agree with some of Michael Robertson's points, I guess I see the whole issue of "Skype openness" as quite orthogonal to the larger issue of open wireless spectrum. I'll write about both issues at some length below.

This is long. Don't plan on reading it on a crackberry or iPhone. Best get a cup of coffee and read it on a laptop or something like that.


WIRELESS OPENNESS

To put it another way, I completely applaud Skype's letter to the FCC and think that the battle for opening up the wireless networks is probably the preeminent "battle" we who are advocates for an open Internet have before us. The wired carriers are well on their way to being commoditized big, fat, dumb pipes. The telcos started selling "data lines" and then soon the world of IP wound up increasingly removing them from the picture as anything other than a big pipe... and that's not the world they want. They are fighting (and will continue to fight) to retain relevance (and ARPU - Average Revenue Per User) but the IP train left the station a long time ago and the telcos are scrambling to catch up and stay on board rather than just being (some of) the providers of the track.

On the wireless side, not only do the carriers own the track, but they still own the train and they are still driving that train. They control who gets on and off... how fast or slow it goes... what color the train is, etc.

I, for one, don't want that. I want them to give us a solid set of tracks to use... but I want the train to be open to all. I want the wireless carriers to be big, fat, dumb pipes. I want choice. *I* want to be in control.

The carriers naturally don't want to relinquish this control. They see how they missed it on the wired side. They want to keep the wireless walled gardens for as long as they can.

The cracks are appearing... Apple's control over the iPhone and AppStore is a phenomenal crack in the telco walls...... although it ultimately really means exchanging the walled gardens of the telcos for the bright shiny walled garden based in Cupertino, CA. I'm not sure that ultimately is the best for all of us... but it does crack the telco walls. I think Google's Android has more potential... but we'll have to see later this month when those phones first come out.

So with that view, you can expect I applaud Skype's efforts to open up the wireless networks and allow consumers to have a choice of what apps they want to run. I want the *wireless* carriers to be big, fat, dump pipes... give me an IP address on the *mobile* Internet and let me do what I want with it. Sure, the carriers can offer their own services, and maybe if I like them I'll pay for them.... but I want the option to use other products and services - without degradation or prioritization...

To put it another way, I pay the wireless telcos for *dialtone* now. Once connected, I can call anyone and use any *voice service* over the PSTN. I could use someone else's voicemail if I want (like GrandCentral), although the carrier's offering may be more convenient (and is usually free). But I can call anyone on the PSTN and use any voice service I want. The carriers just provide me dialtone.

I want "IP dialtone". I want a Big, Fat, Dumb Pipe.

So... go, Skype, go!


SKYPE OPENNESS

Yet having said all this, I agree with Michael Robertson that Skype's got its own issues with openness.

I don't like walled gardens. Period. End-of-story.

I don't like telco walled gardens. I don't like Apple's walled garden. I don't like Facebook's walled garden. I didn't like the walled gardens of CompuServe, AOL, Prodigy, Genie, etc. and I rejoiced over time when the open standards of IP tore down those walls and brought about the Internet (with all of its warts) that we have today. [Tangent: I do worry, actually, that we are retreating a bit back into the walled garden world with things like Facebook and Myspace... but that's another topic I've blogged about.] I can somewhat see some value in walled gardens during the early stages of a product or technology as it reduces the set of parameters/variables and allows the service to be stablized/fixed/improved. But at some point the walls need to be reduced/eliminated. As a security guy, I don't like monocultures... I don't like homogenous systems (where one virus or issue could wipe out the whole system)... I like diversity... heterogenous systems. I don't like single-points-of-failure. I don't like single companies (or small sets) in control. I don't like walled gardens.

I don't like Skype's walled garden.

The PSTN run by the telcos of today does not provide the rich communication experience we want. We need to bypass it and leave it behind and build the massive interconnect of IP communications systems. Players like Skype have a key role in my opinion in building that new infrastructure.

But if we exchange the current PSTN walled garden controlled by the telcos for a new walled garden controlled by eBay/Skype, have we really gained anything?

Sure, it gives us a rich, multi-modal user experience. Sure, it's nice and pretty. Sure, it gives us a central user directory. Sure, it gives us wideband and encrypted audio. Sure, it's cool and all... but it's still a walled garden controlled by a single company.

Ultimately, I would like to see a new voice infrastructure that consists of many different "clouds" all interconnected and able to communicate between the clouds. Skype is one cloud. So are the SIP clouds being run now by various carriers. So are the Voice-over-IM clouds like MSN, AIM, etc. (that try vainly to compete with Skype). So are the various systems being built by vendors all over the place (including all the Microsoft OCS clouds starting to appear within enterprises).

We need to build the interconnect.

Yeah, there are a TON of issues out there that we still need to address to build that interconnect. There's a whole host of security issues... there are billing issues... there are trust issues... there are network plumbing issues. Yes, there are all those issues. But if we are to succeed in ultimately bringing about the rich communication experience we want, we need to make this happen.

And for that, Skype's walls need to come down.... at least a bit.

What we need is that Interconnect from Skype's cloud out to the emerging IP infrastructure. Think about it... Skype right now has a two-way interconnect between Skype's cloud and the cloud we know as the PSTN. It's called "SkypeOut" and "SkypeIn" (or whatever marketing names they are being called now). If you dial my SkypeIn number, you can reach me on Skype wherever I am. From my Skype client, I can call anyone on the PSTN. The two-way interconnect is already there.

So why not offer the same on the IP side?

Because I work at Voxeo and we were one of Skype's original Voice Services partners, I already know that Skype has a massive SIP infrastructure on the backend to do the the PSTN interconnect. Skype users can even dial a specific +99 number and the call goes from Skype's SIP cloud over to Voxeo's SIP cloud... and it works beautifully.

So one half of the interconnect is already there - although only for limited numbers of partners.

But where Skype already has the infrastructure, why not look at making that capability more accessible? What if someone in Skype could just type "sip:dyork@sipserviceprovider.com" and the call would go out from Skype's cloud to the service providers? This could be a new feature as part of the unlimited calling plans, etc.

How many people would use it right now? Probably only a tiny few... today. But suddenly Skype becomes an enabler of the broader post-PSTN infrastructure. New companies can get their services up and running knowing that they can promote them to Skype users and have Skype users get to those services.

Plus, Skype can now connect to all those enterprise VoIP systems being deployed everywhere... so for all those IT managers blocking Skype now but allowing SIP gateways for remote teleworkers using IP phones... Skype can suddenly be that remote softphone being used in the sense that it could connect in to other people on the corporate enterprise system - they just become "sip:" entries in my Skype directory. Skype still is my overall directory and user agent.

And what about the other way? Wouldn't it be great if someone out there on a SIP system could just call something like "sip:danyork@sip.skype.com"? The call goes from their SIP cloud across the Internet to Skype's SIP gateways and into the Skype cloud.

The SIP system user can do this right now... via my SkypeIn number... but they have to use the crappy PSTN. Why not ditch the PSTN and go directly across the IP infrastructure? Hey, maybe some user of a "HD Voice" Polycom phone could call Skype's gateways via SIP and actually wind up talking via wideband audio? (Yeah, okay, I'm probably dreaming on that since Polycom supports G.722 for wideband and Skype uses its SVOPC codec.)

I personally would probably wind up using my Skype client more for a simple reason that I have a SIP IP phone on my desk... but I'm not at my desk all that much. Wouldn't it be great if I could forward that to the SIP URI of my Skype client? (Which I can do now by forwarding to my SkypeIn # but again I'm going across the crappy PSTN.) Or better yet because I have a SIP URI for Skype it becomes one of the various phones I ring when someone calls that number (it's not, now). The number on my business card would then wind up actually going to my Skype client.

Suddenly Skype can be a player in the enterprise "unified communications" market. People don't need Skype-to-PBX gateways or sacrifice chickens and utter weird incantations to get Skype connections working with open source VoIP systems. Skype users can talk to Microsoft OCS systems... or Cisco IP PBXs... or Avaya's or Nortel's or Mitel's or ShoreTel's or... or... or...

What if... even... I could do a SIP invite to make a video call to another system? (Okay, so now maybe I'm really dreaming...)

Suddenly people (like Michael Robertson) have fewer reasons to complain. Sure, the Skype client still uses it's own proprietary protocols and codecs for communication within the Skype cloud... but you can interconnect.

Suddenly Skype is a leader in building the broader overall next-generation IP communications system. Skype's not a walled garden but rather a player in the larger picture.

Sure, there's a whack of issues involved with doing this. On the technical side, Skype has got to build SIP gateways that could deal with the abuse they would undoubtedly suffer by being exposed on the public internet (like any or all of the VoIP security tools out there). They have got to make sure such gateways don't become a way to inject spam/SPIT into the Skype network. Skype has got to figure out how to package it... potentially charge for it, etc. And they have to deal with all the glorious interoperability issues that come with SIP... as the protocol increasingly becomes an unmanageable accretion of all sorts of crap. (And I say that as an advocate for the SIP protocol.)

Ultimately, I think that's the kind of openness Skype needs.

Skype needs to provide the same two-way interconnect to the evolving IP communications infrastructure (that is almost all becoming SIP-based, for better or worse) just as Skype provides the two-way interconnect to the PSTN.

Build it and Skype would silence many of the critics of Skype's lack of openness[1] and give Skype a (much-needed, IMHO) hype-boost among the early adopter crowd who also plays with all the other emerging tools. It would be a bold move that would also help Skype gain some credibility and recognition within the larger industry. In my opinion, outside of the technical issues it would go far in so many ways in helping Skype grow - and helping the industry grow.

Will Skype get there? Good question...

[1] Not all critics would be silenced naturally because someone would still complain that they can't connect their particular client to the Skype P2P overlay network. Or that they can't connect XYZ hard phone to the Skype cloud, etc., etc. But it would silence many of the critics of Skype as a "walled garden".

Technorati Tags: , , , , , , , , , , ,

Want to understand Peer-to-Peer SIP (P2PSIP)? Listen to this podcast...

p2psip.jpgWhat if we could design SIP-based VOIP systems... but without any servers? What if we could have SIP endpoints just communicate with each other and "self-organize" into networks? What if we could essentially build an open standards-based version of Skype? How would it work? Who would use it? How would we secure it?

Those are all questions we discussed in the Squawk Box podcast / interview I did with David Bryan on July 10th. David is the co-chair of the IETF's P2PSIP Working Group and also the CEO of SIPeerior Technologies. It was a great interview where we covered all these questions and much, much more.

P2PSIP, to me, represents one of the most exciting new directions for SIP research and is something I'm definitely following closely. I wrote about my interest in P2PSIP clouds (and connecting them to larger clouds) at some length over on Voxeo's Speaking of Standards blog... it's all about clouds of SIP communication... and how we weave them all together. It's a fascinating time.

If you'd like to understand what P2PSIP is all about, please do definitely check out the Squawk Box podcast... and then, if you are so inclined, head over to P2PSIP.org to find links to learn more and download code...

Technorati Tags: , , , , , , , , , , , ,

Additional thoughts on Skype and hotel networks - there's issues on both sides...

To my immense surprise, my article yesterday about my challenges with Skype and my hotel Internet connection just hit TechMeme today, so welcome, anyone who is coming my way from there. But that also prompted me to want to offer up some additional thoughts on the subject.

First, I'm actually quite annoyed at the Best Western here in Ontario, CA, for essentially blocking Skype by virtue of their network security traffic policies. If travel shall bring me to Ontario, CA, again, you can be pretty sure that I will not be staying here. Skype has become an important communication tool for me and <cue violins>was the way I was intending to call home and stay in touch with my family</violins>. Skype has worked great at the hotel I was at earlier in the week in Phoenix and in fact at every other hotel I've been at lately. I do intend to contact Best Western to express my dissatisfaction at being unable to use the program.

Having said that, as a security professional I do understand WHY the security team at the Internet provider to this Best Western hotel has the policies in place that they do. As Phil Wolff commented, Skype's launch "can look like the beginning of port scanning or a bot-gone-wild". Given that this provider is dealing with hotel rooms where random strangers are connecting who-knows-what onto the network, they have to be extremely vigilant (especially because customers like me while complain quickly if Internet access is slow/unavailable). The more I think about it, hotel networks are really an absolute nightmare from a security point-of-view. You have no way to enforce virus protection, people can put all sorts of machines in all sorts of states onto the network, systems with spyware can easily be scanning/attacking your network -it's really pretty crazy and I'm glad that I'm not involved with running such a network! (Although the security geek in me would admit that the aggregate data they must get from network traffic would probably be fascinating.) However, there is probably a compromise out there where the ISP can tune its filtering rules so that if it sees such traffic and can identify it as Skype traffic, it can not trigger the MAC lock-out.

Which brings me to the final point that there's a lesson here for anyone developing P2P apps, or I suppose any other apps that have a similar traffic profile. If the apps generates traffic that looks like a bot or port scan, odds are that it will be blocked in some places like this one (and the hotel Phil was at). It would be great if developers could take that into account and either: a) naturally put in some kind of rate throttling; or b) perhaps provide a "hotel mode" where it throttles back the number of sessions to some (perhaps user-settable but with a default) value. This of course would make it longer for things like presence information to appear, but would at least let you continue to operate the program without triggering the network security alarms. Of course, you'd have to change to that mode, which many people would forget to do and wind up being locked out, but it might be an interesting "advanced" option for those who know what to do with it.

Any other "lessons learned" you see here?

Technorati Tags: , ,

How using Skype disrupted my hotel Internet connection and locked me out

UPDATE: I have now posted some additional thoughts about this issue.


It's been a frustrating time here at the hotel in Ontario, CA, where all I've been trying to do is use the Internet connection. I'm staying at the Best Western and did so largely because they advertised free high-speed Internet (they were also cheaper than others). First annoyance was discovering that I was too far away from their APs to use wireless, but since I had an ethernet cable I just plugged into the wall jack and expected to get access. The very first time I connected, I did get an IP address and could see an entry in my routing table for the default gateway. However, I couldn't ping it.

Being rather used to network troubleshooting, I did the usual things... bringing the interface up and down, disconnecting and re-connecting the cable. I even went to the hotel lobby and got a new cable in case the issue was with my portable/retractable cable.

Nothing. No net.

In desperation I did the thing that tech support always tells you to do but I avoid... reboot. Nothing.

So finally this morning I got on the phone to the Best Western tech support and after waiting, oh, 20 minutes or so I got through to a tech and ultimately we figured out the problem:

Skype!

More specifically, all the bizillion connections that Skype was making out into the P2P cloud. The tech reset the switch and asked me to connect again and his immediate response was "Whoa! Something on your computer is generating an incredible number of sessions out to the Internet! You are tripping our filters and it is blocking out your MAC address." With him on the phone, we tried some experimentation. I shut down Skype, at which point he said I was generating much more normal traffic. As soon as I launched it again, he noticed a very large jump in the number of session connections I was establishing. He said it was something like 396 sessions he was seeing coming from my computer. He also said that I'll keep being locked out of their system if I keep Skype running.

So I shut down Skype. Which, of course, is annoying. Part of why I wanted to use the high-speed Internet is to use Skype for IM and for voice/video calls.

I find it a bit odd that Skype was generating so much extra traffic, but then again I am pretty much always connected into several persistent group chats and had maybe 8 or 10 individual chat windows still open that I'd left open from when I'd last been chatting with the person. (The Mac Skype client makes this easy to do, but I'll write about that sometime.) The persistent group chats, especially, do generate a good number of connections as they link out into the P2P cloud. Perhaps if I closed all of those windows and killed off all my individual chat windows Skype might have behaved better. (Or perhaps not, I might have had to leave the persistent chats in order for Skype to stop making those connections.) I don't want to try it out, because I do want to keep my Internet connection up right now.

In any event, should you be at a hotel and find yourself unable to connect... it might be a P2P app like Skype tripping off the hotel's filters and blocking your access. Fun, fun, fun....

  • Search:

Other Places I Write

Twitter Updates

    follow me on Twitter

    Disruptive Conversations

    Blogs.voxeo.com

    Voice of VOIPSA