Sedo Reports $1,3 Million in Domain Name Sales ! FootMarseille.com Topped Sedo’s Weekly Sales List at 25,000 EUR

FootMarseille.com topped Sedo’s weekly sales chart at 25,000 EUR. Highlights also include Detal.ca, leading the ccTLD category at $22,600 and BestCasino.info ,leading the “Other” category at $7,050.

 

Other notable domain name sales include :

.COM

teamshirt.com     23,000     USD
xfj.com     17,000     USD
1357.com     15,000     USD
amame.com     15,000     EUR
mybuild.com     10,800     USD
filespace.com     10,000     USD
storq.com     10,000     USD
eaco.com     10,000     EUR
easysquare.com     9,999     USD
geneba.com     7,000     USD
myoffer.com     7,000     USD
froogler.com     5,999     USD
gamebaby.com     5,900     USD
okcard.com     5,350     USD
benchmarkapartments.com     5,000     USD
marketingunited.com     5,000     USD
vitasonline.com     5,000     USD
coinzone.com     5,000     USD
aroragroup.com     5,000     USD
geossl.com     5,000     USD
jobinsider.com     5,000     USD
7726.com     5,000     USD
findescorts.com     4,999     USD
sugarplum.com     4,500     USD
cartage.com     4,000     USD
clios.com     4,000     USD
alchemyai.com     3,900     EUR
aventon.com     3,800     EUR
hkcd.com     3,600     USD
backies.com     3,600     USD
doctorcoach.com     3,550     USD
reutech.com     3,500     USD
cookacademy.com     3,500     USD
ringtel.com     3,216     USD
curemed.com     3,200     USD
andpay.com     3,000     USD
sebir.com     3,000     USD
nationalpestcontrol.com     2,999     USD
wellensiek.com     2,800     EUR
endetail.com     2,800     EUR
affiliatepolice.com     2,795     USD
whatsintown.com     2,595     USD
tuneage.com     2,500     USD
ovronnaz.com     2,500     USD
crowdventure.com     2,500     USD
texasbankruptcy.com     2,500     USD
forex-academy.com     2,500     USD
yoursport.com     2,500     USD
nudeandnaked.com     2,500     USD
funmiiyanda.com     2,500     USD

ccTLD

laptopscreen.co.uk     13,600     USD
offertes.nl     11,000     EUR
hi.tv     10,000     USD
dao.cn     6,800     EUR
wid.fr     6,500     EUR
onpage.ru     5,000     EUR
badoo.mx     4,800     EUR
nextdirect.cl     4,500     GBP
ignition.co     3,500     USD
peel.in     3,500     USD
gametwist.com.br     3,000     EUR
rev.me     3,000     USD
serverbilliger.de     3,000     EUR
stadtnetz.de     2,499     EUR
golftest.de     2,100     EUR
pferdo.de     2,000     EUR
sunday.fr     2,000     EUR
stempelo.de     2,000     EUR
localoffers.co.uk     2,000     USD
rolic.cn     1,999     USD
debtguard.co.uk     1,950     GBP
pns.co.za     1,750     USD
cloak.me     1,500     USD
loyaltycard.co.uk     1,500     GBP
gtd.eu     1,400     EUR
qay.de     1,300     EUR
chukoh.cn     1,200     USD
horeca.gr     1,200     EUR
schoonmaakpersoneel.nl     1,100     EUR
bauzaun24.de     1,099     EUR
hacker-pschorr.cn     1,000     USD
chimpanzee.co     1,000     USD
albemarle.fr     1,000     USD
valentino.com.es     1,000     EUR

Other

eip.org     4,599     USD
bestonlinecasino.info     2,900     USD
alfransi.net     2,500     USD
opt-in.net     2,359     EUR
herbshop.net     2,300     USD
bap.info     1,600     EUR
xbb.net     1,500     USD
steuersoftware.net     1,200     USD
euromillionen.net     1,000     USD
cinvizesi.net     1,000     USD
glaeser.net     750     USD
isse.org     700     USD

