I'm not up to speed on these issues, so I have nothing much to say in any specific way ... yet. :-)
I do think, however, that the IETF release is an awfully good piece of work: mature, thoughtful and appropriate in tone. and I want the authors to have my personal congratulations: good work. Well done. Cheers, -dlj. On 10 September 2013 17:55, Stephen Farrell <[email protected]>wrote: > > Good to see all the discussion. Keep it up! > > Couple of points: > > - I entirely agree that the BoF, other than scene setting (and the > usual ranting which we'll keep to a minimum:-) needs to be focused > on what the IETF can do. (Broader list discussion, e.g. about the > open-source community, seems fine and who knows might lead to some > concrete stuff we would like to talk about at the BoF.) > > - I think that "privacy" is too broad and not sufficiently focused > as a topic for a BoF session. Much as I'd like to see more progress > on corporate privacy-busting, I think this session will be better > kept more focused on recent pervasive monitoring attacks and what > we can do in the IETF to mitigate those attacks. > > - I agree with Dave that it'd be good to have a better idea of what > other protocols/areas of the IETF might be affected and/or part of > the answer. For example, the LISP WG list have an active discussion > now about encrypting encapsulated packet content. That wasn't one > that would have occurred to me but if the LISP folks are up for it > then it seems like a fine addition to their protocol. I'd be keen > to get more examples of IETF protocols where we could do stuff to > counter pervasive monitoring. The protocols where we improve things > btw don't need to have been part of current news stories - I don't > think LISP has featured for example:-) > > So keep the discussion flowing and we'll organise more as we go. > Ta, > S. > _______________________________________________ > perpass mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/perpass >
_______________________________________________ perpass mailing list [email protected] https://www.ietf.org/mailman/listinfo/perpass
