<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [council] RE: Pending additions to ICANN glossary -- update on Council request from Mexico City
hi,
i think that is true of the entire ICANN web site. At least has been
for me ever since it was improved.
a.
On Tue, 2009-04-28 at 21:36 -0400, Rosette, Kristina wrote:
> I stand corrected. But they still have to find it . ..
>
>
> ______________________________________________________________
> From: Adrian Kinderis [mailto:adrian@xxxxxxxxxxxxxxxxxx]
> Sent: Tuesday, April 28, 2009 9:35 PM
> To: Adrian Kinderis; Rosette, Kristina; Council GNSO
> Subject: RE: [council] RE: Pending additions to ICANN glossary
> -- update on Council request from Mexico City
>
>
>
> From my quick click around it seems to be public to me!
>
>
>
> https://st.icann.org/gnso-council/index.cgi?gnso_council_workspace
>
>
>
> Adrian Kinderis
>
>
>
>
>
>
>
>
> From: owner-council@xxxxxxxxxxxxxx
> [mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Adrian
> Kinderis
> Sent: Wednesday, 29 April 2009 11:29 AM
> To: Rosette, Kristina; Council GNSO
> Subject: RE: [council] RE: Pending additions to ICANN glossary
> -- update on Council request from Mexico City
>
>
>
>
> Yes. Didn’t think to address access... although isn’t the GNSO
> Council wiki public?
>
>
>
> Adrian Kinderis
>
>
>
>
> From: owner-council@xxxxxxxxxxxxxx
> [mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Rosette,
> Kristina
> Sent: Wednesday, 29 April 2009 11:25 AM
> To: Council GNSO
> Subject: RE: [council] RE: Pending additions to ICANN glossary
> -- update on Council request from Mexico City
>
>
>
>
> Definitely agree with listing entries by acronym.
>
>
>
> Would definitely be helpful to have a more informal glossary
> for Council, but many who can most benefit from the glossary
> don't have access to the wiki.
>
>
>
> While we're suggesting terms, I'd add: domain tasting, fast
> flux, IPv4, IPv6, RALO, Nominating Committee
>
>
>
> K
>
>
>
>
> ______________________________________________________
> From: owner-council@xxxxxxxxxxxxxx
> [mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of
> Adrian Kinderis
> Sent: Tuesday, April 28, 2009 9:19 PM
> To: Liz Gasster; Council GNSO
> Subject: [council] RE: Pending additions to ICANN
> glossary -- update on Council request from Mexico City
>
> Thanks Liz.
>
>
>
> Would it be possible to have this glossary in a wiki
> format that could be added to and adjusted on the fly?
>
>
>
> I understand having it as an ‘official’ ICANN Glossary
> in this way may be problematic but maybe a GNSO
> Council specific one on our wiki? I note that such
> things as IRT, IDN, DNSSEC etc are not there... we
> could all pitch in to add definitions if it was a
> wiki. Folks in the industry that speak different
> languages could provide translations ‘on the fly’.
>
>
>
> Just a thought...
>
>
>
> Also it would help to list them by acronym not by true
> name. So when someone hears the acronym they can find
> it easily.
>
>
>
> Adrian Kinderis
>
>
>
>
>
>
> From: owner-council@xxxxxxxxxxxxxx
> [mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Liz
> Gasster
> Sent: Wednesday, 29 April 2009 7:29 AM
> To: Council GNSO
> Subject: [council] Pending additions to ICANN glossary
> -- update on Council request from Mexico City
>
>
>
>
> All,
>
>
>
> During our after-action meeting in Mexico City,
> several of you suggested that we update the ICANN
> glossary to add some basic terms that we refer to
> frequently but that are missing currently from that
> compendium
> http://www.icann.org/en/general/glossary.htm .
> Definitions have been developed for the terms that
> were identified by Council members (copied below for
> your reference, note also an updated definition of
> WHOIS has been prepared). These definitions are
> currently being translated and they will be added to
> the glossary when the translations are complete.
>
>
>
> ICANN’s Corporate Affairs department will be updating
> the glossary more broadly in the upcoming weeks.
>
>
>
> We will also be adding a link to the glossary from the
> GNSO home page, http://gnso.icann.org/ . This was
> also suggested in the Mexico meeting.
>
>
>
> Thanks, Liz
>
>
>
>
> PDP - Policy Development Process
>
>
> A set of formal steps, as defined in the ICANN bylaws,
> to guide the initiation, internal and external review,
> timing and approval of policies needed to coordinate
> the global Internet’s system of unique identifiers.
>
>
>
>
> Operations Steering Committee
>
>
> The Operations Steering Committee (OSC) coordinates,
> recommends and reviews changes to certain operational
> activities of the GNSO and its constituencies with a
> view to efficient outcomes. These operational
> activity areas cover GNSO operations, Stakeholder
> Group and Constituency operations, and communications
> with GNSO and between GNSO and other ICANN structures.
>
>
>
>
> Policy Process Steering Committee
>
>
> The Policy Process Steering Committee (PPSC) reviews
> and recommends processes used within the GNSO for
> developing policy, including the use of Working
> Groups, and recommending any changes.
>
>
>
>
> Registry Services Evaluation Process
>
>
> The Registry Services Evaluation Process (RSEP) is
> ICANN’s process for evaluating proposed gTLD registry
> services or contractual modifications for security,
> stability or competition issues. Further information
> on RSEP is available at
> http://www.icann.org/en/registries/rsep/.
>
>
>
>
> WHOIS
>
>
> WHOIS (pronounced "who is"; not an acronym) An
> Internet protocol that is used to query databases to
> obtain information about the registration of a domain
> name (or IP address). The WHOIS protocol was
> originally specified in RFC 954
> <http://www.ietf.org/rfc/rfc954.txt>, published in
> 1985. The current specification is documented in RFC
> 3912 <http://www.ietf.org/rfc/rfc3912.txt>. ICANN's
> gTLD agreements require registries and registrars to
> offer an interactive web page and a port 43 WHOIS
> service providing free public access to data on
> registered names. Such data is commonly referred to as
> "WHOIS data," and includes elements such as the domain
> registration creation and expiration dates,
> nameservers, and contact information for the
> registrant and designated administrative and technical
> contacts.
>
> WHOIS services are typically used to identify domain
> holders for business purposes and to identify parties
> who are able to correct technical problems associated
> with the registered domain.
>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|