Ian, Thanks for sharing the URL. While not explicit, “all metadata” would include both source and destination A+P. Is that the right interpretation?
If an ISP were to use “binding” mode on the BR, then without using net flow/IPFIX, How could the compliance be achieved ? Cheers, Rajiv Asati Distinguished Engineer, Cisco Services On May 4, 2018, at 4:16 AM, "ianfar...@gmx.com<mailto:ianfar...@gmx.com>" <ianfar...@gmx.com<mailto:ianfar...@gmx.com>> wrote: Hi, As another data point on this topic, the storing of A+P data is also mandated in Hungary. From the Hungary paragraph of the 2016 EU report into implementation of the Data Retention Directive (http://fra.europa.eu/en/theme/information-society-privacy-and-data-protection/data-retention): "The new law obliges electronic and IT service providers that allow encrypted communication through their services to store all metadata related to such communications for one year. It thus widens the scope of data retention." Translated: A+P retention. Cheers, Ian PS: Few may be aware of Govt. of India’s mandate* to log both source and destination IP+port pair. Click on “Parameter to be stored in SYS Log of Network Address Translation (NAT) for Internet Access” on this page - https://www.corestack.io/blog/the-log-mandate-enabling-indian-isps-to-adhere-to-dot-compliance-rules/ PS: https://tools.ietf.org/html/rfc6302 https://tools.ietf.org/html/rfc7422 Session and service continuity _______________________________________________ Softwires mailing list softwi...@ietf.org<mailto:softwi...@ietf.org> https://www.ietf.org/mailman/listinfo/softwires
_______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
