Dimitri,
The identifier to locator mapping function MUST supportmapping entriesfor aggregates of identifiers. It MAY also support mappingentries forhost identifiers.i suggest to refine the requirement: one is the nature / structure of the identifier itself, the other is in terms of scalability ("aggregation" of identifiers), and the last one in terms of ID-to-Loc mapping function.
I agree, we should describe what the identifiers are and how they can be aggregated. Then another requirement can specify how the mapping will work.
Hi Tony and Olivier,Does this requirement imply that the identifier must be ahierarchical labelI don't think that a hierarchy is necessary. What is required is a mapping system that deals with blocks of identifiers and not with individual identifiers.(not flat label) so as to be aggregatable?agreed. aggregates of identifiers shall be defined though to complete the initial requirement. what's relationship between block & aggregate of identifiers ?
From my viewpoint block=aggregate Olviier -- http://inl.info.ucl.ac.be , Universite catholique de Louvain, Belgium -- to unsubscribe send a message to rrg-request@psg.com with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg