public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Ray <stephen@mrmighty.net>
To: joy_mm@ieee.org
Cc: linux-newbie@vger.kernel.org
Subject: Re: filtering .mp3 packets
Date: Fri, 29 Apr 2005 08:43:42 -0300	[thread overview]
Message-ID: <42721DEE.7020102@mrmighty.net> (raw)
In-Reply-To: <4b0d6e0d050428200525186e50@mail.gmail.com>

I don't know about compression, but I see two problems with filtering 
based on mp3 headers (other than the apparent lack of tools supporting 
it).  The first is that some p2p protocols, such as Bittorrent, divide 
the files into chunks, sending and receiving them out of order.  So the 
header may be the last part of the file to be sent.  The other problem 
is that in any protocol, an mp3 file is going to be too big for a tcp/ip 
packet.  It seems very likely that an mp3 packet will be split across 
two or more packets.  That would make identification more problematic, 
as you would have to make sure that a header fragment was a header 
fragment, and not part of a legitimate file that happens to be 
coincidentally identical to part of a mp3 header.

Stephen

joy merwin monteiro wrote:
> Hi,
> 
> Since this thread dealt mainly with blocking p2p downloading of 
> mp3s since they consume large b/w, and has come to a discussion of
> https and scp,
> I wanted to know wether any p2p protocol uses the above......
> or even wehter they use compression.......
> 
> if neither is the case, what John said seems to be reasonable,, since
> MP3 _has_ to have a header......
> 
> blocking all outgoing http requests for or blocking all incoming MP3's
> will prevent genuine users who need it. alternatively, there should be
> a limit of connections that a user can open at a single time to get
> MP3s... since most p2p protocol that i've encountered always try to process
> the waiting list as fast as possible by downloading multiple files all
> at once....
> 
> Comments. anyone?
> 
> regards,
> Joy
> 
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2005-04-29 11:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 11:27 filtering .mp3 packets William Stanard
2005-04-25 16:56 ` Ray Olszewski
2005-04-26 11:36 ` John T. Williams
2005-04-27 14:15   ` J.
2005-04-27 15:22     ` simon
2005-04-27 19:51       ` J.
2005-04-27 22:57         ` John T. Williams
2005-04-28  0:39           ` Ray Olszewski
2005-04-29  3:05             ` joy merwin monteiro
2005-04-29 11:43               ` Stephen Ray [this message]
2005-04-29 15:24                 ` joy merwin monteiro
2005-04-29 15:51                   ` Ray Olszewski
2005-04-29 23:39                     ` joy merwin monteiro

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=42721DEE.7020102@mrmighty.net \
    --to=stephen@mrmighty.net \
    --cc=joy_mm@ieee.org \
    --cc=linux-newbie@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