[5gangip] Feedback on draft-xyzy-atick-gaps-00

Tom Herbert <tom@herbertland.com> Mon, 04 June 2018 20:24 UTC

Return-Path: <tom@herbertland.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 ACFBC130DE1 for <5gangip@ietfa.amsl.com>; Mon, 4 Jun 2018 13:24:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.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 ptM6kBoS0W8K for <5gangip@ietfa.amsl.com>; Mon, 4 Jun 2018 13:24:54 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (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 0F34B130DC0 for <5gangip@ietf.org>; Mon, 4 Jun 2018 13:24:53 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id 185-v6so25777440qkk.11 for <5gangip@ietf.org>; Mon, 04 Jun 2018 13:24:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=w6HiR6QmJbC0vJ0GJoszJibb3UrvX9veMiM8a28Oats=; b=fUO8wUs6JIUnUaElP16+yb4+XXL3BaFqEhuycfLRXOEAUPGomGYUnn9fqPyJP3z69w YL8ER7LOZnYGNixkh6NZ9wfcV+XC2ghRKAwFZ7k/nnBE4NR0Ez4UbNx5RhrJxiCOFWcY bVqsrZaI+cG1PjNoWA4nk3i14oWkWuDTi7vAHrl4xO/d8H4BJOFWsIvAxSQNRPTQjB3H 1TCHpSpMn2N4g+BYtfZSK8qXKupaGkREmFa4IH71Shv/RNCEBEYIgqn9FO/GyDAM87U6 Jk68nK7jMQiUxb9cQUB5dxmDohcbUHiN/zoHOwtv/nSJHMzCjF2ilikjPoZrZPfPHS3x jo+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=w6HiR6QmJbC0vJ0GJoszJibb3UrvX9veMiM8a28Oats=; b=l62TSTNmLnMMJKcTeKGYTO8mnc2unlf/JXJXCW8Z8qGKmx6qhqjHz/ycSQ0hRr5oPN WgcCc29SczSKP2Hj9frzwssCD4tgV5kNRZAOndTfP+1ismaeWGKMt9dqKLYWyTL0kxJW AAqewyGT61VpgVecFLmstPcwKn5XavVT8taqrxS61DkY3qeST8GfJ+l9Pj9WFzjCF4s9 QZENAUeYLTIp2dc7WsBwcJ018VrTiebPsRPCcXuP65eC21qHyDCbZl/c4A+YTxfeBLqn Ks5Ms0PA4SaKJYfgTEZKX35PQKHW/3V3V1zH7zipfOr3cxyhXreqYZjuTWF9ETRzUWfD LavA==
X-Gm-Message-State: APt69E0U7m+qjy+Y6eHMDk6Txu9Gb/d/8WKfKfgWBI5zFYeEy6Z3PRVv WYZc2VaeXjHKs/YVQz3x4GCeFIW5w6RjBPsGAzK/G8gp
X-Google-Smtp-Source: ADUXVKJfu43OMpXrYOZMsAvcU4oX8XEuRHoD09/P5BX/MB+Hk5hc73KbMsRLMqs/KM+UNMX5zl3MlOD2+txi6RPWVKE=
X-Received: by 2002:a37:1807:: with SMTP id j7-v6mr21132888qkh.333.1528143892676; Mon, 04 Jun 2018 13:24:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:aed:33a2:0:0:0:0:0 with HTTP; Mon, 4 Jun 2018 13:24:52 -0700 (PDT)
From: Tom Herbert <tom@herbertland.com>
Date: Mon, 04 Jun 2018 13:24:52 -0700
Message-ID: <CALx6S36iOtho-+cPUUPChrKjvyG-ymOjomPo56w8O42BH+XJBQ@mail.gmail.com>
To: 5GANGIP <5gangip@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/Dtq5J-AKxYybhzv7k_UO3nk2uqY>
Subject: [5gangip] Feedback on draft-xyzy-atick-gaps-00
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: Mon, 04 Jun 2018 20:24:56 -0000

As in previous versions, I think this one jumps into talking about
specific solutions too quickly before articulating the problem. I
would make section 3 either be "Problem statement" or "Requirements".
In either case, the text should be generic for any solutions. For
axmaple, some requirements might look like:

* A mapping system is needed to map identifier to locator
* Access to the mapping system must done only by authorized entities.
* Mapping system must mitigate DOS attack
* IP addresses should not expose specific geo-location of users.

etc...

Once the problem or requirments are laid out, then it makes sense to
talk about the specific solutions (should be section 4 in my model),
how they try to address the problems and what their shortcomings are.

I like the idea of section "General recommendations". This would be
section 5 in the model I'm describing, but I suspect this is not
complete. It should be driven to satisfy the requirements or solve the
problem specified in the earlier section. Drawing parts from the
specific solutions makes sense.

Tom