[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Consolidation of several counts thread
this is the fourth memo, summarizing the thread: RE: Consolidation of
several counts thread. Note that there were a lot of subjects covered in
this thread. Only those subjects that directly pertain to the requirements
I-D will be discussed here. Other subjects having merit will be discussed
This memo is written as a summarization by the WG Co-Chair of declaring
consensus on discussed items and requesting changes to be made to the
current (-06) version of the requirements I-D prior to it being reissued
for WG Last Call.
Issue 1: if we start singling out particular types of information that can
or can not be replicated, where do we stop?
We've had two different attempts to characterize this issue. One was the
(in)famous active vs. passive data, and the other was Kurt explicitly
listing several types of attributes with MUST, SHOULD, and MAY support
levels. This implies that some members of the WG are trying to define this
in more detail. However, I would like to see more detail in what we are
recommending. The active vs. passive definition fails due to the lack of
familiarity with the precise meanings of the terms. Similarly, listing some
but not all attributes to be replicated just raises questions about what to
do with the attributes that aren't specified.
Action: Kurt to work with the authors to either build a matrix of ALL
attributes and whether they should be replicated or not, or the authors
convince Kurt that he's wrong ;-) and this doesn't need to be satisfied.
Result to be posted to the WG list.
Issue 2: stop using the term passive data to describe what can be replicated
I'm going to make the decision to stop this discussion. I don't see this
discussion being resolved, and Jerry brought up the point that most
implementations will have operational attributes modified for even the
passive data. Proponents and opponents have still not reached a common
ground, and there are many unanswered questions from each side.
Co-Chair, LDUP WG