[At-Large] FRIENDLY REMINDER: Review on Trusted Community Representation #Root #Zone #DNSSEC [Call for Comments]

[Aida Noblia]

Dear Salanieta:

  I was unable to add my comments on the wiki because the editor does not
load, although I tried several times.

My comment was sent yesterday LACRALO <
lac-discuss-es at atlarge-lists.icann.org> list in spanish, and I copy this
below,  with a variant cleared on that list in another mail, in which I
send it deleted the wrong paragraph .

Best Regards


I agree with the draft Salanieta with the observations made by Olivier ,
except the issue of financing , which I agree with Alexander. The word "
sacred " could be changed to " solemn " because it is a solemnity and
compliance is an essential requirement in the process of KSK .

Responsibility regarding the control of TCR , which mentions Alexander on
ensuring transparency , accountability , and defending the Internet users,
and is set to generic point 9 of the Statement of Commitment between the
Department of Commerce U.S. and ICANN , (the first document cited by
Salanieta ) .

 Moreover, the entire process of the ceremony itself is a guarantee of
transparency and protection of users . There are strict controls and
detailed in the DNSSEC Practice Statement of the procedure for
accreditation of entry of persons, etc., for the Root Zone Operator (TCR )
, your responsibilities are established and each of the steps you must
follow what is proper documents governing safety at these levels of the
root.

 There are also prerequisites for the selection and appointment of the TCR
, instructions for its function.That's part of the technical process of the
company Verisign , specialist in informatic security .

 As for the number of TCR , understand that it is reasonable and who
applied for the position, must know and accept their demands were selected
according to rules and monitored compliance with requirements and is
scheduled for the 21 selected will be appointed only some will setected ( 6
or 8) for two ceremonies that simultaneously at different locations each
year in four opportunities . The amount would be more to cover possible
contingencies.

Regarding see major funding strictly maintain the independence of the
process being controlled , between those who are appointed to control the
process and who is responsible of it, in these last ICANN. This, besides
exposing Alexander and there are many whose travel costs that could and
perhaps should be without, given the possibility of remote participation ,
which is not the case of the TCR , which have be physically present .






2014-02-04 Salanieta T. Tamanikaiwaimaro <
salanieta.tamanikaiwaimaro at gmail.com>:

> Dear All,
>
> The call for comments from At Large closes on 7th February, 2014.
>
> There is currently some difference in views on whether the Trusted
> Community Representatives (TCRs) should have indefinite terms of whether
> this should rotated.
>
> Should TCRs continue to remain self funded or should they be funded?
>
> There are also a few other important aspects of this that we would like to
> consult the wider community on before amending the draft. For those of you
> who have already commented, thank you. I am mindful that we still have not
> heard from others. Feel free to comment directly on the wiki via the link
> below or by responding to this thread.
>
> https://community.icann.org/x/nge6Ag
>
> Your input into this process will help us finalize the Draft. May we have
> your views please?
>
> Kind Regards,
> Sala
>
>
> On Mon, Feb 3, 2014 at 7:45 AM, Salanieta T. Tamanikaiwaimaro <
> salanieta.tamanikaiwaimaro at gmail.com> wrote:
>
> > Dear All,
> >
> > This is just a friendly reminder in case you missed it that there is an
> > ongoing Review on Trusted Community Representation in Root Zone DNSSEC
> Key
> > Signing Ceremonies. Grateful if the RALO Chairs could also ask their
> > members for their views.
> >
> > For the benefit of the general community at large and those who have just
> > entered the community, you would have been advised at some point that
> > anyone in At Large can have their say on aspects of Policies either
> > individually as you comment directly on the site to the staff concerned
> or
> > as we in the At Large community do it through the At Large channels by
> way
> > of the "Wiki" or through email discussions.
> >
> > If you would like to comment on the Draft Statement currently being
> > developed by the At Large on this matter, visit:
> >
> >
> >
> https://community.icann.org/display/alacpolicydev/At-Large+Review+of+Trusted+Community+Representation+in+Root+Zone+DNSSEC+Key+Signing+Ceremonies+Workspace?focusedCommentId=46498543#comment-46498543
> >
> > If you are finding that you have difficulties posting your comment on the
> > wiki, feel free to respond to this thread and post your thoughts. On the
> > wiki you will see that the Review Team had laid several questions for the
> > public and wider community. This can help guide your comments and to
> have a
> > fair idea of the areas that they want and value your feedback on. The At
> > Large will close the call for comments on the 7th of February, 2014 so
> get
> > your thoughts in if you want them factored in.
> >
> > In case you do not have a profile to enable you to post on the Wiki
> (ICANN
> > Confluence) - please contact At Large staff offline.
> >
> > Kind Regards,
> > Sala
> >
> _______________________________________________
> At-Large mailing list
> At-Large at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/at-large
>
> At-Large Official Site: http://atlarge.icann.org
>



-- 
Aida Noblia