[Internal-cg] Document Content and Structure

Daniel Karrenberg daniel.karrenberg at ripe.net
Thu Jun 11 12:27:02 UTC 2015

I'd like to clarify and expand on my contribution to the previous call
regarding the document content and structure.

Our charter says:

"The IANA stewardship transition coordination group (ICG) has one
deliverable: a proposal to the U.S. Commerce Department National
Telecommunications and Information Administration (NTIA) regarding the
transition of NTIA’s stewardship of the IANA functions to the global
multi-stakeholder community."

So I propose to produce exactly that deliverable using as few words as
we are capable of. NTIA does not need a primer on what IANA is. NTIA
does not need a review of the environment or history. What NTIA needs is
the substance of the proposal and how it was produced. Nothing more,
nothing less.

I oppose

	- producing various versions for different audiences,
	- including explanatory material not intended for NTIA, and
	- copying or paraphrasing any existing documents.

If we can avoid it we should not even copy the responses we received
from the operational communities. We should reference them.

I am absolutely fine with collecting and providing a packaged bundle of
all the referenced documents for convenience and for the purpose of
avoiding references that might no longer be available or whose content
might change.

Rationale: We have to both produce and achieve consensus on our
deliverable in a very short time. The more we focus on the chartered
deliverable the less energy we waste producing unnecessary words and the
easier it will be to achieve consensus on the final product.

As I said on the call: we can have explanatory material such as
summaries, info-graphics or even cartoons ;-) produced that may help to
socialise our deliverable and gain acceptance of it. But that is not our
main job.

Let's stay focussed.


More information about the Internal-cg mailing list