Subject: RE: [newtrk] Meeting discussion of ISDs- BCPs as core documents (outstanding)

From: <[email-masked]>
Date: Tue, 16 Nov 2004 07:07:44 +0200

John,

> This is the third of several summaries of my notes from last
> week's discussion of ISDs.   This note and subsequent ones cover
> outstanding issues and areas that are still very much under
> discussion (or where disagreements are known to exist).
> 
> At least conceptually, an ISD has some defining document at its
> core, with other documents supplementing, supporting, modifying,
> or updating it.  It is clear that standards track documents can
> occupy that core and that any other sort of documents can be
> included, either normatively or internationally, as
> additional/supplemental documents.
> 
> Question: Can BCPs be core documents for ISDs, or do "current
> practice" documents continue to belong in a different series.
> 
> Note that, at least for thinking about ISDs, we may need to
> logically partition the BCP series.   We have, at least, the
> following three sorts of documents published as BCPs:
> 
> 	   -- IETF Process documents, such as RFC 2026/BCP 9.
> 	RFC 2026 which would clearly be a core document of an
> 	ISD, as illustrated by Scott's example I-D, if we allow
> 	BCPs as core documents at all.
> 	
> 	   -- Operational practices for the Internet.  These
> 	documents will often be incorporated into ISDs as
> 	supporting documents for some standards track core
> 	document(s), but might stand alone.
> 	
> 	   -- Profiles and applications of standards.  This
> 	third type, in particular, will often be replaced by
> 	listing, with qualifying text, in ISDs with the
> 	associated standards, rather than being separate BCPs.
> 
> The question above might possibly need different answers for
> these three types of BCPs.

I think we shouldn't consider process documents right now, they
seem to fall under general administative documents, and not
standards.

Operational practices should be included within other ISDs.

Profiles and applications of standards type of documents may, 
in the future, become less important as ISDs get used, but
existing ones should be included within other ISDs. I don't
think a seperate ISD needs to be created.

John L.

.
newtrk resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/newtrk.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/newtrk/index.html