[alto] Progress on the unified properties draft and call for comments

Jensen Zhang <jingxuan.n.zhang@gmail.com> Fri, 05 July 2019 22:02 UTC

Return-Path: <jingxuan.n.zhang@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA1D120136 for <alto@ietfa.amsl.com>; Fri, 5 Jul 2019 15:02:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 1sbi13bE_fAN for <alto@ietfa.amsl.com>; Fri, 5 Jul 2019 15:02:50 -0700 (PDT)
Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (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 D9590120129 for <alto@ietf.org>; Fri, 5 Jul 2019 15:02:49 -0700 (PDT)
Received: by mail-yb1-xb2d.google.com with SMTP id a5so1951401ybo.13 for <alto@ietf.org>; Fri, 05 Jul 2019 15:02:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=3w7LhS+AjFr9GDzn75JrFXNKMDjP72lz8EGZSUd0cQ8=; b=hPHXpEEvAgPpr8ie+rt628MJRtYgg5raGAVXrSCgHTIURSZQ07AOOLXjXJN816TOxV VPxtr+RAHdtyy46QaxJUXs2jk/O+/aANdUmT+QozlwgZGRxpFsQJpEcxsLjsowdYGIed jvY44eB2B/1ISozd18c6MSGi3RQzSBgaQcR2Y2PIySolCW14BxyBwkhpF3hyr+YAgoJT peSm3f8si6Tm3956jZ+QrjAhQU/OCZ6/oUEGFHQnjlMdy1M73GG5WoW11SqE+1QSDI+L +RGAEVdWMgZdO+DmMFO+rXey1PoNHjDwAdBTX9Isija3Xzmp0KpSM1EGUnBzq19ABiKl D+7A==
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:cc; bh=3w7LhS+AjFr9GDzn75JrFXNKMDjP72lz8EGZSUd0cQ8=; b=M7bxUDuyKAsc44TpUlNIKD2+MeIBgx6NEydiSsTxHTSJbKtl89yT15zl8m1SJPIXV/ R3MXXwy+FCVG29YA60OLXIBmX4XMRKtNF5lvRm1wwDj1332i+HrSKtTJ1QOuSTzRg14S qiwW7RzIsLyZq6DYV2cM26iX1n1hPQFOUJORinOrZesK+NJZ0Rda0LnHwAIojRs/yKSX 0goUUeSOuPq/u95jmHJ9JM/4teRVM6hT56A+L+UJ7aMRafo/uRW6BigcmUssTYRe72El YavfPvcbLhwh/ivShhHJNs0B/p7dyzYFLPa3WnP0OL3VSq1Ql7cO/DHXKOaQTpMtmCNl trMA==
X-Gm-Message-State: APjAAAXQkT6Dg8WduZoHWfoRiHOZDNeafPVXYMvShX1MfQ6VcxFoJc4H +/XKWZ7zcbdF4rCpgPxeHIiW53JuXWQvHq2xHT4YE0l4
X-Google-Smtp-Source: APXvYqwVVmiXiOzGLo0klco5RYC9blmRRZ0fDkNsYBm4huB7/I1F/7CXVPRJ7X5eW/FtvxdpoO63Di0DNnE567UTKiU=
X-Received: by 2002:a25:35c2:: with SMTP id c185mr3730730yba.466.1562364168749; Fri, 05 Jul 2019 15:02:48 -0700 (PDT)
MIME-Version: 1.0
From: Jensen Zhang <jingxuan.n.zhang@gmail.com>
Date: Fri, 05 Jul 2019 18:02:37 -0400
Message-ID: <CAAbpuyrrRv8aAKaR89d2ptvFTourmWCejMp1HWbs_9gpA3XMRA@mail.gmail.com>
To: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000049c804058cf641cc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/dZvIlyOiTG3NdUnqkjeWqfb7q0Q>
Subject: [alto] Progress on the unified properties draft and call for comments
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jul 2019 22:02:51 -0000

Hi ALTOers,

After some internal discussions, we are happy to update to WG that we are
finalizing the unified properties draft. And below are some key design
points:

---

1. Consider UP (Unified Property Map) service as a unified ATLO information
resources query mechanism

ALTO defines different types of information resources, which have different
representation formats. But every information resource can map some kinds
of entities to some kinds of properties. e.g., a network map can map ipv4
to pid. UP provides a query mechanism to allow clients to get different
ALTO information resources in the unified representation format.

2. Each UP resource declares a set of (resource_i, DT) -> { (resource_ok,
Pk) } mappings

Here, resource_ok MUST be either resource_i or this (the current UP
resource itself).

- When resource_ok == resource_i, the mapping means the client can query
the property mapping DT -> Pk defined by resource_i. e.g., "ipv4" -> "pid"
defined by "networkmap-1".
- When resource_ok == this, the mapping means the client can query entities
in the entity domain resource_i.DT, and UP will return the property P
defined in its own backend database.

The semantics of entity domain resource_i.DT MUST be defined in the IANA
registry of resource type of resource_i
The semantics of mapping DT -> Pk MUST be defined in the IANA registry of
resource type of resource_ok.

2.1. Use DT -> { (resource_ok, Pk) } as a shortcut of the aggregation

A UP resource can declare "ipv4" -> { ("net1", "pid"), ("net2", "pid") }.
It is equivalent to the outer join of ("net1", "ipv4") -> ("net1", "pid")
and ("net2", "ipv4") -> ("net2", "pid"). In this UP, "ipv4" indicates the
union of entity domain "net1.ipv4" and "net2.ipv4".

3. The client sends the UP query based on the declaration

The client queries a list of entities in resource_i.DT or DT, and a subset
of properties { (resource_ok, Pk) }.

---

We will finish the document revision in the next two days. In the meantime,
your comments and feedback are highly welcomed.

Thanks,
Jensen