IETF Logo Mail Archive

Re: [Sip] Are we ready to WGLC draft-ietf-sip-e2m-sec-01?

Cullen Jennings <fluffy@cisco.com> Sat, 29 October 2005 05:30 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVjIe-0007GZ-Q7; Sat, 29 Oct 2005 01:30:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVjIc-0007GO-E1 for sip@megatron.ietf.org; Sat, 29 Oct 2005 01:30:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12106 for <sip@ietf.org>; Sat, 29 Oct 2005 01:30:20 -0400 (EDT)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVjWJ-0000B9-Op for sip@ietf.org; Sat, 29 Oct 2005 01:44:49 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 28 Oct 2005 22:30:28 -0700
X-IronPort-AV: i="3.97,265,1125903600"; d="scan'208"; a="358331741:sNHT25203048"
Received: from vtg-um-e2k4.sj21ad.cisco.com (vtg-um-e2k4.cisco.com [171.70.93.57]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j9T5UQ94024972; Fri, 28 Oct 2005 22:30:26 -0700 (PDT)
Received: from 10.82.216.110 ([10.82.216.110]) by vtg-um-e2k4.sj21ad.cisco.com ([171.70.93.57]) with Microsoft Exchange Server HTTP-DAV ; Sat, 29 Oct 2005 05:30:57 +0000
User-Agent: Microsoft-Entourage/11.2.1.051004
Date: Fri, 28 Oct 2005 22:30:24 -0700
Subject: Re: [Sip] Are we ready to WGLC draft-ietf-sip-e2m-sec-01?
From: Cullen Jennings <fluffy@cisco.com>
To: Dean Willis <dean.willis@softarmor.com>, "sip@ietf.org" <sip@ietf.org>
Message-ID: <BF885700.5D2CE%fluffy@cisco.com>
Thread-Topic: [Sip] Are we ready to WGLC draft-ietf-sip-e2m-sec-01?
Thread-Index: AcXcSdx/GuElMkg9EdqLEAARJEEJ/A==
In-Reply-To: <18417572-8A9E-4DE4-AB15-52EA84C4DC21@softarmor.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: Rohan Mahy <rohan@ekabal.com>
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>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

On 10/26/05 8:45 PM, "Dean Willis" <dean.willis@softarmor.com> wrote:

> 
> At IETF 63 we said we expected to be able to WGLC the next draft
> (which has been published).
> 
> Kumiko tells me that there are currently no open issues to discuss at
> IETF 64.
> 
> The current draft passes idnits and looks superficially good to me.
> 
> 
> Are we ready to WGLC this draft?

yes

> 
> What do we think about requesting some security-area review in
> conjunction with WGLC?

definitely needed

> 
> --
> Dean
> 
> 
> 
> _______________________________________________
> 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

v2.23.0 | Report a Bug | By Email