Re: [lmap] Missing concept from draft-eardley-lmap-terminology-01.txt

"MORTON JR., ALFRED C (AL)" <acmorton@att.com> Wed, 15 May 2013 11:57 UTC

Return-Path: <acmorton@att.com>
X-Original-To: lmap@ietfa.amsl.com
Delivered-To: lmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 752D821F8A53 for <lmap@ietfa.amsl.com>; Wed, 15 May 2013 04:57:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.999
X-Spam-Level:
X-Spam-Status: No, score=-105.999 tagged_above=-999 required=5 tests=[AWL=-0.601, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, J_CHICKENPOX_91=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u9BqNx82mNGZ for <lmap@ietfa.amsl.com>; Wed, 15 May 2013 04:57:37 -0700 (PDT)
Received: from mail-pink.research.att.com (mail-pink.research.att.com [192.20.225.111]) by ietfa.amsl.com (Postfix) with ESMTP id 0674D21F882A for <lmap@ietf.org>; Wed, 15 May 2013 04:57:37 -0700 (PDT)
Received: from mail-green.research.att.com (unknown [135.207.178.10]) by mail-pink.research.att.com (Postfix) with ESMTP id 5D95A1202D7; Wed, 15 May 2013 07:57:35 -0400 (EDT)
Received: from njfpsrvexg7.research.att.com (njfpsrvexg7.research.att.com [135.207.177.33]) by mail-green.research.att.com (Postfix) with ESMTP id D198DE3C5F; Wed, 15 May 2013 07:57:17 -0400 (EDT)
Received: from njfpsrvexg7.research.att.com ([fe80::3598:75fe:b400:9299]) by njfpsrvexg7.research.att.com ([fe80::3598:75fe:b400:9299%11]) with mapi; Wed, 15 May 2013 07:57:36 -0400
From: "MORTON JR., ALFRED C (AL)" <acmorton@att.com>
To: "philip.eardley@bt.com" <philip.eardley@bt.com>, "mattmathis@google.com" <mattmathis@google.com>
Date: Wed, 15 May 2013 07:57:34 -0400
Thread-Topic: [lmap] Missing concept from draft-eardley-lmap-terminology-01.txt
Thread-Index: Ac5Pa0ngWDZbSR4NTl66Yuuqv00ovgB1pwdgAAhAjIA=
Message-ID: <F1312FAF1A1E624DA0972D1C9A91379A1BFFE38AF8@njfpsrvexg7.research.att.com>
References: <CAH56bmBOycc9FuyDF4h3Fw-9OW3NH--+6SY=OEZoo_EcxnUe0Q@mail.gmail.com> <9510D26531EF184D9017DF24659BB87F347540758F@EMV65-UKRD.domain1.systemhost.net>
In-Reply-To: <9510D26531EF184D9017DF24659BB87F347540758F@EMV65-UKRD.domain1.systemhost.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_F1312FAF1A1E624DA0972D1C9A91379A1BFFE38AF8njfpsrvexg7re_"
MIME-Version: 1.0
Cc: "lmap@ietf.org" <lmap@ietf.org>
Subject: Re: [lmap] Missing concept from draft-eardley-lmap-terminology-01.txt
X-BeenThere: lmap@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Large Scale Measurement of Access network Performance <lmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lmap>, <mailto:lmap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lmap>
List-Post: <mailto:lmap@ietf.org>
List-Help: <mailto:lmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lmap>, <mailto:lmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 11:57:42 -0000

+1, Phil and Matt. I intended the reference path to be the basis for
discussions like this, especially when seeking equivalent points
in different access technologies.

Al

From: lmap-bounces@ietf.org [mailto:lmap-bounces@ietf.org] On Behalf Of philip.eardley@bt.com
Sent: Wednesday, May 15, 2013 4:10 AM
To: mattmathis@google.com
Cc: lmap@ietf.org
Subject: Re: [lmap] Missing concept from draft-eardley-lmap-terminology-01.txt

<< I would like to have precise but technology independent terms for the boundary between shared and unshared access resources>>
This seems a nice idea to me

As you say, different technologies have the shared/unshared boundary at different distances from the customer. This means that great care is needed if comparing results to the "sharing point" in two different networks

I also agree that having a virtualised example would be good.

Ps think you're referring to http://tools.ietf.org/html/draft-morton-ippm-lmap-path-01 ? - though an open question whether any of the terms from there should be migrated into http://tools.ietf.org/html/draft-eardley-lmap-terminology-01 - might be nice to have them all in one place? Although organisationally one draft sits in ippm and the other in lmap

Thanks!
phil

From: Matt Mathis [mailto:mattmathis@google.com]
Sent: 13 May 2013 00:49
To: Eardley,PL,Philip,TUB8 R
Cc: lmap@ietf.org
Subject: Missing concept from draft-eardley-lmap-terminology-01.txt

Most of the terminology in this draft defined by routing and addressing concepts.   For measurement, it is also important to have terminology to describe traffic aggregation.  Especially important is over which subpaths might one customer's traffic be subject to resource contention with other customers?

I would like to have precise but technology independent terms for the boundary between shared and unshared access resources.   Note that for many technologies (mobile service, DOCSIS) this is very close to the service demarc at the customer.  For others, such as FTTH and DSL it typically occurs in centralized location.

The measurement problems on either side of this boundary are extremely different, and we need to be able to unambiguously make this dichotomy.

I use "unshared access", "shared access", and "sharing point."   Note that for many technologies the sharing point is L2 or lower, so there might not a natural way to connect a MP at the sharing point.

There is also the risk that addressing and routing are going to become progressively less relevant as more and more of the network becomes virtualized through such technologies as software defined networks.    I consider ownership (responsibility), traffic aggregation and resource contention to be far more important than addressing.

Also, "Destination host" is a rather odd choice for a content provider.   Perhaps "core service provider."

Thanks,
--MM--
The best way to predict the future is to create it.  - Alan Kay

Privacy matters!  We know from recent events that people are using our services to speak in defiance of unjust governments.   We treat privacy and security as matters of life and death, because for some users, they are.

On Thu, May 2, 2013 at 2:52 AM, <philip.eardley@bt.com<mailto:philip.eardley@bt.com>> wrote:
I updated the draft http://tools.ietf.org/html/draft-eardley-lmap-terminology
Thank-you for all the comments!

(the draft is a possible starting point for terminology for the prospective lmap wg)

Best wishes
phil

-----Original Message-----
From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>]
Sent: 02 May 2013 09:40
To: Al Morton; Eardley,PL,Philip,TUB8 R; Burbridge,T,Trevor,TUB8 R; Al C.Morton; Marcelo Bagnulo
Subject: New Version Notification for draft-eardley-lmap-terminology-01.txt


A new version of I-D, draft-eardley-lmap-terminology-01.txt
has been successfully submitted by Philip Eardley and posted to the IETF repository.

Filename:        draft-eardley-lmap-terminology
Revision:        01
Title:           Terminology for Large MeAsurement Platforms (LMAP)
Creation date:   2013-05-02
Group:           Individual Submission
Number of pages: 10
URL:             http://www.ietf.org/internet-drafts/draft-eardley-lmap-terminology-01.txt
Status:          http://datatracker.ietf.org/doc/draft-eardley-lmap-terminology
Htmlized:        http://tools.ietf.org/html/draft-eardley-lmap-terminology-01
Diff:            http://www.ietf.org/rfcdiff?url2=draft-eardley-lmap-terminology-01

Abstract:
   This documents defines terminology for Large Scale Measurement
   Platforms.




The IETF Secretariat

_______________________________________________
lmap mailing list
lmap@ietf.org<mailto:lmap@ietf.org>
https://www.ietf.org/mailman/listinfo/lmap