From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Using pppd as a library
Date: Wed, 15 Aug 2012 13:07:25 +0000 [thread overview]
Message-ID: <502B9F0D.3050302@workingcode.com> (raw)
In-Reply-To: <502A3A31.2050106@ibtechnology.com>
walter harms wrote:
> The question is do they need ppp at all ? I certainly has advantages to use
> tcp/ip but it is no requirement is several cases. Going with a more simple
> protocol can reduce the overhead considerable.
Please explain. What "more simple protocol" are you suggesting? SLIP,
perhaps?
I expect that the original poster's design constraints include having an
interoperable implementation -- that is, being able to talk to peer
machines built by other vendors. Whether the overhead is "considerable"
or not doesn't seem to factor into the choice.
--
James Carlson 42.703N 71.076W <carlsonj@workingcode.com>
prev parent reply other threads:[~2012-08-15 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 11:56 Using pppd as a library neha chatrath
2012-08-14 14:01 ` Charlie Brady
2012-08-14 14:29 ` Bill Unruh
2012-08-14 14:57 ` James Carlson
2012-08-15 6:20 ` Marcel Holtmann
2012-08-15 7:14 ` walter harms
2012-08-15 13:07 ` James Carlson [this message]
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=502B9F0D.3050302@workingcode.com \
--to=carlsonj@workingcode.com \
--cc=linux-ppp@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