
From moloud@blueslice.com  Tue Jun  1 10:57:34 2010
Return-Path: <moloud@blueslice.com>
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 068783A683F for <sip@core3.amsl.com>; Tue,  1 Jun 2010 10:57:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
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 2Mms5glWpLz4 for <sip@core3.amsl.com>; Tue,  1 Jun 2010 10:57:30 -0700 (PDT)
Received: from cx295.800onemail.com (cx295.800onemail.com [209.171.54.144]) by core3.amsl.com (Postfix) with ESMTP id 7BEC63A699C for <sip@ietf.org>; Tue,  1 Jun 2010 10:57:29 -0700 (PDT)
Received: from EX13-N04.exchserver.com ([10.7.5.66]) by cx295.800onemail.com (8.13.8/8.13.8) with ESMTP id o51HvGcG025417 for <sip@ietf.org>; Tue, 1 Jun 2010 13:57:16 -0400
Received: from EX41.exchserver.com ([169.254.1.30]) by EX13-N04.exchserver.com ([10.7.40.180]) with mapi; Tue, 1 Jun 2010 13:57:16 -0400
From: Moloud Mousavi <moloud@blueslice.com>
To: "sip@ietf.org" <sip@ietf.org>
Date: Tue, 1 Jun 2010 13:57:14 -0400
Thread-Topic: Authenication Parameters in response to 401 unauthorized
Thread-Index: AcsBs94LQFLuKZGUTBKHwk73JdQLNw==
Message-ID: <345A3596DB43194797927F6ADFBFFFEF02619B642F@EX41.exchserver.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-crx-noroute: SMTP reroute not required
Content-Type: multipart/alternative; boundary="_000_345A3596DB43194797927F6ADFBFFFEF02619B642FEX41exchserve_"
MIME-Version: 1.0
X-CRXEFW-Info: Please contact Ceryx for more information
X-CRXEFW-Virus: Clean
X-CRXEFW-From: moloud@blueslice.com
X-Mailman-Approved-At: Tue, 01 Jun 2010 12:06:15 -0700
Subject: [Sip] Authenication Parameters in response to 401 unauthorized
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: Tue, 01 Jun 2010 17:57:34 -0000

--_000_345A3596DB43194797927F6ADFBFFFEF02619B642FEX41exchserve_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I was wondering how dresponse in authenticated register is calculated.
The other question: what is the method used for CSeq in case of authenticat=
ed register message?

Thanks,
Moloud

________________________________
NOTICE: This e-mail contains information that may be confidential and propr=
ietary. 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 b=
e 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 k=
ind cooperation.
AVIS : Ce courriel contient des renseignements qui peuvent etre confidentie=
ls ou de propriete industrielle. Si vous n'etes pas le veritable destinatai=
re, la diffusion ou l'usage de ce courriel, des renseignements qu'il contie=
nt 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 ve=
uillez le supprimer sans le lire, l'imprimer, le sauvegarder ou le diffuser=
. Merci de votre aimable collaboration.

--_000_345A3596DB43194797927F6ADFBFFFEF02619B642FEX41exchserve_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I was wondering how dresponse in authenticated regis=
ter is calculated.
<o:p></o:p></p>
<p class=3D"MsoNormal">The other question: what is the method used for CSeq=
 in case of authenticated register message?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal">Moloud<o:p></o:p></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">NOTICE: This e-mail contains=
 information that may be confidential and proprietary. If you are not the i=
ntended recipient, any disclosure or other use of this e-mail or the inform=
ation contained herein or attached hereto
 may be unlawful and is strictly prohibited. If you have received this e-ma=
il in error, please notify the sender immediately and delete this e-mail wi=
thout reading, printing, copying or forwarding it to anyone. Thank you for =
your kind cooperation.<br>
AVIS : Ce courriel contient des renseignements qui peuvent etre confidentie=
ls ou de propriete industrielle. Si vous n'etes pas le veritable destinatai=
re, la diffusion ou l'usage de ce courriel, des renseignements qu'il contie=
nt ou des documents qui lui sont
 joints pourrait etre illegal. Il est donc strictement interdit de les diff=
user 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.<br>
</font>
</body>
</html>

--_000_345A3596DB43194797927F6ADFBFFFEF02619B642FEX41exchserve_--

