keep more strictly to the schedule- Next NANOG in Vancouver
With the current financial conditions, the cost of the accomdations
should be considered. Although our host negotiated a room rate, it still
was a little overboard.
Wireless worked well. An smtp server should have been provided.
Wireless network setup.
Wireless connectivity was horrible and came up too late.should have
been tested and operational a day or two earlier to play it safe.no high-speed
internet access in the rooms. This should be a requirement for future nanog's,
and ideally made free.
Wireless connectivity to the bar
Wireless connection was dandy.
Wireless access took a while to become stable but did eventually work.
Well organized. A table for conference announcements, glossies, etc,
would be useful.
We need hotel rooms with connectivity. Dial up is evil.
Very good meeting
Venue was good, plenty of space, etc. Beer and Gear room is too hot
- this seems quite common at other venues. Sudden influx of a lot of people
talking creates so much hot-air that the a/c cannot cope? :-) Maybe the
room needs "pre-cooling" first? The room rate at this hotel was quite pricey.
Connectivity was a bit flakey on the Sunday, but seemed to improve. It
seems that multicast on the wireless seems to be quite antisocial - we
had the same problems in Oakland, if you recall...There was some really
good operational content at this meeting... stuff that is of real practical
use, and well balanced. Not too much focus on one topic (like the security/DDoS
overkills we have seen).Thinking about future locations, Seattle would
be great (maybe get MSFT to host?), and we should probably pay Canada a
visit soon!
Using a low number of rooms was helpful to keeping energy and
topics focused.
This is quite an experience for a first time attendee. Great organization,
plenty of coffee, cookies etc. Starts and stops on time. Keep up the good
work
This hotel has some issues handling the load of people checking
in. The presentations were done fairly well. The topics were much better
than last. Happy not to see DDOS.
There were some really nice hotels on the ocean front which would
make nice venues for subsequent NANOGs in Miami!:-)Thank you for not DDOS'ing
us with more DDOS slides this time! Topics were good. Also, there was a
theater in this hotel. Could have had some fun running some movies later
into the night.
The wireless network was flaky. It was largely unavailable in
the bar, and oscillated so regularly between minimal strength and zero
strength elsewhere that I was not actually able to use it for anything
much. The hotel was very expensive, although the facilities were certainly
adequate for the meeting.
The speakers & topics on the whole were excellent and of interest.
The seating arrangement was fabulous. I suppose it's expensive
to spend space on tables and power instead of densely packed chairs, but
IMO it's worth it. The tables and less-dense seating make it much easier
to follow the presentations instead of constantly trying to get less uncomfortable.
The room layout was awesome. Having the tables with power available
for everyone was great along with the ample displays at the head of the
room
The program, logistics (with the obvious exception of the A-N
registration snafu), and the hotel worked well.The network improved over
the course of the conference but was - especially the wireless net - very
flaky in the earlier part of the conference.
The network and the room setup worked well. Changing the agenda
at the end and extending the meeting 30 minutes was not good. I had to
leave at 3 p.m to catch my flight. Now that we have to be at the airport
2 hours before a flight, it makes it difficult to stay late and to catch
a transcontinental flight. Very interesting talks at the end...I guess
I'll watch them on video. Also, nice shirts this time!Thanks.
The meeting continues to be run very well, and the flexability
of the agenda and the speakers enables the meeting to adapt. That makes
NANOG what it is.
The infrastructure tours were great.Having lunch spots within
walking distance was also a bonus.The hotel was extremely expensive given
how many people are now self-funding this conference.Please consider the
cost for parking/hotel next time and perhaps a lower-scale location is
in order.
The hotel staff was somewhat unfriendly, although they did make
an effort to satisfy us after we made a stink.Terramark did a good job.It
would have been nice if the entire hotel, or a block of the residential
rooms had been wireless accesible.A la Scottsdale.No complaints about this
Nanog, or the venue, or supporting players.
The Hotel price was a bit steep.
The food was very good, especially at theBeer 'n Gear
The combination of wired and wirelessaccess was good.
Thank you FINALLY for all tables.How about 100% ethernet connections
so we can securly check our mail and not have people like Adam R. and the
other 50 people sniffing the wireless to get my password when my vpn dies
and my mail client re-checks for mail.
Susan was well tamed this year.=>Everything else was well
Sunday organization has to be improved, especially information
and new assistants guidance.
Some of the non-native english speakers were a bit difficult to
understand.Perhaps coaching for these speakers to consciously speak more
slowly.It is a tough problem I realize.
Seating:tables work better than chairs.I liked this meeting's
setup.
Seating worked well.Tables for everyone was a good thing.The network
connectivity was okay, not particularly good or particularly bad.Reasonably
good set of talks this time.
schedule changes should NOT be communicated verbally. a transparency
of the changes in schedule would be better & make it so everyone understands
Room could have been a bit warmer.The wireless worked well this
time.
Realy nice facility and food!Liked the agenda and speakers.Wireless
was kinda flakey, but it was free!Internet access was really good on wires,
and well appreciated.We had to do some work on Monday night, and the connectivity
was good then.
publish in agenda which meals are included (sponsored) and which
are on our own...
Provide suggestions to presentation creators to avoid colors which
do not show up well as projected images (i.e light green, yellow).Short
online survey per tutorial.
Program was very good on Monday. Tuesday is still on going.
People seemed a bit unforgiving about the hiccupsin wireless connectivity.Personally
I think complainingsounds like a cry to volunteer so I willstay silent.
Opportunities to meet with fellowvendors and customers was most
usefulto me.Having a couple of parallel paths oftopic areas. For me, I
was more interestedin core routing issues, so some of thepresentations
were of less interest.
Only suggestion would be aless expensive hotel.Even with the host's
help,this was expensive.
Not having $200 a night room rates.
No useful suggestions, I'm afraid.It seemedto work well, overall.
No lunch?!? Whats up with that?Good wireless, network.
nice breakfastsnie location
Network access
Net connectivity on sunday was poor. Would have been great if
net connectivity could have been extended for greater distances.
Multicast deployment (engineering)was great this time - thank
you Eric!
Move the Sun-Tues format to Mon-Wed or Wed-Fri
Most everything.Things ran really smooth.
More infor push to the attendees. Those who have attended many
know what to expect, not the newbies.For example, no advertising of terminal
reoom to my knowledge
More detail presentation content and info
more bof's and maybe a beer hour on sunday night, was a great
opportunity to meet one folks especially for a first time attendee, wished
it would have happened on Sunday night.
Also had problem with name tags, seems silly but would have been
easier to identify folks if their had their names, but especially the names
of their companies bigger.there were folks i wanted to meet, but had trouble
identifing them
missed having working wireless on Sunday, but it worked well after
that.tutorial screen was too lowtoo cold at times in large roomexpected
lunch but was disappointed
make sure the speakers are aware ofthe presence of non englih
native attendees
Long and wide classroom setting with 4 screens works much better
than Arizona narrow and deep. More comfortable more spacious
Wireless network/terminal room should be Fully operational/Fully
Tested in the common areas no later than 12Noon Saturday.
This was by far the most expensive NANOG I have attended, I know
several folks, John Brown, Suzanne Woolfe, Steve Rubin to name a few who
are regular attenders that felt that $192.00/day/room was way to high and
did not attend due to the costs (cutbacks in company travel ect).Dont get
me wrong, it was a great hotel, however expensive for this group.
One last scheduling thought. When you schedule on the east coast
or west coast, remember that the airline flights leave earlyt or late.
so in otder to make the last flight of the day from MIA to LAX
you have to leave the hotel no later than 3PM or you have to leave on the
12 midnight flight. Like wise on the west coast your flights from LAX to
WAS leave by 3PM to arrive at midnight or leave a midnight to arrive 7AM
the next morning.
I lucked out this time and got a 6:00PM flight west, however most
nanog's i have had to leave around 12-1Pm just to make a convieninet flight.
If you extend the last day many people cannot hear both the conference
and make their planes. Most of us came in on saturday becasue of a saturday
night stay required so perhaps an earlier start on Sunday might help the
schedule a little.Ralph
Location was great for winter.More "networking/peering" opportunities
would be nice.
Liked the emphasis on routing and on analysis of data / performance
in several sessions.
Letting the meeting run late is a BAD idea! Either end the meeting
at noon so people can leave the same day, OR schedule 2 full days so that
people will simply stay tuesday nite and fly out weds morning.
It's been good all round.
it would be good if useful time is not spent on bashing microsoft/qos
etc.
It went smooth as usual.
It can be very difficult to figure out what people from Europe
who speak at the conference are saying.
Internet access worked well, all the speakers and presentation
were well done.excellent time control.keep up the good work.
initial wireless connectivity problems
In my point of view, everything worked well.
improve the wireless connectivity, get it set up earlier.
I wasn't able to use IPv6 on Wireless...It seems router existed,
but he didn'tannounce RA.$ ping6 ff02::2%eth164 bytes from fe80::205:5eff:feda:4610%eth1:
icmp_seq=0 hops=64 time=3829.000 usec64 bytes from fe80::205:5eff:feda:4610%eth1:
icmp_seq=1 hops=64 time=5403.000 usec64 bytes from fe80::205:5eff:feda:4610%eth1:
icmp_seq=3 hops=64 time=4719.000 usec
I thought the presentations on the first day were great. I wouldn't
change a thing.
I think the overall organization that went into putting this together
was great.Being my First NANOG, I didn't really know anyone attending.Thus,
I found the overallsocial atmosphere a big downfall.As with most techies,
we usually lack some degree ofsocial skills.However I would of hoped that
a group of all techies could socialize ormingle outside their circles of
friends.This wasn't the case as I saw it.There werevery few people that
I found to actually want to meet new people.I attempted severaltimes to
start or join in on conversations, only to get the cold shoulder by many.Ifound
quite a few people with chips on their shoulders due to their status (name),
the companythey work for, or just because they assume they are so much
smarter than everyone else.I was however to find a few people that were
willing to socialize with anyone, regardless ofwho they were,
where they worked, or what they did.I have only been a subscriber
of NANOGfor about 4-6 months, and have learned a great deal from some postings.I
found the overallmaterial for the conference very beneficial as well.I
was hoping that by attending thisNANOG I could meet some good and key people
in our industry and show face for my company, as wellas myself.This unfortunately
didn't prove to be a very accepting environment.
I liked the fact there were four screens, and a lot of ethernet.The
wireless SUCKED on Sunday - AS USUAL. There has to be SOMEONE in NANOG
who can do 802.11 better than that.(Hell, I can do it better than they
did.)
I liked that the presentations seemed to be from operators rather
than thinly disguised vendor presentations (a problem with nanog 23)
I know a lot of people who, due to recent travel and expense cutbacks,
are paying for NANOG out of pocket on a regular basis.Some of these people
did not come this time, in large part, due to the $200/night hotel room.I
would suggest keeping it closer to the $100 mark.
I have no recommendations for improvement, I thought it went well.
I found that all my open SMTP mail relayswere closed to your network
so a SMTP mailreloay would be nice. I tried to use one ofthe LINUX systems
but it did not work all Igot were timeouts when I tried to send mailto
it. It should have worked out of the box.
I already did one form earlier. Here's some extras...The schedule
change on Tuesday wasn't handled all that well. I understand changes may
be needed, but from the number of people who either no-showed in the afternoon,
or left early - it obviously caused people problems with their flights.Also,
with the changes in airport security, it's making it harder for people
to get late afternoon/evening flights, because of fear of long check-in/security
lines. Many airlines have cut back on their evening/night flights too,
meaning earlier departures.Either finish the last day no later than 1pm,
or extend the meeting to run all day - meaning an extra night's stay.
Good Points:1. Very well organized.2. You had enough wireless
cards for everyone, which made life REAL simple.3. Ofcourse the presentations
and the technical material was really useful and interesting.improvement:cant
think of any.
Good mix of presentations.Presentations were well done.Excellent
catering.As always, there could be more vendors at the beer and gear, but
there was a nice mix this time.The hotel is too expensive and not near
(walking distance) anything interesting - I would never stay in this hotel
(on my own nickel) to extend my visit.There are no less expensive hotels
in the immediate vicinity.Otherwise, good choice of location.And it's always
nice to have one like Miami with good air access.If you'd like a warm location
with good air access, how about San Juan (if we can get the bandwidth)?Wireless
net worked well once we got the bugs out - kudos!Good web page for this
meeting! (but should've mentioned the supershuttle as a way to get to the
hotel).
good hotel...agenda...speakershow about a nice polo shirt? it
could be a prepaid surcharge..no T-shirt if one chooses the polo shirt
good choice of topics.More presentations from Operators on practices
and problems, implementation experiences would be great.
good choice of topics (most closely aligned with my interests)
Give access to the powerpoint presentations of the PANELMoreover,
why don't you give access to all slides the day before presentation in
order to review it before it is presented; it could improve the level of
understanding and the number of comments !
get hotels with free ethernet to rooms or make it easier for the
growing DIY crowd to get wireless to the floors. This ESPECIALLY means
prearranging hotel cooperation and then making the resources (access to
shaftways and rooftops, etc) known and available to folks needing them.
faster highspeed internet, select hotels that also have hs internet
in room
Everything worked well
Everything was fantastic!Great coordination, planning, organization,
and extra curricular activites - especially enjoyed the eat & linger
with the vendors in the Bay Front room.The last NANOG I attended was in
1997.I was a little afraid to come back (based on that experience).Today's
NANOG compared to then is AWESOME.Dave
Everything seemed okay, just hate the schedule changes.
Even with subsidy, the hotel was very expensive.
Dave Ward's talk was timely.The three CAIDA talks were excellent
and useful.Cengiz's talk on QWest was also quite useful.It is interesting
watching MPLS roll out, though most of the talks had less meat than I would
like.The Hotel was quite expensive, and therestaurant was overpriced.
Data-related talks were really good:CAIDA stuff, Evi, Cengiz,
Olaf.Jeb's talk on the whys and whereforesof peering was also a very useful
review.
Better wlan coverage would be nice. (coverage in the rooms would
be very cool)Everything else seemed good.
Better announcement and web posting ofschedule changes for the
talks (for example,what happened Tuesday).
Best technical talks yet
As a non-operational atendee I found the subjects interresting
and think that the information provided were of value for me.
again, very good room layout with screen distribution and technical
operation support.once the wireless network got up and stable life was
good.
[this is my 2nd survey as i had more iwanted to say.]suggestion:
extend the survy to the talks- so that we can judge each talk.thismight
help to get some idea of what topicspeople find more or less interesting.ditto
speakers.always give html links to the presentations.[not all of us can
deal with powerpoint.]
I also liked the wide main conference room, instead of the long
one that is usually used.Wireless worked much better than last NANOG, but
still needs work, as it didn't seem to be stable until late Sunday. It
seems that whoever sets up the network has the same problems as everyone
else.. maybe some guidelines for successful setup would be appropriate.Provisions
for internet access in the hotel rooms would also be nice. Some 7th floor
people had to set up a PTP 802.11b network with GlobalNAPs across the street
to avoid the hellacious long-distance dialup charges to check email.Hotel
room rate was a bit steep, especially considering lack of internet access.Miami
was an excellent location.. The extra-curricular tour of NOTA was also
interesting.Vixie's normal party was sorely missed.
better wireless coverage
Inter-Domain
Comments:
1:30
| Good level of detail regarding operational experiences
instrumenting POPs |
| Good quality presentation. Interesting material for intermediate
audience. |
| Good topic but needed more detail, examples, case studies |
| Good, but need more "hands-on" detail |
| More case study detail would be helpful. |
| My opinion is biased :) I ran the inter-domain
traffic engineering tutorial with josh. |
| Spoke to fast. |
| The level of detail was intentionally low, so, if the question
is "was the level of detail high?", then no, but if the question is "was
the level of detail appropriate?", then yes. |
| Too short, nothing new. |
IP Routing Policy
Comments:
3:30
Missed part of tutorial because of delays
in hotel registration.
|
Good quality presentation of best practices. Stimulated
thought and practical application.
|
Good way to follow up a trip to the keys, too bad it wasn't
scheduled a little later to give us more time to explore.
|
Great presentation!
|
More examples of where policy has been effectively deployed
would be good. A discussion of monitoring of conformance of actual
routing to policy would have useful.
|
Very good speaker
|
IS-IS
Comments:
1:30
| The speaker was obviously very familiar
with Cisco's ISIS implementation. Although the talk was targetted
at 'intermediate' it changed topics too quickly follow. |
| He could have put some juniper examples,
it was too cisco oriented. Majority of the talk was on
features operators did not use. For example route leaking is only needed
for 2 level ISIS, or forwarding adjacencies are needed for MPLS.
I think OSPF is better for the general NANOG attendees. ISIS is only used
by the large ISPs whose staff probably already know these features. |
Route Registry
Comments:
Chris Frazier deserves and Oscar for his outstanding performance!
:^)
Bug! I attended both the UWho BoF and the RR BoF (one
after the other) and the html form only lets me pick one!
UWho
BOF
Comments:
I attended both the uwho and the irr bof
Not so much a "speaker" BOF, but a community input request.
It was useful. Note that you could attend both UWHO and RR BOF, and
that your
form only allows us to check one
NAP Update
Comments:
good to cover NAP stuff! yes yes!
Definitely needed more preparation from the various speakes.
I had planned to attend the Benchmarking BOF that was listed on the
web-site agenda. It was very close to my project objectives.
Unfortunately this was not held :-(
I was hoping for another "we want to peer, please peer with us" presentation
too for the companies, like it was with Bill Norton at NANOG23.
I would have found it far more helpful if it was the standard peering
bof
Interesting discussions. Useful crowd. Good moderator. :)
Microphones need to be made available in the BOFs like the general sessions
at the start of the BOF. Not as an afterthought.
NAP, exchange, peering, and interconnection are a primary motivation
for my attending
Need to bring back the peering bof
Please have more like this. The Q&A was refreshing.
This form only let's me comment on 1 BoF, yet there were
two sets BoFs. Suggest that you moddify this to be as
the tutorials section is set up. The 2nd was Route Registry
and the same scores apply.
timing was such that route registry BOF was also attended. You preclude
clicking both. It also was OK, but sadly few attended.
we need more of this. it just needs a better list of agenda topics and
operator issues.
Multicast
Comments:
3:30
Best Multicast Overview I have Ever
Seen
|
cookbook multicast tutorial sessions
would be good to consider in the future.
|
Great talk. I'm very familiar with the area and didn't get anything
new, but Greg is a very entertaining presenter.
|
lots of good questions, high level of audience engagement.
|
Nice BOF. The speaker was very knowledgeable, but needs to slow down
his speech.
|
Super super super!
|
This was actually more than excellent.
|
This was labelled "deploying ip multicast" and it should've been labelled
"ip multicast tutorial/introduction"
|
Suggestions
for future NANOG presentations?
Where did the peering BoF go?The NAP BoF was good,
but peering is better.CDNs would be good.OC192+ routing would be nice.IPSEC
stuff.SSL + virtual hosting, stuff like that.
We need to get the equipment vendors to engage more in the meetings
- over and above the beer-and-gear, which is mostly marketing/product management
people, who fly in on Monday afternoon, and are gone again by Tuesday.Getting
vendors to engage in the sessions and the BoFs may help them better understand
our needs.Could Merit do something to encourage the vendors who aren't
well represented to send people, or encourage (technical, marketing-free)
speaking opportunities for them?
vpn deployment experiences (mpls and non mpls)
Voice over IP in a large scale deployment.
Virtual RoutingGMPLS
Use of one speaker's laptop is very good.
Update on efforts like Multi6 would be useful.A lot of folks are
waiting on IPv6, and multihoming seems to be both a driver for going to
IPv6 and a restriction.Multi6 seems to be a really big issue here.
Trobleshoting in internet, for where are going my traffic and
why.
Topics:MeasurementMeasurementMeasurementEconomics of real network
operation (eg Jeb's talk)I think the topic of Route Control has been brought
up; I am, of course, in favor, since it's my space.Vendors include RouteScience
(me), Sockeye, Proficient, netVMG, Opnix.
There are some missing steps for those new in peering.We have
peering 101 covered! There are people that show presentations on lots of
statistics, however, there has never been anything for those who are learning
what peering is about that makes finding this data easy.Something like
"Graduating peering 101, now onto implemention realities and why I should
peer with you"I will send more details in the call for presentations.
Settlement- Inter-domain quality- IPv6- Security
Secure BGP
Protection & Reliability of router/mpls functions:line-cardcontrol-modulescheduling-logicpeering-sessionsAlternative
to NSF via stateful protection.
Practical application is always good. NOC Theory and Practice,
Automation of configuration of network devices, and creating routing policy
guidelines were all directly applicable and useful.
Overviews of the State of the Network in other countries (e.g.
Australisia, Asia, central Europe, etc).Self-consistency audits for IP
networks (how to do configuration management where the configuration database
is the network).
o something stats-related from K Claffyo something operations-related
from Sean Donelan, Matt Ringel, and Tim Browno Randy Bush
no, you're doing a good job
nah
My associate would very much like an acronym dictionary.
More security related topics, More IPSEC, DNSSEC
More routing topics! less MPLS and DDOS!
More moderated panels.The speakers took their slides seriously
and made sure they had content vs. fluff.I would also like to recommend
we have another NANOG outside the borders of the United States.Toronto
(or Vancouver) would be good.Bell Nexxia, Shaw Fiber, Telus, etc. could
host the conference.If going South of the border try TelMex.
More Layer 2 VPNs and also deployments of Metro networks by ISPs.
More IPV6 operational input, configureation/practical applications/problems
solutions.
More dynamic presentations/speakers.
More "hands on" bgp policy, implimentation examples. Also, real
tools and techniques that can be used immediately.Host next NANOG in Vancouver
BC or other NW location (Portland, Seattle).
Moderated exchange-point panel went well, I'd like to see that
again periodically.
looks good, no suggestions.
location: VANCOUVER topics: continue with NAP topics. more regular
updates are needed. it was pathetic that MAE-E FDDI's closure was NEVER
discussed in a presentation, panel or bof thanks for a REAL agenda this
time. last 3 or 4 nanogs have been far too focused on DoS attacks
Like to see one on which providers produce more/less traffic on
the NET.
Lessons from Internet II/Abilene that will shape the future of
the commercial Internet
IPv6
IPv6
Interested in hearing from a tier 2 network engineer and how they
control their traffic through transit providers and peers.
I would like to see more on:Monitoring connectivity and proactive
notification to customer base during network events. The events should
be ticket system that opens/closes tickets with customer information and
inculude resolution codes when issues are resolved.Most of today's solutions
seem way too expensive often requiring a never ending use of consultants.Steps
that are being taken to improve the user interface to Cisco devices.
I like the presentations on measurement.
How will the underground movement to create a wireless 802.11
infrastructure be embraced by the Internet community. Is this an opportunity?
How not to screw up the wireless at NANOG.
govenet/homeland security/changes innational infrastructure
GMPLS...overview of standards
empirical data on hardware, software, and service provider stability.
Dynamic provisioning and TE
Convergence progress - large ISPs moving to the netgen IX (Equinix),
and the resulting effect at the public IX/NAPs.
Configuration management of large scale networksFlat rate vs measured
rate service models.Is there a CDR (call detail record) for IP.
Better setup instructions for wireless access.
A session on peering theory and practice as pertaining to content
delivery networks, as those decisions are different than the ones made
by backbones looking to peer with one another.
A presentation on merging ASes would be good. Process; lessons
learned, etc.
|
Comment
|
E-mail from Survey
|
|
| we will contact you |
[annonymous] |
192.35.165.171 |
| We will consider it. Contact Mike Duckett, BellSouth.net.
|
[annonymous] |
205.152.6.240 |
| Vincent J. Bono (617) 507-5430 |
|
192.35.166.116 |
This yes is a maybe, Please contact me to discuss the location, cost
and time commitment.
If possible we should talk before the meeting ends.
George J. Cornachini 212-424-2961 917-478-4209 |
[annonymous] |
192.35.167.61 |
| This would probably not work this year - due to economic issues. |
|
192.35.167.103 |
| Telefonica peering comitee |
|
192.35.164.176 |
| Sorry, don't know actually |
[annonymous] |
64.102.254.33 |
| possibly. Contain laurie martinez, |
[annonymous] |
207.17.136.130 |
| Perhaps -- would need to know more about what is required.
We're in Portland OR. |
|
192.35.165.79 |
| Patrick W. Gilmore |
|
192.35.166.225 |
| Not my decision :-) |
terwin@foundrynet.com |
192.35.165.185 |
| Myself. David Reoch 801-495-8200 |
|
192.35.167.221 |
| myself, but not for a while; we need some time to grow and mature before
we will be ready |
|
192.35.164.39 |
| maybe, what does it involve? |
|
209.220.53.114 |
| Jere Retzer Probably not this year, but quite possibly next |
|
192.35.164.162 |
| Greg Harp - |
|
216.61.64.84 |
| Dave Meyer () |
[annonymous] |
192.35.166.201 |
| Carey Parker,
|
|
192.35.165.150 |
| Al Rubenstein
|
[annonymous] |
207.99.116.193 |