RFC 1327 Mappings in X.500

[Steve Kille <[e-mail]>]

I started work on editing this yesterday, and working through the
implications of various changes.   

Currently, the mapping is placed in the routing trees.   There is a
note to explain why storing the mapping separately is not chosen.   I
think that we should reverse this decision for the following reasons:


1) There are severe difficulties with maintaining consistency between
1327 mappings held in multiple routing trees.  This has been exposed
in review.

2) A gateway needs good access to all of the mappings.   The new
approach makes replication much easier.

3) The "ommitted component" stuff fits very very badly into the open
routing tree

4) Having a separate area gives a much easier and more manageable
migration/relationship with the table approach


I believe that this is a strong case, and will change the I-D in this
manner.    What do others think?


Steve