Appeal No. 2003-1942 Page 11
Application No. 09/260,796
The first passage of Carter cited by the examiner discloses in pertinent part that
an "operating system 46 generates, maintains, and manages a set of user identifiers 48
such as login names or account numbers." Col. 8, ll. 51-52. The second passage he
cites discloses in pertinent part that "key pairs 76 are stored in key objects 74. In
alternative embodiments, the key pairs 76 are stored in key attributes 74 which are then
associated with user objects 68, with group objects 70, and/or with organizational role
objects 72." Col. 11, ll. 61-65. We find no teaching in either passage of obtaining key
pairs for a group. To the contrary, the reference obtains individual keys for users.
Specifically, a "collaborative access controller 44 obtains one public key 78 for each
collaborative group member." Col. 13, ll. 30-31.
The absence of obtaining a public key and a matched private key for a group of
more than one client negates anticipation. Therefore, we reverse the anticipation
rejection of claim 9 and of claims 11, 13 and 15-17, which depend therefrom.
The examiner does not allege, let alone show, that the addition of Feistel cures
the aforementioned deficiency of Carter. Absent a teaching or suggestion of obtaining a
public key and a matched private key for a group of clients, we are unpersuaded of a
Page: Previous 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Next
Last modified: November 3, 2007