Check out Sedo.com for more information .

ICANN : Publication of One World Trust Report on ICANN Accountability Benchmarks and Metrics

One World Trust (OWT) has submitted an independent assessment and measurement recommendations to the Internet Corporation for Assigned Names and Numbers (ICANN).

OWT was contracted to assist with developing a means to measure ICANN’s accountability performance over time, as well as relative to other (broadly) similar organizations. This effort is part of ICANN’s commitment to accountability and continuous improvement, and also responds to Accountability and Transparency Review Team advice. These measures also will:

    Illustrate and communicate how ICANN is meeting its global accountability obligations;
    Help ICANN benefit from learning how other international organizations are accountable to their stakeholders; and
    Continue to enhance ICANN’s accountability (and transparency, which is viewed as a part of accountability).

The implementation of the accountability framework, metrics and benchmarks is an important step in evolving ICANN’s performance measurement discipline. This process is aligned with broader measurements of performance being implemented as part of ICANN’s Management System to support continuous improvement.

One World Trust is an independent, UK-based organization that conducts research, develops recommendations and advocates for reform to make policy and decision-making processes in global governance more accountable to the people they affect.
SUMMARY

OWT’s “ICANN Accountability and Transparency Metrics and Benchmarks: Consultancy Report,” is available here [PDF, 752 KB]. Their work consisted of several elements:

    Review of the accountability principles promoted by four international accountability standard setting initiatives;

    Qualitative analysis of ICANN’s policies and practices through desk research and interviews with key stakeholders and staff (list available in Appendix C), for insight into ICANN’s current accountability strengths and challenges, as well as gathering ideas about how the metrics and benchmarks might work; and

    Analysis of the accountability policies and practices of three multi-stakeholder, international non-profit organizations, to establish their current level of accountability in comparison with ICANN, and identify useful learning opportunities.

OWT provided a framework and practical suggestions for metrics within each of the six dimensions of Accountability (see Accountability Framework below), and recommended that ICANN staff determine specific metrics, including appropriate targets. This work will be integrated with the development of organization-wide performance metrics as part of ICANN’s Management System, which will include: Key Success Factors and Key Performance Indicators used to plan and measure performance against the Fiscal Year 2015 Operational Plan and Budget; and trend lines demonstrating performance over time illustrated with Executive Dashboards.

OWT found that ICANN has performed well in comparison with other, similar organizations, and they suggested some areas where ICANN accountability could be improved. These recommendations will be considered in conjunction with the recommendations of the Accountability & Transparency Review Team (ATRT2) and will be implemented, as appropriate.

NEXT STEPS

Next steps will include a community briefing and discussion at the ICANN Singapore meeting as part of the “Management System Linkage” session, and additional presentations and discussions, as needed, to gather community input.

ICANN recognizes that this is the beginning of an improved process of continuous improvement and evolution, and in line with OWT’s recommendation, staff will begin the implementation with a “pilot,” including a selection of accountability metrics to illustrate reporting mechanisms and to collect community feedback. Revisions will then be considered and a long-term implementation plan developed.

We welcome your feedback, ideas and questions. Please send your communications to
This email address is being protected from spambots. You need JavaScript enabled to view it.
.

This announcement was sourced from :

http://www.icann.org/en/news/announcements/announcement-04mar14-en.htm

ICANN: Initial Report Inter-Registrar Transfer Policy (IRTP) Part D PDP

icann logoPurpose (Brief):This Public Forum invites comments on the Initial Report [PDF, 936 KB] of the IRTP Part D PDP . The Report provides 12 preliminary recommendations to the six questions that this PDP Working Group ( WG ) was charted with. Please note that the WG is seeking public comment especially on Charter questions B and C to help inform its final recommendation.
 
