Re: [bc-gnso] Last Call: BC discussion draft for SSR comments, to be filed 6-April
- To: "icann" <icann@xxxxxxxxxxxxxx>, "bc-GNSO" <bc-GNSO@xxxxxxxxx>
- Subject: Re: [bc-gnso] Last Call: BC discussion draft for SSR comments, to be filed 6-April
- From: martinsutton@xxxxxxxx
- Date: Fri, 1 Apr 2011 23:17:38 +0100
I like your change to emphasis and support this amendment following Mikey's
I also applaud those that have dedicated effort to draft this (especially
Manager, Group Fraud Risk and Intelligence
Ph: ++44 (0)20 7991 8074
Mob: ++44 (0)777 4556680
Sent from my BlackBerry
HSBC Holdings plc
Registered Office: 8 Canada Square, London E14 5HQ, United Kingdom
Registered in England number 617987
----- Original Message -----
From: "Mike Rodenbaugh" [icann@xxxxxxxxxxxxxx]
Sent: 01/04/2011 14:40 MST
Subject: RE: [bc-gnso] Last Call: BC discussion draft for SSR comments, to be
Thanks Adam, Mikey, Steve and others for drafting this excellent piece. I
have but one issue with it. I suggest changing this sentence, which follows
the numbering of the 3 issues:
The BC recognizes the narrow scope of ICANN's technical coordination role,
but this should not be relied upon to limit participation in coordinated
efforts to combat malicious DNS activity.
I do not think the BC should be recognizing any "narrow scope" of ICANN's
role, at least not without defining what we mean. Instead, I propose this:
ICANN's Bylaws require it "to ensure the stable and secure operation" of the
DNS. Therefore, ICANN must view participation in coordinated, industry
efforts to combat malicious DNS as absolutely essential to that mission.
tel/fax: +1 (415) 738-8087
From: owner-bc-gnso@xxxxxxxxx [mailto:owner-bc-gnso@xxxxxxxxx] On Behalf Of
Sent: Friday, April 01, 2011 1:06 PM
Subject: [bc-gnso] Last Call: BC discussion draft for SSR comments, to be
As discussed on yesterday's BC member call, this is "last call" on SSR.
Please review and comment on our discussion draft in response to SSR
(Security, Stability and Resiliency) review team issues.
SSR Review Team (AoC) Set of Issues (Due 6-Apr)
Adam Palmer's draft circulated 24-Mar.
Mikey O'Connor circulated edits 25-Mar
Awaiting reaction from members and Adam on Mikey's markup. (attached)
On 3/24/11 11:22 PM, "Steve DelBianco" <sdelbianco@xxxxxxxxxxxxx> wrote:
ICANN's Affirmation of Commitments required a community review of DNS
Security Stability & Resiliency (SSR). The SSR Review Team is now
gathering public input on the set of issues it proposes for this review.
Attached is a discussion draft for BC submission, prepared by Adam Palmer.
Several of the 11 issues in this draft are empty - some because answers are
given elsewhere in the draft; rest are blank because Adam wanted to leave
room for other BC members to add their security expertise!
The Review Team is seeking responses by 6-April, so today (24-March) begins
our 14-day review period for this discussion draft.
Please review and post your suggestions/edits as soon as possible. If
there are no disagreements noted by 1-April, these comments will be adopted
without a voting period, and posted to ICANN on 6-April.
As always, BC members are also encouraged to submit their own responses and
to share those with the BC list.
For topic background, see
Thanks again to Adam for volunteering to do this discussion draft.
And thanks to Jeff Brueggeman for serving on the SSR Review Team.
Vice chair for policy coordination
SAVE PAPER - THINK BEFORE YOU PRINT!
This E-mail is confidential.
It may also be legally privileged. If you are not the addressee you
may not copy, forward, disclose or use any part of it. If you have
received this message in error, please delete it and all copies
from your system and notify the sender immediately by return
Internet communications cannot be guaranteed to be timely secure,
error or virus-free. The sender does not accept liability for any
errors or omissions.