Re: [Taps] Prague agenda planning

boza <bozakov@gmail.com> Fri, 30 June 2017 12:31 UTC

Return-Path: <bozakov@gmail.com>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A9D51273E2 for <taps@ietfa.amsl.com>; Fri, 30 Jun 2017 05:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URI_WP_DIRINDEX=1] 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 aF87_PcrLBCF for <taps@ietfa.amsl.com>; Fri, 30 Jun 2017 05:31:56 -0700 (PDT)
Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::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 6245112F265 for <taps@ietf.org>; Fri, 30 Jun 2017 05:31:47 -0700 (PDT)
Received: by mail-vk0-x22e.google.com with SMTP id 191so65133408vko.2 for <taps@ietf.org>; Fri, 30 Jun 2017 05:31:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TJVkRNumqG9ZdjDhnCZbWhR9yOidDcwXW2aChNGbwPA=; b=lmelSml6SSMlhD1kg2fM1koNLrbSLx+BlBI4mmm/a24QN24hCjoUMUv9DcCfWbHaZy tXfIFiJAHRy8v+Rt3n+VWwqYdsGquLT7hVX9D8bUdtxxyLl3OfjDGiSSjBR8XRG1l+BA estzmSwpYpHwJFkLiBRhYw9kYlkZZDJHk5fT1yqmXN6csQ9hgwlTIX28CUDco4FxYd6f nowVe1S+wdd+qrfI6H48iOWAO87y5+GeX+SoUzW0tZq3PalyOQidZVxrw4N+KDox4H9U e0S+gYI5FJknpAS/6EdMorpYRE0dD1/PJ8ey22zZgAfP6IaZuuPdtfOgR4B4D0xNpA0n qkXg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TJVkRNumqG9ZdjDhnCZbWhR9yOidDcwXW2aChNGbwPA=; b=sI9Pqn/sxroLow6c1vrkyDSgi2jq6gNCoEAbSamY8g3CTE1LkD15ttQMFArfAj3L0f MNzd58pgjlM2FmgyVVScqj83qpmtfvsJL+NKPL7CWK2okKzEUbsfCztubTMJWbf2pjP7 FNz7P5bWYJf3RuWV9DqcV4IXMvPHkhX74cFY8w5uUOamlw36bw7TDUAezglKBIug9wOW m1XnKguHp7eq3C+2b2gODOnmmD70UlsvEtBH86PaTgi90UMpzAYuRHIrFcPilIql9fzo 4MwA/hIU25evKW1o5nooQkVhCpnE5eCnyfKoDo271xpPC+tDE3jBvCWg7pS/43+VNFS+ xwfw==
X-Gm-Message-State: AKS2vOyk9Xq7Fzmxf1p/Kv6ZC0L0MI9e0SCZFIgtMWRhAGp6x4ldOgFc dMWD/AXQEudv1x2obLQPSH8bjDNJydRa
X-Received: by 10.31.218.196 with SMTP id r187mr11185908vkg.96.1498825906368; Fri, 30 Jun 2017 05:31:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.87.29 with HTTP; Fri, 30 Jun 2017 05:31:45 -0700 (PDT)
In-Reply-To: <3EC0F8DD-93C9-4551-AF49-BB440D17A68A@ifi.uio.no>
References: <C582EEC8-8762-4CB6-9CA3-4E5AF92C5A68@gmail.com> <3A3686B5-FF60-448E-9E13-4B493B472C6D@gmail.com> <CEA46958-6620-4138-BA2F-B55D1F87674A@trammell.ch> <EDC3DBF5-8463-42AD-BB31-D8EE93CB0BB5@apple.com> <3EC0F8DD-93C9-4551-AF49-BB440D17A68A@ifi.uio.no>
From: boza <bozakov@gmail.com>
Date: Fri, 30 Jun 2017 13:31:45 +0100
Message-ID: <CAGYorBBy2+qcYmYN0oROOC+cnZYjgMEKdW92kJ4B0jSkfCH5TQ@mail.gmail.com>
To: Michael Welzl <michawe@ifi.uio.no>
Cc: "taps@ietf.org" <taps@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c07c562bab90305532c996a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/OLQiI74UZavH0IlxOr93AZF3Hhs>
Subject: Re: [Taps] Prague agenda planning
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions on Transport Services <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 12:31:58 -0000

Hi All,

On Thu, Jun 29, 2017 at 10:09 PM, Michael Welzl <michawe@ifi.uio.no> wrote:

> I think it's time to level up and have a discussion about "policy" and how
> it relates to TAPS.
>
> I'm going to leave the definition of "policy" here deliberately vague with
> the hope that we can start to build some terminology around it at the
> meeting.
>
>
> +1 to having a general discussion on the topic of policy (both
> application-specified and system-specified), likely following onto the
> presentation of intents. Getting a formal set of definitions would really
> help moving forward in our discussions.
>
>
> +1 from me too.
>
> BTW, NEAT already has quite an elaborate policy system built in. Naeem
> gave a high-level look at it at the last meeting:
> https://www.ietf.org/proceedings/98/slides/slides-
> 98-taps-42-neat-naeem-khademi-00.pdf  (slides 6/7)
>
> More details are here:
> https://www.neat-project.org/wp-content/uploads/2017/03/
> commag16-accepted-version.pdf
> This says “until published”, but I think this has just happened:
> http://ieeexplore.ieee.org/document/7945852/
>
> I'd be happy join the discussion on policy aspects (unfortunately, only
remotely). As Michael mentioned, the implemented NEAT policy system is
fairly flexible. The most up-to-date documentation can be found on the NEAT
GitHub <https://github.com/NEAT-project/neat/blob/master/policy/README.md>
pages.
Let me know if you have any questions.

Cheers,
Zdravko