Your basic problem is that you need to read the ABNF specification (RFC 5234)
to understand the syntax descriptions. That example you quoted:

nonce-count = "nc" EQUAL nc-value

species the syntax of a field which has the arbitrary name "nonce-count",
just for purposes of syntax description. The actual syntax is to the right
of the equals sign, and says that the field has the form:

nc= some value whose syntax is spelled oput by the production nc-value elsewhere in the ABNF.

The example you quote has this field:

nc=00000001

Moloud Mousavi wrote:
Hi,

The Cnonce definition in RFC 3261 is confusing. This is what I found:

cnonce = "cnonce" EQUAL cnonce-value cnonce-value = nonce-value


while a bit up an example shows the value of cnonce different than nonce:

nonce="dcd98b7102dd2f0e8b11d0f600bfb0c093", uri="sip:[email protected]", qop=auth, nc=00000001, cnonce="0a4f113b", response="6629fae49393a05397450978507c4ef1",

I need to calculate the challenge response. I don't know where to get this
cnonce from?

One more thing: Why are there many names for the same parameter??? Like this
one: nonce-count = "nc" EQUAL nc-value


THANKs a lot.

Moloud




________________________________ NOTICE: This e-mail contains information
that may be confidential and proprietary. If you are not the intended
recipient, any disclosure or other use of this e-mail or the information
contained herein or attached hereto may be unlawful and is strictly
prohibited. If you have received this e-mail in error, please notify the
sender immediately and delete this e-mail without reading, printing, copying
or forwarding it to anyone. Thank you for your kind cooperation. AVIS : Ce
courriel contient des renseignements qui peuvent etre confidentiels ou de
propriete industrielle. Si vous n'etes pas le veritable destinataire, la
diffusion ou l'usage de ce courriel, des renseignements qu'il contient ou des
documents qui lui sont joints pourrait etre illegal. Il est donc strictement
interdit de les diffuser ou de les utiliser. Si vous avez recu ce courriel
par erreur, veuillez en aviser l'expediteur immediatement et veuillez le
supprimer sans le lire, l'imprimer, le sauvegarder ou le diffuser. Merci de
votre aimable collaboration.



------------------------------------------------------------------------

_______________________________________________ Sip mailing list
https://www.ietf.org/mailman/listinfo/sip This list is essentially closed and
only used for finishing old business. Use [email protected]
for questions on how to develop a SIP implementation. Use [email protected]
for new developments on the application of sip. Use [email protected] for
issues related to maintenance of the core SIP specifications.
_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is essentially closed and only used for finishing old business.
Use [email protected] for questions on how to develop a SIP 
implementation.
Use [email protected] for new developments on the application of sip.
Use [email protected] for issues related to maintenance of the core SIP 
specifications.

Reply via email to