| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
I thought that Carlos meant that that would be the baseline for the threats that they would address mitigation of with the Privacy Considerations Recommended Practice. Not
that they would be putting text from the threat model in their draft. I.e. do we think it is a good description of the threats to privacy so that our work on privacy can be based on addressing those threats? Pat From: Mick Seaman [mailto:mickseaman@xxxxxxxxx]
I am not sure quite what you mean by 'adopt as a baseline'. If the suggestion is to take text, in part or as a whole, as text for an initial draft of the recommended practice then there are copyright/intellectual property considerations
to be taken into account and those would need to be disclosed on the PAR. In that case it would also not be clear why any formal work should occur in IEEE as opposed to all the documentation production being done in the IETF - there would still be a need for
active liaison. Can you clarify please. Mick
Dear Privacy EC SG members, We have provided inputs to the ‘Confidentiality in the Face of Pervasive Surveillance: A Threat Model and Problem Statement’ IAB draft, and these have been incorporated in the latest
version
https://tools.ietf.org/id/draft-iab-privsec-confidentiality-threat-07.txt. As discussed during the recent IETF-IEEE 802 Coordination Virtual Meeting, and assuming the project (PAR/CSD) is approved by the IEEE 802 EC at the July plenary meeting, it would
be beneficial for the project to use this IAB draft as a baseline to work upon. Therefore, I would like to discuss the possibility to endorse/adopt it as baseline for the threat model discussions once the project gets approved. I will allocate agenda time to discuss about this topic during our
upcoming conference call on July 1, at 10:00 EDT. Until then, please feel free to share your thoughts/comments on this email list. Best regards, Juan Carlos
(IEEE 802 Privacy EC SG Chair) |