Scaling problems with Windows Clients name and address lookup

[Luke Kenneth Casson Leighton]

> The scope idea arrived before browsing and--as you say--was never
> implemented properly.  If I understand the RFCs correctly, scope was meant
> to segregate names.  The DNS provides a hierarchy which can be traversed. 
> Scope simply gives a name to a NetBIOS name "subspace". 

[correct]
 
> Machine zoobob.mouthwash would not have a name conflict with
> zoobob.stethe, because the NetBIOS name service would use the scope to
> keep the names separate.

correct. rfc1001/2 state that the NetBIOS scope is the bit from the .
onward, including the .

>  On the other hand, machines in stethe scope
> would not be able to resolve names for machines in the mouthwash scope. 

wrong, or at least, correct due to microsoft's _use_ of NetBIOS, not the
NetBIOS specifications and how it _can_ be used.