Mailing Lists
[ALAC] Draft Security, Stability and Resiliency Report - development of an ALAC Statement
Posted June 10th, 2009 by Mailing list user
Dear DNS Security Issues Working Group leaders,
cc: DNS Security Issues Working Group members and ALAC Members
At its meeting yesterday, the ALAC Executive Committee reviewed the At-Large
Policy Advice Development calendar (please see:
www.atlarge.icann.org/policycalendar) to bring it up to date in advance of
the Sydney meeting.
The public comment period on the Draft Security, Stability and Resiliency
Report is open until 19 June (see:
http://www.icann.org/en/public-comment/#ssr). The ALAC Executive Committee
is requesting that the DNS Security Issues Working Group develop the
At-Large statement by 12 June. The ALAC will then have a five-day vote on
this draft statement between 13-18 June.
We were asked to contact you to ask if you and the other members of the DNS
Security Issues Working Group will be able to develop this draft statement.
Please note that Greg Rattray, ICANN's Chief Internet Security Advisor,
will be holding a briefing on the Draft Security, Stability and Resiliency
Report on Wednesday, 10 June UTC. Details of this briefing, including
participation information and the link to the Adobe Connect chat room are
available at:
https://st.icann.org/alac/index.cgi/index.cgi?ssr_briefing_call.
We understand that this drafting timeline is an extremely tight deadline.
Given that the briefing on the report is on 10 June, we are asking Greg, who
is the staff person responsible for this issue, whether the formal comments
from ALAC can be delivered up to a week later to allow for a more complete
At-Large contribution on this issue.
Please let us know if we can provide any additional information or
assistance on this issue.
Could you please confirm whether you will be able to produce a draft
statement according to the above schedule? We will confirm with you shortly
whether a week extension will be possible.
Regards,
Nick Ashton-Hart, Heidi Ullrich, Matthias Langenegger, Gisella Gruber-White,
Marie-Helene Bouchoms
ICANN At-Large Staff
email: staff@atlarge.icann.org
_______________________________________________
ALAC mailing list
ALAC@atlarge-lists.icann.org
http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann...
At-Large Online: http://www.atlarge.icann.org
ALAC Working Wiki: http://st.icann.org/alac
[Dns-security-wg] Draft Security, Stability and Resiliency Repor
FWIW, please note that I am working on the IRT report statement (++loads
of work in my day job) and I cannot commit to work on this one.
I would appreciate if someone could handle the development of this statement
Thanks,
Patrick
At Large Staff wrote, On 10/6/09 03:40:
>
> Dear DNS Security Issues Working Group leaders,
>
> cc: DNS Security Issues Working Group members and ALAC Members
>
>
>
> At its meeting yesterday, the ALAC Executive Committee reviewed the
> At-Large Policy Advice Development calendar (please see:
> www.atlarge.icann.org/policycalendar
> ) to bring it up to date
> in advance of the Sydney meeting.
>
>
>
> The public comment period on the Draft Security, Stability and
> Resiliency Report is open until 19 June (see:
> http://www.icann.org/en/public-comment/#ssr). The ALAC Executive
> Committee is requesting that the DNS Security Issues Working Group
> develop the At-Large statement by 12 June. The ALAC will then have a
> five-day vote on this draft statement between 13-18 June.
>
>
>
> We were asked to contact you to ask if you and the other members of
> the DNS Security Issues Working Group will be able to develop this
> draft statement.
>
>
>
> Please note that Greg Rattray, ICANN’s Chief Internet Security
> Advisor, will be holding a briefing on the Draft Security, Stability
> and Resiliency Report on Wednesday, 10 June UTC. Details of this
> briefing, including participation information and the link to the
> Adobe Connect chat room are available at:
> https://st.icann.org/alac/index.cgi/index.cgi?ssr_briefing_call.
>
>
>
> We understand that this drafting timeline is an extremely tight
> deadline. Given that the briefing on the report is on 10 June, we are
> asking Greg, who is the staff person responsible for this issue,
> whether the formal comments from ALAC can be delivered up to a week
> later to allow for a more complete At-Large contribution on this issue.
>
>
>
> Please let us know if we can provide any additional information or
> assistance on this issue.
>
>
>
> Could you please confirm whether you will be able to produce a draft
> statement according to the above schedule? We will confirm with you
> shortly whether a week extension will be possible.
>
>
>
> Regards,
>
> Nick Ashton-Hart, Heidi Ullrich, Matthias Langenegger, Gisella
> Gruber-White, Marie-Helene Bouchoms
> ICANN At-Large Staff
> email: _staff@atlarge.icann.org_
>
>
>
>
>
>
>
--
Patrick Vande Walle
Blog: http://patrick.vande-walle.eu
Twitter: http://www.twitter.com/patrickvw
[Dns-security-wg] Draft Security, Stability and Resiliency Repor
FWIW, please note that I am working on the IRT report statement (++loads
of work in my day job) and I cannot commit to work on this one.
I would appreciate if someone could handle the development of this statement
Thanks,
Patrick
At Large Staff wrote, On 10/6/09 03:40:
>
> Dear DNS Security Issues Working Group leaders,
>
> cc: DNS Security Issues Working Group members and ALAC Members
>
>
>
> At its meeting yesterday, the ALAC Executive Committee reviewed the
> At-Large Policy Advice Development calendar (please see:
> www.atlarge.icann.org/policycalendar
> ) to bring it up to date
> in advance of the Sydney meeting.
>
>
>
> The public comment period on the Draft Security, Stability and
> Resiliency Report is open until 19 June (see:
> http://www.icann.org/en/public-comment/#ssr). The ALAC Executive
> Committee is requesting that the DNS Security Issues Working Group
> develop the At-Large statement by 12 June. The ALAC will then have a
> five-day vote on this draft statement between 13-18 June.
>
>
>
> We were asked to contact you to ask if you and the other members of
> the DNS Security Issues Working Group will be able to develop this
> draft statement.
>
>
>
> Please note that Greg Rattray, ICANN’s Chief Internet Security
> Advisor, will be holding a briefing on the Draft Security, Stability
> and Resiliency Report on Wednesday, 10 June UTC. Details of this
> briefing, including participation information and the link to the
> Adobe Connect chat room are available at:
> https://st.icann.org/alac/index.cgi/index.cgi?ssr_briefing_call.
>
>
>
> We understand that this drafting timeline is an extremely tight
> deadline. Given that the briefing on the report is on 10 June, we are
> asking Greg, who is the staff person responsible for this issue,
> whether the formal comments from ALAC can be delivered up to a week
> later to allow for a more complete At-Large contribution on this issue.
>
>
>
> Please let us know if we can provide any additional information or
> assistance on this issue.
>
>
>
> Could you please confirm whether you will be able to produce a draft
> statement according to the above schedule? We will confirm with you
> shortly whether a week extension will be possible.
>
>
>
> Regards,
>
> Nick Ashton-Hart, Heidi Ullrich, Matthias Langenegger, Gisella
> Gruber-White, Marie-Helene Bouchoms
> ICANN At-Large Staff
> email: _staff@atlarge.icann.org_
>
>
>
>
>
>
>
[ALAC] Draft Security, Stability and Resiliency Report - develop
FWIW, please note that I am working on the IRT report statement (++loads
of work in my day job) and I cannot commit to work on this one.
I would appreciate if someone could handle the development of this statement
Thanks,
Patrick
At Large Staff wrote, On 10/6/09 03:40:
>
> Dear DNS Security Issues Working Group leaders,
>
> cc: DNS Security Issues Working Group members and ALAC Members
>
>
>
> At its meeting yesterday, the ALAC Executive Committee reviewed the
> At-Large Policy Advice Development calendar (please see:
> www.atlarge.icann.org/policycalendar
> ) to bring it up to date
> in advance of the Sydney meeting.
>
>
>
> The public comment period on the Draft Security, Stability and
> Resiliency Report is open until 19 June (see:
> http://www.icann.org/en/public-comment/#ssr). The ALAC Executive
> Committee is requesting that the DNS Security Issues Working Group
> develop the At-Large statement by 12 June. The ALAC will then have a
> five-day vote on this draft statement between 13-18 June.
>
>
>
> We were asked to contact you to ask if you and the other members of
> the DNS Security Issues Working Group will be able to develop this
> draft statement.
>
>
>
> Please note that Greg Rattray, ICANN’s Chief Internet Security
> Advisor, will be holding a briefing on the Draft Security, Stability
> and Resiliency Report on Wednesday, 10 June UTC. Details of this
> briefing, including participation information and the link to the
> Adobe Connect chat room are available at:
> https://st.icann.org/alac/index.cgi/index.cgi?ssr_briefing_call.
>
>
>
> We understand that this drafting timeline is an extremely tight
> deadline. Given that the briefing on the report is on 10 June, we are
> asking Greg, who is the staff person responsible for this issue,
> whether the formal comments from ALAC can be delivered up to a week
> later to allow for a more complete At-Large contribution on this issue.
>
>
>
> Please let us know if we can provide any additional information or
> assistance on this issue.
>
>
>
> Could you please confirm whether you will be able to produce a draft
> statement according to the above schedule? We will confirm with you
> shortly whether a week extension will be possible.
>
>
>
> Regards,
>
> Nick Ashton-Hart, Heidi Ullrich, Matthias Langenegger, Gisella
> Gruber-White, Marie-Helene Bouchoms
> ICANN At-Large Staff
> email: _staff@atlarge.icann.org_
>
>
>
>
>
>
>
[Dns-security-wg] [ALAC] Draft Security, Stability and Resilienc
Patrick we understand that fully...and based on the briefing call we had
earlier today /tonight I do not believe the statement needs to be
too onerous either ... We could put something supportive and endorsing what
was said in that call together for the draft IMO
CLO
2009/6/11 Patrick Vande Walle
> FWIW, please note that I am working on the IRT report statement (++loads
> of work in my day job) and I cannot commit to work on this one.
>
> I would appreciate if someone could handle the development of this
> statement
>
> Thanks,
>
> Patrick
>
> At Large Staff wrote, On 10/6/09 03:40:
> >
> > Dear DNS Security Issues Working Group leaders,
> >
> > cc: DNS Security Issues Working Group members and ALAC Members
> >
> >
> >
> > At its meeting yesterday, the ALAC Executive Committee reviewed the
> > At-Large Policy Advice Development calendar (please see:
> > www.atlarge.icann.org/policycalendar
> > ) to bring it up to date
> > in advance of the Sydney meeting.
> >
> >
> >
> > The public comment period on the Draft Security, Stability and
> > Resiliency Report is open until 19 June (see:
> > http://www.icann.org/en/public-comment/#ssr). The ALAC Executive
> > Committee is requesting that the DNS Security Issues Working Group
> > develop the At-Large statement by 12 June. The ALAC will then have a
> > five-day vote on this draft statement between 13-18 June.
> >
> >
> >
> > We were asked to contact you to ask if you and the other members of
> > the DNS Security Issues Working Group will be able to develop this
> > draft statement.
> >
> >
> >
> > Please note that Greg Rattray, ICANN’s Chief Internet Security
> > Advisor, will be holding a briefing on the Draft Security, Stability
> > and Resiliency Report on Wednesday, 10 June UTC. Details of this
> > briefing, including participation information and the link to the
> > Adobe Connect chat room are available at:
> > https://st.icann.org/alac/index.cgi/index.cgi?ssr_briefing_call.
> >
> >
> >
> > We understand that this drafting timeline is an extremely tight
> > deadline. Given that the briefing on the report is on 10 June, we are
> > asking Greg, who is the staff person responsible for this issue,
> > whether the formal comments from ALAC can be delivered up to a week
> > later to allow for a more complete At-Large contribution on this issue.
> >
> >
> >
> > Please let us know if we can provide any additional information or
> > assistance on this issue.
> >
> >
> >
> > Could you please confirm whether you will be able to produce a draft
> > statement according to the above schedule? We will confirm with you
> > shortly whether a week extension will be possible.
> >
> >
> >
> > Regards,
> >
> > Nick Ashton-Hart, Heidi Ullrich, Matthias Langenegger, Gisella
> > Gruber-White, Marie-Helene Bouchoms
> > ICANN At-Large Staff
> > email: _staff@atlarge.icann.org_
> >
> >
> >
> >
> >
> >
> >
>
> --
> Patrick Vande Walle
> Blog: http://patrick.vande-walle.eu
> Twitter: http://www.twitter.com/patrickvw
>
> _______________________________________________
> ALAC mailing list
> ALAC@atlarge-lists.icann.org
>
> http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann...
>
> At-Large Online: http://www.atlarge.icann.org
> ALAC Working Wiki: http://st.icann.org/alac
>
--
Cheryl Langdon-Orr
(CLO)
[Dns-security-wg] [ALAC] Draft Security, Stability and Resilienc
Patrick we understand that fully...and based on the briefing call we had
earlier today /tonight I do not believe the statement needs to be
too onerous either ... We could put something supportive and endorsing what
was said in that call together for the draft IMO
CLO
2009/6/11 Patrick Vande Walle
> FWIW, please note that I am working on the IRT report statement (++loads
> of work in my day job) and I cannot commit to work on this one.
>
> I would appreciate if someone could handle the development of this
> statement
>
> Thanks,
>
> Patrick
>
> At Large Staff wrote, On 10/6/09 03:40:
> >
> > Dear DNS Security Issues Working Group leaders,
> >
> > cc: DNS Security Issues Working Group members and ALAC Members
> >
> >
> >
> > At its meeting yesterday, the ALAC Executive Committee reviewed the
> > At-Large Policy Advice Development calendar (please see:
> > www.atlarge.icann.org/policycalendar
> > ) to bring it up to date
> > in advance of the Sydney meeting.
> >
> >
> >
> > The public comment period on the Draft Security, Stability and
> > Resiliency Report is open until 19 June (see:
> > http://www.icann.org/en/public-comment/#ssr). The ALAC Executive
> > Committee is requesting that the DNS Security Issues Working Group
> > develop the At-Large statement by 12 June. The ALAC will then have a
> > five-day vote on this draft statement between 13-18 June.
> >
> >
> >
> > We were asked to contact you to ask if you and the other members of
> > the DNS Security Issues Working Group will be able to develop this
> > draft statement.
> >
> >
> >
> > Please note that Greg Rattray, ICANN’s Chief Internet Security
> > Advisor, will be holding a briefing on the Draft Security, Stability
> > and Resiliency Report on Wednesday, 10 June UTC. Details of this
> > briefing, including participation information and the link to the
> > Adobe Connect chat room are available at:
> > https://st.icann.org/alac/index.cgi/index.cgi?ssr_briefing_call.
> >
> >
> >
> > We understand that this drafting timeline is an extremely tight
> > deadline. Given that the briefing on the report is on 10 June, we are
> > asking Greg, who is the staff person responsible for this issue,
> > whether the formal comments from ALAC can be delivered up to a week
> > later to allow for a more complete At-Large contribution on this issue.
> >
> >
> >
> > Please let us know if we can provide any additional information or
> > assistance on this issue.
> >
> >
> >
> > Could you please confirm whether you will be able to produce a draft
> > statement according to the above schedule? We will confirm with you
> > shortly whether a week extension will be possible.
> >
> >
> >
> > Regards,
> >
> > Nick Ashton-Hart, Heidi Ullrich, Matthias Langenegger, Gisella
> > Gruber-White, Marie-Helene Bouchoms
> > ICANN At-Large Staff
> > email: _staff@atlarge.icann.org_
> >
> >
> >
> >
> >
> >
> >
>
[ALAC] Draft Security, Stability and Resiliency Report - develop
Patrick we understand that fully...and based on the briefing call we had
earlier today /tonight I do not believe the statement needs to be
too onerous either ... We could put something supportive and endorsing what
was said in that call together for the draft IMO
CLO
2009/6/11 Patrick Vande Walle
> FWIW, please note that I am working on the IRT report statement (++loads
> of work in my day job) and I cannot commit to work on this one.
>
> I would appreciate if someone could handle the development of this
> statement
>
> Thanks,
>
> Patrick
>
> At Large Staff wrote, On 10/6/09 03:40:
> >
> > Dear DNS Security Issues Working Group leaders,
> >
> > cc: DNS Security Issues Working Group members and ALAC Members
> >
> >
> >
> > At its meeting yesterday, the ALAC Executive Committee reviewed the
> > At-Large Policy Advice Development calendar (please see:
> > www.atlarge.icann.org/policycalendar
> > ) to bring it up to date
> > in advance of the Sydney meeting.
> >
> >
> >
> > The public comment period on the Draft Security, Stability and
> > Resiliency Report is open until 19 June (see:
> > http://www.icann.org/en/public-comment/#ssr). The ALAC Executive
> > Committee is requesting that the DNS Security Issues Working Group
> > develop the At-Large statement by 12 June. The ALAC will then have a
> > five-day vote on this draft statement between 13-18 June.
> >
> >
> >
> > We were asked to contact you to ask if you and the other members of
> > the DNS Security Issues Working Group will be able to develop this
> > draft statement.
> >
> >
> >
> > Please note that Greg Rattray, ICANN’s Chief Internet Security
> > Advisor, will be holding a briefing on the Draft Security, Stability
> > and Resiliency Report on Wednesday, 10 June UTC. Details of this
> > briefing, including participation information and the link to the
> > Adobe Connect chat room are available at:
> > https://st.icann.org/alac/index.cgi/index.cgi?ssr_briefing_call.
> >
> >
> >
> > We understand that this drafting timeline is an extremely tight
> > deadline. Given that the briefing on the report is on 10 June, we are
> > asking Greg, who is the staff person responsible for this issue,
> > whether the formal comments from ALAC can be delivered up to a week
> > later to allow for a more complete At-Large contribution on this issue.
> >
> >
> >
> > Please let us know if we can provide any additional information or
> > assistance on this issue.
> >
> >
> >
> > Could you please confirm whether you will be able to produce a draft
> > statement according to the above schedule? We will confirm with you
> > shortly whether a week extension will be possible.
> >
> >
> >
> > Regards,
> >
> > Nick Ashton-Hart, Heidi Ullrich, Matthias Langenegger, Gisella
> > Gruber-White, Marie-Helene Bouchoms
> > ICANN At-Large Staff
> > email: _staff@atlarge.icann.org_
> >
> >
> >
> >
> >
> >
> >
>