At 7:14 PM -0800 2/25/05, Dave Crocker wrote:
On Fri, 25 Feb 2005 09:59:19 +0000, Dave Singer wrote:
Ý a) renaming of the root portion of the file-name is permitted, nay

Ý encouraged, to identify whether the draft is currently individual, or
Ý owned by a group (or even to select a 'better' name for other
Ý reasons);
Ý b) the revision number is NOT reset when the name is otherwise changed;
Ý c) all drafts must include a revision history including the full name
Ý under which each draft was presented.


this is in line with some other postings, and I think it is quite a good summary. retaining version history is a nice touch.

Thanks. I forgot to say on (c) that there MUST be as many entries in the revision history as the revision number indicates (i.e. none for revision 00, and so on). Perhaps a standard format of the revision history would help? Clearly file name, submision date, summary of the nature of what's new in this version...



in terms of naming, I think syntactically it reduces to:


I-D-Name = "draft-" owner "-" category "=" title "-" version

  owner          =  author-name / "ietf"
                   ; who retains change control

  author-name    = { last name of first author }

  category       =  working-group / topic

  working-group  = { IETF working group }

  topic          = { term under which I-D topic fits}

  title          = { text specific to this I-D, to describe it }


* Version 0 must be submitted some extra amount of time before an IETF meeting.


* Use of the working group name is authorized by the working group chair and represents an explicit hand-off of change-control for the document, to the IETF.

* If a working group goes defunct, prior to RFC publication of the I-D, "ownership" reverts to the authors.
d/





d/ -- Dave Crocker Brandenburg InternetWorking +1.408.246.8253 dcrocker Ýa t ... WE'VE MOVED to: Ýwww.bbiw.net


--
David Singer
Apple Computer/QuickTime

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

Reply via email to