Phil Neumiller writes:
>
> I am sorry about that "sand" comment. It seems the arguments quickly get circuitous. What we
> are suggesting is something really subtle.
>
> A). IP needs to create a standard interface method on its unspecified bottom half.
No, unless it describes a protocol, it doesn't. Such a method would
either have to be really vague ("needs some way to send one or more
packets") or would have to be dependent on system architecture. If
it's really vague, then it's at best an Informational document, though
I don't see the purpose. If it's dependent on system architecture,
then it doesn't belong in the IETF.
> B). It already has one on the top, namely sockets.
Note that sockets are not an IETF standard in any way. (Yes, some
documents do have references to them, but I think this is much more
"bug" than "feature.")
Note also that *many* systems have non-sockets ways of accessing IP --
including TLI. The IETF doesn't standardize software interfaces and,
as I've said before, is ill-equipped to do so and ought not do so.
This is what groups like X/Open do for a living.
> This is quite different than saying, all L2s must do this or that. What we want is a mechanism to
> pass L2 information in a standard way up to and through the IP stack. In order for this to
> happen in the correct way, the IETF needs to specify it.
I don't see how that can actually be done.
> What is so complicated about this? Just because we proposing something new, i.e. it
> does not exist in ppp, arp, or other similar mechanisms why is it immediately assumed
> that it is an L2 issue?
The problem is that it's not externally visible. I don't think it can
be specified in any terms that will make sense in an architecture-
neutral form.
> The IETF has already made their recommendations to L2 providers. Now its time for
> the IETF to be a bit more introspective. If there are some skeletons here, let's pull them
> out and take a peek.
I think the recommendations are exactly the right vehicle here.
-- James Carlson, Solaris Networking <james.d.carlson@east.sun.com> SUN Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677_______________________________________________ pilc mailing list pilc@ietf.org https://www1.ietf.org/mailman/listinfo/pilc http://www.ietf.org/html.charters/pilc-charter.html http://pilc.grc.nasa.gov/
This archive was generated by hypermail 2b29 : Tue Jun 18 2002 - 13:03:00 EDT