[NSIS] Re: QoS NSLP - MRM identification in PACKET_CLASSIFIER
Jukka MJ Manner <jmanner@cs.Helsinki.FI> Sat, 27 May 2006 09:50 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjvRB-0002Uz-8z; Sat, 27 May 2006 05:50:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjvRA-0002Uu-Rc for nsis@ietf.org; Sat, 27 May 2006 05:50:24 -0400
Received: from courier.cs.helsinki.fi ([128.214.9.1] helo=mail.cs.helsinki.fi) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FjvR9-0007dT-HC for nsis@ietf.org; Sat, 27 May 2006 05:50:24 -0400
Received: from sbz-31.cs.helsinki.fi (sbz-31.cs.helsinki.fi [128.214.9.99]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Sat, 27 May 2006 12:50:20 +0300 id 00070141.447820DC.0000398C
Date: Sat, 27 May 2006 12:50:20 +0300
From: Jukka MJ Manner <jmanner@cs.Helsinki.FI>
To: Andrew McDonald <andrew.mcdonald@roke.co.uk>
In-Reply-To: <4476C862.8010701@roke.co.uk>
Message-ID: <Pine.LNX.4.58.0605271247010.13888@sbz-31.cs.Helsinki.FI>
References: <4476C862.8010701@roke.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: Georgios Karagiannis <karagian@cs.utwente.nl>, "Nsis (E-mail)" <nsis@ietf.org>
Subject: [NSIS] Re: QoS NSLP - MRM identification in PACKET_CLASSIFIER
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nsis@ietf.org>
List-Help: <mailto:nsis-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nsis>, <mailto:nsis-request@ietf.org?subject=subscribe>
Errors-To: nsis-bounces@ietf.org
Fine with me. Still, with the current path-coupled MRM of 2 bytes, we probably should add 2 bytes of padding (or reserved bits) to make the object a multiple of 32 bits, e.g., From +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Message-Routing-Method | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + // Method-specific classifier data (variable) // +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |X|Y|P|T|F|S|A|B| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ to +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ // Method-specific classifier data (variable) // +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |X|Y|P|T|F|S|A|B| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Jukka On Fri, 26 May 2006, Andrew McDonald wrote: > Hi all, > > In one reviewer's comments of the QoS NSLP, it was pointed out that the > 'Message-Routing-Method' component of the PACKET_CLASSIFIER (the first two > bytes) is redundant, since it will always be the same as the MRM at the GIST > layer. > > This is currently logged as issue 93 in the QoS NSLP issue tracker: > http://nsis.srmr.co.uk/cgi-bin/roundup.cgi/nsis-qos-nslp-issues/issue93 > > I propose to remove this part of the PACKET_CLASSIFIER. Not only is it > duplication of information already available over the GIST API, it also gives > us some extra error cases to handle (e.g. where it doesn't match the GIST > MRM). If we don't remove it, then we will need to work out what additional > error codes are needed. > > Any opposition to this change? (Or agreement with it?) > > regards, > > Andrew > _______________________________________________ nsis mailing list nsis@ietf.org https://www1.ietf.org/mailman/listinfo/nsis
- [NSIS] QoS NSLP - MRM identification in PACKET_CL… Andrew McDonald
- [NSIS] Re: QoS NSLP - MRM identification in PACKE… Jukka MJ Manner