Current Status: The WG has completed and published its Initial Report. The Working Group will present the report, its preliminary recommendations, and all remaining open issues during the ICANN Meeting in Singapore at a Public Workshop. Public comment is especially sought on the recommendations for Charter questions B and C since the WG has decided to concretize its recommendation on some of the issues raised in these questions only once they have received and reviewed all public comments. In addition, the WG will refine the Initial Report’s Annex C, containing a list of use cases, in time for the publication of its Final Report.
 
Next Steps: Following the review of the Community discussion during the ICANN Meeting in Singapore and all public comments and replies received during the comment and reply periods, the WG will finalize its recommendations and publish its Final Report.
 
Detailed Information
Section I: Description, Explanation, and Purpose: 

In addition to background information, an overview of the WG ‘s deliberations and community input received to date, the Initial Report [LINK] contains the following preliminary recommendations:

Proposed Recommendation to Charter Question A

Recommendation #1: The WG recommends that reporting requirements be incorporated into the TDRP policy. Outcomes of all rulings by Dispute Resolution Providers1 should be published on Providers’ website, except in exceptional cases. The Group recommends publishing reports that follow the example of the Asian Domain Name Dispute Resolution Centre (ADNDRC).2 These reports should include at a minimum: a) Information about parties involved in the dispute; b) The full decision of the case; c) The date of the implementation of the decision

Recommendation #2: The WG recommends that the TDRP be amended to include language along the lines of this revised version of the UDRP : ‘The relevant Dispute Resolution Provider shall report any decision made with respect to a transfer dispute initiated under the TDRP . All decisions under this Policy will be published in full over the Internet, except when a Dispute Resolution Panel determines, in an exceptional case, to redact portions of its decision. In any event, the portion of any decision determining a complaint to have been brought in bad faith shall be published.’

Proposed Recommendation to Charter Question B

Recommendation #3: The WG recommends that the TDRP be amended as follows: “Transfers from a Gaining Registrar to a third registrar, and all other subsequent transfers, are null and void if the Gaining Registrar acquired sponsorship from the Registrar of Record through an invalid transfer,** as determined through the dispute resolution process set forth in the Transfer Dispute Resolution Policy.”*

Recommendation #4: The WG recommends that a domain name be returned to the original Registrar of Record if it is found through a TDRP procedure that a non-IRTP compliant domain name transfer has occurred. The TDRP as well as guidelines to registrars, registries and third party dispute providers should be modified accordingly.

Recommendation #5: The WG recommends that the statute of limitation to launch a TDRP be extended from current 6 months to 12 months from the initial transfer. This is to provide registrants the opportunity to become aware of fraudulent transfers when they would no longer receive their registrar’s annual WDRP notification.

Recommendation #6: The WG recommends that if a request for enforcement is initiated under the TDRP the relevant domain should be ‘locked’ against further transfers. The TDRP as well as guidelines to registrars, registries and third party dispute providers should be modified accordingly.

*NB: The Working Group would like to encourage Public Comment on the question of whether costs would need to be refunded to registrars in case of negating/reversing transfers under a multiple-hop scenario.

** NB: The Working Group would like to encourage Public Comment on whether in this context there is a need to clearly define ‘invalid transfer’; and if so, how.

Proposed Recommendation to Charter Question C

The WG does not recommend that dispute options for registrants be developed and implemented as part of the current TDRP .

Recommendation #7: The WG recommends that the GNSO ensure that IRTP-C inter-registrant transfer recommendations are implemented and include appropriate dispute-resolution mechanisms. The IRTP-C and IRTP-D Implementation Review Teams should determine whether the inter-registrant transfer use cases documented in Appendix [?] have been addressed. If there are use cases that have not been addressed by the implementation of IRTP-C-2, the Implementation Review Teams are charged with formulating a request for an Issue Report to review the remaining use cases and consider whether any additional dispute resolution mechanisms (or changes to the TDRP ) should be developed. That request should then be forwarded to the GNSO Council for consideration.

