From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12646 invoked by alias); 19 Dec 2002 13:11:18 -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 12638 invoked from network); 19 Dec 2002 13:11:17 -0000 Message-ID: <3E01C565.7030000@eCosCentric.com> Date: Thu, 19 Dec 2002 05:11:00 -0000 From: Jonathan Larmour User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827 X-Accept-Language: en, en-us MIME-Version: 1.0 To: "Laith Said (DXD)" CC: "'ecos-maintainers@sources.redhat.com'" Subject: Re: eCos for Ethernet Switches References: <387F69AC05062649946B28CFA0FD620C153588@esealnt853.al.sw.ericsson.se> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-12/txt/msg00022.txt.bz2 Laith Said (DXD) wrote: > 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? It's based on the BSD stack which is RFC compliant, but doesn't include those particular features. Jifl -- eCosCentric http://www.eCosCentric.com/ --[ "You can complain because roses have thorns, or you ]-- --[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine