From nsis-bounces@ietf.org  Fri Apr  4 13:45:06 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9ED323A6DDD;
	Fri,  4 Apr 2008 13:45:05 -0700 (PDT)
X-Original-To: nsis@ietf.org
Delivered-To: nsis@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 03A2F3A6969; Fri,  4 Apr 2008 13:45:01 -0700 (PDT)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080404204502.03A2F3A6969@core3.amsl.com>
Date: Fri,  4 Apr 2008 13:45:01 -0700 (PDT)
Cc: nsis@ietf.org
Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-20.txt
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-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>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Next Steps in Signaling Working Group of the IETF.

	Title		: QoS NSLP QSPEC Template
	Author(s)	: G. Ash, A. Bader, C. Kappler, D. Oran
	Filename	: draft-ietf-nsis-qspec-20.txt
	Pages		: 55
	Date		: 2008-4-4
	
The QoS NSLP protocol is used to signal QoS reservations and is
   independent of a specific QoS model (QOSM) such as IntServ or
   DiffServ.  Rather, all information specific to a QOSM is encapsulated
   in a separate object, the QSPEC.  This document defines a template
   for the QSPEC including a number of QSPEC parameters.  The QSPEC
   parameters provide a common language to be re-used in several QOSMs
   and thereby aim to ensure the extensibility and interoperability of
   QoS NSLP.  The node initiating the NSIS signaling adds an initiator
   QSPEC, which indicates the QSPEC parameters that must be interpreted
   by the downstream nodes less the reservation fails, thereby ensuring
   the intention of the NSIS initiator is preserved along the signaling
   path.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-20.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-nsis-qspec-20.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-4-4133554.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--



From nsis-bounces@ietf.org  Wed Apr  9 01:28:40 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A6013A69E7;
	Wed,  9 Apr 2008 01:28:40 -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 D916B3A6B5E
	for <nsis@core3.amsl.com>; Wed,  9 Apr 2008 01:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.437
X-Spam-Level: 
X-Spam-Status: No, score=0.437 tagged_above=-999 required=5
	tests=[BAYES_20=-0.74, HELO_EQ_DE=0.35, J_CHICKENPOX_14=0.6,
	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 z7XrNjpcE+Ol for <nsis@core3.amsl.com>;
	Wed,  9 Apr 2008 01:28:38 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de
	[141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id 139873A68CD
	for <nsis@ietf.org>; Wed,  9 Apr 2008 01:28:38 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps id 1JjVfp-00005U-5p
	for <nsis@ietf.org>; Wed, 09 Apr 2008 10:28:54 +0200
Received: from i72ms.tm.uni-karlsruhe.de ([141.3.70.5]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by irams1.ira.uni-karlsruhe.de with esmtps for <nsis@ietf.org>
	id 1JjVfp-0007tN-2o; Wed, 09 Apr 2008 10:28:53 +0200
Received: from vorta.tm.uka.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:21b:fcff:fe96:fe02])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id F18372FC019
	for <nsis@ietf.org>; Wed,  9 Apr 2008 10:28:52 +0200 (CEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by vorta.tm.uka.de (Postfix) with ESMTP id 14D06103F1
	for <nsis@ietf.org>; Wed,  9 Apr 2008 10:29:13 +0200 (CEST)
Message-ID: <47FC7E58.4020709@tm.uka.de>
Date: Wed, 09 Apr 2008 10:29:12 +0200
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: "nsis@ietf.org" <nsis@ietf.org>
X-Enigmail-Version: 0.95.0
Subject: [NSIS] QSPEC TMOD and packet header overhead
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-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

Hi,

probably a dumb question, but Max Laier and I could not find any
guidance on this in the qspec draft:
I guess that the TMOD-1 r parameter in draft-ietf-nsis-qspec-20
specifies the number of bytes/s for IP packets, including any
IP headers. Now consider a mobile node that adds extra overhead
to its data packets due to the mobility headers etc. This could be
significant for VoIP packets. So in this case the applications has
to increase r depending on the packet rate and m must be increased,
too?

As another example: if the application communicates via IPv4
it has to specify for a normal PCM codec VoIP traffic:
r=50*(20+8+12+160)=10,000 bytes/s
  [packet every 20ms,IP+UDP+RTP+payload], m=200 bytes,
  b= 2000 bytes, p=very high (allowing a burst of 10 packets)
and when communication via IPv6
r=50*(40+8+12+160)=11,000 bytes/s, m=220 bytes,
b= 2200 bytes

Is this correct? Would it make sense to provide a little
guidance on this and an example in the QSPEC?

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


From nsis-bounces@ietf.org  Fri Apr 11 02:12:31 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6F44E3A6E5B;
	Fri, 11 Apr 2008 02:12:31 -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 ACD1D3A6D74
	for <nsis@core3.amsl.com>; Fri, 11 Apr 2008 02:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5
	tests=[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 yvgRq8PUoFS0 for <nsis@core3.amsl.com>;
	Fri, 11 Apr 2008 02:12:27 -0700 (PDT)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id 516E03A6E40
	for <nsis@ietf.org>; Fri, 11 Apr 2008 02:12:27 -0700 (PDT)
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id CC1AC2C026DAC
	for <nsis@ietf.org>; Fri, 11 Apr 2008 11:12:49 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1])
	by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id r-++6JFAacba for <nsis@ietf.org>;
	Fri, 11 Apr 2008 11:12:49 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id B77132C026DAB
	for <nsis@ietf.org>; Fri, 11 Apr 2008 11:12:44 +0200 (CEST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C89BB4.33A0DC24"
Date: Fri, 11 Apr 2008 11:12:44 +0200
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF631240@mx1.office>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-20.txt
thread-index: AciWlQvrAhSmqMlmR1eHKu/KXov1VQFHxIpg
From: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>
To: "nsis" <nsis@ietf.org>
Subject: [NSIS] FW:  I-D ACTION:draft-ietf-nsis-qspec-20.txt
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-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>
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C89BB4.33A0DC24
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

Thanks to Jerry and the co-authors for updating the draft.=20

Please review the draft and send your feedback.

  Martin

stiemerling@nw.neclab.eu   <=3D=3D NEW ADDRESS

NEC Laboratories Europe - Network Research Division
NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, =
London W3 6BL | Registered in England 2832014 =20

> -----Original Message-----
> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On=20
> Behalf Of Internet-Drafts@ietf.org
> Sent: Friday, April 04, 2008 10:45 PM
> To: i-d-announce@ietf.org
> Cc: nsis@ietf.org
> Subject: [NSIS] I-D ACTION:draft-ietf-nsis-qspec-20.txt
>=20
> A New Internet-Draft is available from the on-line=20
> Internet-Drafts directories.
> This draft is a work item of the Next Steps in Signaling=20
> Working Group of the IETF.
>=20
> 	Title		: QoS NSLP QSPEC Template
> 	Author(s)	: G. Ash, A. Bader, C. Kappler, D. Oran
> 	Filename	: draft-ietf-nsis-qspec-20.txt
> 	Pages		: 55
> 	Date		: 2008-4-4
> =09
> The QoS NSLP protocol is used to signal QoS reservations and is
>    independent of a specific QoS model (QOSM) such as IntServ or
>    DiffServ.  Rather, all information specific to a QOSM is=20
> encapsulated
>    in a separate object, the QSPEC.  This document defines a template
>    for the QSPEC including a number of QSPEC parameters.  The QSPEC
>    parameters provide a common language to be re-used in several QOSMs
>    and thereby aim to ensure the extensibility and interoperability of
>    QoS NSLP.  The node initiating the NSIS signaling adds an initiator
>    QSPEC, which indicates the QSPEC parameters that must be=20
> interpreted
>    by the downstream nodes less the reservation fails,=20
> thereby ensuring
>    the intention of the NSIS initiator is preserved along the=20
> signaling
>    path.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qspec-20.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail=20
> reader implementation to automatically retrieve the ASCII=20
> version of the Internet-Draft.
>=20

------_=_NextPart_001_01C89BB4.33A0DC24
Content-Type: application/octet-stream;
	name="draft-ietf-nsis-qspec-20.URL"
Content-Transfer-Encoding: base64
Content-Description: draft-ietf-nsis-qspec-20.URL
Content-Disposition: attachment;
	filename="draft-ietf-nsis-qspec-20.URL"

W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC1pZXRmLW5zaXMtcXNwZWMtMjAudHh0DQo=

------_=_NextPart_001_01C89BB4.33A0DC24
Content-Type: text/plain;
	name="ATT39573.txt"
Content-Transfer-Encoding: base64
Content-Description: ATT39573.txt
Content-Disposition: attachment;
	filename="ATT39573.txt"

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm5zaXMgbWFp
bGluZyBsaXN0DQpuc2lzQGlldGYub3JnDQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL25zaXMNCg==

------_=_NextPart_001_01C89BB4.33A0DC24
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

------_=_NextPart_001_01C89BB4.33A0DC24--


From nsis-bounces@ietf.org  Fri Apr 11 13:43:02 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 99E083A6CA4;
	Fri, 11 Apr 2008 13:43:02 -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 323F13A6CA4
	for <nsis@core3.amsl.com>; Fri, 11 Apr 2008 13:43:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.437
X-Spam-Level: 
X-Spam-Status: No, score=-1.437 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334,
	J_CHICKENPOX_14=0.6, 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 lh5epJz-50kH for <nsis@core3.amsl.com>;
	Fri, 11 Apr 2008 13:43:00 -0700 (PDT)
Received: from web63612.mail.re1.yahoo.com (web63612.mail.re1.yahoo.com
	[69.147.97.82]) by core3.amsl.com (Postfix) with SMTP id 010E03A6C5A
	for <nsis@ietf.org>; Fri, 11 Apr 2008 13:42:59 -0700 (PDT)
Received: (qmail 9017 invoked by uid 60001); 11 Apr 2008 20:43:23 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=wAWG7UTcRW3xqxhj0D8xD8xsYwQxvkN4LWdBLHQGdiTJWQCoHMPyqHuGsFhpEt6jGVN5DTNPcYVrJBA5SqPfgam7lpT0Hj7vmFL0xM288DSq+3Re3tPSE+XgtOufC08+anCrA+l+zQv0oFSXfl9s+uI4ry5EUhV0/WusigwC8Gk=;
X-YMail-OSG: 2kwadGUVM1meBpvcx2aEY2BuRIhdE8fzfHaiYbxZs1BHCiIXtr0AzkDaF9MQOv8oR.c3rof21i5G1.VB6fTp9SDRFNdgs83p3CCP8pwHDOV5wjReBSq7iWZynSDndw--
Received: from [76.19.255.157] by web63612.mail.re1.yahoo.com via HTTP;
	Fri, 11 Apr 2008 13:43:21 PDT
Date: Fri, 11 Apr 2008 13:43:21 -0700 (PDT)
From: Gerald Ash <gash5107@yahoo.com>
To: Roland Bless <bless@tm.uka.de>, "nsis@ietf.org" <nsis@ietf.org>
In-Reply-To: <47FC7E58.4020709@tm.uka.de>
MIME-Version: 1.0
Message-ID: <919677.8993.qm@web63612.mail.re1.yahoo.com>
Subject: Re: [NSIS] QSPEC TMOD and packet header overhead
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-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="===============0651928948=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

--===============0651928948==
Content-Type: multipart/alternative; boundary="0-887504234-1207946601=:8993"
Content-Transfer-Encoding: 8bit

--0-887504234-1207946601=:8993
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi Roland,
   
  I think your examples are fine (although overhead for PPP header and perhaps MPLS labels might also be included).  
   
  However, as stated at the beginning of Section 5.2 (QSPEC Parameter Coding):

   "The references in the following sections point to the normative
   procedures for processing the  QSPEC parameters and
   sub-parameters."
   
  In the case of TMOD-1 and TMOD-2, the normative references are RFC 2210 and RFC 2215.  In particular, Section 3.1 in RFC 2210 and Section 3.6 in RFC 2215 give the necessary guidance on setting the token bucket parameters.
   
  IMO the QSPEC document isn't the place to give detailed examples of how to set these QSPEC parameters, or any other QSPEC parameters, beyond what is contained in the normative references.
   
  Jerry


Roland Bless <bless@tm.uka.de> wrote:
  Hi,

probably a dumb question, but Max Laier and I could not find any
guidance on this in the qspec draft:
I guess that the TMOD-1 r parameter in draft-ietf-nsis-qspec-20
specifies the number of bytes/s for IP packets, including any
IP headers. Now consider a mobile node that adds extra overhead
to its data packets due to the mobility headers etc. This could be
significant for VoIP packets. So in this case the applications has
to increase r depending on the packet rate and m must be increased,
too?

As another example: if the application communicates via IPv4
it has to specify for a normal PCM codec VoIP traffic:
r=50*(20+8+12+160)=10,000 bytes/s
[packet every 20ms,IP+UDP+RTP+payload], m=200 bytes,
b= 2000 bytes, p=very high (allowing a burst of 10 packets)
and when communication via IPv6
r=50*(40+8+12+160)=11,000 bytes/s, m=220 bytes,
b= 2200 bytes

Is this correct? Would it make sense to provide a little
guidance on this and an example in the QSPEC?

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


 __________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
--0-887504234-1207946601=:8993
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div>Hi Roland,</div>  <div>&nbsp;</div>  <div>I think your examples are fine (although overhead for PPP header and perhaps MPLS labels might also be included).&nbsp; </div>  <div>&nbsp;</div>  <div>However, as stated at the beginning of Section 5.2 (QSPEC Parameter Coding):<BR><BR>&nbsp;&nbsp; "The references in the following sections point to the normative<BR>&nbsp;&nbsp; procedures for processing the&nbsp; QSPEC parameters and<BR>&nbsp;&nbsp; sub-parameters."</div>  <div>&nbsp;</div>  <div>In the case of TMOD-1 and TMOD-2, the normative references are RFC 2210 and RFC 2215.&nbsp; In particular, Section 3.1 in RFC 2210 and Section 3.6 in RFC 2215 give the necessary guidance on setting the token bucket parameters.</div>  <div>&nbsp;</div>  <div>IMO the&nbsp;QSPEC document isn't the place to give detailed examples of how to set these QSPEC parameters, or any other QSPEC parameters,&nbsp;beyond what is contained in the normative references.</div>  <div>&nbsp;</div> 
 <div>Jerry<BR><BR><BR><B><I>Roland Bless &lt;bless@tm.uka.de&gt;</I></B> wrote:</div>  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hi,<BR><BR>probably a dumb question, but Max Laier and I could not find any<BR>guidance on this in the qspec draft:<BR>I guess that the TMOD-1 r parameter in draft-ietf-nsis-qspec-20<BR>specifies the number of bytes/s for IP packets, including any<BR>IP headers. Now consider a mobile node that adds extra overhead<BR>to its data packets due to the mobility headers etc. This could be<BR>significant for VoIP packets. So in this case the applications has<BR>to increase r depending on the packet rate and m must be increased,<BR>too?<BR><BR>As another example: if the application communicates via IPv4<BR>it has to specify for a normal PCM codec VoIP traffic:<BR>r=50*(20+8+12+160)=10,000 bytes/s<BR>[packet every 20ms,IP+UDP+RTP+payload], m=200 bytes,<BR>b= 2000 bytes, p=very high (allowing a
 burst of 10 packets)<BR>and when communication via IPv6<BR>r=50*(40+8+12+160)=11,000 bytes/s, m=220 bytes,<BR>b= 2200 bytes<BR><BR>Is this correct? Would it make sense to provide a little<BR>guidance on this and an example in the QSPEC?<BR><BR>Regards,<BR>Roland<BR>_______________________________________________<BR>nsis mailing list<BR>nsis@ietf.org<BR>https://www.ietf.org/mailman/listinfo/nsis<BR></BLOCKQUOTE><BR><p>&#32;__________________________________________________<br>Do You Yahoo!?<br>Tired of spam?  Yahoo! Mail has the best spam protection around <br>http://mail.yahoo.com 
--0-887504234-1207946601=:8993--

--===============0651928948==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0651928948==--


From nsis-bounces@ietf.org  Fri Apr 11 19:35:27 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 59B353A6865;
	Fri, 11 Apr 2008 19:35:27 -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 1D56B3A67CC
	for <nsis@core3.amsl.com>; Fri, 11 Apr 2008 19:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.422
X-Spam-Level: 
X-Spam-Status: No, score=-1.422 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_14=0.6,
	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 1mXr6tt38z8O for <nsis@core3.amsl.com>;
	Fri, 11 Apr 2008 19:35:25 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de
	[212.227.126.171])
	by core3.amsl.com (Postfix) with ESMTP id 0B5023A6B2A
	for <nsis@ietf.org>; Fri, 11 Apr 2008 19:35:12 -0700 (PDT)
Received: from vampire.homelinux.org (dslb-088-066-037-144.pools.arcor-ip.net
	[88.66.37.144])
	by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis)
	id 0MKwpI-1JkVaa1QbU-0001g9; Sat, 12 Apr 2008 04:35:36 +0200
Received: (qmail 78811 invoked from network); 12 Apr 2008 02:34:30 -0000
Received: from myhost.laiers.local (192.168.4.151)
	by mx.laiers.local with SMTP; 12 Apr 2008 02:34:30 -0000
From: Max Laier <max.laier@tm.uka.de>
Organization: FreeBSD
To: nsis@ietf.org
Date: Sat, 12 Apr 2008 04:32:39 +0200
User-Agent: KMail/1.9.9
References: <919677.8993.qm@web63612.mail.re1.yahoo.com>
In-Reply-To: <919677.8993.qm@web63612.mail.re1.yahoo.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200804120432.40206.max.laier@tm.uka.de>
X-Provags-ID: V01U2FsdGVkX1+OBz9RFmbbbGymJ8AFi/6MsZ0+yQMaLDZHobs
	W2RyLZq/Im+bjE6twrRRENvYliVIutrfU0c/sw1Ax6Q5k7HR/a
	F/+EhHl27GurxNLOQWfSw==
Cc: Roland Bless <bless@tm.uka.de>
Subject: Re: [NSIS] QSPEC TMOD and packet header overhead
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-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

On Friday 11 April 2008 22:43:21 Gerald Ash wrote:
> Hi Roland,
>
>   I think your examples are fine (although overhead for PPP header and
> perhaps MPLS labels might also be included).
>
>   However, as stated at the beginning of Section 5.2 (QSPEC Parameter
> Coding):
>
>    "The references in the following sections point to the normative
>    procedures for processing the  QSPEC parameters and
>    sub-parameters."
>
>   In the case of TMOD-1 and TMOD-2, the normative references are RFC
> 2210 and RFC 2215.  In particular, Section 3.1 in RFC 2210 and Section
> 3.6 in RFC 2215 give the necessary guidance on setting the token bucket
> parameters.
>
>   IMO the QSPEC document isn't the place to give detailed examples of
> how to set these QSPEC parameters, or any other QSPEC parameters,
> beyond what is contained in the normative references.

I found a paragraph in the tunnel draft at the end of 6.3.1:

|   If the end-to-end session SHOULD be bound to a tunnel session yet to
|   be created, Tentry assigns the tunnel flow ID, and constructs a
|   tunnel RESERVE' or QUERY' message, depending on whether the tunnel
|   signaling is sender initiated or receiver initiated.  The QSPEC in
|   this tunnel message MAY be different from the original QSPEC, taking
|   into consideration the tunnel overhead of the encapsulation of data
|   packets.  Tentry then associates the tunnel session with the end-to-
|   end session in the NSLP state and sends the tunnel message toward
|   Texit to start reserving resources over the tunnel.  At the same
|   time, Tentry appends a tunnel BOUND_SESSION_ID object to the end-to-
|   end RESERVE message and sends it through the tunnel interface.

Maybe we should expand that with a bit more detail and in the mobility 
draft as well?  I'm really having trouble as to how a middle box can 
calculate the new bandwidth from a per-packet overhead.

>   Jerry
>
>
> Roland Bless <bless@tm.uka.de> wrote:
>   Hi,
>
> probably a dumb question, but Max Laier and I could not find any
> guidance on this in the qspec draft:
> I guess that the TMOD-1 r parameter in draft-ietf-nsis-qspec-20
> specifies the number of bytes/s for IP packets, including any
> IP headers. Now consider a mobile node that adds extra overhead
> to its data packets due to the mobility headers etc. This could be
> significant for VoIP packets. So in this case the applications has
> to increase r depending on the packet rate and m must be increased,
> too?
>
> As another example: if the application communicates via IPv4
> it has to specify for a normal PCM codec VoIP traffic:
> r=50*(20+8+12+160)=10,000 bytes/s
> [packet every 20ms,IP+UDP+RTP+payload], m=200 bytes,
> b= 2000 bytes, p=very high (allowing a burst of 10 packets)
> and when communication via IPv6
> r=50*(40+8+12+160)=11,000 bytes/s, m=220 bytes,
> b= 2200 bytes
>
> Is this correct? Would it make sense to provide a little
> guidance on this and an example in the QSPEC?
>
> Regards,
> Roland
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www.ietf.org/mailman/listinfo/nsis
>
>
>  __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com



-- 
/"\  Best regards,                      | mlaier@freebsd.org
\ /  Max Laier                          | ICQ #67774661
 X   http://pf4freebsd.love2party.net/  | mlaier@EFnet
/ \  ASCII Ribbon Campaign              | Against HTML Mail and News
_______________________________________________
nsis mailing list
nsis@ietf.org
https://www.ietf.org/mailman/listinfo/nsis


From nsis-bounces@ietf.org  Sat Apr 12 00:02:06 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A587A28C119;
	Sat, 12 Apr 2008 00:02:06 -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 CB7AA28C119
	for <nsis@core3.amsl.com>; Sat, 12 Apr 2008 00:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.494
X-Spam-Level: 
X-Spam-Status: No, score=-0.494 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	HTML_MESSAGE=0.001, RDNS_NONE=0.1]
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 b-Wrr-EcW7kZ for <nsis@core3.amsl.com>;
	Sat, 12 Apr 2008 00:02:05 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [61.144.161.55])
	by core3.amsl.com (Postfix) with ESMTP id CF4D53A6A54
	for <nsis@ietf.org>; Sat, 12 Apr 2008 00:02:03 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JZ7000DJA7PVY@szxga03-in.huawei.com> for
	nsis@ietf.org; Sat, 12 Apr 2008 15:02:13 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JZ700JX6A7N54@szxga03-in.huawei.com> for
	nsis@ietf.org; Sat, 12 Apr 2008 15:02:13 +0800 (CST)
Received: from PRABHU1494 ([10.18.4.165])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JZ7006ULA7JYN@szxml03-in.huawei.com> for
	nsis@ietf.org; Sat, 12 Apr 2008 15:02:11 +0800 (CST)
Date: Sat, 12 Apr 2008 12:32:07 +0530
From: Prabhugouda <prabhu_b@huawei.com>
To: nsis@ietf.org
Message-id: <001a01c89c6b$1f3c7a30$a504120a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Office Outlook 11
Thread-index: Acicax60td2VQIapS9Cfw9naa5TJKg==
Subject: [NSIS] Unsubscribe
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: prabhu_b@huawei.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-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="===============1394255188=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1394255188==
Content-type: multipart/alternative;
 boundary="Boundary_(ID_C9JwroFBXOWHKN6bA1cBTQ)"

This is a multi-part message in MIME format.

--Boundary_(ID_C9JwroFBXOWHKN6bA1cBTQ)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

 

 

****************************************************************************
****************************
 This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
above. Any use of the information contained herein in any way (including,
but not limited to, total or partial disclosure, reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

 


--Boundary_(ID_C9JwroFBXOWHKN6bA1cBTQ)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimHei;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:KaiTi_GB2312;}
@font-face
	{font-family:"\@KaiTi_GB2312";}
@font-face
	{font-family:"\@SimHei";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:10.0pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:2.0gd;
	mso-para-margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";}
h1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:21.55pt;
	text-align:justify;
	text-indent:-21.55pt;
	page-break-after:avoid;
	mso-list:l10 level1 lfo35;
	font-size:16.0pt;
	font-family:Arial;}
h2
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:.4in;
	text-align:justify;
	text-indent:-.4in;
	page-break-after:avoid;
	mso-list:l10 level2 lfo35;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:normal;}
h3
	{margin-top:13.0pt;
	margin-right:0in;
	margin-bottom:13.0pt;
	margin-left:.5in;
	mso-para-margin-top:13.0pt;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:13.0pt;
	mso-para-margin-left:2.0gd;
	text-align:justify;
	text-indent:-.5in;
	line-height:173%;
	page-break-after:avoid;
	mso-list:l10 level3 lfo35;
	font-size:12.0pt;
	font-family:Arial;
	font-weight:normal;}
p.MsoHeader, li.MsoHeader, div.MsoHeader
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:justify;
	layout-grid-mode:char;
	font-size:9.0pt;
	font-family:Arial;}
p.MsoFooter, li.MsoFooter, div.MsoFooter
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.Table, li.Table, div.Table
	{margin-top:5.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	mso-para-margin-top:1.0gd;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:0in;
	mso-para-margin-bottom:.0001pt;
	text-align:center;
	text-indent:0in;
	mso-list:l7 level9 lfo5;
	font-size:9.0pt;
	font-family:Arial;}
p.TableText, li.TableText, div.TableText
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Arial;}
p.TableHeader, li.TableHeader, div.TableHeader
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:center;
	font-size:10.5pt;
	font-family:Arial;
	font-weight:bold;}
p.FigureStyle, li.FigureStyle, div.FigureStyle
	{margin-top:4.0pt;
	margin-right:0in;
	margin-bottom:4.0pt;
	margin-left:0in;
	text-align:center;
	line-height:150%;
	page-break-after:avoid;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";}
p.DocumentTitle, li.DocumentTitle, div.DocumentTitle
	{margin-top:15.0pt;
	margin-right:0in;
	margin-bottom:15.0pt;
	margin-left:0in;
	text-align:center;
	line-height:150%;
	text-autospace:none;
	font-size:18.0pt;
	font-family:Arial;}
p.NotesHeader, li.NotesHeader, div.NotesHeader
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:10.0pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:2.0gd;
	mso-para-margin-bottom:.0001pt;
	text-align:justify;
	line-height:150%;
	text-autospace:none;
	border:none;
	padding:0in;
	font-size:9.0pt;
	font-family:Arial;}
p.NotesText, li.NotesText, div.NotesText
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:10.0pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:2.0gd;
	mso-para-margin-bottom:.0001pt;
	text-align:justify;
	text-indent:.25in;
	line-height:150%;
	text-autospace:none;
	border:none;
	padding:0in;
	font-size:9.0pt;
	font-family:Arial;}
p.CompilingAdvice, li.CompilingAdvice, div.CompilingAdvice
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:10.0pt;
	margin-bottom:.0001pt;
	mso-para-margin-top:0in;
	mso-para-margin-right:0in;
	mso-para-margin-bottom:0in;
	mso-para-margin-left:2.0gd;
	mso-para-margin-bottom:.0001pt;
	line-height:150%;
	text-autospace:none;
	font-size:10.5pt;
	font-family:Arial;
	color:blue;
	font-style:italic;}
span.EmailStyle28
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
p.Figure, li.Figure, div.Figure
	{margin:0in;
	margin-bottom:.0001pt;
	text-align:center;
	text-indent:0in;
	line-height:150%;
	mso-list:l7 level8 lfo5;
	text-autospace:none;
	font-size:10.5pt;
	font-family:"Times New Roman";}
 /* Page Definitions */
 @page
	{mso-endnote-separator:url("cid:header.htm\@01C89C99.385E90B0") es;
	mso-endnote-continuation-separator:url("cid:header.htm\@01C89C99.385E90B0") ecs;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-footer:url("cid:header.htm\@01C89C99.385E90B0") f1;
	layout-grid:15.6pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:171800355;
	mso-list-template-ids:-1278163850;}
@list l0:level1
	{mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l0:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l0:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l0:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l0:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l0:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l0:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l0:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l0:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l1
	{mso-list-id:191647984;
	mso-list-template-ids:345692754;}
@list l1:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:\9644\5F55%1;
	mso-level-tab-stop:64.15pt;
	mso-level-number-position:left;
	margin-left:64.15pt;
	text-indent:-.3in;}
@list l1:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:71.35pt;
	mso-level-number-position:left;
	margin-left:71.35pt;
	text-indent:-.4in;}
@list l1:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:78.55pt;
	mso-level-number-position:left;
	margin-left:78.55pt;
	text-indent:-.5in;}
@list l1:level4
	{mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:89.35pt;
	text-indent:-34.0pt;}
@list l1:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:114.55pt;
	mso-level-number-position:left;
	margin-left:114.55pt;
	text-indent:-1.0in;}
@list l1:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:121.75pt;
	mso-level-number-position:left;
	margin-left:121.75pt;
	text-indent:-1.1in;}
@list l2
	{mso-list-id:541409008;
	mso-list-template-ids:-249166292;}
@list l2:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:\9644\5F55%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l2:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l2:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l2:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l2:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l2:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l2:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l2:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l2:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l3
	{mso-list-id:731736200;
	mso-list-template-ids:67698717;}
@list l3:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l3:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:57.25pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-28.35pt;}
@list l3:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:96.55pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-28.35pt;}
@list l3:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:153.8pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l3:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:193.05pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l3:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:232.3pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-56.7pt;}
@list l3:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:271.55pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l3:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:310.8pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l3:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:350.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l4
	{mso-list-id:818422186;
	mso-list-template-ids:1344984950;}
@list l4:level1
	{mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l4:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l4:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l4:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l4:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l4:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l4:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l4:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l4:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l5
	{mso-list-id:838886720;
	mso-list-template-ids:-819953982;}
@list l5:level1
	{mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;
	mso-ansi-font-size:18.0pt;
	mso-bidi-font-size:18.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;
	mso-ansi-font-size:15.0pt;
	mso-bidi-font-size:15.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;
	mso-ansi-font-size:12.0pt;
	mso-bidi-font-size:12.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l5:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l6
	{mso-list-id:942373150;
	mso-list-template-ids:67698717;}
@list l6:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l6:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:57.25pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-28.35pt;}
@list l6:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:96.55pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-28.35pt;}
@list l6:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:135.8pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l6:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:175.05pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l6:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:214.3pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-56.7pt;}
@list l6:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:253.55pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l6:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:292.8pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l6:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:332.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l7
	{mso-list-id:1123964682;
	mso-list-template-ids:548200814;}
@list l7:level1
	{mso-level-suffix:none;
	mso-level-text:"%1  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:0in;
	mso-ansi-font-size:18.0pt;
	mso-bidi-font-size:18.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level2
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:0in;
	mso-ansi-font-size:15.0pt;
	mso-bidi-font-size:15.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level3
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:0in;
	mso-ansi-font-size:12.0pt;
	mso-bidi-font-size:12.0pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level4
	{mso-level-suffix:none;
	mso-level-text:"%1\.%2\.%3\.%4  ";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:0in;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level5
	{mso-level-tab-stop:92.7pt;
	mso-level-number-position:left;
	margin-left:92.7pt;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level6
	{mso-level-text:"%6\)";
	mso-level-tab-stop:92.7pt;
	mso-level-number-position:left;
	margin-left:92.7pt;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level7
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:92.7pt;
	mso-level-number-position:left;
	margin-left:92.7pt;
	text-indent:-15.6pt;
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:Arial;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level8
	{mso-level-reset-level:level1;
	mso-level-style-link:Figure;
	mso-level-suffix:space;
	mso-level-text:Figure%8;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:.5in;
	text-indent:0in;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l7:level9
	{mso-level-reset-level:level1;
	mso-level-style-link:Table;
	mso-level-suffix:space;
	mso-level-text:Table%9;
	mso-level-tab-stop:none;
	mso-level-number-position:center;
	margin-left:.5in;
	text-indent:0in;
	mso-ansi-font-size:9.0pt;
	mso-bidi-font-size:9.0pt;
	font-family:Arial;
	mso-fareast-font-family:SimHei;
	mso-bidi-font-family:"Times New Roman";
	mso-ansi-font-weight:normal;
	mso-ansi-font-style:normal;}
@list l8
	{mso-list-id:1380013528;
	mso-list-template-ids:-1435872280;}
@list l8:level1
	{mso-level-number-format:none;
	mso-level-text:"\9644\5F55A ";
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l8:level2
	{mso-level-text:"A\.%2";
	mso-level-tab-stop:49.6pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-28.35pt;}
@list l8:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-28.35pt;}
@list l8:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:99.2pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l8:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:127.55pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l8:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:163.0pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-56.7pt;}
@list l8:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:191.35pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l8:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:219.7pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l8:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:255.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l9
	{mso-list-id:1425803385;
	mso-list-template-ids:67698717;}
@list l9:level1
	{mso-level-text:%1;
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l9:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:57.25pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-28.35pt;}
@list l9:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:96.55pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-28.35pt;}
@list l9:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:153.8pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l9:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:193.05pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l9:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:232.3pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-56.7pt;}
@list l9:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:271.55pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l9:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:310.8pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l9:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:350.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
@list l10
	{mso-list-id:1666475049;
	mso-list-template-ids:-28945502;}
@list l10:level1
	{mso-level-style-link:"Heading 1";
	mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l10:level2
	{mso-level-style-link:"Heading 2";
	mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l10:level3
	{mso-level-style-link:"Heading 3";
	mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l10:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l10:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l10:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l10:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l10:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l10:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l11
	{mso-list-id:1916042858;
	mso-list-template-ids:-648263936;}
@list l11:level1
	{mso-level-number-format:alpha-upper;
	mso-level-text:\9644\5F55%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;}
@list l11:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;}
@list l11:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;}
@list l11:level4
	{mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l11:level5
	{mso-level-text:%5\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l11:level6
	{mso-level-number-format:alpha-lower;
	mso-level-text:%6\FF09;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l11:level7
	{mso-level-number-format:roman-lower;
	mso-level-text:%7;
	mso-level-tab-stop:28.35pt;
	mso-level-number-position:left;
	margin-left:.65in;
	text-indent:-34.0pt;}
@list l11:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l11:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l12
	{mso-list-id:2114861838;
	mso-list-template-ids:-433129230;}
@list l12:level1
	{mso-level-number-format:none;
	mso-level-text:"\9644\5F55A ";
	mso-level-tab-stop:21.25pt;
	mso-level-number-position:left;
	margin-left:21.25pt;
	text-indent:-21.25pt;}
@list l12:level2
	{mso-level-text:"A\.%2";
	mso-level-tab-stop:49.6pt;
	mso-level-number-position:left;
	margin-left:49.6pt;
	text-indent:-28.35pt;}
@list l12:level3
	{mso-level-text:"%1A\.%2\.%3";
	mso-level-tab-stop:70.9pt;
	mso-level-number-position:left;
	margin-left:70.9pt;
	text-indent:-28.35pt;}
@list l12:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:99.2pt;
	mso-level-number-position:left;
	margin-left:99.2pt;
	text-indent:-35.4pt;}
@list l12:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:127.55pt;
	mso-level-number-position:left;
	margin-left:127.55pt;
	text-indent:-42.5pt;}
@list l12:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:163.0pt;
	mso-level-number-position:left;
	margin-left:163.0pt;
	text-indent:-56.7pt;}
@list l12:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:191.35pt;
	mso-level-number-position:left;
	margin-left:191.35pt;
	text-indent:-63.8pt;}
@list l12:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:219.7pt;
	mso-level-number-position:left;
	margin-left:219.7pt;
	text-indent:-70.9pt;}
@list l12:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:255.1pt;
	mso-level-number-position:left;
	margin-left:255.1pt;
	text-indent:-85.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="3074" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="2" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=EN-US link=blue vlink=purple style='text-justify-trim:punctuation'>

<div class=Section1 style='layout-grid:15.6pt'>

<p class=MsoNormal style='margin-left:21.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal style='margin-left:21.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal style='margin-left:21.0pt'><font size=2 face=Arial><span
style='font-size:10.0pt;line-height:150%;font-family:Arial'>********************************************************************************************************<br>
&nbsp;This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed above.
Any use of the information contained herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by
persons other than the intended recipient's) is prohibited. If you receive this
e-mail in error, please notify the sender by phone or email immediately and
delete it!</span></font><o:p></o:p></p>

<p class=MsoNormal style='margin-left:0in'><font size=2 face="Times New Roman"><span
style='font-size:10.5pt;line-height:150%'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--Boundary_(ID_C9JwroFBXOWHKN6bA1cBTQ)--

--===============1394255188==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1394255188==--


From nsis-bounces@ietf.org  Mon Apr 14 14:57:49 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B8A7C3A6966;
	Mon, 14 Apr 2008 14:57:49 -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 C6DEC3A69F9
	for <nsis@core3.amsl.com>; Mon, 14 Apr 2008 14:57:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.47
X-Spam-Level: 
X-Spam-Status: No, score=-4.47 tagged_above=-999 required=5 tests=[AWL=2.129, 
	BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 nFUMEmCaX1vF for <nsis@core3.amsl.com>;
	Mon, 14 Apr 2008 14:57:47 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 901C23A6D3A
	for <nsis@ietf.org>; Mon, 14 Apr 2008 14:57:47 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m3ELxHcB014725 for <nsis@ietf.org>; Mon, 14 Apr 2008 17:00:35 -0500
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 15 Apr 2008 00:56:57 +0300
Received: from daebe104.NOE.Nokia.com ([10.241.36.13]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Mon, 14 Apr 2008 16:56:47 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 14 Apr 2008 16:56:46 -0500
Message-ID: <19EBBEC503C3B5469070E0A6674A533A01497702@daebe104.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ISOC Fellowship to the IETF - seeking applicants for IETF 72 and
	IETF73
Thread-Index: AcieEnoyFYcmV9YLT5qrsHqmiTLwyAAZ+RZQ
From: <john.loughney@nokia.com>
To: <nsis@ietf.org>
X-OriginalArrivalTime: 14 Apr 2008 21:56:47.0160 (UTC)
	FILETIME=[6F5CA380:01C89E7A]
X-Nokia-AV: Clean
Subject: [NSIS] FW: ISOC Fellowship to the IETF - seeking applicants for
	IETF 72 and IETF73
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-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

For everyone's information.

----- Forwarded message from Mirjam Kuehne <mir@isoc.org> -----

From: Mirjam Kuehne <mir@isoc.org>
To: ietf@ietf.org
Date: Mon, 31 Mar 2008 15:18:05 +0200
Subject: ISOC Fellowship to the IETF - seeking applicants for IETF 72
and IETF 73

[I am sorry if you receive this more than once.]


Dear Colleagues,

The Internet Society announces that it is seeking applications for the
next round of the ISOC Fellowship to the IETF  program. The program
offers engineers from developing countries fellowships that fund the
cost of attending an Internet Engineering Task Force (IETF) meeting.

As you know, the IETF is the Internet's premier standards-making body,
responsible for the development of protocols used in IP-based networks.
IETF participants represent an international community of network
designers, operators, vendors, and researchers involved in the technical
operation of the Internet and the continuing evolution of Internet
architecture.

Fellowships will be awarded through a competitive application process.
The Internet Society is currently accepting fellowship applications for
the next two IETF meetings:

    * IETF 72 being held in Dublin, Ireland, 27 July - 1 August 2008
    * IETF 73 being held in Minneapolis, 16 - 21 November 2008

Up to five fellowships will be awarded for each IETF meeting.

Full details on the ISOC Fellowship to the IETF, including how to apply,
are located on the ISOC website at :

	http://www.isoc.org/educpillar/fellowship

Fellowship applications for both IETF meetings are due by 2 May 2008.

The Internet Society formally launched the ISOC Fellowship to the IETF
program in January 2007 after successfully piloting the program during
2006 at IETF 66 in Montreal and IETF 67 in San Diego. Fifteen
individuals from 12 countries have participated in the program since its
inception.

I encourage you to pass information about this program to individuals
involved in your regional operators' groups that have a keen interest in
the Internet standardisation activities of the IETF.  You also may
consider being a reference for the applicant.

If you have questions, please do not hesiate to contact Karen Rose
<rose@isoc.org> or Mirjam Kuehne <mir@isoc.org>.

Kind Regards,
Mirjam Kuehne
ISOC


----- End forwarded message -----
_______________________________________________
nsis mailing list
nsis@ietf.org
https://www.ietf.org/mailman/listinfo/nsis


From nsis-bounces@ietf.org  Wed Apr 16 08:30:49 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7716028C218;
	Wed, 16 Apr 2008 08:30:49 -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 D3FFA3A6ED6
	for <nsis@core3.amsl.com>; Wed, 16 Apr 2008 08:30:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.793
X-Spam-Level: 
X-Spam-Status: No, score=-0.793 tagged_above=-999 required=5 tests=[AWL=1.229, 
	BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 obCOJBsG8d7P for <nsis@core3.amsl.com>;
	Wed, 16 Apr 2008 08:30:44 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de
	[141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id C40543A6C7F
	for <nsis@ietf.org>; Wed, 16 Apr 2008 08:30:43 -0700 (PDT)
Received: from i72ms.tm.uni-karlsruhe.de ([141.3.70.5]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1Jm9bL-0001S5-L9; Wed, 16 Apr 2008 17:31:17 +0200
Received: from vorta.tm.uka.de (vorta.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:21b:fcff:fe96:fe02])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id A47452FC019;
	Wed, 16 Apr 2008 17:31:11 +0200 (CEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by vorta.tm.uka.de (Postfix) with ESMTP id C0A31101CC;
	Wed, 16 Apr 2008 17:32:03 +0200 (CEST)
Message-ID: <48061BF3.3090908@tm.uka.de>
Date: Wed, 16 Apr 2008 17:32:03 +0200
From: Roland Bless <bless@tm.uka.de>
Organization: Institute of Telematics, University of Karlsruhe
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: Gerald Ash <gash5107@yahoo.com>
References: <919677.8993.qm@web63612.mail.re1.yahoo.com>
In-Reply-To: <919677.8993.qm@web63612.mail.re1.yahoo.com>
X-Enigmail-Version: 0.95.0
Cc: "nsis@ietf.org" <nsis@ietf.org>
Subject: Re: [NSIS] QSPEC TMOD and packet header overhead
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-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

Hi Jerry,

Gerald Ash wrote:
> I think your examples are fine (although overhead for PPP header and
> perhaps MPLS labels might also be included). 

No I disagree here. This doesn't make sense as link level overhead
may change while the packets traverses the net (e.g. PPP header is
stripped of at the next hop) and the application is usually unaware
of any link level technology being used. The RMF is probably aware of
any link layer overhead and resources. RFC 2210 also says about [m]:
   This
   packet size includes the application data and all protocol headers at
   or above the IP level (IP, TCP, UDP, RTP, etc.). The size given does
   not include any link-level headers, because these headers will change
   as the packet crosses different portions of the internetwork.

> However, as stated at the beginning of Section 5.2 (QSPEC Parameter Coding):
> 
>    "The references in the following sections point to the normative
>    procedures for processing the  QSPEC parameters and
>    sub-parameters."
>  
> In the case of TMOD-1 and TMOD-2, the normative references are RFC 2210
> and RFC 2215.  In particular, Section 3.1 in RFC 2210 and Section 3.6 in
> RFC 2215 give the necessary guidance on setting the token bucket parameters.

Yes, they do, but actually there is no TMOD in RFC 2210. So even if the
match is somewhat obvious, it would be probably better to be more exact
and point to the SENDER_TSPEC definition in RFC 2210 or the
TOKEN_BUCKET_TSPEC definition in RFC 2215.

> IMO the QSPEC document isn't the place to give detailed examples of how
> to set these QSPEC parameters, or any other QSPEC parameters, beyond
> what is contained in the normative references.

IMHO, an example in the appendix would be nice.
Shouldn't we copy the missing text from RFC 2210 or RFC 2215 since the
current description is incomplete without those RFCs?

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


From nsis-bounces@ietf.org  Thu Apr 17 04:03:59 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 339D128C531;
	Thu, 17 Apr 2008 04:03:59 -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 A832128C48B;
	Thu, 17 Apr 2008 04:03:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.171
X-Spam-Level: 
X-Spam-Status: No, score=-6.171 tagged_above=-999 required=5 tests=[AWL=0.078, 
	BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 JZF37w3X1kWS; Thu, 17 Apr 2008 04:03:56 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 2BA433A6987;
	Thu, 17 Apr 2008 04:03:56 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	0F06D20F38; Thu, 17 Apr 2008 13:02:18 +0200 (CEST)
X-AuditID: c1b4fb3c-ad89abb00000193b-95-48072e3a4aa9
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	00AB020F36; Thu, 17 Apr 2008 13:02:18 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 17 Apr 2008 13:02:17 +0200
Received: from [127.0.0.1] ([147.214.183.239]) by esealmw128.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 17 Apr 2008 13:02:17 +0200
Message-ID: <48072E38.6010601@ericsson.com>
Date: Thu, 17 Apr 2008 13:02:16 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: NSIS <nsis@ietf.org>
X-Enigmail-Version: 0.95.6
X-OriginalArrivalTime: 17 Apr 2008 11:02:17.0518 (UTC)
	FILETIME=[80120CE0:01C8A07A]
X-Brightmail-Tracker: AAAAAA==
Cc: TSV Area <tsv-area@ietf.org>
Subject: [NSIS] Looking for new WG chair for NSIS
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-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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi,

John Loughney will step down as WG chair for NSIS. Thus we are looking =

for a replacement. If you are interested in becoming WG chair for NSIS =

together with Martin Stiemerling please send me a notification. Any =

candidate should send his or her notice no later then the 11th of May.

If you have any question about the position don't hesitate to send them =

to me or Martin.

Best Regards

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
F=E4r=F6gatan 6                | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

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


From nsis-bounces@ietf.org  Thu Apr 17 05:46:05 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A3D773A6A34;
	Thu, 17 Apr 2008 05:46:05 -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 4A7173A6898
	for <nsis@core3.amsl.com>; Thu, 17 Apr 2008 05:46:05 -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]
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 Y55ypNAU73eZ for <nsis@core3.amsl.com>;
	Thu, 17 Apr 2008 05:46:01 -0700 (PDT)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id E3F6E3A6A24
	for <nsis@ietf.org>; Thu, 17 Apr 2008 05:46:00 -0700 (PDT)
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id DD9B02C0012A7
	for <nsis@ietf.org>; Thu, 17 Apr 2008 14:46:28 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1])
	by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id oEU-IhVeKnbR for <nsis@ietf.org>;
	Thu, 17 Apr 2008 14:46:28 +0200 (CEST)
Received: from eris.office (eris.office [192.168.24.5])
	by smtp0.neclab.eu (Postfix) with ESMTP id C36C42C0012A5
	for <nsis@ietf.org>; Thu, 17 Apr 2008 14:46:23 +0200 (CEST)
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 17 Apr 2008 14:46:33 +0200
Message-ID: <45EDF1C5D301ED41A339796A9F979F7209A253@eris.office>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Chair write-up of: "NSLP for Quality-of-Service Signaling"
Thread-Index: AcigiMqpTzOwa0UiSlC0tOBqYhYTLwAACfTw
From: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>
To: "nsis" <nsis@ietf.org>
Subject: [NSIS] FW: Chair write-up of: "NSLP for Quality-of-Service
	Signaling"
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-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

FYI: John and I have sent this out to our ADs. 

  Martin

stiemerling@nw.neclab.eu   <== NEW ADDRESS

NEC Laboratories Europe - Network Research Division
NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England 2832014  

> -----Original Message-----
> From: Martin Stiemerling [mailto:Stiemerling@nw.neclab.eu] 
> Sent: Thursday, April 17, 2008 2:45 PM
> To: Magnus Westerlund
> Cc: Lars Eggert; nsis-chairs@tools.ietf.org; Hannes Tschofenig
> Subject: Chair write-up of: "NSLP for Quality-of-Service Signaling"
> 
> The draft "NSLP for Quality-of-Service Signaling" has been 
> reviewed by the NSIS WG. 
> 
> There was a working group last call that ended on June 25, 2007. 
> Additionally to this, the draft has been implemented by 
> several parties. The implementations are code independent and 
> have been tested for interoperability at several interops. 
> The list of currently avaialable QoS NSLP implementations is here:
> http://www.stiemerling.org/blog/?page_id=3
> 
> 
> The I-D is now ready for AD and IESG review. Below are 
> details about the I-D:
> 
> Title:  NSLP for Quality-of-Service Signaling
> I-D: 
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-qos-nslp-16.txt
> 
> Status: Proposed Standard
> 
> Response to template:
> 
> 1) Have the chairs personally reviewed this version of the ID and do
>    they believe this ID is sufficiently baked to forward to the IESG
>    for publication? 
> 
> Yes, it is.
> 
> 
> 2) Has the document had adequate review from both key WG members and
>    key non-WG members? Do you have any concerns about the depth or
>    breadth of the reviews that have been performed?
> 
> Yes. The ID has passed working group last calls, has had good 
> reviews during the process, and good feedback by implementors.
> 
> 3) Do you have concerns that the document needs more review from a
>    particular (broader) perspective (e.g., security, operational
>    complexity, etc.)? 
> 
> No concerns.  The document has undergone extensive Working 
> Group review, and has several (at least 3) interoperable 
> implementations.
> 
> 4) Do you have any specific concerns/issues with this document that
>    you believe the ADs and/or IESG should be aware of? For example,
>    perhaps you are uncomfortable with certain parts of the document,
>    or whether there really is a need for it, etc., but at the same
>    time these issues have been discussed in the WG and the WG has
>    indicated it wishes to advance the document anyway.
> 
> No
> 
> 5) How solid is the WG consensus behind this document?  Does it
>    represent the strong concurrence of a few individuals, with others
>    being silent, or does the WG as a whole understand and agree with
>    it?
> 
> There is a strong consensus in the WG supporting this work, 
> at this point there is no disenting voices about the protocol 
> in the WG.
> 
> 6) Has anyone threatened an appeal or otherwise indicated extreme
>    discontent?  If so, please summarize what are they upset about.
> 
> No. 
> 
> 7) Have the chairs verified that the document adheres to _all_ of the
>    ID nits?  (see http://www.ietf.org/ID-nits.html).
> 
> Yes.
> 
> 8) Does the document a) split references into normative/informative,
>    and b) are there normative references to IDs, where the IDs are not
>    also ready for advancement or are otherwise in an unclear state?
>    (Note: the RFC editor will not publish an RFC with normative
>    references to IDs, it will delay publication until all such IDs are
>    also ready for publication as RFCs.)
> 
> The document does split references into normative and 
> informative ones. 
> 
> 9) For Standards Track and BCP documents, the IESG approval
>    announcement includes a writeup section with the following
>    sections:
> 
>    - Technical Summary
> 
> This draft proposes an NSIS Signaling Layer Protocol (NSLP) 
> for signaling QoS reservations in the Internet. The NSLP is 
> the second layer in the two-layer signaling model defined in 
> RFC 4080. Together with GIST (draft-ietf-nsis-ntlp), it 
> provides functionality similar to RSVP and extends it. The 
> QoS NSLP is independent of the used QoS specification or 
> architecture and provides support for different reservation models.
> 
> 
>    - Working Group Summary
> 
> There have been several WGLC on the document, plus several 
> pre-WGLCs on the document. The editors have gotten extensive 
> feedback from implementors and have clarified text based upon 
> the feedback.  There are 3 or more independent 
> implementations of the QoS NSLP, and there were multiple 
> interop events in the past.
> 
>    - Protocol Quality
> 
> This document was reviewed by the working group chair as well 
> as the WG. We feel that this document is ready, and 
> implementors feel that the specification is implementable.
> 
> 
> 
> 
> 
> stiemerling@nw.neclab.eu
> 
> NEC Laboratories Europe - Network Research Division NEC 
> Europe Limited | Registered Office: NEC House, 1 Victoria 
> Road, London W3 6BL | Registered in England 2832014 
> 
_______________________________________________
nsis mailing list
nsis@ietf.org
https://www.ietf.org/mailman/listinfo/nsis


