Re: [5gangip] Requirements on Github
Luigi Iannone <ggx@gigix.net> Thu, 14 June 2018 14:25 UTC
Return-Path: <ggx@gigix.net>
X-Original-To: 5gangip@ietfa.amsl.com
Delivered-To: 5gangip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EAA0130DC0 for <5gangip@ietfa.amsl.com>; Thu, 14 Jun 2018 07:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gigix-net.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zqb5tvcJCX3U for <5gangip@ietfa.amsl.com>; Thu, 14 Jun 2018 07:25:04 -0700 (PDT)
Received: from mail-wr0-x22a.google.com (mail-wr0-x22a.google.com [IPv6:2a00:1450:400c:c0c::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90DE712777C for <5gangip@ietf.org>; Thu, 14 Jun 2018 07:25:04 -0700 (PDT)
Received: by mail-wr0-x22a.google.com with SMTP id a12-v6so6679741wro.1 for <5gangip@ietf.org>; Thu, 14 Jun 2018 07:25:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2TSZLQNVv5ln19WQCWAhxheVG06JkMYHl1PGnRFoXv0=; b=zs2BtVxHOyo0zsksLdTSVtKd2jmZVB14hEAjcmh6TD8IJfICsstv7KPWTu1iaEyHgi CpxPC3y+T2tESLYqs+pQcIZgB+P7eeGuCo9fW6Q8mUl3TWBNxIG2iGuKWZE9TJBeWShX qzgH68FIXmkvVlFISxPUBa+kRvY6HV82EgRZXNPiKQONTR+PKVnoxXbcrxew9m+77uzm FPaQZ3eawstSCu+hLAEaA4q/sLt3Q0gq+kcAVVZH84vNxxT6sn9rPgTjzvXJEoxGTuW4 xDzYVApj+sR6i5/G2b0iy6Cg9ZUO3qUaVzpLSWdqqnN4GCROBT8O7I5umtVBJFlbmu1N VMug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2TSZLQNVv5ln19WQCWAhxheVG06JkMYHl1PGnRFoXv0=; b=W7/PblWK4X0sv6x6kwWXgQQrQ0fo1vFyoK8+iYBfP2ctD2MajZPkp5Y3hzu1bjM1xx TFfHG5vuLRY0KQ6el2yKa/9gaVj5mD0/qCQErMXJtb+vHYTlqQ9NNOnoXicwIMKRx8hc aiNf1fZ3Z0Nieb9o1VBUxRPL1U0NuheVUi3gOURTPJ0lvck7q7Ik9JR6v163jjWJ6TkS w+sLEehs2SOb+WZR/9Q2O4QnvO+6Ywa1jqbGNDsQ1HUXOYCLRMzjMIyZc/KUlSQApuwR dKzzwwamji9De3uF/0Ub+WmNCaHJhlL0ZHhW+yWfxyxA911vGWtE9t6tsRg8sMz6WgLu TOTA==
X-Gm-Message-State: APt69E0QYiHm2tLpsI62ETG/WyEdgrKIXN+8krvb/WvgQh95sbqcTzMu Yg3lU/RwL7dFucM+qD3E2W/QAQ==
X-Google-Smtp-Source: ADUXVKIVBuTaEB45+r8sz7KjVNgUMdFTpgGtgzw5pbNhS/XppR0R9YvuG8XkbzSxAgSaSKHkdFwKTA==
X-Received: by 2002:a5d:4306:: with SMTP id h6-v6mr2614281wrq.58.1528986303050; Thu, 14 Jun 2018 07:25:03 -0700 (PDT)
Received: from ?IPv6:2001:660:330f:a4:1051:20a9:1959:1d0f? ([2001:660:330f:a4:1051:20a9:1959:1d0f]) by smtp.gmail.com with ESMTPSA id g16-v6sm4339120wro.86.2018.06.14.07.25.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Jun 2018 07:25:01 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
From: Luigi Iannone <ggx@gigix.net>
In-Reply-To: <CAPDqMeo_9UiOkVM_8pYcgqu8MpfJR1A=7szLSF19-h7PH3-cTQ@mail.gmail.com>
Date: Thu, 14 Jun 2018 16:24:57 +0200
Cc: Behcet Sarikaya <sarikaya@ieee.org>, 5GANGIP <5gangip@ietf.org>, Dirk.von-Hugo@telekom.de
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B851BBE-EC4C-4997-8B81-572C9677CF38@gigix.net>
References: <CAC8QAcef8-G4z1Sy6Yg41r_whwW_-qxkYwwOmvbKbWujzFV_UQ@mail.gmail.com> <CE0F7437-2764-4378-B84C-AB885D914BD2@gigix.net> <CAPDqMeo_9UiOkVM_8pYcgqu8MpfJR1A=7szLSF19-h7PH3-cTQ@mail.gmail.com>
To: Tom Herbert <tom@quantonium.net>
X-Mailer: Apple Mail (2.3445.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/dZtuBaz7nDyRsDDpTjF0wCcSlFk>
Subject: Re: [5gangip] Requirements on Github
X-BeenThere: 5gangip@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "Discussion of implications of the upcoming 5th Generation \(fixed and\) Mobile communication systems on IP protocols." <5gangip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/5gangip>, <mailto:5gangip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/5gangip/>
List-Post: <mailto:5gangip@ietf.org>
List-Help: <mailto:5gangip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/5gangip>, <mailto:5gangip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Jun 2018 14:25:07 -0000
catching up with mail…. > On 12 Jun 2018, at 20:39, Tom Herbert <tom@quantonium.net> wrote: > > On Tue, Jun 12, 2018 at 1:02 AM, Luigi Iannone <ggx@gigix.net> wrote: >> Hi Behcet, >> >> I just had a look to the github, and I think that the "Addressing >> Requirements” need more work. >> >> It currently just state: >> >> IP addresses should not expose specific geo-location of users. >> >> Now, when you use a mapping system you mapping something into something >> else. >> Usually are addresses (ID) into addresses (LOC). >> So the question is: Shouldn’t we make a difference in the requirements of >> these two ? Or you think just a general requirement about Addresses is >> sufficient? >> > IMO, the requirement should refer to IP addressing in general. More > specifically, it should be something like You mean that it applies whatever the IP is used for, whether it is an ID or a LOC does not matter it still has to respect the same requirements? > > "IP addresses should not encode information that would allow > correlations by untrusted third parties which could expose user > identity, location, or other Personally Identifiable Information > (PII).” > Looks OK, but I would add the second paragraph with the example. so to better clarify what a untrusted third party is. > The "untrusted third party" is relevant to idloc protocols since this > allows the possbility of locators being used in a closed and secure > network that could containt sensitive privacy information. Exteral to > that environment (i.e. in the Internet) addresses must meet the > privacy requirements. > L. > Tom > > >> Thanks >> >> Ciao >> >> L. >> >> >> >> On 11 Jun 2018, at 16:57, Behcet Sarikaya <sarikaya2012@gmail.com> wrote: >> >> Hi all, >> >> Based on Tom's post, we created a requirements txt file and p[osted it at >> our Github depository >> >> atick_requirements.1.txt >> >> Regards, >> >> Behcet >> _______________________________________________ >> 5gangip mailing list >> 5gangip@ietf.org >> https://www.ietf.org/mailman/listinfo/5gangip >> >> >> >> _______________________________________________ >> 5gangip mailing list >> 5gangip@ietf.org >> https://www.ietf.org/mailman/listinfo/5gangip >>
- Re: [5gangip] Requirements on Github Alexandre Petrescu
- Re: [5gangip] Requirements on Github Lori Jakab
- Re: [5gangip] Requirements on Github Luigi Iannone
- Re: [5gangip] Requirements on Github Luigi Iannone
- Re: [5gangip] Requirements on Github Tom Herbert
- Re: [5gangip] Requirements on Github Tom Herbert
- Re: [5gangip] Requirements on Github Behcet Sarikaya
- Re: [5gangip] Requirements on Github Behcet Sarikaya
- Re: [5gangip] Requirements on Github Alexandre Petrescu
- Re: [5gangip] Requirements on Github Luigi Iannone
- Re: [5gangip] Requirements on Github Alexandre Petrescu
- Re: [5gangip] Requirements on Github FIGURELLE, TERRY F
- [5gangip] Requirements on Github Behcet Sarikaya