hi jeffrey
I personally prefer hobbit over cacti and nagios
http://sourceforge.net/projects/hobbitmon/
http://hobbitmon.sourceforge.net/
Thomas Quilling
NCIR GmbH
Network, Consulting Internet Services
Munich / Germany
[EMAIL PROTECTED]
-Ursprungliche Nachricht-
Von: Rev. Jeffrey
Rev. Jeffrey Paul wrote:
Hi. I've a (theoretically) simple problem and I'm wondering how others
solve it.
Taken one at a time, mos of them are simple. Most of life is like that.
1) Is SNMP the best way to do this? Obviously some of the data (service
checks) will need to be collected
Two years ago I posed the question here about the need for TLDs
(http://www.mcabee.org/lists/nanog/May-06/msg00110.html).
I summerizsed that companies IP (Intellectual Property) guidelines
would never allow domain.org to exist if they owned domain.com
(ibm.org vrs ibm.com).I felt that TLDs
On Thu, Jun 26, 2008 at 04:09:30PM -0400, Jim Popovitch wrote:
Two years ago I posed the question here about the need for TLDs
(http://www.mcabee.org/lists/nanog/May-06/msg00110.html). I
summerizsed that companies IP (Intellectual Property) guidelines
would never allow domain.org to exist if
I hear from my friend's attending ICANN in Paris that there are tons
of business folks who want to scoop up a gTLD. I haven't heard of
anything that will be structured so looks like it will be a blood bath.
Zaid
On Jun 26, 2008, at 1:34 PM, Ken Simpson wrote:
Two years ago I posed the
On Jun 26, 2008, at 1:34 PM, Ken Simpson wrote:
How will ICANN be allocating these?
https://par.icann.org/files/paris/GNSO-gTLD-Update-Paris22jun08.pdf
Regards,
-drc
David Conrad wrote:
On Jun 26, 2008, at 1:34 PM, Ken Simpson wrote:
How will ICANN be allocating these?
https://par.icann.org/files/paris/GNSO-gTLD-Update-Paris22jun08.pdf
and
http://www.circleid.com/posts/86262_launch_of_paris_domain_icann/
and
Our upstream provider has a connection to ATT (12.88.71.13) where I
relatively consistently measure with a RTT of 15 msec, but the next hop
(12.122.112.22) comes in with a RTT of 85 msec. Unless ATT is sending that
traffic over a cable modem or to Europe and back, I can't see a reason why
there
And no, companies *aren't* forced to pay for another domain name just
because a new TLD appears -- they aren't doing it *now*
Oh yes we are
brandon
And no, companies *aren't* forced to pay for another domain name just
because a new TLD appears -- they aren't doing it *now*, by and large,
and thank ghod:
The last time I looked there were a few thousand companies protecting their
intellectual property by using companies like Mark Monitor
On Jun 26, 2008, at 4:07 PM, Martin Hannigan wrote:
And no, companies *aren't* forced to pay for another domain name
just
because a new TLD appears -- they aren't doing it *now*, by and
large,
and thank ghod:
The last time I looked there were a few thousand companies
protecting
Has anyone been able to figure out what it will cost to secure a
completely un-contested tld? I haven't been able to find proposed fees
anywhere. I think it will be a practical necessity for all
organizations to secure their own TLD at the outset, lest someone else
secure it for them and
3. It is somewhat anti-social to do so, but, that has rarely been a
constraint on corporate greed, especially amongst the Intelectual
Property crowd.
It doesn't seem to me to be anti-social behavior to ensure when your
customers mistype your domain as a .net or .de (depending on the
1.Nobody is FORCING them to do so.
scammers, squaters and click collectors
3.It is somewhat anti-social to do so
So are the abusers. If someone is going to it may as
well be us (marginally less evil)
brandon
,
there's a good potential for that kind of an outcome.
This gives an (unofficial) estimate :
http://arstechnica.com/news.ars/post/20080626-confusion-icann-opens-up-pandoras-box-of-new-tlds.html
.confusion: ICANN opens up Pandora's Box of new TLDs
By Jacqui Cheng | Published: June 26
1.Nobody is FORCING them to do so.
scammers, squaters and click collectors
3.It is somewhat anti-social to do so
So are the abusers. If someone is going to it may as
well be us (marginally less evil)
There are probably some variations based on the zone, languages, IDN'ability,
Deep Packet Inspection engine delay. G
On Jun 26, 2008, at 6:51 PM, Frank Bulk wrote:
Our upstream provider has a connection to ATT (12.88.71.13) where I
relatively consistently measure with a RTT of 15 msec, but the next
hop
(12.122.112.22) comes in with a RTT of 85 msec. Unless ATT is
When I asked ATT about the sudden latency jump I see in traceroutes,
they told me it was due to how their MPLS network is setup.
--John
Frank Bulk wrote:
Our upstream provider has a connection to ATT (12.88.71.13) where I
relatively consistently measure with a RTT of 15 msec, but the next hop
On Jun 26, 2008, at 7:58 PM, Ken Simpson wrote:
This gives an (unofficial) estimate :
http://arstechnica.com/news.ars/post/20080626-confusion-icann-opens-up-pandoras-box-of-new-tlds.html
.confusion: ICANN opens up Pandora's Box of new TLDs
By Jacqui Cheng | Published: June 26, 2008 - 12
On that note, it will be very interesting to see who manages to
register the *.sucks TLD, and what they do with it.
Oooh -- dibs on that one. And .some, so you can register awe.some,
trouble.some, and fear.some. And .ous, which would allow humm.ous,
seri.ous, fabul.ous, etc..
Oh - vomit
Ah, but some are ... for trademark or brand protection usually.
I know _one_ company that paid $140k just for domain names related to a
rebranding effort.
/TJ
-Original Message-
From: Brandon Butterworth [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2008 6:59 PM
To:
Did that satisfy you? I guess with MPLS they could tag the traffic and send
it around the country twice and I wouldn't see it at L3.
Frank
-Original Message-
From: John T. Yocum [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2008 7:04 PM
To: [EMAIL PROTECTED]
Cc: nanog list
The explanation I got, was that the latency seen at the first hop was
actually a reply from the last hop in the path across their MPLS
network. Hence, all the following hops had very similar latency.
Personally, I thought it was rather strange for them to do that. And,
I've never seen that
Once upon a time, Ken Simpson [EMAIL PROTECTED] said:
Oooh -- dibs on that one. And .some, so you can register awe.some,
trouble.some, and fear.some. And .ous, which would allow humm.ous,
seri.ous, fabul.ous, etc..
Somebody on /. mentioned .dot, so you could tell someone to go to:
eych
On Thu, 26 Jun 2008, John T. Yocum wrote:
The explanation I got, was that the latency seen at the first hop was
actually a reply from the last hop in the path across their MPLS
network. Hence, all the following hops had very similar latency.
Personally, I thought it was rather strange for
They probably don't propagate TTL w/in their MPLS core. Depending on how
they have MPLS implemented, you may only see 2 hops on the network; the
ingress and egress routers. If the ingress router was in NYC and the egress
in Seattle, you could understandably expect a large jump in RTT.
Not an
Two years ago I posed the question here about the need for TLDs
(http://www.mcabee.org/lists/nanog/May-06/msg00110.html).
This all should have been solved by allowing those who
wanted/applied for TLDs to be granted them back in 1995 when
originally requested :
Once upon a time, Ken Simpson [EMAIL PROTECTED] said:
Oooh -- dibs on that one. And .some, so you can register awe.some,
trouble.some, and fear.some. And .ous, which would allow humm.ous,
seri.ous, fabul.ous, etc..
Somebody on /. mentioned .dot, so you could tell someone to go to:
Thanks for the added information.
Even if their MPLS path went from the midwest (where I'm located) to San
Francisco and then back to St. Louis (where 12.122.112.22 appears to be), I
don't think that accounts for a 70 msec jump in traffic. And I don't think
they would (intentionally) create such
We had a similar situation going from Minneapolis to Kansas City via
Chicago. Normal latency from Minneapolis to Chicago via Level3 MPLS
network is about 14msec RTT. When the the circuit from Minneapolis to
Chicago went out for one reason or another, our MPLS link went from
Minneapolis to
You are welcome to ascribe it to whatever you want. I will note that
very few Non-profit organizations engage in such behavior. Very
few governments do so, either. In fact, absent a corporate profit
motive, this behavior seems very rare.
Given the level of customer service most
Interestingly enough, when I trace from my Cisco router it seems to show
some MPLS labels after the hop of interest (12.88.71.13 to 12.122.112.78,
only 24 msec here!). I'm not sure how our Cisco box derives these from a
foreign network.
Router#traceroute 69.28.226.193
Type escape sequence
On Thu, Jun 26, 2008 at 01:34:22PM -0700, Ken Simpson wrote:
How will ICANN be allocating these? An auction format? It will be a
blood bath otherwise.. And for abuse and spam, this is a nightmare.
There's no doubt this last will happen since it has *already* happened,
as I pointed out in a
Is there any full disclosure clause in ICANN member contracts such
that gifts from, or stock in, a Registrar would be declared?
Since ICANN doesn't have members, no.
R's,
John
Frank Bulk - iNAME wrote:
Just google tbr1.sl9mo.ip.att.net and it's clear that high latency through
that point has occurred before. And guess what kind of customer complained
to me about the latency? A gamer.
you can pay a lot of money for the net propagation anomaly detection
services that
On Jun 26, 2008, at 8:12 PM, Jim Popovitch wrote:
Is there any full disclosure clause in ICANN member contracts such
that gifts from, or stock in, a Registrar would be declared?
Not sure who an ICANN member would be. ICANN as a California
501c(3) has to publish all it's financial details.
On Jun 26, 2008, at 9:01 PM, Jean-François Mezei wrote:
Does anyone know how if the new gTLD system will still give some
veto
power to some people over some domain names that are morally
objectable
to some people ?
See pages 17 - 20 of
At 2008-06-26T02:22-0700, Rev. Jeffrey Paul wrote:
Other stuff we really need to keep an eye on is hardware - redundant
PSU status in our 7204s and Dells, temperatures and voltages
Do yourself a favor, monitor temp in C. Most stuff only does C, people
burn routers if there's a mix of C and F
38 matches
Mail list logo
