ICANN/DNSO
DNSO Mailling lists archives

[nc-idn]


<<< Chronological Index >>>    <<< Thread Index >>>

[nc-idn] Re: [council] MINC Position to Names Council's IDN Task Force Activity


> please clarify whether or not the board of MINC approved the resolution.

I thought this was posted to the NC and realized it was sent to only
Ken. FYI for other NC members, too.

----- Original Message -----
From: "Tan Tin Wee" <tinwee@bic.nus.edu.sg>
To: <kstubbs@digitel.net>
Cc: "YJ Park" <yjpark@minc.org>; <board@minc.org>
Sent: Friday, October 26, 2001 8:48 PM
Subject: MINC Position to Names Council's IDN Task Force Activity


> Dear Ken,
>
> Many thanks for your query which has been forwarded by
> MINC Interim CEO YJ Park for MINC Board's immediate
> attention. As you can tell, the draft is
> 0.3, which was forwarded to you by YJ Park proactively.
>
> The board is in the process of improving the text of the draft but
> the key points expressed in the draft will eventually remain the
> same, perhaps rephrased in more diplomatic terms:
>
> a. that DNSO should be aware of the implications of causing
>    user confusion and instability to the IDN world should it
>    enter into an area where MINC, its industry members and its
>    associated groups such as AINC, INFITT, CDNC, JDNA have
>    already made significant progress towards
>    IDN policy areas and coordination amongst key stakeholders
>    along linguistic, technical, testbedding, test-deployment
>    and operational lines.
>
> b. that even the IETF IDN WG has not yet arrived at rough consensus
>    indicates the level of complexity of issues, and that NC and DNSO,
>    in view of its focus on the lesser complexity of ASCII ccTLDs
>    and the challenge it faces in coping with ccTLDs and the ccSO,
>    should advisedly avoid getting embroiled in an area of potential
>    controversy, which MINC and its associated groups have been trying
>    to stabilise for some time.
>
> c. that the inopportune time of NC/DNSO entry into IDN issues without
solving
>    the basic ccTLD issues may drag the IDN efforts of MINC and its
associated
>    groups into more confusion and instability by clouding Multilingual
>    IDNs with ASCII ccTLD-associated politics and controversy.
>
> d. that some ccTLDs which are working with MINC have already
>    implemented <IDN>.<ccTLD> domain names e.g. Japanese.jp, Korean.kr
>    and Chinese.cn,
>    and that DNSO's situation with the current ccSO movement,
>    might make it inadvisable to open up another front of
>    controversy with ccSO supporters.
>
> e. that Names Council and DNSO should work closely
>    with MINC and its associated groups
>    to understand the situation in IDNs better.
>
> Does this sound reasonable?
>
> bestrgds
>
> Tin Wee
> --
> Vice Chairman
> MINC


> ken stubbs
>
> ----- Original Message -----
> From: "MINC" <yjpark@minc.org>
> To: <council@dnso.org>
> Cc: <nc-idn@dnso.org>
> Sent: Thursday, October 25, 2001 10:17 PM
> Subject: [council] MINC Position to Names Council's IDN Task Force
Activity
>
>
> > NC,
> >
> > I am sending this message with my another hat, MINC Interim Acting
> > CEO rather than my NC hat, and IDN TF hat in the DNSO.
> >
> > If you have any further question, I am happy to answer to you.
> >
> > Thank you,
> > YJ Park
> > Interim Acting CEO, MINC
> >
> >
> > [Position of MINC]
> > October. 26. 2001
> > version 0.3
> >
> > Whereas Mulitilingual Interner Names Consortium(MINC) has been
> > promoting multilingual Internet names since the first International
> > coordination meeting in Seoul in February during 2000 APRICOT
> > to identify the issues of multilingual domain names,
> >
> > Whereas, after five months' MINC task force period from February 2000
> > to July 2000, MINC could be finally lauched in Yokohama in July 2000
> > under the supports from various stakeholders from the service providers
> > and the users who have been suffering from language barrier on the
> > ASCII-only cyberspace,
> >
> > Whereas MINC has made every effort to encourage diverse language
> > communities to create their own self-organizing space and have supported
> > the creation of Arabic Internet Names Consortium, International Forum
for
> > Information technology in Tamil, Chinese Domain Name Consortium and
> > others,
> >
> > Whereas MINC has been interacting with International organizations
> > such as Internet Society, Internet Engineering Task Force, International
> > Telecommunication Union, Domain Names Supporting Organization of
> > Internet Corporation for Assigned Names and Numbers etc, MINC
> > has funneled appropriate information and knowledge into them,
> >
> > Whereas MINC regrets the fact that some of those organizations that MINC
> > has been cooperating with are about to take actions without consultation
> > with MINC and its stakeholders,
> >
> > Whereas it is understood that the current Names Council members are
> > from ASCII domain name cyber space except "one member" whose native
> > language is non-ASCII-based language. It is somewhat unprofessional to
> > adopt a resolution among those who have little knowdege and expertise
> > about multilingual Internet Names.
> >
> > Whereas DNSO presented more than two thirds of North American experts
> > in Montevideo NC meting, when it was asked to provide the experts about
> > Uniform Dispute Resolution Policy with a reason that they are true
> experts.
> > If this is the spirit of DNSO, ICANN, this current activities by
> non-experts
> > sounds very contradicting compared to DNSO's accumulated practice,
> >
> > Whereas the charter of this Task Force was presented by the former Chair
> > explicitly seeks cooperation from other multilingual coordination bodies
> > such as MINC,
> >
> > As Multilingual Internet Names Coordination Body, MINC hereby requests
> > that DNSO Names Council consider the following position of MINC:
> >
> > First, DNSO should not try to expand its role to enter into
> > Internationalized Domain Names policy area or multilingual domain names
> > without expertise and proper understanding about it.
> >
> > Second, DNSO should not try to exert influence on issues that might
affect
> > other potential majors SOs including forthcoming ccSO and other
> independent
> > language communities, when those issues might be dealt with more
adquately
> > within other SOs and language communities.
> >
>
> --------------------------------------------------------------------------
> --
> >
> > [Note 1] This is the current list of NC members. Most of them are from
> >               ASCII-space.
> >
> > NorthA (.vi) - Peter de Blanc
> > Europe (.fr) - Elisabeth Porteneuve
> > LatinAC (.mx) - Oscar Alejandro Robles Garay
> > Europe (.uk) - Philip Sheppard
> > NorthA (.us) - Marilyn Cade
> > AsiaPac (.nz) - Grant Forsyth
> > NorthA (.us) - Roger Cochetti
> > AsiaPac (.au) - Richard Tindal
> > Europe (.se) - Cary Karp
> > LatinAC (.ar) - Antonio Harris
> > Europe (.uk) - Tony Holmes
> > NorthAm (.us) - Greg Ruth
> > NorthAm (.us) - Milton Mueller
> > AsiaPac (.kr) - Youn Jung Park
> > LatinAC (.pa) - Nilda Vany Martinez Grajales
> > NorthA (.us) - Ken Stubbs
> > AsiaPac (.au) - Erica Roberts
> > Europe (.uk) - Paul Kane
> > NorthA (.us) - Caroline Chicoine
> > Europe (.de) - Axel Aus der Muhlen
> > LatinAC (.cl) - Guillermo Carey
> >
> >
>



<<< Chronological Index >>>    <<< Thread Index >>>