Yes, the example seems to be buggy when you look at it closely. I guess it is unintentional. The intent is to do a base64 encoding which should result in a string of length a multiple of 4 characters. I'm copying the author Aki Niemi in case he has any comments.
Thanks Subhash Nayak Sonus Networks, Inc. http://www.sonusnet.com <http://www.sonusnet.com/> _____ From: Harish Kr Gupta [mailto:[EMAIL PROTECTED] Sent: Friday, July 08, 2005 1:19 PM To: Nayak, Subhash Cc: [email protected] Subject: RE: [Sip-implementors] HELP ME: questions regarding AKA implementation Subhash, I have one more problem. If you see RFC 3310, it mentions that nonce sent by server is base64 encoded. RFC 3310 gives some example of nonce value, which does not seems to be base64 encoded correctly. I am taking this conclusion because base64 encoded values must be multiple of 4 characters whereas examples in RFC3310 are not. Can you please let me know why it is so. Thanks Harish "Nayak, Subhash" <[EMAIL PROTECTED]> 06/20/2005 04:01 PM To Harish Kr Gupta/[EMAIL PROTECTED], <[email protected]> cc Subject RE: [Sip-implementors] HELP ME: questions regarding AKA implementation Hi Harish, Take a look at the 35 series (Security Algorithms) of 3GPP Technical Specifications for details on these algorithms. Subhash Nayak Sonus Networks Inc. http://www.sonusnet.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Harish Kr Gupta Sent: Monday, June 20, 2005 2:14 PM To: [email protected] Subject: [Sip-implementors] HELP ME: questions regarding AKA implementation Hi All, I am implementing AKA (Authentication and Key agreement for SIP client. I was going through 3GPP TS 33.102 V4.4.0. It is mentioned in this document that SIP client calculates MAC and RES using f1 and f2. where f1 and f2 are message authentication functions for calculating MAC and RES. I tried to find what these functions are. So far I did not find any information on it. Please help me and let me know what are these functions. Thanks in advance. Harish *********************** FSS-Private *********************** "DISCLAIMER: This message is proprietary to Flextronics Software Systems Limited (FSS) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSS accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors *********************** FSS-Private *********************** "DISCLAIMER: This message is proprietary to Flextronics Software Systems Limited (FSS) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSS accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
