mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Telford002@aol.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [HDLC] Purpose of this Driver?
Date: 05 Feb 2002 13:30:30 +0100	[thread overview]
Message-ID: <m3wuxsw1p5.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <107.c6a18b1.29907d5b@aol.com>
In-Reply-To: <107.c6a18b1.29907d5b@aol.com>

Telford002@aol.com writes:

> HDLC is somewhat ambiguous.  CCITT/ITU documents use HDLC
> to refer to a whole class of protocols.  By raw HDLC, I believe is
> meant a specific BOP (Bit-Oriented Protocl) where flags encapsulate
> frames and the transmitter performs bit insertion and the 
> receiver performs bit deletion.  Even if the usual 0x7e flags
> are used with the standard bit insertion/deletion algorithm, there
> are still two variants, one with flag idles and the other with
> mark idles.

Plus there are different CRCs or no CRC (FCS) at all.
In fact, we're using "idle flags" version only (?).

> Is there a document that attempts to specificy the type of
> WAN interface that is a goal?  In truth, if the intent is the
> specification of a generic WAN interface, I would recommend
> aiming for more generality than basic flag-framing and bit-insertion
> bit-deletion BOP.

Not sure what do you mean - we don't aim at raw HDLC only. Raw HDLC
is included for completness, as well as things like FR or PPP are.

If you think of different encapsulation, it can be added of course.
-- 
Krzysztof Halasa
Network Administrator

       reply	other threads:[~2002-02-06 10:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <107.c6a18b1.29907d5b@aol.com>
2002-02-05 12:30 ` Krzysztof Halasa [this message]
     [not found] <143.90e492f.29927e68@aol.com>
2002-02-09  0:20 ` Krzysztof Halasa

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=m3wuxsw1p5.fsf@defiant.pm.waw.pl \
    --to=khc@pm.waw.pl \
    --cc=Telford002@aol.com \
    --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

all inboxes | Powered by JetHome®