> -----Original Message-----
> From: EXT Richard Draves
>
> I have two possible designs for your consideration: A
> (simple) and B (more complex).
Either one is probably easy to implement and use.
I'm just wondering whether this type thing is the right direction to go with
the API? It requires each application to include a user controllable method
for choosing these settings.
In case of web browser, it's not just the case of choosing of care
address/home address for all connections. The actual need is could be to use
either care or home depending on which server one is using.
We already have a selector mechanism for IPSEC. It does occur to me that
this selector part could be a separate component, and IPSEC just one user of
it.
Another use of the selectors would be to define which connections use home
address and which are okay with care address. Similarly, there are probably
many other things that one could control through the selectors (quality of
service paramaters?).
Should we describe an API section that controls some kind of selector
mechanism, which would for example implicitly "fire" the specified socket
options for the connections that match? Let applications just do their own
stuff, and set control paramaters externally.
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
