North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: #nanog: was Re: down

  • From: chip
  • Date: Wed Dec 21 16:04:25 2005
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta;; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=OW4L/FE3VfTWV+B/NFpv/V+lI0jaIXPYR5W6lJaN6px5spUHli5Sio7XDArLTkJJzhMEVZZf/DEQaJ4amC8YNL98m28aj+SMmCZx8xx1OJyiPJ0KqHRaRxY7LjSdGQdbjjdehFtgzXxE/McNZbv2M8Bd6eBNDlBDpDrVvDmkuaE=

On 12/21/05, Albert Meyer <[email protected]> wrote:

I'd like to see a useful #nanog where network operators could chat. I looked
around at the various IRC networks and freenode looks OK. They bind channels to
organizations, so #nanog could be bound to NANOG; this would allow the channel
to be rescued if it got lost. Does anyone agree that this would be a good idea?

Andrew Kirch wrote:
> Hash: SHA1
> william(at) wrote:
>>I think you're confusing nanog-l with #nanog

Actually, looks like #nanog on freenode is already registered as belonging to NANOG:

/msg chanserv info #nanog
>chanserv< info #nanog
-ChanServ-      Channel: #nanog
-ChanServ-      Contact: Duke, last seen: 44 weeks 5 days (13h 25m 33s) ago
-ChanServ-    Alternate: kerx, last seen: 18 weeks 6 days (14h 27m 0s) ago
-ChanServ-   Registered: 2 years 27 weeks 2 days (5h 49m 57s) ago
-ChanServ-        Topic: North American Network Operators Group
-ChanServ-        Email: [email protected]
-ChanServ-      Options: Secure, SecureOps
-ChanServ-    Mode Lock: -s

Just my $.02, your mileage may vary,  batteries not included, etc....