Grouping Listening Points

Hi-

Is there a particular way that listening points should be grouped under 
SipProviders of a given stack? (other than the rule of at most one 
listening point of a given transport type per SipProvider). IE: Given a 
user-specified configuration containing any number of 
IPaddress/port/transport combinations for a single stack instance, it 
seems logical to create a separate SipProvider for each IPaddress/port 
combination. From an application or application container perspective, 
is there any reason why you might not want to do that?

Thanks in advance for any advice-
Becky