[alto] High level comments on draft-roome-alto-unified-props-00

"Y. Richard Yang" <yry@cs.yale.edu> Tue, 21 July 2015 08:29 UTC

Return-Path: <yang.r.yang@gmail.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8B121B2AAB for <alto@ietfa.amsl.com>; Tue, 21 Jul 2015 01:29:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 vRrLuTm10dHs for <alto@ietfa.amsl.com>; Tue, 21 Jul 2015 01:29:10 -0700 (PDT)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (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 513F01B2A9B for <alto@ietf.org>; Tue, 21 Jul 2015 01:29:10 -0700 (PDT)
Received: by igbij6 with SMTP id ij6so102845493igb.1 for <alto@ietf.org>; Tue, 21 Jul 2015 01:29:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=yt+3aptCecS2pn3lk0KkQntRUeGOJhIKeql4acZUCaI=; b=OPDOJLibQtywjZ2dJc0WQWeU5G+LlUKeqS28YIRl0EHgAIp99XmPVOkZY1ztzjoXZ7 rd/H6wYIDDpgcaFVDZ6EpMTJfXqHIqGUaJJA7XhtWOwpY4ujQehLCV303xxj3p0tI3xC w8+8QKl90vFwXKgGnrIvpYauioU+o0/4GQgRTGVVHAU15jMZr5+br0XldvxToyGxQYFe tBU9QmUyiJJDy+7kvA3H4/EPwR1lJ0/4D74l4ivewDz4b2980BA+qB/sfk3c7C+ERwG2 R/0B6rYH9pr62dFUBITxZAuEQ1D6DCcZUzBKqZkW079KsU5NlXLMGPPaqn23kjQwWjbJ /12g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=googleprd; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=yt+3aptCecS2pn3lk0KkQntRUeGOJhIKeql4acZUCaI=; b=liPkCcFLXjuwBn0EqJM/j/gs5oko6q/mlvZueGUaJVZgu+7clj9f0YzU3ZO3PH++xr +GgaRZPeZX6EHJhKb8NsLaFK4NBCooaAWzHmDwIOwDdpH+KuzC2N047CaHLzu0sgivrb bwqpMSYXdfmGhqfHYddwR1UMtol7RzFoAauGg=
MIME-Version: 1.0
X-Received: by 10.50.78.232 with SMTP id e8mr20384882igx.24.1437467349828; Tue, 21 Jul 2015 01:29:09 -0700 (PDT)
Sender: yang.r.yang@gmail.com
Received: by 10.36.141.70 with HTTP; Tue, 21 Jul 2015 01:29:09 -0700 (PDT)
Date: Tue, 21 Jul 2015 16:29:09 +0800
X-Google-Sender-Auth: KA5Qxazkn3U4vsy0YVVJZZ_kle4
Message-ID: <CANUuoLoyyRCNrUTH0Au_0eWWmCcVQzLJEvBj-kAGym9FiNVuPw@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: IETF ALTO <alto@ietf.org>, "nets@cs.yale.edu" <nets@cs.yale.edu>
Content-Type: multipart/alternative; boundary="089e013c6a20c34cc0051b5e72be"
Archived-At: <http://mailarchive.ietf.org/arch/msg/alto/mIu6D8H0lkWGU31GGq0RXQ-5Vqs>
Subject: [alto] High level comments on draft-roome-alto-unified-props-00
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 21 Jul 2015 08:29:11 -0000

Wendy, all,

I just read draft draft-roome-alto-unified-props-00 and liked it a lot. It
is very well written, as Wendy always does, and I recommend that many of
you read this design.

Personally, I see this design as a good candidate as a WG item. Before
making up my mind, I see benefits in discussing two high level design
decisions:
1. Hierarchy of general domains. In the current design, this issue already
appears in the ipv4 and ipv6 domains. The approach that the draft adopts is
longest prefix matching (LPM); see Section 3.1.3.. This can be considered
as smallest containing set, if we see each CIDR as a set, and such sets
form a directed acyclic graph. Q: Does it make sense for the document to go
as far as defining this general principle, instead of the specific LPM?

2. Consistency of the same property across domains. Section 3.2.4 gives one
example of such a case. Q: Is this a specific decision for two specific
domains, or the general principle is no across domain consistency?

Cheers,
Richard
-