Re: Bruce Schneier's Proposal to dedicate November meeting to saving the Internet from the NSA

On 09/09/13 09:29, Eliot Lear wrote: We're talking. Eliot On 9/9/13 10:20 AM, Ross Finlayson wrote: So, has Bruce Schneier actually been invited to speak at the Technical Plenary (or elsewhere) during the Vancouver IETF? I recall him giving an informative talk at least one previous

Re: Bruce Schneier's Proposal to dedicate November meeting to savingthe Internet from the NSA

On 06/09/13 14:45, Scott Brim wrote: I wouldn't focus on government surveillance per se. The IETF should consider that breaking privacy is much easier than it used to be, particularly given consolidation of services at all layers, and take that into account in our engineering best practices.

Re: Bruce Schneier's Proposal to dedicate November meeting to saving the Internet from the NSA

On Sun, Sep 15, 2013 at 9:10 AM, Tobias Gondrom tobias.gond...@gondrom.orgwrote: On 09/09/13 09:29, Eliot Lear wrote: We're talking. Eliot On 9/9/13 10:20 AM, Ross Finlayson wrote: So, has Bruce Schneier actually been invited to speak at the Technical Plenary (or elsewhere) during

Re: Messages to SPFBIS mailing list (was: [spfbis] Benoit Claise's No Objection on draft-ietf-spfbis-4408bis-19: (with COMMENT))

On Sep 14, 2013, at 1:57 PM, S Moonesamy sm+i...@elandsys.com wrote: Hi Doug, At 20:56 13-09-2013, Douglas Otis wrote: If I have said something offensive, allow me once again to assure you this was never my intent. There isn't anything in your message which was offensive. I'll try to

Re: Messages to SPFBIS mailing list (was: [spfbis] Benoit Claise's No Objection on draft-ietf-spfbis-4408bis-19: (with COMMENT))

Hi Doug, At 15:58 15-09-2013, Douglas Otis wrote: This view is fully reasonable using the paradigm SPFbis is just another protocol using DNS. If so, a reference to RFC4033 would be logical and my response would seem off-topic. To clarify, the strong response was aimed specifically at the

Re: Last Call: draft-ietf-insipid-session-id-reqts-08.txt (Requirements for an End-to-End Session Identification in IP-Based Multimedia Communication Networks) to Informational RFC

I don't have that spec in front of me, but if it is used directly, that would reveal personally identifiable information. I would hope it is used as input into a hash out something. The solution spec we're developing would certainly not use such a value directly or allow it to be derived.

STD 77, RFC 7011 on Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information

A new Request for Comments is now available in online RFC libraries. STD 77 RFC 7011 Title: Specification of the IP Flow Information Export (IPFIX) Protocol for the Exchange of Flow Information Author: B.

RFC 7012 on Information Model for IP Flow Information Export (IPFIX)

A new Request for Comments is now available in online RFC libraries. RFC 7012 Title: Information Model for IP Flow Information Export (IPFIX) Author: B. Claise, Ed., B. Trammell, Ed. Status: Standards

RFC 7014 on Flow Selection Techniques

A new Request for Comments is now available in online RFC libraries. RFC 7014 Title: Flow Selection Techniques Author: S. D'Antonio, T. Zseby, C. Henke, L. Peluso Status: Standards Track Stream: IETF

BCP 184, RFC 7013 on Guidelines for Authors and Reviewers of IP Flow Information Export (IPFIX) Information Elements

A new Request for Comments is now available in online RFC libraries. BCP 184 RFC 7013 Title: Guidelines for Authors and Reviewers of IP Flow Information Export (IPFIX) Information Elements Author: B.

RFC 7015 on Flow Aggregation for the IP Flow Information Export (IPFIX) Protocol

A new Request for Comments is now available in online RFC libraries. RFC 7015 Title: Flow Aggregation for the IP Flow Information Export (IPFIX) Protocol Author: B. Trammell, A. Wagner, B.