Recommendation #8: The WG recommends that the TDRP be modified to eliminate the First Level (Registry) layer of the TDRP .***  

Observation: The WG observes that the information on the ICANN website describing registrant options with regard to inter-registrar and inter-registrant transfers is not as clearly formulated and prominently displayed as it should be. The recommendations for Charter question D below address this issue in detail.

***NB: The Working Group would like to encourage Public Comment on the issue of whether to remove the registry layer from the TDRP .

Proposed Recommendation to Charter Question D

Recommendation #9: The WG recommends that ICANN create and maintains a one-stop website containing all relevant information concerning disputed transfers and potential remedies to registrants. This should include: a) Improvements to the ICANN website regarding the display of information on the Inter Registrar Transfer Policy and the Transfer Dispute Resolution Policy is regularly updated; b) Links to the relevant information for registrants on the ICANN website being clearly worded and prominently displayed on the ICANN home page. This will contribute to improving visibility and content of the ICANN website that is devoted to offering guidance to registrants with transfer issues; c) ICANN Compliance clearly indicates on its FAQ/help section under which circumstances it can assist registrants with transfer disputes. This should include situations when registrants can ask ICANN Compliance to insist on registrars taking action on behalf of said registrant; d) Improvements in terms of accessibility and user-friendliness should be devoted especially to these pages:

http://www.icann.org/en/help/dispute-resolution#transfer

http://www.icann.org/en/resources/registrars/transfers/name-holder-faqs

http://www.icann.org/en/resources/registrars/transfers/text

Links to these registrant help-website should also be prominently displayed on internic.net and iana.org in order to assure further that registrants have easy access to information

Recommendation #10: The WG recommends that, as best practice, ICANN accredited Registrars prominently display a link on their website to this ICANN registrant help site. Registrars may chose to add this link to those sections of their website that already contains Registrant-relevant information such as the Registrant Rights and Responsibilities, the WHOIS information and/or other relevant ICANN-required links as noted under 3.16 of the 2013 RAA .

Proposed Recommendation to Charter Question E

Recommendation #11: The WG recommends that no additional penalty provisions be added to the existing policy. The WG concludes that the penalty structures introduced in the 2009 RAA and the 2013 RA are sufficiently nuanced to deal with IRTP violations.

Recommendation #12: The WG recommends that, as a matter of principle, GNSO Consensus Policy should avoid policy-specific sanctions. Rather, it is desirable that the overarching RAA and RA penalty structures be drafted in a way that assures uniformity and consistency of policy violation penalties .

Proposed Recommendation to Charter Question F

The WG does not recommend the elimination of FOAs.


1 The Working Group recommends in Charter question C to remove the Registry as the first dispute resolution layer of the TDRP . Therefore, despite wording of Charter question A, no reporting requirements for the Registries are included here.

2 See four ADNDRC Reports on TDRP decisions: http://www.adndrc.org/mten/TDRP_Decisions.php?st=6

Section II: Background: 

The aim of the Inter-Registrar Transfer Policy ( IRTP ) is to provide a straightforward procedure for domain name holders to transfer their names from one ICANN-accredited registrar to another. The GNSO Council is reviewing and considering revisions to this policy through a series of Working Groups it has established to conduct these efforts. The IRTP Part D PDP Working Group has been tasked to consider the following six questions:

a) Whether reporting requirements for registries and dispute providers should be developed, in order to make precedent and trend information available to the community and allow reference to past cases in dispute submissions;

b) Whether additional provisions should be included in the TDRP (Transfer Dispute Resolution Policy) on how to handle disputes when multiple transfers have occurred;

c) Whether dispute options for registrants should be developed and implemented as part of the policy (registrants currently depend on registrars to initiate a dispute on their behalf);

d) Whether requirements or best practices should be put into place for registrars to make information on transfer dispute resolution options available to registrants;

