From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4470 invoked by alias); 4 Dec 2002 10:57:43 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 4460 invoked from network); 4 Dec 2002 10:57:40 -0000 Message-ID: <387F69AC05062649946B28CFA0FD620C153588@esealnt853.al.sw.ericsson.se> X-Sybari-Trust: 027945c1 ca231590 9763731a 00000138 From: "Laith Said (DXD)" To: "'ecos-maintainers@sources.redhat.com'" Subject: eCos for Ethernet Switches Date: Wed, 04 Dec 2002 02:57:00 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-SW-Source: 2002-12/txt/msg00000.txt.bz2 Hi, My name is Laith Said and I have a small question about eCos. I'm trying to evaluate eCos as an operating system for an Ethernet switch, and there I game to question that I could not find an answer to, that is whether there are any layer 2 packages and RFCs that are implemented and can be used, for example 802.1D Spanning Tree, 802.1Q VLAN, and some other RFCs like 2737 Entity MIB, and RFC2030 SNTP. I know that eCos has the TCP/IP stack ready including TCP, UDP, DHCP, ICMP, .., and FTP, but I can not see any RFC numbers in the documentation, is it not implemented according to the RFCs? Please help me to find out, I think I need the place where I can find such information in general so that I can see what layer 2/3/4 packages are ready and what we should do ourselves. Thanks in advance. Laith...