From nsis-bounces@ietf.org  Fri Apr 18 12:58:27 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 24DE03A6BFE;
	Fri, 18 Apr 2008 12:58:27 -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 B3B493A67F9
	for <nsis@core3.amsl.com>; Fri, 18 Apr 2008 12:58:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.563
X-Spam-Level: 
X-Spam-Status: No, score=0.563 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, 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 sME16GY1ctN6 for <nsis@core3.amsl.com>;
	Fri, 18 Apr 2008 12:58:24 -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 C6B903A6CB0
	for <nsis@ietf.org>; Fri, 18 Apr 2008 12:58:23 -0700 (PDT)
Received: (qmail 15444 invoked by uid 60001); 18 Apr 2008 19:58:25 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=aNTleEOPlPeO3BSBtdzcWHKZqFFyzHXEuw7AaIU3me4cEjP7owoXzTntLLEbygaFjw0AAys8hVokQGliefYmvudbqFT+Xy0a9HN6dvZgfLTEADMiSjPLtjNJEkqi2bKTQiQfJ2w2y/WWeFJ1ACkEGVc2ZwAN7JCeRvauF5LbRU0=;
X-YMail-OSG: Pv0iWKUVM1mm7m9W8i0zQdJBrMOfrnR7qNTWqOThkkzUqv8goxb2yTM9l81VvIqsKhUqcVNF3wMWIV5kjpyvEWfS6dosgyzD_4sNSadcKI5XG1Ck8An2Y14B9Iw-
Received: from [76.19.255.157] by web63608.mail.re1.yahoo.com via HTTP;
	Fri, 18 Apr 2008 12:58:24 PDT
Date: Fri, 18 Apr 2008 12:58:24 -0700 (PDT)
From: Gerald Ash <gash5107@yahoo.com>
To: Roland Bless <bless@tm.uka.de>, "nsis@ietf.org" <nsis@ietf.org>
In-Reply-To: <48061BF3.3090908@tm.uka.de>
MIME-Version: 1.0
Message-ID: <201376.15432.qm@web63608.mail.re1.yahoo.com>
Subject: Re: [NSIS] QSPEC TMOD and packet header overhead
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-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="===============1319280713=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

--===============1319280713==
Content-Type: multipart/alternative; boundary="0-940978368-1208548704=:15432"
Content-Transfer-Encoding: 8bit

--0-940978368-1208548704=:15432
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi Roland,
   
  See comments below.
   
>> However, as stated at the beginning of Section 5.2 (QSPEC Parameter
>> Coding):
>> 
>>    "The references in the following sections point to the normative
>>    procedures for processing the  QSPEC parameters and
>>    sub-parameters."
>>  
>> In the case of TMOD-1 and TMOD-2, the normative references are RFC
>> 2210 and RFC 2215.  In particular, Section 3.1 in RFC 2210 and
  >> Section 3.6 in RFC 2215 give the necessary guidance on setting the
  >> token bucket parameters.
 
> Yes, they do, but actually there is no TMOD in RFC 2210. So even if the
> match is somewhat obvious, it would be probably better to be more exact
> and point to the SENDER_TSPEC definition in RFC 2210 or the
> TOKEN_BUCKET_TSPEC definition in RFC 2215.
   
  Yes I agree that the match between TMOD and TSPEC is pretty obvious.  However it can be made even more explicit with specific references to TSPEC (Section 3.1 in RFC 2210 and Section 3.6 in RFC 2215), as you suggest.
  
>> IMO the QSPEC document isn't the place to give detailed examples of
>> how to set these QSPEC parameters, or any other QSPEC parameters,
  >> beyond what is contained in the normative references.

> IMHO, an example in the appendix would be nice.
   
  Well, the token bucket algorithm has been around for a long time (even before RSVP of course) so there are ample examples and implementations of its use.  IMO it would not be appropriate (and perhaps a bit odd) for the QSPEC to include a tutorial on token bucket.
   
  While RFCs 2210 and 2215 are the applicable normative description of the TSPEC/TMOD parameters, there are no numerical examples there of its use.  So perhaps we could include a reference or 2 to some examples of token bucket implementation.  Maybe that would help?  A couple of references I'm aware of with numerical examples of token bucket implementation include
   
  http://www.amazon.com/Computer-Networks-Approach-Kaufmann-Networking/dp/0123705487/
   
  http://www.amazon.com/Traffic-Engineering-Optimization-Integrated-Networks/dp/0123706254/
   
  Perhaps you could suggest an appropriate reference as well?
   
  OTOH, I couldn't find any RFCs with numerical examples of TSPEC/TMOD implementation (do you know of any?), so that might be a justification to include one or two examples in QSPEC (such as the ones you constructed).  
   
  Does anyone else have a comment on this?
  
