On 4/5/2017 12:46 PM, Michael Welzl wrote: > There isn’t much; Nagle is an example - RFC 1122 just says that the > functionality to enable / disable must be there, without specifying via which > primitive that would happen. > So, my draft says, in pass 2: > > o DISABLE_NAGLE.TCP: > Pass 1 primitive / event: not specified > > Seems like I should do the same for set_auth and get_auth. Set_auth and get_auth are either in the STATUS (as per my previous message) or SEND/RECEIVE.
There may be other signals that need to be specified. E.g., RFC1122 has a few items that need to be indicated, but isn't clear about them being only inside SEND/RECEIVE commands (e.g., see sections 4.1.4 and 4.2.4). Joe _______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
