RE: ND (NUD) on ISATAP links

Hi All,

> 
> The scalability problem you mention only happens when there are
> very few routers serving a lot of hosts.  In that case, a 
> particular router
> is more likely to be picked as a next hop and NUD will be run 
> after the
> AdvReachableTime has expired. The consuption of resources on 
> that ISATAP 
> router will roughly equivalent to a normal IPv6 router in a similar 
> configuration (+ the extra is a tunnel overhead) so I don't 
> see a large 
> problem with scalability.
> 
> 


As I understand it, there are two sides to this question.

In the above, the resources that you speak about 
are the resources needed at a particular ISATAP
router in order to _participate_ in NUD
performed by its ISATAP host (responding to NS's).

Another concern is the scalability issues in relation
to the resources needed at the ISATAP router in order to
_perform_ NUD on its ISATAP neighbours - Do we agree that this has been ruled out -
i.e. that performing NUD only is going to be demanded of ISATAP hosts - or
do we want a LAN-like IPv6 functionality on ISATAP routers ?

(As is (static address resolution) "ISATAP" NUD does not work on routers)

Karen