From moloud@blueslice.com  Tue Jun  1 11:35:44 2010
Return-Path: <moloud@blueslice.com>
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 914903A6A03 for <sip@core3.amsl.com>; Tue,  1 Jun 2010 11:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.948
X-Spam-Level: 
X-Spam-Status: No, score=-1.948 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 vbufbDqao1ic for <sip@core3.amsl.com>; Tue,  1 Jun 2010 11:35:43 -0700 (PDT)
Received: from cx295.800onemail.com (cx295.800onemail.com [209.171.54.144]) by core3.amsl.com (Postfix) with ESMTP id 6977A3A68B3 for <sip@ietf.org>; Tue,  1 Jun 2010 11:35:43 -0700 (PDT)
Received: from EX13-N02.exchserver.com ([10.7.5.66]) by cx295.800onemail.com (8.13.8/8.13.8) with ESMTP id o51IZExf009268 for <sip@ietf.org>; Tue, 1 Jun 2010 14:35:14 -0400
Received: from EX41.exchserver.com ([169.254.1.30]) by EX13-N02.exchserver.com ([10.7.40.170]) with mapi; Tue, 1 Jun 2010 14:35:14 -0400
From: Moloud Mousavi <moloud@blueslice.com>
To: "sip@ietf.org" <sip@ietf.org>
Date: Tue, 1 Jun 2010 14:35:14 -0400
Thread-Topic: Authenication Parameters in response to 401 unauthorized
Thread-Index: AcsBs94LQFLuKZGUTBKHwk73JdQLNwABUaiw
Message-ID: <345A3596DB43194797927F6ADFBFFFEF02619B6495@EX41.exchserver.com>
Accept-Language: en-US, en-CA
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-CA
x-crx-noroute: SMTP reroute not required
Content-Type: multipart/alternative; boundary="_000_345A3596DB43194797927F6ADFBFFFEF02619B6495EX41exchserve_"
MIME-Version: 1.0
X-CRXEFW-Info: Please contact Ceryx for more information
X-CRXEFW-Virus: Clean
X-CRXEFW-From: moloud@blueslice.com
X-Mailman-Approved-At: Tue, 01 Jun 2010 12:06:52 -0700
Subject: [Sip] Authenication Parameters in response to 401 unauthorized
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: Tue, 01 Jun 2010 18:35:44 -0000

--_000_345A3596DB43194797927F6ADFBFFFEF02619B6495EX41exchserve_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I was wondering how dresponse in authenticated register is calculated.
The other question: what is the method used for CSeq in case of authenticat=
ed register message?

Thanks,
Moloud

________________________________
NOTICE: This e-mail contains information that may be confidential and propr=
ietary. 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 b=
e 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 k=
ind cooperation.
AVIS : Ce courriel contient des renseignements qui peuvent etre confidentie=
ls ou de propriete industrielle. Si vous n'etes pas le veritable destinatai=
re, la diffusion ou l'usage de ce courriel, des renseignements qu'il contie=
nt 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 ve=
uillez le supprimer sans le lire, l'imprimer, le sauvegarder ou le diffuser=
. Merci de votre aimable collaboration.

--_000_345A3596DB43194797927F6ADFBFFFEF02619B6495EX41exchserve_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I was wondering how dresponse in authenticated regis=
ter is calculated.
<o:p></o:p></p>
<p class=3D"MsoNormal">The other question: what is the method used for CSeq=
 in case of authenticated register message?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal">Moloud<o:p></o:p></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">NOTICE: This e-mail contains=
 information that may be confidential and proprietary. If you are not the i=
ntended recipient, any disclosure or other use of this e-mail or the inform=
ation contained herein or attached hereto
 may be unlawful and is strictly prohibited. If you have received this e-ma=
il in error, please notify the sender immediately and delete this e-mail wi=
thout reading, printing, copying or forwarding it to anyone. Thank you for =
your kind cooperation.<br>
AVIS : Ce courriel contient des renseignements qui peuvent etre confidentie=
ls ou de propriete industrielle. Si vous n'etes pas le veritable destinatai=
re, la diffusion ou l'usage de ce courriel, des renseignements qu'il contie=
nt ou des documents qui lui sont
 joints pourrait etre illegal. Il est donc strictement interdit de les diff=
user 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.<br>
</font>
</body>
</html>

--_000_345A3596DB43194797927F6ADFBFFFEF02619B6495EX41exchserve_--

From dworley@avaya.com  Tue Jun  1 12:43:02 2010
Return-Path: <dworley@avaya.com>
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 2FC123A6A80 for <sip@core3.amsl.com>; Tue,  1 Jun 2010 12:43:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.577
X-Spam-Level: 
X-Spam-Status: No, score=-1.577 tagged_above=-999 required=5 tests=[AWL=1.022,  BAYES_00=-2.599]
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 JxDCnPRU95Rq for <sip@core3.amsl.com>; Tue,  1 Jun 2010 12:43:01 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id C82093A6986 for <sip@ietf.org>; Tue,  1 Jun 2010 12:43:00 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,342,1272859200"; d="scan'208";a="191421282"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 01 Jun 2010 15:42:46 -0400
X-IronPort-AV: E=Sophos;i="4.53,342,1272859200"; d="scan'208";a="479976314"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 01 Jun 2010 15:42:45 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.188]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Tue, 1 Jun 2010 15:42:45 -0400
From: "WORLEY, Dale R (Dale)" <dworley@avaya.com>
To: Moloud Mousavi <moloud@blueslice.com>, "sip@ietf.org" <sip@ietf.org>
Date: Tue, 1 Jun 2010 15:40:52 -0400
Thread-Topic: Authenication Parameters in response to 401 unauthorized
Thread-Index: AcsBs94LQFLuKZGUTBKHwk73JdQLNwABUaiwAAJM0E4=
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FD736152@DC-US1MBEX4.global.avaya.com>
References: <345A3596DB43194797927F6ADFBFFFEF02619B6495@EX41.exchserver.com>
In-Reply-To: <345A3596DB43194797927F6ADFBFFFEF02619B6495@EX41.exchserver.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Sip] Authenication Parameters in response to 401 unauthorized
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: Tue, 01 Jun 2010 19:43:02 -0000

