Re: [Sip] cnonce in RFC 3261

Tom Taylor <tom111.taylor@bell.net> Thu, 03 June 2010 18:57 UTC

Return-Path: <tom111.taylor@bell.net>
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2FDF3A67D9 for <sip@core3.amsl.com>; Thu, 3 Jun 2010 11:57:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.443
X-Spam-Level: *
X-Spam-Status: No, score=1.443 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_50=0.001, J_CHICKENPOX_34=0.6, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mbPLrqNOZLY8 for <sip@core3.amsl.com>; Thu, 3 Jun 2010 11:57:54 -0700 (PDT)
Received: from blu0-omc4-s13.blu0.hotmail.com (blu0-omc4-s13.blu0.hotmail.com [65.55.111.152]) by core3.amsl.com (Postfix) with ESMTP id BE4233A6781 for <sip@ietf.org>; Thu, 3 Jun 2010 11:57:54 -0700 (PDT)
Received: from BLU0-SMTP85 ([65.55.111.136]) by blu0-omc4-s13.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 3 Jun 2010 11:57:41 -0700
X-Originating-IP: [70.26.21.75]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP851B5BC350E5A1DC109FD5D8D10@phx.gbl>
Received: from [192.168.2.11] ([70.26.21.75]) by BLU0-SMTP85.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 3 Jun 2010 11:57:41 -0700
Date: Thu, 03 Jun 2010 14:57:38 -0400
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Moloud Mousavi <moloud@blueslice.com>
References: <345A3596DB43194797927F6ADFBFFFEF02619B68F9@EX41.exchserver.com>
In-Reply-To: <345A3596DB43194797927F6ADFBFFFEF02619B68F9@EX41.exchserver.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 03 Jun 2010 18:57:41.0448 (UTC) FILETIME=[A4A01C80:01CB034E]
Cc: "sip@ietf.org" <sip@ietf.org>
Subject: Re: [Sip] cnonce in RFC 3261
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sip>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 18:57:55 -0000

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:bob@biloxi.com", 
> 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 sip-implementors@cs.columbia.edu
> for questions on how to develop a SIP implementation. Use dispatch@ietf.org
> for new developments on the application of sip. Use sipcore@ietf.org for
> issues related to maintenance of the core SIP specifications.