Hello!
First off, I apologize for not getting this to you sooner. Thanks for the
reminder. Second off, I will need to spend more time with the spec, but I
did want to put some immediate reactions and questions up.
So here's what I saw upon a quick browse through the document:
- Where does this fit in with the Clearview IP Tunneling work?
- There are other consumers of this API. IKEv2 (or IKEv1 IKE-CFG
support) would use these as well to create tunnel interfaces. The
good news is that I don't see anything so far that would be a
hinderance, and in fact, stability here would help a LOT.
(We can test these APIs with punchind, BTW.)
- I see that there is absolutely no *_algs support ala. ifconfig(1M).
I do not mind EOL-ing these, but I do need to see an agenda for
how. This may be more dladm-level than ipadm, but it is something
we need to take into account.
- I assume the "-t" equivalent will be in the library as well, right?
- I have mixed feelings about EOL-ing XRESOLV. Nobody uses it, but
for IP-over-<new-technology> XRESOLV can provide a better way for
<new-technology> to implement ARP or ARP-like functionality.
(XRESOLV + PF_ROUTE was the inspiration for PF_KEY.)
I'll give a more careful read and see if anything else comes up.
Thanks,
Dan
_______________________________________________
networking-discuss mailing list
[email protected]
