Brian,
Brian E Carpenter wrote:
Well, since there are new data structures defined explicitly in the ISATAP spec, surely there *must* be additional logic to create, process, and delete those data. I'm referring to sections 8.1 and 8.3.1 of draft-ietf-ngtrans-isatap-22.txt.
I guess you are talking about the Potential Router List (PRL)?
That and the associated timers in 8.3.1, and then the PRL initialisation and refresh actions.
For the purpose of ingress filtering and perhaps default router discovery, the PRL should be quite small - usually no more than 1 entry. Any other uses for the PRL shouldn't add any more state beyond what the client already maintains.
OK. But if I was a picky hardware designer, I'd need to know how many entries the PRL might grow to in the worst case.
Brian