[alac] RSTEP Report on Tralliance Proposal

[Bret Fausett <bfausett@xxxxxxxxxxxxxxxx>]

In short, the recommendation is not to allow the .TRAVEL wildcard.


------ Forwarded Message
From: ICANN News Alerts <icann-alerts@xxxxxxxxx>
Date: Thu, 9 Nov 2006 15:33:27 -0800
To: <alerts-text@xxxxxxxxxxxxxxxxxxxx>
Subject: [alerts-text] ICANN News Alert -- RSTEP Report on Tralliance
Proposal Posted for Public Comment

ICANN - The Internet Corporation for Assigned Names and Numbers
<http://www.icann.org/>

News Alert

http://www.icann.org/announcements/announcement-09nov06.htm
 
________________________________


RSTEP Report on Tralliance Proposal Posted for Public Comment

9 November 2006

On 18 September 2006, ICANN referred the Tralliance Corporation
search.travel proposal
<http://www.icann.org/registries/rsep/tralliance_request.pdf> to the
Registry Services Technical Evaluation Panel (RSTEP). The RSTEP
had 45 calendar days to review the proposal and prepare a written report on
whether the proposed Registry Service creates a
reasonable risk of a meaningful adverse effect on Security or Stability. The
RSTEP Review Team completed its report that can be
found at http://www.icann.org/registries/rsep/tralliance_report.pdf.

The Review Team consisted of the following members:

* Patrik Fältström (Cisco; Sweden)
* Lars-Johan Liman (Autonomica; Sweden)
* Cricket Liu (Infoblox; USA)
* Mark McFadden (internet policy advisors, llc; USA)
* Paul Mockapetris (Nominum; USA)

Under the terms of the Registry Services Evaluation Policy
<http://www.icann.org/registries/rsep/rsep.html>, following receipt of
the RSTEP report, the ICANN Board will determine whether the proposed
Registry Service creates a reasonable risk of a meaningful
adverse effect on Stability or Security.

ICANN invites public comments on the RSTEP Report through 18:00 UTC (10:00
PST) on 7 December 2006.
 
Documents related to the Tralliance proposal are available here:

* Tralliance Request
<http://www.icann.org/registries/rsep/tralliance_request.pdf>
* ICANN Letter to SSAC
<http://www.icann.org/registries/rsep/icann-to-ssac-01sep06.pdf>
* SSAC Reply 
<http://www.icann.org/registries/rsep/ssac-to-icann-06sep06.pdf>
* ICANN Letter to Tralliance
<http://www.icann.org/registries/rsep/icann-to-tralliance-13sep06.pdf>
* Tralliance Letter to ICANN
<http://www.icann.org/registries/rsep/tralliance-to-icann-14sep06.pdf>
* ICANN Letter to RSTEP
<http://www.icann.org/registries/rsep/icann-to-rstep-18sep06.pdf>
* RSTEP Report <http://www.icann.org/registries/rsep/tralliance_report.pdf>

Comments can be posted to: tralliance-comments@xxxxxxxxxx

Comments can be viewed at: http://forum.icann.org/lists/tralliance-comments.

________________________________


To unsubscribe from this mailing list, please visit
http://www.icann.org/communications#alerts-text

If you have questions or comments about this mailing list, send an email to
ICANN-Alerts@xxxxxxxxx



------ End of Forwarded Message