p2p, why return known state?

[shanhuhai5739]

Hi there, p2p, why return known state? https://github.com/ethereum/go-ethereum/blob/master/p2p/discv5/net.go#L952

    remoteverifywait = &nodeState{
        name: "remoteverifywait",
        enter: func(net *Network, n *Node) {
            net.timedEvent(respTimeout, n, pingTimeout)
        },
        handle: func(net *Network, n *Node, ev nodeEvent, pkt *ingressPacket) (*nodeState, error) {
            switch ev {
            case pingPacket:
                net.handlePing(n, pkt)
                return remoteverifywait, nil
            case pingTimeout:
                return known, nil
            default:
                return remoteverifywait, errInvalidEvent
            }
        },
    }

[shanhuhai5739]

I think, it should be unknown state if handle pingTimeout

[shanhuhai5739]

hello anybody here?

[fjl]

It returns to known state because the other side had a chance to ping, but didn't use it. We will remove p2p/discv5 code soon, no need to worry about this code :)

[0xmountaintop]

It returns to known state because the other side had a chance to ping, but didn't use it. We will remove p2p/discv5 code soon, no need to worry about this code :)

what does "it" refer to in "but didn't use it"? am i correct that a normal peer will not ping, even if it has a chance, so we won't run into the consequent known state?