Re: [sipcore] Milestone to revise RFC 3265

Paul Kyzivat <pkyzivat@cisco.com> Fri, 12 June 2009 14:29 UTC

Return-Path: <pkyzivat@cisco.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 46B6B3A6814 for <sipcore@core3.amsl.com>; Fri, 12 Jun 2009 07:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level:
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 txsBhbDNzFRv for <sipcore@core3.amsl.com>; Fri, 12 Jun 2009 07:29:04 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id DB0CE3A6765 for <sipcore@ietf.org>; Fri, 12 Jun 2009 07:28:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,210,1243814400"; d="scan'208";a="47150570"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 12 Jun 2009 14:28:44 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5CESiV5014375; Fri, 12 Jun 2009 10:28:44 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n5CESihl014009; Fri, 12 Jun 2009 14:28:44 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 12 Jun 2009 10:28:44 -0400
Received: from [161.44.174.156] ([161.44.174.156]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 12 Jun 2009 10:28:43 -0400
Message-ID: <4A32661B.4090905@cisco.com>
Date: Fri, 12 Jun 2009 10:28:43 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Victor Pascual Ávila <victor.pascual.avila@gmail.com>
References: <4A3227D2.4020808@ericsson.com> <618e24240906120422u7af7f1c7p7487a2216430ba0@mail.gmail.com>
In-Reply-To: <618e24240906120422u7af7f1c7p7487a2216430ba0@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 12 Jun 2009 14:28:43.0777 (UTC) FILETIME=[16C3EF10:01C9EB6A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=428; t=1244816924; x=1245680924; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:=20Re=3A=20[sipcore]=20Milestone=20to=20revise=20R FC=203265 |Sender:=20 |To:=20=3D?UTF-8?B?VmljdG9yIFBhc2N1YWwgw4F2aWxh?=3D=0A=20<v ictor.pascual.avila@gmail.com>; bh=Hki/2avCyv5TZtVjztaOjKPSQuG2SMdO+/1DjaVumgA=; b=c0ux9yPs5pTZUzCBNW0WUCmwAQlJTdx1gKjupY7ITCnSvmAmCWYFb2Tmmw ys/w9FJIJLHvFZCP1jjkPb9ESoCRpC9G+0d755BgfMz8J7Zn3I7neSVTj2e5 yzNf3dYCbz;
Authentication-Results: rtp-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
Cc: SIPCORE <sipcore@ietf.org>
Subject: Re: [sipcore] Milestone to revise RFC 3265
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jun 2009 14:29:05 -0000

Yes

Victor Pascual Ávila wrote:
> On Fri, Jun 12, 2009 at 12:02 PM, Gonzalo
> Camarillo<Gonzalo.Camarillo@ericsson.com> wrote:
>> 1) should we add a milestone to our charter to revise RFC 3265?
> 
> Yes
> 
>> 2) if we add such a milestone, should we take the following draft as the
>> initial WG item for the milestone?
>>
>> http://tools.ietf.org/html/draft-roach-sipcore-rfc3265bis-00
> 
> Yes
> 
> Cheers,