New Contributor
Super Contributor(Host = master, agent = slave here)
If the agent is using the waitrequest signal, meaning you can have variable latency controlled by the agent, and that signal is held "forever", then the host must acknowledge that and continue issuing the address and read/write enable (and writedata if its a write) "forever." There is no provision in the spec for a timeout, though there's no reason why if you're designing a host component that you include a timeout in its design (i.e. counter that counts cycles of waitrequest and releases control signals after a set number of cycles).