________________________________________
From: sip-bounces@ietf.org [sip-bounces@ietf.org] On Behalf Of Moloud Mousa=
vi [moloud@blueslice.com]

I was wondering how dresponse in authenticated register is calculated.
The other question: what is the method used for CSeq in case of authenticat=
ed register message?
________________________________

The details are in RFC 2617 (HTTP authentication: Basic and Digest Access A=
uthentication) as modified by RFC 3261 section 22.4.

Dale

From moloud@blueslice.com  Wed Jun  2 10:58:58 2010
Return-Path: <moloud@blueslice.com>
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 0CD2128B797 for <sip@core3.amsl.com>; Wed,  2 Jun 2010 10:58:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.865
X-Spam-Level: 
X-Spam-Status: No, score=-1.865 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6]
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 wxCry4H580zl for <sip@core3.amsl.com>; Wed,  2 Jun 2010 10:58:53 -0700 (PDT)
Received: from cx295.800onemail.com (cx295.800onemail.com [209.171.54.144]) by core3.amsl.com (Postfix) with ESMTP id 6A4353A67D9 for <sip@ietf.org>; Wed,  2 Jun 2010 10:58:52 -0700 (PDT)
Received: from EX13-N05.exchserver.com ([10.7.5.66]) by cx295.800onemail.com (8.13.8/8.13.8) with ESMTP id o52Hwcao028885 for <sip@ietf.org>; Wed, 2 Jun 2010 13:58:38 -0400
Received: from EX41.exchserver.com ([169.254.1.30]) by EX13-N05.exchserver.com ([10.7.40.160]) with mapi; Wed, 2 Jun 2010 13:58:38 -0400
From: Moloud Mousavi <moloud@blueslice.com>
To: "sip@ietf.org" <sip@ietf.org>
Date: Wed, 2 Jun 2010 13:58:33 -0400
Thread-Topic: cnonce in RFC 3261
Thread-Index: AcsCfTdejNE4ep2+RPur7b3qGobDAw==
Message-ID: <345A3596DB43194797927F6ADFBFFFEF02619B68F9@EX41.exchserver.com>
Accept-Language: en-US, en-CA
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-CA
x-crx-noroute: SMTP reroute not required
Content-Type: multipart/alternative; boundary="_000_345A3596DB43194797927F6ADFBFFFEF02619B68F9EX41exchserve_"
MIME-Version: 1.0
X-CRXEFW-Info: Please contact Ceryx for more information
X-CRXEFW-Virus: Clean
X-CRXEFW-From: moloud@blueslice.com
X-Mailman-Approved-At: Thu, 03 Jun 2010 08:02:34 -0700
Subject: [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: Wed, 02 Jun 2010 17:58:58 -0000

--_000_345A3596DB43194797927F6ADFBFFFEF02619B68F9EX41exchserve_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

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

cnonce =3D "cnonce" EQUAL cnonce-value
cnonce-value =3D nonce-value


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

nonce=3D"dcd98b7102dd2f0e8b11d0f600bfb0c093",
uri=3D"sip:bob@biloxi.com",
qop=3Dauth,
nc=3D00000001,
cnonce=3D"0a4f113b",
response=3D"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 thi=
s one: nonce-count =3D "nc" EQUAL nc-value


THANKs a lot.

Moloud




________________________________
NOTICE: This e-mail contains information that may be confidential and propr=
ietary. 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 b=
e 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 k=
ind cooperation.
AVIS : Ce courriel contient des renseignements qui peuvent etre confidentie=
ls ou de propriete industrielle. Si vous n'etes pas le veritable destinatai=
re, la diffusion ou l'usage de ce courriel, des renseignements qu'il contie=
nt 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 ve=
uillez le supprimer sans le lire, l'imprimer, le sauvegarder ou le diffuser=
. Merci de votre aimable collaboration.

--_000_345A3596DB43194797927F6ADFBFFFEF02619B68F9EX41exchserve_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The Cnonce definition in RFC 3261 is confusing. This=
 is what I found:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-fa=
mily:Courier">cnonce =3D &quot;cnonce&quot; EQUAL cnonce-value<o:p></o:p></=
span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-fa=
mily:Courier">cnonce-value =3D nonce-value<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:Courier"><o:p>&nbsp;</o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:Courier"><o:p>&nbsp;</o:p=
></span></p>
<p class=3D"MsoNormal">while a bit up an example shows the value of cnonce =
different than nonce:<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-family:Courier"><o:p>&nbsp;</o:p=
></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-fa=
mily:Courier">nonce=3D&quot;dcd98b7102dd2f0e8b11d0f600bfb0c093&quot;,<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-fa=
mily:Courier">uri=3D&quot;sip:bob@biloxi.com&quot;,<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-fa=
mily:Courier">qop=3Dauth,<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-fa=
mily:Courier">nc=3D00000001,<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-fa=
mily:Courier">cnonce=3D&quot;0a4f113b&quot;,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:Courier">response=3D&quot=
;6629fae49393a05397450978507c4ef1&quot;,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:Courier"><o:p>&nbsp;</o:p=
></span></p>
<p class=3D"MsoNormal">I need to calculate the challenge response. I don&#8=
217;t know where to get this cnonce from?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">One more thing: Why are there many names for the sam=
e parameter??? Like this one:<span style=3D"font-family:Courier"> nonce-cou=
nt =3D &quot;nc&quot; EQUAL nc-value<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:Courier"><o:p>&nbsp;</o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:Courier"><o:p>&nbsp;</o:p=
></span></p>
<p class=3D"MsoNormal">THANKs a lot.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Moloud<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">NOTICE: This e-mail contains=
 information that may be confidential and proprietary. If you are not the i=
ntended recipient, any disclosure or other use of this e-mail or the inform=
ation contained herein or attached hereto
 may be unlawful and is strictly prohibited. If you have received this e-ma=
il in error, please notify the sender immediately and delete this e-mail wi=
thout reading, printing, copying or forwarding it to anyone. Thank you for =
your kind cooperation.<br>
AVIS : Ce courriel contient des renseignements qui peuvent etre confidentie=
ls ou de propriete industrielle. Si vous n'etes pas le veritable destinatai=
re, la diffusion ou l'usage de ce courriel, des renseignements qu'il contie=
nt ou des documents qui lui sont
 joints pourrait etre illegal. Il est donc strictement interdit de les diff=
user 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.<br>
</font>
</body>
</html>

--_000_345A3596DB43194797927F6ADFBFFFEF02619B68F9EX41exchserve_--

From ibc@aliax.net  Thu Jun  3 08:29:13 2010
Return-Path: <ibc@aliax.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 4FBC23A69DD for <sip@core3.amsl.com>; Thu,  3 Jun 2010 08:29:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.337
X-Spam-Level: *
X-Spam-Status: No, score=1.337 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3]
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 IYQ4hJ5S43AS for <sip@core3.amsl.com>; Thu,  3 Jun 2010 08:29:08 -0700 (PDT)
Received: from mail-pz0-f195.google.com (mail-pz0-f195.google.com [209.85.222.195]) by core3.amsl.com (Postfix) with ESMTP id C05D828C0EF for <sip@ietf.org>; Thu,  3 Jun 2010 08:29:08 -0700 (PDT)
Received: by pzk33 with SMTP id 33so218827pzk.17 for <sip@ietf.org>; Thu, 03 Jun 2010 08:28:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.247.20 with SMTP id u20mr8351656rvh.122.1275578932474;  Thu, 03 Jun 2010 08:28:52 -0700 (PDT)
Received: by 10.140.252.19 with HTTP; Thu, 3 Jun 2010 08:28:52 -0700 (PDT)
In-Reply-To: <345A3596DB43194797927F6ADFBFFFEF02619B68F9@EX41.exchserver.com>
References: <345A3596DB43194797927F6ADFBFFFEF02619B68F9@EX41.exchserver.com>
Date: Thu, 3 Jun 2010 17:28:52 +0200
Message-ID: <AANLkTinfWCU9mpXsZi7g0DCyO3KEQL44vzXGTdtzKpNR@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Moloud Mousavi <moloud@blueslice.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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 15:29:13 -0000

