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

Wendy Roome <w.roome@alcatel-lucent.com> Wed, 29 July 2015 17:47 UTC

Return-Path: <w.roome@alcatel-lucent.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 3DA031B2C30 for <alto@ietfa.amsl.com>; Wed, 29 Jul 2015 10:47:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 aj-dJMLOl9rl for <alto@ietfa.amsl.com>; Wed, 29 Jul 2015 10:47:15 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 679EE1B2C29 for <alto@ietf.org>; Wed, 29 Jul 2015 10:47:15 -0700 (PDT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (unknown [135.5.2.63]) by Websense Email Security Gateway with ESMTPS id 0A0DC7983EBD5 for <alto@ietf.org>; Wed, 29 Jul 2015 17:47:09 +0000 (GMT)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id t6THlBHO014189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <alto@ietf.org>; Wed, 29 Jul 2015 17:47:12 GMT
Received: from [135.222.152.71] (wdr-i7mbp2.mh.lucent.com [135.222.152.71]) by umail.lucent.com (8.13.8/TPES) with ESMTP id t6THl8mX007326 for <alto@ietf.org>; Wed, 29 Jul 2015 12:47:11 -0500 (CDT)
User-Agent: Microsoft-MacOutlook/14.5.2.150604
Date: Wed, 29 Jul 2015 13:47:08 -0400
From: Wendy Roome <w.roome@alcatel-lucent.com>
To: alto@ietf.org
Message-ID: <D1DE85A9.2F2B39%w.roome@alcatel-lucent.com>
Thread-Topic: High level comments on draft-roome-alto-unified-props-00
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/alto/aSg36442jx4-Qtz7mBvfxDsqGSE>
Subject: Re: [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: Wed, 29 Jul 2015 17:47:17 -0000

Richard,

Thanks for the comments.

1. I do not see how we could define a universal hierarchy; I think the
entity hierarchy and inheritance must be defined in the context of each
specific entity domain. Section 2.3 allows for hierarchies, but requires
the domain to define the rules:

   Addresses may be hierarchical, and properties may be inherited based
   on that hierarchy. Again, the rules defining any hierarchy or
   inheritance must be defined when the domain is registered.

If you can suggest a general way to define hierarchy & inheritance for
arbitrary domains, please let me know.

2. I would say the default is no consistency across domains. If there is
any inter-relationship or inheritance between entities from different
domains, the domain rules must define it.

Because PIDs are defined by CIDRs, some readers might think the two
domains are related. So in 3.2.4 I explicitly said they are not.

	- Wendy Roome

>
>Date: Tue, 21 Jul 2015 16:29:09 +0800
>From: "Y. Richard Yang" <yry@cs.yale.edu>
>
>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