IETF Logo Mail Archive

Re: [NSIS] Last Call: draft-ietf-nsis-rmd (RMD-QOSM - The Resource Management in Diffserv QOS Model) to Experimental RFC

Gerald Ash <gash5107@yahoo.com> Mon, 22 March 2010 19:30 UTC

Return-Path: <gash5107@yahoo.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6A5A28C15F for <ietf@core3.amsl.com>; Mon, 22 Mar 2010 12:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.184
X-Spam-Level:
X-Spam-Status: No, score=-100.184 tagged_above=-999 required=5 tests=[AWL=-0.909, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, 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 LKWoun48Gg7q for <ietf@core3.amsl.com>; Mon, 22 Mar 2010 12:30:13 -0700 (PDT)
Received: from web63608.mail.re1.yahoo.com (web63608.mail.re1.yahoo.com [69.147.97.78]) by core3.amsl.com (Postfix) with SMTP id 6727428C130 for <ietf@ietf.org>; Mon, 22 Mar 2010 12:30:04 -0700 (PDT)
Received: (qmail 36964 invoked by uid 60001); 22 Mar 2010 19:30:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1269286219; bh=LZKUy22EgTFBPPeacb70zmB5g0LmdoZpaHO6Y0PTFSI=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=0Wtik2/0r/8o/kg7yKWAJbDpg3eGAcq01gObaUlb9nym+eImRToQkTq39ECCCiWNS2shr7SgsxQoMLv+OjCykW9hvbDeaMZHPqQCf02RD7yQzgRRa6T602c1bpeXhdlaAuett7C7JTsZrE8NTzjj8tQRuuZAsmHZiXmkACl5qY4=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=Nggll/IhPhBqkx5+nLaphYwntR4+QXHtS6zNf9q9WageVjikRAoDl0ZkM9dq3rpbbfcku3ddotJU+W7z14rdVZIH1n7pugKUtnG0BXnR15y2MtK7IfjdgO8gLtJyoWjR0ZY1S9OaaAxeJWlOwdWUCpIZBov29t+INZssDBcMsDU=;
Message-ID: <676573.36462.qm@web63608.mail.re1.yahoo.com>
X-YMail-OSG: CW9dZwEVM1kJ_Tq2Kn9Xbrb0SwPBi2lbONheGXP2SEUMpP6abHoI4NQWvOLH9JohchTzXeVSdU6Iu0deDlUicfoysS3yCeDPVek8dNKzXhIQrJEZw8Z4Doq6_5YH7kktzvQGSZGbnVxdAJ5QGK3Y6aUevwY3V5kgZDmmUSqOQNlH_AbGLTORPsA_O_Tq2pEFxqqcEIrVR6vAMCOlJrNt5_YA7GatMPBd7xuuG71Q4fP6JVd0Juez8wVCxs.tZ1WJ0Q_xkbx0HUBiQOERxWRV.OJn8nj2gb2PDVL2sTlI1SOO1Uk-
Received: from [76.28.13.102] by web63608.mail.re1.yahoo.com via HTTP; Mon, 22 Mar 2010 12:30:19 PDT
X-Mailer: YahooMailClassic/10.0.8 YahooMailWebService/0.8.100.260964
Date: Mon, 22 Mar 2010 12:30:19 -0700
From: Gerald Ash <gash5107@yahoo.com>
Subject: Re: [NSIS] Last Call: draft-ietf-nsis-rmd (RMD-QOSM - The Resource Management in Diffserv QOS Model) to Experimental RFC
To: Georgios Karagiannis <karagian@cs.utwente.nl>
In-Reply-To: <idHgTcpH.1269048294.4369880.karagian@ewi.utwente.nl>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-111658767-1269286219=:36462"
X-Mailman-Approved-At: Tue, 23 Mar 2010 08:43:04 -0700
Cc: Jerry Ash <gash5107@yahoo.com>, "ietf@ietf.org" <ietf@ietf.org>, "nsis@ietf.org" <nsis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Mar 2010 19:30:19 -0000

Hi Georgios,
 
RE:

>> 2. It would further clarify if you put in the bit-level example of the RMD-QSPEC, 
>> as called for by QOSM requirements given in the QSPEC draft.  E.g., such a 
>> bit-level QSPEC example is given in Section 4.5 ("Bit-Level QSPEC Example") 
>> of the Y.1541-QOSM draft
>> (http://tools.ietf.org/html/draft-ietf-nsis-y1541-qosm-10#section-4.5).  
>> This would clarify, for example, the QSPEC Procedure being used and other
>> bit-level details.

> Georgios: but this is already specified in Section 4.1. We could include
> a sentence in the appendix: "The bit level format of the RMD-QSPEC is
> specified in Section 4.1."
 
I don't see a full bit-level RMD-QSPEC example in Section 4.1  For one thing, the QSPEC header isn't given.  IMO it would be better to include a full bit-level example, including headers, etc., somewhere in Appendix A.
 
Thanks,
Jerry

v2.23.0 | Report a Bug | By Email