2010/6/2 Moloud Mousavi <moloud@blueslice.com>:
> Hi,
> The Cnonce definition in RFC 3261 is confusing. This is what I found:
>
> cnonce =3D "cnonce" EQUAL cnonce-value
> cnonce-value =3D nonce-value
>
> while a bit up an example shows the value of cnonce different than nonce:
>
> nonce=3D"dcd98b7102dd2f0e8b11d0f600bfb0c093",
> uri=3D"sip:bob@biloxi.com",
> qop=3Dauth,
> nc=3D00000001,
> cnonce=3D"0a4f113b",
> response=3D"6629fae49393a05397450978507c4ef1",

Why do "you" think that cnonce and nonce are different? just because
the different lenght in *your* example? the BNF for nonce-value field
doesn't mandate a strict length for nonce-value, in fact it's just a
queted string:

  nonce-value         =3D  quoted-string



> I need to calculate the challenge response. I don=E2=80=99t know where to=
 get this
> cnonce from?

Read RFC 2617.




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

Please, read RFC 2617 and 3261 before asking such questions.


--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From ibc@aliax.net  Thu Jun  3 09:52:54 2010
Return-Path: <ibc@aliax.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 B6DBA3A69E4 for <sip@core3.amsl.com>; Thu,  3 Jun 2010 09:52:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.13
X-Spam-Level: *
X-Spam-Status: No, score=1.13 tagged_above=-999 required=5 tests=[AWL=0.207, BAYES_50=0.001, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3]
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 Pi5pvoSGQxGr for <sip@core3.amsl.com>; Thu,  3 Jun 2010 09:52:51 -0700 (PDT)
Received: from mail-pz0-f195.google.com (mail-pz0-f195.google.com [209.85.222.195]) by core3.amsl.com (Postfix) with ESMTP id E80C43A63C9 for <sip@ietf.org>; Thu,  3 Jun 2010 09:52:50 -0700 (PDT)
Received: by pzk33 with SMTP id 33so335255pzk.17 for <sip@ietf.org>; Thu, 03 Jun 2010 09:52:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.143.26.28 with SMTP id d28mr6839478wfj.103.1275583954215; Thu,  03 Jun 2010 09:52:34 -0700 (PDT)
Received: by 10.140.252.19 with HTTP; Thu, 3 Jun 2010 09:52:33 -0700 (PDT)
In-Reply-To: <345A3596DB43194797927F6ADFBFFFEF02619B6D46@EX41.exchserver.com>
References: <345A3596DB43194797927F6ADFBFFFEF02619B68F9@EX41.exchserver.com> <AANLkTinfWCU9mpXsZi7g0DCyO3KEQL44vzXGTdtzKpNR@mail.gmail.com> <345A3596DB43194797927F6ADFBFFFEF02619B6D46@EX41.exchserver.com>
Date: Thu, 3 Jun 2010 18:52:33 +0200
Message-ID: <AANLkTim9Ed6GTfUwZ2631AhE84E0Sq_0C2ltOF-7XLfJ@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Moloud Mousavi <moloud@blueslice.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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 16:52:54 -0000

