Scanning through the document, I will mention PASS or FAILs for some
issues
I know of.
LINK LAYER:
We do not support Ethernet trailing protocol (FAIL)
ARP
We support ARP cache entry invalidation using timeouts (PASS).
ARP timeout is staticly configurable at compile-time only (FAIL).
(We have implementation 1)
We do prevent generating ARP storms. (PASS)
We do support packet queueing of either the last (most recent) packet, or
multiple. (PASS)
NOTE: There is ambiguity about which packet should be queued (oldest or
latest in case of one).
Protocol Layer Upstream Broadcast link flag (FAIL).
NOTE: This can be implemented through a PBUF_FLAG which is already
reserved
for that
purpose, AFAIK.
No Destination Unreachable on no ARP cache entry (PASS).
IP LAYER:
PASS on all "MUST" issues except these:
We do not support multiple default gateways per network link. We do not
detect Dead Gateways and
cannot select another one.
We do support reassembly, but I do not think we support timeouts on
reassembly, or even ICMP Time
Exceeded(Reassembly Timeout).
This might even be an outstanding bug, where a partly reassembled packet
never gives up the fragments
memory space.
So far, I have little time to dive deeper into this at this time,
with regards,
Leon Woestenberg.
----- Original Message -----
From: "Kjell Andersson XW (LM/EAB)" <address@hidden>
To: <address@hidden>
Sent: Tuesday, September 02, 2003 11:48 AM
Subject: [lwip-devel] TCP requirement list
Have anyone taken a look at the RFC1122 chapter 4.2.5?
(http://www.ietf.org/rfc/rfc1122.txt?number=1122)
How well does lwip conform to that feature list?
_______________________________________________
lwip-devel mailing list
address@hidden
http://mail.nongnu.org/mailman/listinfo/lwip-devel
_______________________________________________
lwip-devel mailing list
address@hidden
http://mail.nongnu.org/mailman/listinfo/lwip-devel