IETF Logo Mail Archive

Re: [NSIS] QSPEC Questions

Gerald Ash <gash5107@yahoo.com> Sun, 02 November 2008 18:40 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 B873C3A6A9F; Sun, 2 Nov 2008 10:40:40 -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 7CFC83A6A21 for <nsis@core3.amsl.com>; Sun, 2 Nov 2008 10:40:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.037
X-Spam-Level:
X-Spam-Status: No, score=-2.037 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, SARE_SUB_OBFU_Q1=0.227]
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 4QPij55wnYYM for <nsis@core3.amsl.com>; Sun, 2 Nov 2008 10:40:38 -0800 (PST)
Received: from web63603.mail.re1.yahoo.com (web63603.mail.re1.yahoo.com [69.147.97.73]) by core3.amsl.com (Postfix) with SMTP id 5E9903A6A37 for <nsis@ietf.org>; Sun, 2 Nov 2008 10:40:38 -0800 (PST)
Received: (qmail 19974 invoked by uid 60001); 2 Nov 2008 18:40:36 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=NQPnCu6LaMzNCnmJKK95Cuz2KrkwRf/OT+4am0mzP/+s54+n2jXu+nwK8ZqF+c2LQZ/z4EL60W8L2RcCpb17czktAwCmG+xcvy8zjwhl9I5j2eSGYnmETUn4H+Qy+hcLQpKOytzLTILyZo3/pC+bT58kbd26DtfrYc33Xn2svnI=;
X-YMail-OSG: tplH02MVM1kIn5e09YtSrA5xHjz8ZI0Vlf2WQVSNwusIblYGoq4vEIL5DDLfuuqX1cFY5c31pIp6XTZyb1cluEqIGUTow0saUZECIfSeM_wm919_RGM_sc0rAbUvFW_08f.kTDm6PoiW.B9ri4aGpAkZAxI-
Received: from [76.19.255.157] by web63603.mail.re1.yahoo.com via HTTP; Sun, 02 Nov 2008 10:40:35 PST
X-Mailer: YahooMailWebService/0.7.260.1
Date: Sun, 02 Nov 2008 10:40:35 -0800
From: Gerald Ash <gash5107@yahoo.com>
To: nsis@ietf.org, Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
In-Reply-To: <00ff01c93c55$b62dee80$04ffa8c0@nsnintra.net>
MIME-Version: 1.0
Message-ID: <90840.19963.qm@web63603.mail.re1.yahoo.com>
Subject: Re: [NSIS] QSPEC Questions
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: gash5107@yahoo.com
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-Type: multipart/mixed; boundary="===============1888648902=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hannes,
 
> From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
> Subject: [NSIS] QSPEC Questions
> To: nsis@ietf.org
> Date: Saturday, November 1, 2008, 3:11 PM
> 
> 
> Based on Dan's AD review comments for draft-ietf-dime-qos-parameters-06 I
> need to ask a few questions regarding the QSPEC draft:
> 
> * There is no description of the differences between TMOD-1 and TMOD-2.
> Useful to say something about the difference?  
> 
 
Discussed in some detail in Section 3.3.1 (as Elwyn pointed out).

> * 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.
 
References for <Path Jitter> are [RFC3393], [Y.1540], [Y.1541], as given in Section 3.3.2.
Reference for <Path PLR> is [Y.1541], as given in Section 3.3.2.
Reference for <Path PER> is [Y.1541], as given in Section 3.3.2.
 
These references should also be added to the headings of Sections 5.2.4, 5.2.5, and 5.2.6, respectively.

> 
> * Why is Path Jitter STAT4(Reserved) included in the <Path Jitter>
> parameter?
> 
 
The computation of Path Jitter is discussed in [Y.1541], including numerical examples.  Perhaps Al Morton (editor of [Y.1541]) can provide explanatory text to add to the QSPEC document.

> * The encoding of the  <RPH Priority> Parameter is not inline with
> http://tools.ietf.org/id/draft-ietf-tsvwg-emergency-rsvp-09.txt. The ALRP
> Priority and the Reserved octets 
> positions are inversed. 
> 
> * <DSTE Class Type> Parameter
> 
> The QSPEC draft says:
> "
> DSTE Class Type: Indicates the DSTE class type.  Values currently
>   allowed are 0, 1, 2, 3, 4, 5, 6, 7.
> "
> 
> RFC 4124 does not define a value of 0. Where does 0 come from? 
> In RFC 4124 the field is only 3 bits long. Why is it 8 bytes long in the
> QSPEC document? 
 
I agree with Elwyn that the QSPEC DSTE Class Type parameter should be aligned with RFC 4124.  It also appears that an IANA registry is not needed since none is defined in RFC 4124.
 
Jerry

> 
> Your feedback is appreciated!
> 
> Ciao
> Hannes
>


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

v2.23.0 | Report a Bug | By Email