2010/6/3 Moloud Mousavi <moloud@blueslice.com>:
> Hello I=C3=B1aki,
>
> This is the explanation of cnonce in RFC 2617:
>
> cnonce
> This MUST be specified if a qop directive is sent (see above), and
> MUST NOT be specified if the server did not send a qop directive in
> the WWW-Authenticate header field. The cnonce-value is an opaque
> quoted string value provided by the client and used by both client
> and server to avoid chosen plaintext attacks, to provide mutual
> authentication, and to provide some message integrity protection.
> See the descriptions below of the calculation of the responsedigest
> and request-digest values.
>
>
> It seems that cnonce existence is optional, but then If you want to calcu=
late the responseDigest, you have to consider that again.
>
> Assuming both the same: in fact I tried putting the same value for nonce =
and cnonce, and it didn't work.

Where did you read that nonce and cnonce have to be equal?


> If my question is trivial, why do "YOU" bother to put time to answer me b=
ack, leave it to someone else.

First of all, this maillist is not the place to ask trivial or non
trivial questions about already approved specifications for SIP
protocol, use sip-implementors instead.
Second: you should be not so rude with people trying to help you.

--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From ibc@aliax.net  Thu Jun  3 10:06:36 2010
Return-Path: <ibc@aliax.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 6409028C0F6 for <sip@core3.amsl.com>; Thu,  3 Jun 2010 10:06:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.182
X-Spam-Level: 
X-Spam-Status: No, score=0.182 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3]
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 mRDrGC96f6uy for <sip@core3.amsl.com>; Thu,  3 Jun 2010 10:06:32 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id 3FB9728C0EF for <sip@ietf.org>; Thu,  3 Jun 2010 10:06:32 -0700 (PDT)
Received: by pvf33 with SMTP id 33so168192pvf.31 for <sip@ietf.org>; Thu, 03 Jun 2010 10:06:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.142.196.21 with SMTP id t21mr7012243wff.237.1275584776082;  Thu, 03 Jun 2010 10:06:16 -0700 (PDT)
Received: by 10.140.252.19 with HTTP; Thu, 3 Jun 2010 10:06:15 -0700 (PDT)
In-Reply-To: <345A3596DB43194797927F6ADFBFFFEF02619B6D65@EX41.exchserver.com>
References: <345A3596DB43194797927F6ADFBFFFEF02619B68F9@EX41.exchserver.com> <AANLkTinfWCU9mpXsZi7g0DCyO3KEQL44vzXGTdtzKpNR@mail.gmail.com> <345A3596DB43194797927F6ADFBFFFEF02619B6D46@EX41.exchserver.com> <AANLkTim9Ed6GTfUwZ2631AhE84E0Sq_0C2ltOF-7XLfJ@mail.gmail.com> <345A3596DB43194797927F6ADFBFFFEF02619B6D65@EX41.exchserver.com>
Date: Thu, 3 Jun 2010 19:06:15 +0200
Message-ID: <AANLkTil23KC9iANZNWNhJFm6t5YcWssYoeG5L86zflPR@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Moloud Mousavi <moloud@blueslice.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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 17:06:36 -0000

