From: Arnt Karlsen <arnt@c2i.net>
To: Daniel Chemko <dchemko@smgtec.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: RFC 3514 support?
Date: Wed, 2 Apr 2003 01:28:04 +0200 [thread overview]
Message-ID: <20030402012804.2d306f91.arnt@c2i.net> (raw)
In-Reply-To: <7C9884991ADAE0479C14F10C858BCDF50C6FEA@alderaan.smgtec.com>
On Tue, 1 Apr 2003 14:54:04 -0800,
"Daniel Chemko" <dchemko@smgtec.com> wrote in message
<7C9884991ADAE0479C14F10C858BCDF50C6FEA@alderaan.smgtec.com>:
> http://news.com.com/2100-1001-257064.html?legacy=cnet&tag=nbs
..looks like the RFC-3514 Implementation Team has started
the fun quicker, the 2549 team took a year or so. ;-)
> -----Original Message-----
> From: Arnt Karlsen [mailto:arnt@c2i.net]
> Sent: Tuesday, April 01, 2003 1:13 PM
> To: netfilter@lists.netfilter.org
> Subject: Re: RFC 3514 support?
>
> On Tue, 1 Apr 2003 10:36:11 -0800 (PST),
> Scott MacKay <scottmackay@yahoo.com> wrote in message
> <20030401183611.37140.qmail@web13904.mail.yahoo.com>:
>
> will this enhance quality of service for avian carrier
> grade links too? (http://www.faqs.org/ftp/rfc/rfc2549.txt)
>
> > I plan to add it into my userspace mangler, but only
> > for suspicious source IP addresses (like ones which
> > resolve with dangerous works like 'sinister') :)
> >
> > I also intend to shortcut some of the design for item
> > (4) by simply having a toggled bit to determine if it
> > should be on or off (thus achieving true, pure, even
> > randomness)...
> >
> > -Scott
> >
> > --- Bob Keyes <bob@sinister.com> wrote:
> > > I am wondering if there are any plans to support RFC
> > > 3514 in netfilter?
> > > ftp://ftp.rfc-editor.org/in-notes/rfc3514.txt
> > >
> > > Specifically, I'd like to tag all kazaa packets.
> >
> >
> > __________________________________________________
> > Do you Yahoo!?
> > Yahoo! Tax Center - File online, calculators, forms, and more
> > http://platinum.yahoo.com
> >
>
>
--
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
next parent reply other threads:[~2003-04-01 23:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7C9884991ADAE0479C14F10C858BCDF50C6FEA@alderaan.smgtec.com>
2003-04-01 23:28 ` Arnt Karlsen [this message]
2003-04-01 20:08 RFC 3514 support? Daniel Chemko
2003-04-01 20:22 ` Jeremy Jones
2003-04-01 21:26 ` Jeremy Jones
-- strict thread matches above, loose matches on Subject: below --
2003-04-01 18:12 Bob Keyes
2003-04-01 18:36 ` Scott MacKay
2003-04-01 21:13 ` Arnt Karlsen
2003-04-01 22:31 ` Scott MacKay
2003-04-01 20:34 ` Martin Josefsson
2003-04-01 20:59 ` Bob Keyes
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=20030402012804.2d306f91.arnt@c2i.net \
--to=arnt@c2i.net \
--cc=dchemko@smgtec.com \
--cc=netfilter@lists.netfilter.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