[Sip] Update to RFC3329, aka Security Agreement

Aki Niemi <aki.niemi@nokia.com> Tue, 21 March 2006 00:27 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLUiy-0006gM-Se; Mon, 20 Mar 2006 19:27:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLUix-0006gE-34 for sip@ietf.org; Mon, 20 Mar 2006 19:27:47 -0500
Received: from mgw-ext03.nokia.com ([131.228.20.95]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLUit-0004DK-Js for sip@ietf.org; Mon, 20 Mar 2006 19:27:47 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k2L0QJt5014275 for <sip@ietf.org>; Tue, 21 Mar 2006 02:26:20 +0200
Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 21 Mar 2006 02:26:33 +0200
Received: from [10.241.59.12] ([10.241.59.12]) by esebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Tue, 21 Mar 2006 02:26:33 +0200
Message-ID: <441F4836.5050107@nokia.com>
Date: Tue, 21 Mar 2006 02:26:30 +0200
From: Aki Niemi <aki.niemi@nokia.com>
User-Agent: Thunderbird 1.5 (X11/20051201)
MIME-Version: 1.0
To: sip@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 21 Mar 2006 00:26:33.0630 (UTC) FILETIME=[1B6C23E0:01C64C7E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Subject: [Sip] Update to RFC3329, aka Security Agreement
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

All,

During the past couple of years, there have been a few reported issues
on RFC 3329, based on implementation experience.

I've gathered the set of issues in an I-D:
http://www.ietf.org/internet-drafts/draft-niemi-rfc3329-issues-00.txt

We've already talked about rfc3329bis among the authors, and we feel
this would be appropriate in order to straighten out the issues and
improve interop. Any comments are welcome.

Cheers,
Aki

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip