Inclusion of Individual Internet Users within the City-TLD Multistakeholder Governance Environment
Fellow NARALO Members, ICANN granted the city of New York the right to issue domain names using the .nyc TLD in January 2014. As of May 1, 2016, 76,682 names had been issued to individuals and organizations. Connecting.nyc Inc. is an At-Large Structure associated with the ICANN and an active participant in its multistakeholder governance process. With our focus on the development of the .nyc TLD as a public interest resource, I recently reviewed the .nyc Registry Agreement page on ICANN's website <https://www.icann.org/resources/agreement/nyc-2014-01-23-en>, and noted that four changes to the original agreement had been recorded there. Three were under the heading "Authorization(s) for Release of Reserved Names," as follows: * All Digit/Digit, Letter/Digit, and Digit/Letter Two-Character ASCII Labels at the Second Level (01 December 2014) <https://www.icann.org/en/system/files/files/spec5-amend-two-char-01dec14-en....> * Letter/Letter Two-Character ASCII Labels (26 May 2015) <https://www.icann.org/sites/default/files/tlds/nyc/nyc-auth-ltr-ltr-26may15-...> * Letter/Letter Two-Character ASCII Labels (14 March 2016) <https://www.icann.org/sites/default/files/tlds/nyc/nyc-auth-ltr-ltr-14mar16-...> The fourth was listed under "Amendment No.1 (31 March 2016)": * PDF <https://www.icann.org/sites/default/files/tlds/nyc/nyc-amend-1-pdf-31mar16-e...> This PDF amendment deals with the addition of 14 new data fields to the Registration Data Directory. The existence of these changes came as a complete surprise to me. As Chair of Connecting.nyc Inc., a NYS nonprofit created in 2007 to engage and educate New Yorkers about the use of the .nyc TLD, and as an active participant in ICANN's governance processes through our association as an At-Large Structure, I had presumed we would have been consulted about changes to the registry agreement. My desire for inclusion of individual Internet users in consultations about future registry changes provides the basis for this message. Note: An earlier email on this general subject led some to think I was challenging the 4 registry changes as being out of compliance with approved ICANN procedures. This is not the case. And based on my perusal of precedent references kindly provided by a fellow ALSer (see them below), I’d say that ICANN and the city followed the “letter of the law.” However... However, I do question the efficacy of a process that allows changes to a registry agreement without taking full advantage of the existing machinery of governance, i.e., the multistakeholder model and the extant At-Large Structures (ISOC-NY is also a NYC based ALS). With the Internet community having settled on a multistakeholder governance model, one would imagine that our ALS would be involved in changing the basic agreement that guides the operation of the .nyc TLD. But perhaps we were excluded from the review process for good reason, for example, that the city’s governance structure more effectively represents the needs of the various stakeholders than the Internet’s multistakeholder model. After all, New York City does have a democratic governance system, and a general election was held in November 2013. Perhaps it's thought the people thereby approved or acquiesced to the registry agreement, and thus, in the eyes of ICANN, a city-based ALS should not have a formal role. If this is the situation, I would appreciate someone pointing me to the relevant guidelines. For indeed... At this point, the city is acting as if there is no role for its residents in a traditional multistakeholder model. While there was a 20 month period during which the city acknowledged the role of the residents and users through a .NYC Community Advisory Board (May 2013 - December 2014), the city unilaterally decided that entity should cease to exist on January 1, 2015. And to my dismay, it followed this decision by eliminating all reference to the .NYC Community Advisory Board’s very existence from the city’s website. NOTE: To my knowledge city government has not been provided with any requirement or guideline about the operation of an inclusive, multistakeholder governance process for the .nyc TLD. So I’m not faulting the city administration for the current state of affairs. To do so would be to assume greater awareness and concomitant responsibility about this new resource than is seemingly warranted. What’s to be done? This email seeks the assistance or NARALO in learning if Connecting.nyc Inc. should be provided with an opportunity to consult and consent to future registry agreement changes. We see precedent for this with the .us TLD. The .us TLD is currently governed with the assistance of a .usTLD Stakeholder Council: http://www.neustar.us/ustld-stakeholder-council/structure-and-history/. The council has a charter <http://www.neustar.us/ustld-stakeholder-council/charter/>, operating procedures <http://www.neustar.us/ustld-stakeholder-council/ustld-stakeholder-council-op...>, a membership (which is appointed by the contractor!), and operational parameters (see usTLD Administrative Component graphic below). If it is the consensus that we are inappropriately outside the extant "consultation loop" I suggest that NARALO initiate a review to determine if the current process should be changed to more closely align with the tenets of the multistakeholder governance system that underpins the operation of ICANN and the Internet. Sincerely, Thomas Lowenhaupt ------------------------------------------------------------------------ Basis for ICANN approval of 4 .nyc TLD registry agreement changes * The release of 2-character names at the second level has been the subject of extensive public consultation. The ALAC did comment on these and explicitly said we did not see any problems with that. This was a result of discussion and consultation within-At-Large. The call for comments on our first such statement can be seen at http://atlarge-lists.icann.org/pipermail/alac-announce/2014q3/001875.html. The net result was that we supported the release of such names. Note that the approval to release such names does not compel a registry to release them, it only allows them to make such a decision. * You can see the history of our full process on this by going to https://atlarge.icann.org/policy-summaryand doing a search on statement titles including the words TWO CHARACTER DOMAIN. * The contract amendment to include additional RDDS fields was made at the explicit request of the registry to allow .nyc to satisfy the nexus requirements of the registry (that is, to allow verification that the registrant does have a connection with New York City (http://www.ownit.nyc/policies/nyc_nexus_policy.php). The request by the registry can be viewed at https://www.icann.org/en/system/files/files/rsep-2016002-nyc-request-04jan16.... Such Registry Service Evaluation Process (RSEP) requests can be viewed athttps://www.icann.org/resources/pages/rsep-2014-02-19-en. The overall process followed in RSEP can be seen at https://www.icann.org/resources/pages/workflow-2012-02-25-en. The process requires a formal public comment only if there is the possibility (based on a "quick look" review) of a security or stability issue (which it did not in this case). * The RSEP is the result of one of the early GNSO Consensus Policy Development Processes - http://gnso.icann.org/en/issues/registry-services/final-rpt-registry-approva.... That process was of course subject to public comments and the resultant policy was widely supported.
Tom, you have also addressed this as a question to the candidates for the NARALO ALAC Member selection and in that capacity I will be glad to address this issue at the meeting tomorrow. However, since you have sent this to the entire NARALO list, the answer has far more to it than can be addressed on our candidate teleconference, and many of the recipients will not likely be at that meeting, I thought it appropriate to reply here as well. In the name of transparency I will note that you had already addressed a similar question to the NARALO ALAC Members about two weeks ago, and I did address what I understood to be the issues at that time. I see that you copied the majority of my reply to you below under the title "Basis for ICANN approval of 4 .nyc TLD registry agreement changes". This was presented as my personal understanding and not necessarily the "basis" for the changes. And for the record, I am proudly an Unaffiliated Member of NARALO and not a fellow ALSer. ;-) On to substance. .nyc is Generic Top Level Domain granted under the 2010 round of New gTLDs. It is under the sole control of the applicant and now registry operator, The City of New York through its Department of Information Technology & Telecommunications. It is of course subject to all of the ICANN policy associated with gTLDs. When I say "sole control", that is of course subject to the terms of its contract and and other organization' s restrictions. Many city TLDs chose to also be "community" TLDs (examples are .berlin, .madrid, .paris and .osaka), and in that case, they would also be responsible to the community that supported the application, and that responsibility might include some of the user connections that you desire, But even in those cases, it would depend on the specifics of the contracts and relationships. Regardless of the details, the Registry Agreement is a legal contract between ICANN and the Registry Operator, and its amendment is governed by a host of ICANN policies. At-Large through the ALAC, and with the RALOs and ALSes has a significant ability to influence many issues. That was not always the case, and we certainly do not implicitly overrule others in the multistakeholder community, but we are heard. That being said, one of the prime purposes of ICANN is to establish policy in the gTLD arena. And we do. But of course, once that policy is established, we have to follow it. To look at one of the perhaps less onerous examples you gave, the contract amendment to add several new data fields to the Registration Data Directory (formerly WHOIS). These fields allow the registry to request that all registrants provide information indicating that they are indeed eligible to have a .nyc domain name. Despite the seeming simplicity of the change, how a registry is granted the right to do this is through making a request to establish a new Registry Service (Registry Services is a specifically defined term). The Registry Services Evaluation Policy (RSEP) governs such changes. The RSEP is one of the earlier Consensus Policies establish within ICANN through MS Model deliberations. RSEP evaluates the change for potential security, stability or competition issues. If it has any of these a consultative process is started which ultimately might result in a the ALAC submitted a comment on the proposed registry service (we have done this a number of times). If it has no security, stability or competition issues, then the request is approved, and in this case, required a contract amendment (since the RDS fields are explicitly listed in the Registry Agreement. Now, on to your question, can At-Large change this process to allow for more and explicit consultation. Yes, we can. (Whether we want to or not is a different question - with the New gTLDs, there were about 90 such requests in 2015.) We can cause the policy to be reviewed and potentially changed. I can speak with some authority on the process because I have initiated it twice, and in both cases, the end result was a new gTLD policy that, in my mind and those of many others, significantly improved the gTLD namespace. If you think that this issue is one worthy of the effort it will take to effect the change you want, I encourage you to learn more about the process. I will say (and I have the scars to prove it), you will need to convince a lot of other people that there is a problem and that it is worth addressing. The other amendments are related to 2-character 2nd-level names. As I have mentioned in my earlier reply, this subject has been the topic of a number of formal Public Comments and the ALAC did contribute. I do not recall how much ALS input there was into these processes, but there was surely the opportunity for input at many level. You ask whether your ALS, which clearly has a great interest in the .nyc TLD, should be consulted before the .nyc agreement is modified. I see no way that we can make a specific link between your ALS and the TLD unless the registry chooses to do so. The more general question is whether the wider community should be notified of potential contractual amendments and have an opportunity to comment. That is certainly an issue that could be raised, as with changing RSEP, we would need to make a strong case that there is a problem and that is is worth of community time to address. Regarding the use .us as a model. .us is a ccTLD which operates under a completely different set of rules and constraints. At some level (certainly for a redelegation or transfer of a ccTLD to a new operator), there must be some demonstration that the interested parties within the country/territory support the registry operator and their policies. Of course, the form this takes, and the actual level of real support, varies greatly from country to country. .us was historically operated by Verisign and was redelegated to NeuStar in 2001 (https://www.icann.org/news/announcement-2001-11-19-en). I don't know if the .usTLD Stakeholder Council was put in place out of a sense of public interest, or whether they had to commit to it in order to satisfy the US Government's procurement process. It is certainly a model that can be used for how .nyc should be operated, but perhaps unfortunately, there is nothing in the current policies that could compel .nyc, as a delegated TLD, to adopt such a policy other than voluntarily. On the other hand, if your aim is to make sure that this type of problem does not happen again, a GNSO PDP on setting the policies for any future gTLD rounds (or other methods of release) has just started. It is doing a full review of all policies, and you (and anyone else) are welcome to take an active part in it. See https://community.icann.org/x/RgV1Aw to sign up. Regards, Alan At 08/05/2016 12:04 AM, Thomas Lowenhaupt wrote:
Fellow NARALO Members,
ICANN granted the city of New York the right to issue domain names using the .nyc TLD in January 2014. As of May 1, 2016, 76,682 names had been issued to individuals and organizations.
Connecting.nyc Inc. is an At-Large Structure associated with the ICANN and an active participant in its multistakeholder governance process. With our focus on the development of the .nyc TLD as a public interest resource, I recently reviewed the .nyc Registry Agreement page on ICANN's website <<https://www.icann.org/resources/agreement/nyc-2014-01-23-en>https://www.icann.org/resources/agreement/nyc-2014-01-23-en>, and noted that four changes to the original agreement had been recorded there. Three were under the heading "Authorization(s) for Release of Reserved Names," as follows: * All Digit/Digit, Letter/Digit, and Digit/Letter Two-Character ASCII Labels at the Second Level (01 December 2014) <<https://www.icann.org/en/system/files/files/spec5-amend-two-char-01dec14-en.pdf>https://www.icann.org/en/system/files/files/spec5-amend-two-char-01dec14-en.pdf>
* Letter/Letter Two-Character ASCII Labels (26 May 2015) <<https://www.icann.org/sites/default/files/tlds/nyc/nyc-auth-ltr-ltr-26may15-en.pdf>https://www.icann.org/sites/default/files/tlds/nyc/nyc-auth-ltr-ltr-26may15-en.pdf>
* Letter/Letter Two-Character ASCII Labels (14 March 2016) <<https://www.icann.org/sites/default/files/tlds/nyc/nyc-auth-ltr-ltr-14mar16-en.pdf>https://www.icann.org/sites/default/files/tlds/nyc/nyc-auth-ltr-ltr-14mar16-en.pdf>
The fourth was listed under "Amendment No.1 (31 March 2016)": * PDF <<https://www.icann.org/sites/default/files/tlds/nyc/nyc-amend-1-pdf-31mar16-en.pdf>https://www.icann.org/sites/default/files/tlds/nyc/nyc-amend-1-pdf-31mar16-en.pdf> This PDF amendment deals with the addition of 14 new data fields to the Registration Data Directory.
The existence of these changes came as a complete surprise to me. As Chair of Connecting.nyc Inc., a NYS nonprofit created in 2007 to engage and educate New Yorkers about the use of the .nyc TLD, and as an active participant in ICANN's governance processes through our association as an At-Large Structure, I had presumed we would have been consulted about changes to the registry agreement.
My desire for inclusion of individual Internet users in consultations about future registry changes provides the basis for this message.
Note: An earlier email on this general subject led some to think I was challenging the 4 registry changes as being out of compliance with approved ICANN procedures. This is not the case. And based on my perusal of precedent references kindly provided by a fellow ALSer (see them below), Iâd say that ICANN and the city followed the âletter of the law.â However...
However, I do question the efficacy of a process that allows changes to a registry agreement without taking full advantage of the existing machinery of governance, i.e., the multistakeholder model and the extant At-Large Structures (ISOC-NY is also a NYC based ALS). With the Internet community having settled on a multistakeholder governance model, one would imagine that our ALS would be involved in changing the basic agreement that guides the operation of the .nyc TLD.
But perhaps we were excluded from the review process for good reason, for example, that the cityâs governance structure more effectively represents the needs of the various stakeholders than the Internetâs multistakeholder model. After all, New York City does have a democratic governance system, and a general election was held in November 2013. Perhaps it's thought the people thereby approved or acquiesced to the registry agreement, and thus, in the eyes of ICANN, a city-based ALS should not have a formal role. If this is the situation, I would appreciate someone pointing me to the relevant guidelines. For indeed...
At this point, the city is acting as if there is no role for its residents in a traditional multistakeholder model. While there was a 20 month period during which the city acknowledged the role of the residents and users through a .NYC Community Advisory Board (May 2013 - December 2014), the city unilaterally decided that entity should cease to exist on January 1, 2015. And to my dismay, it followed this decision by eliminating all reference to the .NYC Community Advisory Boardâs very existence from the cityâs website.
NOTE: To my knowledge city government has not been provided with any requirement or guideline about the operation of an inclusive, multistakeholder governance process for the .nyc TLD. So Iâm not faulting the city administration for the current state of affairs. To do so would be to assume greater awareness and concomitant responsibility about this new resource than is seemingly warranted.
Whatâs to be done?
This email seeks the assistance or NARALO in learning if Connecting.nyc Inc. should be provided with an opportunity to consult and consent to future registry agreement changes. We see precedent for this with the .us TLD.
The .us TLD is currently governed with the assistance of a .usTLD Stakeholder Council: <http://www.neustar.us/ustld-stakeholder-council/structure-and-history/>http://www.neustar.us/ustld-stakeholder-council/structure-and-history/. The council has a <http://www.neustar.us/ustld-stakeholder-council/charter/>charter, <http://www.neustar.us/ustld-stakeholder-council/ustld-stakeholder-council-operating-procedures/>operating procedures, a membership (which is appointed by the contractor!), and operational parameters (see usTLD Administrative Component graphic below).
If it is the consensus that we are inappropriately outside the extant "consultation loop" I suggest that NARALO initiate a review to determine if the current process should be changed to more closely align with the tenets of the multistakeholder governance system that underpins the operation of ICANN and the Internet.
Sincerely,
Thomas Lowenhaupt
----------
Basis for ICANN approval of 4 .nyc TLD registry agreement changes
* The release of 2-character names at the second level has been the subject of extensive public consultation. The ALAC did comment on these and explicitly said we did not see any problems with that. This was a result of discussion and consultation within-At-Large. The call for comments on our first such statement can be seen at <http://atlarge-lists.icann.org/pipermail/alac-announce/2014q3/001875.html>http://atlarge-lists.icann.org/pipermail/alac-announce/2014q3/001875.html. The net result was that we supported the release of such names. Note that the approval to release such names does not compel a registry to release them, it only allows them to make such a decision. * You can see the history of our full process on this by going to <https://atlarge.icann.org/policy-summary>https://atlarge.icann.org/policy-summary and doing a search on statement titles including the words TWO CHARACTER DOMAIN. * The contract amendment to include additional RDDS fields was made at the explicit request of the registry to allow .nyc to satisfy the nexus requirements of the registry (that is, to allow verification that the registrant does have a connection with New York City (<http://www.ownit.nyc/policies/nyc_nexus_policy.php>http://www.ownit.nyc/policies/nyc_nexus_policy.php). The request by the registry can be viewed at <https://www.icann.org/en/system/files/files/rsep-2016002-nyc-request-04jan16-en.pdf>https://www.icann.org/en/system/files/files/rsep-2016002-nyc-request-04jan16-en.pdf. Such Registry Service Evaluation Process (RSEP) requests can be viewed at <https://www.icann.org/resources/pages/rsep-2014-02-19-en>https://www.icann.org/resources/pages/rsep-2014-02-19-en. The overall process followed in RSEP can be seen at <https://www.icann.org/resources/pages/workflow-2012-02-25-en>https://www.icann.org/resources/pages/workflow-2012-02-25-en. The process requires a formal public comment only if there is the possibility (based on a "quick look" review) of a security or stability issue (which it did not in this case). * The RSEP is the result of one of the early GNSO Consensus Policy Development Processes - <http://gnso.icann.org/en/issues/registry-services/final-rpt-registry-approval-10july05.htm>http://gnso.icann.org/en/issues/registry-services/final-rpt-registry-approval-10july05.htm. That process was of course subject to public comments and the resultant policy was widely supported.
Content-Type: image/png;
name="CqUBoKoO57Ys6mRwGOc4PEv_FsQwDJoMfH-n9skqModIU8zCCOi6h1jfJBAz7q8BmxymzToDervRbdXUQh5zhTbRlftGScN3qDUjOu8jfRhDoTClAOnVZH3h_tq-xxsoeYWeO1bt" Content-ID: <part9.A530C394.8ADF4F98@communisphere.com> Content-Disposition: inline;
filename*0="CqUBoKoO57Ys6mRwGOc4PEv_FsQwDJoMfH-n9skqModIU8zCCOi6h1jfJBAz";
filename*1="7q8BmxymzToDervRbdXUQh5zhTbRlftGScN3qDUjOu8jfRhDoTClAOnVZH3h"; filename*2="_tq-xxsoeYWeO1bt" X-Microsoft-Exchange-Diagnostics:
1;SN1PR0301MB2030;9:Ug/DpD5yV4BmxIyugixxRGSsv3hRKWl1cx4WR/W9B/DtnY/xrrrktnmxdbgHeoZ4NIEHvpIejuwurBKdd3ijsjFutMqZelfdip/H2/H9RXrkf/LjbaAg6dB8KKAqfPLzGJlR8Rg2C/NGCrUollB4EckY1E4jXhEip+BsLLKwU1c=
Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Microsoft-Exchange-Diagnostics:
1;SN1PR0301MB2030;9:Ug/DpD5yV4BmxIyugixxRGSsv3hRKWl1cx4WR/W9B/DtnY/xrrrktnmxdbgHeoZ4NIEHvpIejuwurBKdd3ijsjFutMqZelfdip/H2/H9RXrkf/LjbaAg6dB8KKAqfPLzGJlR8Rg2C/NGCrUollB4EckY1E4jXhEip+BsLLKwU1c=
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online at http://www.naralo.org ------
On Wed, May 11, 2016 at 10:38 AM, Alan Greenberg <alan.greenberg@mcgill.ca> wrote:
there is nothing in the current policies that could compel .nyc, as a delegated TLD, to adopt such a policy other than voluntarily.
Thanks for your thoughtful and detailed response, Alan. Tom, it does seem that your efforts might be better directed at stirring things up at a local level, but I think there has to be perceptible pain to get any movement.The tradeoffs between privacy, WHOIS and the nexus requirement might be a source of such pain. Currently, since proxy addresses are forbidden under the nexus policy, no private citizen in NYC can register a .nyc domain with revealing their personal address via WHOIS. The allocation and oversight of neighborhood reserved names, as per your recent meetup, is another. j -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -
The point I'm trying to make is: If we've all accepted the multistakeholder model, how is it that the local ALSes and individual Internet users (residents and organizations as well) are left out of the decision making process? Tom On 5/11/2016 11:14 AM, Joly MacFie wrote:
On Wed, May 11, 2016 at 10:38 AM, Alan Greenberg <alan.greenberg@mcgill.ca <mailto:alan.greenberg@mcgill.ca>> wrote:
there is nothing in the current policies that could compel .nyc, as a delegated TLD, to adopt such a policy other than voluntarily.
Thanks for your thoughtful and detailed response, Alan.
Tom, it does seem that your efforts might be better directed at stirring things up at a local level, but I think there has to be perceptible pain to get any movement.The tradeoffs between privacy, WHOIS and the nexus requirement might be a source of such pain. Currently, since proxy addresses are forbidden under the nexus policy, no private citizen in NYC can register a .nyc domain with revealing their personal address via WHOIS. The allocation and oversight of neighborhood reserved names, as per your recent meetup, is another.
j
-- --------------------------------------------------------------- Joly MacFie 218 565 9365 <tel:218%20565%209365> Skype:punkcast -------------------------------------------------------------- -
Your question presumes we are all left out of decision making processes. I do not agree. ICANN holds many public consultations where anyone may provide input and be considered. Some people have claimed there are too many such consultations. In addition to any individual or organization's ability to submit comments, the ALAC often does on behalf of the At-Large Community. The ALAC is empowered to provide advice on any subject at any time. And when an issue arises that the ALAC feels deserves such treatment we do so. And in many and probably most cases, there is an opportunity for our entire community to participate in the development of the advice. In other decisions, there is an established policy that guides how that decision is made. The RSEP process is one such example. The multistakeholder (MS) community was the source of that policy, and once adopted (and until it is changed by a MS process), it is followed. That policy allows for community input in some cases, and in others it was decided (by the community) that input on individual application of the policy was not needed. The RSEP policy could be altered if there was a general perception that it is broken or was no longer appropriate. As another example of this, the 2010 round of New gTLD Applications was governed by an immense set of policies and procedures as described in the Applicant Guide Book. An applicant, by making an application agreed to abide by the rules, and ICANN, in accepting the fee, also agreed to such rules. Among them was that once a complex set of criteria was met, ICANN would sign a Registry Agreement with the applicant. There was a lot of public involvement at many stages, but the actual signing of a contract did not (according to the rules establish with the overall community) did not require public input. Some decisions are controlled by contracts and in those cases, whatever is in the contract dictates how things happen. The release of two character strings at the 2nd level in new gTLDs was the subject of significant public comment, but was also subject to the agreement of the country or territory that has that string as a ccTLD-type string. It is within the realm of possibility that ICANN could adopt a policy by which every single contract and contract amendment. I am pretty sure there would not be a lot of support for such a proposition, and there would be a high cost of implementing it. But it could happen if there were a general will to make it so. Alan At 12/05/2016 12:09 AM, Thomas Lowenhaupt wrote:
The point I'm trying to make is: If we've all accepted the multistakeholder model, how is it that the local ALSes and individual Internet users (residents and organizations as well) are left out of the decision making process?
Tom
On 5/11/2016 11:14 AM, Joly MacFie wrote:
On Wed, May 11, 2016 at 10:38 AM, Alan Greenberg <<mailto:alan.greenberg@mcgill.ca>alan.greenberg@mcgill.ca> wrote: there is nothing in the current policies that could compel .nyc, as a delegated TLD, to adopt such a policy other than voluntarily.
âThanks for your thoughtful and detailed response, Alan.
Tom, it does seem that your efforts might be better directed at stirring things up at a localâ level, but I think there has to be perceptible pain to get any movement.The tradeoffs between privacy, WHOIS and the nexus requirement might be a source of such pain. Currently, since proxy addresses are forbidden under the nexus policy, no private citizen in NYC can register a .nyc domain with revealing their personal address via WHOIS. The allocation and oversight of neighborhood reserved names, as per your recent meetup, is another.
j
-- --------------------------------------------------------------- Joly MacFie <tel:218%20565%209365>218 565 9365 <Skype:punkcast>Skype:punkcast -------------------------------------------------------------- -
Alan, Comments in-line. On 5/12/2016 1:09 AM, Alan Greenberg wrote:
Your question presumes we are all left out of decision making processes. I do not agree.
Depends on who "we" is. Typically it those with the time an resources to participate that steer the decision-making process. And that seems to hold here.
ICANN holds many public consultations where anyone may provide input and be considered. Some people have claimed there are too many such consultations. In addition to any individual or organization's ability to submit comments, the ALAC often does on behalf of the At-Large Community.
It's a bit of a paradox - for the insider there are too many meetings. For those outside that process there aren't enough, or at lease enough accessible meetings (in terms of awareness and time). It's been my experience that you've got to take this on as a full time job to be effective. For example, in a PDP-like process reviewing the new TLD experience I submitted the first comment to the group recommending that cities applying for TLDs in the future be required to demonstrate "informed consent." And I commented on this to the ICANN board of directors at a public meeting (perhaps in Buenos Aires). By the end of that process I couldn't find mention of my contribution in the official record (someone said it was in the appendix, but I couldn't find it). I see there's a new PDP starting on the process that will likely lead to additional TLDs being issued to cities. How do I get the ALAC to take up this task on behalf of IIUs in cities globally?
The ALAC is empowered to provide advice on any subject at any time. And when an issue arises that the ALAC feels deserves such treatment we do so. And in many and probably most cases, there is an opportunity for our entire community to participate in the development of the advice.
But that didn't happen in these instances. 4 changes were made to the registry agreement without (to my knowledge) a single ALS or IIU (Individual Internet Users) in New York City aware of the impending changes or their possible impact and consequences.
In other decisions, there is an established policy that guides how that decision is made. The RSEP process is one such example. The multistakeholder (MS) community was the source of that policy, and once adopted (and until it is changed by a MS process), it is followed. That policy allows for community input in some cases, and in others it was decided (by the community) that input on individual application of the policy was not needed. The RSEP policy could be altered if there was a general perception that it is broken or was no longer appropriate.
The RSEP process was set in 2004 when there was minimal input from ALAC and zero input from the 8,000,000 residents that comprise the New York City community. And now that process allows changes to the registry without any public engagement of the city's IIUs (or businesses, or schools, or or or). I can see the history of this and it is all quite normal. But saying that the ALAC can intervene and giving reasons why it hasn't is hardly reassuring.
As another example of this, the 2010 round of New gTLD Applications was governed by an immense set of policies and procedures as described in the Applicant Guide Book. An applicant, by making an application agreed to abide by the rules, and ICANN, in accepting the fee, also agreed to such rules. Among them was that once a complex set of criteria was met, ICANN would sign a Registry Agreement with the applicant. There was a lot of public involvement at many stages, but the actual signing of a contract did not (according to the rules establish with the overall community) did not require public input.
Some decisions are controlled by contracts and in those cases, whatever is in the contract dictates how things happen.
The release of two character strings at the 2nd level in new gTLDs was the subject of significant public comment, but was also subject to the agreement of the country or territory that has that string as a ccTLD-type string.
I've been having a conversation with my city council member about using these to benefit the various immigrant communities. Had Connecting.nyc Inc. been aware of change request, perhaps some additional action might have been taken.
It is within the realm of possibility that ICANN could adopt a policy by which every single contract and contract amendment. I am pretty sure there would not be a lot of support for such a proposition, and there would be a high cost of implementing it. But it could happen if there were a general will to make it so.
A simple notice about the proposed changes to the agreement and providing an opportunity to comment should not cripple ICANN's budget. How do we make this happen? Thanks for your thoughts on this matter. Tom Lowenhaupt
Alan
At 12/05/2016 12:09 AM, Thomas Lowenhaupt wrote:
The point I'm trying to make is: If we've all accepted the multistakeholder model, how is it that the local ALSes and individual Internet users (residents and organizations as well) are left out of the decision making process?
Tom
On 5/11/2016 11:14 AM, Joly MacFie wrote:
On Wed, May 11, 2016 at 10:38 AM, Alan Greenberg <alan.greenberg@mcgill.ca <mailto:alan.greenberg@mcgill.ca> > wrote:
there is nothing in the current policies that could compel .nyc, as a delegated TLD, to adopt such a policy other than voluntarily.
​Thanks for your thoughtful and detailed response, Alan.
Tom, it does seem that your efforts might be better directed at stirring things up at a local​ level, but I think there has to be perceptible pain to get any movement.The tradeoffs between privacy, WHOIS and the nexus requirement might be a source of such pain. Currently, since proxy addresses are forbidden under the nexus policy, no private citizen in NYC can register a .nyc domain with revealing their personal address via WHOIS. The allocation and oversight of neighborhood reserved names, as per your recent meetup, is another.
j
-- --------------------------------------------------------------- Joly MacFie 218 565 9365 <tel:218%20565%209365> Skype:punkcast -------------------------------------------------------------- -
On Thu, May 12, 2016 at 12:09 AM, Thomas Lowenhaupt <toml@communisphere.com> wrote:
The point I'm trying to make is: If we've all accepted the multistakeholder model, how is it that the local ALSes and individual Internet users (residents and organizations as well) are left out of the decision making process?
Tom
But are we? ALS's and individuals can join RALOs, who inturn can influence the ALAC, who advise the ICANN board. Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory. There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely. j -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -
Joly, In response to my post contending that the multistakeholder model was not effectively meeting the needs of individual Internet users (IIUs) in New York City you said: * "But are we? ALS's and individuals can join RALOs, who in turn can influence the ALAC, who advise the ICANN board." That's correct. And that's what I'm doing right now. * "Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory." Following that line of thought we really don't need a city council or mayor at all. After all, we also have a democratically elected congress and president. Why bother with city government? Just call your congress member about the pothole, garbage pickup, or idea for a park improvement. And indeed you can. But my congress member represents about 700,000 people and avers to the local council member who represents 160,000 residents. He has close ties, that include budgetary control, with the local service providers - the pothole fillers, sanitation and parks departments. So for local service delivery issues it's better to go local. And in this instance, with .nyc, I think we have agreed to go down one more layer and engage the stakeholders in the process. And indeed, ICANN talks bottom-up and multistakeholder. Minimally, minimally, ICANN could send a notification to the local ALSs when a city registry agreement change is proposed. And it would seem reasonable to provide the opportunity for that ALS to respond, and for that response to be considered. One might argue that it is the ALS's responsibility to keep an eye on ICANN's activities. And that's a good idea. And I support and look forward to the day when we're provided by ICANN with a budget to hire a staff member for that task. But for now it seems ICANN's generating a letter about proposed changes to the registry agreement is the simpler way to go. * "There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely." As I recall the situation, the city created the advisory board under duress - there was a challenge to their .nyc application from Connecting.nyc Inc. After the .NYC Community Advisory Board's creation the city retained tight control over its operation. It appointed members, scheduled the meetings, and set the agenda. I informed media-types about the meetings, but they were excluded by the representatives of the mayor. Additionally, even city officials were excluded. Council member Gale Brewer's representative, whom I invited, was told to leave the room when he showed up. And as I mentioned previously, when they abolished it on December 31, 2014 they wiped out any sign of its existence from its website. But you're right, those chains probably could have been broken short of self-immolation. I just never figured out how. Where are we now? While we've taken a hit with the abolition of the .NYC Community Advisory Board, I'm still trying to get a governance process started where IIUs can meaningfully participate in a governance process. My latest thought is to get ICANN, via the ALSs, on board and advocating for a multistakeholder governance process, one that includes IIUs. Any thoughts on how to achieve this are most welcomed. Best, Tom Lowenhaupt On 5/12/2016 1:19 AM, Joly MacFie wrote:
On Thu, May 12, 2016 at 12:09 AM, Thomas Lowenhaupt <toml@communisphere.com <mailto:toml@communisphere.com>> wrote:
The point I'm trying to make is: If we've all accepted the multistakeholder model, how is it that the local ALSes and individual Internet users (residents and organizations as well) are left out of the decision making process?
Tom
But are we? ALS's and individuals can join RALOs, who inturn can influence the ALAC, who advise the ICANN board.
Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory.
There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.
j
-- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -
Hi Tom, Why is the situation rather opaque in .NYC. Because inclusiveness is not promoted ? Because transparency is not an integrated process in the pratices of the management team (the meetings are held behind closed doors? ) Governments obey to a set of rules and processes that they control. This includes the input or contribution from third parties regarding the direction to follow the management approach, etc. I understand that this the situation that you're cought with. Your suggestion to get ICANN on board is certainly appropriate. Is it the only approach for you to advocate for a governance process for NYC? I don't know if other city TLD are facing a similar situation as the one you described. For instance, Dot-Paris is managed by the city under the authority of the mayer. Would it be useful to document how they address governance issues including the multistakeholder model ? Would it be useful to get the GeoTLD Interest Group on board also? At Dot-Quebec, the Board adopted a very openned governance approach. Anybody who can contribute is welcome, but it's a not-for-profit organisation. It's not lead by the government even though we received a financial and political support for the project. We support the multistakeholder model but for the new members of the Board, it needs to be explained. We have people with various and strong CV, but mostly no ICANN experience for some of them. Knowledge sharing is useful then, but it is still necessary to have a partner who is willing to listen. Regards Louis Houle President ISOC Quebec Louis.Houle@isoc.quebec Le 2016-05-12 12:49, Thomas Lowenhaupt a écrit :
Joly,
In response to my post contending that the multistakeholder model was not effectively meeting the needs of individual Internet users (IIUs) in New York City you said:
* "But are we? ALS's and individuals can join RALOs, who in turn can influence the ALAC, who advise the ICANN board."
That's correct. And that's what I'm doing right now.
* "Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory."
Following that line of thought we really don't need a city council or mayor at all. After all, we also have a democratically elected congress and president. Why bother with city government? Just call your congress member about the pothole, garbage pickup, or idea for a park improvement. And indeed you can. But my congress member represents about 700,000 people and avers to the local council member who represents 160,000 residents. He has close ties, that include budgetary control, with the local service providers - the pothole fillers, sanitation and parks departments. So for local service delivery issues it's better to go local. And in this instance, with .nyc, I think we have agreed to go down one more layer and engage the stakeholders in the process. And indeed, ICANN talks bottom-up and multistakeholder. Minimally, minimally, ICANN could send a notification to the local ALSs when a city registry agreement change is proposed. And it would seem reasonable to provide the opportunity for that ALS to respond, and for that response to be considered. One might argue that it is the ALS's responsibility to keep an eye on ICANN's activities. And that's a good idea. And I support and look forward to the day when we're provided by ICANN with a budget to hire a staff member for that task. But for now it seems ICANN's generating a letter about proposed changes to the registry agreement is the simpler way to go.
* "There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely."
As I recall the situation, the city created the advisory board under duress - there was a challenge to their .nyc application from Connecting.nyc Inc. After the .NYC Community Advisory Board's creation the city retained tight control over its operation. It appointed members, scheduled the meetings, and set the agenda. I informed media-types about the meetings, but they were excluded by the representatives of the mayor. Additionally, even city officials were excluded. Council member Gale Brewer's representative, whom I invited, was told to leave the room when he showed up. And as I mentioned previously, when they abolished it on December 31, 2014 they wiped out any sign of its existence from its website. But you're right, those chains probably could have been broken short of self-immolation. I just never figured out how. Where are we now? While we've taken a hit with the abolition of the .NYC Community Advisory Board, I'm still trying to get a governance process started where IIUs can meaningfully participate in a governance process. My latest thought is to get ICANN, via the ALSs, on board and advocating for a multistakeholder governance process, one that includes IIUs. Any thoughts on how to achieve this are most welcomed.
Best,
Tom Lowenhaupt
On 5/12/2016 1:19 AM, Joly MacFie wrote:
On Thu, May 12, 2016 at 12:09 AM, Thomas Lowenhaupt <toml@communisphere.com> wrote:
The point I'm trying to make is: If we've all accepted the multistakeholder model, how is it that the local ALSes and individual Internet users (residents and organizations as well) are left out of the decision making process?
Tom
But are we? ALS's and individuals can join RALOs, who inturn can influence the ALAC, who advise the ICANN board.
Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory.
There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.
j
-- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online at http://www.naralo.org ------
Louis, It certainly would be good to know the level of engagement for IIUs in Paris and the other newly TLD'd cities. Perhaps the At-Large could craft a questionnaire to gather the state of affairs, to be distributed as widely as practicable. Certainly one might imagine excellent penetration in those cities with ALSes. From there we might develop a report of use to many. What's the best tool for creating a questionnaire these days? Surveymonkey <https://www.surveymonkey.com/> seems to be priced right? Anyone with experience in this area? Is there a better alternative? Are there others in the ICANN community that might be interested in a project of this sort? Best, Tom Lowenhaupt On 5/13/2016 2:51 PM, Louis Houle wrote:
Hi Tom,
Why is the situation rather opaque in .NYC. Because inclusiveness is not promoted ? Because transparency is not an integrated process in the pratices of the management team (the meetings are held behind closed doors? )
Governments obey to a set of rules and processes that they control. This includes the input or contribution from third parties regarding the direction to follow the management approach, etc. I understand that this the situation that you're cought with.
Your suggestion to get ICANN on board is certainly appropriate. Is it the only approach for you to advocate for a governance process for NYC? I don't know if other city TLD are facing a similar situation as the one you described. For instance, Dot-Paris is managed by the city under the authority of the mayer. Would it be useful to document how they address governance issues including the multistakeholder model ? Would it be useful to get the GeoTLD Interest Group on board also?
At Dot-Quebec, the Board adopted a very openned governance approach. Anybody who can contribute is welcome, but it's a not-for-profit organisation. It's not lead by the government even though we received a financial and political support for the project. We support the multistakeholder model but for the new members of the Board, it needs to be explained. We have people with various and strong CV, but mostly no ICANN experience for some of them. Knowledge sharing is useful then, but it is still necessary to have a partner who is willing to listen.
Regards
Louis Houle President ISOC Quebec Louis.Houle@isoc.quebec
Le 2016-05-12 12:49, Thomas Lowenhaupt a écrit :
Joly,
In response to my post contending that the multistakeholder model was not effectively meeting the needs of individual Internet users (IIUs) in New York City you said:
* "But are we? ALS's and individuals can join RALOs, who in turn can influence the ALAC, who advise the ICANN board."
That's correct. And that's what I'm doing right now.
* "Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory."
Following that line of thought we really don't need a city council or mayor at all. After all, we also have a democratically elected congress and president. Why bother with city government? Just call your congress member about the pothole, garbage pickup, or idea for a park improvement. And indeed you can. But my congress member represents about 700,000 people and avers to the local council member who represents 160,000 residents. He has close ties, that include budgetary control, with the local service providers - the pothole fillers, sanitation and parks departments. So for local service delivery issues it's better to go local. And in this instance, with .nyc, I think we have agreed to go down one more layer and engage the stakeholders in the process. And indeed, ICANN talks bottom-up and multistakeholder. Minimally, minimally, ICANN could send a notification to the local ALSs when a city registry agreement change is proposed. And it would seem reasonable to provide the opportunity for that ALS to respond, and for that response to be considered. One might argue that it is the ALS's responsibility to keep an eye on ICANN's activities. And that's a good idea. And I support and look forward to the day when we're provided by ICANN with a budget to hire a staff member for that task. But for now it seems ICANN's generating a letter about proposed changes to the registry agreement is the simpler way to go.
* "There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely."
As I recall the situation, the city created the advisory board under duress - there was a challenge to their .nyc application from Connecting.nyc Inc. After the .NYC Community Advisory Board's creation the city retained tight control over its operation. It appointed members, scheduled the meetings, and set the agenda. I informed media-types about the meetings, but they were excluded by the representatives of the mayor. Additionally, even city officials were excluded. Council member Gale Brewer's representative, whom I invited, was told to leave the room when he showed up. And as I mentioned previously, when they abolished it on December 31, 2014 they wiped out any sign of its existence from its website. But you're right, those chains probably could have been broken short of self-immolation. I just never figured out how. Where are we now? While we've taken a hit with the abolition of the .NYC Community Advisory Board, I'm still trying to get a governance process started where IIUs can meaningfully participate in a governance process. My latest thought is to get ICANN, via the ALSs, on board and advocating for a multistakeholder governance process, one that includes IIUs. Any thoughts on how to achieve this are most welcomed.
Best,
Tom Lowenhaupt
On 5/12/2016 1:19 AM, Joly MacFie wrote:
On Thu, May 12, 2016 at 12:09 AM, Thomas Lowenhaupt <toml@communisphere.com> wrote:
The point I'm trying to make is: If we've all accepted the multistakeholder model, how is it that the local ALSes and individual Internet users (residents and organizations as well) are left out of the decision making process?
Tom
But are we? ALS's and individuals can join RALOs, who inturn can influence the ALAC, who advise the ICANN board.
Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory.
There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.
j
-- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online athttp://www.naralo.org ------
As a first step, perhaps you should look at all of the application forms and registry agreements, particularly for those that are Community TLDs, and see what they committed to. -- Sent from my mobile. Please excuse brevity and typos. On May 13, 2016 4:16:47 PM EDT, Thomas Lowenhaupt <toml@communisphere.com> wrote:
Louis,
It certainly would be good to know the level of engagement for IIUs in Paris and the other newly TLD'd cities. Perhaps the At-Large could craft a questionnaire to gather the state of affairs, to be distributed as widely as practicable. Certainly one might imagine excellent penetration in those cities with ALSes. From there we might develop a report of use
to many.
What's the best tool for creating a questionnaire these days? Surveymonkey <https://www.surveymonkey.com/> seems to be priced right? Anyone with experience in this area? Is there a better alternative? Are
there others in the ICANN community that might be interested in a project of this sort?
Best,
Tom Lowenhaupt
On 5/13/2016 2:51 PM, Louis Houle wrote:
Hi Tom,
Why is the situation rather opaque in .NYC. Because inclusiveness is not promoted ? Because transparency is not an integrated process in the pratices of the management team (the meetings are held behind closed doors? )
Governments obey to a set of rules and processes that they control. This includes the input or contribution from third parties regarding the direction to follow the management approach, etc. I understand that this the situation that you're cought with.
Your suggestion to get ICANN on board is certainly appropriate. Is it
the only approach for you to advocate for a governance process for NYC? I don't know if other city TLD are facing a similar situation as
the one you described. For instance, Dot-Paris is managed by the city
under the authority of the mayer. Would it be useful to document how they address governance issues including the multistakeholder model ?
Would it be useful to get the GeoTLD Interest Group on board also?
At Dot-Quebec, the Board adopted a very openned governance approach. Anybody who can contribute is welcome, but it's a not-for-profit organisation. It's not lead by the government even though we received
a financial and political support for the project. We support the multistakeholder model but for the new members of the Board, it needs
to be explained. We have people with various and strong CV, but mostly no ICANN experience for some of them. Knowledge sharing is useful then, but it is still necessary to have a partner who is willing to listen.
Regards
Louis Houle President ISOC Quebec Louis.Houle@isoc.quebec
Le 2016-05-12 12:49, Thomas Lowenhaupt a écrit :
Joly,
In response to my post contending that the multistakeholder model was not effectively meeting the needs of individual Internet users (IIUs) in New York City you said:
* "But are we? ALS's and individuals can join RALOs, who in turn can influence the ALAC, who advise the ICANN board."
That's correct. And that's what I'm doing right now.
* "Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory."
Following that line of thought we really don't need a city council or mayor at all. After all, we also have a democratically elected congress and president. Why bother with city government? Just call your congress member about the pothole, garbage pickup, or idea for a park improvement. And indeed you can. But my congress member represents about 700,000 people and avers to the local council member who represents 160,000 residents. He has close ties, that include budgetary control, with the local service providers - the pothole fillers, sanitation and parks departments. So for local service delivery issues it's better to go local. And in this instance, with .nyc, I think we have agreed to go down one more layer and engage the stakeholders in the process. And indeed, ICANN talks bottom-up and multistakeholder. Minimally, minimally, ICANN could send a notification to the local ALSs when a city registry agreement change
is proposed. And it would seem reasonable to provide the opportunity
for that ALS to respond, and for that response to be considered. One
might argue that it is the ALS's responsibility to keep an eye on ICANN's activities. And that's a good idea. And I support and look forward to the day when we're provided by ICANN with a budget to hire a staff member for that task. But for now it seems ICANN's generating a letter about proposed changes to the registry agreement is the simpler way to go.
* "There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely."
As I recall the situation, the city created the advisory board under
duress - there was a challenge to their .nyc application from Connecting.nyc Inc. After the .NYC Community Advisory Board's creation the city retained tight control over its operation. It appointed members, scheduled the meetings, and set the agenda. I informed media-types about the meetings, but they were excluded by the representatives of the mayor. Additionally, even city officials were excluded. Council member Gale Brewer's representative, whom I invited, was told to leave the room when he showed up. And as I mentioned previously, when they abolished it on December 31, 2014 they wiped out any sign of its existence from its website. But you're right, those chains probably could have been broken short of self-immolation. I just never figured out how. Where are we now? While we've taken a hit with the abolition of the .NYC Community Advisory Board, I'm still trying to get a governance process started
where IIUs can meaningfully participate in a governance process. My latest thought is to get ICANN, via the ALSs, on board and advocating for a multistakeholder governance process, one that includes IIUs. Any thoughts on how to achieve this are most welcomed.
Best,
Tom Lowenhaupt
On 5/12/2016 1:19 AM, Joly MacFie wrote:
On Thu, May 12, 2016 at 12:09 AM, Thomas Lowenhaupt <toml@communisphere.com> wrote:
The point I'm trying to make is: If we've all accepted the multistakeholder model, how is it that the local ALSes and individual Internet users (residents and organizations as well) are left out of the decision making process?
Tom
But are we? ALS's and individuals can join RALOs, who inturn can influence the ALAC, who advise the ICANN board.
Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least
in
theory.
There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.
j
-- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online athttp://www.naralo.org ------
Hi Tom and Alan, I read the Registry agreement - Paris and didn't find real relevant info: «7.8 No Third-Party Beneficiaries. This Agreement will not be construed to create any obligation by either ICANN or Registry Operator to any non-party to this Agreement, including any registrar or registered name holder. Community Registration Policies Registry Operator shall implement and comply with all community registration policies described below and/or attached to this Specification 12. In the event Specification 12 conflicts with the requirements of any other provision of the Registry Agreement, such other provision shall govern. Two types of conditions must be fulfilled for the right to register a TLD name. These are: (A) community membership (bona fide presence in the Paris area) and (B) the additional requirements that: The presence in Paris area and use of domain are generally accepted as legitimate. The presence in Paris area and use of domain are conducive to welfare of the Paris area.» Goog evening Louis Houle President ISOC Quebec Louis.Houle@isoc.quebec Le 2016-05-13 à 16:40, Alan Greenberg a écrit :
As a first step, perhaps you should look at all of the application forms and registry agreements, particularly for those that are Community TLDs, and see what they committed to. -- Sent from my mobile. Please excuse brevity and typos.
On May 13, 2016 4:16:47 PM EDT, Thomas Lowenhaupt <toml@communisphere.com> wrote:
Louis,
It certainly would be good to know the level of engagement for IIUs in Paris and the other newly TLD'd cities. Perhaps the At-Large could craft a questionnaire to gather the state of affairs, to be distributed as widely as practicable. Certainly one might imagine excellent penetration in those cities with ALSes. From there we might develop a report of use to many.
What's the best tool for creating a questionnaire these days? Surveymonkey <https://www.surveymonkey.com/> seems to be priced right? Anyone with experience in this area? Is there a better alternative? Are there others in the ICANN community that might be interested in a project of this sort?
Best,
Tom Lowenhaupt
On 5/13/2016 2:51 PM, Louis Houle wrote:
Hi Tom,
Why is the situation rather opaque in .NYC. Because inclusiveness is not promoted ? Because transparency is not an integrated process in the pratices of the management team (the meetings are held behind closed doors? )
Governments obey to a set of rules and processes that they control. This includes the input or contribution from third parties regarding the direction to follow the management approach, etc. I understand that this the situation that you're cought with.
Your suggestion to get ICANN on board is certainly appropriate. Is it the only approach for you to advocate for a governance process for NYC? I don't know if other city TLD are facing a similar situation as the one you described. For instance, Dot-Paris is managed by the city under the authority of the mayer. Would it be useful to document how they address governance issues including the multistakeholder model ? Would it be useful to get the GeoTLD Interest Group on board also?
At Dot-Quebec, the Board adopted a very openned governance approach. Anybody who can contribute is welcome, but it's a not-for-profit organisation. It's not lead by the government even though we received a financial and political support for the project. We support the multistakeholder model but for the new members of the Board, it needs to be explained. We have people with various and strong CV, but mostly no ICANN experience for some of them. Knowledge sharing is useful then, but it is still necessary to have a partner who is willing to listen.
Regards
Louis Houle President ISOC Quebec Louis.Houle@isoc.quebec
Le 2016-05-12 12:49, Thomas Lowenhaupt a écrit :
Joly,
In response to my post contending that the multistakeholder model was not effectively meeting the needs of individual Internet users (IIUs) in New York City you said:
* "But are we? ALS's and individuals can join RALOs, who in turn can influence the ALAC, who advise the ICANN board."
That's correct. And that's what I'm doing right now.
* "Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory."
Following that line of thought we really don't need a city council or mayor at all. After all, we also have a democratically elected congress and president. Why bother with city government? Just call your congress member about the pothole, garbage pickup, or idea for a park improvement. And indeed you can. But my congress member represents about 700,000 people and avers to the local council member who represents 160,000 residents. He has close ties, that include budgetary control, with the local service providers - the pothole fillers, sanitation and parks departments. So for local service delivery issues it's better to go local. And in this instance, with .nyc, I think we have agreed to go down one more layer and engage the stakeholders in the process. And indeed, ICANN talks bottom-up and multistakeholder. Minimally, minimally, ICANN could send a notification to the local ALSs when a city registry agreement change is proposed. And it would seem reasonable to provide the opportunity for that ALS to respond, and for that response to be considered. One might argue that it is the ALS's responsibility to keep an eye on ICANN's activities. And that's a good idea. And I support and look forward to the day when we're provided by ICANN with a budget to hire a staff member for that task. But for now it seems ICANN's generating a letter about proposed changes to the registry agreement is the simpler way to go.
* "There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely."
As I recall the situation, the city created the advisory board under duress - there was a challenge to their .nyc application from Connecting.nyc Inc. After the .NYC Community Advisory Board's creation the city retained tight control over its operation. It appointed members, scheduled the meetings, and set the agenda. I informed media-types about the meetings, but they were excluded by the representatives of the mayor. Additionally, even city officials were excluded. Council member Gale Brewer's representative, whom I invited, was told to leave the room when he showed up. And as I mentioned previously, when they abolished it on December 31, 2014 they wiped out any sign of its existence from its website. But you're right, those chains probably could have been broken short of self-immolation. I just never figured out how. Where are we now? While we've taken a hit with the abolition of the .NYC Community Advisory Board, I'm still trying to get a governance process started where IIUs can meaningfully participate in a governance process. My latest thought is to get ICANN, via the ALSs, on board and advocating for a multistakeholder governance process, one that includes IIUs. Any thoughts on how to achieve this are most welcomed.
Best,
Tom Lowenhaupt
On 5/12/2016 1:19 AM, Joly MacFie wrote:
On Thu, May 12, 2016 at 12:09 AM, Thomas Lowenhaupt <toml@communisphere.com> wrote:
The point I'm trying to make is: If we've all accepted the multistakeholder model, how is it that the local ALSes and individual Internet users (residents and organizations as well) are left out of the decision making process?
Tom
But are we? ALS's and individuals can join RALOs, who inturn can influence the ALAC, who advise the ICANN board.
Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory.
There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.
j
-- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online athttp://www.naralo.org ------
.paris is a community TLD, and thus subject to the control of the designated community. However, according to the TLD application, the "City of Paris" is deemed to be the representative of that community. So it is completely internal to the City of Paris how it implements any control or other input from Paris residents and businesses. This, for all practical purposes, puts it in the same status as .nyc (which did not apply as a "Community" TLD. Any rules it puts in place, or does not put in place, which gives some level of control or review to NYC residents or businesses is solely up to the city administration. Alan At 12/06/2016 06:07 PM, Louis Houle wrote:
Hi Tom and Alan,
I read the Registry agreement - Paris and didn't find real relevant info:
«7.8 No Third-Party Beneficiaries. This Agreement will not be construed to create any obligation by either ICANN or Registry Operator to any non-party to this Agreement, including any registrar or registered name holder.
Community Registration Policies
Registry Operator shall implement and comply with all community registration policies described below and/or attached to this Specification 12. In the event Specification 12 conflicts with the requirements of any other provision of the Registry Agreement, such other provision shall govern. Two types of conditions must be fulfilled for the right to register a TLD name. These are: (A) community membership (bona fide presence in the Paris area) and (B) the additional requirements that: The presence in Paris area and use of domain are generally accepted as legitimate. The presence in Paris area and use of domain are conducive to welfare of the Paris area.»
Goog evening
Louis Houle President ISOC Quebec <mailto:Louis.Houle@isoc.quebec>Louis.Houle@isoc.quebec
Le 2016-05-13 à 16:40, Alan Greenberg a écrit :
As a first step, perhaps you should look at all of the application forms and registry agreements, particularly for those that are Community TLDs, and see what they committed to. -- Sent from my mobile. Please excuse brevity and typos.
On May 13, 2016 4:16:47 PM EDT, Thomas Lowenhaupt <mailto:toml@communisphere.com><toml@communisphere.com> wrote:
Louis,
It certainly would be good to know the level of engagement for IIUs in Paris and the other newly TLD'd cities. Perhaps the At-Large could craft a questionnaire to gather the state of affairs, to be distributed as widely as practicable. Certainly one might imagine excellent penetration in those cities with ALSes. From there we might develop a report of use to many.
What's the best tool for creating a questionnaire these days? <https://www.surveymonkey.com/>Surveymonkey seems to be priced right? Anyone with experience in this area? Is there a better alternative? Are there others in the ICANN community that might be interested in a project of this sort?
Best,
Tom Lowenhaupt
On 5/13/2016 2:51 PM, Louis Houle wrote:
Hi Tom,
Why is the situation rather opaque in .NYC. Because inclusiveness is not promoted ? Because transparency is not an integrated process in the pratices of the management team (the meetings are held behind closed doors? )
Governments obey to a set of rules and processes that they control. This includes the input or contribution from third parties regarding the direction to follow the management approach, etc. I understand that this the situation that you're cought with.
Your suggestion to get ICANN on board is certainly appropriate. Is it the only approach for you to advocate for a governance process for NYC? I don't know if other city TLD are facing a similar situation as the one you described. For instance, Dot-Paris is managed by the city under the authority of the mayer. Would it be useful to document how they address governance issues including the multistakeholder model ? Would it be useful to get the GeoTLD Interest Group on board also?
At Dot-Quebec, the Board adopted a very openned governance approach. Anybody who can contribute is welcome, but it's a not-for-profit organisation. It's not lead by the government even though we received a financial and political support for the project. We support the multistakeholder model but for the new members of the Board, it needs to be explained. We have people with various and strong CV, but mostly no ICANN experience for some of them. Knowledge sharing is useful then, but it is still necessary to have a partner who is willing to listen.
Regards
Louis Houle
President
ISOC Quebec
<mailto:Louis.Houle@isoc.quebec>Louis.Houle@isoc.quebec
Le 2016-05-12 12:49, Thomas Lowenhaupt a écrit :
Joly,
In response to my post contending that the multistakeholder model was not effectively meeting the needs of individual Internet users (IIUs) in New York City you said: * "âBut are we? ALS's and individuals can join RALOs, who in turn can influence the ALAC, who advise the ICANN board." That's correct. And that's what I'm doing right now. * "Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory." Following that line of thought we really don't need a city council or mayor at all. After all, we also have a democratically elected congress and president. Why bother with city government? Just call your congress member about the pothole, garbage pickup, or idea for a park improvement. And indeed you can. But my congress member represents about 700,000 people and avers to the local council member who represents 160,000 residents. He has close ties, that include budgetary control, with the local service providers - the pothole fillers, sanitation and parks departments. So for local service delivery issues it's better to go local. And in this instance, with .nyc, I think we have agreed to go down one more layer and engage the stakeholders in the process. And indeed, ICANN talks bottom-up and multistakeholder. Minimally, minimally, ICANN could send a notification to the local ALSs when a city registry agreement change is proposed. And it would seem reasonable to provide the opportunity for that ALS to respond, and for that response to be considered. One might argue that it is the ALS's responsibility to keep an eye on ICANN's activities. And that's a good idea. And I support and look forward to the day when we're provided by ICANN with a budget to hire a staff member for that task. But for now it seems ICANN's generating a letter about proposed changes to the registry agreement is the simpler way to go. * "There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.â" As I recall the situation, the city created the advisory board under duress - there was a challenge to their .nyc application from Connecting.nyc Inc. After the .NYC Community Advisory Board's creation the city retained tight control over its operation. It appointed members, scheduled the meetings, and set the agenda. I informed media-types about the meetings, but they were excluded by the representatives of the mayor. Additionally, even city officials were excluded. Council member Gale Brewer's representative, whom I invited, was told to leave the room when he showed up. And as I mentioned previously, when they abolished it on December 31, 2014 they wiped out any sign of its existence from its website. But you're right, those chains probably could have been broken short of self-immolation. I just never figured out how. Where are we now? While we've taken a hit with the abolition of the .NYC Community Advisory Board, I'm still trying to get a governance process started where IIUs can meaningfully participate in a governance process. My latest thought is to get ICANN, via the ALSs, on board and advocating for a multistakeholder governance process, one that includes IIUs. Any thoughts on how to achieve this are most welcomed.
Best,
Tom Lowenhaupt
On 5/12/2016 1:19 AM, Joly MacFie wrote:
On Thu, May 12, 2016 at 12:09 AM, Thomas Lowenhaupt <<mailto:toml@communisphere.com>toml@communisphere.com> wrote:
The point I'm trying to make is: If we've all accepted the multistakeholder model, how is it that the local ALSes and individual Internet users (residents and organizations as well) are left out of the decision making process?
Tom
âBut are we? ALS's and individuals can join RALOs, who inturn can influence the ALAC, who advise the ICANN board.
Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory.
There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.â
âjâ
-- --------------------------------------------------------------- Joly MacFie 218 565 9365 <Skype:punkcast>Skype:punkcast -------------------------------------------------------------- -
------
NA-Discuss mailing list
<mailto:NA-Discuss@atlarge-lists.icann.org>NA-Discuss@atlarge-lists.icann.org
https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online at <http://www.naralo.org>http://www.naralo.org
------
Alan, While I've not completed my research, your conclusion seems to conform to the city's belief here in New York - that it need not provide a process for participation by individual Internet users in shaping the use of the .nyc TLD. Assuming that's the case, that there's no clear responsibility on the part of ICANN or the registry, what responsibility does the At-Large have with regard to the needs of individual Internet users? To me, it would seem ALAC's role is to advise ICANN, politely, that it botched things with regard to city-TLDs, and to suggest a roadmap for reengaging individual Internet users with the governance process. Are you in agreement or have I missed something? Best, Tom Lowenhaupt On 6/13/2016 3:59 PM, Alan Greenberg wrote:
.paris is a community TLD, and thus subject to the control of the designated community. However, according to the TLD application, the "City of Paris" is deemed to be the representative of that community. So it is completely internal to the City of Paris how it implements any control or other input from Paris residents and businesses.
This, for all practical purposes, puts it in the same status as .nyc (which did not apply as a "Community" TLD. Any rules it puts in place, or does not put in place, which gives some level of control or review to NYC residents or businesses is solely up to the city administration.
Alan
At 12/06/2016 06:07 PM, Louis Houle wrote:
Hi Tom and Alan,
I read the Registry agreement - Paris and didn't find real relevant info:
«7.8 No Third-Party Beneficiaries. This Agreement will not be construed to create any obligation by either ICANN or Registry Operator to any non-party to this Agreement, including any registrar or registered name holder.
Community Registration Policies
Registry Operator shall implement and comply with all community registration policies described below and/or attached to this Specification 12. In the event Specification 12 conflicts with the requirements of any other provision of the Registry Agreement, such other provision shall govern. Two types of conditions must be fulfilled for the right to register a TLD name. These are: (A) community membership (bona fide presence in the Paris area) and (B) the additional requirements that: The presence in Paris area and use of domain are generally accepted as legitimate. The presence in Paris area and use of domain are conducive to welfare of the Paris area.»
Goog evening
Louis Houle President ISOC Quebec Louis.Houle@isoc.quebec <mailto:Louis.Houle@isoc.quebec>
Le 2016-05-13 à 16:40, Alan Greenberg a écrit :
As a first step, perhaps you should look at all of the application forms and registry agreements, particularly for those that are Community TLDs, and see what they committed to. -- Sent from my mobile. Please excuse brevity and typos.
On May 13, 2016 4:16:47 PM EDT, Thomas Lowenhaupt <toml@communisphere.com> <mailto:toml@communisphere.com> wrote:
Louis,
It certainly would be good to know the level of engagement for IIUs in Paris and the other newly TLD'd cities. Perhaps the At-Large could craft a questionnaire to gather the state of affairs, to be distributed as widely as practicable. Certainly one might imagine excellent penetration in those cities with ALSes. From there we might develop a report of use to many.
What's the best tool for creating a questionnaire these days? Surveymonkey <https://www.surveymonkey.com/> seems to be priced right? Anyone with experience in this area? Is there a better alternative? Are there others in the ICANN community that might be interested in a project of this sort?
Best,
Tom Lowenhaupt
On 5/13/2016 2:51 PM, Louis Houle wrote:
Hi Tom,
Why is the situation rather opaque in .NYC. Because inclusiveness is not promoted ? Because transparency is not an integrated process in the pratices of the management team (the meetings are held behind closed doors? )
Governments obey to a set of rules and processes that they control. This includes the input or contribution from third parties regarding the direction to follow the management approach, etc. I understand that this the situation that you're cought with.
Your suggestion to get ICANN on board is certainly appropriate. Is it the only approach for you to advocate for a governance process for NYC? I don't know if other city TLD are facing a similar situation as the one you described. For instance, Dot-Paris is managed by the city under the authority of the mayer. Would it be useful to document how they address governance issues including the multistakeholder model ? Would it be useful to get the GeoTLD Interest Group on board also?
At Dot-Quebec, the Board adopted a very openned governance approach. Anybody who can contribute is welcome, but it's a not-for-profit organisation. It's not lead by the government even though we received a financial and political support for the project. We support the multistakeholder model but for the new members of the Board, it needs to be explained. We have people with various and strong CV, but mostly no ICANN experience for some of them. Knowledge sharing is useful then, but it is still necessary to have a partner who is willing to listen.
Regards
Louis Houle
President ISOC Quebec Louis.Houle@isoc.quebec <mailto:Louis.Houle@isoc.quebec> Le 2016-05-12 12:49, Thomas Lowenhaupt a écrit :
Joly,
In response to my post contending that the multistakeholder model was not effectively meeting the needs of individual Internet users (IIUs) in New York City you said:
o "​But are we? ALS's and individuals can join RALOs, who in turn can influence the ALAC, who advise the ICANN board."
That's correct. And that's what I'm doing right now.
o "Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory." Following that line of thought we really don't need a city council or mayor at all. After all, we also have a democratically elected congress and president. Why bother with city government? Just call your congress member about the pothole, garbage pickup, or idea for a park improvement. And indeed you can. But my congress member represents about 700,000 people and avers to the local council member who represents 160,000 residents. He has close ties, that include budgetary control, with the local service providers - the pothole fillers, sanitation and parks departments. So for local service delivery issues it's better to go local. And in this instance, with .nyc, I think we have agreed to go down one more layer and engage the stakeholders in the process. And indeed, ICANN talks bottom-up and multistakeholder. Minimally, minimally, ICANN could send a notification to the local ALSs when a city registry agreement change is proposed. And it would seem reasonable to provide the opportunity for that ALS to respond, and for that response to be considered. One might argue that it is the ALS's responsibility to keep an eye on ICANN's activities. And that's a good idea. And I support and look forward to the day when we're provided by ICANN with a budget to hire a staff member for that task. But for now it seems ICANN's generating a letter about proposed changes to the registry agreement is the simpler way to go. # "There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.​" As I recall the situation, the city created the advisory board under duress - there was a challenge to their .nyc application from Connecting.nyc Inc. After the .NYC Community Advisory Board's creation the city retained tight control over its operation. It appointed members, scheduled the meetings, and set the agenda. I informed media-types about the meetings, but they were excluded by the representatives of the mayor. Additionally, even city officials were excluded. Council member Gale Brewer's representative, whom I invited, was told to leave the room when he showed up. And as I mentioned previously, when they abolished it on December 31, 2014 they wiped out any sign of its existence from its website. But you're right, those chains probably could have been broken short of self-immolation. I just never figured out how. Where are we now? While we've taken a hit with the abolition of the .NYC Community Advisory Board, I'm still trying to get a governance process started where IIUs can meaningfully participate in a governance process. My latest thought is to get ICANN, via the ALSs, on board and advocating for a multistakeholder governance process, one that includes IIUs. Any thoughts on how to achieve this are most welcomed.
Best,
Tom Lowenhaupt
On 5/12/2016 1:19 AM, Joly MacFie wrote:
On Thu, May 12, 2016 at 12:09 AM, Thomas Lowenhaupt <toml@communisphere.com <mailto:toml@communisphere.com> > wrote:
The point I'm trying to make is: If we've all accepted the multistakeholder model, how is it that the local ALSes and individual Internet users (residents and organizations as well) are left out of the decision making process?
Tom
​But are we? ALS's and individuals can join RALOs, who inturn can influence the ALAC, who advise the ICANN board.
Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory.
There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.​
​j​
-- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -
------
NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org <mailto:NA-Discuss@atlarge-lists.icann.org>
https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online at http://www.naralo.org ------
On 13 June 2016 at 23:44, Thomas Lowenhaupt <toml@communisphere.com> wrote:
While I've not completed my research, your conclusion seems to conform to the city's belief here in New York - that it need not provide a process for participation by individual Internet users in shaping the use of the .nyc TLD.
That is absolutely untrue, unless New York and Paris are governed by self-appointing dictatorships. If they are like most cities, over and above the regular high-level governance votes, there are certain levels of community participation in garbage collection, green spaces, parking regulations, urban planning, etc. If such processes exist they offer the (at least indirect) way to influence the cities' policies regarding their TLDs (though I would suggest that the other issues I mentioned are higher up the priority list of most citizens). The case has yet to be made that pubic input into how cities run their TLDs is more pressing and important than, say policing.
Assuming that's the case, that there's no clear responsibility on the part of ICANN or the registry, what responsibility does the At-Large have with regard to the needs of individual Internet users?
In these cases, ALAC has zero input post-delegation unless the registry can be found in breach of its agreement with ICANN. To me, it would seem ALAC's role is to advise ICANN, politely, that it
botched things with regard to city-TLDs, and to suggest a roadmap for reengaging individual Internet users with the governance process.
This grievance claims to speak for issues related to all city gTLDs, yet after years and years and years at this tired complaint we have yet to hear from a single other city community that shares this issue. There is no other conclusion except that this clearly is not a globally applicable problem; ALAC should not get involved, instead leaving the discussion to the appropriate RALO for local handling if any. Are you in agreement or have I missed something?
A great much has been missed. But after so many failed attempts at re-raising the issue and refusal to address even basic answers and challenges, there is little conclusion but that the "missing something" is not only real but deliberate, And, once again, no there is no agreement. Not to this. - Evan
Tom, If there were a ground swell of support for the concept that a geographic TLD must consult (or listen to) citizens on its geographic region, then the ALAC could certainly advise that this would be included if and when there are any new geographic TLDs are allocated. I have little confidence that this is something that would be accepted by ICANN, as it only allocates the TLD and according to its mission has little to do with how it is run. One exception is that if a commitment to do something (or not do something) is in the TLD contract, then ICANN may be in a position to ensure that the contract is honoured. Even if ICANN would accept such a requirement to specify how geographic TLDs are managed, it would not change .nyc as the contracts are already signed and the only changes in this area that could alter the contract would be those voluntarily added by the City of New York. If you want to accomplish that, it is in New York that you need to be convincing people that there is a problem that you can help fix. Alan At 13/06/2016 05:44 PM, Thomas Lowenhaupt wrote: >Alan, > >While I've not completed my research, your >conclusion seems to conform to the city's belief >here in New York - that it need not provide a >process for participation by individual Internet >users in shaping the use of the .nyc TLD. >Assuming that's the case, that there's no clear >responsibility on the part of ICANN or the >registry, what responsibility does the At-Large >have with regard to the needs of individual Internet users? > >To me, it would seem ALAC's role is to advise >ICANN, politely, that it botched things with >regard to city-TLDs, and to suggest a roadmap >for reengaging individual Internet users with the governance process. > >Are you in agreement or have I missed something? > >Best, > >Tom Lowenhaupt > >On 6/13/2016 3:59 PM, Alan Greenberg wrote: >>.paris is a community TLD, and thus subject to >>the control of the designated community. >>However, according to the TLD application, the >>"City of Paris" is deemed to be the >>representative of that community. So it is >>completely internal to the City of Paris how it >>implements any control or other input from Paris residents and businesses. >> >>This, for all practical purposes, puts it in >>the same status as .nyc (which did not apply as >>a "Community" TLD. Any rules it puts in place, >>or does not put in place, which gives some >>level of control or review to NYC residents or >>businesses is solely up to the city administration. >> >>Alan >> >>At 12/06/2016 06:07 PM, Louis Houle wrote: >> >>>Hi Tom and Alan, >>> >>>I read the Registry agreement - Paris and didn't find real relevant info: >>> >>>«7.8 No Third-Party Beneficiaries. This >>>Agreement will not be construed to create any >>>obligation by either ICANN or Registry >>>Operator to any non-party to this Agreement, >>>including any registrar or registered name holder. >>> >>>Community Registration Policies >>> >>>Registry Operator shall implement and comply >>>with all community registration policies >>>described below and/or attached to this >>>Specification 12. In the event Specification >>>12 conflicts with the requirements of any >>>other provision of the Registry Agreement, such other provision shall govern. >>>Two types of conditions must be fulfilled for >>>the right to register a TLD name. These >>>are: (A) community membership (bona fide >>>presence in the Paris area) and (B) the additional requirements that: >>>The presence in Paris area and use of domain >>>are generally accepted as legitimate. >>>The presence in Paris area and use of domain >>>are conducive to welfare of the Paris area.» >>> >>>Goog evening >>> >>> >>> >>>Louis Houle >>>President >>>ISOC Quebec >>><mailto:Louis.Houle@isoc.quebec>Louis.Houle@isoc.quebec >>> >>>Le 2016-05-13 à 16:40, Alan Greenberg a écrit : >>>>As a first step, perhaps you should look at >>>>all of the application forms and registry >>>>agreements, particularly for those that are >>>>Community TLDs, and see what they committed to. >>>>-- >>>>Sent from my mobile. Please excuse brevity and typos. >>>> >>>>On May 13, 2016 4:16:47 PM EDT, Thomas >>>>Lowenhaupt <mailto:toml@communisphere.com><toml@communisphere.com> wrote: >>>>Louis, >>>>It certainly would be good to know the level >>>>of engagement for IIUs in Paris and the other >>>>newly TLD'd cities. Perhaps the At-Large >>>>could craft a questionnaire to gather the >>>>state of affairs, to be distributed as widely >>>>as practicable. Certainly one might imagine >>>>excellent penetration in those cities with >>>>ALSes. From there we might develop a report of use to many. >>>> >>>>What's the best tool for creating a >>>>questionnaire these days? >>>><https://www.surveymonkey.com/>Surveymonkey >>>>seems to be priced right? Anyone with >>>>experience in this area? Is there a better >>>>alternative? Are there others in the ICANN >>>>community that might be interested in a project of this sort? >>>>Best, >>>>Tom Lowenhaupt >>>>On 5/13/2016 2:51 PM, Louis Houle wrote: >>>>>Hi Tom, >>>>>Why is the situation rather opaque in .NYC. >>>>>Because inclusiveness is not promoted ? >>>>>Because transparency is not an integrated >>>>>process in the pratices of the management >>>>>team (the meetings are held behind closed doors? ) >>>>>Governments obey to a set of rules and >>>>>processes that they control. This includes >>>>>the input or contribution from third parties >>>>>regarding the direction to follow the >>>>>management approach, etc. I understand that >>>>>this the situation that you're cought with. >>>>>Your suggestion to get ICANN on board is >>>>>certainly appropriate. Is it the only >>>>>approach for you to advocate for a >>>>>governance process for NYC? I don't know if >>>>>other city TLD are facing a similar >>>>>situation as the one you described. For >>>>>instance, Dot-Paris is managed by the city >>>>>under the authority of the mayer. Would it >>>>>be useful to document how they address >>>>>governance issues including the >>>>>multistakeholder model ? Would it be useful >>>>>to get the GeoTLD Interest Group on board also? >>>>>At Dot-Quebec, the Board adopted a very >>>>>openned governance approach. Anybody who can >>>>>contribute is welcome, but it's a >>>>>not-for-profit organisation. It's not lead >>>>>by the government even though we received a >>>>>financial and political support for the >>>>>project. We support the multistakeholder >>>>>model but for the new members of the Board, >>>>>it needs to be explained. We have people >>>>>with various and strong CV, but mostly no >>>>>ICANN experience for some of them. Knowledge >>>>>sharing is useful then, but it is still >>>>>necessary to have a partner who is willing to listen. >>>>>Regards >>>>> >>>>> >>>>> >>>>>Louis Houle >>>>> >>>>> >>>>>President >>>>> >>>>> >>>>>ISOC Quebec >>>>> >>>>> >>>>><mailto:Louis.Houle@isoc.quebec>Louis.Houle@isoc.quebec >>>>> >>>>>Le 2016-05-12 12:49, Thomas Lowenhaupt a écrit : >>>>>>Joly, >>>>>>In response to my post contending that the >>>>>>multistakeholder model was not effectively >>>>>>meeting the needs of individual Internet >>>>>>users (IIUs) in New York City you said: >>>>>> * "âBut are we? ALS's and individuals >>>>>> can join RALOs, who in turn can influence >>>>>> the ALAC, who advise the ICANN board." >>>>That's correct. And that's what I'm doing right now. >>>> * "Or do you mean locally? Well, we elect >>>> our representatives on the NYC City Council, >>>> who are subject to their constituents, at >>>> least in theory." Following that line of >>>> thought we really don't need a city council >>>> or mayor at all. After all, we also have a >>>> democratically elected congress and >>>> president. Why bother with city government? >>>> Just call your congress member about the >>>> pothole, garbage pickup, or idea for a park >>>> improvement. And indeed you can. But my >>>> congress member represents about 700,000 >>>> people and avers to the local council member >>>> who represents 160,000 residents. He has >>>> close ties, that include budgetary >>>> control, with the local service providers - >>>> the pothole fillers, sanitation and parks >>>> departments. So for local service delivery >>>> issues it's better to go local. And in this >>>> instance, with .nyc, I think we have agreed >>>> to go down one more layer and engage the >>>> stakeholders in the process. And indeed, >>>> ICANN talks bottom-up and multistakeholder. >>>> Minimally, minimally, ICANN could send a >>>> notification to the local ALSs when a city >>>> registry agreement change is proposed. And >>>> it would seem reasonable to provide the >>>> opportunity for that ALS to respond, and for >>>> that response to be considered. One might >>>> argue that it is the ALS's responsibility to >>>> keep an eye on ICANN's activities. And >>>> that's a good idea. And I support and look >>>> forward to the day when we're provided by >>>> ICANN with a budget to hire a staff member >>>> for that task. But for now it seems ICANN's >>>> generating a letter about proposed changes >>>> to the registry agreement is the simpler way to go. >>>> * "There was an advisory board for >>>> .nyc. It hardly met, and the meetings it had >>>> were closed. You were on it. It could've >>>> done something to break its chains if the >>>> will was there, surely.â" As I recall the >>>> situation, the city created the advisory >>>> board under duress - there was a challenge >>>> to their .nyc application from >>>> Connecting.nyc Inc. After the .NYC Community >>>> Advisory Board's creation the city retained >>>> tight control over its operation. It >>>> appointed members, scheduled the meetings, >>>> and set the agenda. I informed media-types >>>> about the meetings, but they were excluded >>>> by the representatives of the mayor. >>>> Additionally, even city officials were >>>> excluded. Council member Gale Brewer's >>>> representative, whom I invited, was told to >>>> leave the room when he showed up. And as I >>>> mentioned previously, when they abolished it >>>> on December 31, 2014 they wiped out any sign >>>> of its existence from its website. But >>>> you're right, those chains probably could >>>> have been broken short of self-immolation. I >>>> just never figured out how. Where are we >>>> now? While we've taken a hit with the >>>> abolition of the .NYC Community Advisory >>>> Board, I'm still trying to get a governance >>>> process started where IIUs can meaningfully >>>> participate in a governance process. My >>>> latest thought is to get ICANN, via the >>>> ALSs, on board and advocating for a >>>> multistakeholder governance process, one >>>> that includes IIUs. Any thoughts on how to achieve this are most welcomed. >>>> Best, >>>> Tom Lowenhaupt >>>> On 5/12/2016 1:19 AM, Joly MacFie wrote: >>>>> On Thu, May 12, 2016 at 12:09 AM, >>>>> Thomas Lowenhaupt >>>>> <<mailto:toml@communisphere.com>toml@communisphere.com > wrote: >>>>> The point I'm trying to make is: If >>>>> we've all accepted the multistakeholder >>>>> model, how is it that the local ALSes and >>>>> individual Internet users (residents and >>>>> organizations as well) are left out of the decision making process? >>>>> Tom >>>>> >>>>> âBut are we? ALS's and individuals >>>>> can join RALOs, who inturn can influence the ALAC, who advise the ICANN board. >>>>> >>>>> Or do you mean locally? Well, we >>>>> elect our representatives on the NYC City >>>>> Council, who are subject to their constituents, at least in theory. >>>>> >>>>> There was an advisory board for >>>>> .nyc. It hardly met, and the meetings it >>>>> had were closed. You were on it. It >>>>> could've done something to break its chains if the will was there, surely.â >>>>> >>>>> âjâ >>>>> >>>>> >>>>> -- >>>>> --------------------------------------------------------------- >>>>> Joly MacFie 218 565 9365 <Skype:punkcast>Skype:punkcast >>>>> -------------------------------------------------------------- >>>>> - >>>> >>>> >>>> >>>> >>>> >>>> ------ >>>> >>>> >>>> NA-Discuss mailing list >>>> >>>> <mailto:NA-Discuss@atlarge-lists.icann.org> >>>> >>>> NA-Discuss@atlarge-lists.icann.org >>>> >>>> >>>> >>>> >>>> https://atlarge-lists.icann.org/mailman/listinfo/na-discuss >>>> >>>> >>>> >>>> Visit the NARALO online at >>>> >>>> <http://www.naralo.org>http://www.naralo.org >>>> >>>> >>>> ------
Alan, There are two issues that are getting merged and perhaps confused here: ICANN's role in issuing TLDs to cities and the ALAC's role. I'm talking about the latter. Let me explain. With ICANN: It seems reasonable that when issuing additional TLDs ICANN should approve their allocation after receiving some form of "Informed Consent" from the city identified by the TLD sought. The intention of this consent would be to assure, as much as practicable, that the governance structure of the city for which the TLD is sought is aware of the potential and uses of a city-TLD. If the mayor and council of Las Vegas agree to use the .vegas TLD to promote gambling and to hell with the public interest, that's up to them and the voters. In the instance of .nyc, the city has signed a contract with ICANN to operate the .nyc TLD for 10 years without what I consider to be informed consent. And the people of New York will deal with that. Hopefully we'll convince the city to set up an advisory board for .nyc similar to the dozens they have for police, sanitation, schools, transport, air quality... With ALAC: Today the individual Internet users in New York City have no official entity through which they can effectively and efficiently voice their concerns about the operation of the .nyc TLD. Perhaps one day they will. In the interim, ICANN is agreeing to changes to the registry agreement without consulting the city's individual Internet users. ICANN's by laws (Article XI, Section 2, 4, j, 10) detail the ALAC's responsibility to include: "Establishing mechanisms and processes that enable two-way communication between members of At-Large Structures and those involved in ICANN decision-making, so interested individuals can share their views on pending ICANN issues." What I'm asking is that the ALAC work to assure that we, as an At Large Structure, are informed when changes to the registry agreement are proposed. I'm asking that ALAC start a formal process to establish a mechanism and process that enables two-way communication between members of our At-Large Structure and those involved in ICANN decision-making, so interested individuals can share their views on pending ICANN issues. We'll deal with the informed consent issue at another time. Best, Tom Lowenhaupt On 6/13/2016 10:55 PM, Alan Greenberg wrote:
Tom,
If there were a ground swell of support for the concept that a geographic TLD must consult (or listen to) citizens on its geographic region, then the ALAC could certainly advise that this would be included if and when there are any new geographic TLDs are allocated. I have little confidence that this is something that would be accepted by ICANN, as it only allocates the TLD and according to its mission has little to do with how it is run. One exception is that if a commitment to do something (or not do something) is in the TLD contract, then ICANN may be in a position to ensure that the contract is honoured.
Even if ICANN would accept such a requirement to specify how geographic TLDs are managed, it would not change .nyc as the contracts are already signed and the only changes in this area that could alter the contract would be those voluntarily added by the City of New York.
If you want to accomplish that, it is in New York that you need to be convincing people that there is a problem that you can help fix.
Alan
At 13/06/2016 05:44 PM, Thomas Lowenhaupt wrote:
Alan,
While I've not completed my research, your conclusion seems to conform to the city's belief here in New York - that it need not provide a process for participation by individual Internet users in shaping the use of the .nyc TLD. Assuming that's the case, that there's no clear responsibility on the part of ICANN or the registry, what responsibility does the At-Large have with regard to the needs of individual Internet users?
To me, it would seem ALAC's role is to advise ICANN, politely, that it botched things with regard to city-TLDs, and to suggest a roadmap for reengaging individual Internet users with the governance process.
Are you in agreement or have I missed something?
Best,
Tom Lowenhaupt
On 6/13/2016 3:59 PM, Alan Greenberg wrote:
.paris is a community TLD, and thus subject to the control of the designated community. However, according to the TLD application, the "City of Paris" is deemed to be the representative of that community. So it is completely internal to the City of Paris how it implements any control or other input from Paris residents and businesses.
This, for all practical purposes, puts it in the same status as .nyc (which did not apply as a "Community" TLD. Any rules it puts in place, or does not put in place, which gives some level of control or review to NYC residents or businesses is solely up to the city administration.
Alan
At 12/06/2016 06:07 PM, Louis Houle wrote:
Hi Tom and Alan,
I read the Registry agreement - Paris and didn't find real relevant info:
«7.8 No Third-Party Beneficiaries. This Agreement will not be construed to create any obligation by either ICANN or Registry Operator to any non-party to this Agreement, including any registrar or registered name holder.
Community Registration Policies
Registry Operator shall implement and comply with all community registration policies described below and/or attached to this Specification 12. In the event Specification 12 conflicts with the requirements of any other provision of the Registry Agreement, such other provision shall govern. Two types of conditions must be fulfilled for the right to register a TLD name. These are: (A) community membership (bona fide presence in the Paris area) and (B) the additional requirements that: The presence in Paris area and use of domain are generally accepted as legitimate. The presence in Paris area and use of domain are conducive to welfare of the Paris area.»
Goog evening
Louis Houle President ISOC Quebec Louis.Houle@isoc.quebec <mailto:Louis.Houle@isoc.quebec>
Le 2016-05-13 à 16:40, Alan Greenberg a écrit :
As a first step, perhaps you should look at all of the application forms and registry agreements, particularly for those that are Community TLDs, and see what they committed to. -- Sent from my mobile. Please excuse brevity and typos.
On May 13, 2016 4:16:47 PM EDT, Thomas Lowenhaupt <toml@communisphere.com> <mailto:toml@communisphere.com> wrote:
Louis, It certainly would be good to know the level of engagement for IIUs in Paris and the other newly TLD'd cities. Perhaps the At-Large could craft a questionnaire to gather the state of affairs, to be distributed as widely as practicable. Certainly one might imagine excellent penetration in those cities with ALSes. From there we might develop a report of use to many.
What's the best tool for creating a questionnaire these days? Surveymonkey <https://www.surveymonkey.com/> seems to be priced right? Anyone with experience in this area? Is there a better alternative? Are there others in the ICANN community that might be interested in a project of this sort? Best, Tom Lowenhaupt On 5/13/2016 2:51 PM, Louis Houle wrote:
Hi Tom, Why is the situation rather opaque in .NYC. Because inclusiveness is not promoted ? Because transparency is not an integrated process in the pratices of the management team (the meetings are held behind closed doors? ) Governments obey to a set of rules and processes that they control. This includes the input or contribution from third parties regarding the direction to follow the management approach, etc. I understand that this the situation that you're cought with. Your suggestion to get ICANN on board is certainly appropriate. Is it the only approach for you to advocate for a governance process for NYC? I don't know if other city TLD are facing a similar situation as the one you described. For instance, Dot-Paris is managed by the city under the authority of the mayer. Would it be useful to document how they address governance issues including the multistakeholder model ? Would it be useful to get the GeoTLD Interest Group on board also? At Dot-Quebec, the Board adopted a very openned governance approach. Anybody who can contribute is welcome, but it's a not-for-profit organisation. It's not lead by the government even though we received a financial and political support for the project. We support the multistakeholder model but for the new members of the Board, it needs to be explained. We have people with various and strong CV, but mostly no ICANN experience for some of them. Knowledge sharing is useful then, but it is still necessary to have a partner who is willing to listen. Regards
Louis Houle
President ISOC Quebec Louis.Houle@isoc.quebec <mailto:Louis.Houle@isoc.quebec> Le 2016-05-12 12:49, Thomas Lowenhaupt a écrit : > Joly, > In response to my post contending that the > multistakeholder model was not effectively meeting > the needs of individual Internet users (IIUs) in New > York City you said: > > o "​But are we? ALS's and individuals can > join RALOs, who in turn can influence the > ALAC, who advise the ICANN board." >
That's correct. And that's what I'm doing right now.
o "Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory." Following that line of thought we really don't need a city council or mayor at all. After all, we also have a democratically elected congress and president. Why bother with city government? Just call your congress member about the pothole, garbage pickup, or idea for a park improvement. And indeed you can. But my congress member represents about 700,000 people and avers to the local council member who represents 160,000 residents. He has close ties, that include budgetary control, with the local service providers - the pothole fillers, sanitation and parks departments. So for local service delivery issues it's better to go local. And in this instance, with .nyc, I think we have agreed to go down one more layer and engage the stakeholders in the process. And indeed, ICANN talks bottom-up and multistakeholder. Minimally, minimally, ICANN could send a notification to the local ALSs when a city registry agreement change is proposed. And it would seem reasonable to provide the opportunity for that ALS to respond, and for that response to be considered. One might argue that it is the ALS's responsibility to keep an eye on ICANN's activities. And that's a good idea. And I support and look forward to the day when we're provided by ICANN with a budget to hire a staff member for that task. But for now it seems ICANN's generating a letter about proposed changes to the registry agreement is the simpler way to go. # "There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.​" As I recall the situation, the city created the advisory board under duress - there was a challenge to their .nyc application from Connecting.nyc Inc. After the .NYC Community Advisory Board's creation the city retained tight control over its operation. It appointed members, scheduled the meetings, and set the agenda. I informed media-types about the meetings, but they were excluded by the representatives of the mayor. Additionally, even city officials were excluded. Council member Gale Brewer's representative, whom I invited, was told to leave the room when he showed up. And as I mentioned previously, when they abolished it on December 31, 2014 they wiped out any sign of its existence from its website. But you're right, those chains probably could have been broken short of self-immolation. I just never figured out how. Where are we now? While we've taken a hit with the abolition of the .NYC Community Advisory Board, I'm still trying to get a governance process started where IIUs can meaningfully participate in a governance process. My latest thought is to get ICANN, via the ALSs, on board and advocating for a multistakeholder governance process, one that includes IIUs. Any thoughts on how to achieve this are most welcomed. Best, Tom Lowenhaupt On 5/12/2016 1:19 AM, Joly MacFie wrote:
On Thu, May 12, 2016 at 12:09 AM, Thomas Lowenhaupt <toml@communisphere.com <mailto:toml@communisphere.com> > wrote:
The point I'm trying to make is: If we've all accepted the multistakeholder model, how is it that the local ALSes and individual Internet users (residents and organizations as well) are left out of the decision making process? Tom
​But are we? ALS's and individuals can join RALOs, who inturn can influence the ALAC, who advise the ICANN board.
Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory.
There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.​
​j​
-- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -
------
NA-Discuss mailing list <mailto:NA-Discuss@atlarge-lists.icann.org> NA-Discuss@atlarge-lists.icann.org <mailto:NA-Discuss@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/na-discuss Visit the NARALO online at http://www.naralo.org ------
Right Alan. My purpose was to search any elements that would relate to the community. How they interact, if they have a proper policy or some guidelines in the agreement, knowing that the city is «sovereign» in its decision making. As I mentioned, I didn't find anything relevant in that sense regarding specific relations with an entity like Communisphere. When I contributed to the DotQuebec application, the multiple Guidebook versions were not so clear on how ICANN would define a community, a linguistic/cultural or a GeoTLD application and how it would impact the registry agreement. To some of us, it might seem obvious but what I understand Tom is probably searching for is a relationship to the community that is upstream, not merely a city/citizens administration. As you mentioned Louis Houle President ISOC Quebec Louis.Houle@isoc.quebec Le 2016-06-13 à 15:59, Alan Greenberg a écrit :
.paris is a community TLD, and thus subject to the control of the designated community. However, according to the TLD application, the "City of Paris" is deemed to be the representative of that community. So it is completely internal to the City of Paris how it implements any control or other input from Paris residents and businesses.
This, for all practical purposes, puts it in the same status as .nyc (which did not apply as a "Community" TLD. Any rules it puts in place, or does not put in place, which gives some level of control or review to NYC residents or businesses is solely up to the city administration.
Alan
At 12/06/2016 06:07 PM, Louis Houle wrote:
Hi Tom and Alan,
I read the Registry agreement - Paris and didn't find real relevant info:
«7.8 No Third-Party Beneficiaries. This Agreement will not be construed to create any obligation by either ICANN or Registry Operator to any non-party to this Agreement, including any registrar or registered name holder.
Community Registration Policies
Registry Operator shall implement and comply with all community registration policies described below and/or attached to this Specification 12. In the event Specification 12 conflicts with the requirements of any other provision of the Registry Agreement, such other provision shall govern. Two types of conditions must be fulfilled for the right to register a TLD name. These are: (A) community membership (bona fide presence in the Paris area) and (B) the additional requirements that: The presence in Paris area and use of domain are generally accepted as legitimate. The presence in Paris area and use of domain are conducive to welfare of the Paris area.»
Goog evening
Louis Houle President ISOC Quebec Louis.Houle@isoc.quebec <mailto:Louis.Houle@isoc.quebec>
Le 2016-05-13 à 16:40, Alan Greenberg a écrit :
As a first step, perhaps you should look at all of the application forms and registry agreements, particularly for those that are Community TLDs, and see what they committed to. -- Sent from my mobile. Please excuse brevity and typos.
On May 13, 2016 4:16:47 PM EDT, Thomas Lowenhaupt <toml@communisphere.com> <mailto:toml@communisphere.com> wrote:
Louis,
It certainly would be good to know the level of engagement for IIUs in Paris and the other newly TLD'd cities. Perhaps the At-Large could craft a questionnaire to gather the state of affairs, to be distributed as widely as practicable. Certainly one might imagine excellent penetration in those cities with ALSes. From there we might develop a report of use to many.
What's the best tool for creating a questionnaire these days? Surveymonkey <https://www.surveymonkey.com/> seems to be priced right? Anyone with experience in this area? Is there a better alternative? Are there others in the ICANN community that might be interested in a project of this sort?
Best,
Tom Lowenhaupt
On 5/13/2016 2:51 PM, Louis Houle wrote:
Hi Tom,
Why is the situation rather opaque in .NYC. Because inclusiveness is not promoted ? Because transparency is not an integrated process in the pratices of the management team (the meetings are held behind closed doors? )
Governments obey to a set of rules and processes that they control. This includes the input or contribution from third parties regarding the direction to follow the management approach, etc. I understand that this the situation that you're cought with.
Your suggestion to get ICANN on board is certainly appropriate. Is it the only approach for you to advocate for a governance process for NYC? I don't know if other city TLD are facing a similar situation as the one you described. For instance, Dot-Paris is managed by the city under the authority of the mayer. Would it be useful to document how they address governance issues including the multistakeholder model ? Would it be useful to get the GeoTLD Interest Group on board also?
At Dot-Quebec, the Board adopted a very openned governance approach. Anybody who can contribute is welcome, but it's a not-for-profit organisation. It's not lead by the government even though we received a financial and political support for the project. We support the multistakeholder model but for the new members of the Board, it needs to be explained. We have people with various and strong CV, but mostly no ICANN experience for some of them. Knowledge sharing is useful then, but it is still necessary to have a partner who is willing to listen.
Regards
Louis Houle
President ISOC Quebec Louis.Houle@isoc.quebec <mailto:Louis.Houle@isoc.quebec> Le 2016-05-12 12:49, Thomas Lowenhaupt a écrit :
Joly,
In response to my post contending that the multistakeholder model was not effectively meeting the needs of individual Internet users (IIUs) in New York City you said:
o "​But are we? ALS's and individuals can join RALOs, who in turn can influence the ALAC, who advise the ICANN board."
That's correct. And that's what I'm doing right now.
o "Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory." Following that line of thought we really don't need a city council or mayor at all. After all, we also have a democratically elected congress and president. Why bother with city government? Just call your congress member about the pothole, garbage pickup, or idea for a park improvement. And indeed you can. But my congress member represents about 700,000 people and avers to the local council member who represents 160,000 residents. He has close ties, that include budgetary control, with the local service providers - the pothole fillers, sanitation and parks departments. So for local service delivery issues it's better to go local. And in this instance, with .nyc, I think we have agreed to go down one more layer and engage the stakeholders in the process. And indeed, ICANN talks bottom-up and multistakeholder. Minimally, minimally, ICANN could send a notification to the local ALSs when a city registry agreement change is proposed. And it would seem reasonable to provide the opportunity for that ALS to respond, and for that response to be considered. One might argue that it is the ALS's responsibility to keep an eye on ICANN's activities. And that's a good idea. And I support and look forward to the day when we're provided by ICANN with a budget to hire a staff member for that task. But for now it seems ICANN's generating a letter about proposed changes to the registry agreement is the simpler way to go. # "There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.​" As I recall the situation, the city created the advisory board under duress - there was a challenge to their .nyc application from Connecting.nyc Inc. After the .NYC Community Advisory Board's creation the city retained tight control over its operation. It appointed members, scheduled the meetings, and set the agenda. I informed media-types about the meetings, but they were excluded by the representatives of the mayor. Additionally, even city officials were excluded. Council member Gale Brewer's representative, whom I invited, was told to leave the room when he showed up. And as I mentioned previously, when they abolished it on December 31, 2014 they wiped out any sign of its existence from its website. But you're right, those chains probably could have been broken short of self-immolation. I just never figured out how. Where are we now? While we've taken a hit with the abolition of the .NYC Community Advisory Board, I'm still trying to get a governance process started where IIUs can meaningfully participate in a governance process. My latest thought is to get ICANN, via the ALSs, on board and advocating for a multistakeholder governance process, one that includes IIUs. Any thoughts on how to achieve this are most welcomed.
Best,
Tom Lowenhaupt
On 5/12/2016 1:19 AM, Joly MacFie wrote:
On Thu, May 12, 2016 at 12:09 AM, Thomas Lowenhaupt <toml@communisphere.com <mailto:toml@communisphere.com> > wrote:
The point I'm trying to make is: If we've all accepted the multistakeholder model, how is it that the local ALSes and individual Internet users (residents and organizations as well) are left out of the decision making process?
Tom
​But are we? ALS's and individuals can join RALOs, who inturn can influence the ALAC, who advise the ICANN board.
Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory.
There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.​
​j​
-- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -
------
NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org <mailto:NA-Discuss@atlarge-lists.icann.org>
https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online at http://www.naralo.org ------
Sorry I was answering the phone and the email decided to reach you without my consent:-[ As you mentioned in a previous email, Alan, the Registry Agreement did not require public input. The relation with the community has to be built accordingly. But don't you feel that something is missing in that governance pattern? Louis Houle President ISOC Quebec Louis.Houle@isoc.quebec Le 2016-06-13 à 18:05, Louis Houle a écrit :
Right Alan.
My purpose was to search any elements that would relate to the community. How they interact, if they have a proper policy or some guidelines in the agreement, knowing that the city is «sovereign» in its decision making. As I mentioned, I didn't find anything relevant in that sense regarding specific relations with an entity like Communisphere.
When I contributed to the DotQuebec application, the multiple Guidebook versions were not so clear on how ICANN would define a community, a linguistic/cultural or a GeoTLD application and how it would impact the registry agreement. To some of us, it might seem obvious but what I understand Tom is probably searching for is a relationship to the community that is upstream, not merely a city/citizens administration.
As you mentioned
Louis Houle President ISOC Quebec Louis.Houle@isoc.quebec
Le 2016-06-13 à 15:59, Alan Greenberg a écrit :
.paris is a community TLD, and thus subject to the control of the designated community. However, according to the TLD application, the "City of Paris" is deemed to be the representative of that community. So it is completely internal to the City of Paris how it implements any control or other input from Paris residents and businesses.
This, for all practical purposes, puts it in the same status as .nyc (which did not apply as a "Community" TLD. Any rules it puts in place, or does not put in place, which gives some level of control or review to NYC residents or businesses is solely up to the city administration.
Alan
At 12/06/2016 06:07 PM, Louis Houle wrote:
Hi Tom and Alan,
I read the Registry agreement - Paris and didn't find real relevant info:
«7.8 No Third-Party Beneficiaries. This Agreement will not be construed to create any obligation by either ICANN or Registry Operator to any non-party to this Agreement, including any registrar or registered name holder.
Community Registration Policies
Registry Operator shall implement and comply with all community registration policies described below and/or attached to this Specification 12. In the event Specification 12 conflicts with the requirements of any other provision of the Registry Agreement, such other provision shall govern. Two types of conditions must be fulfilled for the right to register a TLD name. These are: (A) community membership (bona fide presence in the Paris area) and (B) the additional requirements that: The presence in Paris area and use of domain are generally accepted as legitimate. The presence in Paris area and use of domain are conducive to welfare of the Paris area.»
Goog evening
Louis Houle President ISOC Quebec Louis.Houle@isoc.quebec <mailto:Louis.Houle@isoc.quebec>
Le 2016-05-13 à 16:40, Alan Greenberg a écrit :
As a first step, perhaps you should look at all of the application forms and registry agreements, particularly for those that are Community TLDs, and see what they committed to. -- Sent from my mobile. Please excuse brevity and typos.
On May 13, 2016 4:16:47 PM EDT, Thomas Lowenhaupt <toml@communisphere.com> wrote:
Louis,
It certainly would be good to know the level of engagement for IIUs in Paris and the other newly TLD'd cities. Perhaps the At-Large could craft a questionnaire to gather the state of affairs, to be distributed as widely as practicable. Certainly one might imagine excellent penetration in those cities with ALSes. From there we might develop a report of use to many.
What's the best tool for creating a questionnaire these days? Surveymonkey <https://www.surveymonkey.com/> seems to be priced right? Anyone with experience in this area? Is there a better alternative? Are there others in the ICANN community that might be interested in a project of this sort?
Best,
Tom Lowenhaupt
On 5/13/2016 2:51 PM, Louis Houle wrote:
Hi Tom,
Why is the situation rather opaque in .NYC. Because inclusiveness is not promoted ? Because transparency is not an integrated process in the pratices of the management team (the meetings are held behind closed doors? )
Governments obey to a set of rules and processes that they control. This includes the input or contribution from third parties regarding the direction to follow the management approach, etc. I understand that this the situation that you're cought with.
Your suggestion to get ICANN on board is certainly appropriate. Is it the only approach for you to advocate for a governance process for NYC? I don't know if other city TLD are facing a similar situation as the one you described. For instance, Dot-Paris is managed by the city under the authority of the mayer. Would it be useful to document how they address governance issues including the multistakeholder model ? Would it be useful to get the GeoTLD Interest Group on board also?
At Dot-Quebec, the Board adopted a very openned governance approach. Anybody who can contribute is welcome, but it's a not-for-profit organisation. It's not lead by the government even though we received a financial and political support for the project. We support the multistakeholder model but for the new members of the Board, it needs to be explained. We have people with various and strong CV, but mostly no ICANN experience for some of them. Knowledge sharing is useful then, but it is still necessary to have a partner who is willing to listen.
Regards
Louis Houle
President ISOC Quebec Louis.Houle@isoc.quebec <mailto:Louis.Houle@isoc.quebec> Le 2016-05-12 12:49, Thomas Lowenhaupt a écrit :
Joly,
In response to my post contending that the multistakeholder model was not effectively meeting the needs of individual Internet users (IIUs) in New York City you said:
o "​But are we? ALS's and individuals can join RALOs, who in turn can influence the ALAC, who advise the ICANN board."
That's correct. And that's what I'm doing right now.
o "Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory." Following that line of thought we really don't need a city council or mayor at all. After all, we also have a democratically elected congress and president. Why bother with city government? Just call your congress member about the pothole, garbage pickup, or idea for a park improvement. And indeed you can. But my congress member represents about 700,000 people and avers to the local council member who represents 160,000 residents. He has close ties, that include budgetary control, with the local service providers - the pothole fillers, sanitation and parks departments. So for local service delivery issues it's better to go local. And in this instance, with .nyc, I think we have agreed to go down one more layer and engage the stakeholders in the process. And indeed, ICANN talks bottom-up and multistakeholder. Minimally, minimally, ICANN could send a notification to the local ALSs when a city registry agreement change is proposed. And it would seem reasonable to provide the opportunity for that ALS to respond, and for that response to be considered. One might argue that it is the ALS's responsibility to keep an eye on ICANN's activities. And that's a good idea. And I support and look forward to the day when we're provided by ICANN with a budget to hire a staff member for that task. But for now it seems ICANN's generating a letter about proposed changes to the registry agreement is the simpler way to go. # "There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.​" As I recall the situation, the city created the advisory board under duress - there was a challenge to their .nyc application from Connecting.nyc Inc. After the .NYC Community Advisory Board's creation the city retained tight control over its operation. It appointed members, scheduled the meetings, and set the agenda. I informed media-types about the meetings, but they were excluded by the representatives of the mayor. Additionally, even city officials were excluded. Council member Gale Brewer's representative, whom I invited, was told to leave the room when he showed up. And as I mentioned previously, when they abolished it on December 31, 2014 they wiped out any sign of its existence from its website. But you're right, those chains probably could have been broken short of self-immolation. I just never figured out how. Where are we now? While we've taken a hit with the abolition of the .NYC Community Advisory Board, I'm still trying to get a governance process started where IIUs can meaningfully participate in a governance process. My latest thought is to get ICANN, via the ALSs, on board and advocating for a multistakeholder governance process, one that includes IIUs. Any thoughts on how to achieve this are most welcomed.
Best,
Tom Lowenhaupt
On 5/12/2016 1:19 AM, Joly MacFie wrote:
On Thu, May 12, 2016 at 12:09 AM, Thomas Lowenhaupt <toml@communisphere.com > wrote:
The point I'm trying to make is: If we've all accepted the multistakeholder model, how is it that the local ALSes and individual Internet users (residents and organizations as well) are left out of the decision making process?
Tom
​But are we? ALS's and individuals can join RALOs, who inturn can influence the ALAC, who advise the ICANN board.
Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory.
There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.​
​j​
-- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -
------
NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org <mailto:NA-Discuss@atlarge-lists.icann.org>
https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online at http://www.naralo.org ------
You are asking the wrong person about things missing in governance patterns. I am regularly displeased with things done by my governments at all levels. I am occasionally pleasantly surprised that grass-roots efforts alter those decisions. In the current case, it is not in ICANN's remit to ensure good governance of a private or public enterprise with which it has a contract. Perhaps *IF* there is a general will, AND *IF* it is deemed within ICANN's mission, that might be altered in future TLD allocations (*IF* they were to occur). Those are several big IFs between here and there. Alan At 13/06/2016 06:23 PM, Louis Houle wrote: >Sorry I was answering the phone and the email >decided to reach you without my consent:-[ > >As you mentioned in a previous email, Alan, the >Registry Agreement did not require public input. >The relation with the community has to be built >accordingly. But don't you feel that something >is missing in that governance pattern? > > > >Louis Houle >President >ISOC Quebec ><mailto:Louis.Houle@isoc.quebec>Louis.Houle@isoc.quebec > >Le 2016-06-13 à 18:05, Louis Houle a écrit : >> >>Right Alan. >> >>My purpose was to search any elements that >>would relate to the community. How they >>interact, if they have a proper policy or some >>guidelines in the agreement, knowing that the >>city is «sovereign» in its decision making. As >>I mentioned, I didn't find anything relevant in >>that sense regarding specific relations with an entity like Communisphere. >> >>When I contributed to the DotQuebec >>application, the multiple Guidebook versions >>were not so clear on how ICANN would define a >>community, a linguistic/cultural or a GeoTLD >>application and how it would impact the >>registry agreement. To some of us, it might >>seem obvious but what I understand Tom is >>probably searching for is a relationship to the >>community that is upstream, not merely a city/citizens administration. >> >>As you mentioned >> >>Louis Houle >>President >>ISOC Quebec >><mailto:Louis.Houle@isoc.quebec>Louis.Houle@isoc.quebec >> >>Le 2016-06-13 à 15:59, Alan Greenberg a écrit : >>>.paris is a community TLD, and thus subject to >>>the control of the designated community. >>>However, according to the TLD application, the >>>"City of Paris" is deemed to be the >>>representative of that community. So it is >>>completely internal to the City of Paris how >>>it implements any control or other input from Paris residents and businesses. >>> >>>This, for all practical purposes, puts it in >>>the same status as .nyc (which did not apply >>>as a "Community" TLD. Any rules it puts in >>>place, or does not put in place, which gives >>>some level of control or review to NYC >>>residents or businesses is solely up to the city administration. >>> >>>Alan >>> >>>At 12/06/2016 06:07 PM, Louis Houle wrote: >>> >>>>Hi Tom and Alan, >>>> >>>>I read the Registry agreement - Paris and didn't find real relevant info: >>>> >>>>«7.8 No Third-Party Beneficiaries. This >>>>Agreement will not be construed to create any >>>>obligation by either ICANN or Registry >>>>Operator to any non-party to this Agreement, >>>>including any registrar or registered name holder. >>>> >>>>Community Registration Policies >>>> >>>>Registry Operator shall implement and comply >>>>with all community registration policies >>>>described below and/or attached to this >>>>Specification 12. In the event Specification >>>>12 conflicts with the requirements of any >>>>other provision of the Registry Agreement, such other provision shall govern. >>>>Two types of conditions must be fulfilled for >>>>the right to register a TLD name. These >>>>are: (A) community membership (bona fide >>>>presence in the Paris area) and (B) the additional requirements that: >>>>The presence in Paris area and use of domain >>>>are generally accepted as legitimate. >>>>The presence in Paris area and use of domain >>>>are conducive to welfare of the Paris area.» >>>> >>>>Goog evening >>>> >>>> >>>> >>>>Louis Houle >>>>President >>>>ISOC Quebec >>>><mailto:Louis.Houle@isoc.quebec>Louis.Houle@isoc.quebec >>>> >>>>Le 2016-05-13 à 16:40, Alan Greenberg a écrit : >>>>>As a first step, perhaps you should look at >>>>>all of the application forms and registry >>>>>agreements, particularly for those that are >>>>>Community TLDs, and see what they committed to. >>>>>-- >>>>>Sent from my mobile. Please excuse brevity and typos. >>>>> >>>>>On May 13, 2016 4:16:47 PM EDT, Thomas >>>>>Lowenhaupt <mailto:toml@communisphere.com><toml@communisphere.com> wrote: >>>>>Louis, >>>>>It certainly would be good to know the level >>>>>of engagement for IIUs in Paris and the >>>>>other newly TLD'd cities. Perhaps the >>>>>At-Large could craft a questionnaire to >>>>>gather the state of affairs, to be >>>>>distributed as widely as practicable. >>>>>Certainly one might imagine excellent >>>>>penetration in those cities with ALSes. From >>>>>there we might develop a report of use to many. >>>>>What's the best tool for creating a >>>>>questionnaire these days? >>>>><https://www.surveymonkey.com/>Surveymonkey >>>>>seems to be priced right? Anyone with >>>>>experience in this area? Is there a better >>>>>alternative? Are there others in the ICANN >>>>>community that might be interested in a project of this sort? >>>>>Best, >>>>>Tom Lowenhaupt >>>>>On 5/13/2016 2:51 PM, Louis Houle wrote: >>>>>>Hi Tom, >>>>>>Why is the situation rather opaque in .NYC. >>>>>>Because inclusiveness is not promoted ? >>>>>>Because transparency is not an integrated >>>>>>process in the pratices of the management >>>>>>team (the meetings are held behind closed doors? ) >>>>>>Governments obey to a set of rules and >>>>>>processes that they control. This includes >>>>>>the input or contribution from third >>>>>>parties regarding the direction to follow >>>>>>the management approach, etc. I understand >>>>>>that this the situation that you're cought with. >>>>>>Your suggestion to get ICANN on board is >>>>>>certainly appropriate. Is it the only >>>>>>approach for you to advocate for a >>>>>>governance process for NYC? I don't know if >>>>>>other city TLD are facing a similar >>>>>>situation as the one you described. For >>>>>>instance, Dot-Paris is managed by the city >>>>>>under the authority of the mayer. Would it >>>>>>be useful to document how they address >>>>>>governance issues including the >>>>>>multistakeholder model ? Would it be useful >>>>>>to get the GeoTLD Interest Group on board also? >>>>>>At Dot-Quebec, the Board adopted a very >>>>>>openned governance approach. Anybody who >>>>>>can contribute is welcome, but it's a >>>>>>not-for-profit organisation. It's not lead >>>>>>by the government even though we received a >>>>>>financial and political support for the >>>>>>project. We support the multistakeholder >>>>>>model but for the new members of the Board, >>>>>>it needs to be explained. We have people >>>>>>with various and strong CV, but mostly no >>>>>>ICANN experience for some of them. >>>>>>Knowledge sharing is useful then, but it is >>>>>>still necessary to have a partner who is willing to listen. >>>>>>Regards >>>>>> >>>>>> >>>>>> >>>>>>Louis Houle >>>>>> >>>>>> >>>>>>President >>>>>> >>>>>> >>>>>>ISOC Quebec >>>>>> >>>>>> >>>>>><mailto:Louis.Houle@isoc.quebec>Louis.Houle@isoc.quebec >>>>>> >>>>>>Le 2016-05-12 12:49, Thomas Lowenhaupt a écrit : >>>>>>>Joly, >>>>>>>In response to my post contending that the >>>>>>>multistakeholder model was not effectively >>>>>>>meeting the needs of individual Internet >>>>>>>users (IIUs) in New York City you said: >>>>>>> * "âBut are we? ALS's and >>>>>>> individuals can join RALOs, who in turn >>>>>>> can influence the ALAC, who advise the ICANN board." >>>>>That's correct. And that's what I'm doing right now. >>>>> * "Or do you mean locally? Well, we >>>>> elect our representatives on the NYC City >>>>> Council, who are subject to their >>>>> constituents, at least in theory." >>>>> Following that line of thought we really >>>>> don't need a city council or mayor at all. >>>>> After all, we also have a democratically >>>>> elected congress and president. Why bother >>>>> with city government? Just call your >>>>> congress member about the pothole, garbage >>>>> pickup, or idea for a park improvement. And >>>>> indeed you can. But my congress member >>>>> represents about 700,000 people and avers >>>>> to the local council member who represents >>>>> 160,000 residents. He has close ties, that >>>>> include budgetary control, with the local >>>>> service providers - the pothole fillers, >>>>> sanitation and parks departments. So for >>>>> local service delivery issues it's better >>>>> to go local. And in this instance, with >>>>> .nyc, I think we have agreed to go down one >>>>> more layer and engage the stakeholders in >>>>> the process. And indeed, ICANN talks >>>>> bottom-up and multistakeholder. Minimally, >>>>> minimally, ICANN could send a notification >>>>> to the local ALSs when a city registry >>>>> agreement change is proposed. And it would >>>>> seem reasonable to provide the opportunity >>>>> for that ALS to respond, and for that >>>>> response to be considered. One might argue >>>>> that it is the ALS's responsibility to keep >>>>> an eye on ICANN's activities. And that's a >>>>> good idea. And I support and look forward >>>>> to the day when we're provided by ICANN >>>>> with a budget to hire a staff member for >>>>> that task. But for now it seems ICANN's >>>>> generating a letter about proposed changes >>>>> to the registry agreement is the simpler way to go. >>>>> * "There was an advisory board for >>>>> .nyc. It hardly met, and the meetings it >>>>> had were closed. You were on it. It >>>>> could've done something to break its chains >>>>> if the will was there, surely.â" As I >>>>> recall the situation, the city created the >>>>> advisory board under duress - there was a >>>>> challenge to their .nyc application from >>>>> Connecting.nyc Inc. After the .NYC >>>>> Community Advisory Board's creation the >>>>> city retained tight control over its >>>>> operation. It appointed members, scheduled >>>>> the meetings, and set the agenda. I >>>>> informed media-types about the meetings, >>>>> but they were excluded by the >>>>> representatives of the mayor. Additionally, >>>>> even city officials were excluded. Council >>>>> member Gale Brewer's representative, whom I >>>>> invited, was told to leave the room when he >>>>> showed up. And as I mentioned previously, >>>>> when they abolished it on December 31, 2014 >>>>> they wiped out any sign of its existence >>>>> from its website. But you're right, those >>>>> chains probably could have been broken >>>>> short of self-immolation. I just never >>>>> figured out how. Where are we now? While >>>>> we've taken a hit with the abolition of the >>>>> .NYC Community Advisory Board, I'm still >>>>> trying to get a governance process started >>>>> where IIUs can meaningfully participate in >>>>> a governance process. My latest thought is >>>>> to get ICANN, via the ALSs, on board and >>>>> advocating for a multistakeholder >>>>> governance process, one that includes IIUs. >>>>> Any thoughts on how to achieve this are most welcomed. >>>>> Best, >>>>> Tom Lowenhaupt >>>>> On 5/12/2016 1:19 AM, Joly MacFie wrote: >>>>>> On Thu, May 12, 2016 at 12:09 AM, >>>>>> Thomas Lowenhaupt >>>>>> <<mailto:toml@communisphere.com>toml@communisphere.com > wrote: >>>>>> The point I'm trying to make is: If >>>>>> we've all accepted the multistakeholder >>>>>> model, how is it that the local ALSes and >>>>>> individual Internet users (residents and >>>>>> organizations as well) are left out of the decision making process? >>>>>> Tom >>>>>> >>>>>> âBut are we? ALS's and >>>>>> individuals can join RALOs, who inturn can >>>>>> influence the ALAC, who advise the ICANN board. >>>>>> >>>>>> Or do you mean locally? Well, we >>>>>> elect our representatives on the NYC City >>>>>> Council, who are subject to their constituents, at least in theory. >>>>>> >>>>>> There was an advisory board for >>>>>> .nyc. It hardly met, and the meetings it >>>>>> had were closed. You were on it. It >>>>>> could've done something to break its chains if the will was there, surely.â >>>>>> >>>>>> âjâ >>>>>> >>>>>> >>>>>> -- >>>>>> --------------------------------------------------------------- >>>>>> Joly MacFie 218 565 9365 <Skype:punkcast>Skype:punkcast >>>>>> -------------------------------------------------------------- >>>>>> - >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> ------ >>>>> >>>>> >>>>> NA-Discuss mailing list >>>>> >>>>> <mailto:NA-Discuss@atlarge-lists.icann.org> >>>>> >>>>> NA-Discuss@atlarge-lists.icann.org >>>>> >>>>> >>>>> >>>>> >>>>> https://atlarge-lists.icann.org/mailman/listinfo/na-discuss >>>>> >>>>> >>>>> >>>>> Visit the NARALO online at >>>>> >>>>> <http://www.naralo.org>http://www.naralo.org >>>>> >>>>> >>>>> ------
Tom, Maybe the staff could suggest another tool if Surveymonkey isn't OK. It's the most popular according to worldstream: http://www.wordstream.com/blog/ws/2014/11/10/best-online-survey-tools Louis Houle President ISOC Quebec Louis.Houle@isoc.quebec Le 2016-05-13 16:16, Thomas Lowenhaupt a écrit :
Louis,
It certainly would be good to know the level of engagement for IIUs in Paris and the other newly TLD'd cities. Perhaps the At-Large could craft a questionnaire to gather the state of affairs, to be distributed as widely as practicable. Certainly one might imagine excellent penetration in those cities with ALSes. From there we might develop a report of use to many.
What's the best tool for creating a questionnaire these days? Surveymonkey <https://www.surveymonkey.com/> seems to be priced right? Anyone with experience in this area? Is there a better alternative? Are there others in the ICANN community that might be interested in a project of this sort?
Best,
Tom Lowenhaupt
On 5/13/2016 2:51 PM, Louis Houle wrote:
Hi Tom,
Why is the situation rather opaque in .NYC. Because inclusiveness is not promoted ? Because transparency is not an integrated process in the pratices of the management team (the meetings are held behind closed doors? )
Governments obey to a set of rules and processes that they control. This includes the input or contribution from third parties regarding the direction to follow the management approach, etc. I understand that this the situation that you're cought with.
Your suggestion to get ICANN on board is certainly appropriate. Is it the only approach for you to advocate for a governance process for NYC? I don't know if other city TLD are facing a similar situation as the one you described. For instance, Dot-Paris is managed by the city under the authority of the mayer. Would it be useful to document how they address governance issues including the multistakeholder model ? Would it be useful to get the GeoTLD Interest Group on board also?
At Dot-Quebec, the Board adopted a very openned governance approach. Anybody who can contribute is welcome, but it's a not-for-profit organisation. It's not lead by the government even though we received a financial and political support for the project. We support the multistakeholder model but for the new members of the Board, it needs to be explained. We have people with various and strong CV, but mostly no ICANN experience for some of them. Knowledge sharing is useful then, but it is still necessary to have a partner who is willing to listen.
Regards
Louis Houle President ISOC Quebec Louis.Houle@isoc.quebec
Le 2016-05-12 12:49, Thomas Lowenhaupt a écrit :
Joly,
In response to my post contending that the multistakeholder model was not effectively meeting the needs of individual Internet users (IIUs) in New York City you said:
* "But are we? ALS's and individuals can join RALOs, who in turn can influence the ALAC, who advise the ICANN board."
That's correct. And that's what I'm doing right now.
* "Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory."
Following that line of thought we really don't need a city council or mayor at all. After all, we also have a democratically elected congress and president. Why bother with city government? Just call your congress member about the pothole, garbage pickup, or idea for a park improvement. And indeed you can. But my congress member represents about 700,000 people and avers to the local council member who represents 160,000 residents. He has close ties, that include budgetary control, with the local service providers - the pothole fillers, sanitation and parks departments. So for local service delivery issues it's better to go local. And in this instance, with .nyc, I think we have agreed to go down one more layer and engage the stakeholders in the process. And indeed, ICANN talks bottom-up and multistakeholder. Minimally, minimally, ICANN could send a notification to the local ALSs when a city registry agreement change is proposed. And it would seem reasonable to provide the opportunity for that ALS to respond, and for that response to be considered. One might argue that it is the ALS's responsibility to keep an eye on ICANN's activities. And that's a good idea. And I support and look forward to the day when we're provided by ICANN with a budget to hire a staff member for that task. But for now it seems ICANN's generating a letter about proposed changes to the registry agreement is the simpler way to go.
* "There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely."
As I recall the situation, the city created the advisory board under duress - there was a challenge to their .nyc application from Connecting.nyc Inc. After the .NYC Community Advisory Board's creation the city retained tight control over its operation. It appointed members, scheduled the meetings, and set the agenda. I informed media-types about the meetings, but they were excluded by the representatives of the mayor. Additionally, even city officials were excluded. Council member Gale Brewer's representative, whom I invited, was told to leave the room when he showed up. And as I mentioned previously, when they abolished it on December 31, 2014 they wiped out any sign of its existence from its website. But you're right, those chains probably could have been broken short of self-immolation. I just never figured out how. Where are we now? While we've taken a hit with the abolition of the .NYC Community Advisory Board, I'm still trying to get a governance process started where IIUs can meaningfully participate in a governance process. My latest thought is to get ICANN, via the ALSs, on board and advocating for a multistakeholder governance process, one that includes IIUs. Any thoughts on how to achieve this are most welcomed.
Best,
Tom Lowenhaupt
On 5/12/2016 1:19 AM, Joly MacFie wrote:
On Thu, May 12, 2016 at 12:09 AM, Thomas Lowenhaupt <toml@communisphere.com> wrote:
The point I'm trying to make is: If we've all accepted the multistakeholder model, how is it that the local ALSes and individual Internet users (residents and organizations as well) are left out of the decision making process?
Tom
But are we? ALS's and individuals can join RALOs, who inturn can influence the ALAC, who advise the ICANN board.
Or do you mean locally? Well, we elect our representatives on the NYC City Council, who are subject to their constituents, at least in theory.
There was an advisory board for .nyc. It hardly met, and the meetings it had were closed. You were on it. It could've done something to break its chains if the will was there, surely.
j
-- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online athttp://www.naralo.org ------
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online at http://www.naralo.org ------
Following up on the recent exchange here on NARALO Discuss, concerning the 4 changes to New York City's .nyc registry agreement, and my belief that modification to the extant operating processes were in order, today I reviewed the ICANN By-Laws <https://www.icann.org/resources/pages/governance/bylaws-en#XI> as they relate to ALAC responsibilities. And it seems apparent that more should be done to keep New York City's individual Internet users informed and engaged about ICANN activities. I base this conclusion on my reading of Article XI, subsection 2.4.j which lists 10 responsibilities of ALAC. If one considers responsibilities 2, 4, 5, 6, and 10, one is likely to conclude that something fell through the cracks <https://en.wiktionary.org/wiki/fall_through_the_cracks> in the 4 instances where the registry agreement was changed and the city's individual Internet users were not informed. "The ALAC is also responsible, working in conjunction with the RALOs, for coordinating the following activities: 1. Making a selection by the At-Large Community to fill Seat 15 on the Board. Notification of the At-Large Community's selection shall be given by the ALAC Chair in writing to the ICANN Secretary, consistent with Article VI, Sections 8(4) and 12(1). 2. *Keeping the community of individual Internet users informed about the significant news from **ICANN**;* 3. Distributing (through posting or otherwise) an updated agenda, news about ICANN, and information about items in the ICANN policy-development process; 4. *Promoting outreach activities in the community of individual Internet users;* 5. *Developing and maintaining on-going information and education programs, regarding **ICANN**and its work;* 6. *Establishing an outreach strategy about **ICANN**issues in each RALO's Region;* 7. Participating in the ICANN policy development processes and providing input and advice that accurately reflects the views of individual Internet users; 8. Making public, and analyzing, ICANN's proposed policies and its decisions and their (potential) regional impact and (potential) effect on individuals in the region; 9. Offering Internet-based mechanisms that enable discussions among members of At-Large structures; and 10. *Establishing mechanisms and processes that enable two-way communication between members of At-Large Structures and those involved in **ICANN**decision-making, so interested individuals can share their views on pending **ICANN**issues."* Think about it... Between December 1, 2014 and March 31, 2016 four (4) changes were made to the .nyc registry agreement <https://www.icann.org/resources/agreement/nyc-2014-01-23-en>. No effort was made to inform New York City's individual Internet users about these changes or their possible impact. After reading clauses 2, 4, 5, 6 and 10 does anyone disagree with my conclusion, that more should be done to keep New York City's individual Internet users informed and engaged about ICANN activities? If there 's no disagreement, how do we move ahead to assure that ALAC responsibilities, as spelled out in Article XI of ICANN's By-Laws, are appropriately adhered to in the future? Sincerely, Tom Lowenhaupt
Tom, I apologize if I have not been duly diligent in this matter. What in particular in the changes to the registry agreement is the cause for concern? j On Sun, May 15, 2016 at 10:52 PM, Thomas Lowenhaupt <toml@communisphere.com> wrote:
Following up on the recent exchange here on NARALO Discuss, concerning the 4 changes to New York City's .nyc registry agreement, and my belief that modification to the extant operating processes were in order, today I reviewed the ICANN By-Laws <https://www.icann.org/resources/pages/governance/bylaws-en#XI> as they relate to ALAC responsibilities. And it seems apparent that more should be done to keep New York City's individual Internet users informed and engaged about ICANN activities.
I base this conclusion on my reading of Article XI, subsection 2.4.j which lists 10 responsibilities of ALAC. If one considers responsibilities 2, 4, 5, 6, and 10, one is likely to conclude that something fell through the cracks <https://en.wiktionary.org/wiki/fall_through_the_cracks> in the 4 instances where the registry agreement was changed and the city's individual Internet users were not informed.
"The ALAC is also responsible, working in conjunction with the RALOs, for coordinating the following activities:
1. Making a selection by the At-Large Community to fill Seat 15 on the Board. Notification of the At-Large Community's selection shall be given by the ALAC Chair in writing to the ICANN Secretary, consistent with Article VI, Sections 8(4) and 12(1). 2. *Keeping the community of individual Internet users informed about the significant news from **ICANN**;* 3. Distributing (through posting or otherwise) an updated agenda, news about ICANN, and information about items in the ICANN policy-development process; 4. *Promoting outreach activities in the community of individual Internet users;* 5. *Developing and maintaining on-going information and education programs, regarding **ICANN** and its work;* 6. *Establishing an outreach strategy about **ICANN** issues in each RALO's Region;* 7. Participating in the ICANN policy development processes and providing input and advice that accurately reflects the views of individual Internet users; 8. Making public, and analyzing, ICANN's proposed policies and its decisions and their (potential) regional impact and (potential) effect on individuals in the region; 9. Offering Internet-based mechanisms that enable discussions among members of At-Large structures; and 10. *Establishing mechanisms and processes that enable two-way communication between members of At-Large Structures and those involved in * *ICANN** decision-making, so interested individuals can share their views on pending **ICANN** issues."*
Think about it... Between December 1, 2014 and March 31, 2016 four (4) changes were made to the .nyc registry agreement <https://www.icann.org/resources/agreement/nyc-2014-01-23-en>. No effort was made to inform New York City's individual Internet users about these changes or their possible impact. After reading clauses 2, 4, 5, 6 and 10 does anyone disagree with my conclusion, that more should be done to keep New York City's individual Internet users informed and engaged about ICANN activities?
If there 's no disagreement, how do we move ahead to assure that ALAC responsibilities, as spelled out in Article XI of ICANN's By-Laws, are appropriately adhered to in the future?
Sincerely,
Tom Lowenhaupt
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online at http://www.naralo.org ------
-- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast ISOC-NY - http://isoc-ny.org ---------------------------------------------------------------
Joly, You asked about my cause for concern regarding the changes to the .nyc registry agreement. They are twofold. I’ve some specific concerns about the several changes to the .nyc registry that were undertaken without consulting New York City's individual Internet users. But I’ve broader concerns that center on a governance process that has excluded New York City’s individual Internet users (IIUs) from meaningful participation in scoping and imagining our city’s TLD in every phase of its development and ongoing operation. I review that situation below and conclude with some actions that might help correction the situation. But first, let me address your question about the changes to the .nyc registry agreement. * All Digit/Digit, Letter/Digit, and Digit/Letter Two-Character ASCII Labels at the Second Level <https://www.icann.org/en/system/files/files/spec5-amend-two-char-01dec14-en.pdf>(01 December 2014) This change seems quite reasonable to me. * Letter/Letter Two-Character ASCII Labels <https://www.icann.org/sites/default/files/tlds/nyc/nyc-auth-ltr-ltr-26may15-en.pdf>(26 May 2015) This change also seems reasonable. However, with 1/2 our city's 8 million population foreign born, some might have submitted comments about domain names such as mx.nyc: perhaps suggesting that it be used to address the needs of New York City's 300,000 Mexican immigrants. Or perhaps some of the 800,000 residents with ties to the Dominican Republic would have had suggestions about do.nyc's potential to serve that community. But they (nor the Chinese, Nigerians, Bolivians, etc.) were never provided with that opportunity. One is left to wonder what might have emerged from the minds of those 4,000,000 foreign born and the other New Yorkers. * Letter/Letter Two-Character ASCII Labels <https://www.icann.org/sites/default/files/tlds/nyc/nyc-auth-ltr-ltr-14mar16-en.pdf>(14 March 2016) My comments for the 4 2-character domains activated here (ac, in, na, vg) are similar to those authorized by the 26 May 2015 change above. But seeing the “in” domain name, and with my residence located in “Little India,” and long holding hope of one day traveling to that wonderful country, I dreamt about traveling there and finding a nyc.mumbai, nyc.chennai, or nyc.bangalore, and how they might ease navigation and add comfort to my visit. And on another level I wondered if these domain names might provide an opportunity to establish bilateral social, cultural, and economic exchanges between these great cities? * PDF <https://www.icann.org/sites/default/files/tlds/nyc/nyc-amend-1-pdf-31mar16-e...> With this change (which added 14 new RDDS fields to each domain name’s contact data) I'm curious about the impact it will have on the city's nexus policy. Nexus is a key .nyc feature that offers the potential to differentiate our city’s TLD from the 1000 competitors that strive to sell domain names to our residents and organizations. The policy was arrived at after much consideration and years of urging on our part. Had New York's independent Internet users been consulted here, it might have sparked a broader conversation about the nexus policy . For example, how well it is being enforced, its impact on privacy, how does registration transparency help or hinder name sales, etc. As well, it might have enabled a discussion about open data and bulk access to the registrant data, something the city has refused to share. Let me conclude these thoughts by reiterating that they are my individual concerns and not those of my fellow New Yorkers who were not offered the opportunity to comment on these matters. *Getting back to my broader concern… * When one considers that the city administration has never had a meaningful consultation with NYC's individual Internet users, not during the long process leading up to the submission of the application for the .nyc TLD, nor in the years since its submission, one wonders about how well the public interest is being served and the efficacy of the multistakeholder model, the foundation for Internet governance. And when one considers that there's no ongoing channel enabling New York’s IIUs to participate in a local, home grown, governance process, the At-Large must ask how well the .nyc TLD is advancing the public interest. **What**’s **to **be **done**?** Short term the following: * NARALO, then ALAC should pass a resolution calling for ICANN to redouble its efforts to facilitate engagement of New York City’s IIUs in considering registry changes that impact the operation of the .nyc TLD. (This policy might apply more broadly, e.g., to dotCities globally, but that’s subject to some research. See below.) o The resolution should require that ICANN staff immediately begin sending notifications to local At-Large Structures when the operator of a city-TLD in their realm makes application to modify a registry agreement. o The resolution should include a recommendation that these ALSes be provided with the opportunity to comment on all proposed changes to the registry agreement at traditional ICANN PDPs and locally at open public hearings. (Recognizing that a contract is in place, the ICANN should recommend that appropriate changes take place ASAP, noting that they will seek permanency upon renewal of the registry agreement.) * At-Large Structures located in other cities with TLDs should be asked to assess the level of engagement by IIUs in TLD policy development processes. If the engagement level is unsatisfactory, ICANN should work to facilitate more involvement by IIUs, working through ALSes when practicable. * In cities without At-Large Structures ICANN should determine the level of engagement by IIUs. In instances where it is found to be unsatisfactory, ICANN should seek remediation through the formation of effective At-Large Structures. Long term: * ICANN should require that cities applying for TLDs demonstrate in their applications that a suitable level of "informed consent" about a TLD’s potential role exists in the jurisdiction. * That participants in a multistakeholder environment have been appraised of the opportunities provided by a city-TLD and have been meaningfully engaged in the application’s development. * That cities applying for TLDs incorporate the opinions of residents and independent Internet users when preparing their applications. * That At-Large Structures or similar entities be created to enable long-term engagement by IIUs in the operation of the city-TLD. (Note, there's an obvious At-Large self-interest in such a resolution as it might provide a basis for future development of local At-Large structures.) I hope this answers your question. In support of the above I’d like to see if New York is alone in regard to the exclusion of IIUs from the city-TLD governance process. I’ve compiled two lists of cities that have been issued TLDs: those that have At-Large Structures (13) and those with ISOC chapters (22). There’s some overlap. I’ve begun a Google questionnaire to gather some info here <https://docs.google.com/forms/d/1MO5f2u8aFMxnBEu3I6UICIjl0as12wKgzBMf3f3Hwg0...>. Your thoughts would be greatly appreciated. [_This invite applies to all, not just Joly._] Sincerely, Tom Lowenhaupt ------------------------------------------------------------------------ On 5/16/2016 1:41 AM, Internet Society - NY Chapter wrote:
Tom,
I apologize if I have not been duly diligent in this matter.
What in particular in the changes to the registry agreement is the cause for concern?
j
On Sun, May 15, 2016 at 10:52 PM, Thomas Lowenhaupt <toml@communisphere.com <mailto:toml@communisphere.com>> wrote:
Following up on the recent exchange here on NARALO Discuss, concerning the 4 changes to New York City's .nyc registry agreement, and my belief that modification to the extant operating processes were in order, today I reviewed the ICANN By-Laws <https://www.icann.org/resources/pages/governance/bylaws-en#XI> as they relate to ALAC responsibilities. And it seems apparent that more should be done to keep New York City's individual Internet users informed and engaged about ICANN activities.
I base this conclusion on my reading of Article XI, subsection 2.4.j which lists 10 responsibilities of ALAC. If one considers responsibilities 2, 4, 5, 6, and 10, one is likely to conclude that something fell through the cracks <https://en.wiktionary.org/wiki/fall_through_the_cracks> in the 4 instances where the registry agreement was changed and the city's individual Internet users were not informed.
"The ALAC is also responsible, working in conjunction with the RALOs, for coordinating the following activities:
1. Making a selection by the At-Large Community to fill Seat 15 on the Board. Notification of the At-Large Community's selection shall be given by the ALAC Chair in writing to the ICANN Secretary, consistent with Article VI, Sections 8(4) and 12(1). 2. *Keeping the community of individual Internet users informed about the significant news from **ICANN**;* 3. Distributing (through posting or otherwise) an updated agenda, news about ICANN, and information about items in the ICANN policy-development process; 4. *Promoting outreach activities in the community of individual Internet users;* 5. *Developing and maintaining on-going information and education programs, regarding **ICANN**and its work;* 6. *Establishing an outreach strategy about **ICANN**issues in each RALO's Region;* 7. Participating in the ICANN policy development processes and providing input and advice that accurately reflects the views of individual Internet users; 8. Making public, and analyzing, ICANN's proposed policies and its decisions and their (potential) regional impact and (potential) effect on individuals in the region; 9. Offering Internet-based mechanisms that enable discussions among members of At-Large structures; and 10. *Establishing mechanisms and processes that enable two-way communication between members of At-Large Structures and those involved in **ICANN**decision-making, so interested individuals can share their views on pending **ICANN**issues."*
Think about it... Between December 1, 2014 and March 31, 2016 four (4) changes were made to the .nyc registry agreement <https://www.icann.org/resources/agreement/nyc-2014-01-23-en>. No effort was made to inform New York City's individual Internet users about these changes or their possible impact. After reading clauses 2, 4, 5, 6 and 10 does anyone disagree with my conclusion, that more should be done to keep New York City's individual Internet users informed and engaged about ICANN activities?
If there 's no disagreement, how do we move ahead to assure that ALAC responsibilities, as spelled out in Article XI of ICANN's By-Laws, are appropriately adhered to in the future?
Sincerely,
Tom Lowenhaupt
------ NA-Discuss mailing list NA-Discuss@atlarge-lists.icann.org <mailto:NA-Discuss@atlarge-lists.icann.org> https://atlarge-lists.icann.org/mailman/listinfo/na-discuss
Visit the NARALO online at http://www.naralo.org ------
On 19 May 2016 at 19:33, Thomas Lowenhaupt <toml@communisphere.com> wrote:
But I’ve broader concerns that center on a governance process that has excluded New York City’s individual Internet users (IIUs) from meaningful participation in scoping and imagining our city’s TLD in every phase of its development and ongoing operation.
First you have to argue the point that New York City citizens have more of an entitlement to oversee the operation of its TLD than they do over other day-to-day municipal issues such as trash, police or transit. You have not established that case yet. with 1/2 our city's 8 million population foreign born, some might have
submitted comments about domain names such as mx.nyc: perhaps suggesting that it be used to address the needs of New York City's 300,000 Mexican immigrants.
Evidence, please. I invite you to find ONE Mexican immigrant to NYC who gives a damn about this. The relevance of "MX" to Mexico in TLD space *only* relates to the ISO codes for countries used in their ccTLD designations. It has no special relevance in gTLD space. Why should Mexicans care more about the governance of mx.nyc than mexico.nyc, mex.nyc or (since we're talking about individuals) mexicanos.nyc? Or, better still, rather than just take a wild guess that anyone would care, you actually could have ASKED THEM <http://apemny.org/en/>. But then, it's easier to demand other volunteers to to all the hard slogging than to actually add any evidence to the debate. There is no basis to the assertion that there is any special reason to care about the governance of two letter second-level domains (as opposed to any other 2LDs). This issue is a remnant of the GAC's wish at one point to reserve all two-letter domains for the use of national governments.
Or perhaps some of the 800,000 residents with ties to the Dominican Republic would have had suggestions about do.nyc's potential to serve that community. But they (nor the Chinese, Nigerians, Bolivians, etc.) were never provided with that opportunity. One is left to wonder what might have emerged from the minds of those 4,000,000 foreign born and the other New Yorkers.
So let me get this straight ... your call for the ALAC and NARALO and ICANN staff to engage in a whole slew of resource-sapping activity is based on your sense of wonder?
My comments for the 4 2-character domains activated here (ac, in, na, vg) are similar to those authorized by the 26 May 2015 change above. But seeing the “in” domain name, and with my residence located in “Little India,” and long holding hope of one day traveling to that wonderful country, I dreamt about traveling there and finding a nyc.mumbai, nyc.chennai, or nyc.bangalore, and how they might ease navigation and add comfort to my visit.
How colonial. You might be more likely to find न्यूयॉर्क.चेन्नई, no? Or, better still, a llow me to introduce you to Google , Yelp and TripAdvisor . They may offer the help you seek . And , unlike the product of dreams and wonders, they exist today. In any case, when I think of intuitive uses for the domain "in.nyc", India is not a factor at all.
With this change (which added 14 new RDDS fields to each domain name’s contact data) I'm curious about the impact it will have on the city's nexus policy.
Curiosity, like wish and wonder, does not form a sound basis for policy development, especially that which commits other volunteers to act. I have yet to see any logic or evidence here, just emotions. Ah, enough of this. Life's too short for me to be wasting my time any further in deconstructing this list of hopes, dreams and entitlements masquerading as advocacy. It's an utterly baseless foundation for action. Suffice it to say I would argue vigorously against NARALO indulging activity based on what is presently on offer. - Evan
On 16 May 2016 at 04:52, Thomas Lowenhaupt <toml@communisphere.com> wrote:
Following up on the recent exchange here on NARALO Discuss, concerning the 4 changes to New York City's .nyc registry agreement, and my belief that modification to the extant operating processes were in order, today I reviewed the ICANN By-Laws <https://www.icann.org/resources/pages/governance/bylaws-en#XI> as they relate to ALAC responsibilities. And it seems apparent that more should be done to keep New York City's individual Internet users informed and engaged about ICANN activities.
I fervently disagree, both that "more should be done" and even defining what that "more" is. This is getting tiring. Every so often we see raised the issue of community involvement in .nyc. Every time the challenges, problems and bad assumption identified in the grievance is ignored. Then the discussion just drops, only to come back some time later raise the issue again as if it's brand new. I base this conclusion on my reading of Article XI, subsection 2.4.j which
lists 10 resp o nsibilities of ALAC. If one considers responsibilities 2, 4, 5, 6, and 10, one is likely to conclude that something fell through the cracks <https://en.wiktionary.org/wiki/fall_through_the_cracks> in the 4 instances where the registry agreement was changed and the city's individual Internet users were not informed.
Quoting the ICANN bylaws is FAR from enough. I've been extremely close to those bylaws and have frequently made the case that ALAC under-utilized its authority on a number of occasions.
This is not one of those occasions.
Think about it... Between December 1, 2014 and March 31, 2016 four (4) changes were made to the .nyc registry agreement <https://www.icann.org/resources/agreement/nyc-2014-01-23-en>. No effort was made to inform New York City's individual Internet users about these changes or their possible impact.
I thought about it. For a long time, a long time ago. BIG DEAL. I looked at the changes. They apply to the use of two-letter second-level domains and the collection of additional information on registrants to verify their legitimacy to use the domain.
After reading clauses 2, 4, 5, 6 and 10 does anyone disagree with my conclusion, that more should be done to keep New York City's individual Internet users informed and engaged about ICANN activities?
Specifically, what in the proposed changes does the end-user community of New York City (meaning some group of people significant larger then you alone) have a problem with? If your problem is with process rather than substance, it is my opinion that you're wasting our time. The registry for .nyc is the city government of New York, governed by elected representatives. Moreover, previously when you have raised issued related to .nyc you refuse to answer core questions that challenge what are IMO poor assumptions, and your refusal to provide satisfactory answers has crippled the credibility of your cause. - Given that you've been around the process for a while, you know that ALAC is a global body and its advice to ICANN is not country- (let alone city-)specific. Why, then, have you made no effort to engage in joint activity with other communities where city-TLDs exist, in order to facilitate creation of policy adaptable to a worldwide community? - If the effort has been made but no similar issues have been found at other cities with their own TLDs, that begs a different question: what's so special about the problems with .nyc, that makes it sufficiently worthy to demand attention from other regions and the global ALAC? In both theory and practice, ALAC advice to the Board is neither domain specific nor region specific. - After years of asking, I have yet to hear a satisfactory answer to the question "what is the end-user community interest, specifically, in the .nyc domain, that could not be served through a second-level domain?" If there 's no disagreement, how do we move ahead to assure that ALAC
responsibilities, as spelled out in Article XI of ICANN's By-Laws, are appropriately adhered to in the future?
Consider disagreement had. Tom, you've also been here long enough to know that ALAC volunteers are stretched beyond belief in just taking care of real fires. Since you appear to know the bylaws and ALAC's role so well, why don't you *propose* something rather than merely expect others to fight your battles for you? In any case.... until you can demonstrate that (a) this is a globally relevant problem and (b) it indeed harms end users and (c) creative solutions have been tried and failed .... this is not yet NARALO's (let alone ALAC's) battle. Apologies to readers for what may have come across as overly harsh. But I'm honestly tired of this issue repeatedly advancing and receding, each time draining critical human energy better directed elsewhere. -- Evan Leibovitch Geneva, CH Em: evan at telly dot org Sk: evanleibovitch Tw: el56
participants (6)
-
Alan Greenberg -
Evan Leibovitch -
Internet Society - NY Chapter -
Joly MacFie -
Louis Houle -
Thomas Lowenhaupt