augmenting std MIBs to use TransportAddress

[Andy Bierman <abierman@cisco.com>]

Hi,

I have a couple of Cisco MIB reviews that are augmentations
of the NOTIFICATION-LOG-MIB (RFC 3014) and SNMP-TARGET-MIB
(RFC 3413).  I'm having a little trouble interpreting sec 
3.1.2 of RFC 3419.  These augmentations are 'replacing'
the TAddress and TDomain objects with TransportAddress 
and TransportDomain objects.  The objects getting replaced:

nlmLogEntry:
    nlmLogEngineTAddress       TAddress
    nlmLogEngineTDomain        TDomain
    
snmpTargetAddrEntry:
    snmpTargetAddrTDomain      TDomain
    snmpTargetAddrTAddress     TAddress

Q1) RFC 3014 seems to imply that we should use the old objects
    for existing TAddress/TDomain values and use the new objects
    for new values that TAddress/TDomain doesn't cover.  I think
    this is broken.  I am telling the MIB designer to let the
    new objects override the old ones if they are set, and
    use the old objects if the new ones are not set.  Is this
    what the last paragraph of 3.1.2 is suggesting (and I'm
    just reading it wrong)?

Q2) What is the IETF plan for upgrading MIBs which use the old
    TAddress/TDomain data types to use the types in RFC 3419?

thanks,
Andy