From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 29 Mar 2001 06:46:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 29 Mar 2001 06:45:57 -0500 Received: from zeus.kernel.org ([209.10.41.242]:58848 "EHLO zeus.kernel.org") by vger.kernel.org with ESMTP id ; Thu, 29 Mar 2001 06:45:22 -0500 To: Subject: Re: RFC: configuring net interfaces In-Reply-To: <20010328182729.A16067@se1.cogenit.fr> <20010329112547.A23947@se1.cogenit.fr> Content-Type: text/plain; charset=US-ASCII From: Krzysztof Halasa Date: 29 Mar 2001 13:07:58 +0200 In-Reply-To: Francois Romieu's message of "Thu, 29 Mar 2001 11:25:47 +0200" Message-ID: MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Francois Romieu writes: > Parameters for retransmission of a trame specified in Q922. t200 is the > timeout value and n200 the maximal number of retransmissions. They can > be negocied and default to t200=1,5s, n200=3. Hmm... I've taken a look at it, but it seems to me that they are only used with "acknowledged multiple frame operation". Isn't it for ISDN only? With Frame Relay, we rather use unacknowledged transfers and UI frames. Of course, if we have an implementation using t200, n200 or other parameters, they should be added to the structure. -- Krzysztof Halasa Network Administrator