Responding to option 161 requests in heterogeneous byod-allowed network

[John Wobus]

Anyone have experience to share supporting thin clients with option 161
responses throughout a heterogeneous net?  Is there a useful way to  
target
the response to current and future thin client models that use it
in its current sense?

We've always used classes to target these sorts of functions to  
appropriate
clients but in googling option 161, I've found very little about what  
folks
are doing.  Obviously something both specific to the relevant thin  
clients
and unlikely to be used for anything else is what would have some value.

John Wobus
Cornell University IT