2010/6/3 Moloud Mousavi <moloud@blueslice.com>:
> Regarding your question, please read RFC 3261.

nonce and cnonce must not be equal. Period.


> By the way, as I understood, there is a moderator here. Probably he/she k=
nows what should be forwarded or not.

There is no moderator inspecting each mail before allowing it to be
published or not. For questions/doubts related to SIP protocol the
sip-implementors maillist is the appropriate place.

--=20
I=C3=B1aki Baz Castillo
<ibc@aliax.net>

From tom111.taylor@bell.net  Thu Jun  3 11:57:55 2010
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.

From jmpolk@cisco.com  Thu Jun  3 16:18:33 2010
Return-Path: <jmpolk@cisco.com>
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 545293A682A for <sip@core3.amsl.com>; Thu,  3 Jun 2010 16:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
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 jAqNk0lYxgwY for <sip@core3.amsl.com>; Thu,  3 Jun 2010 16:18:32 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 6E7983A67ED for <sip@ietf.org>; Thu,  3 Jun 2010 16:18:32 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAH/VB0xAaMHG/2dsb2JhbACeMnGlBJoPhRYEg0g
X-IronPort-AV: E=Sophos;i="4.53,357,1272844800"; d="scan'208";a="139130303"
Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-4.cisco.com with ESMTP; 03 Jun 2010 23:18:18 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8713.cisco.com [10.99.80.20]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o53NIFWn004207; Thu, 3 Jun 2010 23:18:16 GMT
Message-Id: <201006032318.o53NIFWn004207@syd-core-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 03 Jun 2010 18:18:14 -0500
To: =?iso-8859-1?Q?I=C3=B1aki?= Baz Castillo <ibc@aliax.net>, Moloud Mousavi <moloud@blueslice.com>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <AANLkTim9Ed6GTfUwZ2631AhE84E0Sq_0C2ltOF-7XLfJ@mail.gmail.c om>
References: <345A3596DB43194797927F6ADFBFFFEF02619B68F9@EX41.exchserver.com> <AANLkTinfWCU9mpXsZi7g0DCyO3KEQL44vzXGTdtzKpNR@mail.gmail.com> <345A3596DB43194797927F6ADFBFFFEF02619B6D46@EX41.exchserver.com> <AANLkTim9Ed6GTfUwZ2631AhE84E0Sq_0C2ltOF-7XLfJ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
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 23:18:33 -0000

I=C3=B1aki Baz Castillo

FWIW -- the only one being rude in this discussion is you.

You could have used a better tone when telling=20
Mousavi that the sip-implementers list is where=20
these questions should be asked.

James

At 11:52 AM 6/3/2010, I=C3=B1aki Baz Castillo wrote:
>2010/6/3 Moloud Mousavi=20
><moloud@blueslice.com>: > Hello I=C3=B1aki, > > This=20
>is the explanation of cnonce in RFC 2617: > >=20
>cnonce > This MUST be specified if a qop=20
>directive is sent (see above), and > MUST NOT be=20
>specified if the server did not send a qop=20
>directive in > the WWW-Authenticate header=20
>field. The cnonce-value is an opaque > quoted=20
>string value provided by the client and used by=20
>both client > and server to avoid chosen=20
>plaintext attacks, to provide mutual >=20
>authentication, and to provide some message=20
>integrity protection. > See the descriptions=20
>below of the calculation of the responsedigest >=20
>and request-digest values. > > > It seems that=20
>cnonce existence is optional, but then If you=20
>want to calculate the responseDigest, you have=20
>to consider that again. > > Assuming both the=20
>same: in fact I tried putting the same value for=20
>nonce and cnonce, and it didn't work. Where did=20
>you read that nonce and cnonce have to be=20
>equal? > If my question is trivial, why do "YOU"=20
>bother to put time to answer me back, leave it=20
>to someone else. First of all, this maillist is=20
>not the place to ask trivial or non trivial=20
>questions about already approved specifications=20
>for SIP protocol, use sip-implementors instead.=20
>Second: you should be not so rude with people=20
>trying to help you. -- I=C3=B1aki Baz Castillo=20
><ibc@aliax.net>=20
>_______________________________________________=20
>Sip mailing=20
>list  https://www.ietf.org/mailman/listinfo/sip=20
>This list is essentially closed and only used=20
>for finishing old business. Use=20
>sip-implementors@cs.columbia.edu for questions=20
>on how to develop a SIP implementation. Use=20
>dispatch@ietf.org for new developments on the=20
>application of sip. Use sipcore@ietf.org for=20
>issues related to maintenance of the core SIP specifications.


