![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Hi Dave and Hannes,Thank you for triggering this useful discussion. And thank you to Brian, Patrik and Lucy for their comments as well. A number of good points have been raised both on the topic and others on the ISOC-IETF intersection. These are items to be taken up with the ISOC Board, IAB and the IETF community.
As has been pointed out, ISOC has brought in additional technical expertise and this, amongst other things, has allowed us to broaden our activities as it relates to the Internet's development. Lucy Lynch is championing our Trust & Identity initiative and is the appropriate contact for that discussion - lynch at isoc.org.
With respect to the ISOC-IETF intersection, Leslie Daigle (ISOC's Chief Internet Technical Officer), Lucy, and I have been having similar discussions - not particularly formally, but the interaction with the IETF and our responsibility to the IETF are always top of our minds - and of course critically important. Others have been involved as well, some from the IAB and others such as Russ in his IETF Chair role (although again not particularly formally) and we will certainly evaluate appropriate next steps. We are interested in your thoughts so please reach out to Leslie or me - daigle at isoc.org or st.amour at isoc.org .
Thanks again, LynnPS. Re: your side note below on the makeup of the ISOC Board, we'll update the list to show the community or mechanism that appoints/ elects Trustees. In the meantime, the IETF appoints 3 Trustees (out of 13, 12 voting and me non-voting). The current IETF appointees to the ISOC Board are: Patrik Fältström, Ted Hardie and Bert Wijnen.
On Mar 1, 2009, at 1:17 PM, Dave CROCKER wrote:
Hannes Tschofenig wrote:Someone could, for example, come upwith the question why ISOC did not join the MIT Kerberos Consortium (see http://www.kerberos.org/), as Kerberos is a technology developed within the IETF, or to support technologies like OpenID, OAuth, etc. that are closer to the Internet deployment. I am sure your team had a lot of conversations with the IAB on whatdirection would be better for the InternetFolks,What is particularly interesting to me, about this line of comment, is not whether the relevant IETF-based technologies are superior or whether an ISOC alliance with an industry Alliance was the right thing to do. There can -- and probably should -- be focussed debate about such questions. But only within a larger context that I'd like to raise:Should there be more or different ISOC/IETF dialogue, when ISOC is pursuing a strategic topic that is relevant to the IETF?The IETF/ISOC relationship has changed dramatically, in recent years, primarily in terms of ISOC involvement in IETF management and funding. What I do not recall seeing is whether there should be changes in the involvement of the IETF in ISOC activities.[1]An easy example is exactly the sort of involvement being implied by the current thread: When ISOC is choosing to take a strategic action, should it seek public discussion within the IETF?Public discussion is messy and IETF-wide consensus is virtually impossible to obtain for any interesting topic. So I'm not at all suggesting that ISOC depend upon gaining that from the IETF. Still, public discussion can surface useful information and opinion.Let me stress: I don't intend this as criticism. As things change, we gain insight. The exchange surfaced an issue that struck me as interesting and potentially useful, and worth pursuing among the ISOC and IETF communities.d/ [1] Side note: The list of ISOC Board of Trustees at: <http://www.isoc.org/isoc/general/trustees/board.php>does not indicate the constituency or selection mechanism that chose particular Trustees; it would be helpful to see that included in the list, to understand whether they are ex officio, elected by from a region, or thelike. -- Dave Crocker Brandenburg InternetWorking bbiw.net _______________________________________________ Ietf mailing list Ietf at ietf.org https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.