Draft agenda can be found at: https://docs.google.com/document/d/160soUX0_aMVpbeqoAIlkUE3pnFrR_4VfbX5KetDK... PDF attached. Will post PDF of the documents under discussion a little later as they are going though an edit pass today. avri --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Dear all My apologies that I can't join this call (2am here in New Zealand). I think with Document A, last call we agreed to do a thorough edit. I haven't had the chance yet to do this. Please add your comments and thoughts on the current working draft, and I'll do the editing job in the next week or so, and we can finalise that document on our call on 16 Feb, in time for the plenary CCWG to discuss at Copenhagen. cheers Jordan On 2 February 2017 at 10:13, avri doria <avri@acm.org> wrote:
Draft agenda can be found at:
https://docs.google.com/document/d/160soUX0_aMVpbeqoAIlkUE3pnFrR_ 4VfbX5KetDKHuA/edit?usp=sharing
PDF attached.
Will post PDF of the documents under discussion a little later as they are going though an edit pass today.
avri
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
_______________________________________________ Ws2-staff_acct mailing list Ws2-staff_acct@icann.org https://mm.icann.org/mailman/listinfo/ws2-staff_acct
-- Jordan Carter Chief Executive *InternetNZ * +64-4-495-2118 (office) | +64-21-442-649 (mob) | Skype: jordancarter jordan@InternetNZ.net.nz | www.InternetNZ.nz *A better world through a better Internet*
Hi, I have attached pdf files for each of the documents. avri On 01-Feb-17 16:13, avri doria wrote:
Draft agenda can be found at:
https://docs.google.com/document/d/160soUX0_aMVpbeqoAIlkUE3pnFrR_4VfbX5KetDK...
PDF attached.
Will post PDF of the documents under discussion a little later as they are going though an edit pass today.
avri
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
_______________________________________________ Ws2-staff_acct mailing list Ws2-staff_acct@icann.org https://mm.icann.org/mailman/listinfo/ws2-staff_acct
--- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Avri, and all, During the last call, some of you were concerned about how to better express the thoughts in document A in the area pf comment[20] to comment[22]. Avri asked me to look at it, and here is my personal view. 1. I'm concentrating on what you appear to want to say about what the Board does not do, not on mediating the IGO/INGO issue, although it forms a backdrop that informs the discussion. 2. I have sympathy with comment[22], since the Board's role was exhaustively studied and prescribed in WS1. 3. As noted near the end of the call, texts like this are littered with the word 'ICANN' when the object described can be interpreted as ICANN org, the ICANN community, ICANN org and the Board, the Board speaking for ICANN org, the Board speaking for ICANN org and the community, or any combination of the above., In addition, the word 'community' means different things to different people, providing more scope for different interpretations. It's a wonder that we manage to be able to communicate as well as we do. 4. Given all this, I would write the first bullet in the following way: • To determine policy when community processes have not exhausted the possibility of reaching consensus. This does beg the question of what happens if everyone were to agree that community processes have been exhausted with regard to a particular issue. My sense is that then you have to leave it to the discretion of the Board. There are issues that need to be solved, urgently, where any resolution is better than no resolution. There are also issues that, if unresolved, do not imply major disaster and can wait until the community is ready to try again to resolve them. My guess is that issues in the former class are a relatively small minority, and that for most issues, the Board should punt the lack of resolution back to the community as their problem. But do you really want to include considerations like this in your report? I'd just go with the bullet above and concentrate on your primary task. 5. I am willing to discuss further if anyone wishes to do so. George
hi George, all George: thanks for this. I like it. I've tracked it as a change in v 1.5 for finalising on the call on Tuesday. Many thanks Jordan On 26 February 2017 at 07:50, George Sadowsky <george.sadowsky@gmail.com> wrote:
Avri, and all,
During the last call, some of you were concerned about how to better express the thoughts in document A in the area pf comment[20] to comment[22]. Avri asked me to look at it, and here is my personal view.
1. I'm concentrating on what you appear to want to say about what the Board does not do, not on mediating the IGO/INGO issue, although it forms a backdrop that informs the discussion.
2. I have sympathy with comment[22], since the Board's role was exhaustively studied and prescribed in WS1.
3. As noted near the end of the call, texts like this are littered with the word 'ICANN' when the object described can be interpreted as ICANN org, the ICANN community, ICANN org and the Board, the Board speaking for ICANN org, the Board speaking for ICANN org and the community, or any combination of the above., In addition, the word 'community' means different things to different people, providing more scope for different interpretations. It's a wonder that we manage to be able to communicate as well as we do.
4. Given all this, I would write the first bullet in the following way:
• To determine policy when community processes have not exhausted the possibility of reaching consensus.
This does beg the question of what happens if everyone were to agree that community processes have been exhausted with regard to a particular issue. My sense is that then you have to leave it to the discretion of the Board. There are issues that need to be solved, urgently, where any resolution is better than no resolution. There are also issues that, if unresolved, do not imply major disaster and can wait until the community is ready to try again to resolve them. My guess is that issues in the former class are a relatively small minority, and that for most issues, the Board should punt the lack of resolution back to the community as their problem.
But do you really want to include considerations like this in your report? I'd just go with the bullet above and concentrate on your primary task.
5. I am willing to discuss further if anyone wishes to do so.
George
_______________________________________________ Ws2-staff_acct mailing list Ws2-staff_acct@icann.org https://mm.icann.org/mailman/listinfo/ws2-staff_acct
-- Jordan Carter Chief Executive *InternetNZ * +64-4-495-2118 (office) | +64-21-442-649 (mob) | Skype: jordancarter jordan@InternetNZ.net.nz | www.InternetNZ.nz *A better world through a better Internet*
participants (4)
-
avri doria -
avri doria -
George Sadowsky -
Jordan Carter