From keith.drage@alcatel-lucent.com  Fri Jun  4 06:50:51 2010
Return-Path: <keith.drage@alcatel-lucent.com>
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 A78BD3A677E for <sip@core3.amsl.com>; Fri,  4 Jun 2010 06:50:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[AWL=-2.271,  BAYES_50=0.001, HELO_EQ_FR=0.35]
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 M6CGdl0zfJcY for <sip@core3.amsl.com>; Fri,  4 Jun 2010 06:50:50 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id 8C7BD3A69B6 for <sip@ietf.org>; Fri,  4 Jun 2010 06:50:50 -0700 (PDT)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o54DZOwk031964 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <sip@ietf.org>; Fri, 4 Jun 2010 15:50:18 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com ([135.120.45.64]) with mapi; Fri, 4 Jun 2010 15:49:19 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "sip@ietf.org" <sip@ietf.org>
Date: Fri, 4 Jun 2010 15:49:18 +0200
Thread-Topic: On moderation
Thread-Index: AcsD0auXEHLVgQ76Qsm+ZKwxDwhAGw==
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE213C6D0AB@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Subject: [Sip] On moderation
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: Fri, 04 Jun 2010 13:50:51 -0000

This list does have a moderator, but:

-	if you are a member of the list, then posts automatically go through unle=
ss they are too long, or hit various SPAM checks applied to all IETF lists.

-	if you are not a member of the list they automatically go into the modera=
tor queue.

In general the moderator does not pass on long messages to the list - gener=
ally this will result in some request to repost in a more concise form.

The moderator will release to the list most material with a SIP related sub=
ject matter, even if it should probably have been posted to sip-implementor=
s or some other list in the first place. If it is cross posted to multiple =
lists, then it may be blocked.

The moderator does not pass on to the list messages that cannot be read on =
the moderator interface, which is substantially text based.

We leave it to the list membership to direct posters to a more appropriate =
list. Please do remember that the initial poster who is a non-member of the=
 list may never have seen the footer that the server puts at the end of all=
 messages until they read a response to their first post.

regards

Keith
List moderator=

From root@core3.amsl.com  Thu Jun 17 12:45:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 60C723A6909; Thu, 17 Jun 2010 12:45:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100617194502.60C723A6909@core3.amsl.com>
Date: Thu, 17 Jun 2010 12:45:02 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-certs-13.txt
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, 17 Jun 2010 19:45:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Protocol Working Group of the IETF.


	Title           : Certificate Management Service for The Session Initiation Protocol (SIP)
	Author(s)       : C. Jennings, J. Fischl
	Filename        : draft-ietf-sip-certs-13.txt
	Pages           : 30
	Date            : 2010-06-17

This draft defines a Credential Service that allows Session
Initiation Protocol (SIP) User Agents (UAs) to use a SIP event
package to discover the certificates of other users.  This mechanism
allows user agents that want to contact a given Address-of-Record
(AOR) to retrieve that AOR's certificate by subscribing to the
Credential Service, which returns an authenticated response
containing that certificate.  The Credential Service also allows
users to store and retrieve their own certificates and private keys.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-certs-13.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-sip-certs-13.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-06-17123608.I-D@ietf.org>


--NextPart--

