ICANNWatch
 
  Inside ICANNWatch  
Submit Story
Home
Lost Password
Preferences
Site Messages
Top 10 Lists
Latest Comments
Search by topic

Our Mission
ICANN for Beginners
About Us
How To Use This Site
ICANNWatch FAQ
Slash Tech Info
Link to Us
Write to Us

  Useful ICANN sites  
  • ICANN itself
  • Bret Fausett's ICANN Blog
  • Internet Governance Project
  • UN Working Group on Internet Governance
  • Karl Auerbach web site
  • Müller-Maguhn home
  • UDRPinfo.com;
  • UDRPlaw.net;
  • CircleID;
  • LatinoamerICANN Project
  • ICB Tollfree News

  •   At Large Membership and Civil Society Participation in ICANN  
  • icannatlarge.com;
  • Noncommercial Users Constituency of ICANN
  • NAIS Project
  • ICANN At Large Study Committee Final Report
  • ICANN (non)Members page
  • ICANN Membership Election site

  • ICANN-Related Reading
    Browse ICANNWatch by Subject

    Ted Byfied
    - ICANN: Defending Our Precious Bodily Fluids
    - Ushering in Banality
    - ICANN! No U CANN't!
    - roving_reporter
    - DNS: A Short History and a Short Future

    David Farber
    - Overcoming ICANN (PFIR statement)

    A. Michael Froomkin
    - When We Say US™, We Mean It!
    - ICANN 2.0: Meet The New Boss
    - Habermas@ discourse.net: Toward a Critical Theory of Cyberspace
    - ICANN and Anti-Trust (with Mark Lemley)
    - Wrong Turn in Cyberspace: Using ICANN to Route Around the APA & the Constitution (html)
    - Form and Substance in Cyberspace
    - ICANN's "Uniform Dispute Resolution Policy"-- Causes and (Partial) Cures

    Milton Mueller
    - Ruling the Root
    - Success by Default: A New Profile of Domain Name Trademark Disputes under ICANN's UDRP
    - Dancing the Quango: ICANN as International Regulatory Regime
    - Goverments and Country Names: ICANN's Transformation into an Intergovernmental Regime
    - Competing DNS Roots: Creative Destruction or Just Plain Destruction?
    - Rough Justice: A Statistical Assessment of the UDRP
    - ICANN and Internet Governance

    David Post
    - Governing Cyberspace, or Where is James Madison When We Need Him?
    - The 'Unsettled Paradox': The Internet, the State, and the Consent of the Governed

    Jonathan Weinberg
    - Sitefinder and Internet Governance
    - ICANN, Internet Stability, and New Top Level Domains
    - Geeks and Greeks
    - ICANN and the Problem of Legitimacy

    Highlights of the ICANNWatch Archive
    (June 1999 - March 2001)


     
    Verisign/NSI VeriSign Reorganizes Website, and Changes Name of its Registry Division
    posted by michael on Sunday April 06 2003, @06:05PM

    dmehus writes "The company formerly known as VeriSign Global Registry Services ("VGRS"), the Registry Operator for the .COM and .NET gTLDs, has reorganized its corporate structure and website. This includes a name change. The company is now known as VeriSign COM NET Registry ("VCNR"), and operates as a division of VeriSign's Directory Services division. The new website address is www.verisign-grs.com/registrar/."



    "Is it just me, or does VeriSign in general change names a lot? First, Network Solutions was rebranded VeriSign Registrar several years ago. Recently, the Registrar business was spun off as a wholly-owned subsidiary of VeriSign and named Network Solutions once again. Now, VeriSign Global Registry Services is reorganized under a new division of VeriSign and undergoes a name change. Do these people really have nothing better to do?

    In addition, shouldn't /registrar be /registry? I encourage ICANNWatch readers to sound off about the latest round in the VeriSign corporate restructuring arena, VeriSign's mismanagement of the DNS root servers, or other related items."

     
      ICANNWatch Login  
    Nickname:

    Password:

    [ Don't have an account yet? Please create one. It's not required, but as a registered user you can customize the site, post comments with your name, and accumulate reputation points ("karma") that will make your comments more visible. ]

     
      Related Links  
  • VeriSign/NSI
  • dmehus
  • VeriSign Global Registry Services
  • www.verisign-grs.com/registrar /
  • More on Verisign/NSI
  • Also by michael
  •  
    This discussion has been archived. No new comments can be posted.
    VeriSign Reorganizes Website, and Changes Name of its Registry Division | Log in/Create an Account | Top | 7 comments | Search Discussion
    Click this button to post a comment to this story
    The options below will change how the comments display
    Threshold:
    Check box to change your default comment view
    The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
    Verisign
    by dtobias (dan@tobias.name) on Sunday April 06 2003, @07:46PM (#11442)
    User #2967 Info | http://domains.dan.info/
    Well, whatever they're calling their registry arm this week, its domain name, verisign-grs.com, is a Stupid Unnecessary Domain Name™ by my standards... addresses for any Verisign-branded properties could have been more logically established as subdomains of verisign.com, such as registry.verisign.com. There's no logical reason to set up sites at separate domains containing the parent company's name as a subdomain when it would be so much more logical to use the hierarchical structure of DNS as it's always been intended to be used.
    [ Reply to This | Parent ]
    there's actually a BIG reason for this
    by Anonymous on Sunday April 06 2003, @11:36PM (#11448)
    The registry at VeriSign (formerly know as VGRS) has been acting fairly conservatively for the past few years, because of all the rules and regulations it had to deal with as part of the gTLD contract.

    The company was weary and extra-cautious about doing anything to damage that contract, which is pretty much their lifeblood. However, with all of their new non-regulated (by the us gov at least) products, like the ccTLDs that they run, that put them in a pretty worthless postion as far as really milking them for what they are worth.

    The new division is structured so that while the com/net stuff still has to play by the DoC rules, the rest of the registry staff and products can have free-reign over new innovation and whatever else they've been dreaming up for years.

    (Yes, I am formerly of VGRS, and left for this very reason about a year ago. The company was just too careful, and not doing ANYTHING, because they were so trained to the ways of the COM / NET registry.)

    [ Reply to This | Parent ]
    Which division is doing the root zone file?
    by KarlAuerbach on Monday April 07 2003, @07:25AM (#11451)
    User #3243 Info | http://www.cavebear.com/
    Is this new com/net division doing the daily preparation of the root zone file for the root-servers.org[*] system of DNS root servers? Or is that job somewhere else in the corporate structure?

    [*] Given the tacit declaration of independence of the folks comprising http://www.root-servers.org [root-servers.org], it seems appropriate to call the dominant root their root rather than NTIA's or ICANN's.
    [ Reply to This | Parent ]
  • 1 reply beneath your current threshold.

  • Search ICANNWatch.org:


    Privacy Policy: We will not knowingly give out your personal data -- other than identifying your postings in the way you direct by setting your configuration options -- without a court order. All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 by ICANNWatch.Org. This web site was made with Slashcode, a web portal system written in perl. Slashcode is Free Software released under the GNU/GPL license.
    You can syndicate our headlines in .rdf, .rss, or .xml. Domain registration services donated by DomainRegistry.com