From owner-ietf-schema-reg@imc.org Tue Feb 8 13:51:00 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07434 for ; Tue, 8 Feb 2000 13:50:58 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id KAA15495 for ietf-schema-reg-bks; Tue, 8 Feb 2000 10:30:54 -0800 (PST) Received: from THOR.INNOSOFT.COM (SYSTEM@THOR.INNOSOFT.COM [192.160.253.66]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA15490 for ; Tue, 8 Feb 2000 10:30:51 -0800 (PST) Received: from threadgill.austin.innosoft.com ([207.8.108.5]) by INNOSOFT.COM (PMDF V6.0-21 #30494) with ESMTP id <01JLNU3O0M7O9BWCNF@INNOSOFT.COM> for ietf-schema-reg@imc.org; Tue, 08 Feb 2000 10:33:34 -0800 (PST) Received: from threadgill.austin.innosoft.com (threadgill.austin.innosoft.com [207.8.108.5]) by austin.innosoft.com (PMDF V5.2-32 #41296) with SMTP id <0FPM00698JJXKW@austin.innosoft.com>; Tue, 08 Feb 2000 12:33:33 -0600 (CST) Date: Tue, 08 Feb 2000 12:33:33 -0600 From: Mark Wahl Subject: Re: Closure of the SCHEMA wg In-reply-to: "Your message of Thu, 27 Jan 2000 20:15:37 +0100." <838925.3157992937@[192.168.111.25]> To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= Cc: ietf-schema-reg@imc.org Message-id: <12712.950034813@threadgill.austin.innosoft.com> Sender: owner-ietf-schema-reg@imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: > The documents are from my point of view basically done apart from the text > which is supposed to describe the actual listing service itself, and that > text can not be created until the listing service exists. Does this mean that those documents with the IESG whose content does not describe the listing service itself will be sent to the RFC Editor for publication? Mark Wahl, Directory Product Architect Innosoft International, Inc. From owner-ietf-schema-reg@imc.org Wed Feb 9 01:12:10 2000 Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19832 for ; Wed, 9 Feb 2000 01:12:09 -0500 (EST) Received: by ns.secondary.com (8.9.3/8.9.3) id WAA12606 for ietf-schema-reg-bks; Tue, 8 Feb 2000 22:01:10 -0800 (PST) Received: from nix.swip.net (nix.swip.net [192.71.220.2]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id WAA12602 for ; Tue, 8 Feb 2000 22:01:07 -0800 (PST) Received: from 192.168.124.51 (workstation1.swip.net [130.244.254.1]) by nix.swip.net (8.8.8/8.8.8) with ESMTP id HAA18087; Wed, 9 Feb 2000 07:01:11 +0100 (MET) Date: Wed, 09 Feb 2000 07:01:05 +0100 From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= To: Mark Wahl cc: ietf-schema-reg@imc.org, Keith Moore , Ned Freed Subject: Re: Closure of the SCHEMA wg Message-ID: <7599047.3159068465@[192.168.124.51]> In-Reply-To: <12712.950034813@threadgill.austin.innosoft.com> X-Mailer: Mulberry/2.0.0b8 (MacOS) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-ietf-schema-reg@imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Content-Transfer-Encoding: 7bit --On 2000-02-08 12.33 -0600, Mark Wahl wrote: >> The documents are from my point of view basically done apart from the >> text which is supposed to describe the actual listing service itself, >> and that text can not be created until the listing service exists. > > Does this mean that those documents with the IESG whose content does not > describe the listing service itself will be sent to the RFC Editor for > publication? I have not got requests for publishing any of the documents until the listing service is implemented. If this is a wish, then those documents have to be published as individual submissions, the normal way. Patrik