RE: [bc-gnso] Last Call: BC discussion draft for SSR comments, to be filed 6-April

["Baskin, James F (Jim)" <james.f.baskin@xxxxxxxxxxx>]

Yes, thanks to all.

Mike R's new language needs one more word in the second sentence:
"...efforts to combat malicious DNS activity..."

I also have a small number of typo/grammar items elsewhere:

Item 1 on page 3 - the comment text needs to start on a new line.

Item 2 on page 3, last para - suggest changing "eliminating a compliance 
environment" to "reversing a compliance environment" [or some other word]

Item 10, first para - correct SRR to SSR

General:  Use of both "Security, Stability, and Resilience" and "Security, 
Stability, and Resiliency."  The title page and at least one other place in the 
doc use "resiliency," but most occurrences use "resilience."  Does it need to 
be consistent?

Finally, is the formal title of the review team "The Security, Stability and 
Resiliency of the DNS Review Team"?  If it is, so be it.  If it isn't, then 
could the title be changed to "Review Team on The Security, Stability and 
Resiliency of the DNS"?  As it is, it sounds like a review of the "security, 
stability, and resiliency" of the "DNS review team." :)

Jim Baskin
Verizon

________________________________
From: owner-bc-gnso@xxxxxxxxx [mailto:owner-bc-gnso@xxxxxxxxx] On Behalf Of 
Mike Rodenbaugh
Sent: Friday, April 01, 2011 5:41 PM
To: bc-GNSO@xxxxxxxxx
Subject: RE: [bc-gnso] Last Call: BC discussion draft for SSR comments, to be 
filed 6-April

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.

Thanks,
Mike

Mike Rodenbaugh
RODENBAUGH LAW
tel/fax:  +1 (415) 738-8087
http://rodenbaugh.com<http://rodenbaugh.com/>

From: owner-bc-gnso@xxxxxxxxx [mailto:owner-bc-gnso@xxxxxxxxx] On Behalf Of 
Steve DelBianco
Sent: Friday, April 01, 2011 1:06 PM
To: bc-GNSO@xxxxxxxxx
Subject: [bc-gnso] Last Call: BC discussion draft for SSR comments, to be filed 
6-April

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<mailto: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  http://www.icann.org/en/public-comment/#ssr-rt-issues

Thanks again to Adam for volunteering to do this discussion draft.

And thanks to Jeff Brueggeman for serving on the SSR Review Team.


Steve DelBianco
Vice chair for policy coordination