> Shouldn't we copy the missing text from RFC 2210 or RFC 2215 since the
> current description is incomplete without those RFCs?
   
  I'm not sure what 'missing text' you suggest to copy.  Once again, the intent of the statement at the beginning of QSPEC Section 5.2 ("The references in the following sections point to the normative procedures for processing the QSPEC parameters and sub-parameters.") is intended to avoid copying normative text into the QSPEC document for each QSPEC parameter.  More generally, that is also the purpose of a normative reference in any RFC.
   
  Do you want to suggest specific text to bring into QSPEC?
   
  Regards,
  Jerry

       
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.
--0-940978368-1208548704=:15432
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div>Hi Roland,</div>  <div>&nbsp;</div>  <div>See comments below.</div>  <div>&nbsp;<BR>&gt;&gt; However, as stated at the beginning of Section 5.2 (QSPEC Parameter<BR>&gt;&gt; Coding):<BR>&gt;&gt; <BR>&gt;&gt;&nbsp;&nbsp;&nbsp; "The references in the following sections point to the normative<BR>&gt;&gt;&nbsp;&nbsp;&nbsp; procedures for processing the&nbsp; QSPEC parameters and<BR>&gt;&gt;&nbsp;&nbsp;&nbsp; sub-parameters."<BR>&gt;&gt;&nbsp; <BR>&gt;&gt; In the case of TMOD-1 and TMOD-2, the normative references are RFC<BR>&gt;&gt;&nbsp;2210 and RFC 2215.&nbsp; In particular, Section 3.1 in RFC 2210 and</div>  <div>&gt;&gt;&nbsp;Section 3.6&nbsp;in RFC 2215 give the necessary guidance on setting the</div>  <div>&gt;&gt;&nbsp;token bucket&nbsp;parameters.<BR>&nbsp;<BR>&gt; Yes, they do, but actually there is no TMOD in RFC 2210. So even if the<BR>&gt; match is somewhat obvious, it would be probably better to be more exact<BR>&gt; and point to the SENDER_TSPEC definition in
 RFC 2210 or the<BR>&gt; TOKEN_BUCKET_TSPEC definition in RFC 2215.</div>  <div>&nbsp;</div>  <div>Yes I agree that the match between TMOD and TSPEC&nbsp;is&nbsp;pretty obvious.&nbsp; However it can be made even more explicit with specific references to TSPEC (Section 3.1 in RFC 2210 and&nbsp;Section 3.6 in&nbsp;RFC 2215),&nbsp;as you suggest.</div>  <div><BR>&gt;&gt; IMO the QSPEC document isn't the place to give detailed examples of<BR>&gt;&gt;&nbsp;how to set these QSPEC parameters, or any other QSPEC parameters,</div>  <div>&gt;&gt;&nbsp;beyond what is contained in the normative references.<BR><BR>&gt; IMHO, an example in the appendix would be nice.</div>  <div>&nbsp;</div>  <DIV>Well, the token bucket algorithm has been around for a long time (even before RSVP of course) so there are ample examples and implementations of its use.&nbsp; IMO it would not be appropriate (and perhaps&nbsp;a bit&nbsp;odd) for the QSPEC to&nbsp;include a&nbsp;tutorial on&nbsp;token
 bucket.</DIV>  <DIV>&nbsp;</DIV>  <DIV>While&nbsp;RFCs 2210 and 2215 are&nbsp;the applicable normative description of the TSPEC/TMOD parameters, there are no numerical examples there of its use.&nbsp; So perhaps we could include&nbsp;a&nbsp;reference or 2 to some examples of token bucket implementation.&nbsp;&nbsp;Maybe that would help?&nbsp; A couple of references I'm aware of with&nbsp;numerical examples&nbsp;of token bucket implementation include</DIV>  <DIV>&nbsp;</DIV>  <DIV><A href="http://www.amazon.com/Computer-Networks-Approach-Kaufmann-Networking/dp/0123705487/" target=_blank rel=nofollow><SPAN class=yshortcuts id=lw_1208547497_0><FONT color=#003399>http://www.amazon.com/Computer-Networks-Approach-Kaufmann-Networking/dp/0123705487/</FONT></SPAN></A></DIV>  <DIV><FONT color=#003399></FONT>&nbsp;</DIV>  <DIV><A href="http://www.amazon.com/Traffic-Engineering-Optimization-Integrated-Networks/dp/0123706254/" target=_blank rel=nofollow><SPAN class=yshortcuts
 id=lw_1208547497_1><FONT color=#003399>http://www.amazon.com/Traffic-Engineering-Optimization-Integrated-Networks/dp/0123706254/</FONT></SPAN></A></DIV>  <DIV><FONT color=#003399></FONT>&nbsp;</DIV>  <DIV>Perhaps you could suggest an appropriate reference as well?</DIV>  <DIV>&nbsp;</DIV>  <DIV>OTOH, I couldn't find any RFCs with numerical examples of TSPEC/TMOD implementation&nbsp;(do you know of any?), so that might be a&nbsp;justification to include one or two examples in QSPEC (such as the ones you constructed).&nbsp; </DIV>  <DIV>&nbsp;</DIV>  <DIV>Does anyone else have a comment on this?</DIV>  <div><BR>&gt; Shouldn't we copy the missing text from RFC 2210 or RFC 2215 since the<BR>&gt; current description is incomplete without those RFCs?</div>  <div>&nbsp;</div>  <div>I'm not sure what 'missing text' you suggest to copy.&nbsp; Once again, the intent of the&nbsp;statement at the beginning of QSPEC Section 5.2 ("The references in the following sections point to the
 normative procedures for processing the QSPEC parameters and sub-parameters.") is intended to avoid copying normative text into the QSPEC document for each QSPEC parameter.&nbsp; More generally, that is also the purpose of a normative reference in any RFC.</div>  <div>&nbsp;</div>  <div>Do you want to suggest specific text to bring into QSPEC?</div>  <div>&nbsp;</div>  <div>Regards,</div>  <div>Jerry</div><p>&#32;

      <hr size=1>Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile. <a href="http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ "> Try it now.</a>
--0-940978368-1208548704=:15432--

--===============1319280713==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1319280713==--


From nsis-bounces@ietf.org  Mon Apr 21 08:32:34 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5FD353A6F05;
	Mon, 21 Apr 2008 08:32:34 -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 6AA733A6BEB
	for <nsis@core3.amsl.com>; Mon, 21 Apr 2008 08:32:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.651
