RE: [ippm] draft-shalunov-ippm-reporting-00.txt - availability

Al Morton <acmorton@att.com> Tue, 02 May 2006 13:24 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FaurW-0004HL-NO; Tue, 02 May 2006 09:24:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FaurV-0004Fc-FG for ippm@ietf.org; Tue, 02 May 2006 09:24:21 -0400
Received: from mail126.messagelabs.com ([216.82.250.99]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FaurT-000392-0K for ippm@ietf.org; Tue, 02 May 2006 09:24:21 -0400
X-VirusChecked: Checked
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-10.tower-126.messagelabs.com!1146576257!11290285!1
X-StarScan-Version: 5.5.9.1; banners=-,-,-
X-Originating-IP: [134.24.146.4]
Received: (qmail 17952 invoked from network); 2 May 2006 13:24:17 -0000
Received: from unknown (HELO maillennium.att.com) (134.24.146.4) by server-10.tower-126.messagelabs.com with SMTP; 2 May 2006 13:24:17 -0000
Received: from acmt.att.com (acmt.mt.att.com[135.16.251.35](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20060502132416gw100100kle>; Tue, 2 May 2006 13:24:16 +0000
Message-Id: <6.2.1.2.0.20060502091126.08aeb8d0@postoffice.maillennium.att.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2
Date: Tue, 02 May 2006 09:24:16 -0400
To: "Geib, Ruediger" <Ruediger.Geib@t-systems.com>, shalunov@internet2.edu
From: Al Morton <acmorton@att.com>
Subject: RE: [ippm] draft-shalunov-ippm-reporting-00.txt - availability
In-Reply-To: <6439282641581441A36F7F6F83ED2ED20E631A@S4DE8PSAAFQ.mitte.t -com.de>
References: <6439282641581441A36F7F6F83ED2ED20E631A@S4DE8PSAAFQ.mitte.t-com.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: ippm@ietf.org
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org >
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org ?subject=unsubscribe>
List-Post: <mailto:ippm@ietf.org >
List-Help: <mailto:ippm-request@ietf.org ?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org ?subject=subscribe>
Errors-To: ippm-bounces@ietf.org

Thanks, Ruediger. Another way to look at this topic:

Users experience network performance in at least two states:
available or "broken" (unavailable) where typically some
sort of failure or misconfiguration cannot be restored automatically
and requires human intervention.

The tricky part is defining the performance levels that
constitute the transitions between the two states,
and keep them application-independent for simplicity.
Despite the difficulties, Availability is probably one of
the most important network metrics, as far as real users
are concerned.

Al


At 08:39 AM 5/2/2006, Geib, Ruediger wrote:
>Stas,
>
>Real time and leased line services are characterised by an "availability". 
>I think availability is a useful and common means to characterise these 
>services. Today, there's only a meausurement principle for IP service 
>availability. There's no commonly implemented IP service availability 
>measurement (RFC2678 on connectivity proposes some metrics which may be 
>useful).
>
>The idea is that you define a service availability over time. If the 
>service is available, the metrics you've listed below are applied to 
>characterise the service. If the service is not available, then no further 
>performance characterisation is required.
>
>As more real time services start to be migrated to the Internet, measuring 
>IP transport availability may be of interest.
>
>Regards,
>
>Rudiger
>
>
>Carsten|> * additionally "availability" could be one metric
>|>   (probably with param = (list of) server(s) or network)
>
>Stas|Why aren't existing metrics enough?  When no packets
>|come through, you'll see
>|
>|delay = +infinity
>|loss = 100%
>|jitter = undefined
>|duplication = 0%
>|reordering = 0%
>|
>|Is that not enough?
>
>_______________________________________________
>ippm mailing list
>ippm@ietf.org
>https://www1.ietf.org/mailman/listinfo/ippm


_______________________________________________
ippm mailing list
ippm@ietf.org 
https://www1.ietf.org/mailman/listinfo/ippm