Re: [NSIS] QSPEC Questions

Al Morton <acmorton@att.com> Thu, 06 November 2008 21:10 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 939523A6AC6; Thu, 6 Nov 2008 13:10:36 -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 0DD8E3A6AB6 for <nsis@core3.amsl.com>; Thu, 6 Nov 2008 13:10:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.618
X-Spam-Level:
X-Spam-Status: No, score=-105.618 tagged_above=-999 required=5 tests=[AWL=-0.049, 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 DWv9J8fy0iqN for <nsis@core3.amsl.com>; Thu, 6 Nov 2008 13:10:34 -0800 (PST)
Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.245.115]) by core3.amsl.com (Postfix) with ESMTP id 0760D28C0DB for <nsis@ietf.org>; Thu, 6 Nov 2008 13:10:33 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-11.tower-121.messagelabs.com!1226005824!26653363!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.128.141]
Received: (qmail 32399 invoked from network); 6 Nov 2008 21:10:25 -0000
Received: from sbcsmtp9.sbc.com (HELO flph161.enaf.ffdc.sbc.com) (144.160.128.141) by server-11.tower-121.messagelabs.com with AES256-SHA encrypted SMTP; 6 Nov 2008 21:10:25 -0000
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flph161.enaf.ffdc.sbc.com (8.14.2/8.14.2) with ESMTP id mA6LANdq006999 for <nsis@ietf.org>; Thu, 6 Nov 2008 13:10:24 -0800
Received: from klph001.kcdc.att.com (klph001.kcdc.att.com [135.188.3.11]) by flph161.enaf.ffdc.sbc.com (8.14.2/8.14.2) with ESMTP id mA6LAIOt006913 for <nsis@ietf.org>; Thu, 6 Nov 2008 13:10:19 -0800
Received: from kcdc.att.com (localhost.localdomain [127.0.0.1]) by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id mA6LAIkO020127 for <nsis@ietf.org>; Thu, 6 Nov 2008 15:10:18 -0600
Received: from maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id mA6LAFku020092 for <nsis@ietf.org>; Thu, 6 Nov 2008 15:10:15 -0600
Message-Id: <200811062110.mA6LAFku020092@klph001.kcdc.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 <20081106211015gw1003sn0ke>; Thu, 6 Nov 2008 21:10:15 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 06 Nov 2008 16:10:15 -0500
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, 'Xiaoming Fu' <fu@cs.uni-goettingen.de>
From: Al Morton <acmorton@att.com>
In-Reply-To: <079101c9404c$51625220$d206d00a@nsnintra.net>
References: <00ff01c93c55$b62dee80$04ffa8c0@nsnintra.net> <490D0132.1000709@cs.uni-goettingen.de> <200811061743.mA6HhqE0030117@klph001.kcdc.att.com> <079101c9404c$51625220$d206d00a@nsnintra.net>
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 03:14 PM 11/6/2008, Hannes Tschofenig wrote:
>Al,
>
>shouldn't we provide that type of context in the document as well?

I agree, perhaps that's why I dug-up the details
and shared them on the list. These are non-trivial
calculations in some cases, but procedures exist.

Al




>They document does not appear self contained enough so that a regular reader
>can understand it easily.
>
>Ciao
>Hannes
>
>
> >-----Original Message-----
> >From: Al Morton [mailto:acmorton@att.com]
> >Sent: 06 November, 2008 19:44
> >To: Xiaoming Fu; Hannes Tschofenig
> >Cc: nsis@ietf.org
> >Subject: Re: [NSIS] QSPEC Questions
> >
> >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