Luigi's contribution #4
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Added several references - Added subsection 3.3 on law issues (to be vetted) - Bootstrapped section 3.1 - Added text section 3.2 - Proposed content for 3.4 - Added text and revised section 4.1
|
@ggx Thanks for this PR! It seems Matthew did a PR just before you so we've merged his and there are now a few conflicts. Would you be able to take a look and fix those up? |
| @@ -1,7 +1,7 @@ | |||
| --- | |||
| title: "IP Address Privacy Considerations" | |||
| abbrev: "IP Address Privacy Considerations" | |||
| docname: draft-ip-address-privacy-considerations | |||
| docname: draft-ip-address-privacy-considerations-latest | |||
There was a problem hiding this comment.
I think we should leave the doc name as draft-ip-address-privacy-considerations unless you had a specific reason for changing it?
There was a problem hiding this comment.
I think the "-latest" suffix is necessary for MT's tooling to produce the correct document version when compiling.
|
|
||
| Commerical VPNs offer a layer of indirection between the user and the destination, however if the VPN endpoint's IP address is static then this simply substitutes one address for another. In addition, commerial VPNs replace tracking across sites with a single company that may track their users' activities. | ||
| ## Mitigations for IP address tracking |
There was a problem hiding this comment.
Most conflicts with Matthew's update are in this section
There was a problem hiding this comment.
Hi,
I went over the conflicts and solved them adjusting the text as needed.
Ciao
L.
|
Hi,
I’ll have a look during the weekend
Ciao
L.
… On 23 Jul 2021, at 18:52, Sara Dickinson ***@***.***> wrote:
@saradickinson commented on this pull request.
In draft-ip-address-privacy-considerations.md <#4 (comment)>:
>
-Commerical VPNs offer a layer of indirection between the user and the destination, however if the VPN endpoint's IP address is static then this simply substitutes one address for another. In addition, commerial VPNs replace tracking across sites with a single company that may track their users' activities.
+## Mitigations for IP address tracking
Most conflicts with Matthew's update are in this section
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#4 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5HQCUYSTE7ERKOQAIDRHTTZGM4HANCNFSM5AXSZNRA>.
|
|
Hi,
I solved all the conflicts adjusting the text as needed.
the repository is now up to date and clean.
Ciao
L.
… On 24 Jul 2021, at 08:43, Luigi Iannone ***@***.***> wrote:
Hi,
I’ll have a look during the weekend
Ciao
L.
> On 23 Jul 2021, at 18:52, Sara Dickinson ***@***.*** ***@***.***>> wrote:
>
>
> @saradickinson commented on this pull request.
>
> In draft-ip-address-privacy-considerations.md <#4 (comment)>:
>
> >
> -Commerical VPNs offer a layer of indirection between the user and the destination, however if the VPN endpoint's IP address is static then this simply substitutes one address for another. In addition, commerial VPNs replace tracking across sites with a single company that may track their users' activities.
> +## Mitigations for IP address tracking
> Most conflicts with Matthew's update are in this section
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub <#4 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5HQCUYSTE7ERKOQAIDRHTTZGM4HANCNFSM5AXSZNRA>.
>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hereafter a list of the main changes. IMHO with these changes the draft is in good shape to ask PEARG community if the document is going in the right direction. Hopefully it is and we can later add more text to the different sections.