ICANN ICANN Email List Archives

[bc-gnso]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [bc-gnso] Who we are

  • To: Susan Kawaguchi <skawaguchi@xxxxxx>
  • Subject: Re: [bc-gnso] Who we are
  • From: "Mike O'Connor" <mike@xxxxxxxxxx>
  • Date: Sun, 12 Dec 2010 22:13:27 -0500

hi all,

first time back on the 'net since the meetings (a great trip to Machu Picchu, 
but no internet access to speak of).  

i'd like to join this bandwagon -- my portfolio is small, but it means a lot to 
me and that's the reason i've been so involved with the endless ongoing series 
of Inter Registrar Transfer Policy Transfer (IRTP) working groups.  

mikey


On Dec 10, 2010, at 4:30 PM, Susan Kawaguchi wrote:

> I agree with Jonathan domain portfolio management issues are critical to most 
> businesses I think the BC focuses on some of the issues that impact 
> management such as WHOIS, registrar compliance with the RAA, registrar and 
> registry security etc.   I know there are other issues I face with managing a 
> portfolio that are not addressed in the BC.
>  
> From: owner-bc-gnso@xxxxxxxxx [mailto:owner-bc-gnso@xxxxxxxxx] On Behalf Of 
> Matkowsky, Jonathan
> Sent: Friday, December 10, 2010 12:22 PM
> To: marilynscade@xxxxxxxxxxx; philip.sheppard@xxxxxx; john@xxxxxxxxxxxxxxxxxxx
> Cc: bc-gnso@xxxxxxxxx
> Subject: Re: [bc-gnso] Who we are
>  
> I think domain portfolio management is one of many important business 
> concerns.
>  
> From: owner-bc-gnso@xxxxxxxxx <owner-bc-gnso@xxxxxxxxx> 
> To: Philip Sheppard <philip.sheppard@xxxxxx>; John Berard 
> <john@xxxxxxxxxxxxxxxxxxx> 
> Cc: bc - GNSO list <bc-gnso@xxxxxxxxx> 
> Sent: Thu Dec 09 12:18:00 2010
> Subject: RE: [bc-gnso] Who we are
> 
> I agree, domain name portfolio management isn't a BC issue per se./I think 
> John is 'brainstorming' and we will just gather ideas and actually discuss 
> different ideas later/I would add SSR, for instance.
> ....   and yes, I will put in a 
> discussion about accountability of officers/councilors, including the duties 
> to participate, consult, etc. 
>  
>  
> 
> 
> 
> > Date: Thu, 9 Dec 2010 19:27:27 +0100
> > Subject: Re: [bc-gnso] Who we are
> > From: philip.sheppard@xxxxxx
> > To: john@xxxxxxxxxxxxxxxxxxx
> > CC: marilynscade@xxxxxxxxxxx; bc-gnso@xxxxxxxxx
> > 
> > 
> > I hope the proposal that the Bc mission is rewritten to promite domain
> > portflio management was a joke.
> > 
> > Here's another one. What exactly is our councillor recall procedure ????
> > 
> > Philip
> > 
> > 
> > > Marilyn,
> > > As we consider a rewrite of the Business Constituency's mission to better
> > > reflect who we are, we might begin with a review of the self-descriptors
> > > used in the round of introductions at our meeting with the new ICANN
> > > finance team. The characteristics fell in two bucket:
> > > To prevent:
> > > FraudBrand abuseMalwarePhishingCybersquattingBarriers to e.commerce
> > >
> > > To promote:
> > > Domain portfolio managementTechnology architectureRisk
> > > managementInnovationEfficiencySecurityEasier e.commerceIP rightsTrademarks
> > > From this, we can build a case for membership in the BC that may resonate
> > > with companies.
> > > Just some raw material for consideration.
> > > Berard
> > >
> > 
> >
> [THE INFORMATION CONTAINED IN THIS E-MAIL MESSAGE IS INTENDED ONLY FOR THE 
> USE OF THE INDIVIDUAL OR ENTITY NAMED ABOVE.  IF THE READER OF THIS MESSAGE 
> IS NOT THE INTENDED RECIPIENT, OR IS NOT THE EMPLOYEE OR AGENT RESPONSIBLE 
> FOR DELIVERING IT TO THE INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY 
> DISSEMINATION, DISTRIBUTION OR COPYING OF THIS COMMUNICATION IS STRICTLY 
> PROHIBITED.  IF YOU HAVE RECEIVED THIS MESSAGE IN ERROR, PLEASE IMMEDIATELY 
> NOTIFY US BY TELEPHONE OR REPLY BY E-MAIL AND THEN PROMPTLY DELETE THE 
> MESSAGE.  THANK YOU.]

- - - - - - - - -
phone   651-647-6109  
fax             866-280-2356  
web     http://www.haven2.com
handle  OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy