> Similar concept, same scaling problems; it just hides the explicit
routing
> from the user (as would any modern "peering" system, presumably).
Then you are presuming wrongly. Nowhere in what I wrote have
I suggested any changes in the existing email technology. I am
not suggesting that we drop
> There are, however, three very big problems. First, it forces people to
> pay for services that they don't pay for today.
Businesses often pay, not for services, but for accountability.
They want someone else to take responsibility for a problem
even if it costs them more money than taking
> > The thousands of bilateral BGP peering contracts are most
> > definitely comparable to the email peering that I am
> > proposing.
>
> Dude, it's 2005. You can put down the X.400 crack pipe now.
Why does fixing the SMTP email architecture by applying some
lessons learned from BGP peering le
[EMAIL PROTECTED] wrote:
Similar concept, same scaling problems; it just hides the explicit
routing
from the user (as would any modern "peering" system, presumably).
One way that it COULD be implemented is for people accepting
incoming email on port 25 to check a whitelist before ac
On 17/06/05, Joe Maimon <[EMAIL PROTECTED]> wrote:
> DNSWL -- this is already being done. It is not widely viewed as being in
> any way similar to a peering concept. What would be more similar would
> be a consortium of large providers providing such a whitelist. That
> would be something I would
Has anyone seen a major issue out of Atlanta with AT&T...
Thanks,
Jim
Hello Everyone:>
We are very happy to report the next steps in the evolution of NANOG are
underway. We welcome your support and feed-back.
The new NANOG charter is available at:
http://www.nanog.org/charter.html
changes in the new charter include:
Section 5: added a parenthetical cl
> The candidates for the Steering Committee are:
>Joe Abley
>Randy Bush
>Christopher Chin
>Ron da Silva
>Vince Fuller
>Steve Gibbard
>Dan Golding
>Martin Hannigan
>Dorian Kim
>Mark Kosters
>Jared Mauch
>Chris Morrow
>William B. Norton
>Philip
I was hoping the report would be cleaned up by now but it hasn't so sorry
for the multiple list post. The Bogon section is IMHO, broken.
Taking just the 1st line as an example:
Prefix Origin AS AS Description Unallocated block
3.0.0.0/8 AS80 GE-CRD - General Electric Company 0.0.0.0 - 3.0.
[EMAIL PROTECTED] said:
> That is something that businesses will pay for.
>
> But first, ISPs have to put their hands up and take
> collective responsibility for Internet email as a service
> that has value and not just as some kind of loss leader
> for Internet access services.
Many large orga
> Many large organizations already have already, in a case by case way,
set
> up private mail peering with others they exchange large volumes of mail
> with. This "trusted traffic" is often able to bypass the expense and
delay
> of the spam-filter farm, making the cost and hassle of a parallel m
[EMAIL PROTECTED] said:
> That's strange because you just finished describing how
> SOME companies are already engaging in email peering on
> a piecemeal basis. And how these companies ARE finding
> this to be beneficial in reducing costs. So please explain
> why my suggestion about widespread e
Only issue we've seen is a number of people connecting Cogent to AT&T in
DFW.
Jim McBurnett wrote:
Has anyone seen a major issue out of Atlanta with AT&T...
Thanks,
Jim
--
--
Tom Sands
H. I saw some alarms on equipment on AT&T's IP network in Grand
Rapids, MI a while ago. The alarm only lasted 10-15 minutes though.
--
Jonathan M. Slivko - [EMAIL PROTECTED]
"Linux: The Choice for the GNU Generation"
- http://www.linux.org/ -
Don't fear the penguin.
In message <[EMAIL PROTECTED]
om>, [EMAIL PROTECTED] writes:
>
>> Similar concept, same scaling problems; it just hides the explicit
>routing
>> from the user (as would any modern "peering" system, presumably).
>
>Then you are presuming wrongly. Nowhere in what I wrote have
>I suggested any chang
I should probbably say my equipment on AT&T's IP network - not the core
network.
--
Jonathan M. Slivko - [EMAIL PROTECTED]
"Linux: The Choice for the GNU Generation"
- http://www.linux.org/ -
Don't fear the penguin.
.^.
/V\
/( )\
^^-^^
He's h
Randy,
People's employers are posted at http://www.nanog.org/candidates05.html.
It gets a bit complicated because some folks work at "infrastructure"
companies - collocation/peering or DNS (Mark, Bill, Josh, Marty). Others do
significant consulting work for large providers or hosters, but aren't
This is an automated weekly mailing describing the state of the Internet
Routing Table as seen from APNIC's router in Japan.
Daily listings are sent to [EMAIL PROTECTED]
If you have any comments please contact Philip Smith <[EMAIL PROTECTED]>.
Routing Table Report 04:00 +10GMT Sat 18 Jun, 2005
I am pleased to announce that the three new members of the
NANOG Committee are:
Joe Abley
Henry (Hank) Kilmer
Christopher Morrow
Although we had many fine, well-qualified candidates to choose among,
we were only able to select people for the three openings.
Please join me in welcom
I am looking for a seller of outdoor Telephone pedestals. I plan to install
a DSLAM, post splitters
and associated cross connect gear in this enclosure. Can anyone suggest a
dealer for this sort of gear ?
James H. Edwards
Routing and Security Administrator
At the Santa Fe Office: Internet at Cybe
On Fri, 17 Jun 2005 [EMAIL PROTECTED] wrote:
> > Similar concept, same scaling problems; it just hides the explicit
> routing
> > from the user (as would any modern "peering" system, presumably).
>
> Then you are presuming wrongly. Nowhere in what I wrote have
> I suggested any changes in the e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greetings,
This is to inform you that on 17 June 2005 the IANA has
allocated the following two (2) IPv4 /8 blocks to LACNIC:
189/8, 190/8
and three (3) IPv4 /8 blocks to ARIN:
74/8, 75/8, 76/8
For a full list of IANA IPv4 allocations please see:
Get ready for even more scripkiddies stolen cc signups for ISP and other
services
-- Forwarded message --
Date: Sat, 18 Jun 2005 00:17:27 -0400
From: David Farber <[EMAIL PROTECTED]>
To: Ip ip
Subject: [IP] the mother of all credit card data thefts?
Begin forwarded message
23 matches
Mail list logo
