requirements List

["John Merrells" <merrells@xxxxxxxxxxxx>]

The architecture abstracts to be aired on Friday must cover
all the requirements in the repl req draft.  Here's my list
of the sub-clauses which must be addressed.  It's expressed
in my terms, and represents my understand of the current
requirements.  I hope this will spur on some more debate...

John


Mega-Summary of Replication Requirements

<4. General Requirements>

1) Replication MUST be simple to configure and maintain.

2.1) MUST be resource efficient.
2.2) SHALL allow replication to be postponed.
2.3) SHALL allow user initiated replication.
2.4) SHOULD update any unavailable replica when it comes back online.

3) All changes MUST eventually be applied to all Replicas.

4) MUST be interoperable.

5.1) MUST authenticate identity of replication partners.
5.2) MUST transfer updates securely.

6.1) MUST deal with differing schema
6.2) MUST recover if a replication party fails during update.

7) MUST provide LDAP access to replication agreements.

8) MUST maintain audit log.

9.1) Replication Agreements MUST allow scheduled replication.
9.2) MUST provide LDAP access to replication agreements. (Repeat of 1 & 7)

10.1) Replication Policy MUST allow scheduled replication. (Repeat of 9.1?)
10.2) Replication Policy MUST allow definition of replication content.
10.3) SHALL support scheduled replication Replication Policy. (repeat of 10.1, 9.1)
10.4) SHALL allow 'number of changes' Replication Policy .

11.1) MUST support Multi-master.
11.2) MUST support Master-Slave.

12.1) MUST allow total update.
12.2) MUST allow incremental update.
12.3) MUST allow updates to multiple replicas

13.1) MUST allow either master or replica be initiator
13.2) MUST allow initiator to determine if it is a supplier or consumer.

14) Master and Replica data SHALL be identical.

15.1) SHALL NOT ensure all Replicas are complete copies.
15.2) SHALL encompass common schema objects and attributes,
15.3) MAY define a mapping between divergent schemas for non-common schema objects and attributes.

16) SHALL define subtree replication (X.525 section 7.2)


<4.1 Replication policy>

17) SHALL store Replication Agreements as entries.


<4.1.1 Propagation behavior>

18) SHALL authenticate identity of replication parties (Repeat of 5.1)

19) SHALL transfer updates securely (Repeat of 5.2)

20) MUST NOT saturate network.

21) SHALL support total update. (Repeat of 12.1)

22) SHALL support be incremental update. (Repeat of 12.2)

23) SHOULD support transactions.

24) SHALL purge change information after replication.

25) Replication policies SHOULD contain clauses to account for the
instance of a replica being unavailable at the scheduled update time.


<4.1.2 Scheduling policies>

26.1) SHALL define replication schedule (Repeat of 9.1?)
26.2) SHOULD support 'every X hours' schedule
26.3) SHOULD support 'every N changes' schedule

27) SHALL support immediate replication of critical attributes.

28) SHALL allow user to initiate replication (Repeat of 2.3)


<4.2 Predetermined Replication Agreements>

29) MUST have Replication Agreements.

30) SHOULD allow LDAP access to Replication Agreements.


<4.3 Scalability>

31) MUST support incremental update. (Repeat of 12.2 & 22)

32.1) MUST scale to internet.
32.2) MUST function in enterprise.

33.1) MUST detect and resolve update conflicts in multi-master topology.
33.2) SHALL detect and resolve update conflicts in multi-master topology.
33.3) MAY store conflicts to allow user intervention.

34) SHALL allow replication with any LDAP server on network


<4.4 LDAP Access>

35) MUST allow LDAP access to replication topology.
35) MUST allow LDAP access to replication agreements. (Repeat)

<4.5 Administration Utility Requirements>

36) SHALL allow diff of Replicas.

37) SHALL allow view of replication topology from single server.

38.1) SHALL report state of each replica.
38.2) SHALL report replication history of each replica.

39) SHALL allow user intervention to resolve conflicts. (Conflict with MAY in 33.3)



--
John Merrells
Netscape Communications
Directory Server
Software Engineer

http://people.netscape.com/merrells