MARK COTE
Plumbers in Amesbury, MA
License number
Massachusetts 21580
Issued Date
Sep 20, 1988
Expiration Date
May 1, 2018
Type
Journeyman Plumber
Address
Address
Amesbury, MA 01913
Personal information
See more information about MARK COTE at radaris.comName
Address
Phone
44 Varley Rd, Marlborough, MA 01752
390 Berlin Rd, Bolton, MA 01740
37 Longfellow Way, Boylston, MA 01505
32 Walker St #1, Lowell, MA 01854
30 Longfellow Way, Boylston, MA 01505
Professional information
See more information about MARK COTE at trustoria.com
Method And Apparatus For Managing And Displaying Contact Authentication In A Peer-To-Peer Collaboration System
Method And Apparatus For Managing And Displaying Contact Authentication In A Peer-To-Peer Collaboration System
US Patent:
7624421, Nov 24, 2009
Filed:
Jul 31, 2003
Appl. No.:
10/631206
Inventors:
Raymond E. Ozzie - Manchester MA, US
George P. Moromisato - Cambridge MA, US
Nimisha Asthagiri - Pasadena CA, US
Wei Dai - St. Bellevue WA, US
Alexei Evdokimov - Swampscott MA, US
Mark Cote - Amesbury MA, US
Adam Weiss - Somerville MA, US
George P. Moromisato - Cambridge MA, US
Nimisha Asthagiri - Pasadena CA, US
Wei Dai - St. Bellevue WA, US
Alexei Evdokimov - Swampscott MA, US
Mark Cote - Amesbury MA, US
Adam Weiss - Somerville MA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
H04L 29/00, H04L 29/02, H04L 29/06, H04L 29/12
US Classification:
726 1, 726 2, 726 3, 726 4, 726 8, 726 21, 709201, 709203, 709205, 709217, 709218, 709219, 709223, 709224, 709225, 709245, 713168, 713169
Abstract:
Proper user-to-data associations are maintained in shared spaces created in a peer-to-peer collaborative system by means of a simplified and minimal user interface that permits users to easily authenticate other members of a shared space. In particular, support is provided for automatically building authenticated relationships even if users do not take the time to authenticate other users. When a user enters a shared space and views the contacts in that space, the display names of each contact are accompanied by distinctive icons that identify that authentication status of that contact. A mechanism is provided for resolving conflicts between contacts with the same display names to prevent confusion and contact “spoofing. ” Security policies can be established to provide a uniform approach to authentication. These policies can be set by a user or, alternatively, the policies can be set by an administrator.