Re: minor nits in draft-ietf-run-adverts-01.txt

Sally Hambridge <sallyh@LUDWIG.SC.INTEL.COM> Fri, 29 October 1999 17:56 UTC

Received: from mailbag.cps.intel.com (mailbag.cps.intel.com [192.102.199.72]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10074 for <run-archive@LISTS.IETF.ORG>; Fri, 29 Oct 1999 13:56:31 -0400 (EDT)
Received: from mailbag.intel.com (mailbag.cps.intel.com [192.102.199.72]) by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id KAA11183; Fri, 29 Oct 1999 10:39:24 -0700 (PDT)
Received: from MAILBAG.INTEL.COM by MAILBAG.INTEL.COM (LISTSERV-TCP/IP release 1.8d) with spool id 168832 for IETF-RUN@MAILBAG.INTEL.COM; Fri, 29 Oct 1999 10:39:23 -0700
Received: from clio.sc.intel.com (clio.sc.intel.com [143.183.152.25]) by mailbag.cps.intel.com (8.9.3/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id KAA11179 for <IETF-RUN@mailbag.cps.intel.com>; Fri, 29 Oct 1999 10:39:23 -0700 (PDT)
Received: from Ludwig.sc.intel.com (ludwig.sc.intel.com [143.183.53.32]) by clio.sc.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.10 1999/10/20 18:19:05 spurcell Exp $) with SMTP id KAA11012 for <IETF-RUN@MAILBAG.INTEL.COM>; Fri, 29 Oct 1999 10:37:03 -0700 (PDT)
Received: by Ludwig.sc.intel.com (4.1/SMI-4.1) id AA07754; Fri, 29 Oct 99 10:34:19 PDT
Message-ID: <9910291734.AA07754@Ludwig.sc.intel.com>
Date: Fri, 29 Oct 1999 10:34:19 -0700
Reply-To: IETF-RUN <IETF-RUN@mailbag.cps.intel.com>
Sender: IETF-RUN <IETF-RUN@mailbag.cps.intel.com>
From: Sally Hambridge <sallyh@LUDWIG.SC.INTEL.COM>
Subject: Re: minor nits in draft-ietf-run-adverts-01.txt
Comments: To: "Gavin, Ted (COR-EX)" <IETF-RUN@mailbag.cps.intel.com>
To: IETF-RUN@mailbag.cps.intel.com

Ted -  best to wait to resubmit until after the Wash DC
meeting.  There will be other feedback
to incorporate generated during the WG session,
so we'll resubmit with an incremented draft
number after the meeting.

Sally
>
>
>Sally, April or Donald - should I resubmit as an incremented draft ID
>number, or should we just wait for RFC consideration to submit the updated
>doc?
>
>tg
>