X-Spam-Level: 
X-Spam-Status: No, score=0.651 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3]
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 hcqpZzO2DEcK for <nsis@core3.amsl.com>;
	Mon, 21 Apr 2008 08:32:32 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de
	[141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id CF5213A6950
	for <nsis@ietf.org>; Mon, 21 Apr 2008 08:32:31 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps id 1Jny0P-0005dU-B3
	for <nsis@ietf.org>; Mon, 21 Apr 2008 17:32:36 +0200
Received: from i72mn03.tm.uni-karlsruhe.de ([141.3.71.33])
	by irams1.ira.uni-karlsruhe.de with esmtpsa for <nsis@ietf.org>
	id 1Jny0P-0003Gm-Kd; Mon, 21 Apr 2008 17:32:33 +0200
Message-ID: <480CB3B5.9030607@tm.uka.de>
Date: Mon, 21 Apr 2008 17:33:09 +0200
From: =?ISO-8859-15?Q?Martin_R=F6hricht?= <roehricht@tm.uka.de>
User-Agent: Thunderbird 2.0.0.12 (X11/20080227)
MIME-Version: 1.0
To: NSIS <nsis@ietf.org>
Subject: [NSIS] NSLP-RMF API Question
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-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

Hi,

Appendix A.1 "Triggers from QOS-NSLP towards RMF" of the current NSLP 
draft lists GIST_API_triggers which are meant to be used by the 
sendrmf() function as one of its arguments.
I was wondering if this is correct or just more of a copy-and-paste-like 
error since these triggers represent attributes that are provided by 
GIST to QoS-NSLP via the GIST API which is not appropriate in this 
context, imho.

Best regards,
Martin
_______________________________________________
nsis mailing list
nsis@ietf.org
https://www.ietf.org/mailman/listinfo/nsis


From nsis-bounces@ietf.org  Tue Apr 22 09:18:17 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6AC1C3A67B3;
	Tue, 22 Apr 2008 09:18:17 -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 B152E3A6E0D
	for <nsis@core3.amsl.com>; Tue, 22 Apr 2008 09:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.178
X-Spam-Level: *
X-Spam-Status: No, score=1.178 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HELO_EQ_DE=0.35, J_CHICKENPOX_23=0.6,
	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 Fv7bmb9fe9tp for <nsis@core3.amsl.com>;
	Tue, 22 Apr 2008 09:18:14 -0700 (PDT)
Received: from mailer.gwdg.de (mailer.gwdg.de [134.76.10.26])
	by core3.amsl.com (Postfix) with ESMTP id 70A8B3A67AE
	for <nsis@ietf.org>; Tue, 22 Apr 2008 09:18:14 -0700 (PDT)
Received: from s4.ifi.informatik.uni-goettingen.de ([134.76.81.226])
	by mailer.gwdg.de with esmtp (Exim 4.69)
	(envelope-from <bschloer@cs.uni-goettingen.de>)
	id 1JoLCE-0002fV-Pv; Tue, 22 Apr 2008 18:18:18 +0200
Received: from [172.22.99.38] (ltbschloer1.tmg.loc [172.22.99.38])
	by smtp.stud.informatik.uni-goettingen.de (Postfix) with ESMTP id
	759D05BA98; Tue, 22 Apr 2008 18:18:18 +0200 (CEST)
Message-ID: <480E0F9E.3080208@cs.uni-goettingen.de>
Date: Tue, 22 Apr 2008 18:17:34 +0200
From: Bernd Schloer <bschloer@cs.uni-goettingen.de>
User-Agent: Thunderbird 1.5.0.7 (X11/20061008)
MIME-Version: 1.0
To: Gerald Ash <gash5107@yahoo.com>
References: <201376.15432.qm@web63608.mail.re1.yahoo.com>
In-Reply-To: <201376.15432.qm@web63608.mail.re1.yahoo.com>
X-Virus-Scanned: (clean) by exiscan+sophie
Cc: Roland Bless <bless@tm.uka.de>, "nsis@ietf.org" <nsis@ietf.org>
Subject: Re: [NSIS] QSPEC TMOD and packet header overhead
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-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

Hi Jerry,

based on Roland's work I have written a numerical example how
the TMOD parameter could be used. Is this of interest for the QSPEC
draft to include?

Best regards,
Bernd

An example VoIP application that uses RTP [RFC 1889] and the
G.711 Codec [ITU-T Rec. G.711] the TMOD-1 parameter could be
set as follows:

In the simplest case the Minimum Policed Unit m is the sum of the
IP-, UDP- and RTP- headers + payload. The IP header in the IPv4
case has a size of 20 bytes (40 bytes if IPv6 is used). The UDP
header has a size of 8 bytes and RTP uses a 12 byte header. The
G.711 Codec specifies a bandwidth of 64 kbit/s (8000 bytes/s).
Assuming RTP transmits voice datagrams every 20ms, the payload
for one datagram is 8000 bytes/s * 0.02 s = 160 bytes.

IPv4+UDP+RTP+payload: m=20+8+12+160 bytes = 200 bytes
IPv6+UDP+RTP+payload: m=40+8+12+160 bytes = 220 bytes

The Rate r specifies the amount of bytes per second. 50 datagrams
are sent per second.

IPv4: r = 50 1/s * m = 10,000 bytes/s
IPv6: r = 50 1/s * m = 11,000 bytes/s

The bucket size b specifies the maximum burst. In this example a
burst of 10 packets is used.

IPv4: b = 10 * m = 2000 bytes
IPv6: b = 10 * m = 2200 bytes

A number of extra headers (e.g. for encapsulation) may be included
into the datagram. A non exhaustive list is given below. For
additional headers m, r and b have to be set accordingly.

Protocol                   Header Size
--------------------------+-----------
GRE [RFC 1701]            | 8 bytes
GREIP4 [RFC 1702]         | 4-8 bytes
IP4INIP4 [RFC 2003]       | 20 bytes
MINENC [RFC 2004]         | 8-12 bytes
IP6GEN [RFC 2473]         | 40 bytes
IP6INIP4 [RFC 4213]       | 20 bytes
IPSec [RFC 4301,RFC 4303] | variable
--------------------------+-----------




Gerald Ash wrote:
> Hi Roland,
>    
>   See comments below.
>    
>>> However, as stated at the beginning of Section 5.2 (QSPEC Parameter
>>> Coding):
>>>
>>>    "The references in the following sections point to the normative
>>>    procedures for processing the  QSPEC parameters and
>>>    sub-parameters."
>>>  
>>> In the case of TMOD-1 and TMOD-2, the normative references are RFC
>>> 2210 and RFC 2215.  In particular, Section 3.1 in RFC 2210 and
>   >> Section 3.6 in RFC 2215 give the necessary guidance on setting the
>   >> token bucket parameters.
>  
>> Yes, they do, but actually there is no TMOD in RFC 2210. So even if the
>> match is somewhat obvious, it would be probably better to be more exact
>> and point to the SENDER_TSPEC definition in RFC 2210 or the
>> TOKEN_BUCKET_TSPEC definition in RFC 2215.
>    
>   Yes I agree that the match between TMOD and TSPEC is pretty obvious.  However it can be made even more explicit with specific references to TSPEC (Section 3.1 in RFC 2210 and Section 3.6 in RFC 2215), as you suggest.
>   
>>> IMO the QSPEC document isn't the place to give detailed examples of
>>> how to set these QSPEC parameters, or any other QSPEC parameters,
>   >> beyond what is contained in the normative references.
> 
>> IMHO, an example in the appendix would be nice.
>    
>   Well, the token bucket algorithm has been around for a long time (even before RSVP of course) so there are ample examples and implementations of its use.  IMO it would not be appropriate (and perhaps a bit odd) for the QSPEC to include a tutorial on token bucket.
>    
>   While RFCs 2210 and 2215 are the applicable normative description of the TSPEC/TMOD parameters, there are no numerical examples there of its use.  So perhaps we could include a reference or 2 to some examples of token bucket implementation.  Maybe that would help?  A couple of references I'm aware of with numerical examples of token bucket implementation include
>    
>   http://www.amazon.com/Computer-Networks-Approach-Kaufmann-Networking/dp/0123705487/
>    
>   http://www.amazon.com/Traffic-Engineering-Optimization-Integrated-Networks/dp/0123706254/
>    
>   Perhaps you could suggest an appropriate reference as well?
>    
>   OTOH, I couldn't find any RFCs with numerical examples of TSPEC/TMOD implementation (do you know of any?), so that might be a justification to include one or two examples in QSPEC (such as the ones you constructed).  
>    
>   Does anyone else have a comment on this?
>   
>> Shouldn't we copy the missing text from RFC 2210 or RFC 2215 since the
>> current description is incomplete without those RFCs?
>    
>   I'm not sure what 'missing text' you suggest to copy.  Once again, the intent of the statement at the beginning of QSPEC Section 5.2 ("The references in the following sections point to the normative procedures for processing the QSPEC parameters and sub-parameters.") is intended to avoid copying normative text into the QSPEC document for each QSPEC parameter.  More generally, that is also the purpose of a normative reference in any RFC.
>    
>   Do you want to suggest specific text to bring into QSPEC?
>    
>   Regards,
>   Jerry
> 
>        
> ---------------------------------
> Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www.ietf.org/mailman/listinfo/nsis
_______________________________________________
nsis mailing list
nsis@ietf.org
https://www.ietf.org/mailman/listinfo/nsis


From nsis-bounces@ietf.org  Tue Apr 22 10:39:23 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7887A3A6EA1;
	Tue, 22 Apr 2008 10:39:23 -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 3A3873A6E9D
	for <nsis@core3.amsl.com>; Tue, 22 Apr 2008 10:39:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.437
X-Spam-Level: 
X-Spam-Status: No, score=-0.437 tagged_above=-999 required=5 tests=[AWL=1.000, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334,
	J_CHICKENPOX_23=0.6, 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 vMdG4rQV+Tec for <nsis@core3.amsl.com>;
	Tue, 22 Apr 2008 10:39:20 -0700 (PDT)
Received: from web63615.mail.re1.yahoo.com (web63615.mail.re1.yahoo.com
	[69.147.97.85]) by core3.amsl.com (Postfix) with SMTP id 845CD3A6FB9
	for <nsis@ietf.org>; Tue, 22 Apr 2008 10:36:26 -0700 (PDT)
Received: (qmail 94005 invoked by uid 60001); 22 Apr 2008 17:36:32 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=gGWXgvKCXPUL1zfq9IIGqyxSD59fZKv1IPlVlgxbQclpIY1YneCRMCvBeawDY5Xe1Bj2CujztfBCMvVEOKDVHQbhBNRw4eeC6bcnE1dU1MdnhD1EcBNopnu+rerCYB0NjEmI5lRCDd2V7JK15dpZIGRe60Z33L2k8SnvGThnA54=;
X-YMail-OSG: pvO36IUVM1mfO3EtOv_L_h4Y1Tbg05EysVYuJx5bAGaU6fNRn9kz3C0V9p9ikev.qEXmJ8zf33m8HL50VlnfuJDU5ilo6RkuWY0uXIVecMIqM.UNeu6Ad0.q8FQ-
Received: from [76.19.255.157] by web63615.mail.re1.yahoo.com via HTTP;
	Tue, 22 Apr 2008 10:36:32 PDT
Date: Tue, 22 Apr 2008 10:36:32 -0700 (PDT)
From: Gerald Ash <gash5107@yahoo.com>
To: Bernd Schloer <bschloer@cs.uni-goettingen.de>
In-Reply-To: <480E0F9E.3080208@cs.uni-goettingen.de>
MIME-Version: 1.0
Message-ID: <209394.88193.qm@web63615.mail.re1.yahoo.com>
Cc: "nsis@ietf.org" <nsis@ietf.org>, Roland Bless <bless@tm.uka.de>
Subject: Re: [NSIS] QSPEC TMOD and packet header overhead
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-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="===============1479709601=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

--===============1479709601==
Content-Type: multipart/alternative; boundary="0-255624357-1208885792=:88193"
Content-Transfer-Encoding: 8bit

--0-255624357-1208885792=:88193
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi Bernd,
   
  The example and text look good, thanks!
   
  I agree that it would be worthwhile to include this as an appendix/example in the QSPEC (after all, you and Roland did all the work :-).
   
  Thanks again,
  Regards,
  Jerry


Bernd Schloer <bschloer@cs.uni-goettingen.de> wrote:
  Hi Jerry,

based on Roland's work I have written a numerical example how
the TMOD parameter could be used. Is this of interest for the QSPEC
draft to include?

Best regards,
Bernd

An example VoIP application that uses RTP [RFC 1889] and the
G.711 Codec [ITU-T Rec. G.711] the TMOD-1 parameter could be
set as follows:

In the simplest case the Minimum Policed Unit m is the sum of the
IP-, UDP- and RTP- headers + payload. The IP header in the IPv4
case has a size of 20 bytes (40 bytes if IPv6 is used). The UDP
header has a size of 8 bytes and RTP uses a 12 byte header. The
G.711 Codec specifies a bandwidth of 64 kbit/s (8000 bytes/s).
Assuming RTP transmits voice datagrams every 20ms, the payload
for one datagram is 8000 bytes/s * 0.02 s = 160 bytes.

IPv4+UDP+RTP+payload: m=20+8+12+160 bytes = 200 bytes
IPv6+UDP+RTP+payload: m=40+8+12+160 bytes = 220 bytes

The Rate r specifies the amount of bytes per second. 50 datagrams
are sent per second.

IPv4: r = 50 1/s * m = 10,000 bytes/s
IPv6: r = 50 1/s * m = 11,000 bytes/s

The bucket size b specifies the maximum burst. In this example a
burst of 10 packets is used.

IPv4: b = 10 * m = 2000 bytes
IPv6: b = 10 * m = 2200 bytes

A number of extra headers (e.g. for encapsulation) may be included
into the datagram. A non exhaustive list is given below. For
additional headers m, r and b have to be set accordingly.

Protocol Header Size
--------------------------+-----------
GRE [RFC 1701] | 8 bytes
GREIP4 [RFC 1702] | 4-8 bytes
IP4INIP4 [RFC 2003] | 20 bytes
MINENC [RFC 2004] | 8-12 bytes
IP6GEN [RFC 2473] | 40 bytes
IP6INIP4 [RFC 4213] | 20 bytes
IPSec [RFC 4301,RFC 4303] | variable
--------------------------+-----------

Gerald Ash wrote:
> Hi Roland,
> 
> See comments below.
> 
>>> However, as stated at the beginning of Section 5.2 (QSPEC Parameter
>>> Coding):
>>>
>>> "The references in the following sections point to the normative
>>> procedures for processing the QSPEC parameters and
>>> sub-parameters."
>>> 
>>> In the case of TMOD-1 and TMOD-2, the normative references are RFC
>>> 2210 and RFC 2215. In particular, Section 3.1 in RFC 2210 and
> >> Section 3.6 in RFC 2215 give the necessary guidance on setting the
> >> token bucket parameters.
> 
>> Yes, they do, but actually there is no TMOD in RFC 2210. So even if the
>> match is somewhat obvious, it would be probably better to be more exact
>> and point to the SENDER_TSPEC definition in RFC 2210 or the
>> TOKEN_BUCKET_TSPEC definition in RFC 2215.
> 
> Yes I agree that the match between TMOD and TSPEC is pretty obvious. However it can be made even more explicit with specific references to TSPEC (Section 3.1 in RFC 2210 and Section 3.6 in RFC 2215), as you suggest.
> 
>>> IMO the QSPEC document isn't the place to give detailed examples of
>>> how to set these QSPEC parameters, or any other QSPEC parameters,
> >> beyond what is contained in the normative references.
> 
>> IMHO, an example in the appendix would be nice.
> 
> Well, the token bucket algorithm has been around for a long time (even before RSVP of course) so there are ample examples and implementations of its use. IMO it would not be appropriate (and perhaps a bit odd) for the QSPEC to include a tutorial on token bucket.
> 
> While RFCs 2210 and 2215 are the applicable normative description of the TSPEC/TMOD parameters, there are no numerical examples there of its use. So perhaps we could include a reference or 2 to some examples of token bucket implementation. Maybe that would help? A couple of references I'm aware of with numerical examples of token bucket implementation include
> 
> http://www.amazon.com/Computer-Networks-Approach-Kaufmann-Networking/dp/0123705487/
> 
> http://www.amazon.com/Traffic-Engineering-Optimization-Integrated-Networks/dp/0123706254/
> 
> Perhaps you could suggest an appropriate reference as well?
> 
> OTOH, I couldn't find any RFCs with numerical examples of TSPEC/TMOD implementation (do you know of any?), so that might be a justification to include one or two examples in QSPEC (such as the ones you constructed). 
> 
> Does anyone else have a comment on this?
> 
>> Shouldn't we copy the missing text from RFC 2210 or RFC 2215 since the
>> current description is incomplete without those RFCs?
> 
> I'm not sure what 'missing text' you suggest to copy. Once again, the intent of the statement at the beginning of QSPEC Section 5.2 ("The references in the following sections point to the normative procedures for processing the QSPEC parameters and sub-parameters.") is intended to avoid copying normative text into the QSPEC document for each QSPEC parameter. More generally, that is also the purpose of a normative reference in any RFC.
> 
> Do you want to suggest specific text to bring into QSPEC?
> 
> Regards,
> Jerry
       
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.
--0-255624357-1208885792=:88193
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>Hi Bernd,</DIV>  <DIV>&nbsp;</DIV>  <DIV>The example and text look good, thanks!</DIV>  <DIV>&nbsp;</DIV>  <DIV>I agree that it would be worthwhile to include&nbsp;this as an appendix/example in the QSPEC (after all, you and Roland&nbsp;did all the work :-).</DIV>  <DIV>&nbsp;</DIV>  <DIV>Thanks again,</DIV>  <DIV>Regards,</DIV>  <DIV>Jerry<BR><BR><BR><B><I>Bernd Schloer &lt;bschloer@cs.uni-goettingen.de&gt;</I></B> wrote:</DIV>  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hi Jerry,<BR><BR>based on Roland's work I have written a numerical example how<BR>the TMOD parameter could be used. Is this of interest for the QSPEC<BR>draft to include?<BR><BR>Best regards,<BR>Bernd<BR><BR>An example VoIP application that uses RTP [RFC 1889] and the<BR>G.711 Codec [ITU-T Rec. G.711] the TMOD-1 parameter could be<BR>set as follows:<BR><BR>In the simplest case the Minimum Policed Unit m is the sum of the<BR>IP-, UDP- and RTP-
 headers + payload. The IP header in the IPv4<BR>case has a size of 20 bytes (40 bytes if IPv6 is used). The UDP<BR>header has a size of 8 bytes and RTP uses a 12 byte header. The<BR>G.711 Codec specifies a bandwidth of 64 kbit/s (8000 bytes/s).<BR>Assuming RTP transmits voice datagrams every 20ms, the payload<BR>for one datagram is 8000 bytes/s * 0.02 s = 160 bytes.<BR><BR>IPv4+UDP+RTP+payload: m=20+8+12+160 bytes = 200 bytes<BR>IPv6+UDP+RTP+payload: m=40+8+12+160 bytes = 220 bytes<BR><BR>The Rate r specifies the amount of bytes per second. 50 datagrams<BR>are sent per second.<BR><BR>IPv4: r = 50 1/s * m = 10,000 bytes/s<BR>IPv6: r = 50 1/s * m = 11,000 bytes/s<BR><BR>The bucket size b specifies the maximum burst. In this example a<BR>burst of 10 packets is used.<BR><BR>IPv4: b = 10 * m = 2000 bytes<BR>IPv6: b = 10 * m = 2200 bytes<BR><BR>A number of extra headers (e.g. for encapsulation) may be included<BR>into the datagram. A non exhaustive list is given below.
 For<BR>additional headers m, r and b have to be set accordingly.<BR><BR>Protocol Header Size<BR>--------------------------+-----------<BR>GRE [RFC 1701] | 8 bytes<BR>GREIP4 [RFC 1702] | 4-8 bytes<BR>IP4INIP4 [RFC 2003] | 20 bytes<BR>MINENC [RFC 2004] | 8-12 bytes<BR>IP6GEN [RFC 2473] | 40 bytes<BR>IP6INIP4 [RFC 4213] | 20 bytes<BR>IPSec [RFC 4301,RFC 4303] | variable<BR>--------------------------+-----------<BR><BR>Gerald Ash wrote:<BR>&gt; Hi Roland,<BR>&gt; <BR>&gt; See comments below.<BR>&gt; <BR>&gt;&gt;&gt; However, as stated at the beginning of Section 5.2 (QSPEC Parameter<BR>&gt;&gt;&gt; Coding):<BR>&gt;&gt;&gt;<BR>&gt;&gt;&gt; "The references in the following sections point to the normative<BR>&gt;&gt;&gt; procedures for processing the QSPEC parameters and<BR>&gt;&gt;&gt; sub-parameters."<BR>&gt;&gt;&gt; <BR>&gt;&gt;&gt; In the case of TMOD-1 and TMOD-2, the normative references are RFC<BR>&gt;&gt;&gt; 2210 and RFC 2215. In particular, Section 3.1 in RFC 2210
 and<BR>&gt; &gt;&gt; Section 3.6 in RFC 2215 give the necessary guidance on setting the<BR>&gt; &gt;&gt; token bucket parameters.<BR>&gt; <BR>&gt;&gt; Yes, they do, but actually there is no TMOD in RFC 2210. So even if the<BR>&gt;&gt; match is somewhat obvious, it would be probably better to be more exact<BR>&gt;&gt; and point to the SENDER_TSPEC definition in RFC 2210 or the<BR>&gt;&gt; TOKEN_BUCKET_TSPEC definition in RFC 2215.<BR>&gt; <BR>&gt; Yes I agree that the match between TMOD and TSPEC is pretty obvious. However it can be made even more explicit with specific references to TSPEC (Section 3.1 in RFC 2210 and Section 3.6 in RFC 2215), as you suggest.<BR>&gt; <BR>&gt;&gt;&gt; IMO the QSPEC document isn't the place to give detailed examples of<BR>&gt;&gt;&gt; how to set these QSPEC parameters, or any other QSPEC parameters,<BR>&gt; &gt;&gt; beyond what is contained in the normative references.<BR>&gt; <BR>&gt;&gt; IMHO, an example in the appendix would be
 nice.<BR>&gt; <BR>&gt; Well, the token bucket algorithm has been around for a long time (even before RSVP of course) so there are ample examples and implementations of its use. IMO it would not be appropriate (and perhaps a bit odd) for the QSPEC to include a tutorial on token bucket.<BR>&gt; <BR>&gt; While RFCs 2210 and 2215 are the applicable normative description of the TSPEC/TMOD parameters, there are no numerical examples there of its use. So perhaps we could include a reference or 2 to some examples of token bucket implementation. Maybe that would help? A couple of references I'm aware of with numerical examples of token bucket implementation include<BR>&gt; <BR>&gt; http://www.amazon.com/Computer-Networks-Approach-Kaufmann-Networking/dp/0123705487/<BR>&gt; <BR>&gt; http://www.amazon.com/Traffic-Engineering-Optimization-Integrated-Networks/dp/0123706254/<BR>&gt; <BR>&gt; Perhaps you could suggest an appropriate reference as well?<BR>&gt; <BR>&gt; OTOH, I couldn't
 find any RFCs with numerical examples of TSPEC/TMOD implementation (do you know of any?), so that might be a justification to include one or two examples in QSPEC (such as the ones you constructed). <BR>&gt; <BR>&gt; Does anyone else have a comment on this?<BR>&gt; <BR>&gt;&gt; Shouldn't we copy the missing text from RFC 2210 or RFC 2215 since the<BR>&gt;&gt; current description is incomplete without those RFCs?<BR>&gt; <BR>&gt; I'm not sure what 'missing text' you suggest to copy. Once again, the intent of the statement at the beginning of QSPEC Section 5.2 ("The references in the following sections point to the normative procedures for processing the QSPEC parameters and sub-parameters.") is intended to avoid copying normative text into the QSPEC document for each QSPEC parameter. More generally, that is also the purpose of a normative reference in any RFC.<BR>&gt; <BR>&gt; Do you want to suggest specific text to bring into QSPEC?<BR>&gt; <BR>&gt; Regards,<BR>&gt;
 Jerry</BLOCKQUOTE><p>&#32;

      <hr size=1>Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile. <a href="http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ "> Try it now.</a>
--0-255624357-1208885792=:88193--

--===============1479709601==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1479709601==--


From nsis-bounces@ietf.org  Wed Apr 23 02:34:00 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 43C0F3A69AF;
	Wed, 23 Apr 2008 02:34:00 -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 189573A69AF
	for <nsis@core3.amsl.com>; Wed, 23 Apr 2008 02:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.558
X-Spam-Level: 
X-Spam-Status: No, score=0.558 tagged_above=-999 required=5 tests=[AWL=0.093, 
	BAYES_40=-0.185, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3]
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 zwJ3n9HGsrjz for <nsis@core3.amsl.com>;
	Wed, 23 Apr 2008 02:33:58 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de
	[141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id 522023A680F
	for <nsis@ietf.org>; Wed, 23 Apr 2008 02:33:58 -0700 (PDT)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps id 1JobMW-0005pJ-P6
	for <nsis@ietf.org>; Wed, 23 Apr 2008 11:34:02 +0200
Received: from i72mn03.tm.uni-karlsruhe.de ([141.3.71.33])
	by irams1.ira.uni-karlsruhe.de with esmtpsa for <nsis@ietf.org>
	id 1JobMX-0000E0-1t; Wed, 23 Apr 2008 11:34:01 +0200
Message-ID: <480F02AF.8050602@tm.uka.de>
Date: Wed, 23 Apr 2008 11:34:39 +0200
From: =?ISO-8859-15?Q?Martin_R=F6hricht?= <roehricht@tm.uka.de>
User-Agent: Thunderbird 2.0.0.12 (X11/20080227)
MIME-Version: 1.0
To: NSIS <nsis@ietf.org>
Subject: [NSIS] QoS NSLP Abstract API -> missing MRI
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-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

Hi,

in order to initiate a reservation from an application using the 
abstract NSLP-RMF API as defined in the current QoS-NSLP draft, I 
suppose we lack information such as the source and destination of the 
reservation request.  So I would like to know whether the MRI should be 
included in this API or not.

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


From nsis-bounces@ietf.org  Thu Apr 24 08:40:12 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1FAB33A6953;
	Thu, 24 Apr 2008 08:40:12 -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 841143A67A8
	for <nsis@core3.amsl.com>; Thu, 24 Apr 2008 08:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.853
X-Spam-Level: 
X-Spam-Status: No, score=0.853 tagged_above=-999 required=5 tests=[AWL=-1.357, 
	BAYES_40=-0.185, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545,
	MIME_8BIT_HEADER=0.3]
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 CucD6TOjaqMD for <nsis@core3.amsl.com>;
	Thu, 24 Apr 2008 08:40:06 -0700 (PDT)
Received: from rotterdam.ewi.utwente.nl (rotterdam.ewi.utwente.nl
	[130.89.10.5]) by core3.amsl.com (Postfix) with ESMTP id 61A403A6953
	for <nsis@ietf.org>; Thu, 24 Apr 2008 08:40:06 -0700 (PDT)
Received: from ewi977 (ewi977.ewi.utwente.nl [130.89.12.129])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	m3OFe1mU029656; Thu, 24 Apr 2008 17:40:08 +0200 (MEST)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "=?iso-8859-1?Q?'Martin_R=F6hricht'?=" <roehricht@tm.uka.de>,
	"'NSIS'" <nsis@ietf.org>
References: <480F02AF.8050602@tm.uka.de>
Date: Thu, 24 Apr 2008 17:39:55 +0200
Message-ID: <001101c8a621$7720a9a0$810c5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AcilJT0/iZztsG+NSVC/a9tytChk0AA+8Hog
In-Reply-To: <480F02AF.8050602@tm.uka.de>
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Thu, 24 Apr 2008 17:40:08 +0200 (MEST)
Subject: Re: [NSIS] QoS NSLP Abstract API -> missing MRI
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-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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Martin

Please note that the MRI information is already included in the "filter" =

parameter, see section A.1:

"filter: the information for packet filtering, based on the MRI and the
PACKET_CLASSIFIER object."

Best regards,
Georgios



 =


> -----Original Message-----
> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On =

> Behalf Of Martin R=F6hricht
> Sent: woensdag 23 april 2008 11:35
> To: NSIS
> Subject: [NSIS] QoS NSLP Abstract API -> missing MRI
> =

> Hi,
> =

> in order to initiate a reservation from an application using =

> the abstract NSLP-RMF API as defined in the current QoS-NSLP =

> draft, I suppose we lack information such as the source and =

> destination of the reservation request.  So I would like to =

> know whether the MRI should be included in this API or not.
> =

> Regards,
> Martin
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www.ietf.org/mailman/listinfo/nsis
> =



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


From nsis-bounces@ietf.org  Thu Apr 24 08:41:59 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 187723A6AB0;
	Thu, 24 Apr 2008 08:41:59 -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 8AB7C3A68C2
	for <nsis@core3.amsl.com>; Thu, 24 Apr 2008 08:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.324
X-Spam-Level: 
X-Spam-Status: No, score=0.324 tagged_above=-999 required=5 tests=[AWL=0.528, 
	BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545,
	MIME_8BIT_HEADER=0.3]
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 cEd0JL810lIh for <nsis@core3.amsl.com>;
	Thu, 24 Apr 2008 08:41:56 -0700 (PDT)
Received: from rotterdam.ewi.utwente.nl (rotterdam.ewi.utwente.nl
	[130.89.10.5]) by core3.amsl.com (Postfix) with ESMTP id 12B233A6C1C
	for <nsis@ietf.org>; Thu, 24 Apr 2008 08:41:55 -0700 (PDT)
Received: from ewi977 (ewi977.ewi.utwente.nl [130.89.12.129])
	by rotterdam.ewi.utwente.nl (8.13.6/8.13.6) with ESMTP id
	m3OFfv0C000496; Thu, 24 Apr 2008 17:42:00 +0200 (MEST)
From: "Georgios Karagiannis" <karagian@cs.utwente.nl>
To: "=?iso-8859-1?Q?'Martin_R=F6hricht'?=" <roehricht@tm.uka.de>,
	"'NSIS'" <nsis@ietf.org>
References: <480CB3B5.9030607@tm.uka.de>
Date: Thu, 24 Apr 2008 17:41:51 +0200
Message-ID: <001201c8a621$ba27ef10$810c5982@dynamic.ewi.utwente.nl>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Thread-Index: AcijxQ15lS3URcF8QNOoQpVzQwB7IgCXHIMg
In-Reply-To: <480CB3B5.9030607@tm.uka.de>
X-Scanned-By: MIMEDefang 2.52 on 130.89.10.5
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0rc3
	(rotterdam.ewi.utwente.nl [130.89.10.5]);
	Thu, 24 Apr 2008 17:42:00 +0200 (MEST)
Subject: Re: [NSIS] NSLP-RMF API Question
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-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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi Martin

Regarding GIST API we say in Section A.1:
"GIST_API_triggers: it represents the attributes that are provided by GIST
to QoS-NSLP via the GIST API."

Thus what this section describes regarding GIST API parameters, is how the
obtained GIST API parameters =

are communicated via QoS-NSLP to RMF.

Best regards,
Georgios

> -----Original Message-----
> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On =

> Behalf Of Martin R=F6hricht
> Sent: maandag 21 april 2008 17:33
> To: NSIS
> Subject: [NSIS] NSLP-RMF API Question
> =

> Hi,
> =

> Appendix A.1 "Triggers from QOS-NSLP towards RMF" of the =

> current NSLP draft lists GIST_API_triggers which are meant to =

> be used by the
> sendrmf() function as one of its arguments.
> I was wondering if this is correct or just more of a =

> copy-and-paste-like error since these triggers represent =

> attributes that are provided by GIST to QoS-NSLP via the GIST =

> API which is not appropriate in this context, imho.
> =

> Best regards,
> Martin
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www.ietf.org/mailman/listinfo/nsis
> =



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


From nsis-bounces@ietf.org  Fri Apr 25 05:07:00 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: nsis-archive@megatron.ietf.org
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 56DD03A6DDB;
	Fri, 25 Apr 2008 05:07:00 -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 B2AA53A6959;
	Fri, 25 Apr 2008 05:06:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 Wydt6Qwfn4QO; Fri, 25 Apr 2008 05:06:49 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62])
	by core3.amsl.com (Postfix) with ESMTP id 0876528C31C;
	Fri, 25 Apr 2008 05:06:40 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	A75A4213DF; Fri, 25 Apr 2008 14:06:44 +0200 (CEST)
X-AuditID: c1b4fb3e-ad196bb000004ec0-dd-4811c954f215
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	81FC2206C4; Fri, 25 Apr 2008 14:06:44 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 25 Apr 2008 14:06:44 +0200
Received: from [127.0.0.1] ([147.214.183.174]) by esealmw129.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 25 Apr 2008 14:06:44 +0200
Message-ID: <4811C952.8090604@ericsson.com>
Date: Fri, 25 Apr 2008 14:06:42 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: TSV Area <tsv-area@ietf.org>
X-Enigmail-Version: 0.95.6
X-OriginalArrivalTime: 25 Apr 2008 12:06:44.0120 (UTC)
	FILETIME=[D40CB180:01C8A6CC]
X-Brightmail-Tracker: AAAAAA==
Cc: tsvwg <tsvwg@ietf.org>, NSIS <nsis@ietf.org>
Subject: [NSIS] Proposed Liaison Statement to ITU-T SG 11 on Flow State
	Aware signalling
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-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="utf-8"
Content-Transfer-Encoding: base64
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

UGxlYXNlIHByb3ZpZGUgYW55IGNvbW1lbnRzIG9uIHRoaXMgZHJhZnQgTFMgYmVmb3JlIHRoZSA1
dGggb2YgTWF5LiBUaGUgCkFEcyB3aWxsIGp1ZGdlIGlmIHRoZXJlIGlzIGNvbnNlbnN1cyBvbiB0
aGlzIHN0YXRlbWVudCBiZWZvcmUgc2VuZGluZyBpdC4KCgpGcm9tOiBJRVRGIFRTViBBUkVBClRv
OiAgIElUVS1UIFNHIDExICh0c2cxMWdlbkBpdHUuaW50KSwKICAgICAgIElUVS1UIFEuNS8xMSAo
dHNnMTFxNUBpdHUuaW50KSwKICAgICAgIElUVS1UIFdQIDIvMTEgU2Vzc2lvbiwgYmVhcmVyIGFu
ZCByZXNvdXJjZSBjb250cm9sCiAgICAgICAgICAgICAodHNnMTF3cDJAaXR1LmludCkKQ2M6ICAg
SUVURiBMaWFpc29uIHRvIElUVS1UIG9uIE5HTiBNb25pcXVlIE1vcnJvdyAobW1vcnJvd0BjaXNj
by5jb20pLAogICAgICAgSUVURiBMaWFpc29uIHRvIElUVS1UIFNjb3R0IEJyYWRuZXIgKHNvYkBo
YXJ2YXJkLmVkdSksCiAgICAgICBJRVRGIENoYWlyIFJ1c3MgSG91c2xleSAoY2hhaXJAaWV0Zi5v
cmcpLAogICAgICAgSVRVLVQgVGVsZWNvbW11bmljYXRpb24gU3RhbmRhcmRpemF0aW9uIEFkdmlz
b3J5IEdyb3VwCiAgICAgICAgICAgICAodHNhZ2dlbkBpdHUuaW50KQpSZXNwb25zZSBDb250YWN0
OiBUcmFuc3BvcnQgQXJlYSBEaXJlY3RvcnM6CiAgICBNYWdudXMgV2VzdGVybHVuZCAobWFnbnVz
Lndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tKQogICAgTGFycyBFZ2dlcnQgKGxhcnMuZWdnZXJ0QG5v
a2lhLmNvbSkKVGVjaG5pY2FsIENvbnRhY3Q6IAkKICAgIE1hZ251cyBXZXN0ZXJsdW5kIChtYWdu
dXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20pLAogICAgTGFycyBFZ2dlcnQgKGxhcnMuZWdnZXJ0
QG5va2lhLmNvbSkKUHVycG9zZTogRm9yIGFjdGlvbgpEZWFkbGluZTogMjAwOC0wNy0yNwoKU3Vi
amVjdDogUmVnYXJkaW5nIGFueSBJRVRGIHdvcmsgcmVxdWlyZWQgZm9yIG5ldyBJVFUtVCBSZWNv
bW1lbmRhdGlvbgogICAgICAgICAgICAgICAgUS5GbG93c3RhdGVzaWcKCkJvZHk6CgpUaGUgSUVU
RiBUcmFuc3BvcnQgQXJlYSB3b3VsZCBsaWtlIHRvIHRoYW5rIElUVS1UIFNHIDExIGZvciB0aGUg
bGlhaXNvbiAKc3RhdGVtZW50IHRpdGxlZCDigJxDb21tZW50cyBvbiB0aGUgSUVURiBMaWFpc29u
IHJlc3BvbnNlIG9uIFkuMjEyMSBhbmQgCnRoZSBkZXZlbG9wbWVudCBvZiBuZXcgUmVjb21tZW5k
YXRpb24gUS5GbG93c3RhdGVzaWfigJ0gKENPTSAxMSAtIExTIDY2IArigJNFKS4gV2UgYXBwcmVj
aWF0ZSBTRzEx4oCZcyB3aWxsaW5nbmVzcyB0byBoYXZlIGEgZ29vZCBjb29wZXJhdGlvbiBhbmQg
Cndvcmsgd2l0aGluIHRoZSBhZ3JlZW1lbnRzIGJldHdlZW4gb3VyIHR3byBvcmdhbml6YXRpb25z
LgoKV2Ugbm90ZSB5b3VyIGNsYXJpZmljYXRpb24gb24gdGhlIGludGVuZGVkIGRlcGxveW1lbnQg
ZW52aXJvbm1lbnQgb2YgCkZsb3cgU3RhdGUgQXdhcmUgKEZTQSkgc2lnbmFsaW5nLiBXZSBsaWtl
IHRvIHJlbWFyayB0aGF0IGFsdGhvdWdoIAppbnRlbmRlZCBkZXBsb3ltZW50IG1heSBiZSBsaW1p
dGVkLCB0aGUgYXNzb2NpYXRlZCBzaWduYWxpbmcgYW5kIGRhdGEgCnRyYWZmaWMgZnJvbSBhIEZT
QSBlbmFibGVkIGVuZC1zeXN0ZW0sIGFwcGVhcnMgdG8gaGF2ZSBhIHZlcnkgaGlnaCAKcHJvYmFi
aWxpdHkgdG8gYmUgc2VudCBvdmVyIHRoZSBnZW5lcmFsIEludGVybmV0LiBUaHVzIHRoZSBkZXZl
bG9wbWVudCAKb2YgYSBzb2x1dGlvbiBmb3Igc3VjaCBmdW5jdGlvbnMgcmVhbGx5IHNob3VsZCB0
YWtlIHV0bW9zdCBjYXJlIHRvIG5vdCAKaGF2ZSBuZWdhdGl2ZSBpbXBhY3Qgb24gZXhpc3Rpbmcg
ZW5kLWhvc3RzIGFuZCBuZXR3b3JrIGluZnJhc3RydWN0dXJlLiAKVGhpcyBpcyBhIG1ham9yIHJl
YXNvbiB3aHkgYW55IHN1Y2ggZXh0ZW5zaW9uIHByb3Bvc2FscyB0aGF0IGFmZmVjdCBJRVRGIApw
cm90b2NvbHMgd2lsbCBuZWVkIGV4dGVuc2l2ZSBhbmQgd2lkZSByZXZpZXcgd2l0aGluIHRoZSBJ
RVRGIGNvbW11bml0eS4gCkNlcnRhaW4gdHlwZXMgb2YgZXh0ZW5zaW9uIHByb3Bvc2FscyB3aWxs
IGJlIHJlcXVpcmVkIHRvIGJlIGRldmVsb3BlZCAKd2l0aGluIElFVEYgaXRzZWxmLgoKV2UgYXJl
IGxvb2tpbmcgZm9yd2FyZCB0byBhIGxpYWlzb24gc3RhdGVtZW50IHdoZXJlIHlvdSBwcm92aWRl
IG91dC1saW5lIApvZiB5b3VyIHByb3Bvc2VkIHNvbHV0aW9uIGZvciBvdXIgdW5kZXJzdGFuZGlu
ZyBhbmQgeW91IGxpc3Rpbmcgd2hlcmUgCnlvdSBmb3Jlc2VlIGl0IGltcGFjdGluZyBwcm90b2Nv
bHMgYW5kIHNwZWNpZmljYXRpb25zIHRoYXQgYXJlIHVuZGVyIApJRVRGIGNoYW5nZSBjb250cm9s
LiBXZSBhbHNvIHN0cm9uZ2x5IGVuY291cmFnZSBtb3JlIGluZm9ybWFsIGNvbnRhY3RzIAp3aXRo
IElFVEYgYXJlYSBkaXJlY3RvcnMsIGxpYWlzb24gcGVyc29ucywgb3IgV0cgY2hhaXJzIG9mIHJl
bGV2YW50IFdHcyAKdG8gZW5hYmxlIGFuIGFzIGVhcmx5IGFzIHBvc3NpYmxlIGNvbW11bmljYXRp
b24gdG8gZGlzY3VzcyByZXF1aXJlZCAKc3RlcHMgdG8gYWNjb21wbGlzaCBhbnkgc3VjaCBjaGFu
Z2VzIG9yIGV4dGVuc2lvbnMuIFRoaXMgYXMgZWFjaCAKaW5kaXZpZHVhbCBpdGVtIG1heSByZXF1
aXJlIGEgZGlmZmVyZW50IHByb2Nlc3Mgd2l0aCBoaWdobHkgdmFyeWluZyB0aW1lIApyZXF1aXJl
ZCB0byBjb21wbGV0ZSB0aGVtLiBUaGVyZSBhcHBlYXJzIHRvIGJlIGEgcG90ZW50aWFsIGluIHRo
ZSAKcGxhbm5lZCBTRzExIHdvcmsgb24gRlNBIHNpZ25hbGluZyBmb3IgZXh0ZW5zaW9ucyB0aGF0
IHdpbGwgYmUgcmVxdWlyZWQgCnRvIGJlIGRldmVsb3BlZCB3aXRoaW4gSUVURiBiYXNlZCBvbiBT
RzExIHJlcXVpcmVtZW50cy4KCkFzIFkuMjEyMSBoaW50cyBhdCB0aGUgcG90ZW50aWFsIHVzYWdl
IG9mIElQIG9wdGlvbnMgZm9yIGNhcnJ5aW5nIHRoZSAKRlNBIGluZm9ybWF0aW9uIHdlIHdvdWxk
IGxpa2UgdG8gdXNlIHRoaXMgYXMgYW4gZXhhbXBsZSBmb3IgdGhlIHJlcXVpcmVkIApwcm9jZXNz
IHdpdGhpbiBJRVRGIGZvciBzcGVjaWZ5aW5nIHN1Y2ggYW4gb3B0aW9uLiBCb3RoIElQdjQgYW5k
IElQdjYgCkhvcC1ieS1ob3Agb3B0aW9ucyBhcmUgdW5kZXIgdGhlIHJlZ2lzdHJhdGlvbiBwb2xp
Y3kg4oCcSUVTRyBBcHByb3ZhbCwgCklFVEYgQ29uc2Vuc3VzIG9yIFN0YW5kYXJkcyBBY3Rpb24g
cHJvY2Vzc2Vz4oCdIGFzIGRlZmluZWQgYnkgUkZDIDI0MzQuIApDb25zaWRlcmluZyB0aGUgcG90
ZW50aWFsIGltcGFjdCBvbiBvdGhlciBzeXN0ZW1zIGZyb20gSVAgb3B0aW9ucyB0aGUgCklFU0cg
YXJlIGxpa2VseSB0byByZXF1aXJlIChJRVRGKSBzdGFuZGFyZHMgYWN0aW9uIGZvciBhbnkgZXh0
ZW5zaW9uLiAKSG93ZXZlciwgdGhlIGV4YWN0IGp1ZGdtZW50IG9uIHRoaXMgd2lsbCBvZiBjb3Vy
c2UgZGVwZW5kIG9uIHRoZSBhY3R1YWwgCnByb3Bvc2FsLiBXaHkgaXQgaXMgaW1wb3J0YW50IHRo
YXQgd2UgYXMgZWFybHkgYXMgcG9zc2libGUgZGV0ZXJtaW5lIAp3aGF0IGV4dGVuc2lvbnMgb3Ig
Y2hhbmdlcyB0aGF0IHdpbGwgYmUgcmVxdWlyZWQuIEFuZCBpbiBjYXNlIHN0YW5kYXJkcyAKYWN0
aW9ucyBhcmUgcmVxdWlyZWQsIGEgd29yayBpdGVtIG5lZWRzIHRvIGJlIGNoYXJ0ZXJlZCBlaXRo
ZXIgaW4gYSAKc3VpdGFibGUgZXhpc3RpbmcgV0cgb3IgdG8gY3JlYXRlIGEgbmV3IFdHLiBUaGVy
ZWZvcmUgd2UgZG8gZXh0ZW5kIG91ciAKZWFybGllciBvZmZlciB0byBydW4gYSBCaXJkIG9mIGEg
RmVhdGhlciAoQk9GKSBzZXNzaW9uIG9uIHRoaXMgdG9waWMgYXQgCmEgZnV0dXJlIElFVEYgbWVl
dGluZy4gTm90ZSB0aGF0IHRoaXMgcmVxdWlyZXMgcHJlcGFyYXRpb25zIGFuZCB0aGUgCnByb3Bv
bmVudHMgZm9yIHRoaXMgd29yayBzaG91bGQgY29udGFjdCB0aGUgdHJhbnNwb3J0IGFyZWEgZGly
ZWN0b3JzLgoKVGhlIElFVEYgVHJhbnNwb3J0IEFyZWEga2luZGx5IHJlcXVlc3RzIHRoZSBmb2xs
b3dpbmcgYWN0aW9ucyBmcm9tIFNHIDExOgoKLSBUaGF0IFNHIDExIGFzIGVhcmx5IGFzIHBvc3Np
YmxlIHByb3ZpZGUgdGhlIElFVEYgdHJhbnNwb3J0IGFyZWEgd2l0aCBhCiAgIGdlbmVyYWwgb3Zl
cnZpZXcgb2YgdGhlIHNvbHV0aW9uIGZvciBGU0Egc2lnbmFsaW5nIGFuZCBpbmZvcm0gdXMgb24K
ICAgdGhlIGZvcmVzZWVuIGltcGFjdCBvbiBJRVRGIHByb3RvY29scyBhbmQgYW55IG5lZWRlZCBl
eHRlbnNpb25zIG9yCiAgIGNoYW5nZXMgdG8gcHJvdG9jb2xzIHVuZGVyIElFVEYgY2hhbmdlIGNv
bnRyb2wuCgotIFRoYXQgU0cxMSBwcm92aWRlcyBhIHRpbWVwbGFuIGZvciB3aGVuIHRoZSBhYm92
ZSBhY3Rpb24gY2FuIGJlCiAgIGNvbXBsZXRlZCBhbmQgYW55IG90aGVyIGtleSBwb2ludHMgaW4g
dGhlIHRpbWVwbGFuIGZvciBjb21wbGV0aW9uIG9mCiAgIHRoZSBuZXcgUmVjb21tZW5kYXRpb24g
d2l0aCB0aGUgd29yayBuYW1lIFEuIEZsb3dzdGF0ZXNpZy4KCi0gVGhhdCBTRzExIHByb3ZpZGVz
IGNsYXJpZmljYXRpb24gb24gd2hhdCBpcyBhY3R1YWxseSBtZWFudCB3aXRoIHRoZQogICBGU0Eg
dHJhbnNwb3J0IHRlY2hub2xvZ3kgYmVpbmcgb3ZlcmxhaWQgb24gdGhlIE5HTi4KClRoaXMgTGlh
aXNvbiBtZXNzYWdlIHJlcHJlc2VudHMgdGhlIHZpZXdzIG9mIHRoZSBUcmFuc3BvcnQgQXJlYSAK
ZGlyZWN0b3JzIGFuZCBoYXMgYmVlbiByZXZpZXdlZCBhbmQgaGFzIHRoZSBjb25zZW5zdXMgb2Yg
dGhlIFRyYW5zcG9ydCAKQXJlYS4KCgoKCi0tIAoKTWFnbnVzIFdlc3Rlcmx1bmQKCklFVEYgVHJh
bnNwb3J0IEFyZWEgRGlyZWN0b3IgJiBUU1ZXRyBDaGFpcgotLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCk11bHRpbWVk
aWEgVGVjaG5vbG9naWVzLCBFcmljc3NvbiBSZXNlYXJjaCBFQUIvVFZNCi0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0K
RXJpY3Nzb24gQUIgICAgICAgICAgICAgICAgfCBQaG9uZSArNDYgOCA0MDQ4Mjg3CkbDpHLDtmdh
dGFuIDYgICAgICAgICAgICAgICAgfCBGYXggICArNDYgOCA3NTc1NTUwClMtMTY0IDgwIFN0b2Nr
aG9sbSwgU3dlZGVuIHwgbWFpbHRvOiBtYWdudXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20KLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18KbnNpcyBtYWlsaW5nIGxpc3QKbnNpc0BpZXRmLm9yZwpodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL25zaXMK


