North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
Re: improving puck contact db
- From: Peter Cohen
- Date: Tue Jan 31 22:28:59 2006
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CiGRDRT/8YnYz5TBSAyoNSzWXqqc/sb5W4eZJtnY+QVOrAd8c4foM7z71gyDsBco9jn/pCnx+riMnuJAGgBQm7SjZzAndvzbxseo8oQZZAxFgs6RfhmY76E27jroY3aBhK3lrSjHvt7IdPdABV2QoQ6wJJwYOUufXjN/1dZ5EzY=
On 1/31/06, Jared Mauch <firstname.lastname@example.org> wrote:
> I'm open to suggestions of how I can improve the puck
> contact db pages for various isps/nocs/teams.
> isp name
> noc email
> cust svc#
> cust svc email
> security ph#
> security email
> with the various toll-free and direct numbers
> available, including aim/y!/jabber/whatnot gateways that reach
> some centralized noc operator too?
> is the concern about putting data there an access/trust
> issue? perhaps some sort of registered user foo can be done where
> people can assign trust for their org (eg: hi, i'm AOL, it's ok to share
> my postmaster and noc data with anyone, but the security number only
> with people who i set a trust/access level on).
> think the social networking foo (orkut, etc..)
> just some random ideas, since i wrote the cgi foo for
> the noc stuff years ago and it needs to be updated.
> - jared
> Jared Mauch | pgp key available via finger from email@example.com
> clue++; | http://puck.nether.net/~jared/ My statements are only mine.
Huge fan of the puck site, what about some colaboration with that
wonder of db/php Richard Steenbergen and the www.peeringdb.com site ?
I find useful information from both of them.