[Dime] Questions regarding RFC 6733

[Ajinkya Joshi <[e-mail]>]

Hello,

I have following questions regarding diameter RFC 6733, I would really
appreciate if someone can help me with these.

1. Regarding diameter peer state machine -

    Section 5.6.1 (Peer State Machine --> Incoming connections) mentions
that Origin-host is used for     identifying peer state machine and as per
state machine, once it moves into I-Open, new CER is       rejected. This
concludes, that there can't be more than one transport connections with
same               diameter host (as specified by Origin-host).

    Section 2.1 (Transport) mentions that "A given Diameter instance of the
peer state machine MUST      NOT use more than one transport connection to
communicate with a given peer, unless multiple        instances exist on
the peer, in which, case a separate connection per process is allowed."

     Questions --

   - Does section 2.1 implicitly assumes that multiple diameter instances
   (within a peer) would correspond to different diameter host ? Otherwise, it
   could contradict with section 5.6.1
   - If multiple transport connections (towards the same peer) are allowed
   per diameter host, is it expected that peer would do load balancing between
   them? (There is a connection load balancing section in RFC 3539 - Section
   3.4.3)

2. Regarding diameter peer failback procedure -

      Section 5.5.4 mentions "a connection request should be periodically
attempted with the failed              peer in order to re-establish the
transport connection"

      Question --


   - If the failed peer is dynamically discovered via DNS lookup, is it
   expected that peer would perform DNS query before trying to establish the
   connection again? Or DNS lookup is driven only by TTL field received in the
   prior DNS answer ?

-- 
Regards,
Ajinkya Joshi