the non-controversial changes i found in my sandbox

   the new address as a response.

   The "SOURCE_ADDR" field is included with NEW and NEWRESOLVE events if

   extended events are enabled.  It indicates the address that requested

   the connection, and can be (e.g.) used to look up the requesting

   program.

   extended events are enabled.  It indicates the address and port

   that requested the connection, and can be (e.g.) used to look up the

   requesting program.

4.1.3. OR Connection status changed

Rejected Alternative:

   "A router's Stability shall be defined as the sum of $\alpha ^ d$ for every

   $d$ such that the router was not observed to be unavailable $d$ days ago."

   $d$ such that the router was considered reachable for the entire day

   $d$ days ago.

   This allows a simpler implementation: every day, we multiply

   yesterday's Stability by alpha, and if the router was observed to be

   (By requiring that routers be up for an entire day to get their

   stability increased, instead of counting fractions of a day, we

   capture the notion that stability is more like "probability of being

   capture the notion that stability is more like "probability of

   staying up for the next hour" than it is like "probability of being

   up at some randomly chosen time over the next hour."  The former

   notion of stability is far more relevant for long-lived circuits.)

  return NULL;

}

/** Helper for sorting a list of time_t* */

/** Helper for sorting a list of time_t*. */

static int

_compare_times(const void **_a, const void **_b)

{

    return 0;

}

/** Helper for sorting a list of int* */

/** Helper for sorting a list of int*. */

static int

_compare_ints(const void **_a, const void **_b)

{

}

/** Given a sorted list of strings <b>lst</b>, return the member that appears

 * most.  Break ties in favor of later-occuring members. */

 * most.  Break ties in favor of later-occurring members. */

static const char *

get_most_frequent_member(smartlist_t *lst)

{