Basic questions belong on [EMAIL PROTECTED]

The answer is that this parameter is case insensitive, so it doesn't
matter what the capitalization is. In fact, any parameter expressed with
quoted strings in a BNF is case insensitive.

-Jonathan R.

Kirchhoff Mechthild wrote:
> 
> Hello,
> I'm in doubt about the right form of the algorithm parameter in an
> WWW/Proxy-Authenticate header.
> 
> In RFC 2617 it is defined as:
> algorithm         = "algorithm" "=" ( "MD5" | "MD5-sess" |
>                                                   token )
> 
> But later in RFC 2617 there is an example:
>         File "digtest.c":
>                        #include <stdio.h>
>                        #include "digcalc.h"
>                        void main(int argc, char ** argv) {
>                              char * pszNonce =
> "dcd98b7102dd2f0e8b11d0f600bfb0c093";
>                              char * pszCNonce = "0a4f113b";
>                              char * pszUser = "Mufasa";
>                              char * pszRealm = "[EMAIL PROTECTED]";
>                              char * pszPass = "Circle Of Life";
>                              char * pszAlg = "md5";
>                              char szNonceCount[9] = "00000001";
>                              char * pszMethod = "GET";
>                              char * pszQop = "auth";
>                              char * pszURI = "/dir/index.html";
>                              HASHHEX HA1;
>                              HASHHEX HA2 = "";
>                              HASHHEX Response;
>                              DigestCalcHA1(pszAlg, pszUser, pszRealm,
> pszPass, pszNonce,
>                        pszCNonce, HA1);
>                              DigestCalcResponse(HA1, pszNonce,
> szNonceCount, pszCNonce, pszQop,
>                               pszMethod, pszURI, HA2, Response);
>                              printf("Response = %s\n", Response);
>                        };
> 
> In the call flows (draft-ietf-call-flows-02.txt) I found:
> 
>         SIP/2.0 407 Proxy Authorization Required
>         Via: SIP/2.0/UDP here.com:5060
>         From: BigGuy <sip:[EMAIL PROTECTED]>
>         To: LittleGuy <sip:[EMAIL PROTECTED]>
>         Call-ID: [EMAIL PROTECTED]
>         CSeq: 1 INVITE
>         Proxy-Authenticate: Digest realm="MCI WorldCom SIP",
>         domain="wcom.com", nonce="wf84f1ceczx41ae6cbe5aea9c8e88d359",
>         opaque="", stale=FALSE, algorithm=MD5
>         Content-Length: 0
> 
> What should a SIP server do if it receives algorithm=md5 in a
> Proxy/-Authorization header?
> Reject the authentication header or accept it and take the response as
> if calculated using the  MD5 algorithm?
> 
> Thanks for your answers.
> 
>         Mit freundlichem Gruss / With kind regards
> 
>         Mechthild Kirchhoff
> 
>         SIEMENS
>         ICN WN CC NA D15
>         Schertlinstrasse 8
>         D-81359 Muenchen
>         Germany
> 
>         Tel. : +49-89-722-49533
>         Email: [EMAIL PROTECTED]
> 
> _______________________________________________
> sip-aaa mailing list
> [EMAIL PROTECTED]
> http://mailman.dynamicsoft.com/mailman/listinfo/sip-aaa

-- 
Jonathan D. Rosenberg, Ph.D.            72 Eagle Rock Avenue
Chief Scientist                         First Floor
dynamicsoft                             East Hanover, NJ 07936
[EMAIL PROTECTED]                 FAX: (973) 952-5050
http://www.jdrosen.net                  PH:  (973) 952-5000
http://www.dynamicsoft.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to