ENRP Server Hunt Timer

Johnson Walter-CWJ002 <[email protected]>
Newsgroups gmane.ietf.rserpool
Message-ID <6F8DFFA2C996D711945800065BFC9E4A119D4E6B@il02exm11>
Currently the draft states in ENRP server hunt procedure of section 3.6 bullet item SH5 on page 21 that

SH5) If the T5-Serverhunt timer expires the following should be
      performed:

      SH5.1) The endpoint MUST double the value of the T5-Serverhunt
         timer.
      SH5.2) The endpoint SHOULD stop the establishment of associations
         and connections.
      SH5.2) The endpoint SHOULD repeat trying to establish an
         association or connection by proceeding to step SH1.  It SHOULD
         attempt to select a different set of transport addresses to
         connect to.

Currently the T5-Serverhunt timer keeps on doubling and there is no upper limit on this so it appears it could go on forever. It would seem reasonable to add a ceiling on the max value that the T5-Serverhunt can reach (e.g. a variable max.severhunt.value to section 5.1) or place to place a threshold of attempts to make called MAX-SERVER-HUNTS in section 5.3. If either max is reached, a signal could be sent to an ASAP application of the failure to find a home ENRP server. 

If people feel this is a good change I can craft the text for it.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.