On 10/30/2015 08:03 PM, Ian Coolidge wrote: > Hello, > > With the Linux SCTP implementation, Max.Init.Retransmits is respected > when INIT messages do not receive a response (ie, if SCTP host is > unavailable). However, if a Linux SCTP host is accessible, but has no > SCTP servers listening for incoming connections, it will quickly reply > ABORT. This doesn't trigger the Max.Init.Retransmits logic, so, > retries occur indefinitely. > > I looked through RFC 2960 for some guidance here. Both 3.3.7 and 4 > were unclear for how this should be handled. I suspect that these > ABORT responses to INIT should count towards Max.Init.Retransmits. > > Is there any clarification that I haven't found? > > What do the SCTP experts think should happen here? > An ABORT should terminate the association thus stopping any further INIT transmissions. Is that not happening? -vlad > Thanks > Ian > -- > To unsubscribe from this list: send the line "unsubscribe linux-sctp" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
