IETF Logo Mail Archive

Re: [5gangip] Requirements on Github

Behcet Sarikaya <sarikaya2012@gmail.com> Tue, 12 June 2018 14:09 UTC

Return-Path: <sarikaya2012@gmail.com>
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 A4758127148 for <5gangip@ietfa.amsl.com>; Tue, 12 Jun 2018 07:09:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 S8Yw-bMpQfYJ for <5gangip@ietfa.amsl.com>; Tue, 12 Jun 2018 07:09:33 -0700 (PDT)
Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::242]) (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 6B9DF130F29 for <5gangip@ietf.org>; Tue, 12 Jun 2018 07:09:25 -0700 (PDT)
Received: by mail-wr0-x242.google.com with SMTP id e18-v6so16001600wrs.5 for <5gangip@ietf.org>; Tue, 12 Jun 2018 07:09:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=hqmbikwaBjoRLwg42sOhvEnQU3GJvTnD42U1rqn9NiI=; b=r+5nA1HN5hB96RzSoASNWKgtSjaD9ffZ731cuT1MAmJEUrC73O3r93sHYOLXrhnWjp ghyKUcnL+jWDHQDERy1xZeABFvv3hksO83yMu6pgAPfntIIAP3KDrDhHXr9VNlIgThNv 0ndFtt+JRjNF5d46YPRHbaKugQ0xVoVMaC5Ml7vOk70M3CWaGcgiwtfwwmCdgfxL+su+ z8bUMOu0TZRBlNyfkTaorcvO/RuygLfCfaIK38jv2oGc7QSRSK35Rn4RaTIhBRgRWR3q GxDjOCwOchKsk44W3/AWet7UJD1Z3Fhr1Onfu21SQOi/qNBv10ojxeC2jcuF02zR04xh qXPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=hqmbikwaBjoRLwg42sOhvEnQU3GJvTnD42U1rqn9NiI=; b=e4xpaipvNLvP8Zxq86gbMj6aDtSJiO82yJuhseJP+GI4b6gXsawKYTbdVFFOfbY9VV tlK/tAP88xEeQHpr9Ex8x13LybRkKex2BVLPF1CeRS/rFqbwvm1QUtL+W2mFpgWFpsCO vRenAQD+YjQ+jVEp5+X4VYlYWCchXmStRiP66ed0Pk60awhoK2jZNKzf6RgEiaNHVC04 FGYcQ7w6NJupaXzHrjnLvZ1g+c8aZMrG5ma2LEXIbJGwtI8T8HF0s3VY7WQweQFkpTGf qIPIXs7hQW39go9AysKr40HNvlrNCnlVOKOB4PiqIFgueUSOgEQWZFaCuSi34r9ZnChy 8K4A==
X-Gm-Message-State: APt69E3/Wb+1/RMrLUsiSL0zgjIjssfBMVb2viUWv8bAzbqTWdTKR0cU lWdElo1BMwTgnZYU9hOrzJJ+jU+7OuNFec/CH2w=
X-Google-Smtp-Source: ADUXVKJDi335f6bm1RzCBeEyOLyoYilFkvaThT+PgJZOhghLcOq6z/xE7zD3sTGKFnJaPZT4CltTPbyMfFjWn32q1ww=
X-Received: by 2002:adf:ca03:: with SMTP id o3-v6mr461727wrh.148.1528812563051; Tue, 12 Jun 2018 07:09:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:adf:fc84:0:0:0:0:0 with HTTP; Tue, 12 Jun 2018 07:09:22 -0700 (PDT)
Reply-To: sarikaya@ieee.org
In-Reply-To: <CE0F7437-2764-4378-B84C-AB885D914BD2@gigix.net>
References: <CAC8QAcef8-G4z1Sy6Yg41r_whwW_-qxkYwwOmvbKbWujzFV_UQ@mail.gmail.com> <CE0F7437-2764-4378-B84C-AB885D914BD2@gigix.net>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Tue, 12 Jun 2018 09:09:22 -0500
Message-ID: <CAC8QAcddDLi3PVLDmK1GZAhbE7AbrgM3jxLBranrB-xzC=ArcQ@mail.gmail.com>
To: Luigi Iannone <ggx@gigix.net>
Cc: 5GANGIP <5gangip@ietf.org>, Dirk.von-Hugo@telekom.de
Content-Type: multipart/alternative; boundary="000000000000bfb70f056e726913"
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/0NU0z6qZA93rdUmUv9PMsXF-rcY>
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: Tue, 12 Jun 2018 14:09:35 -0000

Hi Luigi,

On Tue, Jun 12, 2018 at 3: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?
>
>
We had the identifier in mind and identifiers could be domain specific not
representing an IP address.
So the idea is we are advocating the use of Id-Loc systems rather than the
current IP address as locator based system.

However, I know that in LISP identifier is also an IP address.
Can you propose some wording to cover LISP case as well?



> 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
> <https://github.com/bsarikaya/atic/blob/master/atick_requirements.1.txt>
>
> Regards,
>
> Behcet
> _______________________________________________
> 5gangip mailing list
> 5gangip@ietf.org
> https://www.ietf.org/mailman/listinfo/5gangip
>
>
>

v2.23.0 | Report a Bug | By Email