From Fred_Stacey@Mitel.com  Fri Jun 18 12:50:27 2010
Return-Path: <Fred_Stacey@Mitel.com>
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 202223A698A for <sip@core3.amsl.com>; Fri, 18 Jun 2010 12:50:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level: 
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
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 Hjk6IEZoEVm0 for <sip@core3.amsl.com>; Fri, 18 Jun 2010 12:50:26 -0700 (PDT)
Received: from smtp.mitel.com (smtp.mitel.com [216.191.234.102]) by core3.amsl.com (Postfix) with ESMTP id 382CF3A6978 for <sip@ietf.org>; Fri, 18 Jun 2010 12:50:26 -0700 (PDT)
Received: from localhost (smtp.mitel.com [127.0.0.1]) by smtp.mitel.com (Postfix) with ESMTP id 83F8D2C006 for <sip@ietf.org>; Fri, 18 Jun 2010 15:50:31 -0400 (EDT)
X-Virus-Scanned: by amavisd-new (virusonly) at mitel.com
Received: from smtp.mitel.com ([127.0.0.1]) by localhost (smtp.mitel.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qYusC6oTWrs0 for <sip@ietf.org>; Fri, 18 Jun 2010 15:50:31 -0400 (EDT)
Received: from ottlnmta.mitel.com (ottlnmta.mitel.com [10.44.16.150]) by smtp.mitel.com (Postfix) with ESMTP id 63FF82C005 for <sip@ietf.org>; Fri, 18 Jun 2010 15:50:31 -0400 (EDT)
From: Fred_Stacey@Mitel.com
To: sip@ietf.org
Message-ID: <OFDC01BF02.5B0F7C72-ON85257746.006CFE75-85257746.006CFE75@ottlnmta.mitel.com>
Date: Fri, 18 Jun 2010 15:50:30 -0400
X-MIMETrack: Serialize by Router on OTTLNMTA/Mitel(Release 6.5.6FP3|March 27, 2008) at 06/18/2010 03:50:31 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Subject: [Sip] Fred Stacey is out of the office.
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: Fri, 18 Jun 2010 19:50:27 -0000

I will be out of the office starting  06/16/2010 and will not return until
06/21/2010.



From wwwrun@rfc-editor.org  Wed Jun 23 13:11:59 2010
Return-Path: <wwwrun@rfc-editor.org>
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 271D128C0F3; Wed, 23 Jun 2010 13:11:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
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 gjImAfZIk-iT; Wed, 23 Jun 2010 13:11:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 233683A69DA; Wed, 23 Jun 2010 13:11:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7D3F7E0647; Wed, 23 Jun 2010 13:12:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100623201205.7D3F7E0647@rfc-editor.org>
Date: Wed, 23 Jun 2010 13:12:05 -0700 (PDT)
Cc: sip@ietf.org, rfc-editor@rfc-editor.org
Subject: [Sip] RFC 5922 on Domain Certificates in the Session Initiation Protocol (SIP)
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: Wed, 23 Jun 2010 20:11:59 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5922

        Title:      Domain Certificates in the Session 
                    Initiation Protocol (SIP) 
        Author:     V. Gurbani, S. Lawrence,
                    A. Jeffrey
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2010
        Mailbox:    vkg@alcatel-lucent.com, 
                    scott-ietf@skrb.org, 
                    ajeffrey@alcatel-lucent.com
        Pages:      17
        Characters: 37667
        Updates:    RFC3261

        I-D Tag:    draft-ietf-sip-domain-certs-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5922.txt

This document describes how to construct and interpret certain
information in a PKIX-compliant (Public Key Infrastructure using
X.509) certificate for use in a Session Initiation Protocol (SIP)
over Transport Layer Security (TLS) connection.  More specifically,
this document describes how to encode and extract the identity of a
SIP domain in a certificate and how to use that identity for SIP
domain authentication.  As such, this document is relevant both to
implementors of SIP and to issuers of certificates.  [STANDARDS TRACK]

This document is a product of the Session Initiation Protocol Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From wwwrun@rfc-editor.org  Wed Jun 23 13:12:30 2010
Return-Path: <wwwrun@rfc-editor.org>
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 1539728C167; Wed, 23 Jun 2010 13:12:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.967
X-Spam-Level: 
X-Spam-Status: No, score=-1.967 tagged_above=-999 required=5 tests=[AWL=0.633,  BAYES_00=-2.599, NO_RELAYS=-0.001]
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 ut+jd23ML6+b; Wed, 23 Jun 2010 13:12:29 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id A2A2A28C150; Wed, 23 Jun 2010 13:12:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 096ADE06B7; Wed, 23 Jun 2010 13:12:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100623201231.096ADE06B7@rfc-editor.org>
Date: Wed, 23 Jun 2010 13:12:31 -0700 (PDT)
Cc: sip@ietf.org, rfc-editor@rfc-editor.org
Subject: [Sip] RFC 5924 on Extended Key Usage (EKU) for Session Initiation Protocol (SIP) X.509 Certificates
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: Wed, 23 Jun 2010 20:12:30 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5924

        Title:      Extended Key Usage (EKU) for 
                    Session Initiation Protocol (SIP) X.509 Certificates 
        Author:     S. Lawrence, V. Gurbani
        Status:     Experimental
        Stream:     IETF
        Date:       June 2010
        Mailbox:    scott-ietf@skrb.org, 
                    vkg@bell-labs.com
        Pages:      8
        Characters: 16868
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sip-eku-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5924.txt

This memo documents an extended key usage (EKU) X.509 certificate
extension for restricting the applicability of a certificate to use
with a Session Initiation Protocol (SIP) service.  As such, in
addition to providing rules for SIP implementations, this memo also
provides guidance to issuers of certificates for use with SIP. 
This document defines an Experimental Protocol for the Internet
community.

This document is a product of the Session Initiation Protocol Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From root@core3.amsl.com  Wed Jun 30 14:30:20 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: sip@ietf.org
Delivered-To: sip@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 6BDFA3A6986; Wed, 30 Jun 2010 14:30:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100630213012.6BDFA3A6986@core3.amsl.com>
Date: Wed, 30 Jun 2010 14:30:03 -0700 (PDT)
Cc: sip@ietf.org
Subject: [Sip] I-D Action:draft-ietf-sip-certs-14.txt
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: Wed, 30 Jun 2010 21:30:20 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Session Initiation Protocol Working Group of the IETF.


	Title           : Certificate Management Service for The Session Initiation Protocol (SIP)
	Author(s)       : C. Jennings, J. Fischl
	Filename        : draft-ietf-sip-certs-14.txt
	Pages           : 30
	Date            : 2010-06-30

This draft defines a Credential Service that allows Session
Initiation Protocol (SIP) User Agents (UAs) to use a SIP event
package to discover the certificates of other users.  This mechanism
allows user agents that want to contact a given Address-of-Record
(AOR) to retrieve that AOR's certificate by subscribing to the
Credential Service, which returns an authenticated response
containing that certificate.  The Credential Service also allows
users to store and retrieve their own certificates and private keys.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sip-certs-14.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-sip-certs-14.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-06-30141716.I-D@ietf.org>


--NextPart--