Penalties for IRTP Violations
e) Whether existing penalties for policy violations are sufficient or if additional provisions/penalties for specific violations should be added into the policy;

Need for FOAs
f) Whether the universal adoption and implementation of EPP AuthInfo codes has eliminated the need of FOAs.

Section III: Document and Resource Links: 

N/A

Section IV: Additional Information: 

Comment / Reply Periods (*)

  • Comment Open Date: 3 March 2014
  • Comment Close Date: 3 April 2014 – 23:59 UTC
  • Reply Open Date: 4 April 2014
  • Reply Close Date: 25 April 2014 – 23:59 UTC

Important Information Links

This ICANN announcement was sourced from:
www.icann.org/en/news/public-comment/irtp-d-initial-03mar14-en.htm

ICANN Announces New Global Domains Division Portal – Coming Soon!

ICANN is pleased to announce the upcoming launch of the new Global Domains Division (GDD) Portal, which is anticipated to go live in mid-March 2014.

 

This new tool provides a centralized location for new gTLD Registry Operators to communicate with ICANN and to input and access their Registry-related information. This GDD Portal will serve as the new home for the Registry Onboarding and Sunrise processes and the GDD Registry Services team will use it as the primary mechanism to coordinate future registry activities.

What does this mean for new gTLD Registry Operators?

This GDD Portal enhances efficiency by automating new gTLD Registry Operators’ ability to interact with ICANN in one centralized location. The offline forms used to collect registry contact information, Onboarding Information Request (ONBIR) and TLD Startup Information will now be able to be completed via online forms in the GDD Portal.

What is required of new gTLD Registry Operators?

Nothing right now! In the next few weeks Registry Operators will receive additional information about the new portal, including credentialing information.

When will this be available?

The GDD Portal is anticipated to go live in mid-March 2014. Additional information will be provided during upcoming webinars where ICANN will walk through the new Portal, providing a step-by-step overview of its features and functionality and to answer any questions future users of the GDD portal might have.

What happened to the New gTLD Customer Portal?

Nothing has changed in regard to the New gTLD Customer Portal. This system is still the primary access point for applicants to carry out evaluation and contracting processes. New gTLD registry operators will be the first group with access during the initial rollout of the GDD Portal, but ICANN intends to use the portal for communication and to support processes with other Domain Name System industry groups in the future.

What if I have questions?

There will be two upcoming webinars, Tue, 11 March from 00:00am – 01:00am UTC and Tue, 11 March, from 15:00 – 16:00am UTC, where you will be able see a full demonstration of the portal; each session will end with a Q&A period during which you may ask the presenters questions relating to the new GDD Portal. You may also send questions in advance to:
This email address is being protected from spambots. You need JavaScript enabled to view it.
.

This ICANN announcement was sourced from:
newgtlds.icann.org/en/announcements-and-media/announcement-04mar14-en

Jeff Schmidt to Present Name Collision Management Framework at Research Workshop by Burt Kaliski, Verisign

I’m delighted to announce that the name collisions workshop this weekend will include Jeff Schmidt, CEO of JAS Global Advisors, presenting the Name Collision Occurrence Management Framework that his firm just released for public review.

 

Jeff’s presentation is one of several on the program announced by the program committee for the Workshop and Prize on Root Causes and Mitigations of Name Collisions (WPNC).

The program starts with a keynote presentation by Bruce Schneier, and will also include research papers and invited panels on various aspects and implications of the name collisions issue.

As a gathering of researchers and practitioners with broad expertise in DNS, network operations and Internet systems, the workshop provides an ideal venue for community engagement on the proposals in the new framework document, as well as on solutions to the issue more generally.

Thanks to the program committee for their careful review of the papers submitted to the workshop and the well-rounded program for the event, which runs March 8-10.  To register to attend, visit namecollisions.net/registration

This article by Verisign’s Burt Kaliski was sourced with permission from:
blogs.verisigninc.com/blog/entry/jeff_schmidt_to_present_name