Re: [NSIS] QSPEC Questions

Al Morton <acmorton@att.com> Thu, 06 November 2008 17:44 UTC

Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D60233A6A6D; Thu, 6 Nov 2008 09:44:10 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E4373A69E2 for <nsis@core3.amsl.com>; Thu, 6 Nov 2008 09:44:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.622
X-Spam-Level:
X-Spam-Status: No, score=-105.622 tagged_above=-999 required=5 tests=[AWL=-0.053, BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id alNuODEUsjC9 for <nsis@core3.amsl.com>; Thu, 6 Nov 2008 09:44:09 -0800 (PST)
Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.245.115]) by core3.amsl.com (Postfix) with ESMTP id 5FB2F3A6A2A for <nsis@ietf.org>; Thu, 6 Nov 2008 09:44:09 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-6.tower-121.messagelabs.com!1225993441!21445305!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 1389 invoked from network); 6 Nov 2008 17:44:01 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com) (144.160.20.54) by server-6.tower-121.messagelabs.com with AES256-SHA encrypted SMTP; 6 Nov 2008 17:44:01 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id mA6Hi09l013987 for <nsis@ietf.org>; Thu, 6 Nov 2008 12:44:01 -0500
Received: from alph001.aldc.att.com (alph001.aldc.att.com [135.53.7.26]) by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id mA6HhwaY013956 for <nsis@ietf.org>; Thu, 6 Nov 2008 12:43:58 -0500
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alph001.aldc.att.com (8.14.0/8.14.0) with ESMTP id mA6Hhwwp023217 for <nsis@ietf.org>; Thu, 6 Nov 2008 12:43:58 -0500
Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alph001.aldc.att.com (8.14.0/8.14.0) with ESMTP id mA6HhqCX023125 for <nsis@ietf.org>; Thu, 6 Nov 2008 12:43:52 -0500
Message-Id: <200811061743.mA6HhqCX023125@alph001.aldc.att.com>
Received: from acmt.att.com (dyp004244dys.mt.att.com[135.16.251.219](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20081106174352gw1003snu9e>; Thu, 6 Nov 2008 17:43:52 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 06 Nov 2008 12:43:50 -0500
To: Xiaoming Fu <fu@cs.uni-goettingen.de>, Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
From: Al Morton <acmorton@att.com>
In-Reply-To: <490D0132.1000709@cs.uni-goettingen.de>
References: <00ff01c93c55$b62dee80$04ffa8c0@nsnintra.net> <490D0132.1000709@cs.uni-goettingen.de>
Mime-Version: 1.0
Cc: nsis@ietf.org
Subject: Re: [NSIS] QSPEC Questions
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/nsis>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

At 09:24 PM 11/1/2008, Xiaoming Fu wrote:
>Hannes Tschofenig wrote:
>...
>>* Where does the description for <Path Jitter>, <Path PLR> and <Path PER>
>>come from? There is no reference to another RFC given in these sections.
>
>QSPEC ID suggested packet jitter is based on [rfc3393], but I am not 
>sure whether (nominal) jitter values are directly addable across multiple hops.

It's possible to accumulate Jitter values, if they're measured
and specified in the appropriate form.
The more detailed references include Rec Y.1541,
http://tools.ietf.org/html/draft-ietf-ippm-spatial-composition-07
http://tools.ietf.org/html/draft-ietf-ippm-delay-var-as-01
>Also, is PLR or PER directly addable (or just a multiplication)?

see the first two refs above.
Al

_______________________________________________
nsis mailing list
nsis@ietf.org
https://www.ietf.org/mailman/listinfo/nsis