From: Krzysztof Halasa <khc@intrepid.pm.waw.pl>
To: <linux-kernel@vger.kernel.org>
Subject: Re: RFC: configuring net interfaces
Date: 29 Mar 2001 13:07:58 +0200 [thread overview]
Message-ID: <m33dbw7rzl.fsf@intrepid.pm.waw.pl> (raw)
In-Reply-To: <m3itkuq6xt.fsf@intrepid.pm.waw.pl> <20010328182729.A16067@se1.cogenit.fr> <m34rwd8pj2.fsf@intrepid.pm.waw.pl> <20010329112547.A23947@se1.cogenit.fr>
In-Reply-To: Francois Romieu's message of "Thu, 29 Mar 2001 11:25:47 +0200"
Francois Romieu <romieu@cogenit.fr> 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
next prev parent reply other threads:[~2001-03-29 11:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3itkuq6xt.fsf@intrepid.pm.waw.pl>
2001-03-28 21:24 ` RFC: configuring net interfaces Ivan Passos
2001-03-29 0:11 ` Jeff Garzik
2001-03-28 21:53 ` Ivan Passos
2001-03-29 11:29 ` Krzysztof Halasa
2001-03-30 5:43 ` Jeff Garzik
2001-03-31 22:41 ` Krzysztof Halasa
2001-04-01 22:18 ` Jeff Garzik
2001-04-02 19:10 ` Krzysztof Halasa
2001-04-03 8:27 ` Francois Romieu
2001-04-03 13:07 ` Krzysztof Halasa
2001-04-04 8:18 ` Francois Romieu
2001-03-29 11:24 ` Krzysztof Halasa
[not found] ` <20010328182729.A16067@se1.cogenit.fr>
2001-03-28 23:03 ` Krzysztof Halasa
2001-03-29 0:13 ` Paul Fulghum
2001-03-29 10:34 ` Krzysztof Halasa
2001-03-29 9:25 ` Francois Romieu
2001-03-29 11:07 ` Krzysztof Halasa [this message]
2001-03-29 14:55 ` Paul Fulghum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m33dbw7rzl.fsf@intrepid.pm.waw.pl \
--to=khc@intrepid.pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox