[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: ietf-provreg@cafax.se
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Date: Mon, 09 Apr 2001 18:33:09 -0400
Sender: owner-ietf-provreg@cafax.se
Subject: Re: Provreg WG Last Call (8.4 Data Collection Requirements)

Proposed (minor) changes to draft-ietf-provreg-grrp-reqs-01.txt:
8.4 Data Collection Requirements

current text:
  [1]  Some of the data exchanged between a registrar and registry MAY be
  ...
  A generic protocol MUST provide services to identify information whose
  disclosure is not strictly required for technical reasons.
  
proposed text:
  [1]  Some of the data exchanged between a registrar and registry MAY be
  ...
  A generic protocol MUST provide services to identify data collection
  policies.

Comment:
The first sentence is motivational, and is "close enough".
The second states a requirement, and is over-specific and incomplete.


current text:
  [2] Some of the social information exchanged between a registrar and
  registry MAY be REQUIRED to create, manage, or operate Internet or DNS
  infrastructure facilities, such as zone files.  Such information is
  subject to public disclosure per relevant IETF standards.
  
proposed text:
  None. This section to be omitted.

Comment:
The distinction between "social" and "technical" data originally was that
the second was reflected in zone files. "infrastructure facilities" is not
sufficiently precise. The need for an exemption from a disclosure label is
obviated by labels for disclosure and for non-disclosure. We may need to
add some data granularity beyond "technical" and "social", but this is a
better choice than suggesting that external texts remove any need to put
data collection labels on collected data.

If I've missed something seminal in the decomposition of the T && S model
in the past couple of weeks (and I have been distracted), please let me
know.

Eric

Home | Date list | Subject list