IETF Logo Mail Archive

[NSIS] QSPEC Questions

"Hannes Tschofenig" <Hannes.Tschofenig@gmx.net> Sat, 01 November 2008 19:12 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 9D4293A69AD; Sat, 1 Nov 2008 12:12:14 -0700 (PDT)
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 56B3D3A69AF for <nsis@core3.amsl.com>; Sat, 1 Nov 2008 12:12:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level:
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, 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 GyO8w1Bhzb1G for <nsis@core3.amsl.com>; Sat, 1 Nov 2008 12:12:12 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 7FBED3A69AD for <nsis@ietf.org>; Sat, 1 Nov 2008 12:12:10 -0700 (PDT)
Received: (qmail invoked by alias); 01 Nov 2008 19:11:56 -0000
Received: from a91-154-101-110.elisa-laajakaista.fi (EHLO 4FIL42860) [91.154.101.110] by mail.gmx.net (mp055) with SMTP; 01 Nov 2008 20:11:56 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/ZHXcxC2fZmRTR754Z9ZAqNHzIhgyBqXW7Q17hxH jLsH2yeNC5di6j
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
To: nsis@ietf.org
Date: Sat, 01 Nov 2008 21:11:57 +0200
Message-ID: <00ff01c93c55$b62dee80$04ffa8c0@nsnintra.net>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ack8VInW+kEZwtCtQl6x6FC8tqiHjg==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.5600000000000001
Subject: [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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

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?  

* 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.

* Why is Path Jitter STAT4(Reserved) included in the <Path Jitter>
parameter? 

* 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? 

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