Re: [council] MOTION on Nominees to the new ICANN IDNsCommitee:split into two motions

[Nilda Vany Martinez Grajales <vany@sdnp.org.pa>]

Philip and all:

Regardless ICANN answer, I encourage Names Council members to vote on
the motion proposed.  

Best Regards
Vany



Philip Sheppard wrote:
>Vany,
>
>thanks for you work on this. I have asked ICANN to clarify the proposed
>composition /diversity/expertise of the proposed committee. This will help
>us decide what steps the NC needs to take.
>
>Philip



Nilda Vany Martinez Grajales wrote:
> 
> Hi to all:
> 
> As Philip asked, I asked to Stuart about the composition of ICANN IDN
> Committee.   Stuart has told me that such
> committee is appointing only one person from the DNSO, as far as I understood.
> 
> Due to such answer I want to amend and split the actual motion into two
> motions:
> 
> Motion #1:
> "The Names Council request to ICANN Board that appoints two participants
> representing DNSO instead of one to serve in the ICANN IDNs Committee.  Such
> persons doesn't have to be neceasrily
> Names Council members.  The Names Council will be in charge of appointing such
> two  participants.  One  participant has to be knowledgeable in languages
> covered by ASCII table and the other participant
> has to be knowledgeable in languages not covered by ASCII table.  Both of them
> has to have as mother tongue a language different than English in order to
> assure the proper representation and sensibility for languages and scripts
> different than English be implemented in the DNS"
> 
> Motion #2
> The Names Council request to the ICANN Board that the compostion of the
> ICANN IDNs Committee might be diverse as possible and comprise a wide variety
> of experts and natives, not only
> in ASCII or Non-ASCII characters, also experts in the different kinds of
> scripts
> that can be clasified in the following groups:  Cyrillic, Latin, Katakana,
> Ethiopic, Syriac, Devanagari,
> Arabic, Batak, Bengali, Buginese Buhid, Cham, Han, Greek, Canadian Aboriginal,
> Thaana, Tibetan, Georgian,
> Gujarati, Hanunoo, Hebrew, Hmong, Hiragana, Kannada, Myanmar, Khmer, Thai,
> Malayalam, Thaana, Mongolian,
> Naxi, Oriya, Gurmukhi, Sinhala, Tagalog, Tagbanwa, Tamil, Telegu, Yi".
> 
> The list of scripts was taken from the following webpage:
> http://www.unicode.org/unicode/onlinedat/languages-scripts.html
> 
> Any comments?
> 
> Best Regards
> Vany
> 
> Nilda Vany Martinez Grajales wrote:
> 
> > Milton and all:
> >
> > Milton Mueller wrote:
> > >
> > > I agree with what Vany is proposing here,
> > > only I would say, "Roman" and "non-Roman"
> > > script rather than ASCII v. non-ASCII.
> >
> > Thank you Milton! However not all Roman language scripts are represented
> > in the ASCII table.
> >
> > http://indoeuro.bizland.com/project/script/latin.html  for an overview
> > of Roman Scripts
> > http://developer.apple.com/techpubs/mac/Text/Text-30.html  for an
> > overview on how Scripts System works
> > http://www.asciitable.com/  For the complete ASCII table
> >
> > Slavics languages are, in fact Roman languages then its scripts are also
> > classified as Roman Scripts, but such scripts are not
> > represented in the ASCII table.
> >
> > However, many of the Greek language letters are represented in the ASCII
> > table although Greek Script is not a Roman Script (neither a Roman
> > language, although Roman language origins are in the Greek).
> >
> > So it would be innacurate to speak about Roman Script and Non-Roman
> > Script when actual DNS relies in the ASCII table (and not all characters
> > are implemented).
> >
> > > The committee needs to have a co-chair
> > > perhaps that is someone from the non-Roman
> > > script world. It is an important part of
> > > the IDN puzzle.
> >
> > The actual chair is Japaneese as far as I know.  Then in fact if a
> > co-chair would be appointed
> > needs to be one on the side of ASCII-Character.  In this case I would be
> > tending to suggest a co-chair
> > that doesn't comes from the English worlds since probably this is more
> > than represented.  I would suggest a
> > co-chair that is native from the languages that its complete alphabet is
> > included in ASCII table different than
> > English (Spanish, for example).  Remember that accents and some letters
> > in the ASCII table are not implemented in the DNS system.
> >
> > Please, NC fellows, find below the amended motion:
> >
> > The Names Council will make a call for nominations to the new
> > ICANN IDNs Committee amongst DNSO constituencies. The list of nominees
> > might include people with expertise on languages
> > using ASCII characters and people with expertise
> > on language using non-ASCII characters, required that
> > in both cases, such experts has to be native of the language of
> > character group
> > of expertise (ASCII or Non-ASCII).
> >
> > Futher, also the Names Council request to the ICANN Board that
> > admites in behalf of DNSO in its ICANN IDNs Committee
> > at least two persons: one native from languages of ASCII character group
> > and one native
> > from languages of non-ASCII characters group.
> > In the event that ICANN is willing to select more than two nominees from
> > the nominees list sent by the Names Council to
> > participate in ICANN IDNs Committee then both ASCII and Non-ASCII
> > character natives should be equally
> > represented.
> >
> > Since the Co-Chair is native from a language from the group of Non-ASCII
> > characters, also the Names Council strongly recommends that the ICANN
> > IDNs Committee appoints a co-chair native from a language which complete
> > alphabet is included in ASCII table but such complete alphabet is not
> > implemented in the DNS system (i.e. Spanish, Italina, French, for
> > example).
> >
> > Best Regards
> > Vany
> >
> > Milton Mueller wrote:
> > >
> > > I agree with what Vany is proposing here,
> > > only I would say, "Roman" and "non-Roman"
> > > script rather than ASCII v. non-ASCII.
> > >
> > > The committee needs to have a co-chair
> > > perhaps that is someone from the non-Roman
> > > script world. It is an important part of
> > > the IDN puzzle.
> > >
> > > >>> Nilda Vany Martinez Grajales <vany@sdnp.org.pa> 10/27/01 13:54 PM >>>
> > >
> > > The NC will appoint several nominees to the new
> > > ICANN IDNs Committee. The list of  nominees
> > > might include people with expertise on language
> > > using ASCII characters and people with expertise
> > > in language using non-ASCII characters, required that
> > > in both cases, such experts has to be native
> > > of the group of languages of expertise.
> > >
> > > Futher, also NC request to the ICANN Board that
> > > admites in behalf of
> > > DNSO in its ICANN IDNs Committee
> > > at least two persons: one expert on ASCII characters and one expert in
> > > non ASCII characters.
> > > In the event that ICANN is willing to select more experts from DNSO to
> > > participate in ICANN IDNs Committee
> > > then both ASCII and Non-ASCII character experts should be equally
> > > represented.
> > >
> > > Best Regards
> > > Vany
> > >
> > >
> > -- Philip Sheppard <philip.sheppard@aim.be> wrote:
> > > > New ICANN IDN Committee Names Council nomineeNC,
> > > > at our last NC meeting, we confirmed Elisabeth
> > > > Porteneuve as chair of the Council task force on
> > > > internationalised domain names (IDNs). With respect
> > > > to the request below from ICANN for an NC
> > > > representative to the ICANN Internationalized Domain
> > > > Names Committee, it would seem logical to nominate
> > > > Elisabeth for this role. She has indicated to me she
> > > > would be willing to do this.
> > > >
> > > > Accordingly I nominate her formally. Please indicate
> > > > your support for this nomination or any alternative
> > > > by email latest October 26.
> > > >
> > > > Philip Sheppard
> > > >
> > > > ----- Original Message -----
> > > > From: M. Stuart Lynn
> > > > To: Philip Sheppard
> > > > Cc: Masanobu Katoh ; Andrew McLaughlin
> > > > Sent: 16 October 2001 02:49
> > > > Subject: New ICANN IDN Committee Names Council
> > > > nominee
> > > >
> > > >
> > > > Dear Philip:
> > > >
> > > >
> > > > The purpose of this note is to enquire whether the
> > > > Names Council would be interested in nominating
> > > > someone to be proposed for membership in the new
> > > > ICANN Internationalized Domain Names Committee that
> > > > the Board authorized at its meeting in Montevideo
> > > > last month (see text of resolution appended to this
> > > > note). The overall purpose of this Committee is to
> > > > be a general coordination body for the work on
> > > > policy issues identified in the IDN Working Group
> > > > Final Report(see
> > > > http://www.icann.org/montevideo/idn-topic.htm) and
> > > > such other policy issues that the IDN Committee
> > > > identifies in the course of its activities.
> > > >
> > > >
> > > > You may recall that the IDN Working Group (see
> > > > http://www.icann.org/committees/idn/) was a
> > > > committee composed exclusively of ICANN Directors
> > > > chaired by Director Katoh. It completed its
> > > > activities with its Final Report submitted to the
> > > > Board at  Montevideo. The main recommendations of
> > > > that Final Report were (1) there are a series of
> > > > important policy issues regarding the introduction
> > > > of IDN's that are best considered now in parallel
> > > > with the technical work of the IETF, rather than
> > > > waiting for the IETF  to announce a proposed
> > > > standard, and (2) that the various committees, task
> > > > forces etc involved with the development of these
> > > > policy issues are best coordinated by a single ICANN
> > > > committee, the IDN Committee that is more widely
> > > > rooted in the community. The Board approved the
> > > > formation of this IDN Committee - that will also be
> > > > chaired by Director Katoh - and asked me to propose
> > > > its membership to the Board in consultation with
> > > > Director Katoh and other members of the ICANN
> > > > community. Hence this note
> > > >
> > > >
> > > > I wold certainly be pleased to propose to the Board
> > > > a member nominated by the Names Council. I am sure
> > > > that most of the Committee's work will be conducted
> > > > by email, although there may be the occasional
> > > > teleconference. As I mentioned, it will be chaired
> > > > by Director Katoh. Andrew McLaughlin will provide
> > > > staff support to the Committee during its start-up
> > > > phase.
> > > >
> > > >
> > > > I look forward to hearing from you on the Council's
> > > > decision one way or the other.
> > > >
> > > >
> > > > With  regards,
> > > > Stuart
> > > >
> > > >
> > > > _____________
> > > > Resolution passed by the ICANN Board of Directors at
> > > > its Montevideo meeting, September 10, 2001:
> > > >
> > > >
> > > > Whereas, in resolution 01.39 the Board established
> > > > an internal working group on Internationalized
> > > > Domain Names to identify the various
> > > > internationalization efforts and the issues they
> > > > raise, to engage in dialogue with technical experts
> > > > and other participants in these efforts, and to make
> > > > appropriate recommendations to the Board;
> > > >
> > > > Whereas, the internal working group conducted
> > > > various information-gathering activities, including
> > > > the posting of a community survey;
> > > >
> > > >
> > > > Whereas, the internal working group presented an
> > > > interim report at the ICANN Public Forum held in
> > > > Stockholm on 3 June 2001, and that report was
> > > > discussed at the Public Forum, at the Board Meeting,
> > > > and on ICANN's Internationalized Domain Names
> > > > web-based public forum;
> > > >
> > > >
> > > > Whereas, the internal working group presented its
> > > > final report at the ICANN Public Forum held in
> > > > Montevideo on 9 September 2001;
> > > >
> > > > Whereas, the final report identified several policy
> > > > issues meriting further evaluation and recommended
> > > > that the examination of these issues proceed in
> > > > parallel with continuing technical standardization
> > > > and other preparatory work for the introduction of
> > > > IDNs;
> > > >
> > > >
> > > > Whereas, these policy issues cannot be fully
> > > > resolved until the Internet Engineering Task Force
> > > > completes work on a deployable IDN standard, but
> > > > initial wrk on the policy issues that will arise
> > > > can and should proceed concurrently;
> > > >
> > > > Whereas, the final report also recommended that the
> > > > Board establish an IDN Committee to coordinate the
> > > > work of various ICANN supporting organizations,
> > > > committees, and other groups on the policy issues
> > > > and to promote timely development of policy
> > > > recommendations on them; and
> > > >
> > > >
> > > > Whereas, the Board has considered public comment on
> > > > the final report made electronically and at the
> > > > Montevideo Public Forum;
> > > >
> > > > Resolved [01.94] that IDN Committee is hereby
> > > > established under Article VII, Section 1(c), of the
> > > > ICANN bylaws to serve as a general coordination body
> > > > for the work on policy issues identified in the IDN
> > > > Working Group Report and such other policy issues
> > > > that the IDN Committee shall identify;
> > > >
> > > > Further resolved [01.95] that the IDN Committee
> > > > shall be responsible for promoting the coordination
> > > > of the work of the ICANN supporting organizations,
> > > > committees, and other groups on the policy issues
> > > > arising from IDNs, as documented in the final
> > > > report, and to promote timely development of policy
> > > > recommendations on those issues for consideration by
> > > > the community and the ICANN Board;
> > > >
> > > > Further resolved [01.96] that in its
> > > > policy-coordination activities, the IDN Committee
> > > > should seek to ensure that any recommendations are
> > > > achieved through a bottom-up process, and that those
> > > > recommendations reflect a wide range of expertise on
> > > > the different aspects relevant to the issues;
> > > >
> > > > Further resolved [01.97] that the IDN Committee
> > > > shall be chaired by Director Masanobu Katoh;
> > > >
> > > > Further resolved [01.98] that the President, in
> > > > consultation with the IDN Committee Chair, shall
> > > > propose, for approval by the Board, representatives
> > > > to serve on the IDN Committee from the ICANN Board,
> > > > the Supporting Organizations, the Governmental
> > > > Advisory Committee, and such other individuals who
> > > > in his judgment could meaningfully contribute to
> > > >this effort;
> > > >
> > > > Further resolved [01.99] that the IDN Committee is
> > > > encouraged to commission panels of volunteer experts
> > > > from different countries with practical experience
> > > > in the policy issues identified in the Final Report,
> > > > and linguistic experts (including experts in
> > > > non-ASCII character sets and languages not spoken by
> > > > persons active in current discussions); and
> > > >
> > > > Further resolved [01.100] that the IDN Committee is
> > > > requested to present its initial work plan,
> > > > schedule, and proposed budget for approval by the
> > > > ICANN Board at the third ICANN annual meeting, to be
> > > > held in Marina del Rey in November 2001.
> > > >
> > > >
> > > >
> > > > --
> > > >
> > > >
> > > > __________________
> > > > Stuart Lynn
> > > > President and CEO
> > > > ICANN
> > > > 4676 Admiralty Way, Suite 330
> > > > Marina del Rey, CA 90292
> > > > Tel: 310-823-9358
> > > > Fax: 310-823-8649
> > > > Email: lynn@icann.org
> > > >
> > >
> > > --
> > > Nilda Vany Martinez Grajales
> > > Information Technology Specialist
> > > Sustainable Development Networking Programme/Panama
> > > Tel: (507) 317-0169
> > > http://www.sdnp.org.pa
> > > e-mail:  vany@sdnp.org.pa
> >
> > --
> > Nilda Vany Martinez Grajales
> > Information Technology Specialist
> > Sustainable Development Networking Programme/Panama
> > Tel: (507) 317-0169
> > http://www.sdnp.org.pa
> > e-mail:  vany@sdnp.org.pa
> 
> --
> Nilda Vany Martinez Grajales
> Information Technology Specialist
> Sustainable Development Networking Programme/Panama
> e-mail: vany@sdnp.org.pa
> http://www.sdnp.org.pa

-- 
Nilda Vany Martinez Grajales
Information Technology Specialist
Sustainable Development Networking Programme/Panama
Tel: (507) 317-0169
http://www.sdnp.org.pa
e-mail:  vany@sdnp.org.pa