Re: [Sip] Update to RFC3329, aka Security Agreement
Shida Schubert <shida@ntt-at.com> Tue, 21 March 2006 00:55 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLV9j-00071t-VK; Mon, 20 Mar 2006 19:55:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FLV9i-0006zZ-4a for sip@ietf.org; Mon, 20 Mar 2006 19:55:26 -0500
Received: from [67.18.219.130] (helo=dns.aliantmedia.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FLV9f-0005I7-N2 for sip@ietf.org; Mon, 20 Mar 2006 19:55:26 -0500
Received: from dhcp-wireless-134-205.ietf65.org ([130.129.134.205]) by dns.aliantmedia.net with esmtpa (Exim 4.52) id 1FLV9Y-0005Op-4X; Mon, 20 Mar 2006 18:55:19 -0600
Message-ID: <441F4EF1.6070304@ntt-at.com>
Date: Mon, 20 Mar 2006 16:55:13 -0800
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Aki Niemi <aki.niemi@nokia.com>
Subject: Re: [Sip] Update to RFC3329, aka Security Agreement
References: <441F4836.5050107@nokia.com>
In-Reply-To: <441F4836.5050107@nokia.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - dns.aliantmedia.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - ntt-at.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: sip@ietf.org
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
Hi Aki; I just want to thank you for coming up with this draft. I heard some complaints resulting from the current RFC due to the lack of clarity and hopefully this is going to solve some of the reoccurring issues due to the lack of clarity. Regards Shida Aki Niemi wrote: > 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 > > > > _______________________________________________ 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
- [Sip] Update to RFC3329, aka Security Agreement Aki Niemi
- Re: [Sip] Update to RFC3329, aka Security Agreeme… Shida Schubert
- Re: [Sip] Update to RFC3329, aka Security Agreeme… Cullen Jennings
- RE: [Sip] Update to RFC3329, aka Security Agreeme… Sharon Laivand
- RE: [Sip] Update to RFC3329, aka Security Agreeme… Aki Niemi
- Re: [Sip] Update to RFC3329, aka Security Agreeme… Paul Kyzivat