RE: [pilc] An off topic question on a BCP.

"Spencer Dawkins" <sdawkins@cynetanetworks.com> Wed, 11 December 2002 20:04 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18797 for <pilc-archive@odin.ietf.org>; Wed, 11 Dec 2002 15:04:04 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBBK6Xu17670 for pilc-archive@odin.ietf.org; Wed, 11 Dec 2002 15:06:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBK6Xv17667 for <pilc-web-archive@optimus.ietf.org>; Wed, 11 Dec 2002 15:06:33 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18791 for <pilc-web-archive@ietf.org>; Wed, 11 Dec 2002 15:03:33 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBJxWv17458; Wed, 11 Dec 2002 14:59:32 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBBJuSv17389 for <pilc@optimus.ietf.org>; Wed, 11 Dec 2002 14:56:28 -0500
Received: from MAIL.cynetanetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18439 for <pilc@ietf.org>; Wed, 11 Dec 2002 14:53:27 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: [pilc] An off topic question on a BCP.
Date: Wed, 11 Dec 2002 13:56:22 -0600
Message-ID: <9255B6CD76A88943A3062F7D4E6432F543B9B2@mail.cynetanetworks.com>
Thread-Topic: [pilc] An off topic question on a BCP.
Thread-Index: AcKhTE5ppw+p92TkQdaPbQViGLrHIwAAocdQ
From: Spencer Dawkins <sdawkins@cynetanetworks.com>
To: pilc@ietf.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id gBBJuSv17390
Sender: pilc-admin@ietf.org
Errors-To: pilc-admin@ietf.org
X-BeenThere: pilc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pilc>, <mailto:pilc-request@ietf.org?subject=unsubscribe>
List-Id: Performance Implications of Link Characteristics IETF Working Group <pilc.ietf.org>
List-Post: <mailto:pilc@ietf.org>
List-Help: <mailto:pilc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pilc>, <mailto:pilc-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hi, Emmanuel,

It's in the RFC Editor queue, so it will have an RFC number and BCP number when it's published, but don't believe numbers have been assigned yet. By when do you need a citable citation?

Spencer

> -----Original Message-----
> From: Emmanuel Papirakis [mailto:emmanuel.papirakis@cilys.com]
> Sent: Wednesday, December 11, 2002 12:54 PM
> To: pilc@ietf.org
> Subject: [pilc] An off topic question on a BCP.
> 
> 
> Hi,
> 
>     I have noticed that the document:
> 
> - draft-ietf-pilc-asym-08.txt
> 
> now has BCP  status. It doesn't have an RFC number, although, I have 
> seen other RFCs that hold the exact same status (2026 for example). I 
> would like to know if it would be appropriate to cite this 
> document as a 
> BCP instead of a "work in progress" (and other than this document: 
> http://citeseer.nj.nec.com/261063.html).
> 
> Also, is it expected that this publication will obtain an RFC 
> number at 
> some point ?
> 
> Thank you
> 
> Emmanuel Papirakis
_______________________________________________
pilc mailing list
pilc@ietf.org
https://www1.ietf.org/mailman/listinfo/pilc
http://www.ietf.org/html.charters/pilc-charter.html
http://pilc.grc.nasa.gov/