[gtld-tech] gtld-tech URS technical requeriments

Eric Brunner-Williams ebw at abenaki.wabanaki.net
Tue Jul 9 01:42:53 UTC 2013

Gustavo, Colleagues,

A few meta-comments.

Working with text rather than pdf is the norm for standards track
specifications, and lesser documents, in the IETF.

IETF documents arise from a desire by two or more implementers of the
functionality to be specified to inter-operate.

2119 is a document intended for standards track documents.

IETF standards track documents arise from a desire by two or more
implementers of the previously specified functionality to formalize
the previously specified inter-operation. Generally a series of
non-normative documents precede the publication of a normative
document, e.g., the publication of grrp, xrp and epp drafts prior to
publication of 3730 et seq.

If you could make the obvious changes to the presentation form of the
text (from .pdf to ASCII, generally without the xml2rfc markup), and
delete the normative specification language from a non-normative draft
requirements doc, I could look past the first lines with confidence
that we are using mutually understood terms, I for one would be a
<registrar_hat="ON">happier camper</registrar_hat>.

Eric Brunner-Williams
IETF Performance Directorate

More information about the gtld-tech mailing list