On 19-Jan-06, at 8:32 AM, Peter Davis wrote:
Any solution should support multiple transport layers, but it is
anticipated that this working group will focus on a HTTP based
solution. In this case the user’s software is a web browser, to which
no modifications should be required,
Well, it's an HTTP client.
and the relying party would be a
website.
Well, it's an HTTP aware server, which listens for HTPP messages.
Rewritten this paragraph so that it's more formal:
Any solution should support multiple transport layers, but it is
anticipated that this working group will focus on a HTTP based
solution. In this case the user’s software is a HTTP client, to which
no modifications should be required, and the relying party would be a
HTTP server. Continuing with the theme of simplicity a HTTP server
should require minimal changes to support identity information
exchange. For example, a HTML form could receive information the same
way that a user would provide it, as if they typed it into the form
themselves.
_______________________________________________
dix mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/dix
