Pre-Grant Publication Number: 20080120715
Collaborate on the process of community review for this application. Posting will not be forwarded to the USPTO. Flagging a post as an ACTION ITEM signals further research. Flagging SPAM and ABUSE helps to manage discussion. Placing double brackets around a reference to a claim or prior art will create a hyperlink to the original ex. [[claim 1]] and [[prior art 2]].

Please review the Community Code of Conduct prior to posting

Discussion (2)
  Facilitator's Comment     Action Item
  Show without Noise
2
Gerold Gorman (2 months ago)
From 1999 through late 2000 a company called Spinway provided millions of customers with free Internet Service using a program that placed banner ads on the users screen. This program had a proprietary client server authentication method that initiated and maintained a client session with various other functions such as logging the user into third party e-mail providers (such as Yahoo or Bluelight.com) via their apserver protocol which worked over an HTTP connection with various client server challenges, and verfifications; i.e. with respect to specialized headers or cookies being set up by the application at the client level so that third party web sites such as akamai, or yahoo, etc., would correctly interface with the client for various purposes.

Notice that the Cisco application contians the therefore overly broad "numerous other changes, substitutions, variations may be ascertained and that .... applications encompasses all such changes, substituions ... "

In other words - it looks to me like the Cisco patent simply substitutes the SIP method for Spinways proprietary password encyrption scheme. This is not to be confused with PPP or CHAP; since the the connection process happens in stages; i.e., a connection to the ISP occurs over a dial up connection; then the client software uses the HTTP connection for various purposes; such as logging into the client e-mail; presenting a "hello user" message, etc.
1
Morten Grouleff (4 months ago)
This appears similar to "RFC2617 - HTTP Authentication" as described at http://www.faqs.org/rfcs/rfc2617.html