OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

security-services message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: Question re: core-12 Authenication Code


I am happy with either <AuthenticationMethod> or <AuthNMethod>. I have not
fully assimilated the new naming rules and as usual am being sloppy about
details.

Hal

> -----Original Message-----
> From: Hallam-Baker, Phillip [mailto:pbaker@verisign.com]
> Sent: Monday, August 20, 2001 3:55 PM
> To: 'Hal Lockhart'; Hallam-Baker, Phillip;
> 'security-services@lists.oasis-open.org'
> Subject: RE: Question re: core-12 Authenication Code
> 
> 
> By that I infer <AuthenticationMethod> and not as literal 
> <AuthNMethod> in
> accordance with the naming rules?
> 
> One of the problems with the whiteboard is that an 
> abreviation may not be
> intended quite as such in the final product :-)
> 
> Having saved billions of bytes with my creative spelling of 
> the Referer
> field of HTTP I am now trying to spend them all with verbose XML tags.
> 
> 		Phill
> 
> Phillip Hallam-Baker FBCS C.Eng.
> Principal Scientist
> VeriSign Inc.
> pbaker@verisign.com
> 781 245 6996 x227
> 
> 
> > -----Original Message-----
> > From: Hal Lockhart [mailto:hal.lockhart@entegrity.com]
> > Sent: Monday, August 20, 2001 3:37 PM
> > To: 'Hallam-Baker, Phillip'; 
> 'security-services@lists.oasis-open.org'
> > Subject: RE: Question re: core-12 Authenication Code
> > 
> > 
> > Actually, I checked and the whiteboard transcription says 
> > "AuthN type". I
> > consider AuthN Method to be preferable.
> > 
> > Hal
> > 
> > > -----Original Message-----
> > > From: Hallam-Baker, Phillip [mailto:pbaker@verisign.com]
> > > Sent: Wednesday, August 15, 2001 6:48 PM
> > > To: 'Hal Lockhart'; 'security-services@lists.oasis-open.org'
> > > Subject: RE: Question re: core-12 Authenication Code
> > > 
> > > 
> > > I think it came off the whiteboard.
> > > 
> > > I would very much like to rename it, AuthenticationMethod 
> > > sounds good to me.
> > > I think we should also rename the protocol element in 
> > > <Authenticator> to be
> > > the same.
> > > 
> > > [We can also change authenticator but that is another story 
> > and first
> > > someone needs to come up with a better name, HolderOfKey 
> > being worse]
> > > 
> > > Phillip Hallam-Baker FBCS C.Eng.
> > > Principal Scientist
> > > VeriSign Inc.
> > > pbaker@verisign.com
> > > 781 245 6996 x227
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: Hal Lockhart [mailto:hal.lockhart@entegrity.com]
> > > > Sent: Wednesday, August 15, 2001 5:29 PM
> > > > To: 'security-services@lists.oasis-open.org'
> > > > Subject: Question re: core-12 Authenication Code
> > > > 
> > > > 
> > > > I was wondering why the term "Authentication Code" was 
> > > chosen for the
> > > > consensus schema. I thought we had been using "Authentication 
> > > > Method" a term
> > > > that seems more intuitive to me.
> > > > 
> > > > Hal
> > > > 
> > > > ----------------------------------------------------------------
> > > > To subscribe or unsubscribe from this elist use the subscription
> > > > manager: <http://lists.oasis-open.org/ob/adm.pl>
> > > > 
> > > 
> > > 
> > > 
> > 
> 
> 
> 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC