Re: [Simple] draft-ietf-simple-presence-10.txt

Jonathan Rosenberg <jdrosen@dynamicsoft.com> Mon, 17 May 2004 17:06 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05621 for <simple-archive@ietf.org>; Mon, 17 May 2004 13:06:14 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPlZA-0003sv-9M for simple-archive@ietf.org; Mon, 17 May 2004 13:06:16 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPlYN-0003YE-00 for simple-archive@ietf.org; Mon, 17 May 2004 13:05:28 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BPlXl-0003CM-00; Mon, 17 May 2004 13:04:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPlKQ-0001mL-2V; Mon, 17 May 2004 12:51:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPl8y-0008IN-Vc for simple@optimus.ietf.org; Mon, 17 May 2004 12:39:13 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03810 for <simple@ietf.org>; Mon, 17 May 2004 12:39:09 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPl8x-0002CX-AY for simple@ietf.org; Mon, 17 May 2004 12:39:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPl7z-0001p7-00 for simple@ietf.org; Mon, 17 May 2004 12:38:11 -0400
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com) by ietf-mx with esmtp (Exim 4.12) id 1BPl72-00018q-00 for simple@ietf.org; Mon, 17 May 2004 12:37:12 -0400
Received: from dynamicsoft.com ([63.113.46.76]) by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id i4HGalbo003143; Mon, 17 May 2004 12:36:47 -0400 (EDT)
Message-ID: <40A8EA0C.3010105@dynamicsoft.com>
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Surya Gogineni <sugogine@cisco.com>
CC: simple@ietf.org
Subject: Re: [Simple] draft-ietf-simple-presence-10.txt
References: <40A8C731.2040103@cisco.com>
In-Reply-To: <40A8C731.2040103@cisco.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: simple-admin@ietf.org
Errors-To: simple-admin@ietf.org
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/mail-archive/working-groups/simple/>
Date: Mon, 17 May 2004 12:36:28 -0400
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit

Yes, it is still valid. This is a source of confusion for many people, 
as its an oddity in the IETF process (IMHO).

Once an Internet Draft is submitted to the IESG for consideration for 
publication as an RFC, the document will remain in the IETF archives 
until it is published as an RFC, even if the expiration date passes. In 
the case of draft-ietf-simple-presence, the document was approved for 
publication as RFC quite a long time ago (over a year!!). However, it is 
stuck in the RFC editor's queue due to document dependencies. In 
particular, IETF has a rule that says that document X cannot be 
published if it normatively references document Y and document Y hasn't 
been published yet. SIMPLE is dependent on PIDF, which is in turn 
dependent on draft-ietf-smime-rfc2633bis, which should be done shortly. 
Once the smime draft is done, the whole dependency chain is resolved, 
and the core simple specs (draft-ietf-simple-presence, the watcherinfo 
drafts) along with PIDF and the IMPP documents, can all get published.

Hope that helps.

Thanks,
Jonathan R.

Surya Gogineni wrote:

> Is draft-ietf-simple-presence-10.txt still valid? The doc indicates it 
> expires in July 2003. Is there any follow up doc for this?
> 

-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com

_______________________________________________
Simple mailing list
Simple@ietf.org
https://www1.ietf.org/mailman/listinfo/simple