Re: [IPFIX] Review of draft-irtf-nmrg-location-ipfix-07.txt

--===============2068896401861859018==
Content-Type: multipart/signed;
 boundary="Apple-Mail=_5F31D5C6-F96D-4491-93BB-22E15365282E";
 protocol="application/pgp-signature"; micalg=pgp-sha512


--Apple-Mail=_5F31D5C6-F96D-4491-93BB-22E15365282E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,
Thank you for the feedback. please see comments inline, I hope that they =
help make things clear.
> On 23 Nov 2016, at 12:02, Stewart Bryant <[email protected]> =
wrote:
>=20
>=20
> Collecting this data is not particularly difficult, but protecting the =
privacy is much harder and will, I imagine be subject to significant =
scrutiny as the draft progresses.

The core subject of the draft is far from providing solutions of privacy =
issues when collecting sensitive data. We have clearly mentioned the =
privacy issue in our draft in section =E2=80=99Security and Privacy =
Considerations=E2=80=99. In the section we have referenced existing RFCs =
that have addressed this issue for location information : [RFC3694], =
[RFC3693] and also Flow record anonymization [RFC6235].

>=20
> It seems to me that there are security and privacy issues concerning =
both the traffic and the collector itself. The privacy of the user is a =
widely understood concept and will I am sure be thoroughly examined in =
review. In the case of the collector I am not convinced that it is wise =
to reveal the precise location of the network infrastructure since this =
could result in it being subject to physical attack.

In my opinion, we can also imagine another scenario where location =
information will help operators to identify that their equipments have =
not be moved or stolen, so associating IP flows to the location of the =
device is helpful in this case.

>=20
> An approach that you do not seem to explore is encrypting the location =
record so that this can only be understood by those that are authorised =
to see it.

We have mentioned in the section =E2=80=99Security and privacy =
Consideration=E2=80=99 that location information SHOULD be signed and =
encrypted as specified in [RFC7011].

> Indeed there is a case for something analogous to the selective =
availability system in GPS whereby the location is provided with =
different degrees of precision depending on the authority of the user.
>=20
In section =E2=80=98Enabling Location Extensions=E2=80=99, we have =
mentioned that the metering process selects a location method when many =
are available with different degrees of precision. Yes, we can make it =
more clear by also mentioning that the selection depends on the =
authority of the user.
Best regards,


> - Stewart
>=20
>=20
> On 23/11/2016 02:33, Zhoutianran wrote:
>> Hi,
>>=20
>> Though IPFIX is concluded, could the IPFIX experts in this mailing =
list please help to provide comments for this I-D?
>> https://datatracker.ietf.org/doc/draft-irtf-nmrg-location-ipfix
>>=20
>> It seems this work has a long history. Your help will push this work =
a step forward.
>>=20
>>=20
>> Thanks,
>> Tianran
>>=20
>> _______________________________________________
>> IPFIX mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/ipfix
>=20
> _______________________________________________
> IPFIX mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/ipfix


--Apple-Mail=_5F31D5C6-F96D-4491-93BB-22E15365282E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJYNvyKAAoJEBX1Mi7AAzI6UY4QAKYGixkLTjZQYN4TjjD0KvhH
rGjZRuGvedoFkD3Jw46zNCMX1RTLy+QLZe9y1QepCN0/pUHE3zSyhgjZwFKEYBKb
NVmb7RJAVz1MzH97oqJvi2aboZ74KWa3gub8SfWhd/NRQQVWNtAGP0WU3IscCoSR
bMCec5v4RqpjMn7j4osOV8Hinh7zNCaxotHtigcXbEto2O22RgikGwYof0jcEgSk
BlGizewneTkSoKeL8ctMcKX73txDACQh0imevy7eLj94t8owL+S0cEQfXoT3s/cT
/uPmyG8/jsNO5K7qRCMHie75uhkY8SMnRc3VKZ7WwVpEg9qeA+D52Uyq7FZ/4xYa
QSUGZZPXy8VX9u2KmklnBBk0ii9zRCiBcZd3VPB8Ea8nSQmx57IX24svAi59U8LC
BCIdeHFIAkFdPTh2sXfiDpZygN0L9UKP92+0OLr/uHxq4EacsyYKglh1g1MIIG/Y
43khkojNbNhebODcVfsZw2Kk8+/Wy1vgxgt5uMfGk3PIMDARWbjcLEcUzbn+zl59
BGnx48CoXWni6bYsp44NenM+vc0sWJWcpra+tkQcA76aEdT6rt1Jsqzy8pUEusK/
/Q6+eIRzO4qAa4f51KAo/0KVqZEOcO+Uy2iA4Etl0AlR28Ne1I7u36AuYRsWDHJV
bKyXf3/PzYBGY8ae8AIi
=r7uS
-----END PGP SIGNATURE-----

--Apple-Mail=_5F31D5C6-F96D-4491-93BB-22E15365282E--


--===============2068896401861859018==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
IPFIX mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ipfix

--===============2068896401861859018==--