From nsis-bounces@ietf.org  Fri Feb  1 04:12:43 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB35D28C1D8;
	Fri,  1 Feb 2008 04:12:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id v5YvU6yQZ4QP; Fri,  1 Feb 2008 04:12:42 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C15833A6941;
	Fri,  1 Feb 2008 04:12:42 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C77313A6961
	for <nsis@core3.amsl.com>; Fri,  1 Feb 2008 04:12:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ZQfzoQRbJiii for <nsis@core3.amsl.com>;
	Fri,  1 Feb 2008 04:12:40 -0800 (PST)
Received: from smtp.cs.uni-tuebingen.de (u-173-c156.cs.uni-tuebingen.de
	[134.2.173.156])
	by core3.amsl.com (Postfix) with ESMTP id 32E603A6941
	for <nsis@ietf.org>; Fri,  1 Feb 2008 04:12:39 -0800 (PST)
Received: from u-172-c174.cs.uni-tuebingen.de ([134.2.172.174])
	by smtp.cs.uni-tuebingen.de with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.60) (envelope-from <iinfe01@ri.uni-tuebingen.de>)
	id 1JKumY-0002dT-Mm; Fri, 01 Feb 2008 13:14:10 +0100
Message-ID: <47A30D11.1080204@uni-tuebingen.de>
Date: Fri, 01 Feb 2008 13:14:09 +0100
From: Ali Fessi <ali.fessi@uni-tuebingen.de>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: Martin Stiemerling <Stiemerling@nw.neclab.eu>
References: <C3C64ABB.EA6B%Stiemerling@nw.neclab.eu>
In-Reply-To: <C3C64ABB.EA6B%Stiemerling@nw.neclab.eu>
Cc: nsis <nsis@ietf.org>
Subject: Re: [NSIS] FW:  I-D Action:draft-ietf-nsis-nslp-natfw-17.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: <http://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: <http://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

I think this document is in good shape and ready for IESG review!

Best,
  Ali

Martin Stiemerling wrote:
> Hi,
> 
> This new version of the NATFW NSLP incorporates the comments received in 
> the WGLC.
> 
> Please check if all comments have been addressed properly.
> 
> Thanks,
> 
>   Martin
> 
> Change log natfw-nslp 16 to 17
> - Removed section 8 "open issues"
> - Removed short form of EXT in favour of calling it always EXTERNAL
> - Restructered section 3.2 "Basic Protocol Overview" for better readability
> - Added second proxy example in 3.2. (3.2.3.  Signaling for Proxy Mode)
> - Fixed different issues of editorial nature
> - Clarified on DTINFO; PC-MRM and LE-MRM usage
> - Handled Jukka's comments (e-mail Dec 04 2007)
> - Handled Niklas' comments (e-mail Dec 11 2007)
> - Handled Lauri's comments (e-amil Dec 13 2007)
> - Handled Teemu's comments (e-mail Dec 19 2007)
> - Changed 'transit' timer definition to 30 seconds, at least.
> - Changed Lifetime error messages, i.e., added two new error codes.
> - Changed proxy flag error handling for NOTIFY.
> - Corrected some misspellings.
> - Fixed duplicated stuff in "NSLP Header" section (Hannes' e-mail Jan 30)
> 
>    Martin
> 
> 
> ------ Weitergeleitete Nachricht
> *Von: *<Internet-Drafts@ietf.org>
> *Datum: *Wed, 30 Jan 2008 15:30:01 +0100
> *An: *<i-d-announce@ietf.org>
> *Cc: *<nsis@ietf.org>
> *Unterhaltung: *[NSIS] I-D Action:draft-ietf-nsis-nslp-natfw-17.txt
> *Betreff: *[NSIS] I-D Action:draft-ietf-nsis-nslp-natfw-17.txt
> 
> 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           : NAT/Firewall NSIS Signaling Layer Protocol (NSLP)
>         Author(s)       : M. Stiemerling, et al.
>         Filename        : draft-ietf-nsis-nslp-natfw-17.txt
>         Pages           : 89
>         Date            : 2008-01-30
> 
> This memo defines the NSIS Signaling Layer Protocol (NSLP) for
> Network Address Translators (NATs) and firewalls.  This NSLP allows
> hosts to signal on the data path for NATs and firewalls to be
> configured according to the needs of the application data flows.  For
> instance, it enables hosts behind NATs to obtain a public reachable
> address and hosts behind firewalls to receive data traffic.  The
> overall architecture is given by the framework and requirements
> defined by the Next Steps in Signaling (NSIS) working group.  The
> network scenarios, the protocol itself, and examples for path-coupled
> signaling are given in this memo.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-nslp-natfw-17.txt
> 
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in the body of
> the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the
> username "anonymous" and a password of your e-mail address. After
> logging in, type "cd internet-drafts" and then
>         "get draft-ietf-nsis-nslp-natfw-17.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
>         mailserv@ietf.org.
> In the body type:
>         "FILE /internet-drafts/draft-ietf-nsis-nslp-natfw-17.txt".
> 
> NOTE:   The mail server at ietf.org can return the document in
>         MIME-encoded form by using the "mpack" utility.  To use this
>         feature, insert the command "ENCODING mime" before the "FILE"
>         command.  To decode the response(s), you will need "munpack" or
>         a MIME-compliant mail reader.  Different MIME-compliant mail readers
>         exhibit different behavior, especially when dealing with
>         "multipart" MIME messages (i.e. documents which have been split
>         up into multiple messages), so check your local documentation on
>         how to manipulate these messages.
> 
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 
> 
> ------ Ende der weitergeleiteten Nachricht
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis


-- 
Ali Fessi
Computer Networks and Internet
University of Tuebingen, Germany
Phone: +49 7071 29-70576 / Fax: +49 7071 29-5220
EMail: ali.fessi@uni-tuebingen.de
Web: http://net.informatik.uni-tuebingen.de/~fessi/
_______________________________________________
nsis mailing list
nsis@ietf.org
http://www.ietf.org/mailman/listinfo/nsis
From mailman-bounces@core3.amsl.com  Fri Feb  1 05:33:28 2008
Return-Path: <mailman-bounces@core3.amsl.com>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F3FB729650C
	for <ietfarch-nsis-archive@core3.amsl.com>; Fri,  1 Feb 2008 05:32:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.010,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 1XrorbJN6xOp for <ietfarch-nsis-archive@core3.amsl.com>;
	Fri,  1 Feb 2008 05:32:18 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EC23B2956BC
	for <nsis-archive@megatron.ietf.org>; Fri,  1 Feb 2008 05:06:27 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: nsis-archive@megatron.ietf.org
X-No-Archive: yes
Message-ID: <mailman.11409.1201870974.31726.mailman@core3.amsl.com>
Date: Fri, 01 Feb 2008 05:02:54 -0800
Precedence: bulk
X-BeenThere: mailman@core3.amsl.com
X-Mailman-Version: 2.1.9
List-Id: <mailman.core3.amsl.com>
X-List-Administrivia: yes
Sender: mailman-bounces@core3.amsl.com
Errors-To: mailman-bounces@core3.amsl.com

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

http://www.ietf.org/mailman/options/nsis/nsis-archive%40megatron.ietf.org
From mailman-bounces@core3.amsl.com  Fri Feb  1 05:34:41 2008
Return-Path: <mailman-bounces@core3.amsl.com>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 951A628C470
	for <ietfarch-nsis-archive@core3.amsl.com>; Fri,  1 Feb 2008 05:32:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.010,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id XHJQZHZ3htVj for <ietfarch-nsis-archive@core3.amsl.com>;
	Fri,  1 Feb 2008 05:32:29 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 221E128D333
	for <nsis-archive@megatron.ietf.org>; Fri,  1 Feb 2008 05:06:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: nsis-archive@megatron.ietf.org
X-No-Archive: yes
Message-ID: <mailman.11409.1201870975.31733.mailman@core3.amsl.com>
Date: Fri, 01 Feb 2008 05:02:55 -0800
Precedence: bulk
X-BeenThere: mailman@core3.amsl.com
X-Mailman-Version: 2.1.9
List-Id: <mailman.core3.amsl.com>
X-List-Administrivia: yes
Sender: mailman-bounces@core3.amsl.com
Errors-To: mailman-bounces@core3.amsl.com

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

http://www.ietf.org/mailman/options/nsis/nsis-archive%40megatron.ietf.org
From nsis-bounces@ietf.org  Mon Feb  4 09:19:01 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A5C713A7069;
	Mon,  4 Feb 2008 09:19:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id d2tvoBVt2NqV; Mon,  4 Feb 2008 09:19:00 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6C3453A6FC1;
	Mon,  4 Feb 2008 09:15:02 -0800 (PST)
X-Original-To: nsis@ietf.org
Delivered-To: nsis@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 7A5983A6F90; Mon,  4 Feb 2008 09:15:01 -0800 (PST)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080204171501.7A5983A6F90@core3.amsl.com>
Date: Mon,  4 Feb 2008 09:15:01 -0800 (PST)
Cc: nsis@ietf.org
Subject: [NSIS] I-D Action:draft-ietf-nsis-ntlp-15.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: <http://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: <http://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           : GIST: General Internet Signalling Transport
	Author(s)       : H. Schulzrinne, R. Hancock
	Filename        : draft-ietf-nsis-ntlp-15.txt
	Pages           : 153
	Date            : 2008-02-04

This document specifies protocol stacks for the routing and transport
of per-flow signalling messages along the path taken by that flow
through the network.  The design uses existing transport and security
protocols under a common messaging layer, the General Internet
Signalling Transport (GIST), which provides a common service for
diverse signalling applications.  GIST does not handle signalling
application state itself, but manages its own internal state and the
configuration of the underlying transport and security protocols to
enable the transfer of messages in both directions along the flow
path.  The combination of GIST and the lower layer transport and
security protocols provides a solution for the base protocol
component of the "Next Steps in Signalling" framework.

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

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-nsis-ntlp-15.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-nsis-ntlp-15.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-nsis-ntlp-15.txt

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

Content-Type: text/plain
Content-ID: <2008-02-04090751.I-D\@ietf.org>


--OtherAccess--

--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
http://www.ietf.org/mailman/listinfo/nsis

--NextPart--


From nsis-bounces@ietf.org  Mon Feb  4 13:32:56 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 01BA93A6F87;
	Mon,  4 Feb 2008 13:32:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.599
X-Spam-Level: 
X-Spam-Status: No, score=-1.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=1]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 04Rhn4wdwxc1; Mon,  4 Feb 2008 13:32:55 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BBF9F3A6ECC;
	Mon,  4 Feb 2008 13:32:53 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1BF023A6AC5
	for <nsis@core3.amsl.com>; Mon,  4 Feb 2008 13:32:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5xFqGK3f5XeC for <nsis@core3.amsl.com>;
	Mon,  4 Feb 2008 13:32:51 -0800 (PST)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id 7EA593A7158
	for <nsis@ietf.org>; Mon,  4 Feb 2008 13:32:11 -0800 (PST)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m14LXeiD020502 for <nsis@ietf.org>; Mon, 4 Feb 2008 23:33:42 +0200
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Feb 2008 23:33:40 +0200
Received: from daebe104.NOE.Nokia.com ([10.241.36.13]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Feb 2008 15:33:39 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 4 Feb 2008 15:33:38 -0600
Message-ID: <19EBBEC503C3B5469070E0A6674A533AFA2BC5@daebe104.NOE.Nokia.com>
In-Reply-To: <C3C64CEC.EA72%Stiemerling@nw.neclab.eu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WGLC Ended:  I-D Action:draft-ietf-nsis-nslp-natfw-17.txt 
Thread-Index: AchjTKxdqmOPjwfzSoqN9aOFZmt28wAAUHXgAAAx0FAAACKHfAEJg3sg
References: <19EBBEC503C3B5469070E0A6674A533AF77851@daebe104.NOE.Nokia.com>
	<C3C64CEC.EA72%Stiemerling@nw.neclab.eu>
From: <john.loughney@nokia.com>
To: <nsis@ietf.org>
X-OriginalArrivalTime: 04 Feb 2008 21:33:39.0166 (UTC)
	FILETIME=[9B230FE0:01C86775]
X-Nokia-AV: Clean
Subject: [NSIS] WGLC Ended:  I-D Action:draft-ietf-nsis-nslp-natfw-17.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0379407175=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0379407175==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C86775.9B608B67"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C86775.9B608B67
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Martin has updated the NAT/FW NSLP.  The working group has been
concluded, and there have been a few (mostly minor) issues, and Martin
has updated them. I encourage the WG to check to see if their issues
have been addressed, by the end of this week.  I will then do a WG Chair
write up on the document and get it ready for submission to our AD.
=20
thanks,
John

------_=_NextPart_001_01C86775.9B608B67
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Re: [NSIS] I-D =
Action:draft-ietf-nsis-nslp-natfw-17.txt</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16441" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN style=3D"FONT-SIZE: 12px"><FONT face=3D"Verdana, Helvetica, =
Arial"><SPAN=20
class=3D909283121-04022008><FONT face=3DArial color=3D#0000ff =
size=3D2>Martin has=20
updated the NAT/FW NSLP.&nbsp; The working group has been concluded, and =
there=20
have been a few (mostly minor) issues, and Martin has updated them. I =
encourage=20
the WG to check to see if their issues have been addressed, by the end =
of this=20
week.&nbsp; I will then do a WG Chair write up on the document and get =
it ready=20
for submission to our AD.</FONT></SPAN></FONT></SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 12px"><FONT face=3D"Verdana, Helvetica, =
Arial"><SPAN=20
class=3D909283121-04022008><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN style=3D"FONT-SIZE: 12px"><FONT face=3D"Verdana, Helvetica, =
Arial"><SPAN=20
class=3D909283121-04022008><FONT face=3DArial color=3D#0000ff=20
size=3D2>thanks,</FONT></SPAN></FONT></SPAN></DIV>
<DIV><SPAN style=3D"FONT-SIZE: 12px"><FONT face=3D"Verdana, Helvetica, =
Arial"><SPAN=20
class=3D909283121-04022008><FONT face=3DArial color=3D#0000ff=20
size=3D2>John</FONT></SPAN></DIV></FONT></SPAN></BODY></HTML>

------_=_NextPart_001_01C86775.9B608B67--

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

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

--===============0379407175==--


From nsis-bounces@ietf.org  Thu Feb  7 05:45:05 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B1FB43A7903;
	Thu,  7 Feb 2008 05:45:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1])
	by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yX5uFlrGUsVc; Thu,  7 Feb 2008 05:45:04 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4C8E43A787A;
	Thu,  7 Feb 2008 05:45:03 -0800 (PST)
X-Original-To: nsis@ietf.org
Delivered-To: nsis@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 262F03A7204; Thu,  7 Feb 2008 05:45:00 -0800 (PST)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080207134501.262F03A7204@core3.amsl.com>
Date: Thu,  7 Feb 2008 05:45:01 -0800 (PST)
Cc: nsis@ietf.org
Subject: [NSIS] I-D Action:draft-ietf-nsis-qos-nslp-16.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: <http://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: <http://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           : NSLP for Quality-of-Service Signaling
	Author(s)       : J. Manner, et al.
	Filename        : draft-ietf-nsis-qos-nslp-16.txt
	Pages           : 97
	Date            : 2008-02-07

This specification describes the NSIS Signaling Layer Protocol (NSLP)
for signaling QoS reservations in the Internet.  It is in accordance
with the framework and requirements developed in NSIS.  Together with
GIST, it provides functionality similar to RSVP and extends it.  The
QoS NSLP is independent of the underlying QoS specification or
architecture and provides support for different reservation models.
It is simplified by the elimination of support for multicast flows.
This specification explains the overall protocol approach, design
decisions made and provides examples.  It specifies object, message
formats and processing rules.

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

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-nsis-qos-nslp-16.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-nsis-qos-nslp-16.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-nsis-qos-nslp-16.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-nsis-qos-nslp-16.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-02-07053146.I-D\@ietf.org>


--OtherAccess--

--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
http://www.ietf.org/mailman/listinfo/nsis

--NextPart--


From nsis-bounces@ietf.org  Mon Feb 11 05:59:49 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 04D2B3A6BDF;
	Mon, 11 Feb 2008 05:59:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.708
X-Spam-Level: 
X-Spam-Status: No, score=-0.708 tagged_above=-999 required=5
	tests=[AWL=-0.271, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, 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 dmog+QAU4Dwp; Mon, 11 Feb 2008 05:59:48 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 149263A6BC5;
	Mon, 11 Feb 2008 05:59:48 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 33EBA3A69D5
	for <nsis@core3.amsl.com>; Mon, 11 Feb 2008 05:59:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 F6eqrbfVDWNw for <nsis@core3.amsl.com>;
	Mon, 11 Feb 2008 05:59:45 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id 938B73A6AB1
	for <nsis@ietf.org>; Mon, 11 Feb 2008 05:59:00 -0800 (PST)
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id ADEC62C000357
	for <nsis@ietf.org>; Mon, 11 Feb 2008 15:00:25 +0100 (CET)
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 h8QehzxMUx3z for <nsis@ietf.org>;
	Mon, 11 Feb 2008 15:00:25 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id 9D78B2C000355
	for <nsis@ietf.org>; Mon, 11 Feb 2008 15:00:20 +0100 (CET)
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Mon, 11 Feb 2008 15:00:19 +0100
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF4D0A45@mx1.office>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Index: AchstnAHgWCZvKqhTFyaX2iRIS97Og==
From: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>
To: <nsis@ietf.org>
Subject: [NSIS] (no subject)
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <http://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: <http://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 all,

You have seen some e-mails about QoS and the QSPEC reviews and the NATFW NSLP in the last few days. We are getting some progress towards the core documents. 

Some people might now also ask about the current status of the NSIS WG and here is the status.

* The list of milestones will be updated soon to reflect the current progress of all WG items.

* GIST: All comments seem to be handled, the draft has been updated and it is now up to Magnus.

* QoS NSLP: Finished WGLC some time back. There has been a review of the latest draft and the draft has been updated.

* QSEPC: Finished WGLC some time back. There has been a review of the latest draft and the authors need to response to the review.

* NATFW NSLP: WGLC is about to finish. A new version of the draft has been posted to the list, i.e., the draft is waiting for people to review it onces (if all changes have been implemented correctly).

* Mobility Appl. draft: This draft is still under discussion and we probably need to foster it a bit in the next weeks.

* RMD QOSM: WGLC finished. Waiting for updated draft.

* Y.1541 QOSM: WGLC finished. Waiting for updated draft.

* Tunnel operations: This draft is still under discussion and we probably need to foster it a bit in the next weeks.

* GIST SCTP: This draft is still under discussion and we probably need to foster it a bit in the next weeks.

* Extensibility document: John has posted the first WG version of this right before the last IETF meeting in December. Have people read it yet, i.e., this draft should be und discussion and we definitely need to foster it a bit in the next weeks.

What comes next towards the IESG: The QoS NSLP and the QSPEC will be sent together to Magnus for AD review (and later on to IESG), once they are both available in updated versions. Afterwards, the NATFW NSLP will follow, given that the WG is fine with the current update.

Thanks,

  John and 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 
_______________________________________________
nsis mailing list
nsis@ietf.org
http://www.ietf.org/mailman/listinfo/nsis


From nsis-bounces@ietf.org  Tue Feb 12 00:38:23 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ABEF728C112;
	Tue, 12 Feb 2008 00:38:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.663
X-Spam-Level: 
X-Spam-Status: No, score=-0.663 tagged_above=-999 required=5
	tests=[AWL=-0.226, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, 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 FX02+IcoYXNb; Tue, 12 Feb 2008 00:38:22 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D0C763A6E1F;
	Tue, 12 Feb 2008 00:38:22 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1173A3A6E1F
	for <nsis@core3.amsl.com>; Tue, 12 Feb 2008 00:38:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 Xee0812eJhO8 for <nsis@core3.amsl.com>;
	Tue, 12 Feb 2008 00:38:21 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id DBA1D3A6E01
	for <nsis@ietf.org>; Tue, 12 Feb 2008 00:38:20 -0800 (PST)
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 654472C002B4A
	for <nsis@ietf.org>; Tue, 12 Feb 2008 09:39:45 +0100 (CET)
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 8kB641To9Het for <nsis@ietf.org>;
	Tue, 12 Feb 2008 09:39:45 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id 4ABFE2C000357
	for <nsis@ietf.org>; Tue, 12 Feb 2008 09:39:40 +0100 (CET)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 12 Feb 2008 09:39:39 +0100
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF4D0AE3@mx1.office>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New WG milestones
Thread-Index: AchtUs40n+w238O/R5mYKkG8xh5+Hw==
From: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>
To: <nsis@ietf.org>
Subject: [NSIS] New WG milestones
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <http://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: <http://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 all,

We have a set of updated milestones which should be available on the charter page soon. However, here are already the update milestones.

Thanks,

  Martin

Current Milestones
++++++++++++++++++
Done              Submit 'Signaling Requirements' to IESG for
publication as an Informational RFC.
Done              Submit 'Next Steps in Signaling: Framework' to
IESG for publication as Informational RFC
Done              Submit 'Analysis of Existing Signaling
Protocols' to IESG as Informational RFC
Done              Submit 'RSVP Security Properties' to IESG as
Informational RFC
Done              Submit 'NSIS Threats' to IESG as Informational
RFC
Done              Submit 'NSIS Transport Protocol' to IESG for
publication for Proposed Standard
Jun 2006          Submit 'NSIS QoS Specification Template' to IESG
for publication as an Informational RFC
Jun 2006          Submit 'NSIS QoS Application Protocol' to IESG
for publication for Proposed Standard
Jul 2006          Submit 'NSIS Middle Box Signaling Application
Protocol' to IESG for publication for Proposed Standard
Jul 2006          Submit 'Differentiated Service Signaling on the
Internet' to the IESG for
            publication as an Informational RFC
Jul 2006          Submit 'Y.1541 QoS Model' to the IESG for
publication as an Informational RFC
Nov 2006          Submit 'Applicability Statement of NSIS
Protocols in Mobile Environments' to the
            IESG as an Informational RFC
Dec 2006          Submit 'General Internet Signaling Transport
protocol implementation document'
            to the IESG for publication as an Informational RFC



New Milestones
++++++++
Done              Submit 'Signaling Requirements' to IESG for
publication as an Informational RFC.
Done              Submit 'Next Steps in Signaling: Framework' to
IESG for publication as Informational RFC
Done              Submit 'Analysis of Existing Signaling
Protocols' to IESG as Informational RFC
Done              Submit 'RSVP Security Properties' to IESG as
Informational RFC
Done              Submit 'NSIS Threats' to IESG as Informational
RFC
Done              Submit 'NSIS Transport Protocol' to IESG for
publication for Proposed Standard
Feb 2008          Submit 'NSIS QoS Specification Template' to IESG
for publication as an Informational RFC
Feb 2008          Submit 'NSIS QoS Application Protocol' to IESG
for publication for Proposed Standard
Mar 2008          Submit 'NSIS Middle Box Signaling Application
Protocol' to IESG for publication for Proposed Standard
Sep 2008          Submit 'RMD-QOSM - The Resource Management in
Diffserv QOS Model' to the IESG for
               publication as an Informational RFC
Sep 2008          Submit 'Y.1541 QoS Model' to the IESG for
publication as an Informational RFC

Sep 2008          Submit 'Applicability Statement of NSIS
Protocols in Mobile Environments' to the IESG as an Informational RFC
Nov 2008          Submit 'GIST State Machine' to the IESG for
publication as an Informational RFC
Nov 2008          Submit 'NSIS Operation Over IP Tunnels' to the
IESG for publication as an Informational RFC
Dec 2008          Submit 'NSIS Extensibility Model' to the IESG for
publication as an Informational RFC	



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 
_______________________________________________
nsis mailing list
nsis@ietf.org
http://www.ietf.org/mailman/listinfo/nsis


From nsis-bounces@ietf.org  Thu Feb 14 02:16:47 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AEEA828CE0C;
	Thu, 14 Feb 2008 02:16:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.627
X-Spam-Level: 
X-Spam-Status: No, score=-0.627 tagged_above=-999 required=5
	tests=[AWL=-0.190, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, 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 jXRwRYo0H3UE; Thu, 14 Feb 2008 02:16:46 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 42E4328CDC8;
	Thu, 14 Feb 2008 02:16:46 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AAB1E28CDD8
	for <nsis@core3.amsl.com>; Thu, 14 Feb 2008 02:16:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 RNxJzx+C0Bxk for <nsis@core3.amsl.com>;
	Thu, 14 Feb 2008 02:16:43 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id 51DBF28CDCB
	for <nsis@ietf.org>; Thu, 14 Feb 2008 02:16:43 -0800 (PST)
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 47A1C2C009E8F
	for <nsis@ietf.org>; Thu, 14 Feb 2008 11:18:05 +0100 (CET)
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 Zrj7bwAi-mNf for <nsis@ietf.org>;
	Thu, 14 Feb 2008 11:18:05 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id 16F762C000357
	for <nsis@ietf.org>; Thu, 14 Feb 2008 11:18:00 +0100 (CET)
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_01C86EF2.D8AABEF9"
Date: Thu, 14 Feb 2008 11:17:47 +0100
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF4D0D5B@mx1.office>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: I-D Action:draft-manner-router-alert-iana-01.txt 
Thread-Index: AchugenRyhPyHH6YTC+05E3fID6pugAcKG8w
From: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>
To: <nsis@ietf.org>
Subject: [NSIS] FW: I-D Action:draft-manner-router-alert-iana-01.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: <http://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: <http://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_01C86EF2.D8AABEF9
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

FYI, as this draft is important to NSIS. Please take a look and comment =
if necessary.

Jukka has presented this draft during the last IETF meeting at the INT =
area open meeting and received some positive feedback. The new version =
of the draft incorporates the changes.=20

Jukka will present the update again at the INT area open meeting. It =
would be good to have some of the NSIS people attending this session.

Thanks,

  Martin


> -----Original Message-----
> From: i-d-announce-bounces@ietf.org=20
> [mailto:i-d-announce-bounces@ietf.org] On Behalf Of=20
> Internet-Drafts@ietf.org
> Sent: Wednesday, February 13, 2008 9:45 PM
> To: i-d-announce@ietf.org
> Subject: I-D Action:draft-manner-router-alert-iana-01.txt=20
>=20
> A New Internet-Draft is available from the on-line=20
> Internet-Drafts directories.
>=20
> 	Title           : IANA Considerations for the IPv4 and=20
> IPv6 Router Alert Option
> 	Author(s)       : A. McDonald, J. Manner
> 	Filename        : draft-manner-router-alert-iana-01.txt
> 	Pages           : 8
> 	Date            : 2008-02-13
>=20
> This document provides new instructions to IANA on the allocation of
> IPv4 and IPv6 Router Alert Option Values.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-manner-router-alert-
> iana-01.txt
>=20
> To remove yourself from the I-D Announcement list, send a=20
> message to i-d-announce-request@ietf.org with the word=20
> unsubscribe in the body of the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>=20
> Internet-Drafts are also available by anonymous FTP. Login=20
> with the username "anonymous" and a password of your e-mail=20
> address. After logging in, type "cd internet-drafts" and then
> 	"get draft-manner-router-alert-iana-01.txt".
>=20
> A list of Internet-Drafts directories can be found in=20
> http://www.ietf.org/shadow.html or=20
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-manner-router-alert-iana-01.txt".
>=20
> NOTE:   The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant=20
> mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>=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

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

------_=_NextPart_001_01C86EF2.D8AABEF9
Content-Type: application/octet-stream;
	name="ATT08109.TXT"
Content-Transfer-Encoding: base64
Content-Description: ATT08109.TXT
Content-Disposition: attachment;
	filename="ATT08109.TXT"

Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7DQoJYWNjZXNzLXR5cGU9Im1haWwt
c2VydmVyIjsNCglzZXJ2ZXI9Im1haWxzZXJ2QGlldGYub3JnIg0KDQpDb250ZW50LVR5cGU6IHRl
eHQvcGxhaW4NCkNvbnRlbnQtSUQ6IDwyMDA4LTAyLTEzMTIzNzA5LkktREBpZXRmLm9yZz4NCg0K
RU5DT0RJTkcgbWltZQ0KRklMRSAvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LW1hbm5lci1yb3V0ZXIt
YWxlcnQtaWFuYS0wMS50eHQNCg==

------_=_NextPart_001_01C86EF2.D8AABEF9
Content-Type: application/octet-stream;
	name="draft-manner-router-alert-iana-01.URL"
Content-Transfer-Encoding: base64
Content-Description: draft-manner-router-alert-iana-01.URL
Content-Disposition: attachment;
	filename="draft-manner-router-alert-iana-01.URL"

W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC1tYW5uZXItcm91dGVyLWFsZXJ0LWlhbmEtMDEudHh0DQo=

------_=_NextPart_001_01C86EF2.D8AABEF9
Content-Type: text/plain;
	name="ATT08110.txt"
Content-Transfer-Encoding: base64
Content-Description: ATT08110.txt
Content-Disposition: attachment;
	filename="ATT08110.txt"

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v
dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cDovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ktZC1hbm5vdW5jZQ0K

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

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

------_=_NextPart_001_01C86EF2.D8AABEF9--


From nsis-bounces@ietf.org  Thu Feb 14 02:58:24 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5173928CE2E;
	Thu, 14 Feb 2008 02:58:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.64
X-Spam-Level: 
X-Spam-Status: No, score=-0.64 tagged_above=-999 required=5 tests=[AWL=-0.203,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	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 oNMO7NpBzchE; Thu, 14 Feb 2008 02:58:23 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 866BB28CE1D;
	Thu, 14 Feb 2008 02:58:23 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0505A28CD4E
	for <nsis@core3.amsl.com>; Thu, 14 Feb 2008 02:58:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 h-yldVCy+mcT for <nsis@core3.amsl.com>;
	Thu, 14 Feb 2008 02:58:21 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id 2D28728CE12
	for <nsis@ietf.org>; Thu, 14 Feb 2008 02:58:21 -0800 (PST)
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 0198C2C009E8E
	for <nsis@ietf.org>; Thu, 14 Feb 2008 11:59:43 +0100 (CET)
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 S5PxUuH2k7Um for <nsis@ietf.org>;
	Thu, 14 Feb 2008 11:59:42 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id E574D2C000357
	for <nsis@ietf.org>; Thu, 14 Feb 2008 11:59:37 +0100 (CET)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 14 Feb 2008 11:59:37 +0100
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF4D0D73@mx1.office>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Call for agenda items for IETF#71
Thread-Index: Achu+LCRsvE2hVOTRoW1Yewqf227AQ==
From: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>
To: <nsis@ietf.org>
Subject: [NSIS] Call for agenda items for IETF#71
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <http://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: <http://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 all,

It is time again to set the agenda for the upcoming IETF meeting. 

I'm planning to split the session in

1) WG update and update on WG documents close to AD review or beyond this stage. Those WG documents will (hopefully) just need some wrap-up without presentation. If needed, we will go for separate presentation (e.g., if there is any IESG feedback about GIST)

2) Discussion about WG items still with the WG (e.g., mobility appl. statement, tunnel, etc)

3) Implementation reports: If any of the implementors can briefly report about their current implementations.

4) if time permits: discussions of individual drafts.

Thus, if you are interested in having a presentation slot at the NSIS session, please send the following information to nsis-chairs@tools.ietf.org until 

  **February 24th, 5PM PST**

The request must contain this information:

draft name,
presenter's name,
requested duration.



Thanks,

  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 
_______________________________________________
nsis mailing list
nsis@ietf.org
http://www.ietf.org/mailman/listinfo/nsis


From nsis-bounces@ietf.org  Thu Feb 14 03:25:37 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A2D5028CDC8;
	Thu, 14 Feb 2008 03:25:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.628
X-Spam-Level: 
X-Spam-Status: No, score=-0.628 tagged_above=-999 required=5
	tests=[AWL=-0.191, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, 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 8Fj2Nd2Fe5ag; Thu, 14 Feb 2008 03:25:36 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA19B3A7037;
	Thu, 14 Feb 2008 03:25:36 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D937D3A7037
	for <nsis@core3.amsl.com>; Thu, 14 Feb 2008 03:25:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 DfdVrGx9Czyy for <nsis@core3.amsl.com>;
	Thu, 14 Feb 2008 03:25:35 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id E687A3A6EEF
	for <nsis@ietf.org>; Thu, 14 Feb 2008 03:25:34 -0800 (PST)
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id B647B2C009E8E
	for <nsis@ietf.org>; Thu, 14 Feb 2008 12:26:56 +0100 (CET)
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 lUYKatMfRVkw for <nsis@ietf.org>;
	Thu, 14 Feb 2008 12:26:56 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id A5BC42C000357
	for <nsis@ietf.org>; Thu, 14 Feb 2008 12:26:51 +0100 (CET)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 14 Feb 2008 12:26:51 +0100
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF4D0D82@mx1.office>
In-Reply-To: <C3C65798.EA7B%Stiemerling@nw.neclab.eu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Supplemental web page about NSIS implementations
Thread-Index: AchjVZv12tBVXc9IEdybRgAWy5Ti1QLpqqEw
References: <C3C65798.EA7B%Stiemerling@nw.neclab.eu>
From: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>
To: <nsis@ietf.org>
Subject: Re: [NSIS] Supplemental web page about NSIS implementations
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <http://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: <http://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 all,

The supplemental web page has been updated with all known implementations and the NSIS dissectors for wireshark:

http://ietf.stiemerling.org

  Martin


> -----Original Message-----
> From: Martin Stiemerling [mailto:Stiemerling@nw.neclab.eu] 
> Sent: Wednesday, January 30, 2008 4:35 PM
> To: nsis
> Subject: [NSIS] Supplemental web page about NSIS implementations
> 
> Dear all,
> 
> There is now a supplemental web page summarizing the available NSIS
> implementations:
> 
> ietf.stiemerling.org/
> 
> It is not complete yet but will be filled in the next hours.
> 
>   Martin
> 
> 
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www1.ietf.org/mailman/listinfo/nsis
> 

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  
_______________________________________________
nsis mailing list
nsis@ietf.org
http://www.ietf.org/mailman/listinfo/nsis


From nsis-bounces@ietf.org  Fri Feb 15 04:00:04 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AFBBE28D1A5;
	Fri, 15 Feb 2008 04:00:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,
	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 nvH9-zrEiTsz; Fri, 15 Feb 2008 04:00:03 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BC2C828D18A;
	Fri, 15 Feb 2008 04:00:03 -0800 (PST)
X-Original-To: nsis@ietf.org
Delivered-To: nsis@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 62CFF28CA21; Fri, 15 Feb 2008 04:00:01 -0800 (PST)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080215120001.62CFF28CA21@core3.amsl.com>
Date: Fri, 15 Feb 2008 04:00:01 -0800 (PST)
Cc: nsis@ietf.org
Subject: [NSIS] I-D Action:draft-ietf-nsis-nslp-natfw-18.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: <http://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: <http://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           : NAT/Firewall NSIS Signaling Layer Protocol (NSLP)
	Author(s)       : M. Stiemerling, et al.
	Filename        : draft-ietf-nsis-nslp-natfw-18.txt
	Pages           : 89
	Date            : 2008-02-15

This memo defines the NSIS Signaling Layer Protocol (NSLP) for
Network Address Translators (NATs) and firewalls.  This NSLP allows
hosts to signal on the data path for NATs and firewalls to be
configured according to the needs of the application data flows.  For
instance, it enables hosts behind NATs to obtain a public reachable
address and hosts behind firewalls to receive data traffic.  The
overall architecture is given by the framework and requirements
defined by the Next Steps in Signaling (NSIS) working group.  The
network scenarios, the protocol itself, and examples for path-coupled
signaling are given in this memo.

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

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-nsis-nslp-natfw-18.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-nsis-nslp-natfw-18.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-nsis-nslp-natfw-18.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-nsis-nslp-natfw-18.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-02-15034911.I-D\@ietf.org>


--OtherAccess--

--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
http://www.ietf.org/mailman/listinfo/nsis

--NextPart--


From nsis-bounces@ietf.org  Fri Feb 15 04:16:05 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E98E53A6A9A;
	Fri, 15 Feb 2008 04:16:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.679
X-Spam-Level: 
X-Spam-Status: No, score=-0.679 tagged_above=-999 required=5
	tests=[AWL=-0.242, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, 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 QfKYlEZzyl5V; Fri, 15 Feb 2008 04:16:05 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0A6103A6A82;
	Fri, 15 Feb 2008 04:16:05 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 081C53A68AE
	for <nsis@core3.amsl.com>; Fri, 15 Feb 2008 04:16:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 Dn6QZ1hnPaVJ for <nsis@core3.amsl.com>;
	Fri, 15 Feb 2008 04:16:02 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id 6CEC13A6A6E
	for <nsis@ietf.org>; Fri, 15 Feb 2008 04:16:02 -0800 (PST)
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 1A25F2C009E8F
	for <nsis@ietf.org>; Fri, 15 Feb 2008 13:17:23 +0100 (CET)
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 KcfTWocQHVfh for <nsis@ietf.org>;
	Fri, 15 Feb 2008 13:17:22 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id EE8B42C000357
	for <nsis@ietf.org>; Fri, 15 Feb 2008 13:17:17 +0100 (CET)
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_01C86FCC.B4E5FB87"
Date: Fri, 15 Feb 2008 13:17:17 +0100
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF4D0E87@mx1.office>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] I-D Action:draft-ietf-nsis-nslp-natfw-18.txt
Thread-Index: AchvyqyJmY7+fMzERICThuMb3pW+eAAAZVJA
From: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>
To: <nsis@ietf.org>
Subject: [NSIS] FW:  I-D Action:draft-ietf-nsis-nslp-natfw-18.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: <http://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: <http://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_01C86FCC.B4E5FB87
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

(writing chair's hat off)

Hi all,

Just FYI there is a new draft of the NATFW NSLP. Andrew pointed out in a =
private email that there was no text in the IANA section for the to be =
assigned IPv4 and IPv6 RAO values. The text has now been added.

This has been changed or added to the IANA considerations section:

OLD
   Furthermore, IANA is requested to add a new value to the NSLP
   Identifiers (NSLPID) registry defined in [2] for the NATFW NSLP.

NEW
   GIST NSLPID

   This specification defines an NSLP for use with GIST and thus
   requires an assigned NSLP identifier.  IANA is requested to add a new
   value to the NSLP Identifiers (NSLPID) registry defined in [2] for
   the NATFW NSLP.

   IPv4 and IPv6 Router Alert Option (RAO) value

   The GIST specification also requires that each NSLP-ID be associated
   with specific Router Alert Option (RAO) value.  For the purposes of
   the NATFW NSLP, just a single IPv4 RAO value and a single IPv6 RAO
   must be allocated.


  Martin


> -----Original Message-----
> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On=20
> Behalf Of Internet-Drafts@ietf.org
> Sent: Friday, February 15, 2008 1:00 PM
> To: i-d-announce@ietf.org
> Cc: nsis@ietf.org
> Subject: [NSIS] I-D Action:draft-ietf-nsis-nslp-natfw-18.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
>=20
> 	Title           : NAT/Firewall NSIS Signaling Layer=20
> Protocol (NSLP)
> 	Author(s)       : M. Stiemerling, et al.
> 	Filename        : draft-ietf-nsis-nslp-natfw-18.txt
> 	Pages           : 89
> 	Date            : 2008-02-15
>=20
> This memo defines the NSIS Signaling Layer Protocol (NSLP)=20
> for Network Address Translators (NATs) and firewalls.  This=20
> NSLP allows hosts to signal on the data path for NATs and=20
> firewalls to be configured according to the needs of the=20
> application data flows.  For instance, it enables hosts=20
> behind NATs to obtain a public reachable address and hosts=20
> behind firewalls to receive data traffic.  The overall=20
> architecture is given by the framework and requirements=20
> defined by the Next Steps in Signaling (NSIS) working group. =20
> The network scenarios, the protocol itself, and examples for=20
> path-coupled signaling are given in this memo.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-nslp-natfw-18.txt
>=20
> To remove yourself from the I-D Announcement list, send a=20
> message to i-d-announce-request@ietf.org with the word=20
> unsubscribe in the body of the message.
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
> to change your subscription settings.
>=20
> Internet-Drafts are also available by anonymous FTP. Login=20
> with the username "anonymous" and a password of your e-mail=20
> address. After logging in, type "cd internet-drafts" and then
> 	"get draft-ietf-nsis-nslp-natfw-18.txt".
>=20
> A list of Internet-Drafts directories can be found in=20
> http://www.ietf.org/shadow.html or=20
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-nsis-nslp-natfw-18.txt".
>=20
> NOTE:   The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant=20
> mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
>=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

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

------_=_NextPart_001_01C86FCC.B4E5FB87
Content-Type: application/octet-stream;
	name="ATT33331.TXT"
Content-Transfer-Encoding: base64
Content-Description: ATT33331.TXT
Content-Disposition: attachment;
	filename="ATT33331.TXT"

Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7DQoJYWNjZXNzLXR5cGU9Im1haWwt
c2VydmVyIjsNCglzZXJ2ZXI9Im1haWxzZXJ2QGlldGYub3JnIg0KDQpDb250ZW50LVR5cGU6IHRl
eHQvcGxhaW4NCkNvbnRlbnQtSUQ6IDwyMDA4LTAyLTE1MDM0OTExLkktREBpZXRmLm9yZz4NCg0K
RU5DT0RJTkcgbWltZQ0KRklMRSAvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtbnNpcy1uc2xw
LW5hdGZ3LTE4LnR4dA0K

------_=_NextPart_001_01C86FCC.B4E5FB87
Content-Type: application/octet-stream;
	name="draft-ietf-nsis-nslp-natfw-18.URL"
Content-Transfer-Encoding: base64
Content-Description: draft-ietf-nsis-nslp-natfw-18.URL
Content-Disposition: attachment;
	filename="draft-ietf-nsis-nslp-natfw-18.URL"

W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC1pZXRmLW5zaXMtbnNscC1uYXRmdy0xOC50eHQNCg==

------_=_NextPart_001_01C86FCC.B4E5FB87
Content-Type: text/plain;
	name="ATT33332.txt"
Content-Transfer-Encoding: base64
Content-Description: ATT33332.txt
Content-Disposition: attachment;
	filename="ATT33332.txt"

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm5zaXMgbWFp
bGluZyBsaXN0DQpuc2lzQGlldGYub3JnDQpodHRwOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vbnNpcw0K

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

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

------_=_NextPart_001_01C86FCC.B4E5FB87--


From nsis-bounces@ietf.org  Fri Feb 15 08:08:22 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6F1AE3A6ACA;
	Fri, 15 Feb 2008 08:08:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.43
X-Spam-Level: 
X-Spam-Status: No, score=-2.43 tagged_above=-999 required=5 tests=[AWL=0.169,
	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 F8vEJMMtlCyj; Fri, 15 Feb 2008 08:08:21 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6E38E28D219;
	Fri, 15 Feb 2008 08:08:13 -0800 (PST)
X-Original-To: nsis@ietf.org
Delivered-To: nsis@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30)
	id EDB763A6B23; Fri, 15 Feb 2008 08:08:11 -0800 (PST)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20080215160811.EDB763A6B23@core3.amsl.com>
Date: Fri, 15 Feb 2008 08:08:11 -0800 (PST)
Cc: nsis@ietf.org
Subject: [NSIS] Last Call: draft-ietf-nsis-ntlp (GIST: General Internet
 Signalling Transport) to Proposed Standard
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

The IESG has received a request from the Next Steps in Signaling WG 
(nsis) to consider the following document:

- 'GIST: General Internet Signalling Transport '
   <draft-ietf-nsis-ntlp-15.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2008-03-08. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-nsis-ntlp-15.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=11113&rfc_flag=0

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


From nsis-bounces@ietf.org  Fri Feb 15 08:55:02 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8663628D291;
	Fri, 15 Feb 2008 08:55:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.162
X-Spam-Level: **
X-Spam-Status: No, score=2.162 tagged_above=-999 required=5 tests=[AWL=-0.488,
	BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_MESSAGE=1, MIME_HTML_MOSTLY=0.001, RDNS_NONE=0.1,
	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 NMzyoBQYI9N3; Fri, 15 Feb 2008 08:54:59 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D920A3A68D3;
	Fri, 15 Feb 2008 08:54:57 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5765E3A6874
	for <nsis@core3.amsl.com>; Fri, 15 Feb 2008 08:54:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 TRkVDr8Yb2oD for <nsis@core3.amsl.com>;
	Fri, 15 Feb 2008 08:54:53 -0800 (PST)
Received: from web63604.mail.re1.yahoo.com (web63604.mail.re1.yahoo.com
	[69.147.97.74]) by core3.amsl.com (Postfix) with SMTP id 2E14A28D19B
	for <nsis@ietf.org>; Fri, 15 Feb 2008 08:53:53 -0800 (PST)
Received: (qmail 36606 invoked by uid 60001); 15 Feb 2008 16:55:10 -0000
X-YMail-OSG: 174X8CQVM1kzoZuEumFA999URtsx_EWI9YuApYgv
Received: from [76.19.255.157] by web63604.mail.re1.yahoo.com via HTTP;
	Fri, 15 Feb 2008 08:55:10 PST
Date: Fri, 15 Feb 2008 08:55:10 -0800 (PST)
From: Gerald Ash <gash5107@yahoo.com>
To: Martin Stiemerling <Stiemerling@nw.neclab.eu>, nsis <nsis@ietf.org>
In-Reply-To: <C3C61BFC.EA3F%Stiemerling@nw.neclab.eu>
MIME-Version: 1.0
Message-ID: <370957.34791.qm@web63604.mail.re1.yahoo.com>
Cc: cornelia.kappler@googlemail.com
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1345112473=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

--===============1345112473==
Content-Type: multipart/alternative; boundary="0-66703516-1203094510=:34791"
Content-Transfer-Encoding: 8bit

--0-66703516-1203094510=:34791
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Martin,

Many thanks for your careful review.

Please see comments in line below.

Please let us know of any further comments.  We'll resubmit the document
prior to cutoff date.

Jerry

> Hi all,
>
> Please find my review of draft-ietf-nsis-qspec-18.txt.
>
> There are some minor technical issues to fix. In general the document
> seems
> to be ready to go for AD review,  once the editorials and technical
> issues
> have been fixed.
>
> Please address the issues and submit an updated version of the draft if
> d
> one so. I will go ahead with the updated draft for the protocol write
> up
> (i.e., the step before sending to Magnus and the IESG).
>
>  Martin
>
> ****
> General
> ****
> I found the first part of the document (i.e., until section 5) quite
> confusing and after section five quite clear. This does not mean that
> there
> is an issue, as typically Internet drafts have the need to sketch tech
> things in the beginning without having the reader already at the
> technical
> level. I assume that the text is fine right now, as the WG has not
> pushed to
> change it.

These sections have been rewritten many times.  Please let us know if you
have any particular suggestion to improve clarity.

>
> ****
> Editorial:
> ****
>
> - the idnits tool has found some issues (see below)

OK, will address.

> - Add line in memo heading with: Intended Status: Informational

Although the NSIS milestone says "Informational", the ID tracker lists the
status as "Proposed Standard"
https://datatracker.ietf.org/idtracker/draft-ietf-nsis-qspec/.  IMO the
QSPEC document should be a PS document, in close alignment with the 
  NSLP PS document.  Many IANA registries are created, etc.  I can't see the
  rationale for NSLP being PS and QSPEC being Informational.  I do recall a 
  discussion on this point earlier and several WG members expressed the same
  view.  Perhaps the WG members and chairs can comment.

> -  Section 1: Move to the very end of memo. It it is good to
> acknowledge
> other people, but it is fair enough to do it at the very end, as
> technical
> protocol stuff comes first.

OK.

> - section 2: Adding a line saying that QSPEC readers should (or better
> must?) read the QoS NSLP in advance would be advantageous for the whole
> document.

Note that the first sentence of Section 2 references QoS NSLP since the
documents are closely tied.  The QSPEC document is intended to be (and
should be) self contained so that one doesn't have to ("must") read
something else first before reading and understanding QSPEC.  However, your 
point is well taken.  We can add a sentence in Section 2 such as "See
  [QoS-SIG] for further details on QoS NSLP."

> - section 2, page 5, para starting with "Interoperability between QoS
> NSIS
> entities (QNEs)..." says that parameters can be flagged or not flagged.
> I
> suggest to put the terms "flagged"/"non flagged" in brackets and write
> mandatory and optional parameters. This makes it easier for first time
> readers.

We've eliminated the terminology "mandatory" and "optional" parameters.
Parameters can be flagged by the M flag if they MUST be interpreted, or
otherwise, as follows:

 M Flag: When set indicates the subsequent parameter MUST be
           interpreted. Otherwise the parameter can be ignored if not
           understood.

We don't want to get back into the mandatory/optional terminology at this
point.

> - - section 2, page 5, para starting with " A local QSPEC can be
> defined in
> a local domain with the initiator QSPEC encapsulated, ...". This
> paragraph
> is brief but describes a very powerful mechanism of the QSPEC. I would
> suggest to remove the hint the TMOD parameter and just write that the
> QSPEC
> allows local QPSECs that are domain specific. This also helps first
> time
> readers to understand a basic feature of  QPSEC but not the full
> implementation of it.

OK.

> - section 4.1, 2nd para, text in para starting with " New QoS NSLP
> message
> processing rules can only be defined in Standard...". Is it required to
> say
> this at this part of the document at all? I remember this again stated
> in
> the document somewhere later on at an appropriate place.

It's an important point and I think it appropriate to mention it in Section 
4.1.  Furthermore, I recall extensive discussion on this sentence and I 
  believe it was explicitly agreed to include it here as well as later in the
  document.  Also, mentioning important points more than once often helps
  clarity.

> - section 4.2 two paras below figure 1. Suddenly there is text about
> RESERVE
> and QUERY, but no hint to the QoS NSLP at all. Adding a reference to
> the QoS
> NSLP at this occasion would be excellent. Otherwise it  is hard to see
> where
> those terms are coming from

Good point, will do.

> - section 4.3.1, para starting with " When the TMOD parameter in
> included in
> QoS Available, it..." should read " When the TMOD parameter are
> included in
> QoS Available, it..."

I think the English is correct as it stands.  However, we could say "When
the TMOD sub-parameters are included ..."

> - section 4.3.1. This section nevers talks about tmod-2! tmod-2 is
> mentioned only  in sections 6.2.1 and 6.2.2.

Right, good point.  We'll revise the text to refer to TMOD-1 and TMOD-2 and
explain the difference.  We could include the example of the need for the 
TMOD-2 parameter in Section 4.3.1 (see discussion/example below of the need 
for the TMOD-2 parameter).

> - section 5, 1st and 2nd para suddenly use the E-/N-flag without every
> explaining their meaning.

Well, this is where the M flag, E flag, and N flag are being explained.  The
first paragraph introduces them and there are details later.  We could add
text in the beginning such as "Three flags are used in QSPEC, the M flag, E
flag, and N flag, which are explained in this section."

> - section 5.1, again the support of local QSPECs is quite powerful but
> never
> really good explained with a figure. For instance, the first para of
> section
> 5.1 could refer to a simple figure showing a network configuration for
> a
> single flow, but with indications where which QSPEC is used. This
> instantly
> makes the whole concept better undestandable.

OK, we could add a figure analogous to Figure 3 in the Y.1541-QOSM document
http://www.ietf.org/internet-drafts/draft-ietf-nsis-y1541-qosm-05.txt to
explain the concept.

> - section 5.2.5. formatting error

OK.

> - section 5.3.1 and related. You use tables to define cases and also
> refer
> to them later in the object definition. Thus it would be good to label
> those
> tables.

OK, good suggestion.

> - section 5.3.5 has one formatting issue and one spelling error
> (s/described
> In [QoS-SIG]/ described in [QoS-SIG])

OK.

> - section 5.4. remove reference to NSIS extensibility document, as we
> do not
> have it ready by now.

OK.

> - section 6.1. I got confused by all the different header definition. I
> would propose to split 6.1. in subsections, i.e., one for each header
> definition. This improves readability.

OK, good suggestion.

> - section 6.2.1: Why is there this line    <TMOD-1> = <r> <b> <p> <m>
> [RFC2210, RFC2215]? It is now required for the object definition.

Right, the format is inconsistent with the other subsections and will be
revised accordingly.

> - section 8, text says " Object Types (12 bits):" but should read
> "QSPEC
> Object Types (12 bits):".

But then Section 6.1 would have to be revised to be consistent in
terminology.  While I have no big objection to changing all of this, IMO it
should stay as is; I think it is clear that this is a QSPEC object type.

> - appendix b: add a note in the first line that this appendix should be
> removed by the RFC editor before publication.

OK.

>
>
>
> ***
> Technical
> ***
> - section 5.3.1, para starting with " The QSPEC parameter IDs and
> values
> included in the QoS Reserved...". This paragraph talks about how to set
> the
> parameters in the RESPONSE message for case 2. It is basically fine,
> but the
> second sentence is for me not understandable (" For those QSPEC
> parameters
> that were also included in the QoS Available object in the RESERVE
> message,
> their value is copied into the QoS Desired object.")
> The paragraph is talking about responses, but in RESPONSE there is no
> QoS
> desired object anymore (at least according to the table above). I
> probably
> do misunderstand something here?

Good catch.  The sentence needs to be corrected.  It should be: "For those
QSPEC parameters that were also included in the QoS Available object in the
RESERVE message, their value is copied from the QoS Available object (in
RESERVE) into the QoS Reserved object (in RESPONSE) ."

> - section 6.1 qspec header element definition. The length definition in
> the
> qspec header definition contradicts the length definition at the
> beginning
> of section 6.1 One says "total length of qspec" the other "length is
> always
> exept header"

Very good catch!  IMO the section definition should be revised as
follows:

 Length: The total length of the QSPEC -->
 Length: The total length of the QSPEC excluding the common header

> - section 6.2.2., see also my comment above about tmod-2. Even after
> reading
> section 6.2.2. I do not have any clue why there two tmod parameters.

This is based on discussions with David Black, who recommended the second
TMOD parameter to support DiffServ applications (as noted in Section 6.2.2).
Earlier versions of QSPEC included the following example (due to David), 
which can be added back into the draft (probably in Section 4.3.1):

"It is typically assumed that DiffServ EF traffic is shaped at the ingress
by a single rate token bucket.  Therefore, a single TMOD parameter is
sufficient to signal DiffServ EF traffic.  However, for DiffServ AF traffic
two sets of token bucket parameters are needed, one token bucket for the
average traffic and one token bucket for the burst traffic.  [RFC2697]
defines a Single Rate Three Color Marker (srTCM), which meters a traffic
stream and marks its packets according to three traffic parameters,
Committed Information Rate (CIR), Committed Burst Size (CBS), and Excess
Burst Size (EBS), to be either green, yellow, or red.  A packet is marked
green if it does not exceed the CBS, yellow if it does exceed the CBS, but
not the EBS, and red otherwise.  [RFC2697] defines specific procedures using
two token buckets that run at the same rate.  Therefore 2 TMOD parameters
are sufficient to distinguish among 3 levels of drop precedence.  An example
is also described in the Appendix to [RFC2597]."

Also, the first sentence in Section 6.2.2 should be changed slightly to: ''A
second, QSPEC <TMOD-2> parameter is specified, as could be needed for
example to support some Diffserv applications." (added word "some").

> - section 6.2.7. The slack term is 32 bits as integer. However the
> slack
> term must only be non-negative, i.e., it is actually an unsigned int.
> Why is
> is not specified as unsigned int? However, the current value range
> definition is broken, as an integer of 32 bits cannot have a maximum
> range
> to  2**32-1 (there are only 31 bits left...).

The coding of the slack term is based on RSVP coding:

RFC 2210 says:

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
11  |  Slack Term [S]  (32-bit integer)                             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

RFC 2212 says:
"The Slack term, S, can be represented as a 32-bit integer.  Its value
   can range from 0 to (2**32)-1 microseconds."

I agree it should be specified as an unsigned integer, and the notation
revised to (2**32)-1 as the maximum, to be clear.  I believe the range 0 to
(2**32)-1 is correct for an unsigned integer.

> This also holds true for
> other
> occasions where integer values are used (e.g. section 6.2.3!

Same comments as above.

> - section 6.2.11. para starting with " When excess treatment is set to
> 'shape', ". What is the error handling if excess treatment is set to
> 'shape'
> and no TMOD parameter is given?

The E flag is set for the parameter and the reservation fails.  This can
be specified in Section 6.2.11.

> - section 7. This section is extremely short. This might a non-issue,
> but I
> personally had the feeling the security discussion is too brief. This
> might
> be OK, but the document authors and the WG should be prepared for tough
> questions regarding this when going to the IESG. What about this
> document
> defining just the basics, but other documents defining the real
> behaviour?
> Is it assumed that this does not raise any new security issue?

Good points and questions.  QSPEC security is directly tied to QoS NSLP
security, and the QoS NSLP document has a very detailed security section.
All these considerations apply to QSPEC and that should be noted at the
beginning of Section 7.  I'm not aware of any new security issues introduced
by QSPEC beyond the point made already in Section 7 on priority.
Suggestions welcome from the WG on other security issues that might arise
from QSPEC.

> - section 8 says in several places " A specification is required to
> depreciate, delete, or modify QSPEC versions." What happens to deleted
> IANA
> values? Is IANA allowed to re-assign those or should they be treated as
> deprecated values, i.e., they cannot be used anymore, but the value is
> blocked for ever?

These are IANA specific rules that I don't think need to be reviewed in
Section 8.

>
> ****
> idnits 2.06.01
>
> tmp/draft-ietf-nsis-qspec-18.txt:
> tmp/draft-ietf-nsis-qspec-18.txt(2867): Found possible IPv4 address
> '7.2.9.4' in position 6; this doesn't match RFC3330's suggested
> 192.0.2.0/24
> address range.
>
>  Checking boilerplate required by RFC 3978 and 3979, updated by RFC
> 4748:
>
> ----------------------------------------------------------------------------
>
>     No issues found here.
>
>  Checking nits according to
> http://www.ietf.org/ietf/1id-guidelines.txt:
>
> ----------------------------------------------------------------------------
>
>  == No 'Intended status' indicated for this document; assuming
> Proposed
>     Standard
>
>  == The page length should not exceed 58 lines per page, but there was
> 3
>     longer pages, the longest (page 6) being 59 lines
>
>  == It seems as if not all pages are separated by form feeds - found 0
> form
>     feeds but 55 pages
>
>
>  Checking nits according to http://www.ietf.org/ID-Checklist.html:
>
> ----------------------------------------------------------------------------
>
>  == There are 1 instance of lines with non-RFC3330-compliant IPv4
> addresses
>     in the document.  If these are example addresses, they should be
> changed.
>
>
>  Miscellaneous warnings:
>
> ----------------------------------------------------------------------------
>
>  == The copyright year in the IETF Trust Copyright Line does not match
> the
>     current year
>
>
>  Checking references for intended status: Proposed Standard
>
> ----------------------------------------------------------------------------
>
>     (See RFC 3967 for information about using normative references to
>     lower-maturity documents in RFCs)
>
>  == Missing Reference: 'S' is mentioned on line 1730, but not defined
>     '|  Slack Term [S]  (32-bit integer)
> |...'
>
>  -- Possible downref: Undefined Non-RFC (?) reference : ref. 'S'
>
>  == Unused Reference: 'RFC4506' is defined on line 2363, but no
> explicit
>     reference was found in the text
>     '[RFC4506] Eisler, M., "XDR: External Data Representation
> Standard,"...'
>
>  == Unused Reference: 'IEEE754' is defined on line 2375, but no
> explicit
>     reference was found in the text
>     '[IEEE754] Institute of Electrical and Electronics Engineers,
> "IEEE
> S...'
>
>  == Unused Reference: 'NETWORK-BYTE-ORDER' is defined on line 2381,
> but no
>     explicit reference was found in the text
>     '[NETWORK-BYTE-ORDER] Wikipedia, "Endianness,"
> http://en.wikipedia.or...'
>
>  -- Possible downref: Non-RFC (?) normative reference: ref. '3GPP-1'
>
>  -- Possible downref: Non-RFC (?) normative reference: ref. '3GPP-2'
>
>  -- Possible downref: Non-RFC (?) normative reference: ref. '3GPP-3'
>
>  -- Possible downref: Non-RFC (?) normative reference: ref. 'GIST'
>
>  -- Possible downref: Non-RFC (?) normative reference: ref. 'QoS-SIG'
>
>
>     Summary: 0 errors (**), 9 warnings (==), 6 comments (--).
> ----------------------------------------------------------------------------
> ----
>
>
> stiemerling@netlab.nec.de
>
> NEC Laboratories Europe - Network Research Division
>
> NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road,
> London
> W3 6BL | Registered in England 2832014
>

       
---------------------------------
Never miss a thing.   Make Yahoo your homepage.
--0-66703516-1203094510=:34791
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>Martin,<BR><BR>Many thanks for your careful review.<BR><BR>Please see comments in line below.<BR><BR>Please let us know of any further comments.&nbsp; We'll resubmit the document<BR>prior to cutoff date.<BR><BR>Jerry<BR><BR>&gt; Hi all,<BR>&gt;<BR>&gt; Please find my review of draft-ietf-nsis-qspec-18.txt.<BR>&gt;<BR>&gt; There are some minor technical issues to fix. In general the document<BR>&gt; seems<BR>&gt; to be ready to go for AD review,&nbsp; once the editorials and technical<BR>&gt; issues<BR>&gt; have been fixed.<BR>&gt;<BR>&gt; Please address the issues and submit an updated version of the draft if<BR>&gt; d<BR>&gt; one so. I will go ahead with the updated draft for the protocol write<BR>&gt; up<BR>&gt; (i.e., the step before sending to Magnus and the IESG).<BR>&gt;<BR>&gt;&nbsp; Martin<BR>&gt;<BR>&gt; ****<BR>&gt; General<BR>&gt; ****<BR>&gt; I found the first part of the document (i.e., until section 5) quite<BR>&gt; confusing and after section five quite
 clear. This does not mean that<BR>&gt; there<BR>&gt; is an issue, as typically Internet drafts have the need to sketch tech<BR>&gt; things in the beginning without having the reader already at the<BR>&gt; technical<BR>&gt; level. I assume that the text is fine right now, as the WG has not<BR>&gt; pushed to<BR>&gt; change it.<BR><BR>These sections have been rewritten many times.&nbsp; Please let us know if you<BR>have any particular suggestion to improve clarity.<BR><BR>&gt;<BR>&gt; ****<BR>&gt; Editorial:<BR>&gt; ****<BR>&gt;<BR>&gt; - the idnits tool has found some issues (see below)<BR><BR>OK, will address.<BR><BR>&gt; - Add line in memo heading with: Intended Status: Informational<BR><BR>Although the NSIS milestone says "Informational", the ID tracker lists the<BR>status as "Proposed Standard"<BR><A
 href="mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000038/!x-usc:https://datatracker.ietf.org/idtracker/draft-ietf-nsis-qspec/">https://datatracker.ietf.org/idtracker/draft-ietf-nsis-qspec/</A>.&nbsp; IMO the<BR>QSPEC document should be a PS document, in close alignment with the </DIV>  <DIV>NSLP PS document.&nbsp; Many IANA registries are created, etc.&nbsp; I can't see the</DIV>  <DIV>rationale for NSLP being PS and QSPEC being Informational.&nbsp; I do recall a </DIV>  <DIV>discussion on this point earlier and several WG members expressed the same</DIV>  <DIV>view.&nbsp; Perhaps the WG members and chairs can comment.<BR><BR>&gt; -&nbsp; Section 1: Move to the very end of memo. It it is good to<BR>&gt; acknowledge<BR>&gt; other people, but it is fair enough to do it at the very end, as<BR>&gt; technical<BR>&gt; protocol stuff comes first.<BR><BR>OK.<BR><BR>&gt; - section 2: Adding a line saying that QSPEC readers should (or better<BR>&gt; must?) read the QoS NSLP
 in advance would be advantageous for the whole<BR>&gt; document.<BR><BR>Note that the first sentence of Section 2 references QoS NSLP since the<BR>documents are closely tied.&nbsp; The QSPEC document is intended to be (and<BR>should be) self contained so that one doesn't have to ("must") read<BR>something else first before reading and understanding QSPEC.&nbsp; However, your <BR>point is well taken.&nbsp; We can add a sentence in Section 2 such as "See</DIV>  <DIV>[QoS-SIG] for further details on QoS NSLP."<BR><BR>&gt; - section 2, page 5, para starting with "Interoperability between QoS<BR>&gt; NSIS<BR>&gt; entities (QNEs)..." says that parameters can be flagged or not flagged.<BR>&gt; I<BR>&gt; suggest to put the terms "flagged"/"non flagged" in brackets and write<BR>&gt; mandatory and optional parameters. This makes it easier for first time<BR>&gt; readers.<BR><BR>We've eliminated the terminology "mandatory" and "optional" parameters.<BR>Parameters can be flagged by the
 M flag if they MUST be interpreted, or<BR>otherwise, as follows:<BR><BR>&nbsp;M Flag: When set indicates the subsequent parameter MUST be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interpreted. Otherwise the parameter can be ignored if not<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; understood.<BR><BR>We don't want to get back into the mandatory/optional terminology at this<BR>point.<BR><BR>&gt; - - section 2, page 5, para starting with " A local QSPEC can be<BR>&gt; defined in<BR>&gt; a local domain with the initiator QSPEC encapsulated, ...". This<BR>&gt; paragraph<BR>&gt; is brief but describes a very powerful mechanism of the QSPEC. I would<BR>&gt; suggest to remove the hint the TMOD parameter and just write that the<BR>&gt; QSPEC<BR>&gt; allows local QPSECs that are domain specific. This also helps first<BR>&gt; time<BR>&gt; readers to understand a basic feature of&nbsp; QPSEC but not the full<BR>&gt; implementation of
 it.<BR><BR>OK.<BR><BR>&gt; - section 4.1, 2nd para, text in para starting with " New QoS NSLP<BR>&gt; message<BR>&gt; processing rules can only be defined in Standard...". Is it required to<BR>&gt; say<BR>&gt; this at this part of the document at all? I remember this again stated<BR>&gt; in<BR>&gt; the document somewhere later on at an appropriate place.<BR><BR>It's an important point and I think it appropriate to mention it in Section <BR>4.1.&nbsp; Furthermore, I recall extensive discussion on this sentence and I </DIV>  <DIV>believe it was explicitly agreed to include it here as well as later in the</DIV>  <DIV>document.&nbsp; Also, mentioning important points more than once often helps</DIV>  <DIV>clarity.<BR><BR>&gt; - section 4.2 two paras below figure 1. Suddenly there is text about<BR>&gt; RESERVE<BR>&gt; and QUERY, but no hint to the QoS NSLP at all. Adding a reference to<BR>&gt; the QoS<BR>&gt; NSLP at this occasion would be excellent. Otherwise it&nbsp; is hard
 to see<BR>&gt; where<BR>&gt; those terms are coming from<BR><BR>Good point, will do.<BR><BR>&gt; - section 4.3.1, para starting with " When the TMOD parameter in<BR>&gt; included in<BR>&gt; QoS Available, it..." should read " When the TMOD parameter are<BR>&gt; included in<BR>&gt; QoS Available, it..."<BR><BR>I think the English is correct as it stands.&nbsp; However, we could say "When<BR>the TMOD sub-parameters are included ..."<BR><BR>&gt; - section 4.3.1. This section nevers talks about tmod-2! tmod-2 is<BR>&gt; mentioned only&nbsp; in sections 6.2.1 and 6.2.2.<BR><BR>Right, good point.&nbsp; We'll revise the text to refer to TMOD-1 and TMOD-2 and<BR>explain the difference.&nbsp; We could include the example of the need for the <BR>TMOD-2 parameter in Section 4.3.1 (see discussion/example below of the need <BR>for the TMOD-2 parameter).<BR><BR>&gt; - section 5, 1st and 2nd para suddenly use the E-/N-flag without every<BR>&gt; explaining their meaning.<BR><BR>Well, this
 is where the M flag, E flag, and N flag are being explained.&nbsp; The<BR>first paragraph introduces them and there are details later.&nbsp; We could add<BR>text in the beginning such as "Three flags are used in QSPEC, the M flag, E<BR>flag, and N flag, which are explained in this section."<BR><BR>&gt; - section 5.1, again the support of local QSPECs is quite powerful but<BR>&gt; never<BR>&gt; really good explained with a figure. For instance, the first para of<BR>&gt; section<BR>&gt; 5.1 could refer to a simple figure showing a network configuration for<BR>&gt; a<BR>&gt; single flow, but with indications where which QSPEC is used. This<BR>&gt; instantly<BR>&gt; makes the whole concept better undestandable.<BR><BR>OK, we could add a figure analogous to Figure 3 in the Y.1541-QOSM document<BR><A
 href="mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000038/!x-usc:http://www.ietf.org/internet-drafts/draft-ietf-nsis-y1541-qosm-05.txt">http://www.ietf.org/internet-drafts/draft-ietf-nsis-y1541-qosm-05.txt</A> to<BR>explain the concept.<BR><BR>&gt; - section 5.2.5. formatting error<BR><BR>OK.<BR><BR>&gt; - section 5.3.1 and related. You use tables to define cases and also<BR>&gt; refer<BR>&gt; to them later in the object definition. Thus it would be good to label<BR>&gt; those<BR>&gt; tables.<BR><BR>OK, good suggestion.<BR><BR>&gt; - section 5.3.5 has one formatting issue and one spelling error<BR>&gt; (s/described<BR>&gt; In [QoS-SIG]/ described in [QoS-SIG])<BR><BR>OK.<BR><BR>&gt; - section 5.4. remove reference to NSIS extensibility document, as we<BR>&gt; do not<BR>&gt; have it ready by now.<BR><BR>OK.<BR><BR>&gt; - section 6.1. I got confused by all the different header definition. I<BR>&gt; would propose to split 6.1. in subsections, i.e., one for each
 header<BR>&gt; definition. This improves readability.<BR><BR>OK, good suggestion.<BR><BR>&gt; - section 6.2.1: Why is there this line&nbsp;&nbsp;&nbsp; &lt;TMOD-1&gt; = &lt;r&gt; &lt;b&gt; &lt;p&gt; &lt;m&gt;<BR>&gt; [RFC2210, RFC2215]? It is now required for the object definition.<BR><BR>Right, the format is inconsistent with the other subsections and will be<BR>revised accordingly.<BR><BR>&gt; - section 8, text says " Object Types (12 bits):" but should read<BR>&gt; "QSPEC<BR>&gt; Object Types (12 bits):".<BR><BR>But then Section 6.1 would have to be revised to be consistent in<BR>terminology.&nbsp; While I have no big objection to changing all of this, IMO it<BR>should stay as is; I think it is clear that this is a QSPEC object type.<BR><BR>&gt; - appendix b: add a note in the first line that this appendix should be<BR>&gt; removed by the RFC editor before publication.<BR><BR>OK.<BR><BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; ***<BR>&gt; Technical<BR>&gt; ***<BR>&gt; - section
 5.3.1, para starting with " The QSPEC parameter IDs and<BR>&gt; values<BR>&gt; included in the QoS Reserved...". This paragraph talks about how to set<BR>&gt; the<BR>&gt; parameters in the RESPONSE message for case 2. It is basically fine,<BR>&gt; but the<BR>&gt; second sentence is for me not understandable (" For those QSPEC<BR>&gt; parameters<BR>&gt; that were also included in the QoS Available object in the RESERVE<BR>&gt; message,<BR>&gt; their value is copied into the QoS Desired object.")<BR>&gt; The paragraph is talking about responses, but in RESPONSE there is no<BR>&gt; QoS<BR>&gt; desired object anymore (at least according to the table above). I<BR>&gt; probably<BR>&gt; do misunderstand something here?<BR><BR>Good catch.&nbsp; The sentence needs to be corrected.&nbsp; It should be: "For those<BR>QSPEC parameters that were also included in the QoS Available object in the<BR>RESERVE message, their value is copied from the QoS Available object (in<BR>RESERVE) into
 the QoS Reserved object (in RESPONSE) ."<BR><BR>&gt; - section 6.1 qspec header element definition. The length definition in<BR>&gt; the<BR>&gt; qspec header definition contradicts the length definition at the<BR>&gt; beginning<BR>&gt; of section 6.1 One says "total length of qspec" the other "length is<BR>&gt; always<BR>&gt; exept header"<BR><BR>Very good catch!&nbsp; IMO the section definition should be revised as<BR>follows:<BR><BR>&nbsp;Length: The total length of the QSPEC --&gt;<BR>&nbsp;Length: The total length of the QSPEC excluding the common header<BR><BR>&gt; - section 6.2.2., see also my comment above about tmod-2. Even after<BR>&gt; reading<BR>&gt; section 6.2.2. I do not have any clue why there two tmod parameters.<BR><BR>This is based on discussions with David Black, who recommended the second<BR>TMOD parameter to support DiffServ applications (as noted in Section 6.2.2).<BR>Earlier versions of QSPEC included the following example (due to David), <BR>which
 can be added back into the draft (probably in Section 4.3.1):<BR><BR>"It is typically assumed that DiffServ EF traffic is shaped at the ingress<BR>by a single rate token bucket.&nbsp; Therefore, a single TMOD parameter is<BR>sufficient to signal DiffServ EF traffic.&nbsp; However, for DiffServ AF traffic<BR>two sets of token bucket parameters are needed, one token bucket for the<BR>average traffic and one token bucket for the burst traffic.&nbsp; [RFC2697]<BR>defines a Single Rate Three Color Marker (srTCM), which meters a traffic<BR>stream and marks its packets according to three traffic parameters,<BR>Committed Information Rate (CIR), Committed Burst Size (CBS), and Excess<BR>Burst Size (EBS), to be either green, yellow, or red.&nbsp; A packet is marked<BR>green if it does not exceed the CBS, yellow if it does exceed the CBS, but<BR>not the EBS, and red otherwise.&nbsp; [RFC2697] defines specific procedures using<BR>two token buckets that run at the same rate.&nbsp;
 Therefore 2 TMOD parameters<BR>are sufficient to distinguish among 3 levels of drop precedence.&nbsp; An example<BR>is also described in the Appendix to [RFC2597]."<BR><BR>Also, the first sentence in Section 6.2.2 should be changed slightly to: ''A<BR>second, QSPEC &lt;TMOD-2&gt; parameter is specified, as could be needed for<BR>example to support some Diffserv applications." (added word "some").<BR><BR>&gt; - section 6.2.7. The slack term is 32 bits as integer. However the<BR>&gt; slack<BR>&gt; term must only be non-negative, i.e., it is actually an unsigned int.<BR>&gt; Why is<BR>&gt; is not specified as unsigned int? However, the current value range<BR>&gt; definition is broken, as an integer of 32 bits cannot have a maximum<BR>&gt; range<BR>&gt; to&nbsp; 2**32-1 (there are only 31 bits left...).<BR><BR>The coding of the slack term is based on RSVP coding:<BR><BR>RFC 2210 says:<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>11&nbsp; |&nbsp; Slack Term [S]&nbsp; (32-bit integer)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR><BR>RFC 2212 says:<BR>"The Slack term, S, can be represented as a 32-bit integer.&nbsp; Its value<BR>&nbsp;&nbsp; can range from 0 to (2**32)-1 microseconds."<BR><BR>I agree it should be specified as an unsigned integer, and the notation<BR>revised to (2**32)-1 as the maximum, to be clear.&nbsp; I believe the range 0 to<BR>(2**32)-1 is correct for an unsigned integer.<BR><BR>&gt; This also holds true for<BR>&gt; other<BR>&gt; occasions where integer values are used (e.g. section 6.2.3!<BR><BR>Same comments as above.<BR><BR>&gt; - section 6.2.11. para starting with " When excess
 treatment is set to<BR>&gt; 'shape', ". What is the error handling if excess treatment is set to<BR>&gt; 'shape'<BR>&gt; and no TMOD parameter is given?<BR><BR>The E flag is set for the parameter and the reservation fails.&nbsp; This can<BR>be specified in Section 6.2.11.<BR><BR>&gt; - section 7. This section is extremely short. This might a non-issue,<BR>&gt; but I<BR>&gt; personally had the feeling the security discussion is too brief. This<BR>&gt; might<BR>&gt; be OK, but the document authors and the WG should be prepared for tough<BR>&gt; questions regarding this when going to the IESG. What about this<BR>&gt; document<BR>&gt; defining just the basics, but other documents defining the real<BR>&gt; behaviour?<BR>&gt; Is it assumed that this does not raise any new security issue?<BR><BR>Good points and questions.&nbsp; QSPEC security is directly tied to QoS NSLP<BR>security, and the QoS NSLP document has a very detailed security section.<BR>All these considerations apply
 to QSPEC and that should be noted at the<BR>beginning of Section 7.&nbsp; I'm not aware of any new security issues introduced<BR>by QSPEC beyond the point made already in Section 7 on priority.<BR>Suggestions welcome from the WG on other security issues that might arise<BR>from QSPEC.<BR><BR>&gt; - section 8 says in several places " A specification is required to<BR>&gt; depreciate, delete, or modify QSPEC versions." What happens to deleted<BR>&gt; IANA<BR>&gt; values? Is IANA allowed to re-assign those or should they be treated as<BR>&gt; deprecated values, i.e., they cannot be used anymore, but the value is<BR>&gt; blocked for ever?<BR><BR>These are IANA specific rules that I don't think need to be reviewed in<BR>Section 8.<BR><BR>&gt;<BR>&gt; ****<BR>&gt; idnits 2.06.01<BR>&gt;<BR>&gt; tmp/draft-ietf-nsis-qspec-18.txt:<BR>&gt; tmp/draft-ietf-nsis-qspec-18.txt(2867): Found possible IPv4 address<BR>&gt; '7.2.9.4' in position 6; this doesn't match RFC3330's
 suggested<BR>&gt; 192.0.2.0/24<BR>&gt; address range.<BR>&gt;<BR>&gt;&nbsp; Checking boilerplate required by RFC 3978 and 3979, updated by RFC<BR>&gt; 4748:<BR>&gt;<BR>&gt; ----------------------------------------------------------------------------<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; No issues found here.<BR>&gt;<BR>&gt;&nbsp; Checking nits according to<BR>&gt; <A href="mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000038/!x-usc:http://www.ietf.org/ietf/1id-guidelines.txt">http://www.ietf.org/ietf/1id-guidelines.txt</A>:<BR>&gt;<BR>&gt; ----------------------------------------------------------------------------<BR>&gt;<BR>&gt;&nbsp; == No 'Intended status' indicated for this document; assuming<BR>&gt; Proposed<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Standard<BR>&gt;<BR>&gt;&nbsp; == The page length should not exceed 58 lines per page, but there was<BR>&gt; 3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; longer pages, the longest (page 6) being 59 lines<BR>&gt;<BR>&gt;&nbsp; == It
 seems as if not all pages are separated by form feeds - found 0<BR>&gt; form<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; feeds but 55 pages<BR>&gt;<BR>&gt;<BR>&gt;&nbsp; Checking nits according to <A href="mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000038/!x-usc:http://www.ietf.org/ID-Checklist.html">http://www.ietf.org/ID-Checklist.html</A>:<BR>&gt;<BR>&gt; ----------------------------------------------------------------------------<BR>&gt;<BR>&gt;&nbsp; == There are 1 instance of lines with non-RFC3330-compliant IPv4<BR>&gt; addresses<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; in the document.&nbsp; If these are example addresses, they should be<BR>&gt; changed.<BR>&gt;<BR>&gt;<BR>&gt;&nbsp; Miscellaneous warnings:<BR>&gt;<BR>&gt; ----------------------------------------------------------------------------<BR>&gt;<BR>&gt;&nbsp; == The copyright year in the IETF Trust Copyright Line does not match<BR>&gt; the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; current year<BR>&gt;<BR>&gt;<BR>&gt;&nbsp;
 Checking references for intended status: Proposed Standard<BR>&gt;<BR>&gt; ----------------------------------------------------------------------------<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; (See RFC 3967 for information about using normative references to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; lower-maturity documents in RFCs)<BR>&gt;<BR>&gt;&nbsp; == Missing Reference: 'S' is mentioned on line 1730, but not defined<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; '|&nbsp; Slack Term [S]&nbsp; (32-bit integer)<BR>&gt; |...'<BR>&gt;<BR>&gt;&nbsp; -- Possible downref: Undefined Non-RFC (?) reference : ref. 'S'<BR>&gt;<BR>&gt;&nbsp; == Unused Reference: 'RFC4506' is defined on line 2363, but no<BR>&gt; explicit<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; reference was found in the text<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; '[RFC4506] Eisler, M., "XDR: External Data Representation<BR>&gt; Standard,"...'<BR>&gt;<BR>&gt;&nbsp; == Unused Reference: 'IEEE754' is defined on line 2375, but no<BR>&gt;
 explicit<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; reference was found in the text<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; '[IEEE754] Institute of Electrical and Electronics Engineers,<BR>&gt; "IEEE<BR>&gt; S...'<BR>&gt;<BR>&gt;&nbsp; == Unused Reference: 'NETWORK-BYTE-ORDER' is defined on line 2381,<BR>&gt; but no<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; explicit reference was found in the text<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; '[NETWORK-BYTE-ORDER] Wikipedia, "Endianness,"<BR>&gt; <A href="mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000038/!x-usc:http://en.wikipedia.or...'/">http://en.wikipedia.or...'</A><BR>&gt;<BR>&gt;&nbsp; -- Possible downref: Non-RFC (?) normative reference: ref. '3GPP-1'<BR>&gt;<BR>&gt;&nbsp; -- Possible downref: Non-RFC (?) normative reference: ref. '3GPP-2'<BR>&gt;<BR>&gt;&nbsp; -- Possible downref: Non-RFC (?) normative reference: ref. '3GPP-3'<BR>&gt;<BR>&gt;&nbsp; -- Possible downref: Non-RFC (?) normative reference: ref. 'GIST'<BR>&gt;<BR>&gt;&nbsp; -- Possible
 downref: Non-RFC (?) normative reference: ref. 'QoS-SIG'<BR>&gt;<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Summary: 0 errors (**), 9 warnings (==), 6 comments (--).<BR>&gt; ----------------------------------------------------------------------------<BR>&gt; ----<BR>&gt;<BR>&gt;<BR>&gt; <A href="mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000038/!x-usc:mailto:stiemerling@netlab.nec.de">stiemerling@netlab.nec.de</A><BR>&gt;<BR>&gt; NEC Laboratories Europe - Network Research Division<BR>&gt;<BR>&gt; NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road,<BR>&gt; London<BR>&gt; W3 6BL | Registered in England 2832014<BR>&gt;</DIV><p>&#32;



      <hr size=1>Never miss a thing.  <a href="http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs"> Make Yahoo your homepage.</a>


--0-66703516-1203094510=:34791--

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

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

--===============1345112473==--


From nsis-bounces@ietf.org  Fri Feb 15 14:45:24 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9078F28C3A2;
	Fri, 15 Feb 2008 14:45:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[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 9LWOZIjpH0M6; Fri, 15 Feb 2008 14:45:23 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AE15A28C23A;
	Fri, 15 Feb 2008 14:45:20 -0800 (PST)
X-Original-To: nsis@ietf.org
Delivered-To: nsis@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 0D6953A6B9F; Fri, 15 Feb 2008 14:45:01 -0800 (PST)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080215224502.0D6953A6B9F@core3.amsl.com>
Date: Fri, 15 Feb 2008 14:45:02 -0800 (PST)
Cc: nsis@ietf.org
Subject: [NSIS] I-D Action:draft-ietf-nsis-ntlp-sctp-03.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: <http://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: <http://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           : General Internet Signaling Transport (GIST) over SCTP
	Author(s)       : X. Fu, et al.
	Filename        : draft-ietf-nsis-ntlp-sctp-03.txt
	Pages           : 11
	Date            : 2008-02-15

The General Internet Signaling Transport (GIST) protocol currently
uses TCP or TLS over TCP for connection mode operation.  This
document describes the usage of GIST over the Stream Control
Transmission Protocol (SCTP).  The use of SCTP can take advantage of
features provided by SCTP, namely streaming-based transport, support
of multiple streams to avoid head of line blocking, and the support
of multi-homing to provide network level fault tolerance.
Additionally, the support for the Partial Reliability Extension of
SCTP is discussed.

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

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-nsis-ntlp-sctp-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-nsis-ntlp-sctp-03.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-nsis-ntlp-sctp-03.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-nsis-ntlp-sctp-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-02-15143405.I-D\@ietf.org>


--OtherAccess--

--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
http://www.ietf.org/mailman/listinfo/nsis

--NextPart--


From nsis-bounces@ietf.org  Sun Feb 17 14:12:58 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 827293A6BC2;
	Sun, 17 Feb 2008 14:12:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.918
X-Spam-Level: 
X-Spam-Status: No, score=-0.918 tagged_above=-999 required=5
	tests=[AWL=-0.708, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, 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 CnEfsCIPOgHS; Sun, 17 Feb 2008 14:12:56 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D629B3A6B5D;
	Sun, 17 Feb 2008 14:12:14 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EF5273A67D4
	for <nsis@core3.amsl.com>; Sun, 17 Feb 2008 14:12:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 lrJftBYT4M4X for <nsis@core3.amsl.com>;
	Sun, 17 Feb 2008 14:12:11 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id C26493A6B29
	for <nsis@ietf.org>; Sun, 17 Feb 2008 14:11:20 -0800 (PST)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 17 Feb 2008 04:23:06 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m1HCN6fT009793; 
	Sun, 17 Feb 2008 04:23:06 -0800
Received: from stealth-10-32-245-155.cisco.com
	(stealth-10-32-245-155.cisco.com [10.32.245.155])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m1HCN3vn019032;
	Sun, 17 Feb 2008 12:23:04 GMT
Message-Id: <156F8BF4-340C-4B31-9772-909E8C885E9B@cisco.com>
From: David R Oran <oran@cisco.com>
To: Gerald Ash <gash5107@yahoo.com>
In-Reply-To: <370957.34791.qm@web63604.mail.re1.yahoo.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Sun, 17 Feb 2008 07:23:03 -0500
References: <370957.34791.qm@web63604.mail.re1.yahoo.com>
X-Mailer: Apple Mail (2.919.2)
Authentication-Results: sj-dkim-2; header.From=oran@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: cornelia.kappler@googlemail.com, nsis <nsis@ietf.org>
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://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

Sorry for being completely out of touch on this. I didn't even get to  
read the thread until today. I've been utterly consumed with IAB work  
and my day job. I likely won't have any spare cycles until after IETF,  
so I too would like to deeply thank Jerry for stepping in out of  
retirement (although not even Junior Seau could save the Super bowl  
for the Patriots...sigh).

I will however do my utmost to read the final version after it's  
submitted.

Best to all,

Dave.

On Feb 15, 2008, at 11:55 AM, Gerald Ash wrote:

> Martin,
>
> Many thanks for your careful review.
>
> Please see comments in line below.
>
> Please let us know of any further comments.  We'll resubmit the  
> document
> prior to cutoff date.
>
> Jerry
>
> > Hi all,
> >
> > Please find my review of draft-ietf-nsis-qspec-18.txt.
> >
> > There are some minor technical issues to fix. In general the  
> document
> > seems
> > to be ready to go for AD review,  once the editorials and technical
> > issues
> > have been fixed.
> >
> > Please address the issues and submit an updated version of the  
> draft if
> > d
> > one so. I will go ahead with the updated draft for the protocol  
> write
> > up
> > (i.e., the step before sending to Magnus and the IESG).
> >
> >  Martin
> >
> > ****
> > General
> > ****
> > I found the first part of the document (i.e., until section 5) quite
> > confusing and after section five quite clear. This does not mean  
> that
> > there
> > is an issue, as typically Internet drafts have the need to sketch  
> tech
> > things in the beginning without having the reader already at the
> > technical
> > level. I assume that the text is fine right now, as the WG has not
> > pushed to
> > change it.
>
> These sections have been rewritten many times.  Please let us know  
> if you
> have any particular suggestion to improve clarity.
>
> >
> > ****
> > Editorial:
> > ****
> >
> > - the idnits tool has found some issues (see below)
>
> OK, will address.
>
> > - Add line in memo heading with: Intended Status: Informational
>
> Although the NSIS milestone says "Informational", the ID tracker  
> lists the
> status as "Proposed Standard"
> https://datatracker.ietf.org/idtracker/draft-ietf-nsis-qspec/.  IMO  
> the
> QSPEC document should be a PS document, in close alignment with the
> NSLP PS document.  Many IANA registries are created, etc.  I can't  
> see the
> rationale for NSLP being PS and QSPEC being Informational.  I do  
> recall a
> discussion on this point earlier and several WG members expressed  
> the same
> view.  Perhaps the WG members and chairs can comment.
>
> > -  Section 1: Move to the very end of memo. It it is good to
> > acknowledge
> > other people, but it is fair enough to do it at the very end, as
> > technical
> > protocol stuff comes first.
>
> OK.
>
> > - section 2: Adding a line saying that QSPEC readers should (or  
> better
> > must?) read the QoS NSLP in advance would be advantageous for the  
> whole
> > document.
>
> Note that the first sentence of Section 2 references QoS NSLP since  
> the
> documents are closely tied.  The QSPEC document is intended to be (and
> should be) self contained so that one doesn't have to ("must") read
> something else first before reading and understanding QSPEC.   
> However, your
> point is well taken.  We can add a sentence in Section 2 such as "See
> [QoS-SIG] for further details on QoS NSLP."
>
> > - section 2, page 5, para starting with "Interoperability between  
> QoS
> > NSIS
> > entities (QNEs)..." says that parameters can be flagged or not  
> flagged.
> > I
> > suggest to put the terms "flagged"/"non flagged" in brackets and  
> write
> > mandatory and optional parameters. This makes it easier for first  
> time
> > readers.
>
> We've eliminated the terminology "mandatory" and "optional"  
> parameters.
> Parameters can be flagged by the M flag if they MUST be interpreted,  
> or
> otherwise, as follows:
>
>  M Flag: When set indicates the subsequent parameter MUST be
>            interpreted. Otherwise the parameter can be ignored if not
>            understood.
>
> We don't want to get back into the mandatory/optional terminology at  
> this
> point.
>
> > - - section 2, page 5, para starting with " A local QSPEC can be
> > defined in
> > a local domain with the initiator QSPEC encapsulated, ...". This
> > paragraph
> > is brief but describes a very powerful mechanism of the QSPEC. I  
> would
> > suggest to remove the hint the TMOD parameter and just write that  
> the
> > QSPEC
> > allows local QPSECs that are domain specific. This also helps first
> > time
> > readers to understand a basic feature of  QPSEC but not the full
> > implementation of it.
>
> OK.
>
> > - section 4.1, 2nd para, text in para starting with " New QoS NSLP
> > message
> > processing rules can only be defined in Standard...". Is it  
> required to
> > say
> > this at this part of the document at all? I remember this again  
> stated
> > in
> > the document somewhere later on at an appropriate place.
>
> It's an important point and I think it appropriate to mention it in  
> Section
> 4.1.  Furthermore, I recall extensive discussion on this sentence  
> and I
> believe it was explicitly agreed to include it here as well as later  
> in the
> document.  Also, mentioning important points more than once often  
> helps
> clarity.
>
> > - section 4.2 two paras below figure 1. Suddenly there is text about
> > RESERVE
> > and QUERY, but no hint to the QoS NSLP at all. Adding a reference to
> > the QoS
> > NSLP at this occasion would be excellent. Otherwise it  is hard to  
> see
> > where
> > those terms are coming from
>
> Good point, will do.
>
> > - section 4.3.1, para starting with " When the TMOD parameter in
> > included in
> > QoS Available, it..." should read " When the TMOD parameter are
> > included in
> > QoS Available, it..."
>
> I think the English is correct as it stands.  However, we could say  
> "When
> the TMOD sub-parameters are included ..."
>
> > - section 4.3.1. This section nevers talks about tmod-2! tmod-2 is
> > mentioned only  in sections 6.2.1 and 6.2.2.
>
> Right, good point.  We'll revise the text to refer to TMOD-1 and  
> TMOD-2 and
> explain the difference.  We could include the example of the need  
> for the
> TMOD-2 parameter in Section 4.3.1 (see discussion/example below of  
> the need
> for the TMOD-2 parameter).
>
> > - section 5, 1st and 2nd para suddenly use the E-/N-flag without  
> every
> > explaining their meaning.
>
> Well, this is where the M flag, E flag, and N flag are being  
> explained.  The
> first paragraph introduces them and there are details later.  We  
> could add
> text in the beginning such as "Three flags are used in QSPEC, the M  
> flag, E
> flag, and N flag, which are explained in this section."
>
> > - section 5.1, again the support of local QSPECs is quite powerful  
> but
> > never
> > really good explained with a figure. For instance, the first para of
> > section
> > 5.1 could refer to a simple figure showing a network configuration  
> for
> > a
> > single flow, but with indications where which QSPEC is used. This
> > instantly
> > makes the whole concept better undestandable.
>
> OK, we could add a figure analogous to Figure 3 in the Y.1541-QOSM  
> document
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-y1541- 
> qosm-05.txt to
> explain the concept.
>
> > - section 5.2.5. formatting error
>
> OK.
>
> > - section 5.3.1 and related. You use tables to define cases and also
> > refer
> > to them later in the object definition. Thus it would be good to  
> label
> > those
> > tables.
>
> OK, good suggestion.
>
> > - section 5.3.5 has one formatting issue and one spelling error
> > (s/described
> > In [QoS-SIG]/ described in [QoS-SIG])
>
> OK.
>
> > - section 5.4. remove reference to NSIS extensibility document, as  
> we
> > do not
> > have it ready by now.
>
> OK.
>
> > - section 6.1. I got confused by all the different header  
> definition. I
> > would propose to split 6.1. in subsections, i.e., one for each  
> header
> > definition. This improves readability.
>
> OK, good suggestion.
>
> > - section 6.2.1: Why is there this line    <TMOD-1> = <r> <b> <p>  
> <m>
> > [RFC2210, RFC2215]? It is now required for the object definition.
>
> Right, the format is inconsistent with the other subsections and  
> will be
> revised accordingly.
>
> > - section 8, text says " Object Types (12 bits):" but should read
> > "QSPEC
> > Object Types (12 bits):".
>
> But then Section 6.1 would have to be revised to be consistent in
> terminology.  While I have no big objection to changing all of this,  
> IMO it
> should stay as is; I think it is clear that this is a QSPEC object  
> type.
>
> > - appendix b: add a note in the first line that this appendix  
> should be
> > removed by the RFC editor before publication.
>
> OK.
>
> >
> >
> >
> > ***
> > Technical
> > ***
> > - section 5.3.1, para starting with " The QSPEC parameter IDs and
> > values
> > included in the QoS Reserved...". This paragraph talks about how  
> to set
> > the
> > parameters in the RESPONSE message for case 2. It is basically fine,
> > but the
> > second sentence is for me not understandable (" For those QSPEC
> > parameters
> > that were also included in the QoS Available object in the RESERVE
> > message,
> > their value is copied into the QoS Desired object.")
> > The paragraph is talking about responses, but in RESPONSE there is  
> no
> > QoS
> > desired object anymore (at least according to the table above). I
> > probably
> > do misunderstand something here?
>
> Good catch.  The sentence needs to be corrected.  It should be: "For  
> those
> QSPEC parameters that were also included in the QoS Available object  
> in the
> RESERVE message, their value is copied from the QoS Available object  
> (in
> RESERVE) into the QoS Reserved object (in RESPONSE) ."
>
> > - section 6.1 qspec header element definition. The length  
> definition in
> > the
> > qspec header definition contradicts the length definition at the
> > beginning
> > of section 6.1 One says "total length of qspec" the other "length is
> > always
> > exept header"
>
> Very good catch!  IMO the section definition should be revised as
> follows:
>
>  Length: The total length of the QSPEC -->
>  Length: The total length of the QSPEC excluding the common header
>
> > - section 6.2.2., see also my comment above about tmod-2. Even after
> > reading
> > section 6.2.2. I do not have any clue why there two tmod parameters.
>
> This is based on discussions with David Black, who recommended the  
> second
> TMOD parameter to support DiffServ applications (as noted in Section  
> 6.2.2).
> Earlier versions of QSPEC included the following example (due to  
> David),
> which can be added back into the draft (probably in Section 4.3.1):
>
> "It is typically assumed that DiffServ EF traffic is shaped at the  
> ingress
> by a single rate token bucket.  Therefore, a single TMOD parameter is
> sufficient to signal DiffServ EF traffic.  However, for DiffServ AF  
> traffic
> two sets of token bucket parameters are needed, one token bucket for  
> the
> average traffic and one token bucket for the burst traffic.  [RFC2697]
> defines a Single Rate Three Color Marker (srTCM), which meters a  
> traffic
> stream and marks its packets according to three traffic parameters,
> Committed Information Rate (CIR), Committed Burst Size (CBS), and  
> Excess
> Burst Size (EBS), to be either green, yellow, or red.  A packet is  
> marked
> green if it does not exceed the CBS, yellow if it does exceed the  
> CBS, but
> not the EBS, and red otherwise.  [RFC2697] defines specific  
> procedures using
> two token buckets that run at the same rate.  Therefore 2 TMOD  
> parameters
> are sufficient to distinguish among 3 levels of drop precedence.  An  
> example
> is also described in the Appendix to [RFC2597]."
>
> Also, the first sentence in Section 6.2.2 should be changed slightly  
> to: ''A
> second, QSPEC <TMOD-2> parameter is specified, as could be needed for
> example to support some Diffserv applications." (added word "some").
>
> > - section 6.2.7. The slack term is 32 bits as integer. However the
> > slack
> > term must only be non-negative, i.e., it is actually an unsigned  
> int.
> > Why is
> > is not specified as unsigned int? However, the current value range
> > definition is broken, as an integer of 32 bits cannot have a maximum
> > range
> > to  2**32-1 (there are only 31 bits left...).
>
> The coding of the slack term is based on RSVP coding:
>
> RFC 2210 says:
>
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 
> +-+
> 11  |  Slack Term [S]  (32-bit integer)                             |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 
> +-+
>
> RFC 2212 says:
> "The Slack term, S, can be represented as a 32-bit integer.  Its value
>    can range from 0 to (2**32)-1 microseconds."
>
> I agree it should be specified as an unsigned integer, and the  
> notation
> revised to (2**32)-1 as the maximum, to be clear.  I believe the  
> range 0 to
> (2**32)-1 is correct for an unsigned integer.
>
> > This also holds true for
> > other
> > occasions where integer values are used (e.g. section 6.2.3!
>
> Same comments as above.
>
> > - section 6.2.11. para starting with " When excess treatment is  
> set to
> > 'shape', ". What is the error handling if excess treatment is set to
> > 'shape'
> > and no TMOD parameter is given?
>
> The E flag is set for the parameter and the reservation fails.  This  
> can
> be specified in Section 6.2.11.
>
> > - section 7. This section is extremely short. This might a non- 
> issue,
> > but I
> > personally had the feeling the security discussion is too brief.  
> This
> > might
> > be OK, but the document authors and the WG should be prepared for  
> tough
> > questions regarding this when going to the IESG. What about this
> > document
> > defining just the basics, but other documents defining the real
> > behaviour?
> > Is it assumed that this does not raise any new security issue?
>
> Good points and questions.  QSPEC security is directly tied to QoS  
> NSLP
> security, and the QoS NSLP document has a very detailed security  
> section.
> All these considerations apply to QSPEC and that should be noted at  
> the
> beginning of Section 7.  I'm not aware of any new security issues  
> introduced
> by QSPEC beyond the point made already in Section 7 on priority.
> Suggestions welcome from the WG on other security issues that might  
> arise
> from QSPEC.
>
> > - section 8 says in several places " A specification is required to
> > depreciate, delete, or modify QSPEC versions." What happens to  
> deleted
> > IANA
> > values? Is IANA allowed to re-assign those or should they be  
> treated as
> > deprecated values, i.e., they cannot be used anymore, but the  
> value is
> > blocked for ever?
>
> These are IANA specific rules that I don't think need to be reviewed  
> in
> Section 8.
>
> >
> > ****
> > idnits 2.06.01
> >
> > tmp/draft-ietf-nsis-qspec-18.txt:
> > tmp/draft-ietf-nsis-qspec-18.txt(2867): Found possible IPv4 address
> > '7.2.9.4' in position 6; this doesn't match RFC3330's suggested
> > 192.0.2.0/24
> > address range.
> >
> >  Checking boilerplate required by RFC 3978 and 3979, updated by RFC
> > 4748:
> >
> >  
> ----------------------------------------------------------------------------
> >
> >     No issues found here.
> >
> >  Checking nits according to
> > http://www.ietf.org/ietf/1id-guidelines.txt:
> >
> >  
> ----------------------------------------------------------------------------
> >
> >  == No 'Intended status' indicated for this document; assuming
> > Proposed
> >     Standard
> >
> >  == The page length should not exceed 58 lines per page, but there  
> was
> > 3
> >     longer pages, the longest (page 6) being 59 lines
> >
> >  == It seems as if not all pages are separated by form feeds -  
> found 0
> > form
> >     feeds but 55 pages
> >
> >
> >  Checking nits according to http://www.ietf.org/ID-Checklist.html:
> >
> >  
> ----------------------------------------------------------------------------
> >
> >  == There are 1 instance of lines with non-RFC3330-compliant IPv4
> > addresses
> >     in the document.  If these are example addresses, they should be
> > changed.
> >
> >
> >  Miscellaneous warnings:
> >
> >  
> ----------------------------------------------------------------------------
> >
> >  == The copyright year in the IETF Trust Copyright Line does not  
> match
> > the
> >     current year
> >
> >
> >  Checking references for intended status: Proposed Standard
> >
> >  
> ----------------------------------------------------------------------------
> >
> >     (See RFC 3967 for information about using normative references  
> to
> >     lower-maturity documents in RFCs)
> >
> >  == Missing Reference: 'S' is mentioned on line 1730, but not  
> defined
> >     '|  Slack Term [S]  (32-bit integer)
> > |...'
> >
> >  -- Possible downref: Undefined Non-RFC (?) reference : ref. 'S'
> >
> >  == Unused Reference: 'RFC4506' is defined on line 2363, but no
> > explicit
> >     reference was found in the text
> >     '[RFC4506] Eisler, M., "XDR: External Data Representation
> > Standard,"...'
> >
> >  == Unused Reference: 'IEEE754' is defined on line 2375, but no
> > explicit
> >     reference was found in the text
> >     '[IEEE754] Institute of Electrical and Electronics Engineers,
> > "IEEE
> > S...'
> >
> >  == Unused Reference: 'NETWORK-BYTE-ORDER' is defined on line 2381,
> > but no
> >     explicit reference was found in the text
> >     '[NETWORK-BYTE-ORDER] Wikipedia, "Endianness,"
> > http://en.wikipedia.or...'
> >
> >  -- Possible downref: Non-RFC (?) normative reference: ref. '3GPP-1'
> >
> >  -- Possible downref: Non-RFC (?) normative reference: ref. '3GPP-2'
> >
> >  -- Possible downref: Non-RFC (?) normative reference: ref. '3GPP-3'
> >
> >  -- Possible downref: Non-RFC (?) normative reference: ref. 'GIST'
> >
> >  -- Possible downref: Non-RFC (?) normative reference: ref. 'QoS- 
> SIG'
> >
> >
> >     Summary: 0 errors (**), 9 warnings (==), 6 comments (--).
> >  
> ----------------------------------------------------------------------------
> > ----
> >
> >
> > stiemerling@netlab.nec.de
> >
> > NEC Laboratories Europe - Network Research Division
> >
> > NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road,
> > London
> > W3 6BL | Registered in England 2832014
> >
>
> Never miss a thing. Make Yahoo your homepage.  
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> http://www.ietf.org/mailman/listinfo/nsis

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


From nsis-bounces@ietf.org  Mon Feb 18 05:24:25 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9DC3B28C3DA;
	Mon, 18 Feb 2008 05:24:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.861
X-Spam-Level: *
X-Spam-Status: No, score=1.861 tagged_above=-999 required=5 tests=[AWL=-0.302,
	BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	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 0oKVKBFdKpQK; Mon, 18 Feb 2008 05:24:24 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DD4C428C3C5;
	Mon, 18 Feb 2008 05:24:24 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0DEE128C3A2;
	Mon, 18 Feb 2008 05:24:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 sgE3irknwr9U; Mon, 18 Feb 2008 05:24:23 -0800 (PST)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de
	[141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id EF01128C354;
	Mon, 18 Feb 2008 05:24:22 -0800 (PST)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1JR5yk-0003FP-5J; Mon, 18 Feb 2008 14:24:19 +0100
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 
	id 1JR5yj-00046L-8j; Mon, 18 Feb 2008 14:24:18 +0100
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 25B532FC00C;
	Mon, 18 Feb 2008 14:24:17 +0100 (CET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by vorta.tm.uka.de (Postfix) with ESMTP id 9AF40100D4;
	Mon, 18 Feb 2008 14:25:10 +0100 (CET)
Message-ID: <47B98736.4010000@tm.uka.de>
Date: Mon, 18 Feb 2008 14:25:10 +0100
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>, nsis-imp@ietf.org
X-Enigmail-Version: 0.95.0
X-Spam-Host: irams1.ira.uni-karlsruhe.de
X-ATIS-Checksum: v3zoCAcc32ckk
Subject: [NSIS] Release GISTka 0.95
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <http://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: <http://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,

we are happy to announce the availability
of our GIST implementation GISTka v0.95
(basically at http://tools.ietf.org/html/draft-ietf-nsis-ntlp-15).
Please see
https://projekte.tm.uni-karlsruhe.de/trac/NSIS/
for downloading and more information.

We are also open for remote interop testing if you like.

Regards,
 Roland

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


From nsis-bounces@ietf.org  Tue Feb 19 05:27:16 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 031E028C549;
	Tue, 19 Feb 2008 05:27:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.519
X-Spam-Level: 
X-Spam-Status: No, score=-0.519 tagged_above=-999 required=5
	tests=[AWL=-0.309, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, 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 mamAivqxi64X; Tue, 19 Feb 2008 05:27:14 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1E67028C496;
	Tue, 19 Feb 2008 05:27:14 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E25223A680B
	for <nsis@core3.amsl.com>; Tue, 19 Feb 2008 05:27:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 PPynOkT7SmYq for <nsis@core3.amsl.com>;
	Tue, 19 Feb 2008 05:27:11 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id 0BFD33A6AAA
	for <nsis@ietf.org>; Tue, 19 Feb 2008 05:26:41 -0800 (PST)
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 108222C009E90;
	Tue, 19 Feb 2008 14:26:38 +0100 (CET)
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 nvLQPA494w7E; Tue, 19 Feb 2008 14:26:37 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id D78052C000355;
	Tue, 19 Feb 2008 14:26:22 +0100 (CET)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 19 Feb 2008 14:26:22 +0100
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF4D10C7@mx1.office>
In-Reply-To: <370957.34791.qm@web63604.mail.re1.yahoo.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Review of draft-ietf-nsis-qspec-18.txt
Thread-Index: Achv9HzkCITPHhVrQjqT1WLBTQl3cgDBGfxw
References: <C3C61BFC.EA3F%Stiemerling@nw.neclab.eu>
	<370957.34791.qm@web63604.mail.re1.yahoo.com>
From: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>
To: "Gerald Ash" <gash5107@yahoo.com>,
	"nsis" <nsis@ietf.org>
Cc: cornelia.kappler@googlemail.com
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://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,

Thanks for getting back this. I hope you're doing fine in retirement.

I have just a few things below. How fast can you post an updated version?


> 
> > Hi all,
> >
> > Please find my review of draft-ietf-nsis-qspec-18.txt.
> >
> > There are some minor technical issues to fix. In general 
> the document 
> > seems to be ready to go for AD review,  once the editorials and 
> > technical issues have been fixed.
> >
> > Please address the issues and submit an updated version of 
> the draft 
> > if d one so. I will go ahead with the updated draft for the 
> protocol 
> > write up (i.e., the step before sending to Magnus and the IESG).
> >
> >  Martin
> >
> > ****
> > General
> > ****
> > I found the first part of the document (i.e., until section 
> 5) quite 
> > confusing and after section five quite clear. This does not 
> mean that 
> > there is an issue, as typically Internet drafts have the need to 
> > sketch tech things in the beginning without having the 
> reader already 
> > at the technical level. I assume that the text is fine 
> right now, as 
> > the WG has not pushed to change it.
> 
> These sections have been rewritten many times.  Please let us 
> know if you have any particular suggestion to improve clarity.

I can't say how to improve it. As said, if the WG is otherwise fine with it, we just leave it as is.



> 
> >
> > ****
> > Editorial:
> > ****
> >
> > - the idnits tool has found some issues (see below)
> 
> OK, will address.
> 
> > - Add line in memo heading with: Intended Status: Informational
> 
> Although the NSIS milestone says "Informational", the ID 
> tracker lists the status as "Proposed Standard"
> https://datatracker.ietf.org/idtracker/draft-ietf-nsis-qspec/ 
> <mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000038/!x
> -usc:https://datatracker.ietf.org/idtracker/draft-ietf-nsis-qs
> pec/> .  IMO the QSPEC document should be a PS document, in 
> close alignment with the NSLP PS document.  Many IANA 
> registries are created, etc.  I can't see the rationale for 
> NSLP being PS and QSPEC being Informational.  I do recall a 
> discussion on this point earlier and several WG members 
> expressed the same view.  Perhaps the WG members and chairs 
> can comment.

I remember to have discussed this with the ADs and agreement was that the QSPEC is informational. The charter has the final say.



> 
> > -  Section 1: Move to the very end of memo. It it is good to 
> > acknowledge other people, but it is fair enough to do it at 
> the very 
> > end, as technical protocol stuff comes first.
> 
> OK.
> 
> > - section 2: Adding a line saying that QSPEC readers should 
> (or better
> > must?) read the QoS NSLP in advance would be advantageous for the 
> > whole document.
> 
> Note that the first sentence of Section 2 references QoS NSLP 
> since the documents are closely tied.  The QSPEC document is 
> intended to be (and should be) self contained so that one 
> doesn't have to ("must") read something else first before 
> reading and understanding QSPEC.  However, your point is well 
> taken.  We can add a sentence in Section 2 such as "See 
> [QoS-SIG] for further details on QoS NSLP."

Adding the sentence would be great!

> 
> > - section 2, page 5, para starting with "Interoperability 
> between QoS 
> > NSIS entities (QNEs)..." says that parameters can be flagged or not 
> > flagged.
> > I
> > suggest to put the terms "flagged"/"non flagged" in 
> brackets and write 
> > mandatory and optional parameters. This makes it easier for 
> first time 
> > readers.
> 
> We've eliminated the terminology "mandatory" and "optional" 
> parameters.
> Parameters can be flagged by the M flag if they MUST be 
> interpreted, or otherwise, as follows:
> 
>  M Flag: When set indicates the subsequent parameter MUST be
>            interpreted. Otherwise the parameter can be ignored if not
>            understood.
> 
> We don't want to get back into the mandatory/optional 
> terminology at this point.

Ok, fine with me.

> 
> > - - section 2, page 5, para starting with " A local QSPEC can be 
> > defined in a local domain with the initiator QSPEC 
> encapsulated, ...". 
> > This paragraph is brief but describes a very powerful 
> mechanism of the 
> > QSPEC. I would suggest to remove the hint the TMOD 
> parameter and just 
> > write that the QSPEC allows local QPSECs that are domain specific. 
> > This also helps first time readers to understand a basic 
> feature of  
> > QPSEC but not the full implementation of it.
> 
> OK.
> 
> > - section 4.1, 2nd para, text in para starting with " New QoS NSLP 
> > message processing rules can only be defined in Standard...". Is it 
> > required to say this at this part of the document at all? I 
> remember 
> > this again stated in the document somewhere later on at an 
> appropriate 
> > place.
> 
> It's an important point and I think it appropriate to mention 
> it in Section 4.1.  Furthermore, I recall extensive 
> discussion on this sentence and I believe it was explicitly 
> agreed to include it here as well as later in the document.  
> Also, mentioning important points more than once often helps clarity.

Ok, fine with me.

> 
> > - section 4.2 two paras below figure 1. Suddenly there is 
> text about 
> > RESERVE and QUERY, but no hint to the QoS NSLP at all. Adding a 
> > reference to the QoS NSLP at this occasion would be excellent. 
> > Otherwise it  is hard to see where those terms are coming from
> 
> Good point, will do.
> 
> > - section 4.3.1, para starting with " When the TMOD parameter in 
> > included in QoS Available, it..." should read " When the TMOD 
> > parameter are included in QoS Available, it..."
> 
> I think the English is correct as it stands.  However, we 
> could say "When the TMOD sub-parameters are included ..."

I would prefer your suggestion, as this improves readability for non-native speakers (as I'm).

> 
> > - section 4.3.1. This section nevers talks about tmod-2! tmod-2 is 
> > mentioned only  in sections 6.2.1 and 6.2.2.
> 
> Right, good point.  We'll revise the text to refer to TMOD-1 
> and TMOD-2 and explain the difference.  We could include the 
> example of the need for the
> TMOD-2 parameter in Section 4.3.1 (see discussion/example 
> below of the need for the TMOD-2 parameter).
> 
> > - section 5, 1st and 2nd para suddenly use the E-/N-flag 
> without every 
> > explaining their meaning.
> 
> Well, this is where the M flag, E flag, and N flag are being 
> explained.  The first paragraph introduces them and there are 
> details later.  We could add text in the beginning such as 
> "Three flags are used in QSPEC, the M flag, E flag, and N 
> flag, which are explained in this section."

Please add this sentence, it also improves readability.

> 
> > - section 5.1, again the support of local QSPECs is quite 
> powerful but 
> > never really good explained with a figure. For instance, the first 
> > para of section
> > 5.1 could refer to a simple figure showing a network 
> configuration for 
> > a single flow, but with indications where which QSPEC is used. This 
> > instantly makes the whole concept better undestandable.
> 
> OK, we could add a figure analogous to Figure 3 in the 
> Y.1541-QOSM document 
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-y1541-qosm
> -05.txt 
> <mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000038/!x
> -usc:http://www.ietf.org/internet-drafts/draft-ietf-nsis-y1541
> -qosm-05.txt>  to explain the concept.

This would be great!

> 
> > - section 5.2.5. formatting error
> 
> OK.
> 
> > - section 5.3.1 and related. You use tables to define cases 
> and also 
> > refer to them later in the object definition. Thus it would 
> be good to 
> > label those tables.
> 
> OK, good suggestion.
> 
> > - section 5.3.5 has one formatting issue and one spelling error 
> > (s/described In [QoS-SIG]/ described in [QoS-SIG])
> 
> OK.
> 
> > - section 5.4. remove reference to NSIS extensibility 
> document, as we 
> > do not have it ready by now.
> 
> OK.
> 
> > - section 6.1. I got confused by all the different header 
> definition. 
> > I would propose to split 6.1. in subsections, i.e., one for each 
> > header definition. This improves readability.
> 
> OK, good suggestion.
> 
> > - section 6.2.1: Why is there this line    <TMOD-1> = <r> 
> <b> <p> <m>
> > [RFC2210, RFC2215]? It is now required for the object definition.
> 
> Right, the format is inconsistent with the other subsections 
> and will be revised accordingly.
> 
> > - section 8, text says " Object Types (12 bits):" but should read 
> > "QSPEC Object Types (12 bits):".
> 
> But then Section 6.1 would have to be revised to be 
> consistent in terminology.  While I have no big objection to 
> changing all of this, IMO it should stay as is; I think it is 
> clear that this is a QSPEC object type.

Ok.

> 
> > - appendix b: add a note in the first line that this 
> appendix should 
> > be removed by the RFC editor before publication.
> 
> OK.
> 
> >
> >
> >
> > ***
> > Technical
> > ***
> > - section 5.3.1, para starting with " The QSPEC parameter IDs and 
> > values included in the QoS Reserved...". This paragraph talks about 
> > how to set the parameters in the RESPONSE message for case 2. It is 
> > basically fine, but the second sentence is for me not 
> understandable 
> > (" For those QSPEC parameters that were also included in the QoS 
> > Available object in the RESERVE message, their value is copied into 
> > the QoS Desired object.") The paragraph is talking about responses, 
> > but in RESPONSE there is no QoS desired object anymore (at least 
> > according to the table above). I probably do misunderstand 
> something 
> > here?
> 
> Good catch.  The sentence needs to be corrected.  It should 
> be: "For those QSPEC parameters that were also included in 
> the QoS Available object in the RESERVE message, their value 
> is copied from the QoS Available object (in
> RESERVE) into the QoS Reserved object (in RESPONSE) ."
> 
> > - section 6.1 qspec header element definition. The length 
> definition 
> > in the qspec header definition contradicts the length definition at 
> > the beginning of section 6.1 One says "total length of qspec" the 
> > other "length is always exept header"
> 
> Very good catch!  IMO the section definition should be revised as
> follows:
> 
>  Length: The total length of the QSPEC -->
>  Length: The total length of the QSPEC excluding the common header

OK.

> 
> > - section 6.2.2., see also my comment above about tmod-2. 
> Even after 
> > reading section 6.2.2. I do not have any clue why there two tmod 
> > parameters.
> 
> This is based on discussions with David Black, who 
> recommended the second TMOD parameter to support DiffServ 
> applications (as noted in Section 6.2.2).
> Earlier versions of QSPEC included the following example (due 
> to David), which can be added back into the draft (probably 
> in Section 4.3.1):
> 
> "It is typically assumed that DiffServ EF traffic is shaped 
> at the ingress by a single rate token bucket.  Therefore, a 
> single TMOD parameter is sufficient to signal DiffServ EF 
> traffic.  However, for DiffServ AF traffic two sets of token 
> bucket parameters are needed, one token bucket for the 
> average traffic and one token bucket for the burst traffic.  
> [RFC2697] defines a Single Rate Three Color Marker (srTCM), 
> which meters a traffic stream and marks its packets according 
> to three traffic parameters, Committed Information Rate 
> (CIR), Committed Burst Size (CBS), and Excess Burst Size 
> (EBS), to be either green, yellow, or red.  A packet is 
> marked green if it does not exceed the CBS, yellow if it does 
> exceed the CBS, but not the EBS, and red otherwise.  
> [RFC2697] defines specific procedures using two token buckets 
> that run at the same rate.  Therefore 2 TMOD parameters are 
> sufficient to distinguish among 3 levels of drop precedence.  
> An example is also described in the Appendix to [RFC2597]."

This would be good!

> 
> Also, the first sentence in Section 6.2.2 should be changed 
> slightly to: ''A second, QSPEC <TMOD-2> parameter is 
> specified, as could be needed for example to support some 
> Diffserv applications." (added word "some").

Ok.

> 
> > - section 6.2.7. The slack term is 32 bits as integer. However the 
> > slack term must only be non-negative, i.e., it is actually 
> an unsigned 
> > int.
> > Why is
> > is not specified as unsigned int? However, the current value range 
> > definition is broken, as an integer of 32 bits cannot have 
> a maximum 
> > range to  2**32-1 (there are only 31 bits left...).
> 
> The coding of the slack term is based on RSVP coding:
> 
> RFC 2210 says:
> 
>       
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 11  |  Slack Term [S]  (32-bit integer)                             |
>        
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
> RFC 2212 says:
> "The Slack term, S, can be represented as a 32-bit integer.  Its value
>    can range from 0 to (2**32)-1 microseconds."
> 
> I agree it should be specified as an unsigned integer, and 
> the notation revised to (2**32)-1 as the maximum, to be 
> clear.  I believe the range 0 to
> (2**32)-1 is correct for an unsigned integer.

Right.

> 
> > This also holds true for
> > other
> > occasions where integer values are used (e.g. section 6.2.3!
> 
> Same comments as above.
> 
> > - section 6.2.11. para starting with " When excess 
> treatment is set to 
> > 'shape', ". What is the error handling if excess treatment 
> is set to 
> > 'shape'
> > and no TMOD parameter is given?
> 
> The E flag is set for the parameter and the reservation 
> fails.  This can be specified in Section 6.2.11.

Fine.

> 
> > - section 7. This section is extremely short. This might a 
> non-issue, 
> > but I personally had the feeling the security discussion is 
> too brief. 
> > This might be OK, but the document authors and the WG should be 
> > prepared for tough questions regarding this when going to the IESG. 
> > What about this document defining just the basics, but 
> other documents 
> > defining the real behaviour?
> > Is it assumed that this does not raise any new security issue?
> 
> Good points and questions.  QSPEC security is directly tied 
> to QoS NSLP security, and the QoS NSLP document has a very 
> detailed security section.
> All these considerations apply to QSPEC and that should be 
> noted at the beginning of Section 7.  I'm not aware of any 
> new security issues introduced by QSPEC beyond the point made 
> already in Section 7 on priority.
> Suggestions welcome from the WG on other security issues that 
> might arise from QSPEC.

I'm fine with leaving the section as short as it is. However, adding a reference to the QOS NSLp would be beneficial.

> 
> > - section 8 says in several places " A specification is required to 
> > depreciate, delete, or modify QSPEC versions." What happens 
> to deleted 
> > IANA values? Is IANA allowed to re-assign those or should they be 
> > treated as deprecated values, i.e., they cannot be used 
> anymore, but 
> > the value is blocked for ever?
> 
> These are IANA specific rules that I don't think need to be 
> reviewed in Section 8.

Ok, I'm just noting now to have misread this sentence, as a result of reading too much at the same time.

Thanks,

  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 
_______________________________________________
nsis mailing list
nsis@ietf.org
http://www.ietf.org/mailman/listinfo/nsis


From nsis-bounces@ietf.org  Tue Feb 19 08:24:47 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C4A2528C64E;
	Tue, 19 Feb 2008 08:24:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.942
X-Spam-Level: 
X-Spam-Status: No, score=-1.942 tagged_above=-999 required=5
	tests=[AWL=-1.732, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, 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 golvVcq5vqkH; Tue, 19 Feb 2008 08:24:46 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4A12828C53E;
	Tue, 19 Feb 2008 08:24:46 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C625128C5FA
	for <nsis@core3.amsl.com>; Tue, 19 Feb 2008 08:24:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 MdJHLeWpFbPv for <nsis@core3.amsl.com>;
	Tue, 19 Feb 2008 08:24:44 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 63F0928C58C
	for <nsis@ietf.org>; Tue, 19 Feb 2008 08:24:44 -0800 (PST)
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 19 Feb 2008 17:24:41 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m1JGOftu011108; 
	Tue, 19 Feb 2008 17:24:41 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m1JGOfp6020108; 
	Tue, 19 Feb 2008 16:24:41 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Feb 2008 17:24:41 +0100
Received: from [144.254.53.198] ([144.254.53.198]) by xfe-ams-332.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Feb 2008 17:24:40 +0100
In-Reply-To: <5F6519BF2DE0404D99B7C75607FF76FF4D10C7@mx1.office>
References: <C3C61BFC.EA3F%Stiemerling@nw.neclab.eu>
	<370957.34791.qm@web63604.mail.re1.yahoo.com>
	<5F6519BF2DE0404D99B7C75607FF76FF4D10C7@mx1.office>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <58B97422-395F-4278-8414-6F7507D91E3C@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Date: Tue, 19 Feb 2008 17:24:34 +0100
To: Martin Stiemerling <Stiemerling@nw.neclab.eu>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 19 Feb 2008 16:24:40.0686 (UTC)
	FILETIME=[ED89C0E0:01C87313]
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: cornelia.kappler@googlemail.com, nsis <nsis@ietf.org>
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://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

Hello,

For memory, the next rev of nsis-qspec is also expected to be aligned  =

with the Resolution of the issue related to QoS Parameters encoding  =

in <dime-qos-parameters>, <nsis-qspec> & <tsvwg-emeregncy-rsvp>. For  =

convenience, I included below the recap on the corresponding  =

resolution as announced on NSIS, DIME and TSVWG lists.

Just to make sure this does not fall through the cracks.

Cheers

Francois


>
> Begin forwarded message:
>> From: Francois Le Faucheur IMAP <flefauch@cisco.com>
>> Date: 3 December 2007 12:05:42 GMT+01:00
>> To: dime@ietf.org, nsis@ietf.org, tsvwg tsvwg <tsvwg@ietf.org>
>> Cc: Francois Le Faucheur IMAP <flefauch@cisco.com>, David Oran R  =

>> <oran@cisco.com>, Hannes Tschofenig <Hannes.Tschofenig@gmx.net>,  =

>> ken carlberg <carlberg@g11.org.uk>, Magnus Westerlund  =

>> <magnus.westerlund@ericsson.com>, James Polk <jmpolk@cisco.com>,  =

>> cornelia.kappler@nsn.com, "(IJ/ETH) B=E1der Attila"  =

>> <attila.bader@ericsson.com>, jouni.korhonen@teliasonera.com, Jukka  =

>> Manner MJ <jmanner@cs.Helsinki.FI>, tsvwg chair <tsvwg- =

>> chairs@tools.ietf.org>, nsis-chairs@tools.ietf.org, dime- =

>> chairs@tools.ietf.org, "john.loughney@nokia.com>"  =

>> <john.loughney@nokia.com>
>> Subject: Resolution of issue QoS Parameters encoding in <dime-qos- =

>> parameters>, <nsis-qspec> & <tsvwg-emeregncy-rsvp>
>>
>> Hello,
>>
>> The Issue:
>> =3D=3D=3D=3D=3D=3D=3D
>> Three different documents (dime-qos-parameters, nsis-qos-nslp,  =

>> tsvwg-emergency-rsvp) need to convey an overlapping set of QoS  =

>> parameters (specifically RPH-Priority and Admission Priority) and  =

>> currently do that in an inconsistent manner. This has been brought  =

>> up and partially discussed on the WG mailing lists.
>>
>> The Proposed Resolution
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> Co-authors of the three I-Ds as well as WG chairs of the  =

>> corresponding WGs converged on the following proposed resolution.  =

>> Please let us know if you have an issue/concern with this.
>>
>> o Regarding RPH-Priority:
>> 	* tsvwg-emergency-rsvp will go ahead with its requests to IANA to  =

>> provide numerical registry for RPH priority (via extending  =

>> existing RPH registry). See IANA Considerations section of tsvwg- =

>> emergency-rsvp.
>> 	* nsis-qspec (in section 6.2.10) will point to this registry  =

>> instead of defining its own values
>> 	* dime-qos-parameters (in section 4.11) will point to this  =

>> registry instead of defining its own values
>> 	* tsvwg-emergency-rsvp (in section 3.2) will keep pointing to  =

>> this registry.
>>
>> o Regarding Admission Priority:
>> 	* every protocol spec will only indicate that "higher value means  =

>> higher priority".
>> 	* there is no attempt to define what specific values should be  =

>> used for what. this is left outside the scope of the protocol specs.
>> 	* each protocol spec will add a statement clarifying that a given  =

>> Admission Priority is to be encoded with the same value in each of  =

>> the three protocol spec. For example, in tsvwg-emergency-rsvp,  =

>> under section 3.1.  we will add:
>> "      A given Admission Priority is encoded in this information  =

>> element
>> 	using the same value as when encoded in the Admission Priority
>> 	parameter defined in section 6.2.9 of [nsis-qspec], or in the  =

>> Admission
>> 	 Priority parameter defined in section 4.10 of [dime-qos- =

>> parameters].
>> 	In other words, a given value in any of the [emergency-rsvp]  =

>> Admission
>> 	Priority information element, the [nsis-qspec] Admission Priority  =

>> parameter
>> 	or the [dime-qos-parameters] Admission Priority parameter, refers to
>> 	the same Admission Priority.
>> "
>> 	* the mirror statement will be added in nsis-qspec (section  =

>> 6.2.9) and dime-qos-parameters (section 4.10)
>>
>> Francois
>>




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


From nsis-bounces@ietf.org  Tue Feb 19 15:24:30 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C4ACA28C67A;
	Tue, 19 Feb 2008 15:24:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.96
X-Spam-Level: 
X-Spam-Status: No, score=-0.96 tagged_above=-999 required=5 tests=[AWL=-0.750,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	RDNS_NONE=0.1, 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 yUBFOPAYZ1n9; Tue, 19 Feb 2008 15:24:29 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CD27628C0FE;
	Tue, 19 Feb 2008 15:24:29 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C5E703A68C4
	for <nsis@core3.amsl.com>; Tue, 19 Feb 2008 15:24:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 o8fVvlOQehIZ for <nsis@core3.amsl.com>;
	Tue, 19 Feb 2008 15:24:26 -0800 (PST)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230])
	by core3.amsl.com (Postfix) with ESMTP id 8656C28C287
	for <nsis@ietf.org>; Tue, 19 Feb 2008 15:24:26 -0800 (PST)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m1JNOD1H008004; Wed, 20 Feb 2008 01:24:16 +0200
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Feb 2008 21:58:53 +0200
Received: from daebe104.NOE.Nokia.com ([10.241.36.13]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Feb 2008 13:58:37 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 19 Feb 2008 13:58:36 -0600
Message-ID: <19EBBEC503C3B5469070E0A6674A533A01073360@daebe104.NOE.Nokia.com>
In-Reply-To: <58B97422-395F-4278-8414-6F7507D91E3C@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Review of draft-ietf-nsis-qspec-18.txt
Thread-Index: AchzFAEtMABQ16ObQVSVCAgH6znBCwAHcSgw
References: <C3C61BFC.EA3F%Stiemerling@nw.neclab.eu><370957.34791.qm@web63604.mail.re1.yahoo.com><5F6519BF2DE0404D99B7C75607FF76FF4D10C7@mx1.office>
	<58B97422-395F-4278-8414-6F7507D91E3C@cisco.com>
From: <john.loughney@nokia.com>
To: <flefauch@cisco.com>, <Stiemerling@nw.neclab.eu>
X-OriginalArrivalTime: 19 Feb 2008 19:58:37.0874 (UTC)
	FILETIME=[D1193120:01C87331]
X-Nokia-AV: Clean
Cc: nsis@ietf.org, cornelia.kappler@googlemail.com
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://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

Thanks Francois,

This is something that needs to be updated in the current draft.

John =


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

>Behalf Of ext Francois Le Faucheur IMAP
>Sent: 19 February, 2008 08:25
>To: Martin Stiemerling
>Cc: cornelia.kappler@googlemail.com; nsis
>Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.txt
>
>Hello,
>
>For memory, the next rev of nsis-qspec is also expected to be =

>aligned with the Resolution of the issue related to QoS =

>Parameters encoding in <dime-qos-parameters>, <nsis-qspec> & =

><tsvwg-emeregncy-rsvp>. For convenience, I included below the =

>recap on the corresponding resolution as announced on NSIS, =

>DIME and TSVWG lists.
>
>Just to make sure this does not fall through the cracks.
>
>Cheers
>
>Francois
>
>
>>
>> Begin forwarded message:
>>> From: Francois Le Faucheur IMAP <flefauch@cisco.com>
>>> Date: 3 December 2007 12:05:42 GMT+01:00
>>> To: dime@ietf.org, nsis@ietf.org, tsvwg tsvwg <tsvwg@ietf.org>
>>> Cc: Francois Le Faucheur IMAP <flefauch@cisco.com>, David Oran R =

>>> <oran@cisco.com>, Hannes Tschofenig =

><Hannes.Tschofenig@gmx.net>, ken =

>>> carlberg <carlberg@g11.org.uk>, Magnus Westerlund =

>>> <magnus.westerlund@ericsson.com>, James Polk <jmpolk@cisco.com>, =

>>> cornelia.kappler@nsn.com, "(IJ/ETH) B=E1der Attila"
>>> <attila.bader@ericsson.com>, jouni.korhonen@teliasonera.com, Jukka =

>>> Manner MJ <jmanner@cs.Helsinki.FI>, tsvwg chair <tsvwg- =

>>> chairs@tools.ietf.org>, nsis-chairs@tools.ietf.org, dime- =

>>> chairs@tools.ietf.org, "john.loughney@nokia.com>"
>>> <john.loughney@nokia.com>
>>> Subject: Resolution of issue QoS Parameters encoding in <dime-qos-
>>> parameters>, <nsis-qspec> & <tsvwg-emeregncy-rsvp>
>>>
>>> Hello,
>>>
>>> The Issue:
>>> =3D=3D=3D=3D=3D=3D=3D
>>> Three different documents (dime-qos-parameters, nsis-qos-nslp,
>>> tsvwg-emergency-rsvp) need to convey an overlapping set of QoS =

>>> parameters (specifically RPH-Priority and Admission Priority) and =

>>> currently do that in an inconsistent manner. This has been =

>brought up =

>>> and partially discussed on the WG mailing lists.
>>>
>>> The Proposed Resolution
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> Co-authors of the three I-Ds as well as WG chairs of the =

>>> corresponding WGs converged on the following proposed resolution.
>>> Please let us know if you have an issue/concern with this.
>>>
>>> o Regarding RPH-Priority:
>>> 	* tsvwg-emergency-rsvp will go ahead with its requests =

>to IANA to =

>>> provide numerical registry for RPH priority (via extending existing =

>>> RPH registry). See IANA Considerations section of tsvwg- =

>>> emergency-rsvp.
>>> 	* nsis-qspec (in section 6.2.10) will point to this =

>registry instead =

>>> of defining its own values
>>> 	* dime-qos-parameters (in section 4.11) will point to =

>this registry =

>>> instead of defining its own values
>>> 	* tsvwg-emergency-rsvp (in section 3.2) will keep =

>pointing to this =

>>> registry.
>>>
>>> o Regarding Admission Priority:
>>> 	* every protocol spec will only indicate that "higher =

>value means =

>>> higher priority".
>>> 	* there is no attempt to define what specific values =

>should be used =

>>> for what. this is left outside the scope of the protocol specs.
>>> 	* each protocol spec will add a statement clarifying =

>that a given =

>>> Admission Priority is to be encoded with the same value in each of =

>>> the three protocol spec. For example, in =

>tsvwg-emergency-rsvp, under =

>>> section 3.1.  we will add:
>>> "      A given Admission Priority is encoded in this information  =

>>> element
>>> 	using the same value as when encoded in the Admission Priority
>>> 	parameter defined in section 6.2.9 of [nsis-qspec], or in the =

>>> Admission
>>> 	 Priority parameter defined in section 4.10 of [dime-qos- =

>>> parameters].
>>> 	In other words, a given value in any of the [emergency-rsvp] =

>>> Admission
>>> 	Priority information element, the [nsis-qspec] =

>Admission Priority =

>>> parameter
>>> 	or the [dime-qos-parameters] Admission Priority =

>parameter, refers to
>>> 	the same Admission Priority.
>>> "
>>> 	* the mirror statement will be added in nsis-qspec (section
>>> 6.2.9) and dime-qos-parameters (section 4.10)
>>>
>>> Francois
>>>
>
>
>
>
>_______________________________________________
>nsis mailing list
>nsis@ietf.org
>http://www.ietf.org/mailman/listinfo/nsis
>
_______________________________________________
nsis mailing list
nsis@ietf.org
http://www.ietf.org/mailman/listinfo/nsis


From nsis-bounces@ietf.org  Wed Feb 20 00:08:11 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 17AFF28C75E;
	Wed, 20 Feb 2008 00:08:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.402
X-Spam-Level: *
X-Spam-Status: No, score=1.402 tagged_above=-999 required=5 tests=[AWL=0.350,
	BAYES_05=-1.11, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	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 a4wSKnrs0pqf; Wed, 20 Feb 2008 00:08:10 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2514728C741;
	Wed, 20 Feb 2008 00:08:10 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0363528C74E
	for <nsis@core3.amsl.com>; Wed, 20 Feb 2008 00:08:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 KprU0U6XgOJ3 for <nsis@core3.amsl.com>;
	Wed, 20 Feb 2008 00:08:08 -0800 (PST)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de
	[141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id 4DA4028C739
	for <nsis@ietf.org>; Wed, 20 Feb 2008 00:08:08 -0800 (PST)
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 1JRjzm-0000mm-EG; Wed, 20 Feb 2008 09:08:04 +0100
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 2AAB72FC014;
	Wed, 20 Feb 2008 09:08:02 +0100 (CET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by vorta.tm.uka.de (Postfix) with ESMTP id E3D27100D4;
	Wed, 20 Feb 2008 09:09:02 +0100 (CET)
Message-ID: <47BBE01E.1060008@tm.uka.de>
Date: Wed, 20 Feb 2008 09:09:02 +0100
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: Martin Stiemerling <Stiemerling@nw.neclab.eu>
References: <5F6519BF2DE0404D99B7C75607FF76FF4D0D5B@mx1.office>
In-Reply-To: <5F6519BF2DE0404D99B7C75607FF76FF4D0D5B@mx1.office>
X-Enigmail-Version: 0.95.0
X-Spam-Host: iramx2.ira.uni-karlsruhe.de
X-ATIS-Checksum: v3zoCAcc32ckk
Cc: nsis@ietf.org
Subject: Re: [NSIS] FW: I-D Action:draft-manner-router-alert-iana-01.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: <http://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: <http://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 Martin and all,

Martin Stiemerling wrote:
> FYI, as this draft is important to NSIS. Please take a look and comment if necessary.

I read the document and it looks good to me.

Regards,
 Roland

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


From nsis-bounces@ietf.org  Wed Feb 20 00:28:27 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6810C3A6965;
	Wed, 20 Feb 2008 00:28:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.522
X-Spam-Level: 
X-Spam-Status: No, score=-0.522 tagged_above=-999 required=5
	tests=[AWL=-0.312, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, 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 b7WuApCAFFSH; Wed, 20 Feb 2008 00:28:26 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 60A9C3A6923;
	Wed, 20 Feb 2008 00:28:26 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0B72C3A6923
	for <nsis@core3.amsl.com>; Wed, 20 Feb 2008 00:28:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 Lu2ZPlHVLMuJ for <nsis@core3.amsl.com>;
	Wed, 20 Feb 2008 00:28:24 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id CCCD23A68CA
	for <nsis@ietf.org>; Wed, 20 Feb 2008 00:28:23 -0800 (PST)
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 99EFC2C000357;
	Wed, 20 Feb 2008 09:28:20 +0100 (CET)
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 n9Q6pWc22dp1; Wed, 20 Feb 2008 09:28:20 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id 771742C000355;
	Wed, 20 Feb 2008 09:28:00 +0100 (CET)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 20 Feb 2008 09:27:59 +0100
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF4D1139@mx1.office>
In-Reply-To: <58B97422-395F-4278-8414-6F7507D91E3C@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Review of draft-ietf-nsis-qspec-18.txt
Thread-Index: AchzE/Rlbb8rRcxCSPGXgUIyp2sVwAAhnIyw
References: <C3C61BFC.EA3F%Stiemerling@nw.neclab.eu>
	<370957.34791.qm@web63604.mail.re1.yahoo.com>
	<5F6519BF2DE0404D99B7C75607FF76FF4D10C7@mx1.office>
	<58B97422-395F-4278-8414-6F7507D91E3C@cisco.com>
From: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>
To: "Francois Le Faucheur IMAP" <flefauch@cisco.com>
Cc: cornelia.kappler@googlemail.com, nsis <nsis@ietf.org>
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://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

Hello Francois,

Thanks for bringing this back to attention. I've forgotten about this.

Jerry: Please fix this in the new version of the QSPEC draft.

Thanks,

  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  =


> -----Original Message-----
> From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com] =

> Sent: Tuesday, February 19, 2008 5:25 PM
> To: Martin Stiemerling
> Cc: Francois Le Faucheur IMAP; Gerald Ash; nsis; =

> cornelia.kappler@googlemail.com
> Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.txt
> =

> Hello,
> =

> For memory, the next rev of nsis-qspec is also expected to be =

> aligned with the Resolution of the issue related to QoS =

> Parameters encoding in <dime-qos-parameters>, <nsis-qspec> & =

> <tsvwg-emeregncy-rsvp>. For convenience, I included below the =

> recap on the corresponding resolution as announced on NSIS, =

> DIME and TSVWG lists.
> =

> Just to make sure this does not fall through the cracks.
> =

> Cheers
> =

> Francois
> =

> =

> >
> > Begin forwarded message:
> >> From: Francois Le Faucheur IMAP <flefauch@cisco.com>
> >> Date: 3 December 2007 12:05:42 GMT+01:00
> >> To: dime@ietf.org, nsis@ietf.org, tsvwg tsvwg <tsvwg@ietf.org>
> >> Cc: Francois Le Faucheur IMAP <flefauch@cisco.com>, David Oran R =

> >> <oran@cisco.com>, Hannes Tschofenig =

> <Hannes.Tschofenig@gmx.net>, ken =

> >> carlberg <carlberg@g11.org.uk>, Magnus Westerlund =

> >> <magnus.westerlund@ericsson.com>, James Polk <jmpolk@cisco.com>, =

> >> cornelia.kappler@nsn.com, "(IJ/ETH) B=E1der Attila"
> >> <attila.bader@ericsson.com>, jouni.korhonen@teliasonera.com, Jukka =

> >> Manner MJ <jmanner@cs.Helsinki.FI>, tsvwg chair <tsvwg- =

> >> chairs@tools.ietf.org>, nsis-chairs@tools.ietf.org, dime- =

> >> chairs@tools.ietf.org, "john.loughney@nokia.com>"
> >> <john.loughney@nokia.com>
> >> Subject: Resolution of issue QoS Parameters encoding in <dime-qos-
> >> parameters>, <nsis-qspec> & <tsvwg-emeregncy-rsvp>
> >>
> >> Hello,
> >>
> >> The Issue:
> >> =3D=3D=3D=3D=3D=3D=3D
> >> Three different documents (dime-qos-parameters, nsis-qos-nslp,
> >> tsvwg-emergency-rsvp) need to convey an overlapping set of QoS =

> >> parameters (specifically RPH-Priority and Admission Priority) and =

> >> currently do that in an inconsistent manner. This has been =

> brought up =

> >> and partially discussed on the WG mailing lists.
> >>
> >> The Proposed Resolution
> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >> Co-authors of the three I-Ds as well as WG chairs of the =

> >> corresponding WGs converged on the following proposed resolution.
> >> Please let us know if you have an issue/concern with this.
> >>
> >> o Regarding RPH-Priority:
> >> 	* tsvwg-emergency-rsvp will go ahead with its requests =

> to IANA to =

> >> provide numerical registry for RPH priority (via extending =

> existing =

> >> RPH registry). See IANA Considerations section of tsvwg- =

> >> emergency-rsvp.
> >> 	* nsis-qspec (in section 6.2.10) will point to this =

> registry instead =

> >> of defining its own values
> >> 	* dime-qos-parameters (in section 4.11) will point to =

> this registry =

> >> instead of defining its own values
> >> 	* tsvwg-emergency-rsvp (in section 3.2) will keep =

> pointing to this =

> >> registry.
> >>
> >> o Regarding Admission Priority:
> >> 	* every protocol spec will only indicate that "higher =

> value means =

> >> higher priority".
> >> 	* there is no attempt to define what specific values =

> should be used =

> >> for what. this is left outside the scope of the protocol specs.
> >> 	* each protocol spec will add a statement clarifying =

> that a given =

> >> Admission Priority is to be encoded with the same value in each of =

> >> the three protocol spec. For example, in =

> tsvwg-emergency-rsvp, under =

> >> section 3.1.  we will add:
> >> "      A given Admission Priority is encoded in this information  =

> >> element
> >> 	using the same value as when encoded in the Admission Priority
> >> 	parameter defined in section 6.2.9 of [nsis-qspec], or in the =

> >> Admission
> >> 	 Priority parameter defined in section 4.10 of [dime-qos- =

> >> parameters].
> >> 	In other words, a given value in any of the [emergency-rsvp] =

> >> Admission
> >> 	Priority information element, the [nsis-qspec] =

> Admission Priority =

> >> parameter
> >> 	or the [dime-qos-parameters] Admission Priority =

> parameter, refers to
> >> 	the same Admission Priority.
> >> "
> >> 	* the mirror statement will be added in nsis-qspec (section
> >> 6.2.9) and dime-qos-parameters (section 4.10)
> >>
> >> Francois
> >>
> =

> =

> =

> =

> =

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


From nsis-bounces@ietf.org  Wed Feb 20 07:58:25 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 37C2C28C1E3;
	Wed, 20 Feb 2008 07:58:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.282
X-Spam-Level: *
X-Spam-Status: No, score=1.282 tagged_above=-999 required=5 tests=[AWL=0.492,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_MESSAGE=1, RDNS_NONE=0.1, 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 0QzlYAzsRirb; Wed, 20 Feb 2008 07:58:23 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AEA983A6A7C;
	Wed, 20 Feb 2008 07:58:23 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 20DD73A68E8
	for <nsis@core3.amsl.com>; Wed, 20 Feb 2008 07:58:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 aiWTLqNZ34DB for <nsis@core3.amsl.com>;
	Wed, 20 Feb 2008 07:58:21 -0800 (PST)
Received: from web63605.mail.re1.yahoo.com (web63605.mail.re1.yahoo.com
	[69.147.97.75]) by core3.amsl.com (Postfix) with SMTP id 630D23A68A3
	for <nsis@ietf.org>; Wed, 20 Feb 2008 07:58:21 -0800 (PST)
Received: (qmail 46075 invoked by uid 60001); 20 Feb 2008 15:58:17 -0000
X-YMail-OSG: ETsnCW8VM1lWSnUI9ImNDkRuakrkhsUdjCFUqZjN8dqYCsf.hVbUXyP0jRZOaOf_1ynxH8QAg210.g1uNeJKyH9.iIB80xJVeHh.lhkxHBkLmHsMLkSQX89zjnzqmHSR
Received: from [76.19.255.157] by web63605.mail.re1.yahoo.com via HTTP;
	Wed, 20 Feb 2008 07:58:17 PST
Date: Wed, 20 Feb 2008 07:58:17 -0800 (PST)
From: Gerald Ash <gash5107@yahoo.com>
To: Francois Le Faucheur IMAP <flefauch@cisco.com>,
	Martin Stiemerling <Stiemerling@nw.neclab.eu>, nsis <nsis@ietf.org>
In-Reply-To: <58B97422-395F-4278-8414-6F7507D91E3C@cisco.com>
MIME-Version: 1.0
Message-ID: <824621.42714.qm@web63605.mail.re1.yahoo.com>
Cc: cornelia.kappler@googlemail.com
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0474171622=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

--===============0474171622==
Content-Type: multipart/alternative; boundary="0-436314800-1203523097=:42714"
Content-Transfer-Encoding: 8bit

--0-436314800-1203523097=:42714
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Francois,
   
  In your "Proposed Resolution" posting to NSIS on 3 December http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html you say:
   
  > The Proposed Resolution
> ===================
> Co-authors of the three I-Ds as well as WG chairs of the 
  > corresponding WGs converged on the following proposed 
  > resolution. 
   
  I saw no discussion of this proposed resolution on the NSIS list.  Who were the QSPEC co-authors who worked with you on the proposed resolution?
   
  > o Regarding RPH-Priority:
> * tsvwg-emergency-rsvp will go ahead with its requests to
  > IANA to provide numerical registry for RPH priority (via 
  > extending existing RPH registry). See IANA Considerations
  > section of tsvwg-emergency-rsvp.
  > * nsis-qspec (in section 6.2.10) will point to this registry
  > instead of defining its own values
   
  OK.
   
  > o Regarding Admission Priority:
> * every protocol spec will only indicate that "higher value
  > means higher priority".
  > * there is no attempt to define what specific values should
  > be used for what. this is left outside the scope of the
  > protocol specs.
* each protocol spec will add a statement clarifying that a
  > given Admission Priority is to be encoded with the same
  > value in each of the three protocol spec. For example, in
  > tsvwg-emergency-rsvp, under section 3.1. we will add:
" A given Admission Priority is encoded in this information
  > element using the same value as when encoded in the
  > Admission Priority parameter defined in section 6.2.9 of
  > [nsis-qspec], or in the Admission Priority parameter
  > defined in section 4.10 of [dime-qos-parameters].
  > In other words, a given value in any of the
  > [emergency-rsvp] Admission Priority information element,
  > the [nsis-qspec] Admission Priority parameter or the
  > [dime-qos-parameters] Admission Priority parameter,
  > refers to the same Admission Priority.

  The above proposed paragraph is really unclear.  Which draft is setting up IANA Registries to assign Admission Priority parameters?  The way it reads it sounds like all three drafts are setting up registries but that somehow (magically) all refer "to the same Admission Priority".  How can that be if they assign different values?  Right now emergency-rsvp and nsis-qspec set up registries for Admission Priority and dime-qos-parameters is using the nsis-qspec registry as I recall.
   
  Please clarify the proposal as to which draft is setting up a registry for Admission Priority.  Also, please provide clearer proposed text to include in the drafts.  
   
  It would be good to see some discussion of the proposal on the list, to confirm and validate agreement of the WG.
   
  Jerry
  

Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:
  Hello,

For memory, the next rev of nsis-qspec is also expected to be aligned 
with the Resolution of the issue related to QoS Parameters encoding 
in , & . For 
convenience, I included below the recap on the corresponding 
resolution as announced on NSIS, DIME and TSVWG lists.

Just to make sure this does not fall through the cracks.

Cheers

Francois


>
> Begin forwarded message:
>> From: Francois Le Faucheur IMAP 
>> Date: 3 December 2007 12:05:42 GMT+01:00
>> To: dime@ietf.org, nsis@ietf.org, tsvwg tsvwg 
>> Cc: Francois Le Faucheur IMAP , David Oran R 
>> , Hannes Tschofenig , 
>> ken carlberg , Magnus Westerlund 
>> , James Polk , 
>> cornelia.kappler@nsn.com, "(IJ/ETH) Báder Attila" 
>> , jouni.korhonen@teliasonera.com, Jukka 
>> Manner MJ , tsvwg chair >> chairs@tools.ietf.org>, nsis-chairs@tools.ietf.org, dime- 
>> chairs@tools.ietf.org, "john.loughney@nokia.com>" 
>> 
>> Subject: Resolution of issue QoS Parameters encoding in >> parameters>, & 
>>
>> Hello,
>>
>> The Issue:
>> =======
>> Three different documents (dime-qos-parameters, nsis-qos-nslp, 
>> tsvwg-emergency-rsvp) need to convey an overlapping set of QoS 
>> parameters (specifically RPH-Priority and Admission Priority) and 
>> currently do that in an inconsistent manner. This has been brought 
>> up and partially discussed on the WG mailing lists.
>>
>> The Proposed Resolution
>> ===================
>> Co-authors of the three I-Ds as well as WG chairs of the 
>> corresponding WGs converged on the following proposed resolution. 
>> Please let us know if you have an issue/concern with this.
>>
>> o Regarding RPH-Priority:
>> * tsvwg-emergency-rsvp will go ahead with its requests to IANA to 
>> provide numerical registry for RPH priority (via extending 
>> existing RPH registry). See IANA Considerations section of tsvwg- 
>> emergency-rsvp.
>> * nsis-qspec (in section 6.2.10) will point to this registry 
>> instead of defining its own values
>> * dime-qos-parameters (in section 4.11) will point to this 
>> registry instead of defining its own values
>> * tsvwg-emergency-rsvp (in section 3.2) will keep pointing to 
>> this registry.
>>
>> o Regarding Admission Priority:
>> * every protocol spec will only indicate that "higher value means 
>> higher priority".
>> * there is no attempt to define what specific values should be 
>> used for what. this is left outside the scope of the protocol specs.
>> * each protocol spec will add a statement clarifying that a given 
>> Admission Priority is to be encoded with the same value in each of 
>> the three protocol spec. For example, in tsvwg-emergency-rsvp, 
>> under section 3.1. we will add:
>> " A given Admission Priority is encoded in this information 
>> element
>> using the same value as when encoded in the Admission Priority
>> parameter defined in section 6.2.9 of [nsis-qspec], or in the 
>> Admission
>> Priority parameter defined in section 4.10 of [dime-qos- 
>> parameters].
>> In other words, a given value in any of the [emergency-rsvp] 
>> Admission
>> Priority information element, the [nsis-qspec] Admission Priority 
>> parameter
>> or the [dime-qos-parameters] Admission Priority parameter, refers to
>> the same Admission Priority.
>> "
>> * the mirror statement will be added in nsis-qspec (section 
>> 6.2.9) and dime-qos-parameters (section 4.10)
>>
>> Francois
>>






       
---------------------------------
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.
--0-436314800-1203523097=:42714
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div><FONT face="Courier New">Francois,</FONT></div>  <div><FONT face="Courier New"></FONT>&nbsp;</div>  <div><FONT face="Courier New">In your "Proposed Resolution" posting to NSIS on 3 December <A href="http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html</A>&nbsp;you say:</FONT></div>  <div><FONT face="Courier New"></FONT>&nbsp;</div>  <div><FONT face="Courier New">&gt; The Proposed Resolution<BR>&gt; ===================<BR>&gt; Co-authors of the three I-Ds as well as WG chairs of the </FONT></div>  <div><FONT face="Courier New">&gt; corresponding WGs converged on the following proposed </FONT></div>  <div><FONT face="Courier New">&gt; resolution. </FONT></div>  <div><FONT face="Courier New"></FONT>&nbsp;</div>  <div><FONT face="Courier New">I saw no discussion of this proposed resolution on the NSIS list.&nbsp; Who were the QSPEC co-authors who worked with you on the proposed
 resolution?</FONT></div>  <div>&nbsp;</div>  <div><FONT face="Courier New">&gt; o Regarding RPH-Priority:<BR>&gt; * tsvwg-emergency-rsvp will go ahead with its requests to</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;IANA </FONT><FONT face="Courier New">to provide numerical registry for RPH priority (via </FONT></div>  <div><FONT face="Courier New">&gt; extending existing RPH registry). See IANA Considerations</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;section of tsvwg-emergency-rsvp.</FONT></div>  <div><FONT face="Courier New">&gt; * nsis-qspec (in section 6.2.10) will point to this registry</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;instead of defining its own values</FONT></div>  <div><FONT face="Courier New"></FONT>&nbsp;</div>  <div><FONT face="Courier New">OK.</FONT></div>  <div><FONT face="Courier New"></FONT>&nbsp;</div>  <div><FONT face="Courier New">&gt; o Regarding Admission Priority:<BR>&gt; * every protocol spec will only
 indicate that "higher value</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;means higher priority".</FONT></div>  <div><FONT face="Courier New">&gt; * there is no attempt to define what specific values should</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;be used for what. this is left outside the scope of the</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;protocol specs.<BR>* each protocol spec will add a statement clarifying that a</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;given Admission Priority is to be encoded with the same</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;value in each of the three protocol spec. For example, in</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;tsvwg-emergency-rsvp, under section 3.1. we will add:<BR>" A given Admission Priority is encoded in this information</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;element using the same value as when encoded in the</FONT></div>  <div><FONT
 face="Courier New">&gt;&nbsp;Admission Priority parameter defined in section 6.2.9 of</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;[nsis-qspec], or in the Admission Priority parameter</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;defined in section 4.10 of [dime-qos-parameters].</FONT></div>  <div><FONT face="Courier New">&gt; In other words, a given value in any of the</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;[emergency-rsvp] Admission Priority information element,</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;the [nsis-qspec] Admission Priority parameter or the</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;[dime-qos-parameters] Admission Priority parameter,</FONT></div>  <div><FONT face="Courier New">&gt;&nbsp;refers to the same Admission Priority.<BR></FONT></div>  <div><FONT face="Courier New">The above proposed paragraph is really unclear.&nbsp; Which draft&nbsp;is setting up IANA Registries to assign Admission Priority
 parameters?&nbsp; The way it reads it sounds like all three drafts are setting up registries but that somehow&nbsp;(magically) all&nbsp;refer "to the same Admission Priority".&nbsp; How can that be if they assign different values?&nbsp; Right now emergency-rsvp and nsis-qspec set up registries for Admission Priority and dime-qos-parameters is using the nsis-qspec registry as I recall.</FONT></div>  <div><FONT face="Courier New"></FONT>&nbsp;</div>  <div><FONT face="Courier New">Please clarify the proposal as to which draft is setting up a registry for Admission Priority.&nbsp; Also, please provide clearer&nbsp;proposed text to include in the drafts.&nbsp; </FONT></div>  <div><FONT face="Courier New"></FONT>&nbsp;</div>  <div><FONT face="Courier New">It would be good to see some discussion of the proposal on the list, to confirm and validate agreement of the WG.</FONT></div>  <div><FONT face="Courier New"></FONT>&nbsp;</div>  <div><FONT face="Courier New">Jerry</div></FONT>
  <div><BR><BR><B><I>Francois Le Faucheur IMAP &lt;flefauch@cisco.com&gt;</I></B> wrote:</div>  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hello,<BR><BR>For memory, the next rev of nsis-qspec is also expected to be aligned <BR>with the Resolution of the issue related to QoS Parameters encoding <BR>in <DIME-QOS-PARAMETERS>, <NSIS-QSPEC>&amp; <TSVWG-EMEREGNCY-RSVP>. For <BR>convenience, I included below the recap on the corresponding <BR>resolution as announced on NSIS, DIME and TSVWG lists.<BR><BR>Just to make sure this does not fall through the cracks.<BR><BR>Cheers<BR><BR>Francois<BR><BR><BR>&gt;<BR>&gt; Begin forwarded message:<BR>&gt;&gt; From: Francois Le Faucheur IMAP <FLEFAUCH@CISCO.COM><BR>&gt;&gt; Date: 3 December 2007 12:05:42 GMT+01:00<BR>&gt;&gt; To: dime@ietf.org, nsis@ietf.org, tsvwg tsvwg <TSVWG@IETF.ORG><BR>&gt;&gt; Cc: Francois Le Faucheur IMAP <FLEFAUCH@CISCO.COM>, David Oran R <BR>&gt;&gt;
 <ORAN@CISCO.COM>, Hannes Tschofenig <HANNES.TSCHOFENIG@GMX.NET>, <BR>&gt;&gt; ken carlberg <CARLBERG@G11.ORG.UK>, Magnus Westerlund <BR>&gt;&gt; <MAGNUS.WESTERLUND@ERICSSON.COM>, James Polk <JMPOLK@CISCO.COM>, <BR>&gt;&gt; cornelia.kappler@nsn.com, "(IJ/ETH) Báder Attila" <BR>&gt;&gt; <ATTILA.BADER@ERICSSON.COM>, jouni.korhonen@teliasonera.com, Jukka <BR>&gt;&gt; Manner MJ <JMANNER@CS.HELSINKI.FI>, tsvwg chair <TSVWG- <br>&gt;&gt; chairs@tools.ietf.org&gt;, nsis-chairs@tools.ietf.org, dime- <BR>&gt;&gt; chairs@tools.ietf.org, "john.loughney@nokia.com&gt;" <BR>&gt;&gt; <JOHN.LOUGHNEY@NOKIA.COM><BR>&gt;&gt; Subject: Resolution of issue QoS Parameters encoding in <DIME-QOS- <br>&gt;&gt; parameters&gt;, <NSIS-QSPEC>&amp; <TSVWG-EMEREGNCY-RSVP><BR>&gt;&gt;<BR>&gt;&gt; Hello,<BR>&gt;&gt;<BR>&gt;&gt; The Issue:<BR>&gt;&gt; =======<BR>&gt;&gt; Three different documents (dime-qos-parameters, nsis-qos-nslp, <BR>&gt;&gt; tsvwg-emergency-rsvp) need to convey an overlapping set of QoS
 <BR>&gt;&gt; parameters (specifically RPH-Priority and Admission Priority) and <BR>&gt;&gt; currently do that in an inconsistent manner. This has been brought <BR>&gt;&gt; up and partially discussed on the WG mailing lists.<BR>&gt;&gt;<BR>&gt;&gt; The Proposed Resolution<BR>&gt;&gt; ===================<BR>&gt;&gt; Co-authors of the three I-Ds as well as WG chairs of the <BR>&gt;&gt; corresponding WGs converged on the following proposed resolution. <BR>&gt;&gt; Please let us know if you have an issue/concern with this.<BR>&gt;&gt;<BR>&gt;&gt; o Regarding RPH-Priority:<BR>&gt;&gt; * tsvwg-emergency-rsvp will go ahead with its requests to IANA to <BR>&gt;&gt; provide numerical registry for RPH priority (via extending <BR>&gt;&gt; existing RPH registry). See IANA Considerations section of tsvwg- <BR>&gt;&gt; emergency-rsvp.<BR>&gt;&gt; * nsis-qspec (in section 6.2.10) will point to this registry <BR>&gt;&gt; instead of defining its own values<BR>&gt;&gt; * dime-qos-parameters
 (in section 4.11) will point to this <BR>&gt;&gt; registry instead of defining its own values<BR>&gt;&gt; * tsvwg-emergency-rsvp (in section 3.2) will keep pointing to <BR>&gt;&gt; this registry.<BR>&gt;&gt;<BR>&gt;&gt; o Regarding Admission Priority:<BR>&gt;&gt; * every protocol spec will only indicate that "higher value means <BR>&gt;&gt; higher priority".<BR>&gt;&gt; * there is no attempt to define what specific values should be <BR>&gt;&gt; used for what. this is left outside the scope of the protocol specs.<BR>&gt;&gt; * each protocol spec will add a statement clarifying that a given <BR>&gt;&gt; Admission Priority is to be encoded with the same value in each of <BR>&gt;&gt; the three protocol spec. For example, in tsvwg-emergency-rsvp, <BR>&gt;&gt; under section 3.1. we will add:<BR>&gt;&gt; " A given Admission Priority is encoded in this information <BR>&gt;&gt; element<BR>&gt;&gt; using the same value as when encoded in the Admission Priority<BR>&gt;&gt; parameter
 defined in section 6.2.9 of [nsis-qspec], or in the <BR>&gt;&gt; Admission<BR>&gt;&gt; Priority parameter defined in section 4.10 of [dime-qos- <BR>&gt;&gt; parameters].<BR>&gt;&gt; In other words, a given value in any of the [emergency-rsvp] <BR>&gt;&gt; Admission<BR>&gt;&gt; Priority information element, the [nsis-qspec] Admission Priority <BR>&gt;&gt; parameter<BR>&gt;&gt; or the [dime-qos-parameters] Admission Priority parameter, refers to<BR>&gt;&gt; the same Admission Priority.<BR>&gt;&gt; "<BR>&gt;&gt; * the mirror statement will be added in nsis-qspec (section <BR>&gt;&gt; 6.2.9) and dime-qos-parameters (section 4.10)<BR>&gt;&gt;<BR>&gt;&gt; Francois<BR>&gt;&gt;<BR><BR><BR><BR><BR></BLOCKQUOTE><BR><p>&#32;
      <hr size=1>Looking for last minute shopping deals? <a href="http://us.rd.yahoo.com/evt=51734/*http://tools.search.yahoo.com/newsearch/category.php?category=shopping"> 
Find them fast with Yahoo! Search.</a>
--0-436314800-1203523097=:42714--

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

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

--===============0474171622==--


From nsis-bounces@ietf.org  Wed Feb 20 08:43:53 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D037828C197;
	Wed, 20 Feb 2008 08:43:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.125
X-Spam-Level: 
X-Spam-Status: No, score=-1.125 tagged_above=-999 required=5
	tests=[AWL=-1.916, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, MIME_HTML_MOSTLY=0.001,
	RDNS_NONE=0.1, 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 WmUbbe58LPYd; Wed, 20 Feb 2008 08:43:51 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA7F13A6E35;
	Wed, 20 Feb 2008 08:43:51 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B57713A6E35
	for <nsis@core3.amsl.com>; Wed, 20 Feb 2008 08:43:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 m8HFsHLTsN7j for <nsis@core3.amsl.com>;
	Wed, 20 Feb 2008 08:43:49 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 2C0603A6A90
	for <nsis@ietf.org>; Wed, 20 Feb 2008 08:43:48 -0800 (PST)
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 20 Feb 2008 17:43:44 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m1KGhiAa004542; 
	Wed, 20 Feb 2008 17:43:44 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m1KGhdp6005038; 
	Wed, 20 Feb 2008 16:43:41 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Feb 2008 17:43:40 +0100
Received: from [144.254.53.198] ([144.254.53.198]) by xfe-ams-332.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Feb 2008 17:43:41 +0100
In-Reply-To: <824621.42714.qm@web63605.mail.re1.yahoo.com>
References: <824621.42714.qm@web63605.mail.re1.yahoo.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <4EFF5784-4564-4730-A5C1-CD0477DE740A@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Date: Wed, 20 Feb 2008 17:43:35 +0100
To: Gerald Ash <gash5107@yahoo.com>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 20 Feb 2008 16:43:41.0575 (UTC)
	FILETIME=[BFF95970:01C873DF]
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: cornelia.kappler@googlemail.com, nsis <nsis@ietf.org>
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0027416326=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


--===============0027416326==
Content-Type: multipart/alternative; boundary=Apple-Mail-5--267167476


--Apple-Mail-5--267167476
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=ISO-8859-1;
	delsp=yes;
	format=flowed

Hello Jerry,

On 20 Feb 2008, at 16:58, Gerald Ash wrote:

> Francois,
>
> In your "Proposed Resolution" posting to NSIS on 3 December http://=20
> www.ietf.org/mail-archive/web/nsis/current/msg08155.html you say:
>
> > The Proposed Resolution
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > Co-authors of the three I-Ds as well as WG chairs of the
> > corresponding WGs converged on the following proposed
> > resolution.
>
> I saw no discussion of this proposed resolution on the NSIS list.

which is why we've been assuming there was no issue with it.


> Who were the QSPEC co-authors who worked with you on the proposed =20
> resolution?

Attila, Cornelia and Dave Oran (+ NSIS WG chairs).


>
> > o Regarding RPH-Priority:
> > * tsvwg-emergency-rsvp will go ahead with its requests to
> > IANA to provide numerical registry for RPH priority (via
> > extending existing RPH registry). See IANA Considerations
> > section of tsvwg-emergency-rsvp.
> > * nsis-qspec (in section 6.2.10) will point to this registry
> > instead of defining its own values
>
> OK.
>
> > o Regarding Admission Priority:
> > * every protocol spec will only indicate that "higher value
> > means higher priority".
> > * there is no attempt to define what specific values should
> > be used for what. this is left outside the scope of the
> > protocol specs.
> * each protocol spec will add a statement clarifying that a
> > given Admission Priority is to be encoded with the same
> > value in each of the three protocol spec. For example, in
> > tsvwg-emergency-rsvp, under section 3.1. we will add:
> " A given Admission Priority is encoded in this information
> > element using the same value as when encoded in the
> > Admission Priority parameter defined in section 6.2.9 of
> > [nsis-qspec], or in the Admission Priority parameter
> > defined in section 4.10 of [dime-qos-parameters].
> > In other words, a given value in any of the
> > [emergency-rsvp] Admission Priority information element,
> > the [nsis-qspec] Admission Priority parameter or the
> > [dime-qos-parameters] Admission Priority parameter,
> > refers to the same Admission Priority.
> The above proposed paragraph is really unclear.  Which draft is =20
> setting up IANA Registries to assign Admission Priority =20
> parameters?  The way it reads it sounds like all three drafts are =20
> setting up registries but that somehow (magically) all refer "to =20
> the same Admission Priority".  How can that be if they assign =20
> different values?  Right now emergency-rsvp and nsis-qspec set up =20
> registries for Admission Priority and dime-qos-parameters is using =20
> the nsis-qspec registry as I recall.
>
> Please clarify the proposal as to which draft is setting up a =20
> registry for Admission Priority.

No registry is setup.
It is up to a network administrator to decide how many/which =20
admission priority gets used for what. This is similar to how =20
Preemption is used (ie each network administrator may decide to use =20
it or not, may decide to use 2,3,4,...128,.. levels...).
The statement above only says that the the same value of admission =20
priority should be used in the three protocols to refer to same level =20=

of admission priority.

Cheers

Francois


> Also, please provide clearer proposed text to include in the drafts.
>
> It would be good to see some discussion of the proposal on the =20
> list, to confirm and validate agreement of the WG.
>
> Jerry
>
>
> Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:
> Hello,
>
> For memory, the next rev of nsis-qspec is also expected to be aligned
> with the Resolution of the issue related to QoS Parameters encoding
> in , & . For
> convenience, I included below the recap on the corresponding
> resolution as announced on NSIS, DIME and TSVWG lists.
>
> Just to make sure this does not fall through the cracks.
>
> Cheers
>
> Francois
>
>
> >
> > Begin forwarded message:
> >> From: Francois Le Faucheur IMAP
> >> Date: 3 December 2007 12:05:42 GMT+01:00
> >> To: dime@ietf.org, nsis@ietf.org, tsvwg tsvwg
> >> Cc: Francois Le Faucheur IMAP , David Oran R
> >> , Hannes Tschofenig ,
> >> ken carlberg , Magnus Westerlund
> >> , James Polk ,
> >> cornelia.kappler@nsn.com, "(IJ/ETH) B=E1der Attila"
> >> , jouni.korhonen@teliasonera.com, Jukka
> >> Manner MJ , tsvwg chair
> >> chairs@tools.ietf.org>, nsis-chairs@tools.ietf.org, dime-
> >> chairs@tools.ietf.org, "john.loughney@nokia.com>"
> >>
> >> Subject: Resolution of issue QoS Parameters encoding in
> >> parameters>, &
> >>
> >> Hello,
> >>
> >> The Issue:
> >> =3D=3D=3D=3D=3D=3D=3D
> >> Three different documents (dime-qos-parameters, nsis-qos-nslp,
> >> tsvwg-emergency-rsvp) need to convey an overlapping set of QoS
> >> parameters (specifically RPH-Priority and Admission Priority) and
> >> currently do that in an inconsistent manner. This has been brought
> >> up and partially discussed on the WG mailing lists.
> >>
> >> The Proposed Resolution
> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >> Co-authors of the three I-Ds as well as WG chairs of the
> >> corresponding WGs converged on the following proposed resolution.
> >> Please let us know if you have an issue/concern with this.
> >>
> >> o Regarding RPH-Priority:
> >> * tsvwg-emergency-rsvp will go ahead with its requests to IANA to
> >> provide numerical registry for RPH priority (via extending
> >> existing RPH registry). See IANA Considerations section of tsvwg-
> >> emergency-rsvp.
> >> * nsis-qspec (in section 6.2.10) will point to this registry
> >> instead of defining its own values
> >> * dime-qos-parameters (in section 4.11) will point to this
> >> registry instead of defining its own values
> >> * tsvwg-emergency-rsvp (in section 3.2) will keep pointing to
> >> this registry.
> >>
> >> o Regarding Admission Priority:
> >> * every protocol spec will only indicate that "higher value means
> >> higher priority".
> >> * there is no attempt to define what specific values should be
> >> used for what. this is left outside the scope of the protocol =20
> specs.
> >> * each protocol spec will add a statement clarifying that a given
> >> Admission Priority is to be encoded with the same value in each of
> >> the three protocol spec. For example, in tsvwg-emergency-rsvp,
> >> under section 3.1. we will add:
> >> " A given Admission Priority is encoded in this information
> >> element
> >> using the same value as when encoded in the Admission Priority
> >> parameter defined in section 6.2.9 of [nsis-qspec], or in the
> >> Admission
> >> Priority parameter defined in section 4.10 of [dime-qos-
> >> parameters].
> >> In other words, a given value in any of the [emergency-rsvp]
> >> Admission
> >> Priority information element, the [nsis-qspec] Admission Priority
> >> parameter
> >> or the [dime-qos-parameters] Admission Priority parameter, =20
> refers to
> >> the same Admission Priority.
> >> "
> >> * the mirror statement will be added in nsis-qspec (section
> >> 6.2.9) and dime-qos-parameters (section 4.10)
> >>
> >> Francois
> >>
>
>
>
>
>
>
> Looking for last minute shopping deals? Find them fast with Yahoo! =20
> Search.


--Apple-Mail-5--267167476
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
Hello Jerry,<div><br><div><div>On 20 Feb 2008, at 16:58, Gerald Ash =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div><font face=3D"Courier New">Francois,</font></div>  =
<div><font face=3D"Courier New"></font>=A0</div>  <div><font =
face=3D"Courier New">In your "Proposed Resolution" posting to NSIS on 3 =
December <a =
href=3D"http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html">h=
ttp://www.ietf.org/mail-archive/web/nsis/current/msg08155.html</a>=A0you =
say:</font></div>  <div><font face=3D"Courier New"></font>=A0</div>  =
<div><font face=3D"Courier New">&gt; The Proposed Resolution<br>&gt; =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>&gt; =
Co-authors of the three I-Ds as well as WG chairs of the </font></div>  =
<div><font face=3D"Courier New">&gt; corresponding WGs converged on the =
following proposed </font></div>  <div><font face=3D"Courier New">&gt; =
resolution. </font></div>  <div><font face=3D"Courier =
New"></font>=A0</div>  <div><font face=3D"Courier New">I saw no =
discussion of this proposed resolution on the NSIS =
list.=A0</font></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>which is why we've been =
assuming there was no issue with it. =A0</div><div><br =
class=3D"webkit-block-placeholder"></div><br><blockquote =
type=3D"cite"><div><font face=3D"Courier New"> Who were the QSPEC =
co-authors who worked with you on the proposed =
resolution?</font></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Attila, Cornelia and Dave =
Oran (+ NSIS WG chairs).</div><div><br></div><br><blockquote =
type=3D"cite">  <div>=A0</div>  <div><font face=3D"Courier New">&gt; o =
Regarding RPH-Priority:<br>&gt; * tsvwg-emergency-rsvp will go ahead =
with its requests to</font></div>  <div><font face=3D"Courier =
New">&gt;=A0IANA </font><font face=3D"Courier New">to provide numerical =
registry for RPH priority (via </font></div>  <div><font face=3D"Courier =
New">&gt; extending existing RPH registry). See IANA =
Considerations</font></div>  <div><font face=3D"Courier =
New">&gt;=A0section of tsvwg-emergency-rsvp.</font></div>  <div><font =
face=3D"Courier New">&gt; * nsis-qspec (in section 6.2.10) will point to =
this registry</font></div>  <div><font face=3D"Courier New">&gt;=A0instead=
 of defining its own values</font></div>  <div><font face=3D"Courier =
New"></font>=A0</div>  <div><font face=3D"Courier New">OK.</font></div>  =
<div><font face=3D"Courier New"></font>=A0</div>  <div><font =
face=3D"Courier New">&gt; o Regarding Admission Priority:<br>&gt; * =
every protocol spec will only indicate that "higher value</font></div>  =
<div><font face=3D"Courier New">&gt;=A0means higher =
priority".</font></div>  <div><font face=3D"Courier New">&gt; * there is =
no attempt to define what specific values should</font></div>  =
<div><font face=3D"Courier New">&gt;=A0be used for what. this is left =
outside the scope of the</font></div>  <div><font face=3D"Courier =
New">&gt;=A0protocol specs.<br>* each protocol spec will add a statement =
clarifying that a</font></div>  <div><font face=3D"Courier =
New">&gt;=A0given Admission Priority is to be encoded with the =
same</font></div>  <div><font face=3D"Courier New">&gt;=A0value in each =
of the three protocol spec. For example, in</font></div>  <div><font =
face=3D"Courier New">&gt;=A0tsvwg-emergency-rsvp, under section 3.1. we =
will add:<br>" A given Admission Priority is encoded in this =
information</font></div>  <div><font face=3D"Courier New">&gt;=A0element =
using the same value as when encoded in the</font></div>  <div><font =
face=3D"Courier New">&gt;=A0Admission Priority parameter defined in =
section 6.2.9 of</font></div>  <div><font face=3D"Courier =
New">&gt;=A0[nsis-qspec], or in the Admission Priority =
parameter</font></div>  <div><font face=3D"Courier New">&gt;=A0defined =
in section 4.10 of [dime-qos-parameters].</font></div>  <div><font =
face=3D"Courier New">&gt; In other words, a given value in any of =
the</font></div>  <div><font face=3D"Courier New">&gt;=A0[emergency-rsvp] =
Admission Priority information element,</font></div>  <div><font =
face=3D"Courier New">&gt;=A0the [nsis-qspec] Admission Priority =
parameter or the</font></div>  <div><font face=3D"Courier =
New">&gt;=A0[dime-qos-parameters] Admission Priority =
parameter,</font></div>  <div><font face=3D"Courier New">&gt;=A0refers =
to the same Admission Priority.<br></font></div>  <div><font =
face=3D"Courier New">The above proposed paragraph is really unclear.=A0 =
Which draft=A0is setting up IANA Registries to assign Admission Priority =
parameters?=A0 The way it reads it sounds like all three drafts are =
setting up registries but that somehow=A0(magically) all=A0refer "to the =
same Admission Priority".=A0 How can that be if they assign different =
values?=A0 Right now emergency-rsvp and nsis-qspec set up registries for =
Admission Priority and dime-qos-parameters is using the nsis-qspec =
registry as I recall.</font></div>  <div><font face=3D"Courier =
New"></font>=A0</div>  <div><font face=3D"Courier New">Please clarify =
the proposal as to which draft is setting up a registry for Admission =
Priority.=A0</font></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>No registry is =
setup.</div><div>It is up to a network administrator to decide how =
many/which admission priority gets used for what. This is similar to how =
Preemption is used (ie each network administrator may decide to use it =
or not, may decide to use 2,3,4,...128,.. levels...).</div><div>The =
statement above only says that the the same value of admission priority =
should be used in the three protocols to refer to same level of =
admission priority.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Cheers</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Francois</div><div><br =
class=3D"webkit-block-placeholder"></div><br><blockquote =
type=3D"cite"><div><font face=3D"Courier New"> Also, please provide =
clearer=A0proposed text to include in the drafts.=A0 </font></div>  =
<div><font face=3D"Courier New"></font>=A0</div>  <div><font =
face=3D"Courier New">It would be good to see some discussion of the =
proposal on the list, to confirm and validate agreement of the =
WG.</font></div>  <div><font face=3D"Courier New"></font>=A0</div>  =
<div><font face=3D"Courier New">Jerry</font></div><font face=3D"Courier =
New"></font>  <div><br><br><b><i>Francois Le Faucheur IMAP &lt;<a =
href=3D"mailto:flefauch@cisco.com">flefauch@cisco.com</a>&gt;</i></b> =
wrote:</div>  <blockquote class=3D"replbq" style=3D"PADDING-LEFT: 5px; =
MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hello,<br><br>For =
memory, the next rev of nsis-qspec is also expected to be aligned =
<br>with the Resolution of the issue related to QoS Parameters encoding =
<br>in <dime-qos-parameters>, <nsis-qspec>&amp; <tsvwg-emeregncy-rsvp>. =
For <br>convenience, I included below the recap on the corresponding =
<br>resolution as announced on NSIS, DIME and TSVWG lists.<br><br>Just =
to make sure this does not fall through the =
cracks.<br><br>Cheers<br><br>Francois<br><br><br>&gt;<br>&gt; Begin =
forwarded message:<br>&gt;&gt; From: Francois Le Faucheur IMAP =
<flefauch@cisco.com><br>&gt;&gt; Date: 3 December 2007 12:05:42 =
GMT+01:00<br>&gt;&gt; To: <a =
href=3D"mailto:dime@ietf.org">dime@ietf.org</a>, <a =
href=3D"mailto:nsis@ietf.org">nsis@ietf.org</a>, tsvwg tsvwg =
<tsvwg@ietf.org><br>&gt;&gt; Cc: Francois Le Faucheur IMAP =
<flefauch@cisco.com>, David Oran R <br>&gt;&gt; <oran@cisco.com>, Hannes =
Tschofenig <hannes.tschofenig@gmx.net>, <br>&gt;&gt; ken carlberg =
<carlberg@g11.org.uk>, Magnus Westerlund <br>&gt;&gt; =
<magnus.westerlund@ericsson.com>, James Polk <jmpolk@cisco.com>, =
<br>&gt;&gt; <a =
href=3D"mailto:cornelia.kappler@nsn.com">cornelia.kappler@nsn.com</a>, =
"(IJ/ETH) B=E1der Attila" <br>&gt;&gt; <attila.bader@ericsson.com>, <a =
href=3D"mailto:jouni.korhonen@teliasonera.com">jouni.korhonen@teliasonera.=
com</a>, Jukka <br>&gt;&gt; Manner MJ <jmanner@cs.helsinki.fi>, tsvwg =
chair <tsvwg-><br>&gt;&gt; <a =
href=3D"mailto:chairs@tools.ietf.org">chairs@tools.ietf.org</a>&gt;, <a =
href=3D"mailto:nsis-chairs@tools.ietf.org">nsis-chairs@tools.ietf.org</a>,=
 dime- <br>&gt;&gt; <a =
href=3D"mailto:chairs@tools.ietf.org">chairs@tools.ietf.org</a>, "<a =
href=3D"mailto:john.loughney@nokia.com">john.loughney@nokia.com</a>&gt;" =
<br>&gt;&gt; <john.loughney@nokia.com><br>&gt;&gt; Subject: Resolution =
of issue QoS Parameters encoding in <dime-qos-><br>&gt;&gt; =
parameters&gt;, <nsis-qspec>&amp; =
<tsvwg-emeregncy-rsvp><br>&gt;&gt;<br>&gt;&gt; =
Hello,<br>&gt;&gt;<br>&gt;&gt; The Issue:<br>&gt;&gt; =
=3D=3D=3D=3D=3D=3D=3D<br>&gt;&gt; Three different documents =
(dime-qos-parameters, nsis-qos-nslp, <br>&gt;&gt; tsvwg-emergency-rsvp) =
need to convey an overlapping set of QoS <br>&gt;&gt; parameters =
(specifically RPH-Priority and Admission Priority) and <br>&gt;&gt; =
currently do that in an inconsistent manner. This has been brought =
<br>&gt;&gt; up and partially discussed on the WG mailing =
lists.<br>&gt;&gt;<br>&gt;&gt; The Proposed Resolution<br>&gt;&gt; =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>&gt;&gt; =
Co-authors of the three I-Ds as well as WG chairs of the <br>&gt;&gt; =
corresponding WGs converged on the following proposed resolution. =
<br>&gt;&gt; Please let us know if you have an issue/concern with =
this.<br>&gt;&gt;<br>&gt;&gt; o Regarding RPH-Priority:<br>&gt;&gt; * =
tsvwg-emergency-rsvp will go ahead with its requests to IANA to =
<br>&gt;&gt; provide numerical registry for RPH priority (via extending =
<br>&gt;&gt; existing RPH registry). See IANA Considerations section of =
tsvwg- <br>&gt;&gt; emergency-rsvp.<br>&gt;&gt; * nsis-qspec (in section =
6.2.10) will point to this registry <br>&gt;&gt; instead of defining its =
own values<br>&gt;&gt; * dime-qos-parameters (in section 4.11) will =
point to this <br>&gt;&gt; registry instead of defining its own =
values<br>&gt;&gt; * tsvwg-emergency-rsvp (in section 3.2) will keep =
pointing to <br>&gt;&gt; this registry.<br>&gt;&gt;<br>&gt;&gt; o =
Regarding Admission Priority:<br>&gt;&gt; * every protocol spec will =
only indicate that "higher value means <br>&gt;&gt; higher =
priority".<br>&gt;&gt; * there is no attempt to define what specific =
values should be <br>&gt;&gt; used for what. this is left outside the =
scope of the protocol specs.<br>&gt;&gt; * each protocol spec will add a =
statement clarifying that a given <br>&gt;&gt; Admission Priority is to =
be encoded with the same value in each of <br>&gt;&gt; the three =
protocol spec. For example, in tsvwg-emergency-rsvp, <br>&gt;&gt; under =
section 3.1. we will add:<br>&gt;&gt; " A given Admission Priority is =
encoded in this information <br>&gt;&gt; element<br>&gt;&gt; using the =
same value as when encoded in the Admission Priority<br>&gt;&gt; =
parameter defined in section 6.2.9 of [nsis-qspec], or in the =
<br>&gt;&gt; Admission<br>&gt;&gt; Priority parameter defined in section =
4.10 of [dime-qos- <br>&gt;&gt; parameters].<br>&gt;&gt; In other words, =
a given value in any of the [emergency-rsvp] <br>&gt;&gt; =
Admission<br>&gt;&gt; Priority information element, the [nsis-qspec] =
Admission Priority <br>&gt;&gt; parameter<br>&gt;&gt; or the =
[dime-qos-parameters] Admission Priority parameter, refers =
to<br>&gt;&gt; the same Admission Priority.<br>&gt;&gt; "<br>&gt;&gt; * =
the mirror statement will be added in nsis-qspec (section <br>&gt;&gt; =
6.2.9) and dime-qos-parameters (section 4.10)<br>&gt;&gt;<br>&gt;&gt; =
Francois<br>&gt;&gt;<br><br><br><br><br></tsvwg-emeregncy-rsvp></nsis-qspe=
c></dime-qos-></john.loughney@nokia.com></tsvwg-></jmanner@cs.helsinki.fi>=
</attila.bader@ericsson.com></jmpolk@cisco.com></magnus.westerlund@ericsso=
n.com></carlberg@g11.org.uk></hannes.tschofenig@gmx.net></oran@cisco.com><=
/flefauch@cisco.com></tsvwg@ietf.org></flefauch@cisco.com></tsvwg-emeregnc=
y-rsvp></nsis-qspec></dime-qos-parameters></blockquote><br><div>       =
<br class=3D"khtml-block-placeholder"></div><hr size=3D"1">Looking for =
last minute shopping deals? <a =
href=3D"http://us.rd.yahoo.com/evt=3D51734/*http://tools.search.yahoo.com/=
newsearch/category.php?category=3Dshopping"> Find them fast with Yahoo! =
Search.</a></blockquote></div><br></div></body></html>=

--Apple-Mail-5--267167476--

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

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

--===============0027416326==--


From nsis-bounces@ietf.org  Wed Feb 20 11:00:04 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C73728C935;
	Wed, 20 Feb 2008 11:00:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5
	tests=[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 iVxlShGccLYt; Wed, 20 Feb 2008 11:00:03 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1965328C748;
	Wed, 20 Feb 2008 11:00:03 -0800 (PST)
X-Original-To: nsis@ietf.org
Delivered-To: nsis@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id DA50528C261; Wed, 20 Feb 2008 11:00:01 -0800 (PST)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080220190001.DA50528C261@core3.amsl.com>
Date: Wed, 20 Feb 2008 11:00:01 -0800 (PST)
Cc: nsis@ietf.org
Subject: [NSIS] I-D Action:draft-ietf-nsis-ntlp-sctp-04.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: <http://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: <http://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           : General Internet Signaling Transport (GIST) over SCTP
	Author(s)       : X. Fu, et al.
	Filename        : draft-ietf-nsis-ntlp-sctp-04.txt
	Pages           : 11
	Date            : 2008-02-20

The General Internet Signaling Transport (GIST) protocol currently
uses TCP or TLS over TCP for connection mode operation.  This
document describes the usage of GIST over the Stream Control
Transmission Protocol (SCTP).  The use of SCTP can take advantage of
features provided by SCTP, namely streaming-based transport, support
of multiple streams to avoid head of line blocking, and the support
of multi-homing to provide network level fault tolerance.
Additionally, the support for the Partial Reliability Extension of
SCTP is discussed.

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

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-nsis-ntlp-sctp-04.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-nsis-ntlp-sctp-04.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-nsis-ntlp-sctp-04.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-nsis-ntlp-sctp-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-02-20105110.I-D\@ietf.org>


--OtherAccess--

--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
http://www.ietf.org/mailman/listinfo/nsis

--NextPart--


From nsis-bounces@ietf.org  Thu Feb 21 01:56:44 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A66A328CA84;
	Thu, 21 Feb 2008 01:56:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.476
X-Spam-Level: 
X-Spam-Status: No, score=-0.476 tagged_above=-999 required=5
	tests=[AWL=-0.266, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, 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 mBg6gjwn3GgT; Thu, 21 Feb 2008 01:56:43 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7EA8E28CA31;
	Thu, 21 Feb 2008 01:56:43 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC1B628CA31
	for <nsis@core3.amsl.com>; Thu, 21 Feb 2008 01:56:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 tGW6zB5wbUw3 for <nsis@core3.amsl.com>;
	Thu, 21 Feb 2008 01:56:40 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id 487A428C806
	for <nsis@ietf.org>; Thu, 21 Feb 2008 01:56:40 -0800 (PST)
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 8E1432C002B4A;
	Thu, 21 Feb 2008 10:56:36 +0100 (CET)
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 aeD4mJDdkQTy; Thu, 21 Feb 2008 10:56:36 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id 6ACB62C000355;
	Thu, 21 Feb 2008 10:56:16 +0100 (CET)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 21 Feb 2008 10:56:15 +0100
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF4D1268@mx1.office>
In-Reply-To: <824621.42714.qm@web63605.mail.re1.yahoo.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Review of draft-ietf-nsis-qspec-18.txt
Thread-Index: Achz2W/ellsM00jOSme4rd4/Sa8qKQAlm0qg
References: <58B97422-395F-4278-8414-6F7507D91E3C@cisco.com>
	<824621.42714.qm@web63605.mail.re1.yahoo.com>
From: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>
To: "Gerald Ash" <gash5107@yahoo.com>,
	"Francois Le Faucheur IMAP" <flefauch@cisco.com>, "nsis" <nsis@ietf.org>
Cc: cornelia.kappler@googlemail.com
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://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,

This has been agreed some time back and needs to be fixed. =


Please go ahead with the change.

Thanks,

  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  =


> -----Original Message-----
> From: Gerald Ash [mailto:gash5107@yahoo.com] =

> Sent: Wednesday, February 20, 2008 4:58 PM
> To: Francois Le Faucheur IMAP; Martin Stiemerling; nsis
> Cc: Gerald Ash; cornelia.kappler@googlemail.com
> Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.txt
> =

> Francois,
>  =

> In your "Proposed Resolution" posting to NSIS on 3 December =

> http://www.ietf.org/mail-archive/web/nsis/current/msg08155.htm
> l you say:
>  =

> > The Proposed Resolution
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > Co-authors of the three I-Ds as well as WG chairs of the =

> corresponding =

> > WGs converged on the following proposed resolution.
>  =

> I saw no discussion of this proposed resolution on the NSIS =

> list.  Who were the QSPEC co-authors who worked with you on =

> the proposed resolution?
>  =

> > o Regarding RPH-Priority:
> > * tsvwg-emergency-rsvp will go ahead with its requests to IANA to =

> > provide numerical registry for RPH priority (via extending existing =

> > RPH registry). See IANA Considerations section of =

> > tsvwg-emergency-rsvp.
> > * nsis-qspec (in section 6.2.10) will point to this =

> registry instead =

> > of defining its own values
>  =

> OK.
>  =

> > o Regarding Admission Priority:
> > * every protocol spec will only indicate that "higher value means =

> > higher priority".
> > * there is no attempt to define what specific values should be used =

> > for what. this is left outside the scope of the protocol specs.
> * each protocol spec will add a statement clarifying that a
> > given Admission Priority is to be encoded with the same =

> value in each =

> > of the three protocol spec. For example, in tsvwg-emergency-rsvp, =

> > under section 3.1. we will add:
> " A given Admission Priority is encoded in this information
> > element using the same value as when encoded in the =

> Admission Priority =

> > parameter defined in section 6.2.9 of [nsis-qspec], or in the =

> > Admission Priority parameter defined in section 4.10 of =

> > [dime-qos-parameters].
> > In other words, a given value in any of the =

> [emergency-rsvp] Admission =

> > Priority information element, the [nsis-qspec] Admission Priority =

> > parameter or the [dime-qos-parameters] Admission Priority =

> parameter, =

> > refers to the same Admission Priority.
> =

> The above proposed paragraph is really unclear.  Which draft =

> is setting up IANA Registries to assign Admission Priority =

> parameters?  The way it reads it sounds like all three drafts =

> are setting up registries but that somehow (magically) all =

> refer "to the same Admission Priority".  How can that be if =

> they assign different values?  Right now emergency-rsvp and =

> nsis-qspec set up registries for Admission Priority and =

> dime-qos-parameters is using the nsis-qspec registry as I recall.
>  =

> Please clarify the proposal as to which draft is setting up a =

> registry for Admission Priority.  Also, please provide =

> clearer proposed text to include in the drafts.  =

>  =

> It would be good to see some discussion of the proposal on =

> the list, to confirm and validate agreement of the WG.
>  =

> Jerry
> =

> =

> Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:
> =

> 	Hello,
> 	=

> 	For memory, the next rev of nsis-qspec is also expected =

> to be aligned =

> 	with the Resolution of the issue related to QoS =

> Parameters encoding =

> 	in , & . For =

> 	convenience, I included below the recap on the corresponding =

> 	resolution as announced on NSIS, DIME and TSVWG lists.
> 	=

> 	Just to make sure this does not fall through the cracks.
> 	=

> 	Cheers
> 	=

> 	Francois
> 	=

> 	=

> 	>
> 	> Begin forwarded message:
> 	>> From: Francois Le Faucheur IMAP =

> 	>> Date: 3 December 2007 12:05:42 GMT+01:00
> 	>> To: dime@ietf.org, nsis@ietf.org, tsvwg tsvwg =

> 	>> Cc: Francois Le Faucheur IMAP , David Oran R =

> 	>> , Hannes Tschofenig , =

> 	>> ken carlberg , Magnus Westerlund =

> 	>> , James Polk , =

> 	>> cornelia.kappler@nsn.com, "(IJ/ETH) B=E1der Attila" =

> 	>> , jouni.korhonen@teliasonera.com, Jukka =

> 	>> Manner MJ , tsvwg chair =

> 	>> chairs@tools.ietf.org>, nsis-chairs@tools.ietf.org, dime- =

> 	>> chairs@tools.ietf.org, "john.loughney@nokia.com>" =

> 	>> =

> 	>> Subject: Resolution of issue QoS Parameters encoding in =

> 	>> parameters>, & =

> 	>>
> 	>> Hello,
> 	>>
> 	>> The Issue:
> 	>> =3D=3D=3D=3D=3D=3D=3D
> 	>> Three different documents (dime-qos-parameters, =

> nsis-qos-nslp, =

> 	>> tsvwg-emergency-rsvp) need to convey an overlapping =

> set of QoS =

> 	>> parameters (specifically RPH-Priority and Admission =

> Priority) and =

> 	>> currently do that in an inconsistent manner. This =

> has been brought =

> 	>> up and partially discussed on the WG mailing lists.
> 	>>
> 	>> The Proposed Resolution
> 	>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> 	>> Co-authors of the three I-Ds as well as WG chairs of the =

> 	>> corresponding WGs converged on the following =

> proposed resolution. =

> 	>> Please let us know if you have an issue/concern with this.
> 	>>
> 	>> o Regarding RPH-Priority:
> 	>> * tsvwg-emergency-rsvp will go ahead with its =

> requests to IANA to =

> 	>> provide numerical registry for RPH priority (via extending =

> 	>> existing RPH registry). See IANA Considerations =

> section of tsvwg- =

> 	>> emergency-rsvp.
> 	>> * nsis-qspec (in section 6.2.10) will point to this registry =

> 	>> instead of defining its own values
> 	>> * dime-qos-parameters (in section 4.11) will point to this =

> 	>> registry instead of defining its own values
> 	>> * tsvwg-emergency-rsvp (in section 3.2) will keep =

> pointing to =

> 	>> this registry.
> 	>>
> 	>> o Regarding Admission Priority:
> 	>> * every protocol spec will only indicate that =

> "higher value means =

> 	>> higher priority".
> 	>> * there is no attempt to define what specific values =

> should be =

> 	>> used for what. this is left outside the scope of the =

> protocol specs.
> 	>> * each protocol spec will add a statement clarifying =

> that a given =

> 	>> Admission Priority is to be encoded with the same =

> value in each of =

> 	>> the three protocol spec. For example, in =

> tsvwg-emergency-rsvp, =

> 	>> under section 3.1. we will add:
> 	>> " A given Admission Priority is encoded in this information =

> 	>> element
> 	>> using the same value as when encoded in the =

> Admission Priority
> 	>> parameter defined in section 6.2.9 of [nsis-qspec], =

> or in the =

> 	>> Admission
> 	>> Priority parameter defined in section 4.10 of [dime-qos- =

> 	>> parameters].
> 	>> In other words, a given value in any of the [emergency-rsvp] =

> 	>> Admission
> 	>> Priority information element, the [nsis-qspec] =

> Admission Priority =

> 	>> parameter
> 	>> or the [dime-qos-parameters] Admission Priority =

> parameter, refers to
> 	>> the same Admission Priority.
> 	>> "
> 	>> * the mirror statement will be added in nsis-qspec (section =

> 	>> 6.2.9) and dime-qos-parameters (section 4.10)
> 	>>
> 	>> Francois
> 	>>
> 	=

> 	=

> 	=

> 	=

> 	=

> =

> =

> ________________________________
> =

> Looking for last minute shopping deals? Find them fast with =

> Yahoo! Search. =

> <http://us.rd.yahoo.com/evt=3D51734/*http://tools.search.yahoo.c
> om/newsearch/category.php?category=3Dshopping> =

> =

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


From nsis-bounces@ietf.org  Thu Feb 21 09:00:44 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CB92428CBCA;
	Thu, 21 Feb 2008 09:00:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.567
X-Spam-Level: *
X-Spam-Status: No, score=1.567 tagged_above=-999 required=5 tests=[AWL=-0.108,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=1, MIME_HTML_MOSTLY=0.001,
	RDNS_NONE=0.1, 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 xd-gvbkBEtAc; Thu, 21 Feb 2008 09:00:42 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7792A28CB47;
	Thu, 21 Feb 2008 08:59:22 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2EA9728CB0C
	for <nsis@core3.amsl.com>; Thu, 21 Feb 2008 08:59:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 XFnrgcGlQgNq for <nsis@core3.amsl.com>;
	Thu, 21 Feb 2008 08:59:16 -0800 (PST)
Received: from web63613.mail.re1.yahoo.com (web63613.mail.re1.yahoo.com
	[69.147.97.83]) by core3.amsl.com (Postfix) with SMTP id 60D2E28CB6E
	for <nsis@ietf.org>; Thu, 21 Feb 2008 08:55:48 -0800 (PST)
Received: (qmail 84036 invoked by uid 60001); 21 Feb 2008 16:55:44 -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=teSrL2LUqMczCsbx0x81GrQSS0iWGNTz35ZcyPyWrufaHrgrPJb2GW+2i03vGvdk7rUNxOPlGQf7a1UzfU5iS6LT8felTJY+HHgyHWJOdErcU4K90aVOsLPxISXEWLr2zxypx4xULcBoad8ojf0h7yzGeyGEuMpZpsONc91KwQQ=;
X-YMail-OSG: XBnFkHsVM1m.3nrV_KGy89t7szQAPmNCNzQ82VJc
Received: from [76.19.255.157] by web63613.mail.re1.yahoo.com via HTTP;
	Thu, 21 Feb 2008 08:55:44 PST
Date: Thu, 21 Feb 2008 08:55:44 -0800 (PST)
From: Gerald Ash <gash5107@yahoo.com>
To: Francois Le Faucheur IMAP <flefauch@cisco.com>,
	Martin Stiemerling <Stiemerling@nw.neclab.eu>, john.loughney@nokia.com, 
	nsis <nsis@ietf.org>
In-Reply-To: <4EFF5784-4564-4730-A5C1-CD0477DE740A@cisco.com>
MIME-Version: 1.0
Message-ID: <505424.79660.qm@web63613.mail.re1.yahoo.com>
Cc: cornelia.kappler@googlemail.com
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1614443324=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

--===============1614443324==
Content-Type: multipart/alternative; boundary="0-1636405445-1203612944=:79660"
Content-Transfer-Encoding: 8bit

--0-1636405445-1203612944=:79660
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Francois, Martin, John, All,
   
    >>> o Regarding Admission Priority:
>>> * every protocol spec will only indicate that "higher value
  >>> means higher priority".
  >>> * there is no attempt to define what specific values should
  >>> be used for what. this is left outside the scope of the
  >>> protocol specs.
>>> * each protocol spec will add a statement clarifying that a
  >>> given Admission Priority is to be encoded with the same
  >>> value in each of the three protocol spec. For example, in
  >>> tsvwg-emergency-rsvp, under section 3.1. we will add:
>>> " A given Admission Priority is encoded in this information
  >>> element using the same value as when encoded in the
  >>> Admission Priority parameter defined in section 6.2.9 of
  >>> [nsis-qspec], or in the Admission Priority parameter
  >>> defined in section 4.10 of [dime-qos-parameters].
  >>> In other words, a given value in any of the
  >>> [emergency-rsvp] Admission Priority information element,
  >>> the [nsis-qspec] Admission Priority parameter or the
  >>> [dime-qos-parameters] Admission Priority parameter,
  >>> refers to the same Admission Priority.
   
  >> The above proposed paragraph is really unclear.  Which draft
  >> is setting up IANA Registries to assign Admission Priority
  >> parameters?  The way it reads it sounds like all three drafts
  >> are setting up registries but that somehow (magically) all refer
  >> "to the same Admission Priority".  How can that be if they
  >> assign different values?  Right now emergency-rsvp and
  >> nsis-qspec set up registries for Admission Priority and
  >> dime-qos-parameters is using the nsis-qspec registry as I
  >> recall.
  >>
  >> Please clarify the proposal as to which draft is setting up a
  >> registry for Admission Priority. 
  

  > No registry is setup.
  > It is up to a network administrator to decide how many/which
  > admission priority gets used for what. This is similar to how
  > Preemption is used (ie each network administrator may decide 
  > to use it or not, may decide to use 2,3,4,...128,.. levels...).
  > The statement above only says that the the same value of 
  > admission priority should be used in the three protocols to refer 
  > to same level of admission priority.
   
  That's a fundamental change to NSIS/QSPEC and does away with standardized Admission Priority values.  QSPEC is following Y.1571 (now Y.2171 according to An Nguyen) in standardizing 3 priority levels to have end-to-end cross-domain significance.
   
  If we elimate this standardization, as is proposed, then different admission priority values can be assigned in different Admin domains, and will have no end-to-end significance.  For example, Admin-domain 1, Admin-domain 2, and Admin-domain 3 assign admission priority=2,  admission priority=4, admission priority=10 for the highest level priority, respectively.  Admin-domain 1 and Admin-domain 2 try to initiate end-to-end flows via Admin-domain 3 for a 'high priority' flow.  However, Admin-domain 3 has no idea how to treat the flow admission priority since all 3 domains are using different encodings of high priority.
     
  Admission priority is not the same as preemption priority and should not be based on that model.
   

  IMO we should retain the standardized admission priority levels based on Y.1571/Y.2171.  Otherwise, how do we achieve end-to-end, cross-domain standardization of admission priority?  In any case, we need to see some good justification for the change.
   
    >> I saw no discussion of this proposed resolution on the NSIS list. 
  

  > which is why we've been assuming there was no issue with it. 
   
  It isn't sufficient to declare 'silence is agreement' on making such a fundamental change.  People should weigh in *on the list* and give their technical justifications and confirm their agreement (or disagreement).
   
  >> Who were the QSPEC co-authors who worked with you on the
  >> proposed resolution?
  

  > Attila, Cornelia and Dave Oran (+ NSIS WG chairs).
   
  So far I've not been able to verify agreement from the QSPEC co-authors as yet.  We saw no discussion of the issue on the list, and there needs to be some explanation/justification for the change.  
   
  Perhaps Francois could summarize the technical discussion amonst the co-authors, and also state who explicitly agreed (as opposed to who had no comment or active participation in the discussion).  
   
  It would be good if the co-authors who participated in the discussion of the 'proposed agreement' could weigh in on the list with their technical view.
   
  Also, both NSIS chairs have said there is an agreement on the proposal, so perhaps they could weigh in on the list also with their technical view.
   
  Jerry



Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:
  Hello Jerry,  
    On 20 Feb 2008, at 16:58, Gerald Ash wrote:

    Francois,
   
  In your "Proposed Resolution" posting to NSIS on 3 December http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html you say:
   
  > The Proposed Resolution
> ===================
> Co-authors of the three I-Ds as well as WG chairs of the 
  > corresponding WGs converged on the following proposed 
  > resolution. 
   
  I saw no discussion of this proposed resolution on the NSIS list. 
  

  which is why we've been assuming there was no issue with it.  
  


    Who were the QSPEC co-authors who worked with you on the proposed resolution?
  

  Attila, Cornelia and Dave Oran (+ NSIS WG chairs).
  


     
  > o Regarding RPH-Priority:
> * tsvwg-emergency-rsvp will go ahead with its requests to
  > IANA to provide numerical registry for RPH priority (via 
  > extending existing RPH registry). See IANA Considerations
  > section of tsvwg-emergency-rsvp.
  > * nsis-qspec (in section 6.2.10) will point to this registry
  > instead of defining its own values
   
  OK.
   
  > o Regarding Admission Priority:
> * every protocol spec will only indicate that "higher value
  > means higher priority".
  > * there is no attempt to define what specific values should
  > be used for what. this is left outside the scope of the
  > protocol specs.
* each protocol spec will add a statement clarifying that a
  > given Admission Priority is to be encoded with the same
  > value in each of the three protocol spec. For example, in
  > tsvwg-emergency-rsvp, under section 3.1. we will add:
" A given Admission Priority is encoded in this information
  > element using the same value as when encoded in the
  > Admission Priority parameter defined in section 6.2.9 of
  > [nsis-qspec], or in the Admission Priority parameter
  > defined in section 4.10 of [dime-qos-parameters].
  > In other words, a given value in any of the
  > [emergency-rsvp] Admission Priority information element,
  > the [nsis-qspec] Admission Priority parameter or the
  > [dime-qos-parameters] Admission Priority parameter,
  > refers to the same Admission Priority.

  The above proposed paragraph is really unclear.  Which draft is setting up IANA Registries to assign Admission Priority parameters?  The way it reads it sounds like all three drafts are setting up registries but that somehow (magically) all refer "to the same Admission Priority".  How can that be if they assign different values?  Right now emergency-rsvp and nsis-qspec set up registries for Admission Priority and dime-qos-parameters is using the nsis-qspec registry as I recall.
   
  Please clarify the proposal as to which draft is setting up a registry for Admission Priority. 
  

  No registry is setup.
  It is up to a network administrator to decide how many/which admission priority gets used for what. This is similar to how Preemption is used (ie each network administrator may decide to use it or not, may decide to use 2,3,4,...128,.. levels...).
  The statement above only says that the the same value of admission priority should be used in the three protocols to refer to same level of admission priority.
  

  Cheers
  

  Francois
  


    Also, please provide clearer proposed text to include in the drafts.  
   
  It would be good to see some discussion of the proposal on the list, to confirm and validate agreement of the WG.
   
  Jerry
  

Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:
  Hello,

For memory, the next rev of nsis-qspec is also expected to be aligned 
with the Resolution of the issue related to QoS Parameters encoding 
in , & . For 
convenience, I included below the recap on the corresponding 
resolution as announced on NSIS, DIME and TSVWG lists.

Just to make sure this does not fall through the cracks.

Cheers

Francois


>
> Begin forwarded message:
>> From: Francois Le Faucheur IMAP 
>> Date: 3 December 2007 12:05:42 GMT+01:00
>> To: dime@ietf.org, nsis@ietf.org, tsvwg tsvwg 
>> Cc: Francois Le Faucheur IMAP , David Oran R 
>> , Hannes Tschofenig , 
>> ken carlberg , Magnus Westerlund 
>> , James Polk , 
>> cornelia.kappler@nsn.com, "(IJ/ETH) Báder Attila" 
>> , jouni.korhonen@teliasonera.com, Jukka 
>> Manner MJ , tsvwg chair 
>> chairs@tools.ietf.org>, nsis-chairs@tools.ietf.org, dime- 
>> chairs@tools.ietf.org, "john.loughney@nokia.com>" 
>> 
>> Subject: Resolution of issue QoS Parameters encoding in 
>> parameters>, & 
>>
>> Hello,
>>
>> The Issue:
>> =======
>> Three different documents (dime-qos-parameters, nsis-qos-nslp, 
>> tsvwg-emergency-rsvp) need to convey an overlapping set of QoS 
>> parameters (specifically RPH-Priority and Admission Priority) and 
>> currently do that in an inconsistent manner. This has been brought 
>> up and partially discussed on the WG mailing lists.
>>
>> The Proposed Resolution
>> ===================
>> Co-authors of the three I-Ds as well as WG chairs of the 
>> corresponding WGs converged on the following proposed resolution. 
>> Please let us know if you have an issue/concern with this.
>>
>> o Regarding RPH-Priority:
>> * tsvwg-emergency-rsvp will go ahead with its requests to IANA to 
>> provide numerical registry for RPH priority (via extending 
>> existing RPH registry). See IANA Considerations section of tsvwg- 
>> emergency-rsvp.
>> * nsis-qspec (in section 6.2.10) will point to this registry 
>> instead of defining its own values
>> * dime-qos-parameters (in section 4.11) will point to this 
>> registry instead of defining its own values
>> * tsvwg-emergency-rsvp (in section 3.2) will keep pointing to 
>> this registry.
>>
>> o Regarding Admission Priority:
>> * every protocol spec will only indicate that "higher value means 
>> higher priority".
>> * there is no attempt to define what specific values should be 
>> used for what. this is left outside the scope of the protocol specs.
>> * each protocol spec will add a statement clarifying that a given 
>> Admission Priority is to be encoded with the same value in each of 
>> the three protocol spec. For example, in tsvwg-emergency-rsvp, 
>> under section 3.1. we will add:
>> " A given Admission Priority is encoded in this information 
>> element
>> using the same value as when encoded in the Admission Priority
>> parameter defined in section 6.2.9 of [nsis-qspec], or in the 
>> Admission
>> Priority parameter defined in section 4.10 of [dime-qos- 
>> parameters].
>> In other words, a given value in any of the [emergency-rsvp] 
>> Admission
>> Priority information element, the [nsis-qspec] Admission Priority 
>> parameter
>> or the [dime-qos-parameters] Admission Priority parameter, refers to
>> the same Admission Priority.
>> "
>> * the mirror statement will be added in nsis-qspec (section 
>> 6.2.9) and dime-qos-parameters (section 4.10)
>>
>> Francois
>>





  

  
---------------------------------
  Looking for last minute shopping deals? Find them fast with Yahoo! Search.




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

<div><FONT face=arial>Francois, Martin, John, All,</FONT></div>  <div><FONT face=arial></FONT>&nbsp;</div>  <DIV><FONT face=arial>  <DIV><FONT face=arial>&gt;&gt;&gt; o Regarding Admission Priority:<BR>&gt;&gt;&gt; * every protocol spec will only indicate that "higher value</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;means higher priority".</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt; * there is no attempt to define what specific values should</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;be used for what. this is left outside the scope of the</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;protocol specs.<BR>&gt;&gt;&gt; * each protocol spec will add a statement clarifying that a</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;given Admission Priority is to be encoded with the same</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;value in each of the three protocol spec. For example, in</FONT></DIV>  <DIV><FONT
 face=arial>&gt;&gt;&gt;&nbsp;tsvwg-emergency-rsvp, under section 3.1. we will add:<BR>&gt;&gt;&gt; " A given Admission Priority is encoded in this information</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;element using the same value as when encoded in the</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;Admission Priority parameter defined in section 6.2.9 of</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;[nsis-qspec], or in the Admission Priority parameter</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;defined in section 4.10 of [dime-qos-parameters].</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt; In other words, a given value in any of the</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;[emergency-rsvp] Admission Priority information element,</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;the [nsis-qspec] Admission Priority parameter or the</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;[dime-qos-parameters] Admission
 Priority parameter,</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;refers to the same Admission Priority.</FONT></DIV>  <DIV><FONT face=arial>&nbsp;</DIV></FONT>  <DIV><FONT face=arial>&gt;&gt; The above proposed paragraph is really unclear.&nbsp; Which draft</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;is setting up IANA Registries to assign Admission Priority</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;parameters?&nbsp; The way it reads it sounds like all three drafts</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;are setting up registries but that somehow&nbsp;(magically) all&nbsp;refer</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;"to the same Admission Priority".&nbsp; How can that be if they</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;assign different values?&nbsp; Right now emergency-rsvp and</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;nsis-qspec set up registries for Admission Priority and</FONT></DIV>  <DIV><FONT
 face=arial>&gt;&gt;&nbsp;dime-qos-parameters is using the nsis-qspec registry as I</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;recall.</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt; Please clarify the proposal as to which draft is setting up a</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;registry for Admission Priority.&nbsp;</FONT></DIV>  <DIV><FONT face=arial><BR class=webkit-block-placeholder></FONT></DIV>  <DIV><FONT face=arial>&gt; No registry is setup.</FONT></DIV>  <DIV><FONT face=arial>&gt; It is up to a network administrator to decide how many/which</FONT></DIV>  <DIV><FONT face=arial>&gt;&nbsp;admission priority gets used for what. This is similar to how</FONT></DIV>  <DIV><FONT face=arial>&gt;&nbsp;Preemption is used (ie each network administrator may decide </FONT></DIV>  <DIV><FONT face=arial>&gt; to use it or not, may decide to use 2,3,4,...128,.. levels...).</FONT></DIV>  <DIV><FONT face=arial>&gt; The
 statement above only says that the the same value of </FONT></DIV>  <DIV><FONT face=arial>&gt; admission priority should be used in the three protocols to refer </FONT></DIV>  <DIV><FONT face=arial>&gt; to same level of admission priority.</FONT></DIV>  <DIV>&nbsp;</DIV>  <DIV>That's a fundamental change to NSIS/QSPEC and does away with standardized Admission Priority values.&nbsp; QSPEC is following Y.1571 (now Y.2171 according to An Nguyen) in standardizing 3 priority levels to have end-to-end cross-domain significance.</DIV>  <DIV>&nbsp;</DIV>  <DIV>If we elimate this standardization, as is proposed, then different admission priority values&nbsp;can be&nbsp;assigned in different Admin domains, and will&nbsp;have no end-to-end significance.&nbsp; For example, Admin-domain 1, Admin-domain 2, and Admin-domain 3 assign&nbsp;admission priority=2,&nbsp;&nbsp;admission priority=4, admission priority=10 for the highest level priority, respectively.&nbsp; Admin-domain 1 and
 Admin-domain 2 try to initiate end-to-end flows via Admin-domain&nbsp;3 for a 'high priority' flow.&nbsp;&nbsp;However, Admin-domain 3 has no idea how to treat the flow admission priority since all 3 domains are using different encodings of high priority.</DIV>  <DIV>  <DIV>&nbsp;</DIV>  <DIV>Admission priority is not the same as preemption priority and should not be based on that model.</DIV>  <DIV>&nbsp;</DIV></DIV>  <DIV>IMO we should retain the standardized admission priority levels based on Y.1571/Y.2171.&nbsp; Otherwise, how do we achieve end-to-end, cross-domain standardization of admission priority?&nbsp; In any case, we need to see some good justification for the change.</DIV>  <DIV>&nbsp;</DIV>  <DIV>  <DIV><FONT face=arial>&gt;&gt; I saw no discussion of this proposed resolution on the NSIS list.&nbsp;</FONT></DIV>  <DIV><FONT face=arial><BR class=webkit-block-placeholder></FONT></DIV>  <DIV><FONT face=arial>&gt; which is why we've been assuming there was no
 issue with it. </FONT></DIV>  <DIV>&nbsp;</DIV>  <DIV>It isn't sufficient to&nbsp;declare 'silence is agreement' on making such a fundamental change.&nbsp; People should weigh in *on the list* and give their&nbsp;technical justifications and confirm their agreement (or disagreement).</DIV>  <DIV><FONT face=arial></FONT>&nbsp;</DIV>  <DIV><FONT face=arial>&gt;&gt; Who were the QSPEC co-authors who worked with you on the</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;proposed resolution?</FONT></DIV>  <DIV><FONT face=arial><BR class=webkit-block-placeholder></FONT></DIV>  <DIV><FONT face=arial>&gt; Attila, Cornelia and Dave Oran (+ NSIS WG chairs).</FONT></DIV>  <DIV>&nbsp;</DIV>  <DIV>So far I've not been able to verify agreement from the QSPEC co-authors as yet.&nbsp; We saw no discussion of the issue on the list, and there needs to be some explanation/justification for the change.&nbsp; </DIV>  <DIV>&nbsp;</DIV>  <DIV>Perhaps Francois could summarize the
 technical&nbsp;discussion amonst the co-authors, and also state who explicitly agreed (as opposed to who had no comment or active participation in the discussion).&nbsp;&nbsp;</DIV>  <DIV>&nbsp;</DIV>  <DIV>It would be good if the co-authors who participated&nbsp;in the discussion of the 'proposed agreement' could weigh in on the list with their technical view.</DIV>  <DIV>&nbsp;</DIV>  <DIV>Also, both NSIS chairs have said there is an agreement on the proposal, so perhaps they could weigh in on the list also with their technical view.</DIV>  <DIV>&nbsp;</DIV>  <DIV>Jerry</DIV></DIV></FONT><BR><BR><B><I>Francois Le Faucheur IMAP &lt;flefauch@cisco.com&gt;</I></B> wrote:</DIV>  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hello Jerry,  <DIV><BR>  <DIV>  <DIV>On 20 Feb 2008, at 16:58, Gerald Ash wrote:</DIV><BR class=Apple-interchange-newline>  <BLOCKQUOTE type="cite">  <DIV><FONT face="Courier
 New">Francois,</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">In your "Proposed Resolution" posting to NSIS on 3 December <A href="http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html</A>&nbsp;you say:</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">&gt; The Proposed Resolution<BR>&gt; ===================<BR>&gt; Co-authors of the three I-Ds as well as WG chairs of the </FONT></DIV>  <DIV><FONT face="Courier New">&gt; corresponding WGs converged on the following proposed </FONT></DIV>  <DIV><FONT face="Courier New">&gt; resolution. </FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">I saw no discussion of this proposed resolution on the NSIS list.&nbsp;</FONT></DIV></BLOCKQUOTE>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>which is why we've been
 assuming there was no issue with it. &nbsp;</DIV>  <DIV><BR class=webkit-block-placeholder></DIV><BR>  <BLOCKQUOTE type="cite">  <DIV><FONT face="Courier New">Who were the QSPEC co-authors who worked with you on the proposed resolution?</FONT></DIV></BLOCKQUOTE>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>Attila, Cornelia and Dave Oran (+ NSIS WG chairs).</DIV>  <DIV><BR></DIV><BR>  <BLOCKQUOTE type="cite">  <DIV>&nbsp;</DIV>  <DIV><FONT face="Courier New">&gt; o Regarding RPH-Priority:<BR>&gt; * tsvwg-emergency-rsvp will go ahead with its requests to</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;IANA </FONT><FONT face="Courier New">to provide numerical registry for RPH priority (via </FONT></DIV>  <DIV><FONT face="Courier New">&gt; extending existing RPH registry). See IANA Considerations</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;section of tsvwg-emergency-rsvp.</FONT></DIV>  <DIV><FONT face="Courier New">&gt; * nsis-qspec (in section 6.2.10)
 will point to this registry</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;instead of defining its own values</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">OK.</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">&gt; o Regarding Admission Priority:<BR>&gt; * every protocol spec will only indicate that "higher value</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;means higher priority".</FONT></DIV>  <DIV><FONT face="Courier New">&gt; * there is no attempt to define what specific values should</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;be used for what. this is left outside the scope of the</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;protocol specs.<BR>* each protocol spec will add a statement clarifying that a</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;given Admission Priority is to be encoded with the same</FONT></DIV>  <DIV><FONT
 face="Courier New">&gt;&nbsp;value in each of the three protocol spec. For example, in</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;tsvwg-emergency-rsvp, under section 3.1. we will add:<BR>" A given Admission Priority is encoded in this information</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;element using the same value as when encoded in the</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;Admission Priority parameter defined in section 6.2.9 of</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;[nsis-qspec], or in the Admission Priority parameter</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;defined in section 4.10 of [dime-qos-parameters].</FONT></DIV>  <DIV><FONT face="Courier New">&gt; In other words, a given value in any of the</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;[emergency-rsvp] Admission Priority information element,</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;the [nsis-qspec] Admission Priority
 parameter or the</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;[dime-qos-parameters] Admission Priority parameter,</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;refers to the same Admission Priority.<BR></FONT></DIV>  <DIV><FONT face="Courier New">The above proposed paragraph is really unclear.&nbsp; Which draft&nbsp;is setting up IANA Registries to assign Admission Priority parameters?&nbsp; The way it reads it sounds like all three drafts are setting up registries but that somehow&nbsp;(magically) all&nbsp;refer "to the same Admission Priority".&nbsp; How can that be if they assign different values?&nbsp; Right now emergency-rsvp and nsis-qspec set up registries for Admission Priority and dime-qos-parameters is using the nsis-qspec registry as I recall.</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">Please clarify the proposal as to which draft is setting up a registry for Admission
 Priority.&nbsp;</FONT></DIV></BLOCKQUOTE>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>No registry is setup.</DIV>  <DIV>It is up to a network administrator to decide how many/which admission priority gets used for what. This is similar to how Preemption is used (ie each network administrator may decide to use it or not, may decide to use 2,3,4,...128,.. levels...).</DIV>  <DIV>The statement above only says that the the same value of admission priority should be used in the three protocols to refer to same level of admission priority.</DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>Cheers</DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>Francois</DIV>  <DIV><BR class=webkit-block-placeholder></DIV><BR>  <BLOCKQUOTE type="cite">  <DIV><FONT face="Courier New">Also, please provide clearer&nbsp;proposed text to include in the drafts.&nbsp; </FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">It would
 be good to see some discussion of the proposal on the list, to confirm and validate agreement of the WG.</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">Jerry</FONT></DIV><FONT face="Courier New"></FONT>  <DIV><BR><BR><B><I>Francois Le Faucheur IMAP &lt;<A href="mailto:flefauch@cisco.com">flefauch@cisco.com</A>&gt;</I></B> wrote:</DIV>  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hello,<BR><BR>For memory, the next rev of nsis-qspec is also expected to be aligned <BR>with the Resolution of the issue related to QoS Parameters encoding <BR>in <DIME-QOS-PARAMETERS>, <NSIS-QSPEC>&amp; <TSVWG-EMEREGNCY-RSVP>. For <BR>convenience, I included below the recap on the corresponding <BR>resolution as announced on NSIS, DIME and TSVWG lists.<BR><BR>Just to make sure this does not fall through the cracks.<BR><BR>Cheers<BR><BR>Francois<BR><BR><BR>&gt;<BR>&gt; Begin forwarded
 message:<BR>&gt;&gt; From: Francois Le Faucheur IMAP <FLEFAUCH@CISCO.COM><BR>&gt;&gt; Date: 3 December 2007 12:05:42 GMT+01:00<BR>&gt;&gt; To: <A href="mailto:dime@ietf.org">dime@ietf.org</A>, <A href="mailto:nsis@ietf.org">nsis@ietf.org</A>, tsvwg tsvwg <TSVWG@IETF.ORG><BR>&gt;&gt; Cc: Francois Le Faucheur IMAP <FLEFAUCH@CISCO.COM>, David Oran R <BR>&gt;&gt; <ORAN@CISCO.COM>, Hannes Tschofenig <HANNES.TSCHOFENIG@GMX.NET>, <BR>&gt;&gt; ken carlberg <CARLBERG@G11.ORG.UK>, Magnus Westerlund <BR>&gt;&gt; <MAGNUS.WESTERLUND@ERICSSON.COM>, James Polk <JMPOLK@CISCO.COM>, <BR>&gt;&gt; <A href="mailto:cornelia.kappler@nsn.com">cornelia.kappler@nsn.com</A>, "(IJ/ETH) Báder Attila" <BR>&gt;&gt; <ATTILA.BADER@ERICSSON.COM>, <A href="mailto:jouni.korhonen@teliasonera.com">jouni.korhonen@teliasonera.com</A>, Jukka <BR>&gt;&gt; Manner MJ <JMANNER@CS.HELSINKI.FI>, tsvwg chair <TSVWG-><BR>&gt;&gt; <A href="mailto:chairs@tools.ietf.org">chairs@tools.ietf.org</A>&gt;, <A
 href="mailto:nsis-chairs@tools.ietf.org">nsis-chairs@tools.ietf.org</A>, dime- <BR>&gt;&gt; <A href="mailto:chairs@tools.ietf.org">chairs@tools.ietf.org</A>, "<A href="mailto:john.loughney@nokia.com">john.loughney@nokia.com</A>&gt;" <BR>&gt;&gt; <JOHN.LOUGHNEY@NOKIA.COM><BR>&gt;&gt; Subject: Resolution of issue QoS Parameters encoding in <DIME-QOS-><BR>&gt;&gt; parameters&gt;, <NSIS-QSPEC>&amp; <TSVWG-EMEREGNCY-RSVP><BR>&gt;&gt;<BR>&gt;&gt; Hello,<BR>&gt;&gt;<BR>&gt;&gt; The Issue:<BR>&gt;&gt; =======<BR>&gt;&gt; Three different documents (dime-qos-parameters, nsis-qos-nslp, <BR>&gt;&gt; tsvwg-emergency-rsvp) need to convey an overlapping set of QoS <BR>&gt;&gt; parameters (specifically RPH-Priority and Admission Priority) and <BR>&gt;&gt; currently do that in an inconsistent manner. This has been brought <BR>&gt;&gt; up and partially discussed on the WG mailing lists.<BR>&gt;&gt;<BR>&gt;&gt; The Proposed Resolution<BR>&gt;&gt; ===================<BR>&gt;&gt; Co-authors of
 the three I-Ds as well as WG chairs of the <BR>&gt;&gt; corresponding WGs converged on the following proposed resolution. <BR>&gt;&gt; Please let us know if you have an issue/concern with this.<BR>&gt;&gt;<BR>&gt;&gt; o Regarding RPH-Priority:<BR>&gt;&gt; * tsvwg-emergency-rsvp will go ahead with its requests to IANA to <BR>&gt;&gt; provide numerical registry for RPH priority (via extending <BR>&gt;&gt; existing RPH registry). See IANA Considerations section of tsvwg- <BR>&gt;&gt; emergency-rsvp.<BR>&gt;&gt; * nsis-qspec (in section 6.2.10) will point to this registry <BR>&gt;&gt; instead of defining its own values<BR>&gt;&gt; * dime-qos-parameters (in section 4.11) will point to this <BR>&gt;&gt; registry instead of defining its own values<BR>&gt;&gt; * tsvwg-emergency-rsvp (in section 3.2) will keep pointing to <BR>&gt;&gt; this registry.<BR>&gt;&gt;<BR>&gt;&gt; o Regarding Admission Priority:<BR>&gt;&gt; * every protocol spec will only indicate that "higher value means
 <BR>&gt;&gt; higher priority".<BR>&gt;&gt; * there is no attempt to define what specific values should be <BR>&gt;&gt; used for what. this is left outside the scope of the protocol specs.<BR>&gt;&gt; * each protocol spec will add a statement clarifying that a given <BR>&gt;&gt; Admission Priority is to be encoded with the same value in each of <BR>&gt;&gt; the three protocol spec. For example, in tsvwg-emergency-rsvp, <BR>&gt;&gt; under section 3.1. we will add:<BR>&gt;&gt; " A given Admission Priority is encoded in this information <BR>&gt;&gt; element<BR>&gt;&gt; using the same value as when encoded in the Admission Priority<BR>&gt;&gt; parameter defined in section 6.2.9 of [nsis-qspec], or in the <BR>&gt;&gt; Admission<BR>&gt;&gt; Priority parameter defined in section 4.10 of [dime-qos- <BR>&gt;&gt; parameters].<BR>&gt;&gt; In other words, a given value in any of the [emergency-rsvp] <BR>&gt;&gt; Admission<BR>&gt;&gt; Priority information element, the [nsis-qspec]
 Admission Priority <BR>&gt;&gt; parameter<BR>&gt;&gt; or the [dime-qos-parameters] Admission Priority parameter, refers to<BR>&gt;&gt; the same Admission Priority.<BR>&gt;&gt; "<BR>&gt;&gt; * the mirror statement will be added in nsis-qspec (section <BR>&gt;&gt; 6.2.9) and dime-qos-parameters (section 4.10)<BR>&gt;&gt;<BR>&gt;&gt; Francois<BR>&gt;&gt;<BR><BR><BR><BR><BR></TSVWG-EMEREGNCY-RSVP></NSIS-QSPEC></DIME-QOS-></JOHN.LOUGHNEY@NOKIA.COM></TSVWG-></JMANNER@CS.HELSINKI.FI></ATTILA.BADER@ERICSSON.COM></JMPOLK@CISCO.COM></MAGNUS.WESTERLUND@ERICSSON.COM></CARLBERG@G11.ORG.UK></HANNES.TSCHOFENIG@GMX.NET></ORAN@CISCO.COM></FLEFAUCH@CISCO.COM></TSVWG@IETF.ORG></FLEFAUCH@CISCO.COM></TSVWG-EMEREGNCY-RSVP></NSIS-QSPEC></DIME-QOS-PARAMETERS></BLOCKQUOTE><BR>  <DIV><BR class=khtml-block-placeholder></DIV>  <HR SIZE=1>  Looking for last minute shopping deals? <A href="http://us.rd.yahoo.com/evt=51734/*http://tools.search.yahoo.com/newsearch/category.php?category=shopping">Find
 them fast with Yahoo! Search.</A></BLOCKQUOTE></DIV><BR></DIV></BLOCKQUOTE><BR><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-1636405445-1203612944=:79660--

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

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

--===============1614443324==--


From nsis-bounces@ietf.org  Fri Feb 22 10:08:35 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5DCDE28C474;
	Fri, 22 Feb 2008 10:08:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.558
X-Spam-Level: 
X-Spam-Status: No, score=-99.558 tagged_above=-999 required=5
	tests=[AWL=-1.233, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=1,
	MIME_HTML_MOSTLY=0.001, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id sb3BLKi4fKKK; Fri, 22 Feb 2008 10:08:31 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9DF083A6C47;
	Fri, 22 Feb 2008 10:06:56 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 965EB28C56F
	for <nsis@core3.amsl.com>; Fri, 22 Feb 2008 10:06:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 Uuc2s5trY8R1 for <nsis@core3.amsl.com>;
	Fri, 22 Feb 2008 10:06:51 -0800 (PST)
Received: from mail120.messagelabs.com (mail120.messagelabs.com
	[216.82.250.83])
	by core3.amsl.com (Postfix) with ESMTP id 3F19128CBA2
	for <nsis@ietf.org>; Fri, 22 Feb 2008 10:05:48 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: tarapore@att.com
X-Msg-Ref: server-12.tower-120.messagelabs.com!1203703541!29781129!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 2462 invoked from network); 22 Feb 2008 18:05:42 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com)
	(144.160.20.54)
	by server-12.tower-120.messagelabs.com with AES256-SHA encrypted SMTP;
	22 Feb 2008 18:05:42 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m1MI5fck012417; Fri, 22 Feb 2008 13:05:41 -0500
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m1MI5aco012381; Fri, 22 Feb 2008 13:05:36 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 22 Feb 2008 12:05:36 -0600
Message-ID: <A1F50CB516D211409DFD05D6B3CE6D300CD2B72D@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <A1F50CB516D211409DFD05D6B3CE6D300CD2B729@KCCLUST06EVS1.ugd.att.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Review of draft-ietf-nsis-qspec-18.txt
Thread-Index: Ach0q12MvQahrstuQwun8EOvDsejDwAzPrfwAAE4ozA=
References: <4EFF5784-4564-4730-A5C1-CD0477DE740A@cisco.com>
	<505424.79660.qm@web63613.mail.re1.yahoo.com>
	<A1F50CB516D211409DFD05D6B3CE6D300CD2B729@KCCLUST06EVS1.ugd.att.com>
From: "TARAPORE, PERCY S, ATTLABS" <tarapore@att.com>
To: "Gerald Ash" <gash5107@yahoo.com>,
	"Francois Le Faucheur IMAP" <flefauch@cisco.com>,
	"Martin Stiemerling" <Stiemerling@nw.neclab.eu>,
	<john.loughney@nokia.com>, "nsis" <nsis@ietf.org>
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1553773838=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1553773838==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8757D.8639424B"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8757D.8639424B
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

The purpose and intent for Y.2171 was to standardize a set of admission =
control priority levels that can be recognized across multiple admin =
domains - and acted upon appropriately to provide the necessary CAC =
within each domain. Further, Priority Level 1 - the highest CAC priority =
- is exclusively reserved for emergency telecommunications in Y.2171. =
Thus retaining these in the NSIS-QSPEC is appropriate. They should not =
be changed or removed.
=20
Percy S. Tarapore

________________________________

From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On Behalf Of =
Gerald Ash
Sent: Thursday, February 21, 2008 11:56 AM
To: Francois Le Faucheur IMAP; Martin Stiemerling; =
john.loughney@nokia.com; nsis
Cc: cornelia.kappler@googlemail.com
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.txt


Francois, Martin, John, All,
=20
>>> o Regarding Admission Priority:
>>> * every protocol spec will only indicate that "higher value
>>> means higher priority".
>>> * there is no attempt to define what specific values should
>>> be used for what. this is left outside the scope of the
>>> protocol specs.
>>> * each protocol spec will add a statement clarifying that a
>>> given Admission Priority is to be encoded with the same
>>> value in each of the three protocol spec. For example, in
>>> tsvwg-emergency-rsvp, under section 3.1. we will add:
>>> " A given Admission Priority is encoded in this information
>>> element using the same value as when encoded in the
>>> Admission Priority parameter defined in section 6.2.9 of
>>> [nsis-qspec], or in the Admission Priority parameter
>>> defined in section 4.10 of [dime-qos-parameters].
>>> In other words, a given value in any of the
>>> [emergency-rsvp] Admission Priority information element,
>>> the [nsis-qspec] Admission Priority parameter or the
>>> [dime-qos-parameters] Admission Priority parameter,
>>> refers to the same Admission Priority.
=20
>> The above proposed paragraph is really unclear.  Which draft
>> is setting up IANA Registries to assign Admission Priority
>> parameters?  The way it reads it sounds like all three drafts
>> are setting up registries but that somehow (magically) all refer
>> "to the same Admission Priority".  How can that be if they
>> assign different values?  Right now emergency-rsvp and
>> nsis-qspec set up registries for Admission Priority and
>> dime-qos-parameters is using the nsis-qspec registry as I
>> recall.
>>
>> Please clarify the proposal as to which draft is setting up a
>> registry for Admission Priority.=20


> No registry is setup.
> It is up to a network administrator to decide how many/which
> admission priority gets used for what. This is similar to how
> Preemption is used (ie each network administrator may decide=20
> to use it or not, may decide to use 2,3,4,...128,.. levels...).
> The statement above only says that the the same value of=20
> admission priority should be used in the three protocols to refer=20
> to same level of admission priority.
=20
That's a fundamental change to NSIS/QSPEC and does away with =
standardized Admission Priority values.  QSPEC is following Y.1571 (now =
Y.2171 according to An Nguyen) in standardizing 3 priority levels to =
have end-to-end cross-domain significance.
=20
If we elimate this standardization, as is proposed, then different =
admission priority values can be assigned in different Admin domains, =
and will have no end-to-end significance.  For example, Admin-domain 1, =
Admin-domain 2, and Admin-domain 3 assign admission priority=3D2,  =
admission priority=3D4, admission priority=3D10 for the highest level =
priority, respectively.  Admin-domain 1 and Admin-domain 2 try to =
initiate end-to-end flows via Admin-domain 3 for a 'high priority' flow. =
 However, Admin-domain 3 has no idea how to treat the flow admission =
priority since all 3 domains are using different encodings of high =
priority.
=20
Admission priority is not the same as preemption priority and should not =
be based on that model.
=20
IMO we should retain the standardized admission priority levels based on =
Y.1571/Y.2171.  Otherwise, how do we achieve end-to-end, cross-domain =
standardization of admission priority?  In any case, we need to see some =
good justification for the change.
=20
>> I saw no discussion of this proposed resolution on the NSIS list.=20


> which is why we've been assuming there was no issue with it.=20
=20
It isn't sufficient to declare 'silence is agreement' on making such a =
fundamental change.  People should weigh in *on the list* and give their =
technical justifications and confirm their agreement (or disagreement).
=20
>> Who were the QSPEC co-authors who worked with you on the
>> proposed resolution?


> Attila, Cornelia and Dave Oran (+ NSIS WG chairs).
=20
So far I've not been able to verify agreement from the QSPEC co-authors =
as yet.  We saw no discussion of the issue on the list, and there needs =
to be some explanation/justification for the change. =20
=20
Perhaps Francois could summarize the technical discussion amonst the =
co-authors, and also state who explicitly agreed (as opposed to who had =
no comment or active participation in the discussion). =20
=20
It would be good if the co-authors who participated in the discussion of =
the 'proposed agreement' could weigh in on the list with their technical =
view.
=20
Also, both NSIS chairs have said there is an agreement on the proposal, =
so perhaps they could weigh in on the list also with their technical =
view.
=20
Jerry


Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:

	Hello Jerry,=20

	On 20 Feb 2008, at 16:58, Gerald Ash wrote:


		Francois,
		=20
		In your "Proposed Resolution" posting to NSIS on 3 December =
http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html you say:
		=20
		> The Proposed Resolution
		> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
		> Co-authors of the three I-Ds as well as WG chairs of the=20
		> corresponding WGs converged on the following proposed=20
		> resolution.=20
		=20
		I saw no discussion of this proposed resolution on the NSIS list.=20


	which is why we've been assuming there was no issue with it. =20



		Who were the QSPEC co-authors who worked with you on the proposed =
resolution?


	Attila, Cornelia and Dave Oran (+ NSIS WG chairs).



		=20
		> o Regarding RPH-Priority:
		> * tsvwg-emergency-rsvp will go ahead with its requests to
		> IANA to provide numerical registry for RPH priority (via=20
		> extending existing RPH registry). See IANA Considerations
		> section of tsvwg-emergency-rsvp.
		> * nsis-qspec (in section 6.2.10) will point to this registry
		> instead of defining its own values
		=20
		OK.
		=20
		> o Regarding Admission Priority:
		> * every protocol spec will only indicate that "higher value
		> means higher priority".
		> * there is no attempt to define what specific values should
		> be used for what. this is left outside the scope of the
		> protocol specs.
		* each protocol spec will add a statement clarifying that a
		> given Admission Priority is to be encoded with the same
		> value in each of the three protocol spec. For example, in
		> tsvwg-emergency-rsvp, under section 3.1. we will add:
		" A given Admission Priority is encoded in this information
		> element using the same value as when encoded in the
		> Admission Priority parameter defined in section 6.2.9 of
		> [nsis-qspec], or in the Admission Priority parameter
		> defined in section 4.10 of [dime-qos-parameters].
		> In other words, a given value in any of the
		> [emergency-rsvp] Admission Priority information element,
		> the [nsis-qspec] Admission Priority parameter or the
		> [dime-qos-parameters] Admission Priority parameter,
		> refers to the same Admission Priority.
	=09
		The above proposed paragraph is really unclear.  Which draft is =
setting up IANA Registries to assign Admission Priority parameters?  The =
way it reads it sounds like all three drafts are setting up registries =
but that somehow (magically) all refer "to the same Admission Priority". =
 How can that be if they assign different values?  Right now =
emergency-rsvp and nsis-qspec set up registries for Admission Priority =
and dime-qos-parameters is using the nsis-qspec registry as I recall.
		=20
		Please clarify the proposal as to which draft is setting up a registry =
for Admission Priority.=20


	No registry is setup.
	It is up to a network administrator to decide how many/which admission =
priority gets used for what. This is similar to how Preemption is used =
(ie each network administrator may decide to use it or not, may decide =
to use 2,3,4,...128,.. levels...).
	The statement above only says that the the same value of admission =
priority should be used in the three protocols to refer to same level of =
admission priority.

	Cheers

	Francois



		Also, please provide clearer proposed text to include in the drafts. =20
		=20
		It would be good to see some discussion of the proposal on the list, =
to confirm and validate agreement of the WG.
		=20
		Jerry
	=09


		Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:

			Hello,
		=09
			For memory, the next rev of nsis-qspec is also expected to be aligned =

			with the Resolution of the issue related to QoS Parameters encoding=20
			in , & . For=20
			convenience, I included below the recap on the corresponding=20
			resolution as announced on NSIS, DIME and TSVWG lists.
		=09
			Just to make sure this does not fall through the cracks.
		=09
			Cheers
		=09
			Francois
		=09
		=09
			>
			> Begin forwarded message:
			>> From: Francois Le Faucheur IMAP=20
			>> Date: 3 December 2007 12:05:42 GMT+01:00
			>> To: dime@ietf.org, nsis@ietf.org, tsvwg tsvwg=20
			>> Cc: Francois Le Faucheur IMAP , David Oran R=20
			>> , Hannes Tschofenig ,=20
			>> ken carlberg , Magnus Westerlund=20
			>> , James Polk ,=20
			>> cornelia.kappler@nsn.com, "(IJ/ETH) B=E1der Attila"=20
			>> , jouni.korhonen@teliasonera.com, Jukka=20
			>> Manner MJ , tsvwg chair=20
			>> chairs@tools.ietf.org>, nsis-chairs@tools.ietf.org, dime-=20
			>> chairs@tools.ietf.org, "john.loughney@nokia.com>"=20
			>>=20
			>> Subject: Resolution of issue QoS Parameters encoding in=20
			>> parameters>, &=20
			>>
			>> Hello,
			>>
			>> The Issue:
			>> =3D=3D=3D=3D=3D=3D=3D
			>> Three different documents (dime-qos-parameters, nsis-qos-nslp,=20
			>> tsvwg-emergency-rsvp) need to convey an overlapping set of QoS=20
			>> parameters (specifically RPH-Priority and Admission Priority) and=20
			>> currently do that in an inconsistent manner. This has been brought =

			>> up and partially discussed on the WG mailing lists.
			>>
			>> The Proposed Resolution
			>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
			>> Co-authors of the three I-Ds as well as WG chairs of the=20
			>> corresponding WGs converged on the following proposed resolution.=20
			>> Please let us know if you have an issue/concern with this.
			>>
			>> o Regarding RPH-Priority:
			>> * tsvwg-emergency-rsvp will go ahead with its requests to IANA to=20
			>> provide numerical registry for RPH priority (via extending=20
			>> existing RPH registry). See IANA Considerations section of tsvwg-=20
			>> emergency-rsvp.
			>> * nsis-qspec (in section 6.2.10) will point to this registry=20
			>> instead of defining its own values
			>> * dime-qos-parameters (in section 4.11) will point to this=20
			>> registry instead of defining its own values
			>> * tsvwg-emergency-rsvp (in section 3.2) will keep pointing to=20
			>> this registry.
			>>
			>> o Regarding Admission Priority:
			>> * every protocol spec will only indicate that "higher value means=20
			>> higher priority".
			>> * there is no attempt to define what specific values should be=20
			>> used for what. this is left outside the scope of the protocol =
specs.
			>> * each protocol spec will add a statement clarifying that a given=20
			>> Admission Priority is to be encoded with the same value in each of =

			>> the three protocol spec. For example, in tsvwg-emergency-rsvp,=20
			>> under section 3.1. we will add:
			>> " A given Admission Priority is encoded in this information=20
			>> element
			>> using the same value as when encoded in the Admission Priority
			>> parameter defined in section 6.2.9 of [nsis-qspec], or in the=20
			>> Admission
			>> Priority parameter defined in section 4.10 of [dime-qos-=20
			>> parameters].
			>> In other words, a given value in any of the [emergency-rsvp]=20
			>> Admission
			>> Priority information element, the [nsis-qspec] Admission Priority=20
			>> parameter
			>> or the [dime-qos-parameters] Admission Priority parameter, refers =
to
			>> the same Admission Priority.
			>> "
			>> * the mirror statement will be added in nsis-qspec (section=20
			>> 6.2.9) and dime-qos-parameters (section 4.10)
			>>
			>> Francois
			>>
		=09
		=09
		=09
		=09
		=09



________________________________

		Looking for last minute shopping deals? Find them fast with Yahoo! =
Search. =
<http://us.rd.yahoo.com/evt=3D51734/*http://tools.search.yahoo.com/newsea=
rch/category.php?category=3Dshopping>=20



________________________________

Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try =
it now. =
<http://us.rd.yahoo.com/evt=3D51733/*http://mobile.yahoo.com/;_ylt=3DAhu0=
6i62sR8HDtDypao8Wcj9tAcJ> =20

------_=_NextPart_001_01C8757D.8639424B
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3268" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D005322817-22022008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The purpose and intent for Y.2171 was =
to&nbsp;standardize a=20
set of admission control priority levels<SPAN=20
class=3D090300318-22022008>&nbsp;</SPAN>that can be =
recognized&nbsp;across=20
multiple admin domains - and acted upon appropriately to provide the =
necessary=20
CAC within each domain. Further, Priority Level 1 - the highest CAC =
priority -=20
is exclusively reserved for emergency telecommunications in Y.2171. Thus =

retaining these in the NSIS-QSPEC is appropriate. They should not be =
changed or=20
removed.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D005322817-22022008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D005322817-22022008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Percy S. Tarapore</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> nsis-bounces@ietf.org=20
[mailto:nsis-bounces@ietf.org] <B>On Behalf Of </B>Gerald =
Ash<BR><B>Sent:</B>=20
Thursday, February 21, 2008 11:56 AM<BR><B>To:</B> Francois Le Faucheur =
IMAP;=20
Martin Stiemerling; john.loughney@nokia.com; nsis<BR><B>Cc:</B>=20
cornelia.kappler@googlemail.com<BR><B>Subject:</B> Re: [NSIS] Review of=20
draft-ietf-nsis-qspec-18.txt<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=3Darial>Francois, Martin, John, All,</FONT></DIV>
<DIV><FONT face=3Darial></FONT>&nbsp;</DIV>
<DIV><FONT face=3Darial>
<DIV><FONT face=3Darial>&gt;&gt;&gt; o Regarding Admission=20
Priority:<BR>&gt;&gt;&gt; * every protocol spec will only indicate that =
"higher=20
value</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;means higher =
priority".</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt; * there is no attempt to define =
what specific=20
values should</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;be used for what. this is left =
outside=20
the scope of the</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;protocol =
specs.<BR>&gt;&gt;&gt; * each=20
protocol spec will add a statement clarifying that a</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;given Admission Priority is to =
be=20
encoded with the same</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;value in each of the three =
protocol=20
spec. For example, in</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;tsvwg-emergency-rsvp, under =
section 3.1.=20
we will add:<BR>&gt;&gt;&gt; " A given Admission Priority is encoded in =
this=20
information</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;element using the same value =
as when=20
encoded in the</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;Admission Priority parameter =
defined in=20
section 6.2.9 of</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;[nsis-qspec], or in the =
Admission=20
Priority parameter</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;defined in section 4.10 of=20
[dime-qos-parameters].</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt; In other words, a given value in =
any of=20
the</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;[emergency-rsvp] Admission =
Priority=20
information element,</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;the [nsis-qspec] Admission =
Priority=20
parameter or the</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;[dime-qos-parameters] =
Admission Priority=20
parameter,</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;refers to the same Admission=20
Priority.</FONT></DIV>
<DIV><FONT face=3Darial>&nbsp;</DIV></FONT>
<DIV><FONT face=3Darial>&gt;&gt; The above proposed paragraph is really=20
unclear.&nbsp; Which draft</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&nbsp;is setting up IANA Registries to =
assign=20
Admission Priority</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&nbsp;parameters?&nbsp; The way it reads =
it sounds=20
like all three drafts</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&nbsp;are setting up registries but that =

somehow&nbsp;(magically) all&nbsp;refer</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&nbsp;"to the same Admission =
Priority".&nbsp; How=20
can that be if they</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&nbsp;assign different values?&nbsp; =
Right now=20
emergency-rsvp and</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&nbsp;nsis-qspec set up registries for =
Admission=20
Priority and</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&nbsp;dime-qos-parameters is using the =
nsis-qspec=20
registry as I</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&nbsp;recall.</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt; Please clarify the proposal as to which =
draft is=20
setting up a</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&nbsp;registry for Admission=20
Priority.&nbsp;</FONT></DIV>
<DIV><FONT face=3Darial><BR =
class=3Dwebkit-block-placeholder></FONT></DIV>
<DIV><FONT face=3Darial>&gt; No registry is setup.</FONT></DIV>
<DIV><FONT face=3Darial>&gt; It is up to a network administrator to =
decide how=20
many/which</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&nbsp;admission priority gets used for what. =
This is=20
similar to how</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&nbsp;Preemption is used (ie each network=20
administrator may decide </FONT></DIV>
<DIV><FONT face=3Darial>&gt; to use it or not, may decide to use =
2,3,4,...128,..=20
levels...).</FONT></DIV>
<DIV><FONT face=3Darial>&gt; The statement above only says that the the =
same value=20
of </FONT></DIV>
<DIV><FONT face=3Darial>&gt; admission priority should be used in the =
three=20
protocols to refer </FONT></DIV>
<DIV><FONT face=3Darial>&gt; to same level of admission =
priority.</FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV>That's a fundamental change to NSIS/QSPEC and does away with =
standardized=20
Admission Priority values.&nbsp; QSPEC is following Y.1571 (now Y.2171 =
according=20
to An Nguyen) in standardizing 3 priority levels to have end-to-end =
cross-domain=20
significance.</DIV>
<DIV>&nbsp;</DIV>
<DIV>If we elimate this standardization, as is proposed, then different=20
admission priority values&nbsp;can be&nbsp;assigned in different Admin =
domains,=20
and will&nbsp;have no end-to-end significance.&nbsp; For example, =
Admin-domain=20
1, Admin-domain 2, and Admin-domain 3 assign&nbsp;admission=20
priority=3D2,&nbsp;&nbsp;admission priority=3D4, admission priority=3D10 =
for the=20
highest level priority, respectively.&nbsp; Admin-domain 1 and =
Admin-domain 2=20
try to initiate end-to-end flows via Admin-domain&nbsp;3 for a 'high =
priority'=20
flow.&nbsp;&nbsp;However, Admin-domain 3 has no idea how to treat the =
flow=20
admission priority since all 3 domains are using different encodings of =
high=20
priority.</DIV>
<DIV>
<DIV>&nbsp;</DIV>
<DIV>Admission priority is not the same as preemption priority and =
should not be=20
based on that model.</DIV>
<DIV>&nbsp;</DIV></DIV>
<DIV>IMO we should retain the standardized admission priority levels =
based on=20
Y.1571/Y.2171.&nbsp; Otherwise, how do we achieve end-to-end, =
cross-domain=20
standardization of admission priority?&nbsp; In any case, we need to see =
some=20
good justification for the change.</DIV>
<DIV>&nbsp;</DIV>
<DIV>
<DIV><FONT face=3Darial>&gt;&gt; I saw no discussion of this proposed =
resolution=20
on the NSIS list.&nbsp;</FONT></DIV>
<DIV><FONT face=3Darial><BR =
class=3Dwebkit-block-placeholder></FONT></DIV>
<DIV><FONT face=3Darial>&gt; which is why we've been assuming there was =
no issue=20
with it. </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>It isn't sufficient to&nbsp;declare 'silence is agreement' on =
making such a=20
fundamental change.&nbsp; People should weigh in *on the list* and give=20
their&nbsp;technical justifications and confirm their agreement (or=20
disagreement).</DIV>
<DIV><FONT face=3Darial></FONT>&nbsp;</DIV>
<DIV><FONT face=3Darial>&gt;&gt; Who were the QSPEC co-authors who =
worked with you=20
on the</FONT></DIV>
<DIV><FONT face=3Darial>&gt;&gt;&nbsp;proposed resolution?</FONT></DIV>
<DIV><FONT face=3Darial><BR =
class=3Dwebkit-block-placeholder></FONT></DIV>
<DIV><FONT face=3Darial>&gt; Attila, Cornelia and Dave Oran (+ NSIS WG=20
chairs).</FONT></DIV>
<DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV>So far I've not been able to verify agreement from the QSPEC =
co-authors as=20
yet.&nbsp; We saw no discussion of the issue on the list, and there =
needs to be=20
some explanation/justification for the change.&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>Perhaps Francois could summarize the technical&nbsp;discussion =
amonst the=20
co-authors, and also state who explicitly agreed (as opposed to who had =
no=20
comment or active participation in the discussion).&nbsp;&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>It would be good if the co-authors who participated&nbsp;in the =
discussion=20
of the 'proposed agreement' could weigh in on the list with their =
technical=20
view.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Also, both NSIS chairs have said there is an agreement on the =
proposal, so=20
perhaps they could weigh in on the list also with their technical =
view.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Jerry</DIV></DIV></FONT><BR><BR><B><I>Francois Le Faucheur IMAP=20
&lt;flefauch@cisco.com&gt;</I></B> wrote:</DIV>
<BLOCKQUOTE class=3Dreplbq=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px =
solid">Hello=20
  Jerry,=20
  <DIV><BR>
  <DIV>
  <DIV>On 20 Feb 2008, at 16:58, Gerald Ash wrote:</DIV><BR=20
  class=3DApple-interchange-newline>
  <BLOCKQUOTE type=3D"cite">
    <DIV><FONT face=3D"Courier&#13;&#10; New">Francois,</FONT></DIV>
    <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
    <DIV><FONT face=3D"Courier New">In your "Proposed Resolution" =
posting to NSIS=20
    on 3 December <A=20
    =
href=3D"http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html">=
http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html</A>&nbsp;=
you=20
    say:</FONT></DIV>
    <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
    <DIV><FONT face=3D"Courier New">&gt; The Proposed Resolution<BR>&gt; =

    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>&gt; =
Co-authors of the three I-Ds as well as WG=20
    chairs of the </FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt; corresponding WGs converged on =
the=20
    following proposed </FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt; resolution. </FONT></DIV>
    <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
    <DIV><FONT face=3D"Courier New">I saw no discussion of this proposed =

    resolution on the NSIS list.&nbsp;</FONT></DIV></BLOCKQUOTE>
  <DIV><BR class=3Dwebkit-block-placeholder></DIV>
  <DIV>which is why we've been assuming there was no issue with it. =
&nbsp;</DIV>
  <DIV><BR class=3Dwebkit-block-placeholder></DIV><BR>
  <BLOCKQUOTE type=3D"cite">
    <DIV><FONT face=3D"Courier New">Who were the QSPEC co-authors who =
worked with=20
    you on the proposed resolution?</FONT></DIV></BLOCKQUOTE>
  <DIV><BR class=3Dwebkit-block-placeholder></DIV>
  <DIV>Attila, Cornelia and Dave Oran (+ NSIS WG chairs).</DIV>
  <DIV><BR></DIV><BR>
  <BLOCKQUOTE type=3D"cite">
    <DIV>&nbsp;</DIV>
    <DIV><FONT face=3D"Courier New">&gt; o Regarding =
RPH-Priority:<BR>&gt; *=20
    tsvwg-emergency-rsvp will go ahead with its requests to</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;IANA </FONT><FONT=20
    face=3D"Courier New">to provide numerical registry for RPH priority =
(via=20
    </FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt; extending existing RPH =
registry). See=20
    IANA Considerations</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;section of=20
    tsvwg-emergency-rsvp.</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt; * nsis-qspec (in section =
6.2.10) will=20
    point to this registry</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;instead of defining its =
own=20
    values</FONT></DIV>
    <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
    <DIV><FONT face=3D"Courier New">OK.</FONT></DIV>
    <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
    <DIV><FONT face=3D"Courier New">&gt; o Regarding Admission =
Priority:<BR>&gt; *=20
    every protocol spec will only indicate that "higher =
value</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;means higher =
priority".</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt; * there is no attempt to define =
what=20
    specific values should</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;be used for what. this is =
left=20
    outside the scope of the</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;protocol specs.<BR>* each =
protocol=20
    spec will add a statement clarifying that a</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;given Admission Priority =
is to be=20
    encoded with the same</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;value in each of the three =
protocol=20
    spec. For example, in</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;tsvwg-emergency-rsvp, =
under section=20
    3.1. we will add:<BR>" A given Admission Priority is encoded in this =

    information</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;element using the same =
value as when=20
    encoded in the</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;Admission Priority =
parameter defined=20
    in section 6.2.9 of</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;[nsis-qspec], or in the =
Admission=20
    Priority parameter</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;defined in section 4.10 of =

    [dime-qos-parameters].</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt; In other words, a given value =
in any of=20
    the</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;[emergency-rsvp] Admission =
Priority=20
    information element,</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;the [nsis-qspec] Admission =
Priority=20
    parameter or the</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;[dime-qos-parameters] =
Admission=20
    Priority parameter,</FONT></DIV>
    <DIV><FONT face=3D"Courier New">&gt;&nbsp;refers to the same =
Admission=20
    Priority.<BR></FONT></DIV>
    <DIV><FONT face=3D"Courier New">The above proposed paragraph is =
really=20
    unclear.&nbsp; Which draft&nbsp;is setting up IANA Registries to =
assign=20
    Admission Priority parameters?&nbsp; The way it reads it sounds like =
all=20
    three drafts are setting up registries but that =
somehow&nbsp;(magically)=20
    all&nbsp;refer "to the same Admission Priority".&nbsp; How can that =
be if=20
    they assign different values?&nbsp; Right now emergency-rsvp and =
nsis-qspec=20
    set up registries for Admission Priority and dime-qos-parameters is =
using=20
    the nsis-qspec registry as I recall.</FONT></DIV>
    <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
    <DIV><FONT face=3D"Courier New">Please clarify the proposal as to =
which draft=20
    is setting up a registry for Admission=20
  Priority.&nbsp;</FONT></DIV></BLOCKQUOTE>
  <DIV><BR class=3Dwebkit-block-placeholder></DIV>
  <DIV>No registry is setup.</DIV>
  <DIV>It is up to a network administrator to decide how many/which =
admission=20
  priority gets used for what. This is similar to how Preemption is used =
(ie=20
  each network administrator may decide to use it or not, may decide to =
use=20
  2,3,4,...128,.. levels...).</DIV>
  <DIV>The statement above only says that the the same value of =
admission=20
  priority should be used in the three protocols to refer to same level =
of=20
  admission priority.</DIV>
  <DIV><BR class=3Dwebkit-block-placeholder></DIV>
  <DIV>Cheers</DIV>
  <DIV><BR class=3Dwebkit-block-placeholder></DIV>
  <DIV>Francois</DIV>
  <DIV><BR class=3Dwebkit-block-placeholder></DIV><BR>
  <BLOCKQUOTE type=3D"cite">
    <DIV><FONT face=3D"Courier New">Also, please provide =
clearer&nbsp;proposed=20
    text to include in the drafts.&nbsp; </FONT></DIV>
    <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
    <DIV><FONT face=3D"Courier New">It would be good to see some =
discussion of the=20
    proposal on the list, to confirm and validate agreement of the=20
    WG.</FONT></DIV>
    <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
    <DIV><FONT face=3D"Courier New">Jerry</FONT></DIV><FONT=20
    face=3D"Courier New"></FONT>
    <DIV><BR><BR><B><I>Francois Le Faucheur IMAP &lt;<A=20
    =
href=3D"mailto:flefauch@cisco.com">flefauch@cisco.com</A>&gt;</I></B>=20
    wrote:</DIV>
    <BLOCKQUOTE class=3Dreplbq=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff =
2px solid">Hello,<BR><BR>For=20
      memory, the next rev of nsis-qspec is also expected to be aligned =
<BR>with=20
      the Resolution of the issue related to QoS Parameters encoding =
<BR>in=20
      <DIME-QOS-PARAMETERS>, <NSIS-QSPEC>&amp; <TSVWG-EMEREGNCY-RSVP>. =
For=20
      <BR>convenience, I included below the recap on the corresponding=20
      <BR>resolution as announced on NSIS, DIME and TSVWG =
lists.<BR><BR>Just to=20
      make sure this does not fall through the=20
      cracks.<BR><BR>Cheers<BR><BR>Francois<BR><BR><BR>&gt;<BR>&gt; =
Begin=20
      forwarded message:<BR>&gt;&gt; From: Francois Le Faucheur IMAP=20
      <FLEFAUCH@CISCO.COM><BR>&gt;&gt; Date: 3 December 2007 12:05:42=20
      GMT+01:00<BR>&gt;&gt; To: <A=20
      href=3D"mailto:dime@ietf.org">dime@ietf.org</A>, <A=20
      href=3D"mailto:nsis@ietf.org">nsis@ietf.org</A>, tsvwg tsvwg=20
      <TSVWG@IETF.ORG><BR>&gt;&gt; Cc: Francois Le Faucheur IMAP=20
      <FLEFAUCH@CISCO.COM>, David Oran R <BR>&gt;&gt; <ORAN@CISCO.COM>, =
Hannes=20
      Tschofenig <HANNES.TSCHOFENIG@GMX.NET>, <BR>&gt;&gt; ken carlberg=20
      <CARLBERG@G11.ORG.UK>, Magnus Westerlund <BR>&gt;&gt;=20
      <MAGNUS.WESTERLUND@ERICSSON.COM>, James Polk <JMPOLK@CISCO.COM>,=20
      <BR>&gt;&gt; <A=20
      =
href=3D"mailto:cornelia.kappler@nsn.com">cornelia.kappler@nsn.com</A>,=20
      "(IJ/ETH) B=E1der Attila" <BR>&gt;&gt; =
<ATTILA.BADER@ERICSSON.COM>, <A=20
      =
href=3D"mailto:jouni.korhonen@teliasonera.com">jouni.korhonen@teliasonera=
.com</A>,=20
      Jukka <BR>&gt;&gt; Manner MJ <JMANNER@CS.HELSINKI.FI>, tsvwg chair =

      <TSVWG-><BR>&gt;&gt; <A=20
      =
href=3D"mailto:chairs@tools.ietf.org">chairs@tools.ietf.org</A>&gt;, <A=20
      =
href=3D"mailto:nsis-chairs@tools.ietf.org">nsis-chairs@tools.ietf.org</A>=
,=20
      dime- <BR>&gt;&gt; <A=20
      href=3D"mailto:chairs@tools.ietf.org">chairs@tools.ietf.org</A>, =
"<A=20
      =
href=3D"mailto:john.loughney@nokia.com">john.loughney@nokia.com</A>&gt;" =

      <BR>&gt;&gt; <JOHN.LOUGHNEY@NOKIA.COM><BR>&gt;&gt; Subject: =
Resolution of=20
      issue QoS Parameters encoding in <DIME-QOS-><BR>&gt;&gt; =
parameters&gt;,=20
      <NSIS-QSPEC>&amp; <TSVWG-EMEREGNCY-RSVP><BR>&gt;&gt;<BR>&gt;&gt;=20
      Hello,<BR>&gt;&gt;<BR>&gt;&gt; The Issue:<BR>&gt;&gt; =
=3D=3D=3D=3D=3D=3D=3D<BR>&gt;&gt;=20
      Three different documents (dime-qos-parameters, nsis-qos-nslp,=20
      <BR>&gt;&gt; tsvwg-emergency-rsvp) need to convey an overlapping =
set of=20
      QoS <BR>&gt;&gt; parameters (specifically RPH-Priority and =
Admission=20
      Priority) and <BR>&gt;&gt; currently do that in an inconsistent =
manner.=20
      This has been brought <BR>&gt;&gt; up and partially discussed on =
the WG=20
      mailing lists.<BR>&gt;&gt;<BR>&gt;&gt; The Proposed =
Resolution<BR>&gt;&gt;=20
      =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>&gt;&gt; =
Co-authors of the three I-Ds as well as WG=20
      chairs of the <BR>&gt;&gt; corresponding WGs converged on the =
following=20
      proposed resolution. <BR>&gt;&gt; Please let us know if you have =
an=20
      issue/concern with this.<BR>&gt;&gt;<BR>&gt;&gt; o Regarding=20
      RPH-Priority:<BR>&gt;&gt; * tsvwg-emergency-rsvp will go ahead =
with its=20
      requests to IANA to <BR>&gt;&gt; provide numerical registry for =
RPH=20
      priority (via extending <BR>&gt;&gt; existing RPH registry). See =
IANA=20
      Considerations section of tsvwg- <BR>&gt;&gt; =
emergency-rsvp.<BR>&gt;&gt;=20
      * nsis-qspec (in section 6.2.10) will point to this registry =
<BR>&gt;&gt;=20
      instead of defining its own values<BR>&gt;&gt; * =
dime-qos-parameters (in=20
      section 4.11) will point to this <BR>&gt;&gt; registry instead of =
defining=20
      its own values<BR>&gt;&gt; * tsvwg-emergency-rsvp (in section 3.2) =
will=20
      keep pointing to <BR>&gt;&gt; this =
registry.<BR>&gt;&gt;<BR>&gt;&gt; o=20
      Regarding Admission Priority:<BR>&gt;&gt; * every protocol spec =
will only=20
      indicate that "higher value means <BR>&gt;&gt; higher=20
      priority".<BR>&gt;&gt; * there is no attempt to define what =
specific=20
      values should be <BR>&gt;&gt; used for what. this is left outside =
the=20
      scope of the protocol specs.<BR>&gt;&gt; * each protocol spec will =
add a=20
      statement clarifying that a given <BR>&gt;&gt; Admission Priority =
is to be=20
      encoded with the same value in each of <BR>&gt;&gt; the three =
protocol=20
      spec. For example, in tsvwg-emergency-rsvp, <BR>&gt;&gt; under =
section=20
      3.1. we will add:<BR>&gt;&gt; " A given Admission Priority is =
encoded in=20
      this information <BR>&gt;&gt; element<BR>&gt;&gt; using the same =
value as=20
      when encoded in the Admission Priority<BR>&gt;&gt; parameter =
defined in=20
      section 6.2.9 of [nsis-qspec], or in the <BR>&gt;&gt;=20
      Admission<BR>&gt;&gt; Priority parameter defined in section 4.10 =
of=20
      [dime-qos- <BR>&gt;&gt; parameters].<BR>&gt;&gt; In other words, a =
given=20
      value in any of the [emergency-rsvp] <BR>&gt;&gt; =
Admission<BR>&gt;&gt;=20
      Priority information element, the [nsis-qspec] Admission Priority=20
      <BR>&gt;&gt; parameter<BR>&gt;&gt; or the [dime-qos-parameters] =
Admission=20
      Priority parameter, refers to<BR>&gt;&gt; the same Admission=20
      Priority.<BR>&gt;&gt; "<BR>&gt;&gt; * the mirror statement will be =
added=20
      in nsis-qspec (section <BR>&gt;&gt; 6.2.9) and dime-qos-parameters =

      (section 4.10)<BR>&gt;&gt;<BR>&gt;&gt;=20
      =
Francois<BR>&gt;&gt;<BR><BR><BR><BR><BR></TSVWG-EMEREGNCY-RSVP></NSIS-QSP=
EC></DIME-QOS-></JOHN.LOUGHNEY@NOKIA.COM></TSVWG-></JMANNER@CS.HELSINKI.F=
I></ATTILA.BADER@ERICSSON.COM></JMPOLK@CISCO.COM></MAGNUS.WESTERLUND@ERIC=
SSON.COM></CARLBERG@G11.ORG.UK></HANNES.TSCHOFENIG@GMX.NET></ORAN@CISCO.C=
OM></FLEFAUCH@CISCO.COM></TSVWG@IETF.ORG></FLEFAUCH@CISCO.COM></TSVWG-EME=
REGNCY-RSVP></NSIS-QSPEC></DIME-QOS-PARAMETERS></BLOCKQUOTE><BR>
    <DIV><BR class=3Dkhtml-block-placeholder></DIV>
    <HR SIZE=3D1>
    Looking for last minute shopping deals? <A=20
    =
href=3D"http://us.rd.yahoo.com/evt=3D51734/*http://tools.search.yahoo.com=
/newsearch/category.php?category=3Dshopping">Find=20
    them fast with Yahoo! =
Search.</A></BLOCKQUOTE></DIV><BR></DIV></BLOCKQUOTE><BR>
<P>
<HR SIZE=3D1>
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. <A=20
href=3D"http://us.rd.yahoo.com/evt=3D51733/*http://mobile.yahoo.com/;_ylt=
=3DAhu06i62sR8HDtDypao8Wcj9tAcJ ">Try=20
it now.</A> </BODY></HTML>

------_=_NextPart_001_01C8757D.8639424B--

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

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

--===============1553773838==--


From nsis-bounces@ietf.org  Fri Feb 22 10:54:32 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 02EAB28C836;
	Fri, 22 Feb 2008 10:54:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.156
X-Spam-Level: 
X-Spam-Status: No, score=0.156 tagged_above=-999 required=5 tests=[AWL=-2.915,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=1, MIME_HTML_MOSTLY=0.001,
	MIME_QP_LONG_LINE=1.396, RDNS_NONE=0.1, 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 EfMb4HMTlp8B; Fri, 22 Feb 2008 10:54:28 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 73B1828CAD2;
	Fri, 22 Feb 2008 10:54:12 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7AA9728CA45
	for <nsis@core3.amsl.com>; Fri, 22 Feb 2008 10:54:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 F-Q7qhEbnk0T for <nsis@core3.amsl.com>;
	Fri, 22 Feb 2008 10:54:08 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 486E828C9E0
	for <nsis@ietf.org>; Fri, 22 Feb 2008 10:52:39 -0800 (PST)
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 22 Feb 2008 19:52:28 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m1MIqS6c025145; 
	Fri, 22 Feb 2008 19:52:28 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m1MIqEXN011705; 
	Fri, 22 Feb 2008 18:52:23 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Feb 2008 19:52:22 +0100
Received: from [144.254.53.198] ([144.254.53.198]) by xfe-ams-332.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Feb 2008 19:52:21 +0100
In-Reply-To: <A1F50CB516D211409DFD05D6B3CE6D300CD2B72D@KCCLUST06EVS1.ugd.att.com>
References: <4EFF5784-4564-4730-A5C1-CD0477DE740A@cisco.com>
	<505424.79660.qm@web63613.mail.re1.yahoo.com>
	<A1F50CB516D211409DFD05D6B3CE6D300CD2B729@KCCLUST06EVS1.ugd.att.com>
	<A1F50CB516D211409DFD05D6B3CE6D300CD2B72D@KCCLUST06EVS1.ugd.att.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <5D6F2B15-4E24-4FFF-8EFF-D3B7DB99F751@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Date: Fri, 22 Feb 2008 19:52:18 +0100
To: "TARAPORE, PERCY S, ATTLABS" <tarapore@att.com>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 22 Feb 2008 18:52:21.0058 (UTC)
	FILETIME=[0DF87A20:01C87584]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=42563; t=1203706348;
	x=1204570348; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com>
	|Subject:=20Re=3A=20[NSIS]=20Review=20of=20draft-ietf-nsis-
	qspec-18.txt |Sender:=20;
	bh=7+UG5G3CjSA1mYvWwuvF7AWW+q/BxqS6DKoeWzBG4QY=;
	b=uLAW1rFfNlWb5g9AdX+koArYXJE9tWfhms5NRBUQ9g+AEqQFhZJ7+5u7CH
	Gb0I7pBYW4zNHOeodlgy0DfIOyWROCWTB4adeiw2ys8fmxJgbU2HhLMH1oRU
	3B50DkaGrr;
Authentication-Results: ams-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: john.loughney@nokia.com, nsis <nsis@ietf.org>
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0405226331=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


--===============0405226331==
Content-Type: multipart/alternative; boundary=Apple-Mail-19--86644756


--Apple-Mail-19--86644756
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=ISO-8859-1;
	delsp=yes;
	format=flowed

Hello Percy,

Some of the considerations that led to the decision to not re-specify =20=

in <emergency-rsvp>, <dime-qos-parameters> and <nsis-qspec> the =20
admission priority values that are already specified in Y.2171 specs =20
included:
	* they are already defined in this ITU spec
	* if one wants to comply with the ITU way to do Admission =
Priority =20
they can follow the ITU spec
	* it is not 100% obvious that absolutely every network =
administrator =20
will ever want to implement admission priority exactly as specified =20
by ITU and by that particular spec. Maybe one administrator will want =20=

to use less priorities, maybe one will want to use more...
	* the admission mechanism to be defined by IETF should be =
flexible =20
and not tied to one single application of one single SDO.
	* the admission priority mechanism defined in IETF should allow =20=

support of a particular application of a particular SDO. This can be =20
achieved by deliberate choice of a network administrator to use the =20
values of that application/SDO (but we don't have to mandate that =20
everybody using the admission priority mechanisms use it in the same =20
way)
	* this is the approach already used for the "Preemption" =
mechanism =20
supported by NSIS and RSVP (ie it is up to network administrator to =20
decide which preemption priority value to use in their network and =20
their semantic is not defined in the documents)
	* as a side practical considerations: it is undesirable to have =
an =20
IETF spec tied to specifications of another body (eg what happens if =20
ITU defines Y.2171bis with one more value? do we have to immediately =20
reissue <emergency-rsvp>, <dime-qos-parameters> and <nsis-qspec>)? =20
For example, if those documents would have mandated the ITU values =20
and have been standardised in 2006, they would have referred to Y.=20
1571 (as I think Qspec used to do before Y.1571 got superseded by Y.=20
2171...)

Cheers

Francois

On 22 Feb 2008, at 19:05, TARAPORE, PERCY S, ATTLABS wrote:

> The purpose and intent for Y.2171 was to standardize a set of =20
> admission control priority levels that can be recognized across =20
> multiple admin domains - and acted upon appropriately to provide =20
> the necessary CAC within each domain. Further, Priority Level 1 - =20
> the highest CAC priority - is exclusively reserved for emergency =20
> telecommunications in Y.2171. Thus retaining these in the NSIS-=20
> QSPEC is appropriate. They should not be changed or removed.
>
> Percy S. Tarapore
>
> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On =20
> Behalf Of Gerald Ash
> Sent: Thursday, February 21, 2008 11:56 AM
> To: Francois Le Faucheur IMAP; Martin Stiemerling; =20
> john.loughney@nokia.com; nsis
> Cc: cornelia.kappler@googlemail.com
> Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.txt
>
> Francois, Martin, John, All,
>
> >>> o Regarding Admission Priority:
> >>> * every protocol spec will only indicate that "higher value
> >>> means higher priority".
> >>> * there is no attempt to define what specific values should
> >>> be used for what. this is left outside the scope of the
> >>> protocol specs.
> >>> * each protocol spec will add a statement clarifying that a
> >>> given Admission Priority is to be encoded with the same
> >>> value in each of the three protocol spec. For example, in
> >>> tsvwg-emergency-rsvp, under section 3.1. we will add:
> >>> " A given Admission Priority is encoded in this information
> >>> element using the same value as when encoded in the
> >>> Admission Priority parameter defined in section 6.2.9 of
> >>> [nsis-qspec], or in the Admission Priority parameter
> >>> defined in section 4.10 of [dime-qos-parameters].
> >>> In other words, a given value in any of the
> >>> [emergency-rsvp] Admission Priority information element,
> >>> the [nsis-qspec] Admission Priority parameter or the
> >>> [dime-qos-parameters] Admission Priority parameter,
> >>> refers to the same Admission Priority.
>
> >> The above proposed paragraph is really unclear.  Which draft
> >> is setting up IANA Registries to assign Admission Priority
> >> parameters?  The way it reads it sounds like all three drafts
> >> are setting up registries but that somehow (magically) all refer
> >> "to the same Admission Priority".  How can that be if they
> >> assign different values?  Right now emergency-rsvp and
> >> nsis-qspec set up registries for Admission Priority and
> >> dime-qos-parameters is using the nsis-qspec registry as I
> >> recall.
> >>
> >> Please clarify the proposal as to which draft is setting up a
> >> registry for Admission Priority.
>
> > No registry is setup.
> > It is up to a network administrator to decide how many/which
> > admission priority gets used for what. This is similar to how
> > Preemption is used (ie each network administrator may decide
> > to use it or not, may decide to use 2,3,4,...128,.. levels...).
> > The statement above only says that the the same value of
> > admission priority should be used in the three protocols to refer
> > to same level of admission priority.
>
> That's a fundamental change to NSIS/QSPEC and does away with =20
> standardized Admission Priority values.  QSPEC is following Y.1571 =20
> (now Y.2171 according to An Nguyen) in standardizing 3 priority =20
> levels to have end-to-end cross-domain significance.
>
> If we elimate this standardization, as is proposed, then different =20
> admission priority values can be assigned in different Admin =20
> domains, and will have no end-to-end significance.  For example, =20
> Admin-domain 1, Admin-domain 2, and Admin-domain 3 assign admission =20=

> priority=3D2,  admission priority=3D4, admission priority=3D10 for the =
=20
> highest level priority, respectively.  Admin-domain 1 and Admin-=20
> domain 2 try to initiate end-to-end flows via Admin-domain 3 for a =20
> 'high priority' flow.  However, Admin-domain 3 has no idea how to =20
> treat the flow admission priority since all 3 domains are using =20
> different encodings of high priority.
>
> Admission priority is not the same as preemption priority and =20
> should not be based on that model.
>
> IMO we should retain the standardized admission priority levels =20
> based on Y.1571/Y.2171.  Otherwise, how do we achieve end-to-end, =20
> cross-domain standardization of admission priority?  In any case, =20
> we need to see some good justification for the change.
>
> >> I saw no discussion of this proposed resolution on the NSIS list.
>
> > which is why we've been assuming there was no issue with it.
>
> It isn't sufficient to declare 'silence is agreement' on making =20
> such a fundamental change.  People should weigh in *on the list* =20
> and give their technical justifications and confirm their agreement =20=

> (or disagreement).
>
> >> Who were the QSPEC co-authors who worked with you on the
> >> proposed resolution?
>
> > Attila, Cornelia and Dave Oran (+ NSIS WG chairs).
>
> So far I've not been able to verify agreement from the QSPEC co-=20
> authors as yet.  We saw no discussion of the issue on the list, and =20=

> there needs to be some explanation/justification for the change.
>
> Perhaps Francois could summarize the technical discussion amonst =20
> the co-authors, and also state who explicitly agreed (as opposed to =20=

> who had no comment or active participation in the discussion).
>
> It would be good if the co-authors who participated in the =20
> discussion of the 'proposed agreement' could weigh in on the list =20
> with their technical view.
>
> Also, both NSIS chairs have said there is an agreement on the =20
> proposal, so perhaps they could weigh in on the list also with =20
> their technical view.
>
> Jerry
>
>
> Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:
> Hello Jerry,
>
> On 20 Feb 2008, at 16:58, Gerald Ash wrote:
>
>> Francois,
>>
>> In your "Proposed Resolution" posting to NSIS on 3 December http://=20=

>> www.ietf.org/mail-archive/web/nsis/current/msg08155.html you say:
>>
>> > The Proposed Resolution
>> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> > Co-authors of the three I-Ds as well as WG chairs of the
>> > corresponding WGs converged on the following proposed
>> > resolution.
>>
>> I saw no discussion of this proposed resolution on the NSIS list.
>
> which is why we've been assuming there was no issue with it.
>
>
>> Who were the QSPEC co-authors who worked with you on the proposed =20
>> resolution?
>
> Attila, Cornelia and Dave Oran (+ NSIS WG chairs).
>
>
>>
>> > o Regarding RPH-Priority:
>> > * tsvwg-emergency-rsvp will go ahead with its requests to
>> > IANA to provide numerical registry for RPH priority (via
>> > extending existing RPH registry). See IANA Considerations
>> > section of tsvwg-emergency-rsvp.
>> > * nsis-qspec (in section 6.2.10) will point to this registry
>> > instead of defining its own values
>>
>> OK.
>>
>> > o Regarding Admission Priority:
>> > * every protocol spec will only indicate that "higher value
>> > means higher priority".
>> > * there is no attempt to define what specific values should
>> > be used for what. this is left outside the scope of the
>> > protocol specs.
>> * each protocol spec will add a statement clarifying that a
>> > given Admission Priority is to be encoded with the same
>> > value in each of the three protocol spec. For example, in
>> > tsvwg-emergency-rsvp, under section 3.1. we will add:
>> " A given Admission Priority is encoded in this information
>> > element using the same value as when encoded in the
>> > Admission Priority parameter defined in section 6.2.9 of
>> > [nsis-qspec], or in the Admission Priority parameter
>> > defined in section 4.10 of [dime-qos-parameters].
>> > In other words, a given value in any of the
>> > [emergency-rsvp] Admission Priority information element,
>> > the [nsis-qspec] Admission Priority parameter or the
>> > [dime-qos-parameters] Admission Priority parameter,
>> > refers to the same Admission Priority.
>> The above proposed paragraph is really unclear.  Which draft is =20
>> setting up IANA Registries to assign Admission Priority =20
>> parameters?  The way it reads it sounds like all three drafts are =20
>> setting up registries but that somehow (magically) all refer "to =20
>> the same Admission Priority".  How can that be if they assign =20
>> different values?  Right now emergency-rsvp and nsis-qspec set up =20
>> registries for Admission Priority and dime-qos-parameters is using =20=

>> the nsis-qspec registry as I recall.
>>
>> Please clarify the proposal as to which draft is setting up a =20
>> registry for Admission Priority.
>
> No registry is setup.
> It is up to a network administrator to decide how many/which =20
> admission priority gets used for what. This is similar to how =20
> Preemption is used (ie each network administrator may decide to use =20=

> it or not, may decide to use 2,3,4,...128,.. levels...).
> The statement above only says that the the same value of admission =20
> priority should be used in the three protocols to refer to same =20
> level of admission priority.
>
> Cheers
>
> Francois
>
>
>> Also, please provide clearer proposed text to include in the drafts.
>>
>> It would be good to see some discussion of the proposal on the =20
>> list, to confirm and validate agreement of the WG.
>>
>> Jerry
>>
>>
>> Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:
>> Hello,
>>
>> For memory, the next rev of nsis-qspec is also expected to be aligned
>> with the Resolution of the issue related to QoS Parameters encoding
>> in , & . For
>> convenience, I included below the recap on the corresponding
>> resolution as announced on NSIS, DIME and TSVWG lists.
>>
>> Just to make sure this does not fall through the cracks.
>>
>> Cheers
>>
>> Francois
>>
>>
>> >
>> > Begin forwarded message:
>> >> From: Francois Le Faucheur IMAP
>> >> Date: 3 December 2007 12:05:42 GMT+01:00
>> >> To: dime@ietf.org, nsis@ietf.org, tsvwg tsvwg
>> >> Cc: Francois Le Faucheur IMAP , David Oran R
>> >> , Hannes Tschofenig ,
>> >> ken carlberg , Magnus Westerlund
>> >> , James Polk ,
>> >> cornelia.kappler@nsn.com, "(IJ/ETH) B=E1der Attila"
>> >> , jouni.korhonen@teliasonera.com, Jukka
>> >> Manner MJ , tsvwg chair
>> >> chairs@tools.ietf.org>, nsis-chairs@tools.ietf.org, dime-
>> >> chairs@tools.ietf.org, "john.loughney@nokia.com>"
>> >>
>> >> Subject: Resolution of issue QoS Parameters encoding in
>> >> parameters>, &
>> >>
>> >> Hello,
>> >>
>> >> The Issue:
>> >> =3D=3D=3D=3D=3D=3D=3D
>> >> Three different documents (dime-qos-parameters, nsis-qos-nslp,
>> >> tsvwg-emergency-rsvp) need to convey an overlapping set of QoS
>> >> parameters (specifically RPH-Priority and Admission Priority) and
>> >> currently do that in an inconsistent manner. This has been brought
>> >> up and partially discussed on the WG mailing lists.
>> >>
>> >> The Proposed Resolution
>> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> >> Co-authors of the three I-Ds as well as WG chairs of the
>> >> corresponding WGs converged on the following proposed resolution.
>> >> Please let us know if you have an issue/concern with this.
>> >>
>> >> o Regarding RPH-Priority:
>> >> * tsvwg-emergency-rsvp will go ahead with its requests to IANA to
>> >> provide numerical registry for RPH priority (via extending
>> >> existing RPH registry). See IANA Considerations section of tsvwg-
>> >> emergency-rsvp.
>> >> * nsis-qspec (in section 6.2.10) will point to this registry
>> >> instead of defining its own values
>> >> * dime-qos-parameters (in section 4.11) will point to this
>> >> registry instead of defining its own values
>> >> * tsvwg-emergency-rsvp (in section 3.2) will keep pointing to
>> >> this registry.
>> >>
>> >> o Regarding Admission Priority:
>> >> * every protocol spec will only indicate that "higher value means
>> >> higher priority".
>> >> * there is no attempt to define what specific values should be
>> >> used for what. this is left outside the scope of the protocol =20
>> specs.
>> >> * each protocol spec will add a statement clarifying that a given
>> >> Admission Priority is to be encoded with the same value in each of
>> >> the three protocol spec. For example, in tsvwg-emergency-rsvp,
>> >> under section 3.1. we will add:
>> >> " A given Admission Priority is encoded in this information
>> >> element
>> >> using the same value as when encoded in the Admission Priority
>> >> parameter defined in section 6.2.9 of [nsis-qspec], or in the
>> >> Admission
>> >> Priority parameter defined in section 4.10 of [dime-qos-
>> >> parameters].
>> >> In other words, a given value in any of the [emergency-rsvp]
>> >> Admission
>> >> Priority information element, the [nsis-qspec] Admission Priority
>> >> parameter
>> >> or the [dime-qos-parameters] Admission Priority parameter, =20
>> refers to
>> >> the same Admission Priority.
>> >> "
>> >> * the mirror statement will be added in nsis-qspec (section
>> >> 6.2.9) and dime-qos-parameters (section 4.10)
>> >>
>> >> Francois
>> >>
>>
>>
>>
>>
>>
>>
>> Looking for last minute shopping deals? Find them fast with Yahoo! =20=

>> Search.
>
>
>
> Be a better friend, newshound, and know-it-all with Yahoo! Mobile. =20
> Try it now.


--Apple-Mail-19--86644756
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
Hello Percy,<div><br class=3D"webkit-block-placeholder"></div><div>Some =
of the considerations that led to the decision to not re-specify in =
&lt;emergency-rsvp&gt;, &lt;dime-qos-parameters&gt; and =
&lt;nsis-qspec&gt; the admission priority values that are already =
specified in Y.2171 specs included:</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>* they =
are already defined in this ITU spec</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>* if one =
wants to comply with the ITU way to do Admission Priority they can =
follow the ITU spec</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>* it is not 100% obvious that =
absolutely every network administrator will ever want to implement =
admission priority exactly as specified by ITU and by that particular =
spec. Maybe one=A0administrator=A0will want to use less priorities, =
maybe one will want to use more...</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>* the =
admission mechanism to be defined by IETF should be flexible and not =
tied to one single application of one single SDO.<br =
class=3D"webkit-block-placeholder"></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>* the =
admission priority mechanism defined in IETF should allow support of a =
particular application of a particular SDO. This can be achieved by =
deliberate choice of a network administrator to use=A0the=A0values of =
that application/SDO (but we don't have to mandate that everybody using =
the=A0admission=A0priority mechanisms use it in the same way)=A0<br =
class=3D"webkit-block-placeholder"></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>* this is =
the approach already used for the "Preemption" mechanism supported by =
NSIS and RSVP (ie it is up to network administrator to decide which =
preemption priority value to use in their network and their semantic is =
not defined in the documents)<br =
class=3D"webkit-block-placeholder"></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>* as a =
side practical considerations: it is undesirable to have an IETF spec =
tied to specifications of another body (eg what happens if ITU defines =
Y.2171bis with one more value? do we have to immediately reissue =
&lt;emergency-rsvp&gt;, &lt;dime-qos-parameters&gt; and =
&lt;nsis-qspec&gt;)? For example, if those documents would have mandated =
the ITU values and have been standardised in 2006, =
they=A0would=A0have=A0referred=A0to Y.1571 (as I think Qspec used to do =
before Y.1571 got superseded by Y.2171...)</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Cheers</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Francois</div><div><br><div>=
<div>On 22 Feb 2008, at 19:05, TARAPORE, PERCY S, ATTLABS =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">  <div dir=3D"ltr" align=3D"left"><span =
class=3D"005322817-22022008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">The purpose and intent for Y.2171 was to=A0standardize a set =
of admission control priority levels<span =
class=3D"090300318-22022008">=A0</span>that can be recognized=A0across =
multiple admin domains - and acted upon appropriately to provide the =
necessary CAC within each domain. Further, Priority Level 1 - the =
highest CAC priority - is exclusively reserved for emergency =
telecommunications in Y.2171. Thus retaining these in the NSIS-QSPEC is =
appropriate. They should not be changed or removed.</font></span></div> =
<div dir=3D"ltr" align=3D"left"><span class=3D"005322817-22022008"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>=A0</div> <div =
dir=3D"ltr" align=3D"left"><span class=3D"005322817-22022008"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2">Percy S. =
Tarapore</font></span></div><br> <div class=3D"OutlookMessageHeader" =
lang=3D"en-us" dir=3D"ltr" align=3D"left"> <hr tabindex=3D"-1"> <font =
face=3D"Tahoma" size=3D"2"><b>From:</b> nsis-bounces@ietf.org [<a =
href=3D"mailto:nsis-bounces@ietf.org">mailto:nsis-bounces@ietf.org</a>] =
<b>On Behalf Of </b>Gerald Ash<br><b>Sent:</b> Thursday, February 21, =
2008 11:56 AM<br><b>To:</b> Francois Le Faucheur IMAP; Martin =
Stiemerling; <a =
href=3D"mailto:john.loughney@nokia.com">john.loughney@nokia.com</a>; =
nsis<br><b>Cc:</b> <a =
href=3D"mailto:cornelia.kappler@googlemail.com">cornelia.kappler@googlemai=
l.com</a><br><b>Subject:</b> Re: [NSIS] Review of =
draft-ietf-nsis-qspec-18.txt<br></font><br></div> <div></div> <div><font =
face=3D"arial">Francois, Martin, John, All,</font></div> <div><font =
face=3D"arial"></font>=A0</div> <div><font face=3D"arial"> <div><font =
face=3D"arial">&gt;&gt;&gt; o Regarding Admission =
Priority:<br>&gt;&gt;&gt; * every protocol spec will only indicate that =
"higher value</font></div> <div><font face=3D"arial">&gt;&gt;&gt;=A0means =
higher priority".</font></div> <div><font face=3D"arial">&gt;&gt;&gt; * =
there is no attempt to define what specific values should</font></div> =
<div><font face=3D"arial">&gt;&gt;&gt;=A0be used for what. this is left =
outside the scope of the</font></div> <div><font =
face=3D"arial">&gt;&gt;&gt;=A0protocol specs.<br>&gt;&gt;&gt; * each =
protocol spec will add a statement clarifying that a</font></div> =
<div><font face=3D"arial">&gt;&gt;&gt;=A0given Admission Priority is to =
be encoded with the same</font></div> <div><font =
face=3D"arial">&gt;&gt;&gt;=A0value in each of the three protocol spec. =
For example, in</font></div> <div><font =
face=3D"arial">&gt;&gt;&gt;=A0tsvwg-emergency-rsvp, under section 3.1. =
we will add:<br>&gt;&gt;&gt; " A given Admission Priority is encoded in =
this information</font></div> <div><font =
face=3D"arial">&gt;&gt;&gt;=A0element using the same value as when =
encoded in the</font></div> <div><font =
face=3D"arial">&gt;&gt;&gt;=A0Admission Priority parameter defined in =
section 6.2.9 of</font></div> <div><font =
face=3D"arial">&gt;&gt;&gt;=A0[nsis-qspec], or in the Admission Priority =
parameter</font></div> <div><font face=3D"arial">&gt;&gt;&gt;=A0defined =
in section 4.10 of [dime-qos-parameters].</font></div> <div><font =
face=3D"arial">&gt;&gt;&gt; In other words, a given value in any of =
the</font></div> <div><font face=3D"arial">&gt;&gt;&gt;=A0[emergency-rsvp]=
 Admission Priority information element,</font></div> <div><font =
face=3D"arial">&gt;&gt;&gt;=A0the [nsis-qspec] Admission Priority =
parameter or the</font></div> <div><font =
face=3D"arial">&gt;&gt;&gt;=A0[dime-qos-parameters] Admission Priority =
parameter,</font></div> <div><font face=3D"arial">&gt;&gt;&gt;=A0refers =
to the same Admission Priority.</font></div> <div><font =
face=3D"arial">=A0</font></div><font face=3D"arial"></font> <div><font =
face=3D"arial">&gt;&gt; The above proposed paragraph is really unclear.=A0=
 Which draft</font></div> <div><font face=3D"arial">&gt;&gt;=A0is =
setting up IANA Registries to assign Admission Priority</font></div> =
<div><font face=3D"arial">&gt;&gt;=A0parameters?=A0 The way it reads it =
sounds like all three drafts</font></div> <div><font =
face=3D"arial">&gt;&gt;=A0are setting up registries but that =
somehow=A0(magically) all=A0refer</font></div> <div><font =
face=3D"arial">&gt;&gt;=A0"to the same Admission Priority".=A0 How can =
that be if they</font></div> <div><font face=3D"arial">&gt;&gt;=A0assign =
different values?=A0 Right now emergency-rsvp and</font></div> =
<div><font face=3D"arial">&gt;&gt;=A0nsis-qspec set up registries for =
Admission Priority and</font></div> <div><font =
face=3D"arial">&gt;&gt;=A0dime-qos-parameters is using the nsis-qspec =
registry as I</font></div> <div><font =
face=3D"arial">&gt;&gt;=A0recall.</font></div> <div><font =
face=3D"arial">&gt;&gt;</font></div> <div><font face=3D"arial">&gt;&gt; =
Please clarify the proposal as to which draft is setting up =
a</font></div> <div><font face=3D"arial">&gt;&gt;=A0registry for =
Admission Priority.=A0</font></div> <div><font face=3D"arial"><br =
class=3D"webkit-block-placeholder"></font></div> <div><font =
face=3D"arial">&gt; No registry is setup.</font></div> <div><font =
face=3D"arial">&gt; It is up to a network administrator to decide how =
many/which</font></div> <div><font face=3D"arial">&gt;=A0admission =
priority gets used for what. This is similar to how</font></div> =
<div><font face=3D"arial">&gt;=A0Preemption is used (ie each network =
administrator may decide </font></div> <div><font face=3D"arial">&gt; to =
use it or not, may decide to use 2,3,4,...128,.. =
levels...).</font></div> <div><font face=3D"arial">&gt; The statement =
above only says that the the same value of </font></div> <div><font =
face=3D"arial">&gt; admission priority should be used in the three =
protocols to refer </font></div> <div><font face=3D"arial">&gt; to same =
level of admission priority.</font></div> <div><font color=3D"#0000ff" =
size=3D"2"></font>=A0</div> <div>That's a fundamental change to =
NSIS/QSPEC and does away with standardized Admission Priority values.=A0 =
QSPEC is following Y.1571 (now Y.2171 according to An Nguyen) in =
standardizing 3 priority levels to have end-to-end cross-domain =
significance.</div> <div>=A0</div> <div>If we elimate this =
standardization, as is proposed, then different admission priority =
values=A0can be=A0assigned in different Admin domains, and will=A0have =
no end-to-end significance.=A0 For example, Admin-domain 1, Admin-domain =
2, and Admin-domain 3 assign=A0admission priority=3D2,=A0=A0admission =
priority=3D4, admission priority=3D10 for the highest level priority, =
respectively.=A0 Admin-domain 1 and Admin-domain 2 try to initiate =
end-to-end flows via Admin-domain=A03 for a 'high priority' =
flow.=A0=A0However, Admin-domain 3 has no idea how to treat the flow =
admission priority since all 3 domains are using different encodings of =
high priority.</div> <div> <div>=A0</div> <div>Admission priority is not =
the same as preemption priority and should not be based on that =
model.</div> <div>=A0</div></div> <div>IMO we should retain the =
standardized admission priority levels based on Y.1571/Y.2171.=A0 =
Otherwise, how do we achieve end-to-end, cross-domain standardization of =
admission priority?=A0 In any case, we need to see some good =
justification for the change.</div> <div>=A0</div> <div> <div><font =
face=3D"arial">&gt;&gt; I saw no discussion of this proposed resolution =
on the NSIS list.=A0</font></div> <div><font face=3D"arial"><br =
class=3D"webkit-block-placeholder"></font></div> <div><font =
face=3D"arial">&gt; which is why we've been assuming there was no issue =
with it. </font></div> <div>=A0</div> <div>It isn't sufficient =
to=A0declare 'silence is agreement' on making such a fundamental =
change.=A0 People should weigh in *on the list* and give their=A0technical=
 justifications and confirm their agreement (or disagreement).</div> =
<div><font face=3D"arial"></font>=A0</div> <div><font =
face=3D"arial">&gt;&gt; Who were the QSPEC co-authors who worked with =
you on the</font></div> <div><font face=3D"arial">&gt;&gt;=A0proposed =
resolution?</font></div> <div><font face=3D"arial"><br =
class=3D"webkit-block-placeholder"></font></div> <div><font =
face=3D"arial">&gt; Attila, Cornelia and Dave Oran (+ NSIS WG =
chairs).</font></div> <div><font color=3D"#0000ff" =
size=3D"2"></font>=A0</div> <div>So far I've not been able to verify =
agreement from the QSPEC co-authors as yet.=A0 We saw no discussion of =
the issue on the list, and there needs to be some =
explanation/justification for the change.=A0 </div> <div>=A0</div> =
<div>Perhaps Francois could summarize the technical=A0discussion amonst =
the co-authors, and also state who explicitly agreed (as opposed to who =
had no comment or active participation in the discussion).=A0=A0</div> =
<div>=A0</div> <div>It would be good if the co-authors who =
participated=A0in the discussion of the 'proposed agreement' could weigh =
in on the list with their technical view.</div> <div>=A0</div> =
<div>Also, both NSIS chairs have said there is an agreement on the =
proposal, so perhaps they could weigh in on the list also with their =
technical view.</div> <div>=A0</div> =
<div>Jerry</div></div></font><br><br><b><i>Francois Le Faucheur IMAP =
&lt;<a =
href=3D"mailto:flefauch@cisco.com">flefauch@cisco.com</a>&gt;</i></b> =
wrote:</div> <blockquote class=3D"replbq" style=3D"PADDING-LEFT: 5px; =
MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hello   Jerry,   =
<div><br>  <div>  <div>On 20 Feb 2008, at 16:58, Gerald Ash =
wrote:</div><br class=3D"Apple-interchange-newline">  <blockquote =
type=3D"cite">    <div><font face=3D"Courier=0D
 New">Francois,</font></div>    <div><font face=3D"Courier =
New"></font>=A0</div>    <div><font face=3D"Courier New">In your =
"Proposed Resolution" posting to NSIS     on 3 December <a =
href=3D"http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html">h=
ttp://www.ietf.org/mail-archive/web/nsis/current/msg08155.html</a>=A0you =
    say:</font></div>    <div><font face=3D"Courier New"></font>=A0</div> =
   <div><font face=3D"Courier New">&gt; The Proposed Resolution<br>&gt;  =
   =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>&gt; =
Co-authors of the three I-Ds as well as WG     chairs of the =
</font></div>    <div><font face=3D"Courier New">&gt; corresponding WGs =
converged on the     following proposed </font></div>    <div><font =
face=3D"Courier New">&gt; resolution. </font></div>    <div><font =
face=3D"Courier New"></font>=A0</div>    <div><font face=3D"Courier =
New">I saw no discussion of this proposed     resolution on the NSIS =
list.=A0</font></div></blockquote>  <div><br =
class=3D"webkit-block-placeholder"></div>  <div>which is why we've been =
assuming there was no issue with it. =A0</div>  <div><br =
class=3D"webkit-block-placeholder"></div><br>  <blockquote type=3D"cite"> =
   <div><font face=3D"Courier New">Who were the QSPEC co-authors who =
worked with     you on the proposed =
resolution?</font></div></blockquote>  <div><br =
class=3D"webkit-block-placeholder"></div>  <div>Attila, Cornelia and =
Dave Oran (+ NSIS WG chairs).</div>  <div><br></div><br>  <blockquote =
type=3D"cite">    <div>=A0</div>    <div><font face=3D"Courier New">&gt; =
o Regarding RPH-Priority:<br>&gt; *     tsvwg-emergency-rsvp will go =
ahead with its requests to</font></div>    <div><font face=3D"Courier =
New">&gt;=A0IANA </font><font face=3D"Courier New">to provide numerical =
registry for RPH priority (via     </font></div>    <div><font =
face=3D"Courier New">&gt; extending existing RPH registry). See     IANA =
Considerations</font></div>    <div><font face=3D"Courier =
New">&gt;=A0section of     tsvwg-emergency-rsvp.</font></div>    =
<div><font face=3D"Courier New">&gt; * nsis-qspec (in section 6.2.10) =
will     point to this registry</font></div>    <div><font face=3D"Courier=
 New">&gt;=A0instead of defining its own     values</font></div>    =
<div><font face=3D"Courier New"></font>=A0</div>    <div><font =
face=3D"Courier New">OK.</font></div>    <div><font face=3D"Courier =
New"></font>=A0</div>    <div><font face=3D"Courier New">&gt; o =
Regarding Admission Priority:<br>&gt; *     every protocol spec will =
only indicate that "higher value</font></div>    <div><font =
face=3D"Courier New">&gt;=A0means higher priority".</font></div>    =
<div><font face=3D"Courier New">&gt; * there is no attempt to define =
what     specific values should</font></div>    <div><font face=3D"Courier=
 New">&gt;=A0be used for what. this is left     outside the scope of =
the</font></div>    <div><font face=3D"Courier New">&gt;=A0protocol =
specs.<br>* each protocol     spec will add a statement clarifying that =
a</font></div>    <div><font face=3D"Courier New">&gt;=A0given Admission =
Priority is to be     encoded with the same</font></div>    <div><font =
face=3D"Courier New">&gt;=A0value in each of the three protocol     =
spec. For example, in</font></div>    <div><font face=3D"Courier =
New">&gt;=A0tsvwg-emergency-rsvp, under section     3.1. we will =
add:<br>" A given Admission Priority is encoded in this     =
information</font></div>    <div><font face=3D"Courier New">&gt;=A0element=
 using the same value as when     encoded in the</font></div>    =
<div><font face=3D"Courier New">&gt;=A0Admission Priority parameter =
defined     in section 6.2.9 of</font></div>    <div><font face=3D"Courier=
 New">&gt;=A0[nsis-qspec], or in the Admission     Priority =
parameter</font></div>    <div><font face=3D"Courier New">&gt;=A0defined =
in section 4.10 of     [dime-qos-parameters].</font></div>    <div><font =
face=3D"Courier New">&gt; In other words, a given value in any of     =
the</font></div>    <div><font face=3D"Courier =
New">&gt;=A0[emergency-rsvp] Admission Priority     information =
element,</font></div>    <div><font face=3D"Courier New">&gt;=A0the =
[nsis-qspec] Admission Priority     parameter or the</font></div>    =
<div><font face=3D"Courier New">&gt;=A0[dime-qos-parameters] Admission   =
  Priority parameter,</font></div>    <div><font face=3D"Courier =
New">&gt;=A0refers to the same Admission     Priority.<br></font></div>  =
  <div><font face=3D"Courier New">The above proposed paragraph is really =
    unclear.=A0 Which draft=A0is setting up IANA Registries to assign    =
 Admission Priority parameters?=A0 The way it reads it sounds like all   =
  three drafts are setting up registries but that somehow=A0(magically)  =
   all=A0refer "to the same Admission Priority".=A0 How can that be if   =
  they assign different values?=A0 Right now emergency-rsvp and =
nsis-qspec     set up registries for Admission Priority and =
dime-qos-parameters is using     the nsis-qspec registry as I =
recall.</font></div>    <div><font face=3D"Courier New"></font>=A0</div> =
   <div><font face=3D"Courier New">Please clarify the proposal as to =
which draft     is setting up a registry for Admission   =
Priority.=A0</font></div></blockquote>  <div><br =
class=3D"webkit-block-placeholder"></div>  <div>No registry is =
setup.</div>  <div>It is up to a network administrator to decide how =
many/which admission   priority gets used for what. This is similar to =
how Preemption is used (ie   each network administrator may decide to =
use it or not, may decide to use   2,3,4,...128,.. levels...).</div>  =
<div>The statement above only says that the the same value of admission  =
 priority should be used in the three protocols to refer to same level =
of   admission priority.</div>  <div><br =
class=3D"webkit-block-placeholder"></div>  <div>Cheers</div>  <div><br =
class=3D"webkit-block-placeholder"></div>  <div>Francois</div>  <div><br =
class=3D"webkit-block-placeholder"></div><br>  <blockquote type=3D"cite"> =
   <div><font face=3D"Courier New">Also, please provide clearer=A0proposed=
     text to include in the drafts.=A0 </font></div>    <div><font =
face=3D"Courier New"></font>=A0</div>    <div><font face=3D"Courier =
New">It would be good to see some discussion of the     proposal on the =
list, to confirm and validate agreement of the     WG.</font></div>    =
<div><font face=3D"Courier New"></font>=A0</div>    <div><font =
face=3D"Courier New">Jerry</font></div><font face=3D"Courier =
New"></font>    <div><br><br><b><i>Francois Le Faucheur IMAP &lt;<a =
href=3D"mailto:flefauch@cisco.com">flefauch@cisco.com</a>&gt;</i></b>    =
 wrote:</div>    <blockquote class=3D"replbq" style=3D"PADDING-LEFT: =
5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hello,<br><br>For =
      memory, the next rev of nsis-qspec is also expected to be aligned =
<br>with       the Resolution of the issue related to QoS Parameters =
encoding <br>in       <dime-qos-parameters>, <nsis-qspec>&amp; =
<tsvwg-emeregncy-rsvp>. For       <br>convenience, I included below the =
recap on the corresponding       <br>resolution as announced on NSIS, =
DIME and TSVWG lists.<br><br>Just to       make sure this does not fall =
through the       =
cracks.<br><br>Cheers<br><br>Francois<br><br><br>&gt;<br>&gt; Begin      =
 forwarded message:<br>&gt;&gt; From: Francois Le Faucheur IMAP       =
<flefauch@cisco.com><br>&gt;&gt; Date: 3 December 2007 12:05:42       =
GMT+01:00<br>&gt;&gt; To: <a =
href=3D"mailto:dime@ietf.org">dime@ietf.org</a>, <a =
href=3D"mailto:nsis@ietf.org">nsis@ietf.org</a>, tsvwg tsvwg       =
<tsvwg@ietf.org><br>&gt;&gt; Cc: Francois Le Faucheur IMAP       =
<flefauch@cisco.com>, David Oran R <br>&gt;&gt; <oran@cisco.com>, Hannes =
      Tschofenig <hannes.tschofenig@gmx.net>, <br>&gt;&gt; ken carlberg  =
     <carlberg@g11.org.uk>, Magnus Westerlund <br>&gt;&gt;       =
<magnus.westerlund@ericsson.com>, James Polk <jmpolk@cisco.com>,       =
<br>&gt;&gt; <a =
href=3D"mailto:cornelia.kappler@nsn.com">cornelia.kappler@nsn.com</a>,   =
    "(IJ/ETH) B=E1der Attila" <br>&gt;&gt; <attila.bader@ericsson.com>, =
<a =
href=3D"mailto:jouni.korhonen@teliasonera.com">jouni.korhonen@teliasonera.=
com</a>,       Jukka <br>&gt;&gt; Manner MJ <jmanner@cs.helsinki.fi>, =
tsvwg chair       <tsvwg-><br>&gt;&gt; <a =
href=3D"mailto:chairs@tools.ietf.org">chairs@tools.ietf.org</a>&gt;, <a =
href=3D"mailto:nsis-chairs@tools.ietf.org">nsis-chairs@tools.ietf.org</a>,=
       dime- <br>&gt;&gt; <a =
href=3D"mailto:chairs@tools.ietf.org">chairs@tools.ietf.org</a>, "<a =
href=3D"mailto:john.loughney@nokia.com">john.loughney@nokia.com</a>&gt;" =
      <br>&gt;&gt; <john.loughney@nokia.com><br>&gt;&gt; Subject: =
Resolution of       issue QoS Parameters encoding in =
<dime-qos-><br>&gt;&gt; parameters&gt;,       <nsis-qspec>&amp; =
<tsvwg-emeregncy-rsvp><br>&gt;&gt;<br>&gt;&gt;       =
Hello,<br>&gt;&gt;<br>&gt;&gt; The Issue:<br>&gt;&gt; =
=3D=3D=3D=3D=3D=3D=3D<br>&gt;&gt;       Three different documents =
(dime-qos-parameters, nsis-qos-nslp,       <br>&gt;&gt; =
tsvwg-emergency-rsvp) need to convey an overlapping set of       QoS =
<br>&gt;&gt; parameters (specifically RPH-Priority and Admission       =
Priority) and <br>&gt;&gt; currently do that in an inconsistent manner.  =
     This has been brought <br>&gt;&gt; up and partially discussed on =
the WG       mailing lists.<br>&gt;&gt;<br>&gt;&gt; The Proposed =
Resolution<br>&gt;&gt;       =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>&gt;&gt; Co-authors of the three I-Ds as well as WG      =
 chairs of the <br>&gt;&gt; corresponding WGs converged on the following =
      proposed resolution. <br>&gt;&gt; Please let us know if you have =
an       issue/concern with this.<br>&gt;&gt;<br>&gt;&gt; o Regarding    =
   RPH-Priority:<br>&gt;&gt; * tsvwg-emergency-rsvp will go ahead with =
its       requests to IANA to <br>&gt;&gt; provide numerical registry =
for RPH       priority (via extending <br>&gt;&gt; existing RPH =
registry). See IANA       Considerations section of tsvwg- <br>&gt;&gt; =
emergency-rsvp.<br>&gt;&gt;       * nsis-qspec (in section 6.2.10) will =
point to this registry <br>&gt;&gt;       instead of defining its own =
values<br>&gt;&gt; * dime-qos-parameters (in       section 4.11) will =
point to this <br>&gt;&gt; registry instead of defining       its own =
values<br>&gt;&gt; * tsvwg-emergency-rsvp (in section 3.2) will       =
keep pointing to <br>&gt;&gt; this registry.<br>&gt;&gt;<br>&gt;&gt; o   =
    Regarding Admission Priority:<br>&gt;&gt; * every protocol spec will =
only       indicate that "higher value means <br>&gt;&gt; higher       =
priority".<br>&gt;&gt; * there is no attempt to define what specific     =
  values should be <br>&gt;&gt; used for what. this is left outside the  =
     scope of the protocol specs.<br>&gt;&gt; * each protocol spec will =
add a       statement clarifying that a given <br>&gt;&gt; Admission =
Priority is to be       encoded with the same value in each of =
<br>&gt;&gt; the three protocol       spec. For example, in =
tsvwg-emergency-rsvp, <br>&gt;&gt; under section       3.1. we will =
add:<br>&gt;&gt; " A given Admission Priority is encoded in       this =
information <br>&gt;&gt; element<br>&gt;&gt; using the same value as     =
  when encoded in the Admission Priority<br>&gt;&gt; parameter defined =
in       section 6.2.9 of [nsis-qspec], or in the <br>&gt;&gt;       =
Admission<br>&gt;&gt; Priority parameter defined in section 4.10 of      =
 [dime-qos- <br>&gt;&gt; parameters].<br>&gt;&gt; In other words, a =
given       value in any of the [emergency-rsvp] <br>&gt;&gt; =
Admission<br>&gt;&gt;       Priority information element, the =
[nsis-qspec] Admission Priority       <br>&gt;&gt; parameter<br>&gt;&gt; =
or the [dime-qos-parameters] Admission       Priority parameter, refers =
to<br>&gt;&gt; the same Admission       Priority.<br>&gt;&gt; =
"<br>&gt;&gt; * the mirror statement will be added       in nsis-qspec =
(section <br>&gt;&gt; 6.2.9) and dime-qos-parameters       (section =
4.10)<br>&gt;&gt;<br>&gt;&gt;       =
Francois<br>&gt;&gt;<br><br><br><br><br></tsvwg-emeregncy-rsvp></nsis-qspe=
c></dime-qos-></john.loughney@nokia.com></tsvwg-></jmanner@cs.helsinki.fi>=
</attila.bader@ericsson.com></jmpolk@cisco.com></magnus.westerlund@ericsso=
n.com></carlberg@g11.org.uk></hannes.tschofenig@gmx.net></oran@cisco.com><=
/flefauch@cisco.com></tsvwg@ietf.org></flefauch@cisco.com></tsvwg-emeregnc=
y-rsvp></nsis-qspec></dime-qos-parameters></blockquote><br>    <div><br =
class=3D"khtml-block-placeholder"></div>    <hr size=3D"1">    Looking =
for last minute shopping deals? <a =
href=3D"http://us.rd.yahoo.com/evt=3D51734/*http://tools.search.yahoo.com/=
newsearch/category.php?category=3Dshopping">Find     them fast with =
Yahoo! Search.</a></blockquote></div><br></div></blockquote><br><div> =
<br class=3D"khtml-block-placeholder"></div><hr size=3D"1"> Be a better =
friend, newshound, and know-it-all with Yahoo! Mobile. <a =
href=3D"http://us.rd.yahoo.com/evt=3D51733/*http://mobile.yahoo.com/;_ylt=3D=
Ahu06i62sR8HDtDypao8Wcj9tAcJ ">Try it now.</a> =
</blockquote></div><br></div></body></html>=

--Apple-Mail-19--86644756--

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

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

--===============0405226331==--


From nsis-bounces@ietf.org  Fri Feb 22 13:04:47 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C9F0228C3FD;
	Fri, 22 Feb 2008 13:04:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.036
X-Spam-Level: 
X-Spam-Status: No, score=-99.036 tagged_above=-999 required=5
	tests=[AWL=-0.711, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=1,
	MIME_HTML_MOSTLY=0.001, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id yxH2mTPuDUdN; Fri, 22 Feb 2008 13:04:44 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E167728C2C0;
	Fri, 22 Feb 2008 13:04:44 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6574B28C2C0
	for <nsis@core3.amsl.com>; Fri, 22 Feb 2008 13:04:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 FlNxL1Jd6cwT for <nsis@core3.amsl.com>;
	Fri, 22 Feb 2008 13:04:41 -0800 (PST)
Received: from mail120.messagelabs.com (mail120.messagelabs.com
	[216.82.250.83])
	by core3.amsl.com (Postfix) with ESMTP id 3FC2328C199
	for <nsis@ietf.org>; Fri, 22 Feb 2008 13:04:41 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: tarapore@att.com
X-Msg-Ref: server-8.tower-120.messagelabs.com!1203714274!27102779!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 8784 invoked from network); 22 Feb 2008 21:04:34 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com)
	(144.160.20.54)
	by server-8.tower-120.messagelabs.com with AES256-SHA encrypted SMTP;
	22 Feb 2008 21:04:34 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m1ML4XFU014058; Fri, 22 Feb 2008 16:04:34 -0500
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m1ML4Vpp014037; Fri, 22 Feb 2008 16:04:31 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 22 Feb 2008 15:04:30 -0600
Message-ID: <A1F50CB516D211409DFD05D6B3CE6D300CD2B731@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <5D6F2B15-4E24-4FFF-8EFF-D3B7DB99F751@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Review of draft-ietf-nsis-qspec-18.txt
Thread-Index: Ach1hBs8yvpYIiTlSJeHbqjulTT3GAADpn9Q
References: <4EFF5784-4564-4730-A5C1-CD0477DE740A@cisco.com>
	<505424.79660.qm@web63613.mail.re1.yahoo.com>
	<A1F50CB516D211409DFD05D6B3CE6D300CD2B729@KCCLUST06EVS1.ugd.att.com>
	<A1F50CB516D211409DFD05D6B3CE6D300CD2B72D@KCCLUST06EVS1.ugd.att.com>
	<5D6F2B15-4E24-4FFF-8EFF-D3B7DB99F751@cisco.com>
From: "TARAPORE, PERCY S, ATTLABS" <tarapore@att.com>
To: "Francois Le Faucheur IMAP" <flefauch@cisco.com>
Cc: john.loughney@nokia.com, nsis <nsis@ietf.org>
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0518200029=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0518200029==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C87596.849548EF"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C87596.849548EF
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Francois,
=20
If it is undesirable to tie in to specs from another SDO, then should we =
completely abandon all other efforts that are related? For example, =
should we drop the tie-in to Y.1541-QSPEC that NSIS is also working on?
=20
Can you demonstrate how domain-specific priority assignments could =
possibly work? See Jerry's statement from the e-mail thread:
=20
"...If we eliminate this standardization, as is proposed, then different =
admission priority values can be assigned in different Admin domains, =
and will have no end-to-end significance.  For example, Admin-domain 1, =
Admin-domain 2, and Admin-domain 3 assign admission priority=3D2,  =
admission priority=3D4, admission priority=3D10 for the highest level =
priority, respectively.  Admin-domain 1 and Admin-domain 2 try to =
initiate end-to-end flows via Admin-domain 3 for a 'high priority' flow. =
 However, Admin-domain 3 has no idea how to treat the flow admission =
priority since all 3 domains are using different encodings of high =
priority...."
=20
Can you please indicate how this situation could be resolved without an =
accepted standardized set of priority levels that can be exchanged =
across domains?=20
=20
It is also my understanding that there really is no major issue in =
changing an IETF spec that is tied to an ITU-T spec. If for example, =
Y.2171 is updated some time in the future to add a 4th priority level, =
then IANA can accommodate this by an appropriate change in NSIS-QSPEC. =
Jerry can you please confirm this?
=20
I still do not see any merit in removing Y.2171 priority levels from =
NSIS-QSPEC.
=20
Thanks
=20
Percy

________________________________

From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com]=20
Sent: Friday, February 22, 2008 1:52 PM
To: TARAPORE, PERCY S, ATTLABS
Cc: Francois Le Faucheur IMAP; Gerald Ash; Martin Stiemerling; =
john.loughney@nokia.com; nsis
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.txt


Hello Percy,=20

Some of the considerations that led to the decision to not re-specify in =
<emergency-rsvp>, <dime-qos-parameters> and <nsis-qspec> the admission =
priority values that are already specified in Y.2171 specs included:
* they are already defined in this ITU spec
* if one wants to comply with the ITU way to do Admission Priority they =
can follow the ITU spec
* it is not 100% obvious that absolutely every network administrator =
will ever want to implement admission priority exactly as specified by =
ITU and by that particular spec. Maybe one administrator will want to =
use less priorities, maybe one will want to use more...
* the admission mechanism to be defined by IETF should be flexible and =
not tied to one single application of one single SDO.

* the admission priority mechanism defined in IETF should allow support =
of a particular application of a particular SDO. This can be achieved by =
deliberate choice of a network administrator to use the values of that =
application/SDO (but we don't have to mandate that everybody using the =
admission priority mechanisms use it in the same way)=20

* this is the approach already used for the "Preemption" mechanism =
supported by NSIS and RSVP (ie it is up to network administrator to =
decide which preemption priority value to use in their network and their =
semantic is not defined in the documents)

* as a side practical considerations: it is undesirable to have an IETF =
spec tied to specifications of another body (eg what happens if ITU =
defines Y.2171bis with one more value? do we have to immediately reissue =
<emergency-rsvp>, <dime-qos-parameters> and <nsis-qspec>)? For example, =
if those documents would have mandated the ITU values and have been =
standardised in 2006, they would have referred to Y.1571 (as I think =
Qspec used to do before Y.1571 got superseded by Y.2171...)

Cheers

Francois

On 22 Feb 2008, at 19:05, TARAPORE, PERCY S, ATTLABS wrote:


	The purpose and intent for Y.2171 was to standardize a set of admission =
control priority levels that can be recognized across multiple admin =
domains - and acted upon appropriately to provide the necessary CAC =
within each domain. Further, Priority Level 1 - the highest CAC priority =
- is exclusively reserved for emergency telecommunications in Y.2171. =
Thus retaining these in the NSIS-QSPEC is appropriate. They should not =
be changed or removed.
	=20
	Percy S. Tarapore

________________________________

	From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On Behalf Of =
Gerald Ash
	Sent: Thursday, February 21, 2008 11:56 AM
	To: Francois Le Faucheur IMAP; Martin Stiemerling; =
john.loughney@nokia.com; nsis
	Cc: cornelia.kappler@googlemail.com
	Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.txt
=09
=09
	Francois, Martin, John, All,
	=20
=09
	>>> o Regarding Admission Priority:
	>>> * every protocol spec will only indicate that "higher value
	>>> means higher priority".
	>>> * there is no attempt to define what specific values should
	>>> be used for what. this is left outside the scope of the
	>>> protocol specs.
	>>> * each protocol spec will add a statement clarifying that a
	>>> given Admission Priority is to be encoded with the same
	>>> value in each of the three protocol spec. For example, in
	>>> tsvwg-emergency-rsvp, under section 3.1. we will add:
	>>> " A given Admission Priority is encoded in this information
	>>> element using the same value as when encoded in the
	>>> Admission Priority parameter defined in section 6.2.9 of
	>>> [nsis-qspec], or in the Admission Priority parameter
	>>> defined in section 4.10 of [dime-qos-parameters].
	>>> In other words, a given value in any of the
	>>> [emergency-rsvp] Admission Priority information element,
	>>> the [nsis-qspec] Admission Priority parameter or the
	>>> [dime-qos-parameters] Admission Priority parameter,
	>>> refers to the same Admission Priority.
	=20
=09
	>> The above proposed paragraph is really unclear.  Which draft
	>> is setting up IANA Registries to assign Admission Priority
	>> parameters?  The way it reads it sounds like all three drafts
	>> are setting up registries but that somehow (magically) all refer
	>> "to the same Admission Priority".  How can that be if they
	>> assign different values?  Right now emergency-rsvp and
	>> nsis-qspec set up registries for Admission Priority and
	>> dime-qos-parameters is using the nsis-qspec registry as I
	>> recall.
	>>
	>> Please clarify the proposal as to which draft is setting up a
	>> registry for Admission Priority.=20
=09
=09
	> No registry is setup.
	> It is up to a network administrator to decide how many/which
	> admission priority gets used for what. This is similar to how
	> Preemption is used (ie each network administrator may decide=20
	> to use it or not, may decide to use 2,3,4,...128,.. levels...).
	> The statement above only says that the the same value of=20
	> admission priority should be used in the three protocols to refer=20
	> to same level of admission priority.
	=20
	That's a fundamental change to NSIS/QSPEC and does away with =
standardized Admission Priority values.  QSPEC is following Y.1571 (now =
Y.2171 according to An Nguyen) in standardizing 3 priority levels to =
have end-to-end cross-domain significance.
	=20
	If we elimate this standardization, as is proposed, then different =
admission priority values can be assigned in different Admin domains, =
and will have no end-to-end significance.  For example, Admin-domain 1, =
Admin-domain 2, and Admin-domain 3 assign admission priority=3D2,  =
admission priority=3D4, admission priority=3D10 for the highest level =
priority, respectively.  Admin-domain 1 and Admin-domain 2 try to =
initiate end-to-end flows via Admin-domain 3 for a 'high priority' flow. =
 However, Admin-domain 3 has no idea how to treat the flow admission =
priority since all 3 domains are using different encodings of high =
priority.
	=20
	Admission priority is not the same as preemption priority and should =
not be based on that model.
	=20
	IMO we should retain the standardized admission priority levels based =
on Y.1571/Y.2171.  Otherwise, how do we achieve end-to-end, cross-domain =
standardization of admission priority?  In any case, we need to see some =
good justification for the change.
	=20
	>> I saw no discussion of this proposed resolution on the NSIS list.=20
=09
=09
	> which is why we've been assuming there was no issue with it.=20
	=20
	It isn't sufficient to declare 'silence is agreement' on making such a =
fundamental change.  People should weigh in *on the list* and give their =
technical justifications and confirm their agreement (or disagreement).
	=20
	>> Who were the QSPEC co-authors who worked with you on the
	>> proposed resolution?
=09
=09
	> Attila, Cornelia and Dave Oran (+ NSIS WG chairs).
	=20
	So far I've not been able to verify agreement from the QSPEC co-authors =
as yet.  We saw no discussion of the issue on the list, and there needs =
to be some explanation/justification for the change. =20
	=20
	Perhaps Francois could summarize the technical discussion amonst the =
co-authors, and also state who explicitly agreed (as opposed to who had =
no comment or active participation in the discussion). =20
	=20
	It would be good if the co-authors who participated in the discussion =
of the 'proposed agreement' could weigh in on the list with their =
technical view.
	=20
	Also, both NSIS chairs have said there is an agreement on the proposal, =
so perhaps they could weigh in on the list also with their technical =
view.
	=20
	Jerry


	Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:

		Hello Jerry,=20

		On 20 Feb 2008, at 16:58, Gerald Ash wrote:


			Francois,
			=20
			In your "Proposed Resolution" posting to NSIS on 3 December =
http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html you say:
			=20
			> The Proposed Resolution
			> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
			> Co-authors of the three I-Ds as well as WG chairs of the=20
			> corresponding WGs converged on the following proposed=20
			> resolution.=20
			=20
			I saw no discussion of this proposed resolution on the NSIS list.=20


		which is why we've been assuming there was no issue with it. =20



			Who were the QSPEC co-authors who worked with you on the proposed =
resolution?


		Attila, Cornelia and Dave Oran (+ NSIS WG chairs).



			=20
			> o Regarding RPH-Priority:
			> * tsvwg-emergency-rsvp will go ahead with its requests to
			> IANA to provide numerical registry for RPH priority (via=20
			> extending existing RPH registry). See IANA Considerations
			> section of tsvwg-emergency-rsvp.
			> * nsis-qspec (in section 6.2.10) will point to this registry
			> instead of defining its own values
			=20
			OK.
			=20
			> o Regarding Admission Priority:
			> * every protocol spec will only indicate that "higher value
			> means higher priority".
			> * there is no attempt to define what specific values should
			> be used for what. this is left outside the scope of the
			> protocol specs.
			* each protocol spec will add a statement clarifying that a
			> given Admission Priority is to be encoded with the same
			> value in each of the three protocol spec. For example, in
			> tsvwg-emergency-rsvp, under section 3.1. we will add:
			" A given Admission Priority is encoded in this information
			> element using the same value as when encoded in the
			> Admission Priority parameter defined in section 6.2.9 of
			> [nsis-qspec], or in the Admission Priority parameter
			> defined in section 4.10 of [dime-qos-parameters].
			> In other words, a given value in any of the
			> [emergency-rsvp] Admission Priority information element,
			> the [nsis-qspec] Admission Priority parameter or the
			> [dime-qos-parameters] Admission Priority parameter,
			> refers to the same Admission Priority.
		=09
			The above proposed paragraph is really unclear.  Which draft is =
setting up IANA Registries to assign Admission Priority parameters?  The =
way it reads it sounds like all three drafts are setting up registries =
but that somehow (magically) all refer "to the same Admission Priority". =
 How can that be if they assign different values?  Right now =
emergency-rsvp and nsis-qspec set up registries for Admission Priority =
and dime-qos-parameters is using the nsis-qspec registry as I recall.
			=20
			Please clarify the proposal as to which draft is setting up a =
registry for Admission Priority.=20


		No registry is setup.
		It is up to a network administrator to decide how many/which admission =
priority gets used for what. This is similar to how Preemption is used =
(ie each network administrator may decide to use it or not, may decide =
to use 2,3,4,...128,.. levels...).
		The statement above only says that the the same value of admission =
priority should be used in the three protocols to refer to same level of =
admission priority.

		Cheers

		Francois



			Also, please provide clearer proposed text to include in the drafts.  =

			=20
			It would be good to see some discussion of the proposal on the list, =
to confirm and validate agreement of the WG.
			=20
			Jerry
		=09


			Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:

				Hello,
			=09
				For memory, the next rev of nsis-qspec is also expected to be =
aligned=20
				with the Resolution of the issue related to QoS Parameters encoding=20
				in , & . For=20
				convenience, I included below the recap on the corresponding=20
				resolution as announced on NSIS, DIME and TSVWG lists.
			=09
				Just to make sure this does not fall through the cracks.
			=09
				Cheers
			=09
				Francois
			=09
			=09
				>
				> Begin forwarded message:
				>> From: Francois Le Faucheur IMAP=20
				>> Date: 3 December 2007 12:05:42 GMT+01:00
				>> To: dime@ietf.org, nsis@ietf.org, tsvwg tsvwg=20
				>> Cc: Francois Le Faucheur IMAP , David Oran R=20
				>> , Hannes Tschofenig ,=20
				>> ken carlberg , Magnus Westerlund=20
				>> , James Polk ,=20
				>> cornelia.kappler@nsn.com, "(IJ/ETH) B=E1der Attila"=20
				>> , jouni.korhonen@teliasonera.com, Jukka=20
				>> Manner MJ , tsvwg chair=20
				>> chairs@tools.ietf.org>, nsis-chairs@tools.ietf.org, dime-=20
				>> chairs@tools.ietf.org, "john.loughney@nokia.com>"=20
				>>=20
				>> Subject: Resolution of issue QoS Parameters encoding in=20
				>> parameters>, &=20
				>>
				>> Hello,
				>>
				>> The Issue:
				>> =3D=3D=3D=3D=3D=3D=3D
				>> Three different documents (dime-qos-parameters, nsis-qos-nslp,=20
				>> tsvwg-emergency-rsvp) need to convey an overlapping set of QoS=20
				>> parameters (specifically RPH-Priority and Admission Priority) and =

				>> currently do that in an inconsistent manner. This has been =
brought=20
				>> up and partially discussed on the WG mailing lists.
				>>
				>> The Proposed Resolution
				>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
				>> Co-authors of the three I-Ds as well as WG chairs of the=20
				>> corresponding WGs converged on the following proposed resolution. =

				>> Please let us know if you have an issue/concern with this.
				>>
				>> o Regarding RPH-Priority:
				>> * tsvwg-emergency-rsvp will go ahead with its requests to IANA to =

				>> provide numerical registry for RPH priority (via extending=20
				>> existing RPH registry). See IANA Considerations section of tsvwg- =

				>> emergency-rsvp.
				>> * nsis-qspec (in section 6.2.10) will point to this registry=20
				>> instead of defining its own values
				>> * dime-qos-parameters (in section 4.11) will point to this=20
				>> registry instead of defining its own values
				>> * tsvwg-emergency-rsvp (in section 3.2) will keep pointing to=20
				>> this registry.
				>>
				>> o Regarding Admission Priority:
				>> * every protocol spec will only indicate that "higher value means =

				>> higher priority".
				>> * there is no attempt to define what specific values should be=20
				>> used for what. this is left outside the scope of the protocol =
specs.
				>> * each protocol spec will add a statement clarifying that a given =

				>> Admission Priority is to be encoded with the same value in each =
of=20
				>> the three protocol spec. For example, in tsvwg-emergency-rsvp,=20
				>> under section 3.1. we will add:
				>> " A given Admission Priority is encoded in this information=20
				>> element
				>> using the same value as when encoded in the Admission Priority
				>> parameter defined in section 6.2.9 of [nsis-qspec], or in the=20
				>> Admission
				>> Priority parameter defined in section 4.10 of [dime-qos-=20
				>> parameters].
				>> In other words, a given value in any of the [emergency-rsvp]=20
				>> Admission
				>> Priority information element, the [nsis-qspec] Admission Priority =

				>> parameter
				>> or the [dime-qos-parameters] Admission Priority parameter, refers =
to
				>> the same Admission Priority.
				>> "
				>> * the mirror statement will be added in nsis-qspec (section=20
				>> 6.2.9) and dime-qos-parameters (section 4.10)
				>>
				>> Francois
				>>
			=09
			=09
			=09
			=09
			=09



________________________________

			Looking for last minute shopping deals? Find them fast with Yahoo! =
Search. =
<http://us.rd.yahoo.com/evt=3D51734/*http://tools.search.yahoo.com/newsea=
rch/category.php?category=3Dshopping>=20




________________________________

	Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try =
it now. =
<http://us.rd.yahoo.com/evt=3D51733/*http://mobile.yahoo.com/;_ylt=3DAhu0=
6i62sR8HDtDypao8Wcj9tAcJ> =20



------_=_NextPart_001_01C87596.849548EF
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3268" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D941143720-22022008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Francois,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D941143720-22022008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D941143720-22022008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>If it is undesirable to tie in to specs from =
another SDO,=20
then should we completely abandon all other efforts that are related? =
For=20
example, should we drop the tie-in to Y.1541-QSPEC that NSIS is also =
working=20
on?</FONT></SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV><SPAN class=3D941143720-22022008></SPAN><FONT face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2>C<SPAN class=3D941143720-22022008>an you =
demonstrate=20
how domain-specific priority assignments could possibly work? See =
Jerry's=20
statement from the e-mail thread:</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D941143720-22022008></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT><FONT><SPAN class=3D941143720-22022008>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D941143720-22022008>"...</SPAN>If we eliminate this =
standardization, as is=20
proposed, then different admission priority values&nbsp;can =
be&nbsp;assigned in=20
different Admin domains, and will&nbsp;have no end-to-end =
significance.&nbsp;=20
For example, Admin-domain 1, Admin-domain 2, and Admin-domain 3=20
assign&nbsp;admission priority=3D2,&nbsp;&nbsp;admission priority=3D4, =
admission=20
priority=3D10 for the highest level priority, respectively.&nbsp; =
Admin-domain 1=20
and Admin-domain 2 try to initiate end-to-end flows via =
Admin-domain&nbsp;3 for=20
a 'high priority' flow.&nbsp;&nbsp;However, Admin-domain 3 has no idea =
how to=20
treat the flow admission priority since all 3 domains are using =
different=20
encodings of high priority.<SPAN=20
class=3D941143720-22022008>..."</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D941143720-22022008></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D941143720-22022008>Can you please indicate how this situation =
could be=20
resolved without an accepted standardized set of priority levels that =
can be=20
exchanged across domains? </SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D941143720-22022008></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D941143720-22022008>It is also my understanding that there really =
is no=20
major issue in changing an IETF spec that is tied to an ITU-T spec. If =
for=20
example, Y.2171 is updated some time in the future to add a 4th priority =
level,=20
then IANA can accommodate this by an appropriate change in NSIS-QSPEC. =
Jerry can=20
you please confirm this?</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D941143720-22022008></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D941143720-22022008>I still do not see any merit in removing =
Y.2171=20
priority levels from NSIS-QSPEC.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D941143720-22022008></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D941143720-22022008>Thanks</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D941143720-22022008></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D941143720-22022008>Percy</SPAN></FONT></FONT></FONT></DIV></SPAN>=
</FONT></FONT></DIV>
<DIV><BR></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Francois Le Faucheur IMAP=20
[mailto:flefauch@cisco.com] <BR><B>Sent:</B> Friday, February 22, 2008 =
1:52=20
PM<BR><B>To:</B> TARAPORE, PERCY S, ATTLABS<BR><B>Cc:</B> Francois Le =
Faucheur=20
IMAP; Gerald Ash; Martin Stiemerling; john.loughney@nokia.com;=20
nsis<BR><B>Subject:</B> Re: [NSIS] Review of=20
draft-ietf-nsis-qspec-18.txt<BR></FONT><BR></DIV>
<DIV></DIV>Hello Percy,
<DIV><BR class=3Dwebkit-block-placeholder></DIV>
<DIV>Some of the considerations that led to the decision to not =
re-specify in=20
&lt;emergency-rsvp&gt;, &lt;dime-qos-parameters&gt; and =
&lt;nsis-qspec&gt; the=20
admission priority values that are already specified in Y.2171 specs=20
included:</DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
they are=20
already defined in this ITU spec</DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* if =
one wants=20
to comply with the ITU way to do Admission Priority they can follow the =
ITU=20
spec</DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* it =
is not 100%=20
obvious that absolutely every network administrator will ever want to =
implement=20
admission priority exactly as specified by ITU and by that particular =
spec.=20
Maybe one&nbsp;administrator&nbsp;will want to use less priorities, =
maybe one=20
will want to use more...</DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
the admission=20
mechanism to be defined by IETF should be flexible and not tied to one =
single=20
application of one single SDO.<BR =
class=3Dwebkit-block-placeholder></DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
the admission=20
priority mechanism defined in IETF should allow support of a particular=20
application of a particular SDO. This can be achieved by deliberate =
choice of a=20
network administrator to use&nbsp;the&nbsp;values of that =
application/SDO (but=20
we don't have to mandate that everybody using =
the&nbsp;admission&nbsp;priority=20
mechanisms use it in the same way)&nbsp;<BR=20
class=3Dwebkit-block-placeholder></DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* =
this is the=20
approach already used for the "Preemption" mechanism supported by NSIS =
and RSVP=20
(ie it is up to network administrator to decide which preemption =
priority value=20
to use in their network and their semantic is not defined in the =
documents)<BR=20
class=3Dwebkit-block-placeholder></DIV>
<DIV><SPAN class=3DApple-tab-span style=3D"WHITE-SPACE: pre"></SPAN>* as =
a side=20
practical considerations: it is undesirable to have an IETF spec tied to =

specifications of another body (eg what happens if ITU defines Y.2171bis =
with=20
one more value? do we have to immediately reissue =
&lt;emergency-rsvp&gt;,=20
&lt;dime-qos-parameters&gt; and &lt;nsis-qspec&gt;)? For example, if =
those=20
documents would have mandated the ITU values and have been standardised =
in 2006,=20
they&nbsp;would&nbsp;have&nbsp;referred&nbsp;to Y.1571 (as I think Qspec =
used to=20
do before Y.1571 got superseded by Y.2171...)</DIV>
<DIV><BR class=3Dwebkit-block-placeholder></DIV>
<DIV>Cheers</DIV>
<DIV><BR class=3Dwebkit-block-placeholder></DIV>
<DIV>Francois</DIV>
<DIV><BR>
<DIV>
<DIV>On 22 Feb 2008, at 19:05, TARAPORE, PERCY S, ATTLABS =
wrote:</DIV><BR=20
class=3DApple-interchange-newline>
<BLOCKQUOTE type=3D"cite">
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D005322817-22022008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>The purpose and intent for Y.2171 was =
to&nbsp;standardize=20
  a set of admission control priority levels<SPAN=20
  class=3D090300318-22022008>&nbsp;</SPAN>that can be =
recognized&nbsp;across=20
  multiple admin domains - and acted upon appropriately to provide the =
necessary=20
  CAC within each domain. Further, Priority Level 1 - the highest CAC =
priority -=20
  is exclusively reserved for emergency telecommunications in Y.2171. =
Thus=20
  retaining these in the NSIS-QSPEC is appropriate. They should not be =
changed=20
  or removed.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D005322817-22022008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D005322817-22022008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Percy S. Tarapore</FONT></SPAN></DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> nsis-bounces@ietf.org [<A=20
  =
href=3D"mailto:nsis-bounces@ietf.org">mailto:nsis-bounces@ietf.org</A>] =
<B>On=20
  Behalf Of </B>Gerald Ash<BR><B>Sent:</B> Thursday, February 21, 2008 =
11:56=20
  AM<BR><B>To:</B> Francois Le Faucheur IMAP; Martin Stiemerling; <A=20
  href=3D"mailto:john.loughney@nokia.com">john.loughney@nokia.com</A>;=20
  nsis<BR><B>Cc:</B> <A=20
  =
href=3D"mailto:cornelia.kappler@googlemail.com">cornelia.kappler@googlema=
il.com</A><BR><B>Subject:</B>=20
  Re: [NSIS] Review of draft-ietf-nsis-qspec-18.txt<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3Darial>Francois, Martin, John, All,</FONT></DIV>
  <DIV><FONT face=3Darial></FONT>&nbsp;</DIV>
  <DIV><FONT face=3Darial>
  <DIV><FONT face=3Darial>&gt;&gt;&gt; o Regarding Admission=20
  Priority:<BR>&gt;&gt;&gt; * every protocol spec will only indicate =
that=20
  "higher value</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;means higher =
priority".</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt; * there is no attempt to define =
what=20
  specific values should</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;be used for what. this is =
left outside=20
  the scope of the</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;protocol =
specs.<BR>&gt;&gt;&gt; * each=20
  protocol spec will add a statement clarifying that a</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;given Admission Priority is =
to be=20
  encoded with the same</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;value in each of the three =
protocol=20
  spec. For example, in</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;tsvwg-emergency-rsvp, under =
section=20
  3.1. we will add:<BR>&gt;&gt;&gt; " A given Admission Priority is =
encoded in=20
  this information</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;element using the same value =
as when=20
  encoded in the</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;Admission Priority parameter =
defined=20
  in section 6.2.9 of</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;[nsis-qspec], or in the =
Admission=20
  Priority parameter</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;defined in section 4.10 of=20
  [dime-qos-parameters].</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt; In other words, a given value in =
any of=20
  the</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;[emergency-rsvp] Admission =
Priority=20
  information element,</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;the [nsis-qspec] Admission =
Priority=20
  parameter or the</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;[dime-qos-parameters] =
Admission=20
  Priority parameter,</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&gt;&nbsp;refers to the same Admission =

  Priority.</FONT></DIV>
  <DIV><FONT face=3Darial></FONT>&nbsp;</DIV><FONT face=3Darial></FONT>
  <DIV><FONT face=3Darial>&gt;&gt; The above proposed paragraph is =
really=20
  unclear.&nbsp; Which draft</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&nbsp;is setting up IANA Registries to =
assign=20
  Admission Priority</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&nbsp;parameters?&nbsp; The way it =
reads it=20
  sounds like all three drafts</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&nbsp;are setting up registries but =
that=20
  somehow&nbsp;(magically) all&nbsp;refer</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&nbsp;"to the same Admission =
Priority".&nbsp;=20
  How can that be if they</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&nbsp;assign different values?&nbsp; =
Right now=20
  emergency-rsvp and</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&nbsp;nsis-qspec set up registries for =
Admission=20
  Priority and</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&nbsp;dime-qos-parameters is using the =

  nsis-qspec registry as I</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&nbsp;recall.</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt; Please clarify the proposal as to =
which draft=20
  is setting up a</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&nbsp;registry for Admission=20
  Priority.&nbsp;</FONT></DIV>
  <DIV><FONT face=3Darial><BR =
class=3Dwebkit-block-placeholder></FONT></DIV>
  <DIV><FONT face=3Darial>&gt; No registry is setup.</FONT></DIV>
  <DIV><FONT face=3Darial>&gt; It is up to a network administrator to =
decide how=20
  many/which</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&nbsp;admission priority gets used for =
what. This is=20
  similar to how</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&nbsp;Preemption is used (ie each network=20
  administrator may decide </FONT></DIV>
  <DIV><FONT face=3Darial>&gt; to use it or not, may decide to use =
2,3,4,...128,..=20
  levels...).</FONT></DIV>
  <DIV><FONT face=3Darial>&gt; The statement above only says that the =
the same=20
  value of </FONT></DIV>
  <DIV><FONT face=3Darial>&gt; admission priority should be used in the =
three=20
  protocols to refer </FONT></DIV>
  <DIV><FONT face=3Darial>&gt; to same level of admission =
priority.</FONT></DIV>
  <DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
  <DIV>That's a fundamental change to NSIS/QSPEC and does away with =
standardized=20
  Admission Priority values.&nbsp; QSPEC is following Y.1571 (now Y.2171 =

  according to An Nguyen) in standardizing 3 priority levels to have =
end-to-end=20
  cross-domain significance.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>If we elimate this standardization, as is proposed, then =
different=20
  admission priority values&nbsp;can be&nbsp;assigned in different Admin =

  domains, and will&nbsp;have no end-to-end significance.&nbsp; For =
example,=20
  Admin-domain 1, Admin-domain 2, and Admin-domain 3 =
assign&nbsp;admission=20
  priority=3D2,&nbsp;&nbsp;admission priority=3D4, admission =
priority=3D10 for the=20
  highest level priority, respectively.&nbsp; Admin-domain 1 and =
Admin-domain 2=20
  try to initiate end-to-end flows via Admin-domain&nbsp;3 for a 'high =
priority'=20
  flow.&nbsp;&nbsp;However, Admin-domain 3 has no idea how to treat the =
flow=20
  admission priority since all 3 domains are using different encodings =
of high=20
  priority.</DIV>
  <DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Admission priority is not the same as preemption priority and =
should not=20
  be based on that model.</DIV>
  <DIV>&nbsp;</DIV></DIV>
  <DIV>IMO we should retain the standardized admission priority levels =
based on=20
  Y.1571/Y.2171.&nbsp; Otherwise, how do we achieve end-to-end, =
cross-domain=20
  standardization of admission priority?&nbsp; In any case, we need to =
see some=20
  good justification for the change.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>
  <DIV><FONT face=3Darial>&gt;&gt; I saw no discussion of this proposed =
resolution=20
  on the NSIS list.&nbsp;</FONT></DIV>
  <DIV><FONT face=3Darial><BR =
class=3Dwebkit-block-placeholder></FONT></DIV>
  <DIV><FONT face=3Darial>&gt; which is why we've been assuming there =
was no issue=20
  with it. </FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV>It isn't sufficient to&nbsp;declare 'silence is agreement' on =
making such=20
  a fundamental change.&nbsp; People should weigh in *on the list* and =
give=20
  their&nbsp;technical justifications and confirm their agreement (or=20
  disagreement).</DIV>
  <DIV><FONT face=3Darial></FONT>&nbsp;</DIV>
  <DIV><FONT face=3Darial>&gt;&gt; Who were the QSPEC co-authors who =
worked with=20
  you on the</FONT></DIV>
  <DIV><FONT face=3Darial>&gt;&gt;&nbsp;proposed =
resolution?</FONT></DIV>
  <DIV><FONT face=3Darial><BR =
class=3Dwebkit-block-placeholder></FONT></DIV>
  <DIV><FONT face=3Darial>&gt; Attila, Cornelia and Dave Oran (+ NSIS WG =

  chairs).</FONT></DIV>
  <DIV><FONT color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
  <DIV>So far I've not been able to verify agreement from the QSPEC =
co-authors=20
  as yet.&nbsp; We saw no discussion of the issue on the list, and there =
needs=20
  to be some explanation/justification for the change.&nbsp; </DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Perhaps Francois could summarize the technical&nbsp;discussion =
amonst the=20
  co-authors, and also state who explicitly agreed (as opposed to who =
had no=20
  comment or active participation in the discussion).&nbsp;&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>It would be good if the co-authors who participated&nbsp;in the=20
  discussion of the 'proposed agreement' could weigh in on the list with =
their=20
  technical view.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Also, both NSIS chairs have said there is an agreement on the =
proposal,=20
  so perhaps they could weigh in on the list also with their technical=20
  view.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Jerry</DIV></DIV></FONT><BR><BR><B><I>Francois Le Faucheur IMAP =
&lt;<A=20
  href=3D"mailto:flefauch@cisco.com">flefauch@cisco.com</A>&gt;</I></B>=20
  wrote:</DIV>
  <BLOCKQUOTE class=3Dreplbq=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px =
solid">Hello=20
    Jerry,=20
    <DIV><BR>
    <DIV>
    <DIV>On 20 Feb 2008, at 16:58, Gerald Ash wrote:</DIV><BR=20
    class=3DApple-interchange-newline>
    <BLOCKQUOTE type=3D"cite">
      <DIV><FONT face=3D"Courier&#13;&#13;&#10; =
New">Francois,</FONT></DIV>
      <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
      <DIV><FONT face=3D"Courier New">In your "Proposed Resolution" =
posting to=20
      NSIS on 3 December <A=20
      =
href=3D"http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html">=
http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html</A>&nbsp;=
you=20
      say:</FONT></DIV>
      <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
      <DIV><FONT face=3D"Courier New">&gt; The Proposed =
Resolution<BR>&gt;=20
      =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>&gt; =
Co-authors of the three I-Ds as well as WG=20
      chairs of the </FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt; corresponding WGs converged =
on the=20
      following proposed </FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt; resolution. </FONT></DIV>
      <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
      <DIV><FONT face=3D"Courier New">I saw no discussion of this =
proposed=20
      resolution on the NSIS list.&nbsp;</FONT></DIV></BLOCKQUOTE>
    <DIV><BR class=3Dwebkit-block-placeholder></DIV>
    <DIV>which is why we've been assuming there was no issue with it.=20
    &nbsp;</DIV>
    <DIV><BR class=3Dwebkit-block-placeholder></DIV><BR>
    <BLOCKQUOTE type=3D"cite">
      <DIV><FONT face=3D"Courier New">Who were the QSPEC co-authors who =
worked=20
      with you on the proposed resolution?</FONT></DIV></BLOCKQUOTE>
    <DIV><BR class=3Dwebkit-block-placeholder></DIV>
    <DIV>Attila, Cornelia and Dave Oran (+ NSIS WG chairs).</DIV>
    <DIV><BR></DIV><BR>
    <BLOCKQUOTE type=3D"cite">
      <DIV>&nbsp;</DIV>
      <DIV><FONT face=3D"Courier New">&gt; o Regarding =
RPH-Priority:<BR>&gt; *=20
      tsvwg-emergency-rsvp will go ahead with its requests =
to</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;IANA </FONT><FONT=20
      face=3D"Courier New">to provide numerical registry for RPH =
priority (via=20
      </FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt; extending existing RPH =
registry). See=20
      IANA Considerations</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;section of=20
      tsvwg-emergency-rsvp.</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt; * nsis-qspec (in section =
6.2.10) will=20
      point to this registry</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;instead of defining its =
own=20
      values</FONT></DIV>
      <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
      <DIV><FONT face=3D"Courier New">OK.</FONT></DIV>
      <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
      <DIV><FONT face=3D"Courier New">&gt; o Regarding Admission =
Priority:<BR>&gt;=20
      * every protocol spec will only indicate that "higher =
value</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;means higher=20
      priority".</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt; * there is no attempt to =
define what=20
      specific values should</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;be used for what. this =
is left=20
      outside the scope of the</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;protocol specs.<BR>* =
each protocol=20
      spec will add a statement clarifying that a</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;given Admission Priority =
is to be=20
      encoded with the same</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;value in each of the =
three=20
      protocol spec. For example, in</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;tsvwg-emergency-rsvp, =
under=20
      section 3.1. we will add:<BR>" A given Admission Priority is =
encoded in=20
      this information</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;element using the same =
value as=20
      when encoded in the</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;Admission Priority =
parameter=20
      defined in section 6.2.9 of</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;[nsis-qspec], or in the =
Admission=20
      Priority parameter</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;defined in section 4.10 =
of=20
      [dime-qos-parameters].</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt; In other words, a given value =
in any of=20
      the</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;[emergency-rsvp] =
Admission=20
      Priority information element,</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;the [nsis-qspec] =
Admission=20
      Priority parameter or the</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;[dime-qos-parameters] =
Admission=20
      Priority parameter,</FONT></DIV>
      <DIV><FONT face=3D"Courier New">&gt;&nbsp;refers to the same =
Admission=20
      Priority.<BR></FONT></DIV>
      <DIV><FONT face=3D"Courier New">The above proposed paragraph is =
really=20
      unclear.&nbsp; Which draft&nbsp;is setting up IANA Registries to =
assign=20
      Admission Priority parameters?&nbsp; The way it reads it sounds =
like all=20
      three drafts are setting up registries but that =
somehow&nbsp;(magically)=20
      all&nbsp;refer "to the same Admission Priority".&nbsp; How can =
that be if=20
      they assign different values?&nbsp; Right now emergency-rsvp and=20
      nsis-qspec set up registries for Admission Priority and=20
      dime-qos-parameters is using the nsis-qspec registry as I=20
      recall.</FONT></DIV>
      <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
      <DIV><FONT face=3D"Courier New">Please clarify the proposal as to =
which=20
      draft is setting up a registry for Admission=20
    Priority.&nbsp;</FONT></DIV></BLOCKQUOTE>
    <DIV><BR class=3Dwebkit-block-placeholder></DIV>
    <DIV>No registry is setup.</DIV>
    <DIV>It is up to a network administrator to decide how many/which =
admission=20
    priority gets used for what. This is similar to how Preemption is =
used (ie=20
    each network administrator may decide to use it or not, may decide =
to use=20
    2,3,4,...128,.. levels...).</DIV>
    <DIV>The statement above only says that the the same value of =
admission=20
    priority should be used in the three protocols to refer to same =
level of=20
    admission priority.</DIV>
    <DIV><BR class=3Dwebkit-block-placeholder></DIV>
    <DIV>Cheers</DIV>
    <DIV><BR class=3Dwebkit-block-placeholder></DIV>
    <DIV>Francois</DIV>
    <DIV><BR class=3Dwebkit-block-placeholder></DIV><BR>
    <BLOCKQUOTE type=3D"cite">
      <DIV><FONT face=3D"Courier New">Also, please provide =
clearer&nbsp;proposed=20
      text to include in the drafts.&nbsp; </FONT></DIV>
      <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
      <DIV><FONT face=3D"Courier New">It would be good to see some =
discussion of=20
      the proposal on the list, to confirm and validate agreement of the =

      WG.</FONT></DIV>
      <DIV><FONT face=3D"Courier New"></FONT>&nbsp;</DIV>
      <DIV><FONT face=3D"Courier New">Jerry</FONT></DIV><FONT=20
      face=3D"Courier New"></FONT>
      <DIV><BR><BR><B><I>Francois Le Faucheur IMAP &lt;<A=20
      =
href=3D"mailto:flefauch@cisco.com">flefauch@cisco.com</A>&gt;</I></B>=20
      wrote:</DIV>
      <BLOCKQUOTE class=3Dreplbq=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff =
2px solid">Hello,<BR><BR>For=20
        memory, the next rev of nsis-qspec is also expected to be =
aligned=20
        <BR>with the Resolution of the issue related to QoS Parameters =
encoding=20
        <BR>in <DIME-QOS-PARAMETERS>, <NSIS-QSPEC>&amp; =
<TSVWG-EMEREGNCY-RSVP>.=20
        For <BR>convenience, I included below the recap on the =
corresponding=20
        <BR>resolution as announced on NSIS, DIME and TSVWG =
lists.<BR><BR>Just=20
        to make sure this does not fall through the=20
        cracks.<BR><BR>Cheers<BR><BR>Francois<BR><BR><BR>&gt;<BR>&gt; =
Begin=20
        forwarded message:<BR>&gt;&gt; From: Francois Le Faucheur IMAP=20
        <FLEFAUCH@CISCO.COM><BR>&gt;&gt; Date: 3 December 2007 12:05:42=20
        GMT+01:00<BR>&gt;&gt; To: <A=20
        href=3D"mailto:dime@ietf.org">dime@ietf.org</A>, <A=20
        href=3D"mailto:nsis@ietf.org">nsis@ietf.org</A>, tsvwg tsvwg=20
        <TSVWG@IETF.ORG><BR>&gt;&gt; Cc: Francois Le Faucheur IMAP=20
        <FLEFAUCH@CISCO.COM>, David Oran R <BR>&gt;&gt; =
<ORAN@CISCO.COM>, Hannes=20
        Tschofenig <HANNES.TSCHOFENIG@GMX.NET>, <BR>&gt;&gt; ken =
carlberg=20
        <CARLBERG@G11.ORG.UK>, Magnus Westerlund <BR>&gt;&gt;=20
        <MAGNUS.WESTERLUND@ERICSSON.COM>, James Polk <JMPOLK@CISCO.COM>, =

        <BR>&gt;&gt; <A=20
        =
href=3D"mailto:cornelia.kappler@nsn.com">cornelia.kappler@nsn.com</A>,=20
        "(IJ/ETH) B=E1der Attila" <BR>&gt;&gt; =
<ATTILA.BADER@ERICSSON.COM>, <A=20
        =
href=3D"mailto:jouni.korhonen@teliasonera.com">jouni.korhonen@teliasonera=
.com</A>,=20
        Jukka <BR>&gt;&gt; Manner MJ <JMANNER@CS.HELSINKI.FI>, tsvwg =
chair=20
        <TSVWG-><BR>&gt;&gt; <A=20
        =
href=3D"mailto:chairs@tools.ietf.org">chairs@tools.ietf.org</A>&gt;, <A=20
        =
href=3D"mailto:nsis-chairs@tools.ietf.org">nsis-chairs@tools.ietf.org</A>=
,=20
        dime- <BR>&gt;&gt; <A=20
        href=3D"mailto:chairs@tools.ietf.org">chairs@tools.ietf.org</A>, =
"<A=20
        =
href=3D"mailto:john.loughney@nokia.com">john.loughney@nokia.com</A>&gt;" =

        <BR>&gt;&gt; <JOHN.LOUGHNEY@NOKIA.COM><BR>&gt;&gt; Subject: =
Resolution=20
        of issue QoS Parameters encoding in <DIME-QOS-><BR>&gt;&gt;=20
        parameters&gt;, <NSIS-QSPEC>&amp;=20
        <TSVWG-EMEREGNCY-RSVP><BR>&gt;&gt;<BR>&gt;&gt;=20
        Hello,<BR>&gt;&gt;<BR>&gt;&gt; The Issue:<BR>&gt;&gt;=20
        =3D=3D=3D=3D=3D=3D=3D<BR>&gt;&gt; Three different documents =
(dime-qos-parameters,=20
        nsis-qos-nslp, <BR>&gt;&gt; tsvwg-emergency-rsvp) need to convey =
an=20
        overlapping set of QoS <BR>&gt;&gt; parameters (specifically=20
        RPH-Priority and Admission Priority) and <BR>&gt;&gt; currently =
do that=20
        in an inconsistent manner. This has been brought <BR>&gt;&gt; up =
and=20
        partially discussed on the WG mailing =
lists.<BR>&gt;&gt;<BR>&gt;&gt; The=20
        Proposed Resolution<BR>&gt;&gt; =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>&gt;&gt;=20
        Co-authors of the three I-Ds as well as WG chairs of the =
<BR>&gt;&gt;=20
        corresponding WGs converged on the following proposed =
resolution.=20
        <BR>&gt;&gt; Please let us know if you have an issue/concern =
with=20
        this.<BR>&gt;&gt;<BR>&gt;&gt; o Regarding =
RPH-Priority:<BR>&gt;&gt; *=20
        tsvwg-emergency-rsvp will go ahead with its requests to IANA to=20
        <BR>&gt;&gt; provide numerical registry for RPH priority (via =
extending=20
        <BR>&gt;&gt; existing RPH registry). See IANA Considerations =
section of=20
        tsvwg- <BR>&gt;&gt; emergency-rsvp.<BR>&gt;&gt; * nsis-qspec (in =
section=20
        6.2.10) will point to this registry <BR>&gt;&gt; instead of =
defining its=20
        own values<BR>&gt;&gt; * dime-qos-parameters (in section 4.11) =
will=20
        point to this <BR>&gt;&gt; registry instead of defining its own=20
        values<BR>&gt;&gt; * tsvwg-emergency-rsvp (in section 3.2) will =
keep=20
        pointing to <BR>&gt;&gt; this registry.<BR>&gt;&gt;<BR>&gt;&gt; =
o=20
        Regarding Admission Priority:<BR>&gt;&gt; * every protocol spec =
will=20
        only indicate that "higher value means <BR>&gt;&gt; higher=20
        priority".<BR>&gt;&gt; * there is no attempt to define what =
specific=20
        values should be <BR>&gt;&gt; used for what. this is left =
outside the=20
        scope of the protocol specs.<BR>&gt;&gt; * each protocol spec =
will add a=20
        statement clarifying that a given <BR>&gt;&gt; Admission =
Priority is to=20
        be encoded with the same value in each of <BR>&gt;&gt; the three =

        protocol spec. For example, in tsvwg-emergency-rsvp, =
<BR>&gt;&gt; under=20
        section 3.1. we will add:<BR>&gt;&gt; " A given Admission =
Priority is=20
        encoded in this information <BR>&gt;&gt; element<BR>&gt;&gt; =
using the=20
        same value as when encoded in the Admission Priority<BR>&gt;&gt; =

        parameter defined in section 6.2.9 of [nsis-qspec], or in the=20
        <BR>&gt;&gt; Admission<BR>&gt;&gt; Priority parameter defined in =
section=20
        4.10 of [dime-qos- <BR>&gt;&gt; parameters].<BR>&gt;&gt; In =
other words,=20
        a given value in any of the [emergency-rsvp] <BR>&gt;&gt;=20
        Admission<BR>&gt;&gt; Priority information element, the =
[nsis-qspec]=20
        Admission Priority <BR>&gt;&gt; parameter<BR>&gt;&gt; or the=20
        [dime-qos-parameters] Admission Priority parameter, refers=20
        to<BR>&gt;&gt; the same Admission Priority.<BR>&gt;&gt; =
"<BR>&gt;&gt; *=20
        the mirror statement will be added in nsis-qspec (section =
<BR>&gt;&gt;=20
        6.2.9) and dime-qos-parameters (section =
4.10)<BR>&gt;&gt;<BR>&gt;&gt;=20
        =
Francois<BR>&gt;&gt;<BR><BR><BR><BR><BR></TSVWG-EMEREGNCY-RSVP></NSIS-QSP=
EC></DIME-QOS-></JOHN.LOUGHNEY@NOKIA.COM></TSVWG-></JMANNER@CS.HELSINKI.F=
I></ATTILA.BADER@ERICSSON.COM></JMPOLK@CISCO.COM></MAGNUS.WESTERLUND@ERIC=
SSON.COM></CARLBERG@G11.ORG.UK></HANNES.TSCHOFENIG@GMX.NET></ORAN@CISCO.C=
OM></FLEFAUCH@CISCO.COM></TSVWG@IETF.ORG></FLEFAUCH@CISCO.COM></TSVWG-EME=
REGNCY-RSVP></NSIS-QSPEC></DIME-QOS-PARAMETERS></BLOCKQUOTE><BR>
      <DIV><BR class=3Dkhtml-block-placeholder></DIV>
      <HR SIZE=3D1>
      Looking for last minute shopping deals? <A=20
      =
href=3D"http://us.rd.yahoo.com/evt=3D51734/*http://tools.search.yahoo.com=
/newsearch/category.php?category=3Dshopping">Find=20
      them fast with Yahoo!=20
Search.</A></BLOCKQUOTE></DIV><BR></DIV></BLOCKQUOTE><BR>
  <DIV><BR class=3Dkhtml-block-placeholder></DIV>
  <HR SIZE=3D1>
  Be a better friend, newshound, and know-it-all with Yahoo! Mobile. <A=20
  =
href=3D"http://us.rd.yahoo.com/evt=3D51733/*http://mobile.yahoo.com/;_ylt=
=3DAhu06i62sR8HDtDypao8Wcj9tAcJ ">Try=20
  it now.</A> </BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>

------_=_NextPart_001_01C87596.849548EF--

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

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

--===============0518200029==--


From nsis-bounces@ietf.org  Sat Feb 23 06:44:52 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F2E163A67F7;
	Sat, 23 Feb 2008 06:44:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.78
X-Spam-Level: 
X-Spam-Status: No, score=0.78 tagged_above=-999 required=5 tests=[AWL=-0.083,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_MESSAGE=1, MIME_8BIT_HEADER=0.3, 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 PHm5bO+TG4z6; Sat, 23 Feb 2008 06:44:51 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 19DD73A67FD;
	Sat, 23 Feb 2008 06:44:51 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0239C3A68A2
	for <nsis@core3.amsl.com>; Sat, 23 Feb 2008 06:44:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 I7Po-C2+AZD8 for <nsis@core3.amsl.com>;
	Sat, 23 Feb 2008 06:44:48 -0800 (PST)
Received: from mail-2.ci.uc.pt (mail.uc.pt [193.137.200.38])
	by core3.amsl.com (Postfix) with ESMTP id D80C33A67F7
	for <nsis@ietf.org>; Sat, 23 Feb 2008 06:44:47 -0800 (PST)
Received: from mail-2.ci.uc.pt (mail.uc.pt [127.0.0.1])
	by localhost.mail.uc.pt (Postfix) with ESMTP id DC61788DE3F
	for <nsis@ietf.org>; Sat, 23 Feb 2008 14:44:41 +0000 (WET)
Received: from [192.168.1.102] (a81-84-56-240.cpe.netcabo.pt [81.84.56.240])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail-2.ci.uc.pt (Postfix) with ESMTP id 9889C88DE3E
	for <nsis@ietf.org>; Sat, 23 Feb 2008 14:44:41 +0000 (WET)
Message-ID: <47C0314C.4040303@dei.uc.pt>
Date: Sat, 23 Feb 2008 14:44:28 +0000
From: =?ISO-8859-1?Q?Lu=EDs_Cordeiro?= <cordeiro@dei.uc.pt>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: NSIS Group <nsis@ietf.org>
Content-Type: multipart/mixed; boundary="------------050909030105020904000903"
Subject: [NSIS] [Fwd: I-D ACTION:draft-cordeiro-nsis-mih-nslp-00.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: <http://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: <http://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.
--------------050909030105020904000903
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
<br>
I forward to you this new I-D that defines the new MIH NSLP for the
transport
of messages from the IEEE 802.21 standard using the Next Steps in
Signalling
(NSIS) framework.<br>
<br>
I look forward to receive your comments.<br>
<br>
BR,<br>
Lu&iacute;s Cordeiro<br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
 cellspacing="0">
  <tbody>
    <tr>
      <th align="right" nowrap="nowrap" valign="baseline">Subject: </th>
      <td>I-D ACTION:draft-cordeiro-nsis-mih-nslp-00.txt</td>
    </tr>
    <tr>
      <th align="right" nowrap="nowrap" valign="baseline">Date: </th>
      <td>Thu, 21 Feb 2008 17:00:01 -0800 (PST)</td>
    </tr>
    <tr>
      <th align="right" nowrap="nowrap" valign="baseline">From: </th>
      <td><a class="moz-txt-link-abbreviated" href="mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a></td>
    </tr>
    <tr>
      <th align="right" nowrap="nowrap" valign="baseline">Reply-To: </th>
      <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
    </tr>
    <tr>
      <th align="right" nowrap="nowrap" valign="baseline">To: </th>
      <td><a class="moz-txt-link-abbreviated" href="mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a></td>
    </tr>
  </tbody>
</table>
<br>
<br>
<pre>A New Internet-Draft is available from the on-line Internet-Drafts 
directories.


	Title		: Media Independent Handover Network Signalling Layer Protocol (MIH NSLP)
	Author(s)	: S. Sargento, G. Landi, X. Fu
	Filename	: draft-cordeiro-nsis-mih-nslp-00.txt
	Pages		: 23
	Date		: 2008-2-18
	
This memo defines the Media Independent Handover Network Signalling
   Layer Protocol (MIH NSLP) for the transport of messages from the IEEE
   802.21 standard using the Next Steps in Signalling (NSIS) framework.
   The MIH NSLP is responsible for the transport of MIH messages to
   remote entities reporting on link layer information, in order to
   support seamless mobility in heterogeneous environments.  A usage
   example of the MIH NSLP is also provided.


A URL for this Internet-Draft is:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-cordeiro-nsis-mih-nslp-00.txt">http://www.ietf.org/internet-drafts/draft-cordeiro-nsis-mih-nslp-00.txt</a>

To remove yourself from the I-D Announcement list, send a message to 
<a class="moz-txt-link-abbreviated" href="mailto:i-d-announce-request@ietf.org">i-d-announce-request@ietf.org</a> with the word unsubscribe in the body of 
the message. 
You can also visit <a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1.ietf.org/mailman/listinfo/I-D-announce</a> 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-cordeiro-nsis-mih-nslp-00.txt".

A list of Internet-Drafts directories can be found in
<a class="moz-txt-link-freetext" href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a> 
or <a class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a>

</pre>
</body>
</html>

--------------050909030105020904000903
Content-Type: text/plain;
 name="file:///C:/DOCUME~1/CORDEIRO/LOCALS~1/TEMP/nsmail.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename*0="file:///C:/DOCUME~1/CORDEIRO/LOCALS~1/TEMP/nsmail.txt"

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
http://www.ietf.org/mailman/listinfo/i-d-announce


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

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

--------------050909030105020904000903--


From nsis-bounces@ietf.org  Sat Feb 23 07:46:04 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6A3E228C293;
	Sat, 23 Feb 2008 07:46:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.569
X-Spam-Level: *
X-Spam-Status: No, score=1.569 tagged_above=-999 required=5 tests=[AWL=-0.106,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=1, MIME_HTML_MOSTLY=0.001,
	RDNS_NONE=0.1, 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 l-1+YFtHEZ9t; Sat, 23 Feb 2008 07:46:01 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7BFDD28C369;
	Sat, 23 Feb 2008 07:46:01 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BB85D28C31D
	for <nsis@core3.amsl.com>; Sat, 23 Feb 2008 07:45:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 lDU1D3M1FMXo for <nsis@core3.amsl.com>;
	Sat, 23 Feb 2008 07:45:56 -0800 (PST)
Received: from web63608.mail.re1.yahoo.com (web63608.mail.re1.yahoo.com
	[69.147.97.78]) by core3.amsl.com (Postfix) with SMTP id C60F828C293
	for <nsis@ietf.org>; Sat, 23 Feb 2008 07:45:52 -0800 (PST)
Received: (qmail 48635 invoked by uid 60001); 23 Feb 2008 15:45:48 -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=vIRt/pPNNKM4XJeGL6yoe8qbX9BFaEICzkA/iHC/odpUY4G8E/QOrPYQHoPQwfRCncGZyGxyr34MUreyX1c0NjoFBU5VSLyKY4Gg/WVofsvDX5id968JSrqS1xCTg37k3BXqV/IhHcT9BFT5VRzmFFs5iQkGvC+RfCWxkvx/RLo=;
X-YMail-OSG: .G7VSjQVM1mlK.Gr1OnS5CtWP2zI4V3VrS53WofTc6YyFCjZnIiGQQc617FpPCMc9s2t9cX8E_ZaNNta6umft.bn3w--
Received: from [76.19.255.157] by web63608.mail.re1.yahoo.com via HTTP;
	Sat, 23 Feb 2008 07:45:47 PST
Date: Sat, 23 Feb 2008 07:45:47 -0800 (PST)
From: Gerald Ash <gash5107@yahoo.com>
To: "TARAPORE, PERCY S, ATTLABS" <tarapore@att.com>,
	Francois Le Faucheur IMAP <flefauch@cisco.com>
In-Reply-To: <A1F50CB516D211409DFD05D6B3CE6D300CD2B731@KCCLUST06EVS1.ugd.att.com>
MIME-Version: 1.0
Message-ID: <984574.82097.qm@web63608.mail.re1.yahoo.com>
Cc: john.loughney@nokia.com, nsis <nsis@ietf.org>
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0665998287=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

--===============0665998287==
Content-Type: multipart/alternative; boundary="0-1829644322-1203781547=:82097"
Content-Transfer-Encoding: 8bit

--0-1829644322-1203781547=:82097
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Percy,
   
  > It is also my understanding that there really is no major issue in
  > changing an IETF spec that is tied to an ITU-T spec. If for example,
  > Y.2171 is updated some time in the future to add a 4th priority level,
  > then IANA can accommodate this by an appropriate change in
  > NSIS-QSPEC. Jerry can you please confirm this?
   
    Right, there is no issue in having an IETF spec tied to an ITU spec.  If ITU modifies their spec, IANA will make the corresponding changes in the IETF IANA assignments.  E.g., if ITU later standardizes more priority levels, say in "Y.2171.bis', IANA will change the admission priority registry accordingly.  I checked that out with IANA a while ago, IANA can tie into ITU specs in this way.
   
  In fact, many IETF standards incorporate ITU standards.  As you point out, NSIS/NSLP/QSPEC incorporates Y.1541, and there are lots of other examples.  I don't think we can reject this approach to admission priority because it is based on an ITU standard, in fact, IMO it strengthens the approach in this case.

   
  Thanks,
  Jerry

"TARAPORE, PERCY S, ATTLABS" <tarapore@att.com> wrote:
      Francois,
   
  If it is undesirable to tie in to specs from another SDO, then should we completely abandon all other efforts that are related? For example, should we drop the tie-in to Y.1541-QSPEC that NSIS is also working on?
   
  Can you demonstrate how domain-specific priority assignments could possibly work? See Jerry's statement from the e-mail thread:
   
    "...If we eliminate this standardization, as is proposed, then different admission priority values can be assigned in different Admin domains, and will have no end-to-end significance.  For example, Admin-domain 1, Admin-domain 2, and Admin-domain 3 assign admission priority=2,  admission priority=4, admission priority=10 for the highest level priority, respectively.  Admin-domain 1 and Admin-domain 2 try to initiate end-to-end flows via Admin-domain 3 for a 'high priority' flow.  However, Admin-domain 3 has no idea how to treat the flow admission priority since all 3 domains are using different encodings of high priority...."
   
  Can you please indicate how this situation could be resolved without an accepted standardized set of priority levels that can be exchanged across domains? 
   
  It is also my understanding that there really is no major issue in changing an IETF spec that is tied to an ITU-T spec. If for example, Y.2171 is updated some time in the future to add a 4th priority level, then IANA can accommodate this by an appropriate change in NSIS-QSPEC. Jerry can you please confirm this?
   
  I still do not see any merit in removing Y.2171 priority levels from NSIS-QSPEC.
   
  Thanks
   
  Percy

  

    
---------------------------------
  From: Francois Le Faucheur IMAP [mailto:flefauch@cisco.com] 
Sent: Friday, February 22, 2008 1:52 PM
To: TARAPORE, PERCY S, ATTLABS
Cc: Francois Le Faucheur IMAP; Gerald Ash; Martin Stiemerling; john.loughney@nokia.com; nsis
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.txt


  
Hello Percy,   

  Some of the considerations that led to the decision to not re-specify in <emergency-rsvp>, <dime-qos-parameters> and <nsis-qspec> the admission priority values that are already specified in Y.2171 specs included:
  * they are already defined in this ITU spec
  * if one wants to comply with the ITU way to do Admission Priority they can follow the ITU spec
  * it is not 100% obvious that absolutely every network administrator will ever want to implement admission priority exactly as specified by ITU and by that particular spec. Maybe one administrator will want to use less priorities, maybe one will want to use more...
  * the admission mechanism to be defined by IETF should be flexible and not tied to one single application of one single SDO.

  * the admission priority mechanism defined in IETF should allow support of a particular application of a particular SDO. This can be achieved by deliberate choice of a network administrator to use the values of that application/SDO (but we don't have to mandate that everybody using the admission priority mechanisms use it in the same way) 

  * this is the approach already used for the "Preemption" mechanism supported by NSIS and RSVP (ie it is up to network administrator to decide which preemption priority value to use in their network and their semantic is not defined in the documents)

  * as a side practical considerations: it is undesirable to have an IETF spec tied to specifications of another body (eg what happens if ITU defines Y.2171bis with one more value? do we have to immediately reissue <emergency-rsvp>, <dime-qos-parameters> and <nsis-qspec>)? For example, if those documents would have mandated the ITU values and have been standardised in 2006, they would have referred to Y.1571 (as I think Qspec used to do before Y.1571 got superseded by Y.2171...)
  

  Cheers
  

  Francois
  
    On 22 Feb 2008, at 19:05, TARAPORE, PERCY S, ATTLABS wrote:

    The purpose and intent for Y.2171 was to standardize a set of admission control priority levels that can be recognized across multiple admin domains - and acted upon appropriately to provide the necessary CAC within each domain. Further, Priority Level 1 - the highest CAC priority - is exclusively reserved for emergency telecommunications in Y.2171. Thus retaining these in the NSIS-QSPEC is appropriate. They should not be changed or removed.
   
  Percy S. Tarapore

    
---------------------------------
  From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On Behalf Of Gerald Ash
Sent: Thursday, February 21, 2008 11:56 AM
To: Francois Le Faucheur IMAP; Martin Stiemerling; john.loughney@nokia.com; nsis
Cc: cornelia.kappler@googlemail.com
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.txt


  
  Francois, Martin, John, All,
   
    >>> o Regarding Admission Priority:
>>> * every protocol spec will only indicate that "higher value
  >>> means higher priority".
  >>> * there is no attempt to define what specific values should
  >>> be used for what. this is left outside the scope of the
  >>> protocol specs.
>>> * each protocol spec will add a statement clarifying that a
  >>> given Admission Priority is to be encoded with the same
  >>> value in each of the three protocol spec. For example, in
  >>> tsvwg-emergency-rsvp, under section 3.1. we will add:
>>> " A given Admission Priority is encoded in this information
  >>> element using the same value as when encoded in the
  >>> Admission Priority parameter defined in section 6.2.9 of
  >>> [nsis-qspec], or in the Admission Priority parameter
  >>> defined in section 4.10 of [dime-qos-parameters].
  >>> In other words, a given value in any of the
  >>> [emergency-rsvp] Admission Priority information element,
  >>> the [nsis-qspec] Admission Priority parameter or the
  >>> [dime-qos-parameters] Admission Priority parameter,
  >>> refers to the same Admission Priority.
   
  >> The above proposed paragraph is really unclear.  Which draft
  >> is setting up IANA Registries to assign Admission Priority
  >> parameters?  The way it reads it sounds like all three drafts
  >> are setting up registries but that somehow (magically) all refer
  >> "to the same Admission Priority".  How can that be if they
  >> assign different values?  Right now emergency-rsvp and
  >> nsis-qspec set up registries for Admission Priority and
  >> dime-qos-parameters is using the nsis-qspec registry as I
  >> recall.
  >>
  >> Please clarify the proposal as to which draft is setting up a
  >> registry for Admission Priority. 
  

  > No registry is setup.
  > It is up to a network administrator to decide how many/which
  > admission priority gets used for what. This is similar to how
  > Preemption is used (ie each network administrator may decide 
  > to use it or not, may decide to use 2,3,4,...128,.. levels...).
  > The statement above only says that the the same value of 
  > admission priority should be used in the three protocols to refer 
  > to same level of admission priority.
   
  That's a fundamental change to NSIS/QSPEC and does away with standardized Admission Priority values.  QSPEC is following Y.1571 (now Y.2171 according to An Nguyen) in standardizing 3 priority levels to have end-to-end cross-domain significance.
   
  If we elimate this standardization, as is proposed, then different admission priority values can be assigned in different Admin domains, and will have no end-to-end significance.  For example, Admin-domain 1, Admin-domain 2, and Admin-domain 3 assign admission priority=2,  admission priority=4, admission priority=10 for the highest level priority, respectively.  Admin-domain 1 and Admin-domain 2 try to initiate end-to-end flows via Admin-domain 3 for a 'high priority' flow.  However, Admin-domain 3 has no idea how to treat the flow admission priority since all 3 domains are using different encodings of high priority.
     
  Admission priority is not the same as preemption priority and should not be based on that model.
   

  IMO we should retain the standardized admission priority levels based on Y.1571/Y.2171.  Otherwise, how do we achieve end-to-end, cross-domain standardization of admission priority?  In any case, we need to see some good justification for the change.
   
    >> I saw no discussion of this proposed resolution on the NSIS list. 
  

  > which is why we've been assuming there was no issue with it. 
   
  It isn't sufficient to declare 'silence is agreement' on making such a fundamental change.  People should weigh in *on the list* and give their technical justifications and confirm their agreement (or disagreement).
   
  >> Who were the QSPEC co-authors who worked with you on the
  >> proposed resolution?
  

  > Attila, Cornelia and Dave Oran (+ NSIS WG chairs).
   
  So far I've not been able to verify agreement from the QSPEC co-authors as yet.  We saw no discussion of the issue on the list, and there needs to be some explanation/justification for the change.  
   
  Perhaps Francois could summarize the technical discussion amonst the co-authors, and also state who explicitly agreed (as opposed to who had no comment or active participation in the discussion).  
   
  It would be good if the co-authors who participated in the discussion of the 'proposed agreement' could weigh in on the list with their technical view.
   
  Also, both NSIS chairs have said there is an agreement on the proposal, so perhaps they could weigh in on the list also with their technical view.
   
  Jerry



Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:
  Hello Jerry,   
    On 20 Feb 2008, at 16:58, Gerald Ash wrote:

    Francois,
   
  In your "Proposed Resolution" posting to NSIS on 3 December http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html you say:
   
  > The Proposed Resolution
> ===================
> Co-authors of the three I-Ds as well as WG chairs of the 
  > corresponding WGs converged on the following proposed 
  > resolution. 
   
  I saw no discussion of this proposed resolution on the NSIS list. 
  

  which is why we've been assuming there was no issue with it.  
  


    Who were the QSPEC co-authors who worked with you on the proposed resolution?
  

  Attila, Cornelia and Dave Oran (+ NSIS WG chairs).
  


     
  > o Regarding RPH-Priority:
> * tsvwg-emergency-rsvp will go ahead with its requests to
  > IANA to provide numerical registry for RPH priority (via 
  > extending existing RPH registry). See IANA Considerations
  > section of tsvwg-emergency-rsvp.
  > * nsis-qspec (in section 6.2.10) will point to this registry
  > instead of defining its own values
   
  OK.
   
  > o Regarding Admission Priority:
> * every protocol spec will only indicate that "higher value
  > means higher priority".
  > * there is no attempt to define what specific values should
  > be used for what. this is left outside the scope of the
  > protocol specs.
* each protocol spec will add a statement clarifying that a
  > given Admission Priority is to be encoded with the same
  > value in each of the three protocol spec. For example, in
  > tsvwg-emergency-rsvp, under section 3.1. we will add:
" A given Admission Priority is encoded in this information
  > element using the same value as when encoded in the
  > Admission Priority parameter defined in section 6.2.9 of
  > [nsis-qspec], or in the Admission Priority parameter
  > defined in section 4.10 of [dime-qos-parameters].
  > In other words, a given value in any of the
  > [emergency-rsvp] Admission Priority information element,
  > the [nsis-qspec] Admission Priority parameter or the
  > [dime-qos-parameters] Admission Priority parameter,
  > refers to the same Admission Priority.

  The above proposed paragraph is really unclear.  Which draft is setting up IANA Registries to assign Admission Priority parameters?  The way it reads it sounds like all three drafts are setting up registries but that somehow (magically) all refer "to the same Admission Priority".  How can that be if they assign different values?  Right now emergency-rsvp and nsis-qspec set up registries for Admission Priority and dime-qos-parameters is using the nsis-qspec registry as I recall.
   
  Please clarify the proposal as to which draft is setting up a registry for Admission Priority. 
  

  No registry is setup.
  It is up to a network administrator to decide how many/which admission priority gets used for what. This is similar to how Preemption is used (ie each network administrator may decide to use it or not, may decide to use 2,3,4,...128,.. levels...).
  The statement above only says that the the same value of admission priority should be used in the three protocols to refer to same level of admission priority.
  

  Cheers
  

  Francois
  


    Also, please provide clearer proposed text to include in the drafts.  
   
  It would be good to see some discussion of the proposal on the list, to confirm and validate agreement of the WG.
   
  Jerry
  

Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:
  Hello,

For memory, the next rev of nsis-qspec is also expected to be aligned 
with the Resolution of the issue related to QoS Parameters encoding 
in , & . For 
convenience, I included below the recap on the corresponding 
resolution as announced on NSIS, DIME and TSVWG lists.

Just to make sure this does not fall through the cracks.

Cheers

Francois


>
> Begin forwarded message:
>> From: Francois Le Faucheur IMAP 
>> Date: 3 December 2007 12:05:42 GMT+01:00
>> To: dime@ietf.org, nsis@ietf.org, tsvwg tsvwg 
>> Cc: Francois Le Faucheur IMAP , David Oran R 
>> , Hannes Tschofenig , 
>> ken carlberg , Magnus Westerlund 
>> , James Polk , 
>> cornelia.kappler@nsn.com, "(IJ/ETH) Báder Attila" 
>> , jouni.korhonen@teliasonera.com, Jukka 
>> Manner MJ , tsvwg chair 
>> chairs@tools.ietf.org>, nsis-chairs@tools.ietf.org, dime- 
>> chairs@tools.ietf.org, "john.loughney@nokia.com>" 
>> 
>> Subject: Resolution of issue QoS Parameters encoding in 
>> parameters>, & 
>>
>> Hello,
>>
>> The Issue:
>> =======
>> Three different documents (dime-qos-parameters, nsis-qos-nslp, 
>> tsvwg-emergency-rsvp) need to convey an overlapping set of QoS 
>> parameters (specifically RPH-Priority and Admission Priority) and 
>> currently do that in an inconsistent manner. This has been brought 
>> up and partially discussed on the WG mailing lists.
>>
>> The Proposed Resolution
>> ===================
>> Co-authors of the three I-Ds as well as WG chairs of the 
>> corresponding WGs converged on the following proposed resolution. 
>> Please let us know if you have an issue/concern with this.
>>
>> o Regarding RPH-Priority:
>> * tsvwg-emergency-rsvp will go ahead with its requests to IANA to 
>> provide numerical registry for RPH priority (via extending 
>> existing RPH registry). See IANA Considerations section of tsvwg- 
>> emergency-rsvp.
>> * nsis-qspec (in section 6.2.10) will point to this registry 
>> instead of defining its own values
>> * dime-qos-parameters (in section 4.11) will point to this 
>> registry instead of defining its own values
>> * tsvwg-emergency-rsvp (in section 3.2) will keep pointing to 
>> this registry.
>>
>> o Regarding Admission Priority:
>> * every protocol spec will only indicate that "higher value means 
>> higher priority".
>> * there is no attempt to define what specific values should be 
>> used for what. this is left outside the scope of the protocol specs.
>> * each protocol spec will add a statement clarifying that a given 
>> Admission Priority is to be encoded with the same value in each of 
>> the three protocol spec. For example, in tsvwg-emergency-rsvp, 
>> under section 3.1. we will add:
>> " A given Admission Priority is encoded in this information 
>> element
>> using the same value as when encoded in the Admission Priority
>> parameter defined in section 6.2.9 of [nsis-qspec], or in the 
>> Admission
>> Priority parameter defined in section 4.10 of [dime-qos- 
>> parameters].
>> In other words, a given value in any of the [emergency-rsvp] 
>> Admission
>> Priority information element, the [nsis-qspec] Admission Priority 
>> parameter
>> or the [dime-qos-parameters] Admission Priority parameter, refers to
>> the same Admission Priority.
>> "
>> * the mirror statement will be added in nsis-qspec (section 
>> 6.2.9) and dime-qos-parameters (section 4.10)
>>
>> Francois
>>




       
---------------------------------
Never miss a thing.   Make Yahoo your homepage.
--0-1829644322-1203781547=:82097
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>Percy,</DIV>  <DIV>&nbsp;</DIV>  <DIV><FONT face=Arial><FONT size=2><SPAN class=941143720-22022008>&gt; It is also my understanding that there really is no major issue in</SPAN></FONT></FONT></DIV>  <DIV><FONT face=Arial><FONT size=2><SPAN class=941143720-22022008>&gt;&nbsp;changing an IETF spec that is tied to an ITU-T spec. If for example,</SPAN></FONT></FONT></DIV>  <DIV><FONT face=Arial><FONT size=2><SPAN class=941143720-22022008>&gt;&nbsp;Y.2171 is updated some time in the future to add a 4th priority level,</SPAN></FONT></FONT></DIV>  <DIV><FONT face=Arial><FONT size=2><SPAN class=941143720-22022008>&gt;&nbsp;then IANA can accommodate this by an appropriate change in</SPAN></FONT></FONT></DIV>  <DIV><FONT face=Arial><FONT size=2><SPAN class=941143720-22022008>&gt;&nbsp;NSIS-QSPEC. Jerry can you please confirm this?</SPAN></FONT></FONT></DIV>  <DIV><FONT face=Arial><FONT size=2><SPAN class=941143720-22022008></SPAN></FONT></FONT>&nbsp;</DIV>  <DIV><FONT
 face=Arial><FONT size=2><SPAN class=941143720-22022008>  <DIV>Right, there is no issue in having an IETF spec tied to an ITU spec.&nbsp; If ITU modifies their spec,&nbsp;IANA will make the corresponding changes in the IETF IANA assignments.&nbsp; E.g., if ITU later standardizes more priority levels, say&nbsp;in "Y.2171.bis', IANA will change the admission priority registry&nbsp;accordingly.&nbsp; I checked that out with IANA&nbsp;a while&nbsp;ago, IANA can tie into ITU specs in this way.</DIV>  <DIV>&nbsp;</DIV>  <DIV>In fact, many IETF standards incorporate&nbsp;ITU standards.&nbsp; As you point out, NSIS/NSLP/QSPEC incorporates Y.1541, and there are lots of other examples.&nbsp; I don't think we can reject this approach to admission priority because it is based on an ITU standard, in fact, IMO it strengthens the approach in this case.</DIV></SPAN></FONT></FONT></DIV>  <DIV>&nbsp;</DIV>  <DIV>Thanks,</DIV>  <DIV>Jerry<BR><BR><B><I>"TARAPORE, PERCY S, ATTLABS"
 &lt;tarapore@att.com&gt;</I></B> wrote:</DIV>  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">  <META content="MSHTML 6.00.2900.3268" name=GENERATOR>  <DIV dir=ltr align=left><SPAN class=941143720-22022008><FONT face=Arial color=#0000ff size=2>Francois,</FONT></SPAN></DIV>  <DIV dir=ltr align=left><SPAN class=941143720-22022008><FONT face=Arial color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>  <DIV dir=ltr align=left><SPAN class=941143720-22022008><FONT face=Arial color=#0000ff size=2>If it is undesirable to tie in to specs from another SDO, then should we completely abandon all other efforts that are related? For example, should we drop the tie-in to Y.1541-QSPEC that NSIS is also working on?</FONT></SPAN></DIV>  <DIV>&nbsp;</DIV>  <DIV><SPAN class=941143720-22022008></SPAN><FONT face=Arial><FONT color=#0000ff><FONT size=2>C<SPAN class=941143720-22022008>an you demonstrate how domain-specific priority assignments could
 possibly work? See Jerry's statement from the e-mail thread:</SPAN></FONT></FONT></FONT></DIV>  <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=941143720-22022008></SPAN></FONT></FONT></FONT>&nbsp;</DIV>  <DIV><FONT size=+0><FONT size=+0><SPAN class=941143720-22022008>  <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=941143720-22022008>"...</SPAN>If we eliminate this standardization, as is proposed, then different admission priority values&nbsp;can be&nbsp;assigned in different Admin domains, and will&nbsp;have no end-to-end significance.&nbsp; For example, Admin-domain 1, Admin-domain 2, and Admin-domain 3 assign&nbsp;admission priority=2,&nbsp;&nbsp;admission priority=4, admission priority=10 for the highest level priority, respectively.&nbsp; Admin-domain 1 and Admin-domain 2 try to initiate end-to-end flows via Admin-domain&nbsp;3 for a 'high priority' flow.&nbsp;&nbsp;However, Admin-domain 3 has no idea how to treat the flow
 admission priority since all 3 domains are using different encodings of high priority.<SPAN class=941143720-22022008>..."</SPAN></FONT></FONT></FONT></DIV>  <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=941143720-22022008></SPAN></FONT></FONT></FONT>&nbsp;</DIV>  <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=941143720-22022008>Can you please indicate how this situation could be resolved without an accepted standardized set of priority levels that can be exchanged across domains? </SPAN></FONT></FONT></FONT></DIV>  <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=941143720-22022008></SPAN></FONT></FONT></FONT>&nbsp;</DIV>  <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=941143720-22022008>It is also my understanding that there really is no major issue in changing an IETF spec that is tied to an ITU-T spec. If for example, Y.2171 is updated some time in the future to add a 4th priority level, then
 IANA can accommodate this by an appropriate change in NSIS-QSPEC. Jerry can you please confirm this?</SPAN></FONT></FONT></FONT></DIV>  <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=941143720-22022008></SPAN></FONT></FONT></FONT>&nbsp;</DIV>  <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=941143720-22022008>I still do not see any merit in removing Y.2171 priority levels from NSIS-QSPEC.</SPAN></FONT></FONT></FONT></DIV>  <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=941143720-22022008></SPAN></FONT></FONT></FONT>&nbsp;</DIV>  <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=941143720-22022008>Thanks</SPAN></FONT></FONT></FONT></DIV>  <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN class=941143720-22022008></SPAN></FONT></FONT></FONT>&nbsp;</DIV>  <DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
 class=941143720-22022008>Percy</SPAN></FONT></FONT></FONT></DIV></SPAN></FONT></FONT></DIV>  <DIV><BR></DIV>  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>  <HR tabIndex=-1>  <FONT face=Tahoma size=2><B>From:</B> Francois Le Faucheur IMAP [mailto:flefauch@cisco.com] <BR><B>Sent:</B> Friday, February 22, 2008 1:52 PM<BR><B>To:</B> TARAPORE, PERCY S, ATTLABS<BR><B>Cc:</B> Francois Le Faucheur IMAP; Gerald Ash; Martin Stiemerling; john.loughney@nokia.com; nsis<BR><B>Subject:</B> Re: [NSIS] Review of draft-ietf-nsis-qspec-18.txt<BR></FONT><BR></DIV>  <DIV></DIV>Hello Percy,   <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>Some of the considerations that led to the decision to not re-specify in &lt;emergency-rsvp&gt;, &lt;dime-qos-parameters&gt; and &lt;nsis-qspec&gt; the admission priority values that are already specified in Y.2171 specs included:</DIV>  <DIV><SPAN class=Apple-tab-span style="WHITE-SPACE: pre"></SPAN>* they are already defined in this
 ITU spec</DIV>  <DIV><SPAN class=Apple-tab-span style="WHITE-SPACE: pre"></SPAN>* if one wants to comply with the ITU way to do Admission Priority they can follow the ITU spec</DIV>  <DIV><SPAN class=Apple-tab-span style="WHITE-SPACE: pre"></SPAN>* it is not 100% obvious that absolutely every network administrator will ever want to implement admission priority exactly as specified by ITU and by that particular spec. Maybe one&nbsp;administrator&nbsp;will want to use less priorities, maybe one will want to use more...</DIV>  <DIV><SPAN class=Apple-tab-span style="WHITE-SPACE: pre"></SPAN>* the admission mechanism to be defined by IETF should be flexible and not tied to one single application of one single SDO.<BR class=webkit-block-placeholder></DIV>  <DIV><SPAN class=Apple-tab-span style="WHITE-SPACE: pre"></SPAN>* the admission priority mechanism defined in IETF should allow support of a particular application of a particular SDO. This can be achieved by deliberate choice
 of a network administrator to use&nbsp;the&nbsp;values of that application/SDO (but we don't have to mandate that everybody using the&nbsp;admission&nbsp;priority mechanisms use it in the same way)&nbsp;<BR class=webkit-block-placeholder></DIV>  <DIV><SPAN class=Apple-tab-span style="WHITE-SPACE: pre"></SPAN>* this is the approach already used for the "Preemption" mechanism supported by NSIS and RSVP (ie it is up to network administrator to decide which preemption priority value to use in their network and their semantic is not defined in the documents)<BR class=webkit-block-placeholder></DIV>  <DIV><SPAN class=Apple-tab-span style="WHITE-SPACE: pre"></SPAN>* as a side practical considerations: it is undesirable to have an IETF spec tied to specifications of another body (eg what happens if ITU defines Y.2171bis with one more value? do we have to immediately reissue &lt;emergency-rsvp&gt;, &lt;dime-qos-parameters&gt; and &lt;nsis-qspec&gt;)? For example, if those documents
 would have mandated the ITU values and have been standardised in 2006, they&nbsp;would&nbsp;have&nbsp;referred&nbsp;to Y.1571 (as I think Qspec used to do before Y.1571 got superseded by Y.2171...)</DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>Cheers</DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>Francois</DIV>  <DIV><BR>  <DIV>  <DIV>On 22 Feb 2008, at 19:05, TARAPORE, PERCY S, ATTLABS wrote:</DIV><BR class=Apple-interchange-newline>  <BLOCKQUOTE type="cite">  <DIV dir=ltr align=left><SPAN class=005322817-22022008><FONT face=Arial color=#0000ff size=2>The purpose and intent for Y.2171 was to&nbsp;standardize a set of admission control priority levels<SPAN class=090300318-22022008>&nbsp;</SPAN>that can be recognized&nbsp;across multiple admin domains - and acted upon appropriately to provide the necessary CAC within each domain. Further, Priority Level 1 - the highest CAC priority - is exclusively reserved for emergency telecommunications in
 Y.2171. Thus retaining these in the NSIS-QSPEC is appropriate. They should not be changed or removed.</FONT></SPAN></DIV>  <DIV dir=ltr align=left><SPAN class=005322817-22022008><FONT face=Arial color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>  <DIV dir=ltr align=left><SPAN class=005322817-22022008><FONT face=Arial color=#0000ff size=2>Percy S. Tarapore</FONT></SPAN></DIV><BR>  <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>  <HR tabIndex=-1>  <FONT face=Tahoma size=2><B>From:</B> nsis-bounces@ietf.org [<A href="mailto:nsis-bounces@ietf.org">mailto:nsis-bounces@ietf.org</A>] <B>On Behalf Of </B>Gerald Ash<BR><B>Sent:</B> Thursday, February 21, 2008 11:56 AM<BR><B>To:</B> Francois Le Faucheur IMAP; Martin Stiemerling; <A href="mailto:john.loughney@nokia.com">john.loughney@nokia.com</A>; nsis<BR><B>Cc:</B> <A href="mailto:cornelia.kappler@googlemail.com">cornelia.kappler@googlemail.com</A><BR><B>Subject:</B> Re: [NSIS] Review of
 draft-ietf-nsis-qspec-18.txt<BR></FONT><BR></DIV>  <DIV></DIV>  <DIV><FONT face=arial>Francois, Martin, John, All,</FONT></DIV>  <DIV><FONT face=arial></FONT>&nbsp;</DIV>  <DIV><FONT face=arial>  <DIV><FONT face=arial>&gt;&gt;&gt; o Regarding Admission Priority:<BR>&gt;&gt;&gt; * every protocol spec will only indicate that "higher value</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;means higher priority".</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt; * there is no attempt to define what specific values should</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;be used for what. this is left outside the scope of the</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;protocol specs.<BR>&gt;&gt;&gt; * each protocol spec will add a statement clarifying that a</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;given Admission Priority is to be encoded with the same</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;value in each of the three protocol spec.
 For example, in</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;tsvwg-emergency-rsvp, under section 3.1. we will add:<BR>&gt;&gt;&gt; " A given Admission Priority is encoded in this information</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;element using the same value as when encoded in the</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;Admission Priority parameter defined in section 6.2.9 of</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;[nsis-qspec], or in the Admission Priority parameter</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;defined in section 4.10 of [dime-qos-parameters].</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt; In other words, a given value in any of the</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;[emergency-rsvp] Admission Priority information element,</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;the [nsis-qspec] Admission Priority parameter or the</FONT></DIV>  <DIV><FONT
 face=arial>&gt;&gt;&gt;&nbsp;[dime-qos-parameters] Admission Priority parameter,</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;refers to the same Admission Priority.</FONT></DIV>  <DIV><FONT face=arial></FONT>&nbsp;</DIV><FONT face=arial></FONT>  <DIV><FONT face=arial>&gt;&gt; The above proposed paragraph is really unclear.&nbsp; Which draft</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;is setting up IANA Registries to assign Admission Priority</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;parameters?&nbsp; The way it reads it sounds like all three drafts</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;are setting up registries but that somehow&nbsp;(magically) all&nbsp;refer</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;"to the same Admission Priority".&nbsp; How can that be if they</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;assign different values?&nbsp; Right now emergency-rsvp and</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;nsis-qspec
 set up registries for Admission Priority and</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;dime-qos-parameters is using the nsis-qspec registry as I</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;recall.</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt; Please clarify the proposal as to which draft is setting up a</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;registry for Admission Priority.&nbsp;</FONT></DIV>  <DIV><FONT face=arial><BR class=webkit-block-placeholder></FONT></DIV>  <DIV><FONT face=arial>&gt; No registry is setup.</FONT></DIV>  <DIV><FONT face=arial>&gt; It is up to a network administrator to decide how many/which</FONT></DIV>  <DIV><FONT face=arial>&gt;&nbsp;admission priority gets used for what. This is similar to how</FONT></DIV>  <DIV><FONT face=arial>&gt;&nbsp;Preemption is used (ie each network administrator may decide </FONT></DIV>  <DIV><FONT face=arial>&gt; to use it or not, may decide to use
 2,3,4,...128,.. levels...).</FONT></DIV>  <DIV><FONT face=arial>&gt; The statement above only says that the the same value of </FONT></DIV>  <DIV><FONT face=arial>&gt; admission priority should be used in the three protocols to refer </FONT></DIV>  <DIV><FONT face=arial>&gt; to same level of admission priority.</FONT></DIV>  <DIV><FONT color=#0000ff size=2></FONT>&nbsp;</DIV>  <DIV>That's a fundamental change to NSIS/QSPEC and does away with standardized Admission Priority values.&nbsp; QSPEC is following Y.1571 (now Y.2171 according to An Nguyen) in standardizing 3 priority levels to have end-to-end cross-domain significance.</DIV>  <DIV>&nbsp;</DIV>  <DIV>If we elimate this standardization, as is proposed, then different admission priority values&nbsp;can be&nbsp;assigned in different Admin domains, and will&nbsp;have no end-to-end significance.&nbsp; For example, Admin-domain 1, Admin-domain 2, and Admin-domain 3 assign&nbsp;admission priority=2,&nbsp;&nbsp;admission
 priority=4, admission priority=10 for the highest level priority, respectively.&nbsp; Admin-domain 1 and Admin-domain 2 try to initiate end-to-end flows via Admin-domain&nbsp;3 for a 'high priority' flow.&nbsp;&nbsp;However, Admin-domain 3 has no idea how to treat the flow admission priority since all 3 domains are using different encodings of high priority.</DIV>  <DIV>  <DIV>&nbsp;</DIV>  <DIV>Admission priority is not the same as preemption priority and should not be based on that model.</DIV>  <DIV>&nbsp;</DIV></DIV>  <DIV>IMO we should retain the standardized admission priority levels based on Y.1571/Y.2171.&nbsp; Otherwise, how do we achieve end-to-end, cross-domain standardization of admission priority?&nbsp; In any case, we need to see some good justification for the change.</DIV>  <DIV>&nbsp;</DIV>  <DIV>  <DIV><FONT face=arial>&gt;&gt; I saw no discussion of this proposed resolution on the NSIS list.&nbsp;</FONT></DIV>  <DIV><FONT face=arial><BR
 class=webkit-block-placeholder></FONT></DIV>  <DIV><FONT face=arial>&gt; which is why we've been assuming there was no issue with it. </FONT></DIV>  <DIV>&nbsp;</DIV>  <DIV>It isn't sufficient to&nbsp;declare 'silence is agreement' on making such a fundamental change.&nbsp; People should weigh in *on the list* and give their&nbsp;technical justifications and confirm their agreement (or disagreement).</DIV>  <DIV><FONT face=arial></FONT>&nbsp;</DIV>  <DIV><FONT face=arial>&gt;&gt; Who were the QSPEC co-authors who worked with you on the</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;proposed resolution?</FONT></DIV>  <DIV><FONT face=arial><BR class=webkit-block-placeholder></FONT></DIV>  <DIV><FONT face=arial>&gt; Attila, Cornelia and Dave Oran (+ NSIS WG chairs).</FONT></DIV>  <DIV><FONT color=#0000ff size=2></FONT>&nbsp;</DIV>  <DIV>So far I've not been able to verify agreement from the QSPEC co-authors as yet.&nbsp; We saw no discussion of the issue on the list, and
 there needs to be some explanation/justification for the change.&nbsp; </DIV>  <DIV>&nbsp;</DIV>  <DIV>Perhaps Francois could summarize the technical&nbsp;discussion amonst the co-authors, and also state who explicitly agreed (as opposed to who had no comment or active participation in the discussion).&nbsp;&nbsp;</DIV>  <DIV>&nbsp;</DIV>  <DIV>It would be good if the co-authors who participated&nbsp;in the discussion of the 'proposed agreement' could weigh in on the list with their technical view.</DIV>  <DIV>&nbsp;</DIV>  <DIV>Also, both NSIS chairs have said there is an agreement on the proposal, so perhaps they could weigh in on the list also with their technical view.</DIV>  <DIV>&nbsp;</DIV>  <DIV>Jerry</DIV></DIV></FONT><BR><BR><B><I>Francois Le Faucheur IMAP &lt;<A href="mailto:flefauch@cisco.com">flefauch@cisco.com</A>&gt;</I></B> wrote:</DIV>  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hello Jerry,  
 <DIV><BR>  <DIV>  <DIV>On 20 Feb 2008, at 16:58, Gerald Ash wrote:</DIV><BR class=Apple-interchange-newline>  <BLOCKQUOTE type="cite">  <DIV><FONT face="Courier&#13;&#10;&#13;&#10; New">Francois,</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">In your "Proposed Resolution" posting to NSIS on 3 December <A href="http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html</A>&nbsp;you say:</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">&gt; The Proposed Resolution<BR>&gt; ===================<BR>&gt; Co-authors of the three I-Ds as well as WG chairs of the </FONT></DIV>  <DIV><FONT face="Courier New">&gt; corresponding WGs converged on the following proposed </FONT></DIV>  <DIV><FONT face="Courier New">&gt; resolution. </FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">I
 saw no discussion of this proposed resolution on the NSIS list.&nbsp;</FONT></DIV></BLOCKQUOTE>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>which is why we've been assuming there was no issue with it. &nbsp;</DIV>  <DIV><BR class=webkit-block-placeholder></DIV><BR>  <BLOCKQUOTE type="cite">  <DIV><FONT face="Courier New">Who were the QSPEC co-authors who worked with you on the proposed resolution?</FONT></DIV></BLOCKQUOTE>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>Attila, Cornelia and Dave Oran (+ NSIS WG chairs).</DIV>  <DIV><BR></DIV><BR>  <BLOCKQUOTE type="cite">  <DIV>&nbsp;</DIV>  <DIV><FONT face="Courier New">&gt; o Regarding RPH-Priority:<BR>&gt; * tsvwg-emergency-rsvp will go ahead with its requests to</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;IANA </FONT><FONT face="Courier New">to provide numerical registry for RPH priority (via </FONT></DIV>  <DIV><FONT face="Courier New">&gt; extending existing RPH registry). See IANA
 Considerations</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;section of tsvwg-emergency-rsvp.</FONT></DIV>  <DIV><FONT face="Courier New">&gt; * nsis-qspec (in section 6.2.10) will point to this registry</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;instead of defining its own values</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">OK.</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">&gt; o Regarding Admission Priority:<BR>&gt; * every protocol spec will only indicate that "higher value</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;means higher priority".</FONT></DIV>  <DIV><FONT face="Courier New">&gt; * there is no attempt to define what specific values should</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;be used for what. this is left outside the scope of the</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;protocol specs.<BR>* each protocol
 spec will add a statement clarifying that a</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;given Admission Priority is to be encoded with the same</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;value in each of the three protocol spec. For example, in</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;tsvwg-emergency-rsvp, under section 3.1. we will add:<BR>" A given Admission Priority is encoded in this information</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;element using the same value as when encoded in the</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;Admission Priority parameter defined in section 6.2.9 of</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;[nsis-qspec], or in the Admission Priority parameter</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;defined in section 4.10 of [dime-qos-parameters].</FONT></DIV>  <DIV><FONT face="Courier New">&gt; In other words, a given value in any of the</FONT></DIV>  <DIV><FONT
 face="Courier New">&gt;&nbsp;[emergency-rsvp] Admission Priority information element,</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;the [nsis-qspec] Admission Priority parameter or the</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;[dime-qos-parameters] Admission Priority parameter,</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;refers to the same Admission Priority.<BR></FONT></DIV>  <DIV><FONT face="Courier New">The above proposed paragraph is really unclear.&nbsp; Which draft&nbsp;is setting up IANA Registries to assign Admission Priority parameters?&nbsp; The way it reads it sounds like all three drafts are setting up registries but that somehow&nbsp;(magically) all&nbsp;refer "to the same Admission Priority".&nbsp; How can that be if they assign different values?&nbsp; Right now emergency-rsvp and nsis-qspec set up registries for Admission Priority and dime-qos-parameters is using the nsis-qspec registry as I recall.</FONT></DIV>  <DIV><FONT
 face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">Please clarify the proposal as to which draft is setting up a registry for Admission Priority.&nbsp;</FONT></DIV></BLOCKQUOTE>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>No registry is setup.</DIV>  <DIV>It is up to a network administrator to decide how many/which admission priority gets used for what. This is similar to how Preemption is used (ie each network administrator may decide to use it or not, may decide to use 2,3,4,...128,.. levels...).</DIV>  <DIV>The statement above only says that the the same value of admission priority should be used in the three protocols to refer to same level of admission priority.</DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>Cheers</DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>Francois</DIV>  <DIV><BR class=webkit-block-placeholder></DIV><BR>  <BLOCKQUOTE type="cite">  <DIV><FONT face="Courier New">Also, please provide
 clearer&nbsp;proposed text to include in the drafts.&nbsp; </FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">It would be good to see some discussion of the proposal on the list, to confirm and validate agreement of the WG.</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">Jerry</FONT></DIV><FONT face="Courier New"></FONT>  <DIV><BR><BR><B><I>Francois Le Faucheur IMAP &lt;<A href="mailto:flefauch@cisco.com">flefauch@cisco.com</A>&gt;</I></B> wrote:</DIV>  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hello,<BR><BR>For memory, the next rev of nsis-qspec is also expected to be aligned <BR>with the Resolution of the issue related to QoS Parameters encoding <BR>in <DIME-QOS-PARAMETERS>, <NSIS-QSPEC>&amp; <TSVWG-EMEREGNCY-RSVP>. For <BR>convenience, I included below the recap on the corresponding <BR>resolution as announced on NSIS,
 DIME and TSVWG lists.<BR><BR>Just to make sure this does not fall through the cracks.<BR><BR>Cheers<BR><BR>Francois<BR><BR><BR>&gt;<BR>&gt; Begin forwarded message:<BR>&gt;&gt; From: Francois Le Faucheur IMAP <FLEFAUCH@CISCO.COM><BR>&gt;&gt; Date: 3 December 2007 12:05:42 GMT+01:00<BR>&gt;&gt; To: <A href="mailto:dime@ietf.org">dime@ietf.org</A>, <A href="mailto:nsis@ietf.org">nsis@ietf.org</A>, tsvwg tsvwg <TSVWG@IETF.ORG><BR>&gt;&gt; Cc: Francois Le Faucheur IMAP <FLEFAUCH@CISCO.COM>, David Oran R <BR>&gt;&gt; <ORAN@CISCO.COM>, Hannes Tschofenig <HANNES.TSCHOFENIG@GMX.NET>, <BR>&gt;&gt; ken carlberg <CARLBERG@G11.ORG.UK>, Magnus Westerlund <BR>&gt;&gt; <MAGNUS.WESTERLUND@ERICSSON.COM>, James Polk <JMPOLK@CISCO.COM>, <BR>&gt;&gt; <A href="mailto:cornelia.kappler@nsn.com">cornelia.kappler@nsn.com</A>, "(IJ/ETH) Báder Attila" <BR>&gt;&gt; <ATTILA.BADER@ERICSSON.COM>, <A href="mailto:jouni.korhonen@teliasonera.com">jouni.korhonen@teliasonera.com</A>, Jukka <BR>&gt;&gt;
 Manner MJ <JMANNER@CS.HELSINKI.FI>, tsvwg chair <TSVWG-><BR>&gt;&gt; <A href="mailto:chairs@tools.ietf.org">chairs@tools.ietf.org</A>&gt;, <A href="mailto:nsis-chairs@tools.ietf.org">nsis-chairs@tools.ietf.org</A>, dime- <BR>&gt;&gt; <A href="mailto:chairs@tools.ietf.org">chairs@tools.ietf.org</A>, "<A href="mailto:john.loughney@nokia.com">john.loughney@nokia.com</A>&gt;" <BR>&gt;&gt; <JOHN.LOUGHNEY@NOKIA.COM><BR>&gt;&gt; Subject: Resolution of issue QoS Parameters encoding in <DIME-QOS-><BR>&gt;&gt; parameters&gt;, <NSIS-QSPEC>&amp; <TSVWG-EMEREGNCY-RSVP><BR>&gt;&gt;<BR>&gt;&gt; Hello,<BR>&gt;&gt;<BR>&gt;&gt; The Issue:<BR>&gt;&gt; =======<BR>&gt;&gt; Three different documents (dime-qos-parameters, nsis-qos-nslp, <BR>&gt;&gt; tsvwg-emergency-rsvp) need to convey an overlapping set of QoS <BR>&gt;&gt; parameters (specifically RPH-Priority and Admission Priority) and <BR>&gt;&gt; currently do that in an inconsistent manner. This has been brought <BR>&gt;&gt; up and
 partially discussed on the WG mailing lists.<BR>&gt;&gt;<BR>&gt;&gt; The Proposed Resolution<BR>&gt;&gt; ===================<BR>&gt;&gt; Co-authors of the three I-Ds as well as WG chairs of the <BR>&gt;&gt; corresponding WGs converged on the following proposed resolution. <BR>&gt;&gt; Please let us know if you have an issue/concern with this.<BR>&gt;&gt;<BR>&gt;&gt; o Regarding RPH-Priority:<BR>&gt;&gt; * tsvwg-emergency-rsvp will go ahead with its requests to IANA to <BR>&gt;&gt; provide numerical registry for RPH priority (via extending <BR>&gt;&gt; existing RPH registry). See IANA Considerations section of tsvwg- <BR>&gt;&gt; emergency-rsvp.<BR>&gt;&gt; * nsis-qspec (in section 6.2.10) will point to this registry <BR>&gt;&gt; instead of defining its own values<BR>&gt;&gt; * dime-qos-parameters (in section 4.11) will point to this <BR>&gt;&gt; registry instead of defining its own values<BR>&gt;&gt; * tsvwg-emergency-rsvp (in section 3.2) will keep pointing to
 <BR>&gt;&gt; this registry.<BR>&gt;&gt;<BR>&gt;&gt; o Regarding Admission Priority:<BR>&gt;&gt; * every protocol spec will only indicate that "higher value means <BR>&gt;&gt; higher priority".<BR>&gt;&gt; * there is no attempt to define what specific values should be <BR>&gt;&gt; used for what. this is left outside the scope of the protocol specs.<BR>&gt;&gt; * each protocol spec will add a statement clarifying that a given <BR>&gt;&gt; Admission Priority is to be encoded with the same value in each of <BR>&gt;&gt; the three protocol spec. For example, in tsvwg-emergency-rsvp, <BR>&gt;&gt; under section 3.1. we will add:<BR>&gt;&gt; " A given Admission Priority is encoded in this information <BR>&gt;&gt; element<BR>&gt;&gt; using the same value as when encoded in the Admission Priority<BR>&gt;&gt; parameter defined in section 6.2.9 of [nsis-qspec], or in the <BR>&gt;&gt; Admission<BR>&gt;&gt; Priority parameter defined in section 4.10 of [dime-qos- <BR>&gt;&gt;
 parameters].<BR>&gt;&gt; In other words, a given value in any of the [emergency-rsvp] <BR>&gt;&gt; Admission<BR>&gt;&gt; Priority information element, the [nsis-qspec] Admission Priority <BR>&gt;&gt; parameter<BR>&gt;&gt; or the [dime-qos-parameters] Admission Priority parameter, refers to<BR>&gt;&gt; the same Admission Priority.<BR>&gt;&gt; "<BR>&gt;&gt; * the mirror statement will be added in nsis-qspec (section <BR>&gt;&gt; 6.2.9) and dime-qos-parameters (section 4.10)<BR>&gt;&gt;<BR>&gt;&gt; Francois<BR>&gt;&gt;</BLOCKQUOTE></BLOCKQUOTE></DIV></DIV></BLOCKQUOTE></BLOCKQUOTE></DIV></DIV></BLOCKQUOTE><p>&#32;



      <hr size=1>Never miss a thing.  <a href="http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs"> Make Yahoo your homepage.</a>


--0-1829644322-1203781547=:82097--

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

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

--===============0665998287==--


From nsis-bounces@ietf.org  Sat Feb 23 07:47:48 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4D0A728C3B1;
	Sat, 23 Feb 2008 07:47:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.561
X-Spam-Level: *
X-Spam-Status: No, score=1.561 tagged_above=-999 required=5 tests=[AWL=-0.114,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=1, MIME_HTML_MOSTLY=0.001,
	RDNS_NONE=0.1, 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 wztPdRuQWSXr; Sat, 23 Feb 2008 07:47:46 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F1C2D3A6A92;
	Sat, 23 Feb 2008 07:47:45 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 43B6E28C31D
	for <nsis@core3.amsl.com>; Sat, 23 Feb 2008 07:47:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 vej0BvlrTaby for <nsis@core3.amsl.com>;
	Sat, 23 Feb 2008 07:47:42 -0800 (PST)
Received: from web63615.mail.re1.yahoo.com (web63615.mail.re1.yahoo.com
	[69.147.97.85]) by core3.amsl.com (Postfix) with SMTP id A398C3A6A16
	for <nsis@ietf.org>; Sat, 23 Feb 2008 07:47:41 -0800 (PST)
Received: (qmail 37734 invoked by uid 60001); 23 Feb 2008 15:47:36 -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=xzXfD3RAcgo4Al5H4Uq4gTm9kI1zsmFUjF/XKiieSlw40NNsvq43pHyBaiwn81w203qmylikzQQ3/rTJ0H10mbC3DkV/uYeYNrC1NP0xsqfSlUVpwzPSPE2X9zha8L/aMqdnIimxtS+YbhAfxNbPJSd9Ih6qMlC5tffNtBeHi58=;
X-YMail-OSG: vE0BwtQVM1mOjOmBCGEla.J0_fYXu4esFdFn17uzqRTkNuiQTnFDzUw9mhjBCAVMHnbNISZGxm5cM0oJTRqKzBOndwL4CNmoVUL_
Received: from [76.19.255.157] by web63615.mail.re1.yahoo.com via HTTP;
	Sat, 23 Feb 2008 07:47:36 PST
Date: Sat, 23 Feb 2008 07:47:36 -0800 (PST)
From: Gerald Ash <gash5107@yahoo.com>
To: Martin Stiemerling <Stiemerling@nw.neclab.eu>, john.loughney@nokia.com,
	nsis <nsis@ietf.org>
In-Reply-To: <505424.79660.qm@web63613.mail.re1.yahoo.com>
MIME-Version: 1.0
Message-ID: <445889.37182.qm@web63615.mail.re1.yahoo.com>
Cc: cornelia.kappler@googlemail.com
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0657139471=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

--===============0657139471==
Content-Type: multipart/alternative; boundary="0-431395853-1203781656=:37182"
Content-Transfer-Encoding: 8bit

--0-431395853-1203781656=:37182
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Martin, John, All,
   
  We've not seen justification for a fundamental change to NSIS/QSPEC that does away with standardized Admission Priority values, as proposed in http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html.  QSPEC is following Y.2171 in standardizing 3 priority levels to have end-to-end cross-domain significance.  Having domain-specific assignments can't possibly work across domains if each network administrator decides a different set of priority levels and encodings.
   
  Adoption of the extension to the RPH Priority registry specified in [EMERGENCY-RSVP], as proposed in http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html, is fine.
     

    However, without justification there is no reason to change the NSIS/QSPEC approach to admission priority or eliminate the admission priority IANA registry at this point.  If valid arguments come forward later (*on the list*) to make a change, we can do it then of course.

   
  Jerry


Gerald Ash <gash5107@yahoo.com> wrote:
    Francois, Martin, John, All,
   
    >>> o Regarding Admission Priority:
>>> * every protocol spec will only indicate that "higher value
  >>> means higher priority".
  >>> * there is no attempt to define what specific values should
  >>> be used for what. this is left outside the scope of the
  >>> protocol specs.
>>> * each protocol spec will add a statement clarifying that a
  >>> given Admission Priority is to be encoded with the same
  >>> value in each of the three protocol spec. For example, in
  >>> tsvwg-emergency-rsvp, under section 3.1. we will add:
>>> " A given Admission Priority is encoded in this information
  >>> element using the same value as when encoded in the
  >>> Admission Priority parameter defined in section 6.2.9 of
  >>> [nsis-qspec], or in the Admission Priority parameter
  >>> defined in section 4.10 of [dime-qos-parameters].
  >>> In other words, a given value in any of the
  >>> [emergency-rsvp] Admission Priority information element,
  >>> the [nsis-qspec] Admission Priority parameter or the
  >>> [dime-qos-parameters] Admission Priority parameter,
  >>> refers to the same Admission Priority.
   
  >> The above proposed paragraph is really unclear.  Which draft
  >> is setting up IANA Registries to assign Admission Priority
  >> parameters?  The way it reads it sounds like all three drafts
  >> are setting up registries but that somehow (magically) all refer
  >> "to the same Admission Priority".  How can that be if they
  >> assign different values?  Right now emergency-rsvp and
  >> nsis-qspec set up registries for Admission Priority and
  >> dime-qos-parameters is using the nsis-qspec registry as I
  >> recall.
  >>
  >> Please clarify the proposal as to which draft is setting up a
  >> registry for Admission Priority. 
  

  > No registry is setup.
  > It is up to a network administrator to decide how many/which
  > admission priority gets used for what. This is similar to how
  > Preemption is used (ie each network administrator may decide 
  > to use it or not, may decide to use 2,3,4,...128,.. levels...).
  > The statement above only says that the the same value of 
  > admission priority should be used in the three protocols to refer 
  > to same level of admission priority.
   
  That's a fundamental change to NSIS/QSPEC and does away with standardized Admission Priority values.  QSPEC is following Y.1571 (now Y.2171 according to An Nguyen) in standardizing 3 priority levels to have end-to-end cross-domain significance.
   
  If we elimate this standardization, as is proposed, then different admission priority values can be assigned in different Admin domains, and will have no end-to-end significance.  For example, Admin-domain 1, Admin-domain 2, and Admin-domain 3 assign admission priority=2,  admission priority=4, admission priority=10 for the highest level priority, respectively.  Admin-domain 1 and Admin-domain 2 try to initiate end-to-end flows via Admin-domain 3 for a 'high priority' flow.  However, Admin-domain 3 has no idea how to treat the flow admission priority since all 3 domains are using different encodings of high priority.
     
  Admission priority is not the same as preemption priority and should not be based on that model.
   

  IMO we should retain the standardized admission priority levels based on Y.1571/Y.2171.  Otherwise, how do we achieve end-to-end, cross-domain standardization of admission priority?  In any case, we need to see some good justification for the change.
   
    >> I saw no discussion of this proposed resolution on the NSIS list. 
  

  > which is why we've been assuming there was no issue with it. 
   
  It isn't sufficient to declare 'silence is agreement' on making such a fundamental change.  People should weigh in *on the list* and give their technical justifications and confirm their agreement (or disagreement).
   
  >> Who were the QSPEC co-authors who worked with you on the
  >> proposed resolution?
  

  > Attila, Cornelia and Dave Oran (+ NSIS WG chairs).
   
  So far I've not been able to verify agreement from the QSPEC co-authors as yet.  We saw no discussion of the issue on the list, and there needs to be some explanation/justification for the change.  
   
  Perhaps Francois could summarize the technical discussion amonst the co-authors, and also state who explicitly agreed (as opposed to who had no comment or active participation in the discussion).  
   
  It would be good if the co-authors who participated in the discussion of the 'proposed agreement' could weigh in on the list with their technical view.
   
  Also, both NSIS chairs have said there is an agreement on the proposal, so perhaps they could weigh in on the list also with their technical view.
   
  Jerry



Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:
  Hello Jerry,   
    On 20 Feb 2008, at 16:58, Gerald Ash wrote:

    Francois,
   
  In your "Proposed Resolution" posting to NSIS on 3 December http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html you say:
   
  > The Proposed Resolution
> ===================
> Co-authors of the three I-Ds as well as WG chairs of the 
  > corresponding WGs converged on the following proposed 
  > resolution. 
   
  I saw no discussion of this proposed resolution on the NSIS list. 
  

  which is why we've been assuming there was no issue with it.  
  


    Who were the QSPEC co-authors who worked with you on the proposed resolution?
  

  Attila, Cornelia and Dave Oran (+ NSIS WG chairs).
  


     
  > o Regarding RPH-Priority:
> * tsvwg-emergency-rsvp will go ahead with its requests to
  > IANA to provide numerical registry for RPH priority (via 
  > extending existing RPH registry). See IANA Considerations
  > section of tsvwg-emergency-rsvp.
  > * nsis-qspec (in section 6.2.10) will point to this registry
  > instead of defining its own values
   
  OK.
   
  > o Regarding Admission Priority:
> * every protocol spec will only indicate that "higher value
  > means higher priority".
  > * there is no attempt to define what specific values should
  > be used for what. this is left outside the scope of the
  > protocol specs.
* each protocol spec will add a statement clarifying that a
  > given Admission Priority is to be encoded with the same
  > value in each of the three protocol spec. For example, in
  > tsvwg-emergency-rsvp, under section 3.1. we will add:
" A given Admission Priority is encoded in this information
  > element using the same value as when encoded in the
  > Admission Priority parameter defined in section 6.2.9 of
  > [nsis-qspec], or in the Admission Priority parameter
  > defined in section 4.10 of [dime-qos-parameters].
  > In other words, a given value in any of the
  > [emergency-rsvp] Admission Priority information element,
  > the [nsis-qspec] Admission Priority parameter or the
  > [dime-qos-parameters] Admission Priority parameter,
  > refers to the same Admission Priority.

  The above proposed paragraph is really unclear.  Which draft is setting up IANA Registries to assign Admission Priority parameters?  The way it reads it sounds like all three drafts are setting up registries but that somehow (magically) all refer "to the same Admission Priority".  How can that be if they assign different values?  Right now emergency-rsvp and nsis-qspec set up registries for Admission Priority and dime-qos-parameters is using the nsis-qspec registry as I recall.
   
  Please clarify the proposal as to which draft is setting up a registry for Admission Priority. 
  

  No registry is setup.
  It is up to a network administrator to decide how many/which admission priority gets used for what. This is similar to how Preemption is used (ie each network administrator may decide to use it or not, may decide to use 2,3,4,...128,.. levels...).
  The statement above only says that the the same value of admission priority should be used in the three protocols to refer to same level of admission priority.
  

  Cheers
  

  Francois
  


    Also, please provide clearer proposed text to include in the drafts.  
   
  It would be good to see some discussion of the proposal on the list, to confirm and validate agreement of the WG.
   
  Jerry
  

Francois Le Faucheur IMAP <flefauch@cisco.com> wrote:
  Hello,

For memory, the next rev of nsis-qspec is also expected to be aligned 
with the Resolution of the issue related to QoS Parameters encoding 
in , & . For 
convenience, I included below the recap on the corresponding 
resolution as announced on NSIS, DIME and TSVWG lists.

Just to make sure this does not fall through the cracks.

Cheers

Francois


>
> Begin forwarded message:
>> From: Francois Le Faucheur IMAP 
>> Date: 3 December 2007 12:05:42 GMT+01:00
>> To: dime@ietf.org, nsis@ietf.org, tsvwg tsvwg 
>> Cc: Francois Le Faucheur IMAP , David Oran R 
>> , Hannes Tschofenig , 
>> ken carlberg , Magnus Westerlund 
>> , James Polk , 
>> cornelia.kappler@nsn.com, "(IJ/ETH) Báder Attila" 
>> , jouni.korhonen@teliasonera.com, Jukka 
>> Manner MJ , tsvwg chair 
>> chairs@tools.ietf.org>, nsis-chairs@tools.ietf.org, dime- 
>> chairs@tools.ietf.org, "john.loughney@nokia.com>" 
>> 
>> Subject: Resolution of issue QoS Parameters encoding in 
>> parameters>, & 
>>
>> Hello,
>>
>> The Issue:
>> =======
>> Three different documents (dime-qos-parameters, nsis-qos-nslp, 
>> tsvwg-emergency-rsvp) need to convey an overlapping set of QoS 
>> parameters (specifically RPH-Priority and Admission Priority) and 
>> currently do that in an inconsistent manner. This has been brought 
>> up and partially discussed on the WG mailing lists.
>>
>> The Proposed Resolution
>> ===================
>> Co-authors of the three I-Ds as well as WG chairs of the 
>> corresponding WGs converged on the following proposed resolution. 
>> Please let us know if you have an issue/concern with this.
>>
>> o Regarding RPH-Priority:
>> * tsvwg-emergency-rsvp will go ahead with its requests to IANA to 
>> provide numerical registry for RPH priority (via extending 
>> existing RPH registry). See IANA Considerations section of tsvwg- 
>> emergency-rsvp.
>> * nsis-qspec (in section 6.2.10) will point to this registry 
>> instead of defining its own values
>> * dime-qos-parameters (in section 4.11) will point to this 
>> registry instead of defining its own values
>> * tsvwg-emergency-rsvp (in section 3.2) will keep pointing to 
>> this registry.
>>
>> o Regarding Admission Priority:
>> * every protocol spec will only indicate that "higher value means 
>> higher priority".
>> * there is no attempt to define what specific values should be 
>> used for what. this is left outside the scope of the protocol specs.
>> * each protocol spec will add a statement clarifying that a given 
>> Admission Priority is to be encoded with the same value in each of 
>> the three protocol spec. For example, in tsvwg-emergency-rsvp, 
>> under section 3.1. we will add:
>> " A given Admission Priority is encoded in this information 
>> element
>> using the same value as when encoded in the Admission Priority
>> parameter defined in section 6.2.9 of [nsis-qspec], or in the 
>> Admission
>> Priority parameter defined in section 4.10 of [dime-qos- 
>> parameters].
>> In other words, a given value in any of the [emergency-rsvp] 
>> Admission
>> Priority information element, the [nsis-qspec] Admission Priority 
>> parameter
>> or the [dime-qos-parameters] Admission Priority parameter, refers to
>> the same Admission Priority.
>> "
>> * the mirror statement will be added in nsis-qspec (section 
>> 6.2.9) and dime-qos-parameters (section 4.10)
>>
>> Francois
>>


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

<DIV>Martin, John, All,</DIV>  <DIV>&nbsp;</DIV>  <DIV>We've not seen justification for&nbsp;a fundamental change to NSIS/QSPEC&nbsp;that does away with standardized Admission Priority values, as proposed in <A href="http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html</A>.&nbsp; QSPEC&nbsp;is following Y.2171&nbsp;in standardizing 3 priority levels to have end-to-end cross-domain significance.&nbsp; Having domain-specific assignments&nbsp;can't possibly work across domains if each network administrator decides a different set of priority levels and encodings.</DIV>  <DIV>&nbsp;</DIV>  <DIV>Adoption of the extension to the RPH Priority registry specified in&nbsp;[EMERGENCY-RSVP], as proposed in <A href="http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html</A>,&nbsp;is fine.</DIV>  <DIV>  <DIV>&nbsp;</DIV></DIV>  <DIV> 
 <DIV>However, without justification there is no reason to change the NSIS/QSPEC approach to admission priority or eliminate the admission priority IANA registry at this point.&nbsp; If valid arguments come forward&nbsp;later (*on the list*) to make a change, we can do it then of course.</DIV></DIV>  <DIV>&nbsp;</DIV>  <DIV>Jerry<BR><BR><BR><B><I>Gerald Ash &lt;gash5107@yahoo.com&gt;</I></B> wrote:</DIV>  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">  <DIV><FONT face=arial>Francois, Martin, John, All,</FONT></DIV>  <DIV><FONT face=arial></FONT>&nbsp;</DIV>  <DIV><FONT face=arial>  <DIV><FONT face=arial>&gt;&gt;&gt; o Regarding Admission Priority:<BR>&gt;&gt;&gt; * every protocol spec will only indicate that "higher value</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;means higher priority".</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt; * there is no attempt to define what specific values should</FONT></DIV> 
 <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;be used for what. this is left outside the scope of the</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;protocol specs.<BR>&gt;&gt;&gt; * each protocol spec will add a statement clarifying that a</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;given Admission Priority is to be encoded with the same</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;value in each of the three protocol spec. For example, in</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;tsvwg-emergency-rsvp, under section 3.1. we will add:<BR>&gt;&gt;&gt; " A given Admission Priority is encoded in this information</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;element using the same value as when encoded in the</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;Admission Priority parameter defined in section 6.2.9 of</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;[nsis-qspec], or in the Admission Priority parameter</FONT></DIV> 
 <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;defined in section 4.10 of [dime-qos-parameters].</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt; In other words, a given value in any of the</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;[emergency-rsvp] Admission Priority information element,</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;the [nsis-qspec] Admission Priority parameter or the</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;[dime-qos-parameters] Admission Priority parameter,</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&gt;&nbsp;refers to the same Admission Priority.</FONT></DIV>  <DIV><FONT face=arial>&nbsp;</DIV></FONT>  <DIV><FONT face=arial>&gt;&gt; The above proposed paragraph is really unclear.&nbsp; Which draft</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;is setting up IANA Registries to assign Admission Priority</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;parameters?&nbsp; The way it reads it sounds like all three
 drafts</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;are setting up registries but that somehow&nbsp;(magically) all&nbsp;refer</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;"to the same Admission Priority".&nbsp; How can that be if they</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;assign different values?&nbsp; Right now emergency-rsvp and</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;nsis-qspec set up registries for Admission Priority and</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;dime-qos-parameters is using the nsis-qspec registry as I</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;recall.</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt; Please clarify the proposal as to which draft is setting up a</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;registry for Admission Priority.&nbsp;</FONT></DIV>  <DIV><FONT face=arial><BR class=webkit-block-placeholder></FONT></DIV>  <DIV><FONT face=arial>&gt; No
 registry is setup.</FONT></DIV>  <DIV><FONT face=arial>&gt; It is up to a network administrator to decide how many/which</FONT></DIV>  <DIV><FONT face=arial>&gt;&nbsp;admission priority gets used for what. This is similar to how</FONT></DIV>  <DIV><FONT face=arial>&gt;&nbsp;Preemption is used (ie each network administrator may decide </FONT></DIV>  <DIV><FONT face=arial>&gt; to use it or not, may decide to use 2,3,4,...128,.. levels...).</FONT></DIV>  <DIV><FONT face=arial>&gt; The statement above only says that the the same value of </FONT></DIV>  <DIV><FONT face=arial>&gt; admission priority should be used in the three protocols to refer </FONT></DIV>  <DIV><FONT face=arial>&gt; to same level of admission priority.</FONT></DIV>  <DIV>&nbsp;</DIV>  <DIV>That's a fundamental change to NSIS/QSPEC and does away with standardized Admission Priority values.&nbsp; QSPEC is following Y.1571 (now Y.2171 according to An Nguyen) in standardizing 3 priority levels to have end-to-end
 cross-domain significance.</DIV>  <DIV>&nbsp;</DIV>  <DIV>If we elimate this standardization, as is proposed, then different admission priority values&nbsp;can be&nbsp;assigned in different Admin domains, and will&nbsp;have no end-to-end significance.&nbsp; For example, Admin-domain 1, Admin-domain 2, and Admin-domain 3 assign&nbsp;admission priority=2,&nbsp;&nbsp;admission priority=4, admission priority=10 for the highest level priority, respectively.&nbsp; Admin-domain 1 and Admin-domain 2 try to initiate end-to-end flows via Admin-domain&nbsp;3 for a 'high priority' flow.&nbsp;&nbsp;However, Admin-domain 3 has no idea how to treat the flow admission priority since all 3 domains are using different encodings of high priority.</DIV>  <DIV>  <DIV>&nbsp;</DIV>  <DIV>Admission priority is not the same as preemption priority and should not be based on that model.</DIV>  <DIV>&nbsp;</DIV></DIV>  <DIV>IMO we should retain the standardized admission priority levels based on
 Y.1571/Y.2171.&nbsp; Otherwise, how do we achieve end-to-end, cross-domain standardization of admission priority?&nbsp; In any case, we need to see some good justification for the change.</DIV>  <DIV>&nbsp;</DIV>  <DIV>  <DIV><FONT face=arial>&gt;&gt; I saw no discussion of this proposed resolution on the NSIS list.&nbsp;</FONT></DIV>  <DIV><FONT face=arial><BR class=webkit-block-placeholder></FONT></DIV>  <DIV><FONT face=arial>&gt; which is why we've been assuming there was no issue with it. </FONT></DIV>  <DIV>&nbsp;</DIV>  <DIV>It isn't sufficient to&nbsp;declare 'silence is agreement' on making such a fundamental change.&nbsp; People should weigh in *on the list* and give their&nbsp;technical justifications and confirm their agreement (or disagreement).</DIV>  <DIV><FONT face=arial></FONT>&nbsp;</DIV>  <DIV><FONT face=arial>&gt;&gt; Who were the QSPEC co-authors who worked with you on the</FONT></DIV>  <DIV><FONT face=arial>&gt;&gt;&nbsp;proposed
 resolution?</FONT></DIV>  <DIV><FONT face=arial><BR class=webkit-block-placeholder></FONT></DIV>  <DIV><FONT face=arial>&gt; Attila, Cornelia and Dave Oran (+ NSIS WG chairs).</FONT></DIV>  <DIV>&nbsp;</DIV>  <DIV>So far I've not been able to verify agreement from the QSPEC co-authors as yet.&nbsp; We saw no discussion of the issue on the list, and there needs to be some explanation/justification for the change.&nbsp; </DIV>  <DIV>&nbsp;</DIV>  <DIV>Perhaps Francois could summarize the technical&nbsp;discussion amonst the co-authors, and also state who explicitly agreed (as opposed to who had no comment or active participation in the discussion).&nbsp;&nbsp;</DIV>  <DIV>&nbsp;</DIV>  <DIV>It would be good if the co-authors who participated&nbsp;in the discussion of the 'proposed agreement' could weigh in on the list with their technical view.</DIV>  <DIV>&nbsp;</DIV>  <DIV>Also, both NSIS chairs have said there is an agreement on the proposal, so perhaps they could weigh
 in on the list also with their technical view.</DIV>  <DIV>&nbsp;</DIV>  <DIV>Jerry</DIV></DIV></FONT><BR><BR><B><I>Francois Le Faucheur IMAP &lt;flefauch@cisco.com&gt;</I></B> wrote:</DIV>  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hello Jerry,   <DIV><BR>  <DIV>  <DIV>On 20 Feb 2008, at 16:58, Gerald Ash wrote:</DIV><BR class=Apple-interchange-newline>  <BLOCKQUOTE type="cite">  <DIV><FONT face="Courier&#13;&#10; New">Francois,</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">In your "Proposed Resolution" posting to NSIS on 3 December <A href="http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html</A>&nbsp;you say:</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">&gt; The Proposed Resolution<BR>&gt; ===================<BR>&gt; Co-authors of the three
 I-Ds as well as WG chairs of the </FONT></DIV>  <DIV><FONT face="Courier New">&gt; corresponding WGs converged on the following proposed </FONT></DIV>  <DIV><FONT face="Courier New">&gt; resolution. </FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">I saw no discussion of this proposed resolution on the NSIS list.&nbsp;</FONT></DIV></BLOCKQUOTE>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>which is why we've been assuming there was no issue with it. &nbsp;</DIV>  <DIV><BR class=webkit-block-placeholder></DIV><BR>  <BLOCKQUOTE type="cite">  <DIV><FONT face="Courier New">Who were the QSPEC co-authors who worked with you on the proposed resolution?</FONT></DIV></BLOCKQUOTE>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>Attila, Cornelia and Dave Oran (+ NSIS WG chairs).</DIV>  <DIV><BR></DIV><BR>  <BLOCKQUOTE type="cite">  <DIV>&nbsp;</DIV>  <DIV><FONT face="Courier New">&gt; o Regarding RPH-Priority:<BR>&gt; *
 tsvwg-emergency-rsvp will go ahead with its requests to</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;IANA </FONT><FONT face="Courier New">to provide numerical registry for RPH priority (via </FONT></DIV>  <DIV><FONT face="Courier New">&gt; extending existing RPH registry). See IANA Considerations</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;section of tsvwg-emergency-rsvp.</FONT></DIV>  <DIV><FONT face="Courier New">&gt; * nsis-qspec (in section 6.2.10) will point to this registry</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;instead of defining its own values</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">OK.</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">&gt; o Regarding Admission Priority:<BR>&gt; * every protocol spec will only indicate that "higher value</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;means higher priority".</FONT></DIV> 
 <DIV><FONT face="Courier New">&gt; * there is no attempt to define what specific values should</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;be used for what. this is left outside the scope of the</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;protocol specs.<BR>* each protocol spec will add a statement clarifying that a</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;given Admission Priority is to be encoded with the same</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;value in each of the three protocol spec. For example, in</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;tsvwg-emergency-rsvp, under section 3.1. we will add:<BR>" A given Admission Priority is encoded in this information</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;element using the same value as when encoded in the</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;Admission Priority parameter defined in section 6.2.9 of</FONT></DIV>  <DIV><FONT face="Courier
 New">&gt;&nbsp;[nsis-qspec], or in the Admission Priority parameter</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;defined in section 4.10 of [dime-qos-parameters].</FONT></DIV>  <DIV><FONT face="Courier New">&gt; In other words, a given value in any of the</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;[emergency-rsvp] Admission Priority information element,</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;the [nsis-qspec] Admission Priority parameter or the</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;[dime-qos-parameters] Admission Priority parameter,</FONT></DIV>  <DIV><FONT face="Courier New">&gt;&nbsp;refers to the same Admission Priority.<BR></FONT></DIV>  <DIV><FONT face="Courier New">The above proposed paragraph is really unclear.&nbsp; Which draft&nbsp;is setting up IANA Registries to assign Admission Priority parameters?&nbsp; The way it reads it sounds like all three drafts are setting up registries but that somehow&nbsp;(magically)
 all&nbsp;refer "to the same Admission Priority".&nbsp; How can that be if they assign different values?&nbsp; Right now emergency-rsvp and nsis-qspec set up registries for Admission Priority and dime-qos-parameters is using the nsis-qspec registry as I recall.</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">Please clarify the proposal as to which draft is setting up a registry for Admission Priority.&nbsp;</FONT></DIV></BLOCKQUOTE>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>No registry is setup.</DIV>  <DIV>It is up to a network administrator to decide how many/which admission priority gets used for what. This is similar to how Preemption is used (ie each network administrator may decide to use it or not, may decide to use 2,3,4,...128,.. levels...).</DIV>  <DIV>The statement above only says that the the same value of admission priority should be used in the three protocols to refer to same level of admission
 priority.</DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>Cheers</DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>Francois</DIV>  <DIV><BR class=webkit-block-placeholder></DIV><BR>  <BLOCKQUOTE type="cite">  <DIV><FONT face="Courier New">Also, please provide clearer&nbsp;proposed text to include in the drafts.&nbsp; </FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">It would be good to see some discussion of the proposal on the list, to confirm and validate agreement of the WG.</FONT></DIV>  <DIV><FONT face="Courier New"></FONT>&nbsp;</DIV>  <DIV><FONT face="Courier New">Jerry</FONT></DIV><FONT face="Courier New"></FONT>  <DIV><BR><BR><B><I>Francois Le Faucheur IMAP &lt;<A href="mailto:flefauch@cisco.com">flefauch@cisco.com</A>&gt;</I></B> wrote:</DIV>  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hello,<BR><BR>For memory, the next rev of nsis-qspec
 is also expected to be aligned <BR>with the Resolution of the issue related to QoS Parameters encoding <BR>in <DIME-QOS-PARAMETERS>, <NSIS-QSPEC>&amp; <TSVWG-EMEREGNCY-RSVP>. For <BR>convenience, I included below the recap on the corresponding <BR>resolution as announced on NSIS, DIME and TSVWG lists.<BR><BR>Just to make sure this does not fall through the cracks.<BR><BR>Cheers<BR><BR>Francois<BR><BR><BR>&gt;<BR>&gt; Begin forwarded message:<BR>&gt;&gt; From: Francois Le Faucheur IMAP <FLEFAUCH@CISCO.COM><BR>&gt;&gt; Date: 3 December 2007 12:05:42 GMT+01:00<BR>&gt;&gt; To: <A href="mailto:dime@ietf.org">dime@ietf.org</A>, <A href="mailto:nsis@ietf.org">nsis@ietf.org</A>, tsvwg tsvwg <TSVWG@IETF.ORG><BR>&gt;&gt; Cc: Francois Le Faucheur IMAP <FLEFAUCH@CISCO.COM>, David Oran R <BR>&gt;&gt; <ORAN@CISCO.COM>, Hannes Tschofenig <HANNES.TSCHOFENIG@GMX.NET>, <BR>&gt;&gt; ken carlberg <CARLBERG@G11.ORG.UK>, Magnus Westerlund <BR>&gt;&gt; <MAGNUS.WESTERLUND@ERICSSON.COM>, James
 Polk <JMPOLK@CISCO.COM>, <BR>&gt;&gt; <A href="mailto:cornelia.kappler@nsn.com">cornelia.kappler@nsn.com</A>, "(IJ/ETH) Báder Attila" <BR>&gt;&gt; <ATTILA.BADER@ERICSSON.COM>, <A href="mailto:jouni.korhonen@teliasonera.com">jouni.korhonen@teliasonera.com</A>, Jukka <BR>&gt;&gt; Manner MJ <JMANNER@CS.HELSINKI.FI>, tsvwg chair <TSVWG-><BR>&gt;&gt; <A href="mailto:chairs@tools.ietf.org">chairs@tools.ietf.org</A>&gt;, <A href="mailto:nsis-chairs@tools.ietf.org">nsis-chairs@tools.ietf.org</A>, dime- <BR>&gt;&gt; <A href="mailto:chairs@tools.ietf.org">chairs@tools.ietf.org</A>, "<A href="mailto:john.loughney@nokia.com">john.loughney@nokia.com</A>&gt;" <BR>&gt;&gt; <JOHN.LOUGHNEY@NOKIA.COM><BR>&gt;&gt; Subject: Resolution of issue QoS Parameters encoding in <DIME-QOS-><BR>&gt;&gt; parameters&gt;, <NSIS-QSPEC>&amp; <TSVWG-EMEREGNCY-RSVP><BR>&gt;&gt;<BR>&gt;&gt; Hello,<BR>&gt;&gt;<BR>&gt;&gt; The Issue:<BR>&gt;&gt; =======<BR>&gt;&gt; Three different documents (dime-qos-parameters,
 nsis-qos-nslp, <BR>&gt;&gt; tsvwg-emergency-rsvp) need to convey an overlapping set of QoS <BR>&gt;&gt; parameters (specifically RPH-Priority and Admission Priority) and <BR>&gt;&gt; currently do that in an inconsistent manner. This has been brought <BR>&gt;&gt; up and partially discussed on the WG mailing lists.<BR>&gt;&gt;<BR>&gt;&gt; The Proposed Resolution<BR>&gt;&gt; ===================<BR>&gt;&gt; Co-authors of the three I-Ds as well as WG chairs of the <BR>&gt;&gt; corresponding WGs converged on the following proposed resolution. <BR>&gt;&gt; Please let us know if you have an issue/concern with this.<BR>&gt;&gt;<BR>&gt;&gt; o Regarding RPH-Priority:<BR>&gt;&gt; * tsvwg-emergency-rsvp will go ahead with its requests to IANA to <BR>&gt;&gt; provide numerical registry for RPH priority (via extending <BR>&gt;&gt; existing RPH registry). See IANA Considerations section of tsvwg- <BR>&gt;&gt; emergency-rsvp.<BR>&gt;&gt; * nsis-qspec (in section 6.2.10) will point to this
 registry <BR>&gt;&gt; instead of defining its own values<BR>&gt;&gt; * dime-qos-parameters (in section 4.11) will point to this <BR>&gt;&gt; registry instead of defining its own values<BR>&gt;&gt; * tsvwg-emergency-rsvp (in section 3.2) will keep pointing to <BR>&gt;&gt; this registry.<BR>&gt;&gt;<BR>&gt;&gt; o Regarding Admission Priority:<BR>&gt;&gt; * every protocol spec will only indicate that "higher value means <BR>&gt;&gt; higher priority".<BR>&gt;&gt; * there is no attempt to define what specific values should be <BR>&gt;&gt; used for what. this is left outside the scope of the protocol specs.<BR>&gt;&gt; * each protocol spec will add a statement clarifying that a given <BR>&gt;&gt; Admission Priority is to be encoded with the same value in each of <BR>&gt;&gt; the three protocol spec. For example, in tsvwg-emergency-rsvp, <BR>&gt;&gt; under section 3.1. we will add:<BR>&gt;&gt; " A given Admission Priority is encoded in this information <BR>&gt;&gt;
 element<BR>&gt;&gt; using the same value as when encoded in the Admission Priority<BR>&gt;&gt; parameter defined in section 6.2.9 of [nsis-qspec], or in the <BR>&gt;&gt; Admission<BR>&gt;&gt; Priority parameter defined in section 4.10 of [dime-qos- <BR>&gt;&gt; parameters].<BR>&gt;&gt; In other words, a given value in any of the [emergency-rsvp] <BR>&gt;&gt; Admission<BR>&gt;&gt; Priority information element, the [nsis-qspec] Admission Priority <BR>&gt;&gt; parameter<BR>&gt;&gt; or the [dime-qos-parameters] Admission Priority parameter, refers to<BR>&gt;&gt; the same Admission Priority.<BR>&gt;&gt; "<BR>&gt;&gt; * the mirror statement will be added in nsis-qspec (section <BR>&gt;&gt; 6.2.9) and dime-qos-parameters (section 4.10)<BR>&gt;&gt;<BR>&gt;&gt; Francois<BR>&gt;&gt;</BLOCKQUOTE></BLOCKQUOTE></DIV></DIV></BLOCKQUOTE></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-431395853-1203781656=:37182--

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

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

--===============0657139471==--


From nsis-bounces@ietf.org  Sat Feb 23 11:39:28 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1B8813A6874;
	Sat, 23 Feb 2008 11:39:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.722
X-Spam-Level: 
X-Spam-Status: No, score=0.722 tagged_above=-999 required=5 tests=[AWL=-0.141,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_MESSAGE=1, MIME_8BIT_HEADER=0.3, 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 hoSdq5kvYgug; Sat, 23 Feb 2008 11:39:27 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2BB8F3A6998;
	Sat, 23 Feb 2008 11:39:27 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DF5C23A6998
	for <nsis@core3.amsl.com>; Sat, 23 Feb 2008 11:39:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 5dYedx8Eu092 for <nsis@core3.amsl.com>;
	Sat, 23 Feb 2008 11:39:25 -0800 (PST)
Received: from mail-1.ci.uc.pt (mail.uc.pt [193.137.200.37])
	by core3.amsl.com (Postfix) with ESMTP id A76933A6874
	for <nsis@ietf.org>; Sat, 23 Feb 2008 11:39:24 -0800 (PST)
Received: from mail-1.ci.uc.pt (mail-1.ci.uc.pt [127.0.0.1])
	by localhost.mail.uc.pt (Postfix) with ESMTP id 2AC5525F6FF
	for <nsis@ietf.org>; Sat, 23 Feb 2008 19:39:18 +0000 (WET)
Received: from [192.168.1.102] (a81-84-56-240.cpe.netcabo.pt [81.84.56.240])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail-1.ci.uc.pt (Postfix) with ESMTP id C3C8A25F6FB
	for <nsis@ietf.org>; Sat, 23 Feb 2008 19:39:17 +0000 (WET)
Message-ID: <47C07662.1040807@dei.uc.pt>
Date: Sat, 23 Feb 2008 19:39:14 +0000
From: =?ISO-8859-1?Q?Lu=EDs_Cordeiro?= <cordeiro@dei.uc.pt>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: NSIS Group <nsis@ietf.org>
Content-Type: multipart/mixed; boundary="------------080404080205040404050906"
Subject: [NSIS] [Fwd: I-D Action:draft-cordeiro-nsis-hypath-05.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: <http://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: <http://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.
--------------080404080205040404050906
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1"><font face="Arial">Dear all,<br>
<br>
The new version of the HyPath proposal has been submitted.<br>
<br>
</font></font>I look forward to receive your comments.<font size="-1"><font
 face="Arial"><br>
<br>
BR,<br>
Lu&iacute;s Cordeiro</font></font><br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
 cellspacing="0">
  <tbody>
    <tr>
      <th align="right" nowrap="nowrap" valign="baseline">Subject: </th>
      <td>I-D Action:draft-cordeiro-nsis-hypath-05.txt</td>
    </tr>
    <tr>
      <th align="right" nowrap="nowrap" valign="baseline">Date: </th>
      <td>Sat, 23 Feb 2008 11:15:03 -0800 (PST)</td>
    </tr>
    <tr>
      <th align="right" nowrap="nowrap" valign="baseline">From: </th>
      <td><a class="moz-txt-link-abbreviated" href="mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a></td>
    </tr>
    <tr>
      <th align="right" nowrap="nowrap" valign="baseline">Reply-To: </th>
      <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
    </tr>
    <tr>
      <th align="right" nowrap="nowrap" valign="baseline">To: </th>
      <td><a class="moz-txt-link-abbreviated" href="mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a></td>
    </tr>
  </tbody>
</table>
<br>
<br>
<pre>A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : GIST Extension for Hybrid On-path Off-path Signaling (HyPath)
	Author(s)       : L. Cordeiro, et al.
	Filename        : draft-cordeiro-nsis-hypath-05.txt
	Pages           : 27
	Date            : 2008-02-23

In a multi-domain Internet that offers QoS guaranties for
applications, there is the need of signaling among the domain
entities that are responsible for the management of QoS.  Because
different domains have different network protocols and topologies,
the HyPath approach uses the NSIS protocol and interactions with the
local routing protocols to have an off-path signaling in hybrid
environments.

A URL for this Internet-Draft is:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-cordeiro-nsis-hypath-05.txt">http://www.ietf.org/internet-drafts/draft-cordeiro-nsis-hypath-05.txt</a>

To remove yourself from the I-D Announcement list, send a message to
<a class="moz-txt-link-abbreviated" href="mailto:i-d-announce-request@ietf.org">i-d-announce-request@ietf.org</a> with the word unsubscribe in the body of 
the message.
You can also visit <a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/I-D-announce">https://www1.ietf.org/mailman/listinfo/I-D-announce</a>
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-cordeiro-nsis-hypath-05.txt".

A list of Internet-Drafts directories can be found in
<a class="moz-txt-link-freetext" href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>
or <a class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a>

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	<a class="moz-txt-link-abbreviated" href="mailto:mailserv@ietf.org">mailserv@ietf.org</a>.
In the body type:
	"FILE /internet-drafts/draft-cordeiro-nsis-hypath-05.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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

</pre>
</body>
</html>

--------------080404080205040404050906
Content-Type: Message/External-body;
 name="draft-cordeiro-nsis-hypath-05.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="draft-cordeiro-nsis-hypath-05.txt"

Content-Type: text/plain
Content-ID: <2008-02-23110702.I-D\@ietf.org>



--------------080404080205040404050906
Content-Type: text/plain;
 name="file:///C:/DOCUME~1/CORDEIRO/LOCALS~1/TEMP/nsmail.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename*0="file:///C:/DOCUME~1/CORDEIRO/LOCALS~1/TEMP/nsmail.txt"

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
http://www.ietf.org/mailman/listinfo/i-d-announce


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

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

--------------080404080205040404050906--


From nsis-bounces@ietf.org  Mon Feb 25 10:03:24 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9C19528C7CC;
	Mon, 25 Feb 2008 10:03:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.584
X-Spam-Level: 
X-Spam-Status: No, score=-2.584 tagged_above=-999 required=5 tests=[AWL=0.015,
	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 fPQrLfECKzyY; Mon, 25 Feb 2008 10:03:23 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 024EE28C8EC;
	Mon, 25 Feb 2008 10:00:05 -0800 (PST)
X-Original-To: nsis@ietf.org
Delivered-To: nsis@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id E46DB28C8BF; Mon, 25 Feb 2008 10:00:01 -0800 (PST)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080225180001.E46DB28C8BF@core3.amsl.com>
Date: Mon, 25 Feb 2008 10:00:01 -0800 (PST)
Cc: nsis@ietf.org
Subject: [NSIS] I-D Action:draft-ietf-nsis-y1541-qosm-06.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: <http://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: <http://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           : Y.1541-QOSM -- Y.1541 QoS Model for Networks Using Y.1541 QoS Classes
	Author(s)       : G. Ash, et al.
	Filename        : draft-ietf-nsis-y1541-qosm-06.txt
	Pages           : 17
	Date            : 2008-02-25

This draft describes a QoS-NSLP QoS model (QOSM) based on ITU-T
Recommendation Y.1541 Network QoS Classes and related signaling
requirements.  Y.1541 specifies 8 classes of Network Performance
objectives, and the Y.1541-QOSM extensions include additional QSPEC
parameters and QOSM processing guidelines.

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

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-nsis-y1541-qosm-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-nsis-y1541-qosm-06.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-nsis-y1541-qosm-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-nsis-y1541-qosm-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-02-25095236.I-D\@ietf.org>


--OtherAccess--

--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
http://www.ietf.org/mailman/listinfo/nsis

--NextPart--


From nsis-bounces@ietf.org  Mon Feb 25 12:00:38 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EB4A628CBD6;
	Mon, 25 Feb 2008 12:00:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.644
X-Spam-Level: 
X-Spam-Status: No, score=0.644 tagged_above=-999 required=5 tests=[AWL=-0.745,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_MESSAGE=1, J_CHICKENPOX_14=0.6, RDNS_NONE=0.1,
	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 Qvb-NzJDRKhW; Mon, 25 Feb 2008 12:00:34 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5DB983A6E05;
	Mon, 25 Feb 2008 11:54:44 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 095803A6E03
	for <nsis@core3.amsl.com>; Mon, 25 Feb 2008 11:54:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 0QlDR1gCilRj for <nsis@core3.amsl.com>;
	Mon, 25 Feb 2008 11:54:42 -0800 (PST)
Received: from QMTA02.westchester.pa.mail.comcast.net
	(qmta02.westchester.pa.mail.comcast.net [76.96.62.24])
	by core3.amsl.com (Postfix) with ESMTP id 4FD9F28C8A8
	for <nsis@ietf.org>; Mon, 25 Feb 2008 11:50:32 -0800 (PST)
Received: from OMTA06.westchester.pa.mail.comcast.net ([76.96.62.51])
	by QMTA02.westchester.pa.mail.comcast.net with comcast
	id tvmR1Y00616LCl05200t00; Mon, 25 Feb 2008 19:49:59 +0000
Received: from [192.168.1.120] ([69.255.64.27])
	by OMTA06.westchester.pa.mail.comcast.net with comcast
	id tvqQ1Y00Z0bGsMR3S00000; Mon, 25 Feb 2008 19:50:26 +0000
X-Authority-Analysis: v=1.0 c=1 a=L5Q-NXtkWhM1LLc7IyAA:9
	a=pMGSlDG2fOyzP3yxYN8A:7 a=vCiL7A5fHwtrhuxNu334dobfBOUA:4
	a=QMgMR9M9BAsA:10
	a=IOfEZFCVVG1Utiqv4dIA:9 a=F0wyPlpWmr2_3Rq3zn4A:7
	a=PKEne9dwdXzbqeWAFHZUVE_EKLYA:4 a=37WNUvjkh6kA:10
Message-Id: <17811FF8-52E1-48AC-9966-3B96798C1A0A@g11.org.uk>
From: ken carlberg <carlberg@g11.org.uk>
To: gash5107@yahoo.com
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 25 Feb 2008 14:50:24 -0500
X-Mailer: Apple Mail (2.919.2)
Cc: john.loughney@nokia.com, "nsis \(\(E-mail\)\)" <nsis@ietf.org>
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1322303978=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


--===============1322303978==
Content-Type: multipart/alternative; boundary=Apple-Mail-6-176041846


--Apple-Mail-6-176041846
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Jerry,

 > Right, there is no issue in having an IETF spec tied to an ITU  
spec.  If ITU modifies their
 > spec, IANA will make the corresponding changes in the IETF IANA  
assignments.  E.g., if
 > ITU later standardizes more priority levels, say in "Y.2171.bis',  
IANA will change the
 > admission priority registry accordingly.  I checked that out with  
IANA a while ago, IANA can
 > tie into ITU specs in this way.

if the Admission field in the QSPEC is to be so entwined with Y.1541  
values (and possibly Y.2171.bis), then perhaps the Admission field in  
QSPEC should be renamed as ITU-Admission?  Or possibly one could  
define a new field called ITU-admission that supports the Y.1541 pre- 
defined values.  It would also seem helpful to add another related  
field that indicates which Y.xxxx standard is being used since there  
may be some domains that only support Y.1541, others supporting Y. 
2171.bis, and whatever future iteration is defined by the ITU.  I  
assume  folks are not relying on a flag day change in support of new  
updates generated by the ITU?

and as far as the current values set by Y.1541, I wish there was  
support for Scavenger Service, which is considered less than Best  
Effort (already defined as "0" in Y.1541).  Since I'm not a member of  
the ITU, I can't advocate this position nor accomplish it if the  
Admission field of all three drafts <emergency-rsvp>, <dime-qos- 
parameters> and <nsis-qspec> are subject to values defined by the ITU.

and please note, I'm not saying that a field cannot reflect efforts  
put forth by the ITU, but rather if the need must exist, then I'd  
prefer that the QSPEC authors rename or create a new field for Y.1541  
or Y.2171.bis

regards,

-ken


--Apple-Mail-6-176041846
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>Jerry,</div><div><br =
class=3D"webkit-block-placeholder"></div><div><span =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: 13px; =
">&gt; Right, there is no issue in having an IETF spec tied to an ITU =
spec.&nbsp; If ITU modifies their&nbsp;</span></div><div><span =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: 13px; =
">&gt; spec,&nbsp;IANA will make the corresponding changes in the IETF =
IANA assignments.&nbsp; E.g., if&nbsp;</span></div><div><span =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: 13px; =
">&gt; ITU later standardizes more priority levels, say&nbsp;in =
"Y.2171.bis', IANA will change the&nbsp;</span></div><div><span =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: 13px; =
">&gt; admission priority registry&nbsp;accordingly.&nbsp; I checked =
that out with IANA&nbsp;a while&nbsp;ago, IANA =
can&nbsp;</span></div><div><span class=3D"Apple-style-span" =
style=3D"font-family: Arial; font-size: 13px; ">&gt; tie into ITU specs =
in this way.</span></div><div><font class=3D"Apple-style-span" =
face=3D"Arial" size=3D"3"><span class=3D"Apple-style-span" =
style=3D"font-size: 13px;"><br =
class=3D"webkit-block-placeholder"></span></font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial" size=3D"3"><span =
class=3D"Apple-style-span" style=3D"font-size: 13px;">if the Admission =
field in the QSPEC is to be so entwined with Y.1541 values (and possibly =
Y.2171.bis), then perhaps the Admission field in QSPEC should be renamed =
as ITU-Admission? &nbsp;Or possibly one could define a new field called =
ITU-admission that supports the Y.1541 pre-defined values. &nbsp;It =
would also seem helpful to add another related field that indicates =
which Y.xxxx standard is being used since there may be some domains that =
only support Y.1541, others supporting Y.2171.bis, and whatever future =
iteration is defined by the ITU. &nbsp;I assume &nbsp;folks are not =
relying on a flag day change in support of new updates generated by the =
ITU?</span></font></div><div><font class=3D"Apple-style-span" =
face=3D"Arial" size=3D"3"><span class=3D"Apple-style-span" =
style=3D"font-size: 13px;"><br =
class=3D"webkit-block-placeholder"></span></font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial" size=3D"3"><span =
class=3D"Apple-style-span" style=3D"font-size: 13px;">and as far as the =
current values set by Y.1541, I wish there was support for Scavenger =
Service, which is considered less than Best Effort (already defined as =
"0" in Y.1541). &nbsp;Since I'm not a member of the ITU, I can't =
advocate this position nor accomplish it if the Admission field of all =
three drafts&nbsp;<span class=3D"Apple-style-span" style=3D"font-family: =
Times; font-size: 15px; ">&lt;emergency-rsvp&gt;, =
&lt;dime-qos-parameters&gt; and &lt;nsis-qspec&gt;</span>&nbsp;are =
subject to values defined by the ITU.</span></font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial" size=3D"3"><span =
class=3D"Apple-style-span" style=3D"font-size: 13px;"><br =
class=3D"webkit-block-placeholder"></span></font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial" size=3D"3"><span =
class=3D"Apple-style-span" style=3D"font-size: 13px;">and please note, =
I'm not saying that a field cannot reflect efforts put forth by the ITU, =
but rather if the need must exist, then I'd prefer that the QSPEC =
authors rename or create a new field for Y.1541 or =
Y.2171.bis</span></font></div><div><font class=3D"Apple-style-span" =
face=3D"Arial" size=3D"3"><span class=3D"Apple-style-span" =
style=3D"font-size: 13px;"><br =
class=3D"webkit-block-placeholder"></span></font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial" size=3D"3"><span =
class=3D"Apple-style-span" style=3D"font-size: =
13px;">regards,</span></font></div><div><font class=3D"Apple-style-span" =
face=3D"Arial" size=3D"3"><span class=3D"Apple-style-span" =
style=3D"font-size: 13px;"><br =
class=3D"webkit-block-placeholder"></span></font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial" size=3D"3"><span =
class=3D"Apple-style-span" style=3D"font-size: =
13px;">-ken</span></font></div><div><font class=3D"Apple-style-span" =
face=3D"Arial" size=3D"3"><span class=3D"Apple-style-span" =
style=3D"font-size: 13px;"><br =
class=3D"webkit-block-placeholder"></span></font></div></body></html>=

--Apple-Mail-6-176041846--

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

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

--===============1322303978==--


From nsis-bounces@ietf.org  Mon Feb 25 12:34:58 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF25A3A6DE4;
	Mon, 25 Feb 2008 12:34:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.588
X-Spam-Level: 
X-Spam-Status: No, score=-2.588 tagged_above=-999 required=5 tests=[AWL=0.011,
	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 Hcr24jYKfe+a; Mon, 25 Feb 2008 12:34:57 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F23923A6DF3;
	Mon, 25 Feb 2008 12:30:02 -0800 (PST)
X-Original-To: nsis@ietf.org
Delivered-To: nsis@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 11A7F3A6DF1; Mon, 25 Feb 2008 12:30:01 -0800 (PST)
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080225203002.11A7F3A6DF1@core3.amsl.com>
Date: Mon, 25 Feb 2008 12:30:02 -0800 (PST)
Cc: nsis@ietf.org
Subject: [NSIS] I-D Action:draft-ietf-nsis-ntlp-statemachine-05.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: <http://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: <http://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           : GIST State Machine
	Author(s)       : T. Tsenov, et al.
	Filename        : draft-ietf-nsis-ntlp-statemachine-05.txt
	Pages           : 23
	Date            : 2008-02-25

This document describes the state machines for the General Internet
Signaling Transport (GIST). The states of GIST nodes for a given flow
and their transitions are presented in order to illustrate how GIST
may be implemented.

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

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
	"get draft-ietf-nsis-ntlp-statemachine-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-nsis-ntlp-statemachine-05.txt".

NOTE:   The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-nsis-ntlp-statemachine-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-nsis-ntlp-statemachine-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2008-02-25121529.I-D\@ietf.org>


--OtherAccess--

--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
http://www.ietf.org/mailman/listinfo/nsis

--NextPart--


From nsis-bounces@ietf.org  Mon Feb 25 12:39:58 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 642E828C73F;
	Mon, 25 Feb 2008 12:39:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.424
X-Spam-Level: 
X-Spam-Status: No, score=0.424 tagged_above=-999 required=5 tests=[AWL=-0.366,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_MESSAGE=1, RDNS_NONE=0.1, 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 wGtLKUlefFsr; Mon, 25 Feb 2008 12:39:57 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9FDCB3A6EFF;
	Mon, 25 Feb 2008 12:33:40 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1F12F3A6EF8
	for <nsis@core3.amsl.com>; Mon, 25 Feb 2008 12:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 Pr6NNrjBSFy4 for <nsis@core3.amsl.com>;
	Mon, 25 Feb 2008 12:33:38 -0800 (PST)
Received: from QMTA09.westchester.pa.mail.comcast.net
	(qmta09.westchester.pa.mail.comcast.net [76.96.62.96])
	by core3.amsl.com (Postfix) with ESMTP id 12A0828C642
	for <nsis@ietf.org>; Mon, 25 Feb 2008 12:27:44 -0800 (PST)
Received: from OMTA10.westchester.pa.mail.comcast.net ([76.96.62.28])
	by QMTA09.westchester.pa.mail.comcast.net with comcast
	id too51Y0020cZkys590pr00; Mon, 25 Feb 2008 20:26:47 +0000
Received: from [192.168.1.120] ([69.255.64.27])
	by OMTA10.westchester.pa.mail.comcast.net with comcast
	id twTd1Y0010bGsMR3W00000; Mon, 25 Feb 2008 20:27:37 +0000
X-Authority-Analysis: v=1.0 c=1 a=WpPcJscwvhgA:10 a=8vM4TlC4MgAUuefHg9sA:9
	a=Vgz2t8xw01tironVWGUfpWJXSl8A:4 a=zUBsD6tbDSsA:10
	a=A6z6c84N0_AVup5ILhUA:9
	a=rMFT2hhO89Co7SUantQA:7 a=aRbrkvy2ewNlKDmZYpxLc3J2QVoA:4
	a=37WNUvjkh6kA:10
Message-Id: <13369810-81EB-4ABA-940B-EEF45823167D@g11.org.uk>
From: ken carlberg <carlberg@g11.org.uk>
To: <john.loughney@nokia.com>
In-Reply-To: <19EBBEC503C3B5469070E0A6674A533A010C40F3@daebe104.NOE.Nokia.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 25 Feb 2008 15:27:36 -0500
References: <17811FF8-52E1-48AC-9966-3B96798C1A0A@g11.org.uk>
	<19EBBEC503C3B5469070E0A6674A533A010C40F3@daebe104.NOE.Nokia.com>
X-Mailer: Apple Mail (2.919.2)
Cc: nsis@ietf.org
Subject: Re: [NSIS] Admission field in QSPECRE: Review of
	draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1280804458=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


--===============1280804458==
Content-Type: multipart/alternative; boundary=Apple-Mail-7-178273924


--Apple-Mail-7-178273924
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

John,

> I think wee need to be able to support a few different scenarios and  
> usages for the admission priority.  Is there a way that we could  
> have a  common structure to hold the values, and the ability to set  
> the values accordingly?

we have one way, as described by Francois.

however, if there is a segment that is absolutely adamant in having a  
field reflect the defined values of Y.1541 or Y.2171bis in the QSPEC,  
then I think a new field should be defined in that document to contain  
those values.  The authors of the other documents can decide if they  
too wish to add an ITU dependent field.

the other option is to disregard any relation between the Admission  
Priority field of the QSPEC and tsvwg-emergency-rsvp, which would be a  
shame.

-ken





--Apple-Mail-7-178273924
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; =
">John,<br><div><div><br></div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 255); font-family: Arial; font-size: 11px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; ">I think wee need to be able to =
support a few different scenarios and usages for&nbsp;the admission =
priority.&nbsp; Is there a way that we could have a<span =
class=3D"Apple-converted-space">&nbsp;</span> common structure to hold =
the values, and the ability to set the values =
accordingly?</span></blockquote></div><br><div>we have one way, as =
described by Francois. &nbsp;</div><div><br =
class=3D"webkit-block-placeholder"></div><div>however, if there is a =
segment that is absolutely adamant in having a field reflect the defined =
values of Y.1541 or Y.2171bis in the QSPEC, then I think a new field =
should be defined in that document to contain those values. &nbsp;The =
authors of the other documents can decide if they too wish to add an ITU =
dependent field.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>the other option is to =
disregard any relation between the Admission Priority field of the QSPEC =
and&nbsp;<span class=3D"Apple-style-span" style=3D"font-family: Arial; =
">tsvwg-emergency-rsvp, which would be a shame.</span></div><div><font =
class=3D"Apple-style-span" face=3D"Arial"><br =
class=3D"webkit-block-placeholder"></font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial">-ken</font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial"><br =
class=3D"webkit-block-placeholder"></font></div><div><br =
class=3D"webkit-block-placeholder"></div><div><br></div><div><br =
class=3D"webkit-block-placeholder"></div></body></html>=

--Apple-Mail-7-178273924--

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

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

--===============1280804458==--


From nsis-bounces@ietf.org  Mon Feb 25 12:41:44 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 67E3928C8E1;
	Mon, 25 Feb 2008 12:41:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.157
X-Spam-Level: 
X-Spam-Status: No, score=0.157 tagged_above=-999 required=5 tests=[AWL=-1.233,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_MESSAGE=1, J_CHICKENPOX_14=0.6, RDNS_NONE=0.1,
	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 tiiDK5aYy1Vf; Mon, 25 Feb 2008 12:41:43 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A092228C8D3;
	Mon, 25 Feb 2008 12:10:54 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 9007028CFFC
	for <nsis@core3.amsl.com>; Mon, 25 Feb 2008 12:10:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 xYZwrOYtipMu for <nsis@core3.amsl.com>;
	Mon, 25 Feb 2008 12:10:52 -0800 (PST)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134])
	by core3.amsl.com (Postfix) with ESMTP id 241EB3A6CEA
	for <nsis@ietf.org>; Mon, 25 Feb 2008 12:02:06 -0800 (PST)
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-mx09.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id
	m1PK3FPi005409; Mon, 25 Feb 2008 14:03:23 -0600
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 25 Feb 2008 22:01:46 +0200
Received: from daebe104.NOE.Nokia.com ([10.241.36.13]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 25 Feb 2008 14:01:42 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 25 Feb 2008 14:01:38 -0600
Message-ID: <19EBBEC503C3B5469070E0A6674A533A010C40F3@daebe104.NOE.Nokia.com>
In-Reply-To: <17811FF8-52E1-48AC-9966-3B96798C1A0A@g11.org.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Admission field in QSPECRE: [NSIS] Review of
	draft-ietf-nsis-qspec-18.txt
Thread-Index: Ach358ufvM5U/dwVRoCN+JlD5iiboQAAIGCg
References: <17811FF8-52E1-48AC-9966-3B96798C1A0A@g11.org.uk>
From: <john.loughney@nokia.com>
To: <carlberg@g11.org.uk>, <gash5107@yahoo.com>
X-OriginalArrivalTime: 25 Feb 2008 20:01:42.0836 (UTC)
	FILETIME=[3DD2A740:01C877E9]
X-Nokia-AV: Clean
Cc: nsis@ietf.org
Subject: [NSIS] Admission field in QSPECRE: Review of
	draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1152907177=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1152907177==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C877E9.3BF84F5D"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C877E9.3BF84F5D
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,
=20
Just some background history.  There are 3 documents defining similar
fields
=20
 tsvwg-emergency-rsvp=20
 nsis-qspec=20
 dime-qos-parameters
=20
We discussed this on this list and at previous IETF meetings. My view of
consensus was that there should be some harmony and a common registry
between these documents. =20
=20
I think wee need to be able to support a few different scenarios and
usages for the admission priority.  Is there a way that we could have a
common structure to hold the values, and the ability to set the values
accordingly?
=20
John
=20
________________________________

From: ext ken carlberg [mailto:carlberg@g11.org.uk]=20
Sent: 25 February, 2008 11:50
To: gash5107@yahoo.com
Cc: nsis ((E-mail)); tarapore@att.com; Francois Le Faucheur IMAP;
Loughney John (Nokia-OCTO/PaloAlto)
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.txt



	Jerry,

	> Right, there is no issue in having an IETF spec tied to an ITU
spec.  If ITU modifies their=20
	> spec, IANA will make the corresponding changes in the IETF
IANA assignments.  E.g., if=20
	> ITU later standardizes more priority levels, say in
"Y.2171.bis', IANA will change the=20
	> admission priority registry accordingly.  I checked that out
with IANA a while ago, IANA can=20
	> tie into ITU specs in this way.
=09
=09
	if the Admission field in the QSPEC is to be so entwined with
Y.1541 values (and possibly Y.2171.bis), then perhaps the Admission
field in QSPEC should be renamed as ITU-Admission?  Or possibly one
could define a new field called ITU-admission that supports the Y.1541
pre-defined values.  It would also seem helpful to add another related
field that indicates which Y.xxxx standard is being used since there may
be some domains that only support Y.1541, others supporting Y.2171.bis,
and whatever future iteration is defined by the ITU.  I assume  folks
are not relying on a flag day change in support of new updates generated
by the ITU?
=09
=09
	and as far as the current values set by Y.1541, I wish there was
support for Scavenger Service, which is considered less than Best Effort
(already defined as "0" in Y.1541).  Since I'm not a member of the ITU,
I can't advocate this position nor accomplish it if the Admission field
of all three drafts <emergency-rsvp>, <dime-qos-parameters> and
<nsis-qspec> are subject to values defined by the ITU.
=09
=09
	and please note, I'm not saying that a field cannot reflect
efforts put forth by the ITU, but rather if the need must exist, then
I'd prefer that the QSPEC authors rename or create a new field for
Y.1541 or Y.2171.bis
=09
=09
	regards,
=09
=09
	-ken
=09
=09


------_=_NextPart_001_01C877E9.3BF84F5D
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16441" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space">
<DIV><SPAN class=3D044595419-25022008><FONT face=3DArial color=3D#0000ff =
size=3D2>Hi=20
all,</FONT></SPAN></DIV>
<DIV><SPAN class=3D044595419-25022008><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D044595419-25022008><FONT face=3DArial color=3D#0000ff =
size=3D2>Just=20
some background history.&nbsp; There are 3 documents defining similar=20
fields</FONT></SPAN></DIV>
<DIV><SPAN class=3D044595419-25022008><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D044595419-25022008><FONT =
face=3DArial>&nbsp;tsvwg-emergency-rsvp=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D044595419-25022008><FONT =
face=3DArial>&nbsp;nsis-qspec=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D044595419-25022008><FONT=20
face=3DArial>&nbsp;dime-qos-parameters</FONT></SPAN></DIV>
<DIV><SPAN class=3D044595419-25022008></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D044595419-25022008><FONT face=3DArial color=3D#0000ff =
size=3D2>We=20
discussed this on this list and at previous IETF meetings. My view of =
consensus=20
was that there should be some harmony and a common registry between =
these=20
documents.&nbsp; </FONT></SPAN></DIV>
<DIV><SPAN class=3D044595419-25022008><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D044595419-25022008><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
think wee need to be able to support a few different scenarios and =
usages=20
for&nbsp;the admission priority.&nbsp; Is there a way that we could have =
a=20
common structure to hold the values, and the ability to set the values=20
accordingly?</FONT></SPAN></DIV>
<DIV><SPAN class=3D044595419-25022008><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D044595419-25022008><FONT face=3DArial color=3D#0000ff =

size=3D2>John</FONT></SPAN></DIV>
<DIV><SPAN class=3D044595419-25022008><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV>
<HR tabIndex=3D-1>
</DIV>
<DIV><FONT face=3DTahoma size=3D2><B>From:</B> ext ken carlberg=20
[mailto:carlberg@g11.org.uk] <BR><B>Sent:</B> 25 February, 2008=20
11:50<BR><B>To:</B> gash5107@yahoo.com<BR><B>Cc:</B> nsis ((E-mail));=20
tarapore@att.com; Francois Le Faucheur IMAP; Loughney John=20
(Nokia-OCTO/PaloAlto)<BR><B>Subject:</B> Re: [NSIS] Review of=20
draft-ietf-nsis-qspec-18.txt<BR></FONT><BR></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV>Jerry,</DIV>
  <DIV><BR class=3Dwebkit-block-placeholder></DIV>
  <DIV><SPAN class=3DApple-style-span=20
  style=3D"FONT-SIZE: 13px; FONT-FAMILY: Arial">&gt; Right, there is no =
issue in=20
  having an IETF spec tied to an ITU spec.&nbsp; If ITU modifies=20
  their&nbsp;</SPAN></DIV>
  <DIV><SPAN class=3DApple-style-span=20
  style=3D"FONT-SIZE: 13px; FONT-FAMILY: Arial">&gt; spec,&nbsp;IANA =
will make the=20
  corresponding changes in the IETF IANA assignments.&nbsp; E.g.,=20
  if&nbsp;</SPAN></DIV>
  <DIV><SPAN class=3DApple-style-span=20
  style=3D"FONT-SIZE: 13px; FONT-FAMILY: Arial">&gt; ITU later =
standardizes more=20
  priority levels, say&nbsp;in "Y.2171.bis', IANA will change=20
  the&nbsp;</SPAN></DIV>
  <DIV><SPAN class=3DApple-style-span=20
  style=3D"FONT-SIZE: 13px; FONT-FAMILY: Arial">&gt; admission priority=20
  registry&nbsp;accordingly.&nbsp; I checked that out with IANA&nbsp;a=20
  while&nbsp;ago, IANA can&nbsp;</SPAN></DIV>
  <DIV><SPAN class=3DApple-style-span=20
  style=3D"FONT-SIZE: 13px; FONT-FAMILY: Arial">&gt; tie into ITU specs =
in this=20
  way.</SPAN></DIV>
  <DIV><FONT class=3DApple-style-span face=3DArial size=3D3><SPAN=20
  class=3DApple-style-span style=3D"FONT-SIZE: 13px"><BR=20
  class=3Dwebkit-block-placeholder></SPAN></FONT></DIV>
  <DIV><FONT class=3DApple-style-span face=3DArial size=3D3><SPAN=20
  class=3DApple-style-span style=3D"FONT-SIZE: 13px">if the Admission =
field in the=20
  QSPEC is to be so entwined with Y.1541 values (and possibly =
Y.2171.bis), then=20
  perhaps the Admission field in QSPEC should be renamed as =
ITU-Admission?=20
  &nbsp;Or possibly one could define a new field called ITU-admission =
that=20
  supports the Y.1541 pre-defined values. &nbsp;It would also seem =
helpful to=20
  add another related field that indicates which Y.xxxx standard is =
being used=20
  since there may be some domains that only support Y.1541, others =
supporting=20
  Y.2171.bis, and whatever future iteration is defined by the ITU. =
&nbsp;I=20
  assume &nbsp;folks are not relying on a flag day change in support of =
new=20
  updates generated by the ITU?</SPAN></FONT></DIV>
  <DIV><FONT class=3DApple-style-span face=3DArial size=3D3><SPAN=20
  class=3DApple-style-span style=3D"FONT-SIZE: 13px"><BR=20
  class=3Dwebkit-block-placeholder></SPAN></FONT></DIV>
  <DIV><FONT class=3DApple-style-span face=3DArial size=3D3><SPAN=20
  class=3DApple-style-span style=3D"FONT-SIZE: 13px">and as far as the =
current=20
  values set by Y.1541, I wish there was support for Scavenger Service, =
which is=20
  considered less than Best Effort (already defined as "0" in Y.1541).=20
  &nbsp;Since I'm not a member of the ITU, I can't advocate this =
position nor=20
  accomplish it if the Admission field of all three drafts&nbsp;<SPAN=20
  class=3DApple-style-span=20
  style=3D"FONT-SIZE: 15px; FONT-FAMILY: Times">&lt;emergency-rsvp&gt;,=20
  &lt;dime-qos-parameters&gt; and &lt;nsis-qspec&gt;</SPAN>&nbsp;are =
subject to=20
  values defined by the ITU.</SPAN></FONT></DIV>
  <DIV><FONT class=3DApple-style-span face=3DArial size=3D3><SPAN=20
  class=3DApple-style-span style=3D"FONT-SIZE: 13px"><BR=20
  class=3Dwebkit-block-placeholder></SPAN></FONT></DIV>
  <DIV><FONT class=3DApple-style-span face=3DArial size=3D3><SPAN=20
  class=3DApple-style-span style=3D"FONT-SIZE: 13px">and please note, =
I'm not saying=20
  that a field cannot reflect efforts put forth by the ITU, but rather =
if the=20
  need must exist, then I'd prefer that the QSPEC authors rename or =
create a new=20
  field for Y.1541 or Y.2171.bis</SPAN></FONT></DIV>
  <DIV><FONT class=3DApple-style-span face=3DArial size=3D3><SPAN=20
  class=3DApple-style-span style=3D"FONT-SIZE: 13px"><BR=20
  class=3Dwebkit-block-placeholder></SPAN></FONT></DIV>
  <DIV><FONT class=3DApple-style-span face=3DArial size=3D3><SPAN=20
  class=3DApple-style-span style=3D"FONT-SIZE: =
13px">regards,</SPAN></FONT></DIV>
  <DIV><FONT class=3DApple-style-span face=3DArial size=3D3><SPAN=20
  class=3DApple-style-span style=3D"FONT-SIZE: 13px"><BR=20
  class=3Dwebkit-block-placeholder></SPAN></FONT></DIV>
  <DIV><FONT class=3DApple-style-span face=3DArial size=3D3><SPAN=20
  class=3DApple-style-span style=3D"FONT-SIZE: =
13px">-ken</SPAN></FONT></DIV>
  <DIV><FONT class=3DApple-style-span face=3DArial size=3D3><SPAN=20
  class=3DApple-style-span style=3D"FONT-SIZE: 13px"><BR=20
  =
class=3Dwebkit-block-placeholder></SPAN></FONT></DIV></BLOCKQUOTE></BODY>=
</HTML>

------_=_NextPart_001_01C877E9.3BF84F5D--

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

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

--===============1152907177==--


From nsis-bounces@ietf.org  Mon Feb 25 13:11:42 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5AEA03A6ED1;
	Mon, 25 Feb 2008 13:11:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.26
X-Spam-Level: 
X-Spam-Status: No, score=-101.26 tagged_above=-999 required=5
	tests=[AWL=-1.626, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, MSGID_FROM_MTA_HEADER=0.803, RDNS_NONE=0.1,
	USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id LI7nPQc7m1cn; Mon, 25 Feb 2008 13:11:41 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3D83728CB05;
	Mon, 25 Feb 2008 13:05:12 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8FD7928CC18
	for <nsis@core3.amsl.com>; Mon, 25 Feb 2008 13:05:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 xk8GztciBJNR for <nsis@core3.amsl.com>;
	Mon, 25 Feb 2008 13:05:10 -0800 (PST)
Received: from mail121.messagelabs.com (mail121.messagelabs.com
	[216.82.241.195])
	by core3.amsl.com (Postfix) with ESMTP id 36A7528CB05
	for <nsis@ietf.org>; Mon, 25 Feb 2008 12:58:30 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: acmorton@att.com
X-Msg-Ref: server-13.tower-121.messagelabs.com!1203973102!25877602!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.128.141]
Received: (qmail 4737 invoked from network); 25 Feb 2008 20:58:23 -0000
Received: from sbcsmtp9.sbc.com (HELO flph161.enaf.ffdc.sbc.com)
	(144.160.128.141)
	by server-13.tower-121.messagelabs.com with AES256-SHA encrypted SMTP;
	25 Feb 2008 20:58:23 -0000
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1])
	by flph161.enaf.ffdc.sbc.com (8.14.2/8.14.2) with ESMTP id
	m1PKwM8k028737 for <nsis@ietf.org>; Mon, 25 Feb 2008 12:58:22 -0800
Received: from klph001.kcdc.att.com (klph001.kcdc.att.com [135.188.3.11])
	by flph161.enaf.ffdc.sbc.com (8.14.2/8.14.2) with ESMTP id
	m1PKwGCN028184 for <nsis@ietf.org>; Mon, 25 Feb 2008 12:58:17 -0800
Received: from kcdc.att.com (localhost.localdomain [127.0.0.1])
	by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id m1PKwG7B006722
	for <nsis@ietf.org>; Mon, 25 Feb 2008 14:58:16 -0600
Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99])
	by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id m1PKw8CD006480
	for <nsis@ietf.org>; Mon, 25 Feb 2008 14:58:08 -0600
Message-Id: <200802252058.m1PKw8CD006480@klph001.kcdc.att.com>
Received: from acmt.att.com (unknown[135.210.37.231](misconfigured sender))
	by maillennium.att.com (mailgw1) with SMTP
	id <20080225205807gw10010gole>; Mon, 25 Feb 2008 20:58:07 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 25 Feb 2008 15:58:06 -0500
To: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>, <nsis@ietf.org>
From: Al Morton <acmorton@att.com>
In-Reply-To: <5F6519BF2DE0404D99B7C75607FF76FF4D0A45@mx1.office>
References: <5F6519BF2DE0404D99B7C75607FF76FF4D0A45@mx1.office>
Mime-Version: 1.0
Subject: Re: [NSIS] (no subject)
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <http://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: <http://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

At 09:00 AM 2/11/2008, Martin Stiemerling wrote:
>...
>* Y.1541 QOSM: WGLC finished. Waiting for updated draft.
It's posted, addresses all comments, AFAICT,
including the required bit-level example
(The co-authors thank Hannes again for his helpful review).
http://www.ietf.org/internet-drafts/draft-ietf-nsis-y1541-qosm-06.txt

Al

PS I don't think there's a connection between Y.1541 and
the various ITU-T Admission Recs (Y.1571, now Y.2171).
Y.1541 specifies categories of performance objectives (mostly), and
it seems like a Scavenger service would have "Unspecified" objectives
(same as the Y.1541 Best Effort). Scavenger is more about *when* it
works than about how well, IMO.

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


From nsis-bounces@ietf.org  Mon Feb 25 13:54:41 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AF89D28CAE8;
	Mon, 25 Feb 2008 13:54:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.407
X-Spam-Level: *
X-Spam-Status: No, score=1.407 tagged_above=-999 required=5 tests=[AWL=0.016,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_MESSAGE=1, J_CHICKENPOX_14=0.6, MIME_HTML_MOSTLY=0.001,
	RDNS_NONE=0.1, 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 3yBDwsDitmZ7; Mon, 25 Feb 2008 13:54:40 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E04C628C6A4;
	Mon, 25 Feb 2008 13:01:19 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EBBDF28C69D
	for <nsis@core3.amsl.com>; Mon, 25 Feb 2008 13:01:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 DQ055a0e33Vo for <nsis@core3.amsl.com>;
	Mon, 25 Feb 2008 13:01:14 -0800 (PST)
Received: from web63607.mail.re1.yahoo.com (web63607.mail.re1.yahoo.com
	[69.147.97.77]) by core3.amsl.com (Postfix) with SMTP id B652528C711
	for <nsis@ietf.org>; Mon, 25 Feb 2008 12:55:15 -0800 (PST)
Received: (qmail 87264 invoked by uid 60001); 25 Feb 2008 20:55:08 -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=cDDHBn7S71cdblrMGHnLf/PaUeJYXTgTe58qDmWbprgIGZdUfOO525KlMLYhI3jDgcQxYidx5Lwpg2NUEE3yruEuPrfjYh6E7ZZ+J01st3WQyssWkV6uTObAc1YtyGfdCXwpNl0UM1MyhwCsq+agUOh6OYgXkzu8eEQsvIoiv50=;
X-YMail-OSG: Zszsy84VM1mPHUiABUhHOiVQi1mBtN6GJTeThvqywhGN2PQxkeqMxAm.z8ldXsLZd23n2Nifrl2ZyU9dSeC8CsGRL9PV3tMGdg9iW4Fb9L9aXqDyBpgsRQ--
Received: from [76.19.255.157] by web63607.mail.re1.yahoo.com via HTTP;
	Mon, 25 Feb 2008 12:55:08 PST
Date: Mon, 25 Feb 2008 12:55:08 -0800 (PST)
From: Gerald Ash <gash5107@yahoo.com>
To: ken carlberg <carlberg@g11.org.uk>
In-Reply-To: <17811FF8-52E1-48AC-9966-3B96798C1A0A@g11.org.uk>
MIME-Version: 1.0
Message-ID: <608933.86882.qm@web63607.mail.re1.yahoo.com>
Cc: john.loughney@nokia.com, "nsis \(\(E-mail\)\)" <nsis@ietf.org>
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1413643560=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

--===============1413643560==
Content-Type: multipart/alternative; boundary="0-79360610-1203972908=:86882"
Content-Transfer-Encoding: 8bit

--0-79360610-1203972908=:86882
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Ken,
   
  >> Right, there is no issue in having an IETF spec tied to an ITU spec.  
  >> If ITU modifies their spec, IANA will make the corresponding changes
  >> in the IETF IANA assignments.  E.g., if ITU later standardizes more
  >> priority levels, say in "Y.2171.bis', IANA will change the 
  >> admission priority registry accordingly.  I checked that out with IANA
  >> a while ago, IANA can tie into ITU specs in this way.
  

  > if the Admission field in the QSPEC is to be so entwined with Y.1541
  > values (and possibly Y.2171.bis), then perhaps the Admission field
  > in QSPEC should be renamed as ITU-Admission?
    > Or possibly one could define a new field called ITU-admission that
  > supports the Y.1541 pre-defined values.  It would also seem helpful to
  > add another related field that indicates which Y.xxxx standard is being
  > used since there may be some domains that only support Y.1541,
  > others supporting Y.2171.bis, and whatever future iteration is defined
  > by the ITU.  I assume  folks are not relying on a flag day change in
  > support of new updates generated by the ITU?

   
  This is confusing to me because admission priority has nothing to do with Y.1541.  Y.1541 is associated with the <Y.1541.QoS Class> field (see Section 5.2.14 of the updated -19 QSPEC document or Section 6.2.14 of the current -18 QSPEC document).  
   
  QSPEC admission priority is simply using the 3 priority levels already standardized by Y.2171.  Admission priority is a generic concept, not invented by the ITU, so this is not 'ITU admission priority', just plain ole' admission priority.
   
  What's missing here is an explanation of what the approach is in [EMERGENCY-RSVP].  As I posted earlier in http://www.ietf.org/mail-archive/web/nsis/current/msg08231.html:
   
  "QSPEC is ... standardizing 3 priority levels to have end-to-end cross-domain significance.   
  If we elimate this standardization, as is proposed (in [EMERGENCY-RSVP]), then different admission priority values can be assigned in different Admin domains, and will have no end-to-end significance.  For example, Admin-domain 1, Admin-domain 2, and Admin-domain 3 assign admission priority=2,  admission priority=4, admission priority=10 for the highest level priority, respectively.  Admin-domain 1 and Admin-domain 2 try to initiate end-to-end flows via Admin-domain 3 for a 'high priority' flow.  However, Admin-domain 3 has no idea how to treat the flow admission priority since all 3 domains are using different encodings of high priority."
   
  I've not seen a response to the above example and/or an explanation of how the [EMERGENCY-RSVP] approach achieves end-to-end cross-domain standardization?
   
  Perhaps it is some different approach to priority more like preemption priority?  Perhaps the [EMERGENCY-RSVP] approach should be called "RSVP-priority"?
   

  > and as far as the current values set by Y.1541, I wish there was support
  > for Scavenger Service, which is considered less than Best Effort (already
  > defined as "0" in Y.1541).
   
  I'm not sure what your suggestion is here for Y.1541, but perhaps that should be discussed on a separate thread (perhaps associated with the Y.1541-QOSM draft http://www.ietf.org/internet-drafts/draft-ietf-nsis-y1541-qosm-06.txt)?
   
  Thanks,
  Jerry

ken carlberg <carlberg@g11.org.uk> wrote:
    Jerry,
  

  > Right, there is no issue in having an IETF spec tied to an ITU spec.  If ITU modifies their 
  > spec, IANA will make the corresponding changes in the IETF IANA assignments.  E.g., if 
  > ITU later standardizes more priority levels, say in "Y.2171.bis', IANA will change the 
  > admission priority registry accordingly.  I checked that out with IANA a while ago, IANA can 
  > tie into ITU specs in this way.
  

  if the Admission field in the QSPEC is to be so entwined with Y.1541 values (and possibly Y.2171.bis), then perhaps the Admission field in QSPEC should be renamed as ITU-Admission?  Or possibly one could define a new field called ITU-admission that supports the Y.1541 pre-defined values.  It would also seem helpful to add another related field that indicates which Y.xxxx standard is being used since there may be some domains that only support Y.1541, others supporting Y.2171.bis, and whatever future iteration is defined by the ITU.  I assume  folks are not relying on a flag day change in support of new updates generated by the ITU?
  

  and as far as the current values set by Y.1541, I wish there was support for Scavenger Service, which is considered less than Best Effort (already defined as "0" in Y.1541).  Since I'm not a member of the ITU, I can't advocate this position nor accomplish it if the Admission field of all three drafts <emergency-rsvp>, <dime-qos-parameters> and <nsis-qspec> are subject to values defined by the ITU.
  

  and please note, I'm not saying that a field cannot reflect efforts put forth by the ITU, but rather if the need must exist, then I'd prefer that the QSPEC authors rename or create a new field for Y.1541 or Y.2171.bis
  

  regards,
  

  -ken
  



       
---------------------------------
Never miss a thing.   Make Yahoo your homepage.
--0-79360610-1203972908=:86882
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY: Arial">Ken,</SPAN></DIV>  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY: Arial"></SPAN>&nbsp;</DIV>  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY: Arial">&gt;&gt; Right, there is no issue in having an IETF spec tied to an ITU spec.&nbsp; </SPAN></DIV>  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY: Arial">&gt;&gt; If ITU modifies their&nbsp;</SPAN><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY: Arial">spec,&nbsp;IANA will make the corresponding changes</SPAN></DIV>  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY: Arial">&gt;&gt;&nbsp;in the IETF IANA assignments.&nbsp; E.g., if&nbsp;</SPAN><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY: Arial">ITU later standardizes more</SPAN></DIV>  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY:
 Arial">&gt;&gt;&nbsp;priority levels, say&nbsp;in "Y.2171.bis', IANA will change the&nbsp;</SPAN></DIV>  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY: Arial">&gt;&gt; admission priority registry&nbsp;accordingly.&nbsp; I checked that out with IANA</SPAN></DIV>  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY: Arial">&gt;&gt;&nbsp;a while&nbsp;ago, IANA can&nbsp;</SPAN><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY: Arial">tie into ITU specs in this way.</SPAN></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px"><BR class=webkit-block-placeholder></SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">&gt; if the Admission field in the QSPEC is to be so entwined with Y.1541</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span
 style="FONT-SIZE: 13px">&gt;&nbsp;values (and possibly Y.2171.bis), then perhaps the Admission field</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">&gt;&nbsp;in QSPEC should be renamed as ITU-Admission?</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">&gt;&nbsp;Or possibly one could define a new field called ITU-admission that</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">&gt;&nbsp;supports the Y.1541 pre-defined values. &nbsp;It would also seem helpful to</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">&gt;&nbsp;add another related field that indicates which
 Y.xxxx standard is being</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">&gt;&nbsp;used since there may be some domains that only support Y.1541,</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">&gt;&nbsp;others supporting Y.2171.bis, and whatever future iteration is defined</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">&gt;&nbsp;by the ITU. &nbsp;I assume &nbsp;folks are not relying on a flag day change in</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">&gt;&nbsp;support of new updates generated by the ITU?</SPAN></FONT></DIV></SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE:
 13px"></SPAN></FONT>&nbsp;</DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">This is confusing to me because&nbsp;admission priority has nothing to do with Y.1541.&nbsp; Y.1541 is associated with&nbsp;the &lt;Y.1541.QoS Class&gt; field (see Section 5.2.14 of the updated -19 QSPEC document or Section 6.2.14 of the current -18 QSPEC document).&nbsp; </SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px"></SPAN></FONT>&nbsp;</DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">QSPEC admission priority is simply using the 3 priority levels already standardized by Y.2171.&nbsp; Admission priority is a generic concept, not invented by the ITU, so this is not 'ITU admission priority', just plain ole' admission priority.</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial
 size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px"></SPAN></FONT>&nbsp;</DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">What's missing here&nbsp;is an explanation of what the approach is in [EMERGENCY-RSVP].&nbsp; As I&nbsp;posted earlier in&nbsp;<A href="http://www.ietf.org/mail-archive/web/nsis/current/msg08231.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08231.html</A>:</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px"></SPAN></FONT>&nbsp;</DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">"QSPEC is&nbsp;... standardizing 3 priority levels to have end-to-end cross-domain significance.  <DIV>&nbsp;</DIV>  <DIV>If we elimate this standardization, as is proposed (in [EMERGENCY-RSVP]), then different admission priority values&nbsp;can be&nbsp;assigned in
 different Admin domains, and will&nbsp;have no end-to-end significance.&nbsp; For example, Admin-domain 1, Admin-domain 2, and Admin-domain 3 assign&nbsp;admission priority=2,&nbsp;&nbsp;admission priority=4, admission priority=10 for the highest level priority, respectively.&nbsp; Admin-domain 1 and Admin-domain 2 try to initiate end-to-end flows via Admin-domain&nbsp;3 for a 'high priority' flow.&nbsp;&nbsp;However, Admin-domain 3 has no idea how to treat the flow admission priority since all 3 domains are using different encodings of high priority."</DIV>  <DIV>&nbsp;</DIV>  <DIV>I've not seen a response to the above example and/or an explanation of how the [EMERGENCY-RSVP] approach achieves end-to-end cross-domain standardization?</DIV>  <DIV>&nbsp;</DIV>  <DIV>Perhaps it is some different approach to priority more like preemption priority?&nbsp; Perhaps the [EMERGENCY-RSVP] approach should be called "RSVP-priority"?</DIV>  <DIV></SPAN></FONT><FONT
 class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px"></SPAN></FONT><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px"></SPAN></FONT>&nbsp;</DIV></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">&gt; and as far as the current values set by Y.1541, I wish there was support</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">&gt;&nbsp;for Scavenger Service, which is considered less than Best Effort (already</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">&gt;&nbsp;defined as "0" in Y.1541).</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px"></SPAN></FONT>&nbsp;</DIV>  <DIV><FONT class=Apple-style-span
 face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">I'm not sure what&nbsp;your suggestion is here for Y.1541, but perhaps that should be discussed on a separate thread (perhaps associated with the Y.1541-QOSM draft <A href="http://www.ietf.org/internet-drafts/draft-ietf-nsis-y1541-qosm-06.txt">http://www.ietf.org/internet-drafts/draft-ietf-nsis-y1541-qosm-06.txt</A>)?</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px"></SPAN></FONT>&nbsp;</DIV>  <div>Thanks,</div>  <div>Jerry<BR><BR><B><I>ken carlberg &lt;carlberg@g11.org.uk&gt;</I></B> wrote:</div>  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">  <DIV>Jerry,</DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY: Arial">&gt; Right, there is no issue in having an IETF spec tied to an ITU spec.&nbsp; If ITU
 modifies their&nbsp;</SPAN></DIV>  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY: Arial">&gt; spec,&nbsp;IANA will make the corresponding changes in the IETF IANA assignments.&nbsp; E.g., if&nbsp;</SPAN></DIV>  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY: Arial">&gt; ITU later standardizes more priority levels, say&nbsp;in "Y.2171.bis', IANA will change the&nbsp;</SPAN></DIV>  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY: Arial">&gt; admission priority registry&nbsp;accordingly.&nbsp; I checked that out with IANA&nbsp;a while&nbsp;ago, IANA can&nbsp;</SPAN></DIV>  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 13px; FONT-FAMILY: Arial">&gt; tie into ITU specs in this way.</SPAN></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px"><BR class=webkit-block-placeholder></SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial
 size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">if the Admission field in the QSPEC is to be so entwined with Y.1541 values (and possibly Y.2171.bis), then perhaps the Admission field in QSPEC should be renamed as ITU-Admission? &nbsp;Or possibly one could define a new field called ITU-admission that supports the Y.1541 pre-defined values. &nbsp;It would also seem helpful to add another related field that indicates which Y.xxxx standard is being used since there may be some domains that only support Y.1541, others supporting Y.2171.bis, and whatever future iteration is defined by the ITU. &nbsp;I assume &nbsp;folks are not relying on a flag day change in support of new updates generated by the ITU?</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px"><BR class=webkit-block-placeholder></SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span
 style="FONT-SIZE: 13px">and as far as the current values set by Y.1541, I wish there was support for Scavenger Service, which is considered less than Best Effort (already defined as "0" in Y.1541). &nbsp;Since I'm not a member of the ITU, I can't advocate this position nor accomplish it if the Admission field of all three drafts&nbsp;<SPAN class=Apple-style-span style="FONT-SIZE: 15px; FONT-FAMILY: Times">&lt;emergency-rsvp&gt;, &lt;dime-qos-parameters&gt; and &lt;nsis-qspec&gt;</SPAN>&nbsp;are subject to values defined by the ITU.</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px"><BR class=webkit-block-placeholder></SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">and please note, I'm not saying that a field cannot reflect efforts put forth by the ITU, but rather if the need must exist, then I'd prefer that the QSPEC
 authors rename or create a new field for Y.1541 or Y.2171.bis</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px"><BR class=webkit-block-placeholder></SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">regards,</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px"><BR class=webkit-block-placeholder></SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">-ken</SPAN></FONT></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px"><BR class=webkit-block-placeholder></SPAN></FONT></DIV></BLOCKQUOTE><BR><p>&#32;

      <hr size=1>Never miss a thing.  <a href="http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs"> Make Yahoo your homepage.</a>


--0-79360610-1203972908=:86882--

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

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

--===============1413643560==--


From nsis-bounces@ietf.org  Mon Feb 25 15:12:42 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2AB9528C97F;
	Mon, 25 Feb 2008 15:12:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.368
X-Spam-Level: 
X-Spam-Status: No, score=-99.368 tagged_above=-999 required=5
	tests=[AWL=-0.158, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1,
	SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id omWPb-86MTaw; Mon, 25 Feb 2008 15:12:41 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 706F428CBB4;
	Mon, 25 Feb 2008 15:04:29 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D138B28CBA2
	for <nsis@core3.amsl.com>; Mon, 25 Feb 2008 15:04:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 k13gr3dwkZsF for <nsis@core3.amsl.com>;
	Mon, 25 Feb 2008 15:04:27 -0800 (PST)
Received: from mail203.messagelabs.com (mail203.messagelabs.com
	[216.82.254.243])
	by core3.amsl.com (Postfix) with ESMTP id CCC7528CBBD
	for <nsis@ietf.org>; Mon, 25 Feb 2008 14:50:13 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: tarapore@att.com
X-Msg-Ref: server-6.tower-203.messagelabs.com!1203979804!5304188!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 6131 invoked from network); 25 Feb 2008 22:50:05 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com)
	(144.160.20.54)
	by server-6.tower-203.messagelabs.com with AES256-SHA encrypted SMTP;
	25 Feb 2008 22:50:05 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m1PMo6U2008249; Mon, 25 Feb 2008 17:50:06 -0500
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m1PMnxej008123; Mon, 25 Feb 2008 17:49:59 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 25 Feb 2008 16:49:58 -0600
Message-ID: <A1F50CB516D211409DFD05D6B3CE6D300CD2B73E@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <13369810-81EB-4ABA-940B-EEF45823167D@g11.org.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Admission field in QSPECRE: [NSIS] Review of
	draft-ietf-nsis-qspec-18.txt
Thread-Index: Ach37OVRlRv/TtxTSZe92UMh3k/WOQAE12kg
References: <17811FF8-52E1-48AC-9966-3B96798C1A0A@g11.org.uk>
	<19EBBEC503C3B5469070E0A6674A533A010C40F3@daebe104.NOE.Nokia.com>
	<13369810-81EB-4ABA-940B-EEF45823167D@g11.org.uk>
From: "TARAPORE, PERCY S, ATTLABS" <tarapore@att.com>
To: "ken carlberg" <carlberg@g11.org.uk>, <john.loughney@nokia.com>
Cc: nsis@ietf.org
Subject: Re: [NSIS] Admission field in QSPECRE: Review of
	draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0419327398=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0419327398==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C87800.BF95BB61"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C87800.BF95BB61
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Ken,
=20
You state that Francois has "one way" that supposedly defines a "common
structure to hold the values and the ability to set the values
accordingly" as John desires. I am somewhat at a loss here - what
exactly has Francois described that takes an incoming CAC priority value
as desired by a customer at the initial domain which then passes it on
to the other domains in the path. After all, Y.2171 is simply a vehicle
for providing a CAC priority value. It does not mandate how that value
can be acted upon in each domain.
=20
Thanks
=20
Percy

________________________________

From: ken carlberg [mailto:carlberg@g11.org.uk]=20
Sent: Monday, February 25, 2008 3:28 PM
To: john.loughney@nokia.com
Cc: gash5107@yahoo.com; nsis@ietf.org; TARAPORE, PERCY S, ATTLABS;
flefauch@cisco.com
Subject: Re: Admission field in QSPECRE: [NSIS] Review of
draft-ietf-nsis-qspec-18.txt


John,



	I think wee need to be able to support a few different scenarios
and usages for the admission priority.  Is there a way that we could
have a  common structure to hold the values, and the ability to set the
values accordingly?


we have one way, as described by Francois. =20

however, if there is a segment that is absolutely adamant in having a
field reflect the defined values of Y.1541 or Y.2171bis in the QSPEC,
then I think a new field should be defined in that document to contain
those values.  The authors of the other documents can decide if they too
wish to add an ITU dependent field.

the other option is to disregard any relation between the Admission
Priority field of the QSPEC and tsvwg-emergency-rsvp, which would be a
shame.


-ken






------_=_NextPart_001_01C87800.BF95BB61
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3268" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D886294622-25022008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Ken,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D886294622-25022008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D886294622-25022008>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D734462820-25022008><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN class=3D886294622-25022008>You=20
state</SPAN>&nbsp;that Francois has "one way" that supposedly defines a =
"common=20
structure to hold the values and the ability to set the values =
accordingly" as=20
John desires. I am somewhat at a loss here - what exactly has Francois =
described=20
that takes an incoming CAC priority value as desired by a customer at =
the=20
initial domain which then passes it on to the other domains in the path. =
After=20
all, Y.2171 is simply a vehicle for providing a CAC priority value. It =
does not=20
mandate how that value can be acted upon in each=20
domain.</FONT></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D734462820-25022008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D734462820-25022008><SPAN=20
class=3D886294622-25022008><FONT face=3DArial color=3D#0000ff=20
size=3D2>Thanks</FONT></SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D734462820-25022008><SPAN=20
class=3D886294622-25022008><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D734462820-25022008><SPAN=20
class=3D886294622-25022008><FONT face=3DArial color=3D#0000ff=20
size=3D2>Percy</FONT></SPAN></SPAN></DIV></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> ken carlberg =
[mailto:carlberg@g11.org.uk]=20
<BR><B>Sent:</B> Monday, February 25, 2008 3:28 PM<BR><B>To:</B>=20
john.loughney@nokia.com<BR><B>Cc:</B> gash5107@yahoo.com; nsis@ietf.org; =

TARAPORE, PERCY S, ATTLABS; flefauch@cisco.com<BR><B>Subject:</B> Re: =
Admission=20
field in QSPECRE: [NSIS] Review of=20
draft-ietf-nsis-qspec-18.txt<BR></FONT><BR></DIV>
<DIV></DIV>John,<BR>
<DIV>
<DIV><BR></DIV>
<BLOCKQUOTE type=3D"cite"><SPAN class=3DApple-style-span=20
  style=3D"WORD-SPACING: 0px; FONT: 11px Arial; TEXT-TRANSFORM: none; =
COLOR: rgb(0,0,255); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate; orphans: 2; widows: =
2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0">I=20
  think wee need to be able to support a few different scenarios and =
usages=20
  for&nbsp;the admission priority.&nbsp; Is there a way that we could =
have=20
  a<SPAN class=3DApple-converted-space>&nbsp;</SPAN> common structure to =
hold the=20
  values, and the ability to set the values=20
accordingly?</SPAN></BLOCKQUOTE></DIV><BR>
<DIV>we have one way, as described by Francois. &nbsp;</DIV>
<DIV><BR class=3Dwebkit-block-placeholder></DIV>
<DIV>however, if there is a segment that is absolutely adamant in having =
a field=20
reflect the defined values of Y.1541 or Y.2171bis in the QSPEC, then I =
think a=20
new field should be defined in that document to contain those values. =
&nbsp;The=20
authors of the other documents can decide if they too wish to add an ITU =

dependent field.</DIV>
<DIV><BR class=3Dwebkit-block-placeholder></DIV>
<DIV>the other option is to disregard any relation between the Admission =

Priority field of the QSPEC and&nbsp;<SPAN class=3DApple-style-span=20
style=3D"FONT-FAMILY: Arial">tsvwg-emergency-rsvp, which would be a=20
shame.</SPAN></DIV>
<DIV><FONT class=3DApple-style-span face=3DArial><BR=20
class=3Dwebkit-block-placeholder></FONT></DIV>
<DIV><FONT class=3DApple-style-span face=3DArial>-ken</FONT></DIV>
<DIV><FONT class=3DApple-style-span face=3DArial><BR=20
class=3Dwebkit-block-placeholder></FONT></DIV>
<DIV><BR class=3Dwebkit-block-placeholder></DIV>
<DIV><BR></DIV>
<DIV><BR class=3Dwebkit-block-placeholder></DIV></BODY></HTML>

------_=_NextPart_001_01C87800.BF95BB61--

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

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

--===============0419327398==--


From nsis-bounces@ietf.org  Mon Feb 25 17:48:28 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 233AD28CC65;
	Mon, 25 Feb 2008 17:48:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.588
X-Spam-Level: 
X-Spam-Status: No, score=-2.588 tagged_above=-999 required=5 tests=[AWL=0.011,
	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 c2zKxHo4EMEp; Mon, 25 Feb 2008 17:48:27 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B589E28C671;
	Mon, 25 Feb 2008 17:45:07 -0800 (PST)
X-Original-To: nsis@ietf.org
Delivered-To: nsis@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 77EBE28C64A; Mon, 25 Feb 2008 17:45:00 -0800 (PST)
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <20080226014501.77EBE28C64A@core3.amsl.com>
Date: Mon, 25 Feb 2008 17:45:01 -0800 (PST)
Cc: nsis@ietf.org
Subject: [NSIS] I-D
 ACTION:draft-ietf-nsis-applicability-mobility-signaling-09.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: <http://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: <http://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



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		: Applicability Statement of NSIS Protocols in Mobile Environments
	Author(s)	: S. Lee
	Filename	: draft-ietf-nsis-applicability-mobility-signaling-09.txt
	Pages		: 47
	Date		: 2008-2-25
	
Mobility of an IP-based node affects routing paths, and as a result,
   can have a significant effect on the protocol operation and state
   management.  This draft discusses the effects mobility can cause to
   the NSIS protocol suite, and how the protocols operate in different
   scenarios, with mobility management protocols.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-nsis-applicability-mobility-signaling-09.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-nsis-applicability-mobility-signaling-09.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


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


From nsis-bounces@ietf.org  Tue Feb 26 12:41:31 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3CFF928C4E2;
	Tue, 26 Feb 2008 12:41:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.562
X-Spam-Level: 
X-Spam-Status: No, score=0.562 tagged_above=-999 required=5 tests=[AWL=-0.228,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_MESSAGE=1, RDNS_NONE=0.1, 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 4uNBIslpV+pV; Tue, 26 Feb 2008 12:41:29 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DDA2A28C20F;
	Tue, 26 Feb 2008 12:41:29 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6C85928C0FA
	for <nsis@core3.amsl.com>; Tue, 26 Feb 2008 12:41:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 tTbWRcpSLYWy for <nsis@core3.amsl.com>;
	Tue, 26 Feb 2008 12:41:28 -0800 (PST)
Received: from QMTA02.westchester.pa.mail.comcast.net
	(qmta02.westchester.pa.mail.comcast.net [76.96.62.24])
	by core3.amsl.com (Postfix) with ESMTP id A8FB63A68BD
	for <nsis@ietf.org>; Tue, 26 Feb 2008 12:41:27 -0800 (PST)
Received: from OMTA14.westchester.pa.mail.comcast.net ([76.96.62.60])
	by QMTA02.westchester.pa.mail.comcast.net with comcast
	id uFpW1Y0011HzFnQ520WF00; Tue, 26 Feb 2008 20:40:52 +0000
Received: from [192.168.1.120] ([69.255.66.123])
	by OMTA14.westchester.pa.mail.comcast.net with comcast
	id uLhK1Y0062fa1BZ3a00000; Tue, 26 Feb 2008 20:41:19 +0000
X-Authority-Analysis: v=1.0 c=1 a=48vgC7mUAAAA:8 a=reLiOMIHzeO3RavNRmIA:9
	a=yP1rGBasgYWldKedB6AA:7 a=f8VWTFOis-VFL3P9qNxZN-BMFuMA:4
	a=QMgMR9M9BAsA:10
	a=ETtDzLJwAiMLbwHAe3wA:9 a=jw_JGc9ckzB87QuiO9IA:7
	a=BuWk_gcxeG4-89gXp1szAEkGn34A:4 a=37WNUvjkh6kA:10
Message-Id: <8235DDEA-6B91-4151-8E2F-E6EC01AD470D@g11.org.uk>
From: ken carlberg <carlberg@g11.org.uk>
To: Gerald Ash <gash5107@yahoo.com>
In-Reply-To: <608933.86882.qm@web63607.mail.re1.yahoo.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 26 Feb 2008 15:41:18 -0500
References: <608933.86882.qm@web63607.mail.re1.yahoo.com>
X-Mailer: Apple Mail (2.919.2)
Cc: john.loughney@nokia.com, "nsis \(\(E-mail\)\)" <nsis@ietf.org>
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0801467514=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


--===============0801467514==
Content-Type: multipart/alternative; boundary=Apple-Mail-9-265496035


--Apple-Mail-9-265496035
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Jerry,

> This is confusing to me because admission priority has nothing to do  
> with Y.1541.  Y.1541 is associated with the <Y.1541.QoS Class> field  
> (see Section 5.2.14 of the updated -19 QSPEC document or Section  
> 6.2.14 of the current -18 QSPEC document).

mea culpa!!!  in my ramblings, I meant Y.1571, so just swap all  
reference of Y.1541 with Y.1571 from my previous postings

>
> QSPEC admission priority is simply using the 3 priority levels  
> already standardized by Y.2171.  Admission priority is a generic  
> concept, not invented by the ITU, so this is not 'ITU admission  
> priority', just plain ole' admission priority.

I beg to differ.  We are in agreement that admission priority is a  
generic concept, but in Section 6.2.9 of the QSPEC you have bound an  
Admission Priority field with pre-existing values defined in Y.1571   
as written in the following:

	High priority flows, normal priority flows, and best-effort priority
	flows can have access to resources depending on their admission
	priority value, as described in [Y.1571], as follows:

	Admission Priority:

	0 - best-effort priority flow
	1 - normal priority flow
	2 - high priority flow

And now we're told these values are to be updated by Y.2171.  By the  
way, could you tell us what these new values are?  Some of the members  
of the NSIS list are not members of the ITU, and so don't have that  
information on hand.

> What's missing here is an explanation of what the approach is in  
> [EMERGENCY-RSVP].  As I posted earlier in http://www.ietf.org/mail-archive/web/nsis/current/msg08231.html 
> :

as stated by francois:

 >> o Regarding Admission Priority:
 >> 	* every protocol spec will only indicate that "higher value means
 >> higher priority".
 >> 	* there is no attempt to define what specific values should be
 >> used for what. this is left outside the scope of the protocol specs.
but to get to the specifics of what you ask below...

>  "QSPEC is ... standardizing 3 priority levels to have end-to-end  
> cross-domain significance.
>
> If we elimate this standardization, as is proposed (in [EMERGENCY- 
> RSVP]), then different admission priority values can be assigned in  
> different Admin domains, and will have no end-to-end significance.   
> For example, Admin-domain 1, Admin-domain 2, and Admin-domain 3  
> assign admission priority=2,  admission priority=4, admission  
> priority=10 for the highest level priority, respectively.  Admin- 
> domain 1 and Admin-domain 2 try to initiate end-to-end flows via  
> Admin-domain 3 for a 'high priority' flow.  However, Admin-domain 3  
> has no idea how to treat the flow admission priority since all 3  
> domains are using different encodings of high priority."
>
> I've not seen a response to the above example and/or an explanation  
> of how the [EMERGENCY-RSVP] approach achieves end-to-end cross- 
> domain standardization?

[emergency-rsvp] has a policy element that contains numeric-only  
namespace & priority values that can be used as a standard cross- 
domain agreement of sets of priorities.  from this tuple, one can map  
to a locally defined Admission Priority set.  if we take an example  
namespace of "FOO-A", we'll assume: (a)  some set of domains have been  
contracted to support it, and (b) initially, that set of domains  
choose to support the service models of Y.1571.  Here we have an exact  
end-to-end consistency that is agreed to  on a per-domain basis.

later, a subset of these domains (AD-2, AD-3) decide to support  
another namespace "FOO-B", which specifically calls for support of a  
service lower than best effort.  These set of domains then decide to  
support SUPER-Admission-Priority-SET, which is not defined by the ITU  
but includes the values defined Y.1571 along with lower-than-best- 
effort Admission Priority in order to support FOO-B.

policy decision points at the domain edges would do the mappings  
between namespace.priority tuple to admission priority.  and in the  
case of rfc-3181, this would include preemption priority if so needed.

>  Perhaps it is some different approach to priority more like  
> preemption priority?

preemption and defending priority for RSVP is already covered by  
rfc-3181, as mentioned in [emergency-rsvp]

> Perhaps the [EMERGENCY-RSVP] approach should be called "RSVP- 
> priority"?

why?  lets take a step back and see what you are requesting.  you are  
taking what we agree to be a generic named field of Admission Priority  
and asking all of us to only populate it with values defined by the  
ITU.  perhaps I see things oddly, but to me, this field is no longer  
generic but rather explicitly bound to an ITU document.  and please  
note I have no qualms about binding a field to an ITU document, but I  
don't consider that field to be generic.

now, I'll re-ask my question.  if we follow your original approach  
concerning the Admission Priority field, how do we know what priority  
set is to be supported if the ITU comes back and updates Y.2171 with a  
different set of values?  the QSPEC document started with Y.1571, and  
now we have Y.2171.  Certainly a flag day is not what is expected as a  
solution to support Y.<next-priority-set>.

-ken

ps, all is not lost from the original agreement back in Nov/Dec.  All  
three documents are (I believe :-) still in agreement about the  
Namespace.Priority fields and their IANA registration.  If we cannot  
come to consensus about the Admission Priority, then we drop that from  
the agreement.


--Apple-Mail-9-265496035
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>Jerry,</div><div><br =
class=3D"webkit-block-placeholder"></div><blockquote type=3D"cite">  =
<div><span class=3D"Apple-style-span" style=3D"-webkit-text-stroke-width: =
-1; ">This is confusing to me because&nbsp;admission priority has =
nothing to do with Y.1541.&nbsp; Y.1541 is associated with&nbsp;the =
&lt;Y.1541.QoS Class&gt; field (see Section 5.2.14 of the updated -19 =
QSPEC document or Section 6.2.14 of the current -18 QSPEC =
document).&nbsp;</span></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>mea culpa!!! &nbsp;in my =
ramblings, I meant Y.1571, so just swap all reference of Y.1541 with =
Y.1571 from my previous postings</div><br><blockquote =
type=3D"cite"><div><span class=3D"Apple-style-span" =
style=3D"-webkit-text-stroke-width: -1; ">&nbsp;</span></div>  =
<div><font class=3D"Apple-style-span" face=3D"Arial" size=3D"3"><span =
class=3D"Apple-style-span" style=3D"FONT-SIZE: 13px">QSPEC admission =
priority is simply using the 3 priority levels already standardized by =
Y.2171.&nbsp; Admission priority is a generic concept, not invented by =
the ITU, so this is not 'ITU admission priority', just plain ole' =
admission priority.</span></font></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>I beg to differ. &nbsp;We =
are in agreement that admission priority is a generic concept, but in =
Section 6.2.9 of the QSPEC&nbsp;you have bound an Admission Priority =
field with pre-existing values defined in Y.1571 &nbsp;as written in the =
following:</div><div><br =
class=3D"webkit-block-placeholder"></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>High =
priority flows, normal priority flows, and best-effort priority&nbsp;<br =
class=3D"webkit-block-placeholder"></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>flows can =
have access to resources depending on their admission<br =
class=3D"webkit-block-placeholder"></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>priority =
value, as described in [Y.1571], as follows:<br =
class=3D"webkit-block-placeholder"></div><div><br =
class=3D"webkit-block-placeholder"></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Admission =
Priority:<br class=3D"webkit-block-placeholder"></div><div><br =
class=3D"webkit-block-placeholder"></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>0 - =
best-effort priority flow<br =
class=3D"webkit-block-placeholder"></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>1 - =
normal priority flow<br =
class=3D"webkit-block-placeholder"></div><div><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>2 - high =
priority flow<br class=3D"webkit-block-placeholder"></div><div><br =
class=3D"webkit-block-placeholder"></div><div>And now we're told these =
values are to be updated by Y.2171. &nbsp;By the way, could you tell us =
what these new values are? &nbsp;Some of the members of the NSIS list =
are not members of the ITU, and so don't have that information on =
hand.</div><div><br class=3D"webkit-block-placeholder"></div><blockquote =
type=3D"cite">  <div><font class=3D"Apple-style-span" face=3D"Arial" =
size=3D"3"><span class=3D"Apple-style-span" style=3D"FONT-SIZE: =
13px">What's missing here&nbsp;is an explanation of what the approach is =
in [EMERGENCY-RSVP].&nbsp; As I&nbsp;posted earlier in&nbsp;<a =
href=3D"http://www.ietf.org/mail-archive/web/nsis/current/msg08231.html">h=
ttp://www.ietf.org/mail-archive/web/nsis/current/msg08231.html</a>:</span>=
</font></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>as stated by =
francois:</div><div><br></div><div><span class=3D"Apple-style-span" =
style=3D"font-family: Times; font-size: 16px; "><pre style=3D"font-size: =
12px; ">&gt;&gt; o Regarding Admission Priority:
&gt;&gt; 	* every protocol spec will only indicate that "higher =
value means =20
&gt;&gt; higher priority".
&gt;&gt; 	* there is no attempt to define what specific values =
should be =20
&gt;&gt; used for what. this is left outside the scope of the protocol =
specs.</pre></span></div>but to get to the specifics of what you ask =
below...</div><div><br><blockquote type=3D"cite">  <div><font =
class=3D"Apple-style-span" face=3D"Arial" size=3D"3"><span =
class=3D"Apple-style-span" style=3D"FONT-SIZE: =
13px"></span></font>&nbsp;<span class=3D"Apple-style-span" =
style=3D"-webkit-text-stroke-width: -1; ">"QSPEC is&nbsp;... =
standardizing 3 priority levels to have end-to-end cross-domain =
significance.</span></div><div><font class=3D"Apple-style-span" =
face=3D"Arial" size=3D"3"><span class=3D"Apple-style-span" =
style=3D"FONT-SIZE: 13px"><div>&nbsp;</div>  <div>If we elimate this =
standardization, as is proposed (in [EMERGENCY-RSVP]), then different =
admission priority values&nbsp;can be&nbsp;assigned in different Admin =
domains, and will&nbsp;have no end-to-end significance.&nbsp; For =
example, Admin-domain 1, Admin-domain 2, and Admin-domain 3 =
assign&nbsp;admission priority=3D2,&nbsp;&nbsp;admission priority=3D4, =
admission priority=3D10 for the highest level priority, =
respectively.&nbsp; Admin-domain 1 and Admin-domain 2 try to initiate =
end-to-end flows via Admin-domain&nbsp;3 for a 'high priority' =
flow.&nbsp;&nbsp;However, Admin-domain 3 has no idea how to treat the =
flow admission priority since all 3 domains are using different =
encodings of high priority."</div>  <div>&nbsp;</div>  <div>I've not =
seen a response to the above example and/or an explanation of how the =
[EMERGENCY-RSVP] approach achieves end-to-end cross-domain =
standardization?</div></span></font></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>[emergency-rsvp] has a =
policy element that contains numeric-only namespace &amp; priority =
values that can be used as a standard cross-domain agreement of sets of =
priorities. &nbsp;from this tuple, one can map to a locally defined =
Admission Priority set. &nbsp;if we take an example namespace of =
"FOO-A", we'll assume: (a) &nbsp;some set of domains have been =
contracted to support it, and (b) initially, that set of domains choose =
to support the service models of Y.1571. &nbsp;Here we have an exact =
end-to-end consistency that is agreed to &nbsp;on a per-domain basis. =
&nbsp;</div><div><br class=3D"webkit-block-placeholder"></div><div>later, =
a subset of these domains (AD-2, AD-3) decide to support another =
namespace "FOO-B", which specifically calls for support of a service =
lower than best effort. &nbsp;These set of domains then decide to =
support SUPER-Admission-Priority-SET, which is not defined by the ITU =
but includes the values defined Y.1571 along with lower-than-best-effort =
Admission Priority in order to support FOO-B. &nbsp;</div><div><br =
class=3D"webkit-block-placeholder"></div><div>policy decision points at =
the domain edges would do the mappings between namespace.priority tuple =
to admission priority. &nbsp;and in the case of rfc-3181, this would =
include preemption priority if so =
needed.</div><div><br></div><blockquote type=3D"cite"><div><font =
class=3D"Apple-style-span" face=3D"Arial" size=3D"3"><span =
class=3D"Apple-style-span" style=3D"FONT-SIZE: 13px"><div><span =
class=3D"Apple-style-span" style=3D"font-size: 14px; =
-webkit-text-stroke-width: -1; ">&nbsp;Perhaps it is some different =
approach to priority more like preemption priority?&nbsp; =
</span></div></span></font></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>preemption and defending =
priority for RSVP is already covered by rfc-3181, as mentioned in =
[emergency-rsvp]</div><br><blockquote type=3D"cite"><div><font =
class=3D"Apple-style-span" face=3D"Arial" size=3D"3"><span =
class=3D"Apple-style-span" style=3D"FONT-SIZE: 13px"><div><span =
class=3D"Apple-style-span" style=3D"font-size: 14px; =
-webkit-text-stroke-width: -1; ">Perhaps the [EMERGENCY-RSVP] approach =
should be called =
"RSVP-priority"?</span></div></span></font></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>why? &nbsp;lets take a =
step back and see what you are requesting. &nbsp;you are taking what we =
agree to be a generic named field of Admission Priority and asking all =
of us to only populate it with values defined by the ITU. &nbsp;perhaps =
I see things oddly, but to me, this field is no longer generic but =
rather explicitly bound to an ITU document. &nbsp;and please note I have =
no qualms about binding a field to an ITU document, but I don't consider =
that field to be generic.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>now, I'll re-ask my =
question. &nbsp;if we follow your original approach concerning the =
Admission Priority field, how do we know what priority set is to be =
supported if the ITU comes back and updates Y.2171 with a different set =
of values? &nbsp;the QSPEC document started with Y.1571, and now we have =
Y.2171. &nbsp;Certainly a flag day is not what is expected as a solution =
to support Y.&lt;next-priority-set&gt;. &nbsp;</div><div><br =
class=3D"webkit-block-placeholder"></div></div><div>-ken</div><div><br =
class=3D"webkit-block-placeholder"></div><div>ps, all is not lost from =
the original agreement back in Nov/Dec. &nbsp;All three documents are (I =
believe :-) still in agreement about the Namespace.Priority fields and =
their IANA registration. &nbsp;If we cannot come to consensus about the =
Admission Priority, then we drop that from the agreement.</div><div><br =
class=3D"webkit-block-placeholder"></div></body></html>=

--Apple-Mail-9-265496035--

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

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

--===============0801467514==--


From nsis-bounces@ietf.org  Tue Feb 26 12:48:51 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0D3753A6878;
	Tue, 26 Feb 2008 12:48:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.082
X-Spam-Level: 
X-Spam-Status: No, score=-0.082 tagged_above=-999 required=5 tests=[AWL=0.355,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	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 Q9WOShUIahur; Tue, 26 Feb 2008 12:48:50 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3FF573A6B68;
	Tue, 26 Feb 2008 12:48:50 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DD3A83A6CEF
	for <nsis@core3.amsl.com>; Tue, 26 Feb 2008 12:48:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 r3NBlHQWgzny for <nsis@core3.amsl.com>;
	Tue, 26 Feb 2008 12:48:47 -0800 (PST)
Received: from QMTA08.westchester.pa.mail.comcast.net
	(qmta08.westchester.pa.mail.comcast.net [76.96.62.80])
	by core3.amsl.com (Postfix) with ESMTP id CCCEC28C7EF
	for <nsis@ietf.org>; Tue, 26 Feb 2008 12:47:31 -0800 (PST)
Received: from OMTA04.westchester.pa.mail.comcast.net ([76.96.62.35])
	by QMTA08.westchester.pa.mail.comcast.net with comcast
	id uCUK1Y0030ldTLk580f800; Tue, 26 Feb 2008 20:47:00 +0000
Received: from [192.168.1.120] ([69.255.66.123])
	by OMTA04.westchester.pa.mail.comcast.net with comcast
	id uLnP1Y0032fa1BZ3Q00000; Tue, 26 Feb 2008 20:47:23 +0000
X-Authority-Analysis: v=1.0 c=1 a=5NZpY6yATj7C73OzZ08A:9
	a=taUIcKKT0weLnByo1DMGn0f5Ac0A:4 a=M3PvEdNFSBYA:10
Message-Id: <E87AE144-7717-4D3C-B0BD-E23C290AA88D@g11.org.uk>
From: ken carlberg <carlberg@g11.org.uk>
To: Al Morton <acmorton@att.com>
In-Reply-To: <200802252058.m1PKw8CD006480@klph001.kcdc.att.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 26 Feb 2008 15:47:22 -0500
References: <5F6519BF2DE0404D99B7C75607FF76FF4D0A45@mx1.office>
	<200802252058.m1PKw8CD006480@klph001.kcdc.att.com>
X-Mailer: Apple Mail (2.919.2)
Cc: nsis@ietf.org
Subject: Re: [NSIS] (no subject)
X-BeenThere: nsis@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Next Steps in Signaling <nsis.ietf.org>
List-Unsubscribe: <http://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: <http://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


> PS I don't think there's a connection between Y.1541 and
> the various ITU-T Admission Recs (Y.1571, now Y.2171).
> Y.1541 specifies categories of performance objectives (mostly), and
> it seems like a Scavenger service would have "Unspecified" objectives
> (same as the Y.1541 Best Effort). Scavenger is more about *when* it
> works than about how well, IMO.

again, my fault for twisting the references around.  I meant to refer  
to Y.1571

as for scavenger service, it uses resources not used by best effort or  
better than best effort flows.  so, if we assume a transit node only  
supports best effort, then during bursty spikes in load will allocate  
available resources to BE at the expense of scavenger service.  that  
may be a case of "when", but the result is a service below that of BE  
since you are not relying on random drop or drop from head schemas.

outside of scavenger service, I know of another on-going proprietary  
effort at lower than best effort service.

regards,

-ken

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


From nsis-bounces@ietf.org  Tue Feb 26 14:39:10 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 418AF3A6CC7;
	Tue, 26 Feb 2008 14:39:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.073
X-Spam-Level: *
X-Spam-Status: No, score=1.073 tagged_above=-999 required=5 tests=[AWL=0.282,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_MESSAGE=1, MIME_HTML_MOSTLY=0.001, RDNS_NONE=0.1,
	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 k-YAdTDB28G1; Tue, 26 Feb 2008 14:39:07 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC94A3A68BE;
	Tue, 26 Feb 2008 14:39:07 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C696F3A69D7
	for <nsis@core3.amsl.com>; Tue, 26 Feb 2008 14:39:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 zZCh0KeujNa7 for <nsis@core3.amsl.com>;
	Tue, 26 Feb 2008 14:39:04 -0800 (PST)
Received: from web63604.mail.re1.yahoo.com (web63604.mail.re1.yahoo.com
	[69.147.97.74]) by core3.amsl.com (Postfix) with SMTP id D33153A6869
	for <nsis@ietf.org>; Tue, 26 Feb 2008 14:39:03 -0800 (PST)
Received: (qmail 8141 invoked by uid 60001); 26 Feb 2008 22:38:57 -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=rOHCxI9ZjGqYVNvDOkSw9p9V1yQjAZ3ItXuHzmVQCSLEEcP0dEm08oeHa27TQkGMnx0MFNOB+rAB3PQHOzpdC5w0O6vFQSPz6z4H21B6FhxJ00N6Qagn/5BCrdd0zySBteraL8Ae4kNRkpUbwClL1sWyYZi/8KWzjRnHrt+HMI4=;
X-YMail-OSG: 36WR5gUVM1mEQPxUa2IG6nr3mBlRKfW6aNZ6fhBG
Received: from [76.19.255.157] by web63604.mail.re1.yahoo.com via HTTP;
	Tue, 26 Feb 2008 14:38:57 PST
Date: Tue, 26 Feb 2008 14:38:57 -0800 (PST)
From: Gerald Ash <gash5107@yahoo.com>
To: ken carlberg <carlberg@g11.org.uk>, "nsis \(\(E-mail\)\)" <nsis@ietf.org>
In-Reply-To: <8235DDEA-6B91-4151-8E2F-E6EC01AD470D@g11.org.uk>
MIME-Version: 1.0
Message-ID: <379162.6526.qm@web63604.mail.re1.yahoo.com>
Cc: john.loughney@nokia.com
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0347166414=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

--===============0347166414==
Content-Type: multipart/alternative; boundary="0-1139383281-1204065537=:6526"
Content-Transfer-Encoding: 8bit

--0-1139383281-1204065537=:6526
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Ken,
   
  > Jerry,
 
>> This is confusing to me because admission priority has nothing to do with 
>> Y.1541.  Y.1541 is associated with the <Y.1541.QoS Class> field (see Section 
>> 5.2.14 of the updated -19 QSPEC document or Section 6.2.14 of the 
>> current -18 QSPEC document).
 
> mea culpa!!!  in my ramblings, I meant Y.1571, so just swap all reference of 
> Y.1541 with Y.1571 from my previous postings
   
  There is no Y.1571, only Y.2171 (it was renumbered).
 
>> QSPEC admission priority is simply using the 3 priority levels already 
>> standardized by Y.2171.  Admission priority is a generic concept, not 
>> invented by the ITU, so this is not 'ITU admission priority', just plain 
>> ole' admission priority.
 
> I beg to differ.  We are in agreement that admission priority is a generic 
> concept, but in Section 6.2.9 of the QSPEC you have bound an Admission 
> Priority field with pre-existing values defined in Y.1571  as written in the 
> following:
> 
> High priority flows, normal priority flows, and best-effort priority
> flows can have access to resources depending on their admission
> priority value, as described in [Y.1571], as follows:
> 
> Admission Priority:
> 0 - best-effort priority flow
> 1 - normal priority flow
> 2 - high priority flow
> 
> And now we're told these values are to be updated by Y.2171.  By the way, 
> could you tell us what these new values are?  Some of the members of the 
> NSIS list are not members of the ITU, and so don't have that information on 
> hand.
   
  The values are unchanged.  There is no Y.1571, it was renumbered Y.2171, the reference has been corrected in QSPEC -19.  
   
  You don't have to be a member of ITU to get a recommendation, they are all freely available on the www.itu.int web-site.  Y.2171 can be downloaded at http://www.itu.int/rec/T-REC-Y.2171/en.  
   
  BTW, essentially all service providers and equipment vendors belong to and participate in the ITU.  All these service providers and equipment vendors have unanimously agreed to Y.2171.
  
>> What's missing here is an explanation of what the approach is in 
>> [EMERGENCY-RSVP].  As I posted earlier in 
>> http://www.ietf.org/mail-archive/web/nsis/current/msg08231.html:
 
> as stated by francois:
> 
> o Regarding Admission Priority:
>  * every protocol spec will only indicate that "higher value means
> higher priority".
>  * there is no attempt to define what specific values should be
> used for what. this is left outside the scope of the protocol specs.
> but to get to the specifics of what you ask below...
   
  The above "proposed agreement" doesn't at all describe the complex approach apparently being taken by [EMERGENCY-RSVP] to 'admission priority', as illustrated by your example below.  It is a very different approach to 'admission priority' from what QSPEC is standardizing.
   
  >> "QSPEC is ... standardizing 3 priority levels to have end-to-end 
>> cross-domain significance.
>> 
>> If we elimate this standardization, as is proposed (in [EMERGENCY-RSVP]), 
>> then different admission priority values can be assigned in different Admin 
>> domains, and will have no end-to-end significance.  For example, 
>> Admin-domain 1, Admin-domain 2, and Admin-domain 3 assign admission 
>> priority=2,  admission priority=4, admission priority=10 for the highest 
>> level priority, respectively.  Admin-domain 1 and Admin-domain 2 try to 
>> initiate end-to-end flows via Admin-domain 3 for a 'high priority' flow. 
>> However, Admin-domain 3 has no idea how to treat the flow admission priority 
>> since all 3 domains are using different encodings of high priority."
>>
>> I've not seen a response to the above example and/or an explanation of how 
>> the [EMERGENCY-RSVP] approach achieves end-to-end cross-domain 
>> standardization?
   
  > [emergency-rsvp] has a policy element that contains numeric-only namespace & 
> priority values that can be used as a standard cross-domain agreement of 
> sets of priorities.  from this tuple, one can map to a locally defined 
> Admission Priority set.  if we take an example namespace of "FOO-A", we'll 
> assume: (a)  some set of domains have been contracted to support it, and (b) 
> initially, that set of domains choose to support the service models of 
> Y.1571.  Here we have an exact end-to-end consistency that is agreed to  on 
> a per-domain basis.
  >
> later, a subset of these domains (AD-2, AD-3) decide to support another 
> namespace "FOO-B", which specifically calls for support of a service lower 
> than best effort.  These set of domains then decide to support 
> SUPER-Admission-Priority-SET, which is not defined by the ITU but includes 
> the values defined Y.1571 along with lower-than-best-effort Admission 
> Priority in order to support FOO-B.
> 
> policy decision points at the domain edges would do the mappings between 
> namespace.priority tuple to admission priority.  and in the case of 
> rfc-3181, this would include preemption priority if so needed.
   
  This is a very different approach to 'admission priority' from what QSPEC is standardizing.  You are introducing policy elements, PDPs doing 'mappings', preemption, and namespaces.  AFAIK preemption priority doesn't have namespaces, are you perhaps referring to RPH namespaces here?  In any case it appears that [EMERGENCY-RSVP] is doing something quite different from what QSPEC is doing.  
   
  The "proposed agreement" should have fully described what the proposed change is.  I.e., you want to scrap whatever *was* in QSPEC and replace it with something else being done in [EMERGENCY-RSVP], but undefined in the proposed agreement.
   
  >> Perhaps the [EMERGENCY-RSVP] approach should be called "RSVP-priority"?

  
> why? 
   
  Because, as above, it's a totally different approach from QSPEC.  It doesn't look much like the approach agreed by all participating service providers/equipment vendors in Y.2171.  BTW, the Y.2171 approach matches admission priority as implemented in some networks.
   
  > lets take a step back and see what you are requesting.  you are taking 
> what we agree to be a generic named field of Admission Priority and asking 
> all of us to only populate it with values defined by the ITU.  perhaps I see 
> things oddly, but to me, this field is no longer generic but rather 
> explicitly bound to an ITU document.  and please note I have no qualms about 
> binding a field to an ITU document, but I don't consider that field to be 
> generic.
> 
> now, I'll re-ask my question.  if we follow your original approach 
> concerning the Admission Priority field, how do we know what priority set is 
> to be supported if the ITU comes back and updates Y.2171 with a different 
> set of values?  the QSPEC document started with Y.1571, and now we have 
> Y.2171.  Certainly a flag day is not what is expected as a solution to 
> support Y.<next-priority-set>.
   
  There is only Y.2171 and no Y.1571.  If ITU modifies Y.2171 later, say adds more values, IANA tracks those changes into the admission priority registry defined in QSPEC.  This is standard IANA policy; registries do not have to be based *only* on IETF standards, they can be based on standards from other SDOs.  I pointed this out earlier based on my discussion with IANA a while ago.
  
> ps, all is not lost from the original agreement back in Nov/Dec.  All three 
> documents are (I believe :-) still in agreement about the Namespace.Priority 
> fields and their IANA registration.  If we cannot come to consensus about 
> the Admission Priority, then we drop that from the agreement.
   
  That appears to be the case.  However, it would be good to have other WG members weigh in on this issue.
   
  Jerry


ken carlberg <carlberg@g11.org.uk> wrote:      Jerry,
  

    This is confusing to me because admission priority has nothing to do with Y.1541.  Y.1541 is associated with the <Y.1541.QoS Class> field (see Section 5.2.14 of the updated -19 QSPEC document or Section 6.2.14 of the current -18 QSPEC document). 
  

  mea culpa!!!  in my ramblings, I meant Y.1571, so just swap all reference of Y.1541 with Y.1571 from my previous postings

     
  QSPEC admission priority is simply using the 3 priority levels already standardized by Y.2171.  Admission priority is a generic concept, not invented by the ITU, so this is not 'ITU admission priority', just plain ole' admission priority.
  

  I beg to differ.  We are in agreement that admission priority is a generic concept, but in Section 6.2.9 of the QSPEC you have bound an Admission Priority field with pre-existing values defined in Y.1571  as written in the following:
  

  High priority flows, normal priority flows, and best-effort priority 

  flows can have access to resources depending on their admission

  priority value, as described in [Y.1571], as follows:

  

  Admission Priority:

  

  0 - best-effort priority flow

  1 - normal priority flow

  2 - high priority flow

  

  And now we're told these values are to be updated by Y.2171.  By the way, could you tell us what these new values are?  Some of the members of the NSIS list are not members of the ITU, and so don't have that information on hand.
  

    What's missing here is an explanation of what the approach is in [EMERGENCY-RSVP].  As I posted earlier in http://www.ietf.org/mail-archive/web/nsis/current/msg08231.html:
  

  as stated by francois:
  

  
>> o Regarding Admission Priority:  >>  * every protocol spec will only indicate that "higher value means    >> higher priority".  >>  * there is no attempt to define what specific values should be    >> used for what. this is left outside the scope of the protocol specs.

but to get to the specifics of what you ask below...
  
     "QSPEC is ... standardizing 3 priority levels to have end-to-end cross-domain significance.
     
  If we elimate this standardization, as is proposed (in [EMERGENCY-RSVP]), then different admission priority values can be assigned in different Admin domains, and will have no end-to-end significance.  For example, Admin-domain 1, Admin-domain 2, and Admin-domain 3 assign admission priority=2,  admission priority=4, admission priority=10 for the highest level priority, respectively.  Admin-domain 1 and Admin-domain 2 try to initiate end-to-end flows via Admin-domain 3 for a 'high priority' flow.  However, Admin-domain 3 has no idea how to treat the flow admission priority since all 3 domains are using different encodings of high priority."
   
  I've not seen a response to the above example and/or an explanation of how the [EMERGENCY-RSVP] approach achieves end-to-end cross-domain standardization?

  

  [emergency-rsvp] has a policy element that contains numeric-only namespace & priority values that can be used as a standard cross-domain agreement of sets of priorities.  from this tuple, one can map to a locally defined Admission Priority set.  if we take an example namespace of "FOO-A", we'll assume: (a)  some set of domains have been contracted to support it, and (b) initially, that set of domains choose to support the service models of Y.1571.  Here we have an exact end-to-end consistency that is agreed to  on a per-domain basis.  
  

  later, a subset of these domains (AD-2, AD-3) decide to support another namespace "FOO-B", which specifically calls for support of a service lower than best effort.  These set of domains then decide to support SUPER-Admission-Priority-SET, which is not defined by the ITU but includes the values defined Y.1571 along with lower-than-best-effort Admission Priority in order to support FOO-B.  
  

  policy decision points at the domain edges would do the mappings between namespace.priority tuple to admission priority.  and in the case of rfc-3181, this would include preemption priority if so needed.
  

       Perhaps it is some different approach to priority more like preemption priority?  

  

  preemption and defending priority for RSVP is already covered by rfc-3181, as mentioned in [emergency-rsvp]

      Perhaps the [EMERGENCY-RSVP] approach should be called "RSVP-priority"?

  

  why?  lets take a step back and see what you are requesting.  you are taking what we agree to be a generic named field of Admission Priority and asking all of us to only populate it with values defined by the ITU.  perhaps I see things oddly, but to me, this field is no longer generic but rather explicitly bound to an ITU document.  and please note I have no qualms about binding a field to an ITU document, but I don't consider that field to be generic.
  

  now, I'll re-ask my question.  if we follow your original approach concerning the Admission Priority field, how do we know what priority set is to be supported if the ITU comes back and updates Y.2171 with a different set of values?  the QSPEC document started with Y.1571, and now we have Y.2171.  Certainly a flag day is not what is expected as a solution to support Y.<next-priority-set>.  
  


  -ken
  

  ps, all is not lost from the original agreement back in Nov/Dec.  All three documents are (I believe :-) still in agreement about the Namespace.Priority fields and their IANA registration.  If we cannot come to consensus about the Admission Priority, then we drop that from the agreement.
  



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

<DIV>Ken,</DIV>  <DIV>&nbsp;</DIV>  <DIV>&gt; Jerry,<BR>&nbsp;<BR>&gt;&gt; This is confusing to me because admission priority has nothing to do with <BR>&gt;&gt; Y.1541.&nbsp; Y.1541 is associated with the &lt;Y.1541.QoS Class&gt; field (see Section <BR>&gt;&gt; 5.2.14 of the updated -19 QSPEC document or Section 6.2.14 of the <BR>&gt;&gt; current -18 QSPEC document).<BR>&nbsp;<BR>&gt; mea culpa!!!&nbsp; in my ramblings, I meant Y.1571, so just swap all reference of <BR>&gt; Y.1541 with Y.1571 from my previous postings</DIV>  <DIV>&nbsp;</DIV>  <DIV>There is no Y.1571, only Y.2171 (it was renumbered).<BR>&nbsp;<BR>&gt;&gt; QSPEC admission priority is simply using the 3 priority levels already <BR>&gt;&gt; standardized by Y.2171.&nbsp; Admission priority is a generic concept, not <BR>&gt;&gt; invented by the ITU, so this is not 'ITU admission priority', just plain <BR>&gt;&gt; ole' admission priority.<BR>&nbsp;<BR>&gt; I beg to differ.&nbsp; We are in agreement that
 admission priority is a generic <BR>&gt; concept, but in Section 6.2.9 of the QSPEC you have bound an Admission <BR>&gt; Priority field with pre-existing values defined in Y.1571&nbsp; as written in the <BR>&gt; following:<BR>&gt;&nbsp;<BR>&gt; High priority flows, normal priority flows, and best-effort priority<BR>&gt; flows can have access to resources depending on their admission<BR>&gt; priority value, as described in [Y.1571], as follows:<BR>&gt; <BR>&gt; Admission Priority:<BR>&gt; 0 - best-effort priority flow<BR>&gt; 1 - normal priority flow<BR>&gt; 2 - high priority flow<BR>&gt; <BR>&gt; And now we're told these values are to be updated by Y.2171.&nbsp; By the way, <BR>&gt; could you tell us what these new values are?&nbsp; Some of the members of the <BR>&gt; NSIS list are not members of the ITU, and so don't have that information on <BR>&gt; hand.</DIV>  <DIV>&nbsp;</DIV>  <DIV>The values are unchanged.&nbsp; There is no Y.1571, it was renumbered Y.2171, the
 reference has been corrected in QSPEC -19.&nbsp; </DIV>  <DIV>&nbsp;</DIV>  <DIV>You don't have to be a member of ITU to get a recommendation, they are all freely available on the <A href="http://www.itu.int">www.itu.int</A> web-site.&nbsp; Y.2171 can be downloaded&nbsp;at <A href="http://www.itu.int/rec/T-REC-Y.2171/en">http://www.itu.int/rec/T-REC-Y.2171/en</A>.&nbsp; </DIV>  <DIV>&nbsp;</DIV>  <DIV>BTW,&nbsp;essentially all service providers and equipment vendors belong to and participate in the ITU.&nbsp; All these service providers and equipment vendors have unanimously agreed to Y.2171.</DIV>  <DIV><BR>&gt;&gt; What's missing here is an explanation of what the approach is in <BR>&gt;&gt; [EMERGENCY-RSVP].&nbsp; As I posted earlier in <BR>&gt;&gt; <A
 href="mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000015/!x-usc:http://www.ietf.org/mail-archive/web/nsis/current/msg08231.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08231.html</A>:<BR>&nbsp;<BR>&gt; as stated by francois:<BR>&gt;&nbsp;<BR>&gt; o Regarding Admission Priority:<BR>&gt;&nbsp; * every protocol spec will only indicate that "higher value means<BR>&gt; higher priority".<BR>&gt;&nbsp; * there is no attempt to define what specific values should be<BR>&gt; used for what. this is left outside the scope of the protocol specs.<BR>&gt; but to get to the specifics of what you ask below...</DIV>  <DIV>&nbsp;</DIV>  <DIV>The above&nbsp;"proposed agreement" doesn't at all describe&nbsp;the complex approach apparently being taken by [EMERGENCY-RSVP] to 'admission priority', as illustrated by your example below.&nbsp; It is a very different approach to 'admission priority' from what&nbsp;QSPEC is standardizing.</DIV>  <DIV>&nbsp;</DIV> 
 <DIV>&gt;&gt;&nbsp;"QSPEC is ... standardizing 3 priority levels to have end-to-end <BR>&gt;&gt; cross-domain significance.<BR>&gt;&gt; <BR>&gt;&gt; If we elimate this standardization, as is proposed (in [EMERGENCY-RSVP]), <BR>&gt;&gt; then different admission priority values can be assigned in different Admin <BR>&gt;&gt; domains, and will have no end-to-end significance.&nbsp; For example, <BR>&gt;&gt; Admin-domain 1, Admin-domain 2, and Admin-domain 3 assign admission <BR>&gt;&gt; priority=2,&nbsp; admission priority=4, admission priority=10 for the highest <BR>&gt;&gt; level priority, respectively.&nbsp; Admin-domain 1 and Admin-domain 2 try to <BR>&gt;&gt; initiate end-to-end flows via Admin-domain 3 for a 'high priority' flow. <BR>&gt;&gt; However, Admin-domain 3 has no idea how to treat the flow admission priority <BR>&gt;&gt; since all 3 domains are using different encodings of high priority."<BR>&gt;&gt;<BR>&gt;&gt; I've not seen a response to the above example
 and/or an explanation of how <BR>&gt;&gt; the [EMERGENCY-RSVP] approach achieves end-to-end cross-domain <BR>&gt;&gt; standardization?</DIV>  <DIV>&nbsp;</DIV>  <DIV>&gt; [emergency-rsvp] has a policy element that contains numeric-only namespace &amp; <BR>&gt; priority values that can be used as a standard cross-domain agreement of <BR>&gt; sets of priorities.&nbsp; from this tuple, one can map to a locally defined <BR>&gt; Admission Priority set.&nbsp; if we take an example namespace of "FOO-A", we'll <BR>&gt; assume: (a)&nbsp; some set of domains have been contracted to support it, and (b) <BR>&gt; initially, that set of domains choose to support the service models of <BR>&gt; Y.1571.&nbsp; Here we have an exact end-to-end consistency that is agreed to&nbsp; on <BR>&gt; a per-domain basis.</DIV>  <DIV>&gt;<BR>&gt; later, a subset of these domains (AD-2, AD-3) decide to support another <BR>&gt; namespace "FOO-B", which specifically calls for support of a service lower
 <BR>&gt; than best effort.&nbsp; These set of domains then decide to support <BR>&gt; SUPER-Admission-Priority-SET, which is not defined by the ITU but includes <BR>&gt; the values defined Y.1571 along with lower-than-best-effort Admission <BR>&gt; Priority in order to support FOO-B.<BR>&gt; <BR>&gt; policy decision points at the domain edges would do the mappings between <BR>&gt; namespace.priority tuple to admission priority.&nbsp; and in the case of <BR>&gt; rfc-3181, this would include preemption priority if so needed.</DIV>  <DIV>&nbsp;</DIV>  <DIV>This&nbsp;is a very different approach to 'admission priority' from what QSPEC is standardizing.&nbsp; You are introducing policy elements, PDPs doing 'mappings', preemption, and namespaces.&nbsp; AFAIK preemption priority doesn't have namespaces, are you perhaps referring to RPH namespaces here?&nbsp; In any case it appears that [EMERGENCY-RSVP] is doing something quite different from what QSPEC is doing.&nbsp; </DIV> 
 <DIV>&nbsp;</DIV>  <DIV>The "proposed agreement" should have fully described what the proposed change is.&nbsp; I.e., you want to scrap whatever *was* in QSPEC and replace it with something else being done in [EMERGENCY-RSVP], but&nbsp;undefined in the proposed agreement.</DIV>  <DIV>&nbsp;</DIV>  <DIV>&gt;&gt; Perhaps the [EMERGENCY-RSVP] approach should be called "RSVP-priority"?<BR></DIV>  <DIV><BR>&gt; why?&nbsp;</DIV>  <DIV>&nbsp;</DIV>  <DIV>Because, as above, it's a totally different approach from QSPEC.&nbsp; It doesn't look much like the approach agreed by all participating service providers/equipment vendors&nbsp;in Y.2171.&nbsp;&nbsp;BTW, the Y.2171 approach matches admission priority as implemented in some networks.</DIV>  <DIV>&nbsp;</DIV>  <DIV>&gt;&nbsp;lets take a step back and see what you are requesting.&nbsp; you are taking <BR>&gt; what we agree to be a generic named field of Admission Priority and asking <BR>&gt; all of us to only populate it with
 values defined by the ITU.&nbsp; perhaps I see <BR>&gt; things oddly, but to me, this field is no longer generic but rather <BR>&gt; explicitly bound to an ITU document.&nbsp; and please note I have no qualms about <BR>&gt; binding a field to an ITU document, but I don't consider that field to be <BR>&gt; generic.<BR>&gt;&nbsp;<BR>&gt; now, I'll re-ask my question.&nbsp; if we follow your original approach <BR>&gt; concerning the Admission Priority field, how do we know what priority set is <BR>&gt; to be supported if the ITU comes back and updates Y.2171 with a different <BR>&gt; set of values?&nbsp; the QSPEC document started with Y.1571, and now we have <BR>&gt; Y.2171.&nbsp; Certainly a flag day is not what is expected as a solution to <BR>&gt; support Y.&lt;next-priority-set&gt;.</DIV>  <DIV>&nbsp;</DIV>  <DIV>There is only Y.2171 and no Y.1571.&nbsp; If ITU modifies Y.2171 later, say adds more values, IANA tracks those changes into the admission priority registry
 defined in QSPEC.&nbsp; This is standard IANA policy; registries do not have to be based *only* on IETF standards, they can be based on standards from other SDOs.&nbsp; I pointed this out earlier based on my discussion with IANA&nbsp;a while ago.</DIV>  <DIV><BR>&gt; ps, all is not lost from the original agreement back in Nov/Dec.&nbsp; All three <BR>&gt; documents are (I believe :-) still in agreement about the Namespace.Priority <BR>&gt; fields and their IANA registration.&nbsp; If we cannot come to consensus about <BR>&gt; the Admission Priority, then we drop that from the agreement.</DIV>  <DIV>&nbsp;</DIV>  <DIV>That appears to be the case.&nbsp; However, it would be good to have other WG members weigh in on this issue.</DIV>  <DIV>&nbsp;</DIV>  <DIV>Jerry</DIV><BR><BR><B><I>ken carlberg &lt;carlberg@g11.org.uk&gt;</I></B> wrote:  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">  <DIV>  <DIV>Jerry,</DIV>  <DIV><BR
 class=webkit-block-placeholder></DIV>  <BLOCKQUOTE type="cite">  <DIV><SPAN class=Apple-style-span style="-webkit-text-stroke-width: -1">This is confusing to me because&nbsp;admission priority has nothing to do with Y.1541.&nbsp; Y.1541 is associated with&nbsp;the &lt;Y.1541.QoS Class&gt; field (see Section 5.2.14 of the updated -19 QSPEC document or Section 6.2.14 of the current -18 QSPEC document).&nbsp;</SPAN></DIV></BLOCKQUOTE>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>mea culpa!!! &nbsp;in my ramblings, I meant Y.1571, so just swap all reference of Y.1541 with Y.1571 from my previous postings</DIV><BR>  <BLOCKQUOTE type="cite">  <DIV><SPAN class=Apple-style-span style="-webkit-text-stroke-width: -1"></SPAN>&nbsp;</DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">QSPEC admission priority is simply using the 3 priority levels already standardized by Y.2171.&nbsp; Admission priority is a generic
 concept, not invented by the ITU, so this is not 'ITU admission priority', just plain ole' admission priority.</SPAN></FONT></DIV></BLOCKQUOTE>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>I beg to differ. &nbsp;We are in agreement that admission priority is a generic concept, but in Section 6.2.9 of the QSPEC&nbsp;you have bound an Admission Priority field with pre-existing values defined in Y.1571 &nbsp;as written in the following:</DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV><SPAN class=Apple-tab-span style="WHITE-SPACE: pre"></SPAN>High priority flows, normal priority flows, and best-effort priority&nbsp;<BR class=webkit-block-placeholder></DIV>  <DIV><SPAN class=Apple-tab-span style="WHITE-SPACE: pre"></SPAN>flows can have access to resources depending on their admission<BR class=webkit-block-placeholder></DIV>  <DIV><SPAN class=Apple-tab-span style="WHITE-SPACE: pre"></SPAN>priority value, as described in [Y.1571], as follows:<BR
 class=webkit-block-placeholder></DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV><SPAN class=Apple-tab-span style="WHITE-SPACE: pre"></SPAN>Admission Priority:<BR class=webkit-block-placeholder></DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV><SPAN class=Apple-tab-span style="WHITE-SPACE: pre"></SPAN>0 - best-effort priority flow<BR class=webkit-block-placeholder></DIV>  <DIV><SPAN class=Apple-tab-span style="WHITE-SPACE: pre"></SPAN>1 - normal priority flow<BR class=webkit-block-placeholder></DIV>  <DIV><SPAN class=Apple-tab-span style="WHITE-SPACE: pre"></SPAN>2 - high priority flow<BR class=webkit-block-placeholder></DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>And now we're told these values are to be updated by Y.2171. &nbsp;By the way, could you tell us what these new values are? &nbsp;Some of the members of the NSIS list are not members of the ITU, and so don't have that information on hand.</DIV>  <DIV><BR
 class=webkit-block-placeholder></DIV>  <BLOCKQUOTE type="cite">  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">What's missing here&nbsp;is an explanation of what the approach is in [EMERGENCY-RSVP].&nbsp; As I&nbsp;posted earlier in&nbsp;<A href="http://www.ietf.org/mail-archive/web/nsis/current/msg08231.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08231.html</A>:</SPAN></FONT></DIV></BLOCKQUOTE>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>as stated by francois:</DIV>  <DIV><BR></DIV>  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 16px; FONT-FAMILY: Times"><PRE style="FONT-SIZE: 12px">&gt;&gt; o Regarding Admission Priority:  &gt;&gt;  * every protocol spec will only indicate that "higher value means    &gt;&gt; higher priority".  &gt;&gt;  * there is no attempt to define what specific values should be    &gt;&gt; used for what. this is left outside the scope of the protocol
 specs.</PRE></SPAN></DIV>but to get to the specifics of what you ask below...</DIV>  <DIV><BR>  <BLOCKQUOTE type="cite">  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px"></SPAN></FONT>&nbsp;<SPAN class=Apple-style-span style="-webkit-text-stroke-width: -1">"QSPEC is&nbsp;... standardizing 3 priority levels to have end-to-end cross-domain significance.</SPAN></DIV>  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">  <DIV>&nbsp;</DIV>  <DIV>If we elimate this standardization, as is proposed (in [EMERGENCY-RSVP]), then different admission priority values&nbsp;can be&nbsp;assigned in different Admin domains, and will&nbsp;have no end-to-end significance.&nbsp; For example, Admin-domain 1, Admin-domain 2, and Admin-domain 3 assign&nbsp;admission priority=2,&nbsp;&nbsp;admission priority=4, admission priority=10 for the highest level priority, respectively.&nbsp;
 Admin-domain 1 and Admin-domain 2 try to initiate end-to-end flows via Admin-domain&nbsp;3 for a 'high priority' flow.&nbsp;&nbsp;However, Admin-domain 3 has no idea how to treat the flow admission priority since all 3 domains are using different encodings of high priority."</DIV>  <DIV>&nbsp;</DIV>  <DIV>I've not seen a response to the above example and/or an explanation of how the [EMERGENCY-RSVP] approach achieves end-to-end cross-domain standardization?</DIV></SPAN></FONT></DIV></BLOCKQUOTE>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>[emergency-rsvp] has a policy element that contains numeric-only namespace &amp; priority values that can be used as a standard cross-domain agreement of sets of priorities. &nbsp;from this tuple, one can map to a locally defined Admission Priority set. &nbsp;if we take an example namespace of "FOO-A", we'll assume: (a) &nbsp;some set of domains have been contracted to support it, and (b) initially, that set of domains choose to
 support the service models of Y.1571. &nbsp;Here we have an exact end-to-end consistency that is agreed to &nbsp;on a per-domain basis. &nbsp;</DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>later, a subset of these domains (AD-2, AD-3) decide to support another namespace "FOO-B", which specifically calls for support of a service lower than best effort. &nbsp;These set of domains then decide to support SUPER-Admission-Priority-SET, which is not defined by the ITU but includes the values defined Y.1571 along with lower-than-best-effort Admission Priority in order to support FOO-B. &nbsp;</DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>policy decision points at the domain edges would do the mappings between namespace.priority tuple to admission priority. &nbsp;and in the case of rfc-3181, this would include preemption priority if so needed.</DIV>  <DIV><BR></DIV>  <BLOCKQUOTE type="cite">  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN
 class=Apple-style-span style="FONT-SIZE: 13px">  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 14px; -webkit-text-stroke-width: -1">&nbsp;Perhaps it is some different approach to priority more like preemption priority?&nbsp; </SPAN></DIV></SPAN></FONT></DIV></BLOCKQUOTE>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>preemption and defending priority for RSVP is already covered by rfc-3181, as mentioned in [emergency-rsvp]</DIV><BR>  <BLOCKQUOTE type="cite">  <DIV><FONT class=Apple-style-span face=Arial size=3><SPAN class=Apple-style-span style="FONT-SIZE: 13px">  <DIV><SPAN class=Apple-style-span style="FONT-SIZE: 14px; -webkit-text-stroke-width: -1">Perhaps the [EMERGENCY-RSVP] approach should be called "RSVP-priority"?</SPAN></DIV></SPAN></FONT></DIV></BLOCKQUOTE>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>why? &nbsp;lets take a step back and see what you are requesting. &nbsp;you are taking what we agree to be a generic named field of Admission
 Priority and asking all of us to only populate it with values defined by the ITU. &nbsp;perhaps I see things oddly, but to me, this field is no longer generic but rather explicitly bound to an ITU document. &nbsp;and please note I have no qualms about binding a field to an ITU document, but I don't consider that field to be generic.</DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>now, I'll re-ask my question. &nbsp;if we follow your original approach concerning the Admission Priority field, how do we know what priority set is to be supported if the ITU comes back and updates Y.2171 with a different set of values? &nbsp;the QSPEC document started with Y.1571, and now we have Y.2171. &nbsp;Certainly a flag day is not what is expected as a solution to support Y.&lt;next-priority-set&gt;. &nbsp;</DIV>  <DIV><BR class=webkit-block-placeholder></DIV></DIV>  <DIV>-ken</DIV>  <DIV><BR class=webkit-block-placeholder></DIV>  <DIV>ps, all is not lost from the original
 agreement back in Nov/Dec. &nbsp;All three documents are (I believe :-) still in agreement about the Namespace.Priority fields and their IANA registration. &nbsp;If we cannot come to consensus about the Admission Priority, then we drop that from the agreement.</DIV>  <DIV><BR class=webkit-block-placeholder></DIV></BLOCKQUOTE><BR><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-1139383281-1204065537=:6526--

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

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

--===============0347166414==--


From nsis-bounces@ietf.org  Tue Feb 26 14:55:09 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7D1463A6B68;
	Tue, 26 Feb 2008 14:55:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.241
X-Spam-Level: 
X-Spam-Status: No, score=0.241 tagged_above=-999 required=5 tests=[AWL=-1.540,
	BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1,
	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 BZAhiMWSFOUS; Tue, 26 Feb 2008 14:55:08 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7D4BD28C0FA;
	Tue, 26 Feb 2008 14:55:08 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6716728C0FA
	for <nsis@core3.amsl.com>; Tue, 26 Feb 2008 14:55:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 H16G7+McTs50 for <nsis@core3.amsl.com>;
	Tue, 26 Feb 2008 14:55:06 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117])
	by core3.amsl.com (Postfix) with ESMTP id 0B4D53A6B68
	for <nsis@ietf.org>; Tue, 26 Feb 2008 14:55:06 -0800 (PST)
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 26 Feb 2008 14:55:00 -0800
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m1QMsxda031258; 
	Tue, 26 Feb 2008 14:54:59 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m1QMsnpQ025784;
	Tue, 26 Feb 2008 22:54:59 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Feb 2008 14:54:55 -0800
Received: from [10.255.8.24] ([10.21.91.66]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Feb 2008 14:54:53 -0800
In-Reply-To: <A1F50CB516D211409DFD05D6B3CE6D300CD2B73E@KCCLUST06EVS1.ugd.att.com>
References: <17811FF8-52E1-48AC-9966-3B96798C1A0A@g11.org.uk>
	<19EBBEC503C3B5469070E0A6674A533A010C40F3@daebe104.NOE.Nokia.com>
	<13369810-81EB-4ABA-940B-EEF45823167D@g11.org.uk>
	<A1F50CB516D211409DFD05D6B3CE6D300CD2B73E@KCCLUST06EVS1.ugd.att.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <07EB0685-E9B2-42F0-A2C8-041CF46B3D6D@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Date: Tue, 26 Feb 2008 11:19:41 +0100
To: "TARAPORE, PERCY S, ATTLABS" <tarapore@att.com>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 26 Feb 2008 22:54:54.0236 (UTC)
	FILETIME=[99FE35C0:01C878CA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=8365; t=1204066499;
	x=1204930499; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com>
	|Subject:=20Re=3A=20Admission=20field=20in=20QSPECRE=3A=20[
	NSIS]=20Review=20of=20draft-ietf-nsis-qspec-18.txt |Sender:=20;
	bh=XTnaBwu/ZN0CB7QPWALtJP9qTsaP1hex5oWWcz+YSfg=;
	b=Lr2ioSWckV8vFhVH3VprvsderZUOasx27SIwCJEKZWjF7GkEcm6Zg/U33j
	M7F6ITZO1hpRzqDWxkYKS9/mCXVdxdct5kHB/mEK+aIZoIswOZbXkaEYyLoR
	HLVbH2N2T0;
Authentication-Results: sj-dkim-2; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
Cc: john.loughney@nokia.com, nsis@ietf.org
Subject: Re: [NSIS] Admission field in QSPECRE: Review of
	draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0393623105=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


--===============0393623105==
Content-Type: multipart/alternative; boundary=Apple-Mail-7-228198120


--Apple-Mail-7-228198120
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed


On 25 Feb 2008, at 23:49, TARAPORE, PERCY S, ATTLABS wrote:

> Ken,
>
> You state that Francois has "one way" that supposedly defines a  
> "common structure to hold the values and the ability to set the  
> values accordingly" as John desires.

As I said before, we are recommending that the Admission Priority  
value be handled in a similar way to how Preemption Priority is  
already handled today in NSIS and RSVP: it is up to the network  
administrator to decide what values should be used for what. If the  
network administrator wants to use values as defined in Y.2171, this  
is all fine and good. But if the network administrator decides to use  
different values, this is also fine too.

Francois


> I am somewhat at a loss here - what exactly has Francois described  
> that takes an incoming CAC priority value as desired by a customer  
> at the initial domain which then passes it on to the other domains  
> in the path. After all, Y.2171 is simply a vehicle for providing a  
> CAC priority value. It does not mandate how that value can be acted  
> upon in each domain.
>
> Thanks
>
> Percy
>
> From: ken carlberg [mailto:carlberg@g11.org.uk]
> Sent: Monday, February 25, 2008 3:28 PM
> To: john.loughney@nokia.com
> Cc: gash5107@yahoo.com; nsis@ietf.org; TARAPORE, PERCY S, ATTLABS;  
> flefauch@cisco.com
> Subject: Re: Admission field in QSPECRE: [NSIS] Review of draft- 
> ietf-nsis-qspec-18.txt
>
> John,
>
>> I think wee need to be able to support a few different scenarios  
>> and usages for the admission priority.  Is there a way that we  
>> could have a  common structure to hold the values, and the ability  
>> to set the values accordingly?
>
> we have one way, as described by Francois.
>
> however, if there is a segment that is absolutely adamant in having  
> a field reflect the defined values of Y.1541 or Y.2171bis in the  
> QSPEC, then I think a new field should be defined in that document  
> to contain those values.  The authors of the other documents can  
> decide if they too wish to add an ITU dependent field.
>
> the other option is to disregard any relation between the Admission  
> Priority field of the QSPEC and tsvwg-emergency-rsvp, which would  
> be a shame.
>
> -ken
>
>
>
>


--Apple-Mail-7-228198120
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
<br><div><div>On 25 Feb 2008, at 23:49, TARAPORE, PERCY S, ATTLABS =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">  <div dir=3D"ltr" align=3D"left"><span =
class=3D"886294622-25022008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">Ken,</font></span></div> <div dir=3D"ltr" align=3D"left"><span =
class=3D"886294622-25022008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span>=A0</div> <div dir=3D"ltr" align=3D"left"><span =
class=3D"886294622-25022008"> <div dir=3D"ltr" align=3D"left"><span =
class=3D"734462820-25022008"><font face=3D"Arial"><font =
color=3D"#0000ff"><font size=3D"2"><span class=3D"886294622-25022008">You =
state</span>=A0that Francois has "one way" that supposedly defines a =
"common structure to hold the values and the ability to set the values =
accordingly" as John desires. =
</font></font></font></span></div></span></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>As I said before, we are =
recommending that the Admission Priority value be handled in a similar =
way to how Preemption Priority is already handled today in NSIS and =
RSVP: it is up to the network administrator to decide what values should =
be used for what. If the network administrator wants to use values as =
defined in Y.2171, this is all fine and good. But if the network =
administrator decides to use different values, this is also fine =
too.</div><div><br></div><div>Francois</div><div>=A0</div><br><blockquote =
type=3D"cite"><div dir=3D"ltr" align=3D"left"><span =
class=3D"886294622-25022008"><div dir=3D"ltr" align=3D"left"><span =
class=3D"734462820-25022008"><font face=3D"Arial"><font =
color=3D"#0000ff"><font size=3D"2">I am somewhat at a loss here - what =
exactly has Francois described that takes an incoming CAC priority value =
as desired by a customer at the initial domain which then passes it on =
to the other domains in the path. After all, Y.2171 is simply a vehicle =
for providing a CAC priority value. It does not mandate how that value =
can be acted upon in each domain.</font></font></font></span></div> <div =
dir=3D"ltr" align=3D"left"><span class=3D"734462820-25022008"><font =
face=3D"Arial" color=3D"#0000ff" size=3D"2"></font></span>=A0</div> <div =
dir=3D"ltr" align=3D"left"><span class=3D"734462820-25022008"><span =
class=3D"886294622-25022008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">Thanks</font></span></span></div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"734462820-25022008"><span =
class=3D"886294622-25022008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2"></font></span></span>=A0</div> <div dir=3D"ltr" =
align=3D"left"><span class=3D"734462820-25022008"><span =
class=3D"886294622-25022008"><font face=3D"Arial" color=3D"#0000ff" =
size=3D"2">Percy</font></span></span></div></span></div><br> <div =
class=3D"OutlookMessageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"left"> =
<hr tabindex=3D"-1"> <font face=3D"Tahoma" size=3D"2"><b>From:</b> ken =
carlberg [<a =
href=3D"mailto:carlberg@g11.org.uk">mailto:carlberg@g11.org.uk</a>] =
<br><b>Sent:</b> Monday, February 25, 2008 3:28 PM<br><b>To:</b> <a =
href=3D"mailto:john.loughney@nokia.com">john.loughney@nokia.com</a><br><b>=
Cc:</b> <a href=3D"mailto:gash5107@yahoo.com">gash5107@yahoo.com</a>; <a =
href=3D"mailto:nsis@ietf.org">nsis@ietf.org</a>; TARAPORE, PERCY S, =
ATTLABS; <a =
href=3D"mailto:flefauch@cisco.com">flefauch@cisco.com</a><br><b>Subject:</=
b> Re: Admission field in QSPECRE: [NSIS] Review of =
draft-ietf-nsis-qspec-18.txt<br></font><br></div> <div></div>John,<br> =
<div> <div><br></div> <blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"WORD-SPACING: 0px; FONT: 11px Arial; =
TEXT-TRANSFORM: none; COLOR: rgb(0,0,255); TEXT-INDENT: 0px; =
WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate; =
orphans: 2; widows: 2; webkit-border-horizontal-spacing: 0px; =
webkit-border-vertical-spacing: 0px; webkit-text-decorations-in-effect: =
none; webkit-text-size-adjust: auto; webkit-text-stroke-width: 0">I   =
think wee need to be able to support a few different scenarios and =
usages   for=A0the admission priority.=A0 Is there a way that we could =
have   a<span class=3D"Apple-converted-space">=A0</span> common =
structure to hold the   values, and the ability to set the values =
accordingly?</span></blockquote></div><br> <div>we have one way, as =
described by Francois. =A0</div> <div><br =
class=3D"webkit-block-placeholder"></div> <div>however, if there is a =
segment that is absolutely adamant in having a field reflect the defined =
values of Y.1541 or Y.2171bis in the QSPEC, then I think a new field =
should be defined in that document to contain those values. =A0The =
authors of the other documents can decide if they too wish to add an ITU =
dependent field.</div> <div><br class=3D"webkit-block-placeholder"></div> =
<div>the other option is to disregard any relation between the Admission =
Priority field of the QSPEC and=A0<span class=3D"Apple-style-span" =
style=3D"FONT-FAMILY: Arial">tsvwg-emergency-rsvp, which would be a =
shame.</span></div> <div><font class=3D"Apple-style-span" =
face=3D"Arial"><br class=3D"webkit-block-placeholder"></font></div> =
<div><font class=3D"Apple-style-span" face=3D"Arial">-ken</font></div> =
<div><font class=3D"Apple-style-span" face=3D"Arial"><br =
class=3D"webkit-block-placeholder"></font></div> <div><br =
class=3D"webkit-block-placeholder"></div> <div><br></div> <div><br =
class=3D"webkit-block-placeholder"></div></blockquote></div><br></body></h=
tml>=

--Apple-Mail-7-228198120--

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

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

--===============0393623105==--


From nsis-bounces@ietf.org  Tue Feb 26 14:55:18 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D17C528C67A;
	Tue, 26 Feb 2008 14:55:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.097
X-Spam-Level: *
X-Spam-Status: No, score=1.097 tagged_above=-999 required=5 tests=[AWL=-0.685,
	BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1,
	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 A0+qcMn1TlxL; Tue, 26 Feb 2008 14:55:17 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B610428C611;
	Tue, 26 Feb 2008 14:55:17 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3AC8028C5FA
	for <nsis@core3.amsl.com>; Tue, 26 Feb 2008 14:55:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 5ahNqlgmaHB6 for <nsis@core3.amsl.com>;
	Tue, 26 Feb 2008 14:55:16 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 29AAD28C2EA
	for <nsis@ietf.org>; Tue, 26 Feb 2008 14:55:16 -0800 (PST)
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-1.cisco.com with ESMTP; 26 Feb 2008 14:55:09 -0800
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id m1QMt8HO014089; 
	Tue, 26 Feb 2008 14:55:08 -0800
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id m1QMt85q018819;
	Tue, 26 Feb 2008 22:55:08 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Feb 2008 14:54:57 -0800
Received: from [10.255.8.24] ([10.21.91.66]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 26 Feb 2008 14:54:57 -0800
In-Reply-To: <13369810-81EB-4ABA-940B-EEF45823167D@g11.org.uk>
References: <17811FF8-52E1-48AC-9966-3B96798C1A0A@g11.org.uk>
	<19EBBEC503C3B5469070E0A6674A533A010C40F3@daebe104.NOE.Nokia.com>
	<13369810-81EB-4ABA-940B-EEF45823167D@g11.org.uk>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <ECC43666-5B8B-4CBE-9622-6E5F5DD4A9F5@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Date: Tue, 26 Feb 2008 11:23:25 +0100
To: ken carlberg <carlberg@g11.org.uk>, Gerald Ash <gash5107@yahoo.com>,
	ATTLABS PERCY S TARAPORE <tarapore@att.com>,
	John Loughney <john.loughney@nokia.com>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 26 Feb 2008 22:54:57.0611 (UTC)
	FILETIME=[9C0131B0:01C878CA]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4286; t=1204066508;
	x=1204930508; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com>
	|Subject:=20Re=3A=20Admission=20field=20in=20QSPECRE=3A=20[
	NSIS]=20Review=20of=20draft-ietf-nsis-qspec-18.txt |Sender:=20;
	bh=d4zmh74PsVzWfsGV8wSxEZRPxBQ2LqFvbVVo/i6EV+U=;
	b=iBBzajl/OoLUPt/tYfaHVw7TuAKzagPteXAV2gpRBBWohjxh1ZSCXaTHGu
	N/qPHP7ijSx2sRkFMRVJPShi8EQqly0weSrVRz04T/qbYkWy6kGDCf828S8a
	rbcrwd8HxO;
Authentication-Results: sj-dkim-3; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
Cc: nsis <nsis@ietf.org>
Subject: Re: [NSIS] Admission field in QSPECRE: Review of
	draft-ietf-nsis-qspec-18.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: <http://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: <http://www.ietf.org/mailman/listinfo/nsis>,
	<mailto:nsis-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1249156338=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


--===============1249156338==
Content-Type: multipart/alternative; boundary=Apple-Mail-8-228422149


--Apple-Mail-8-228422149
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed


On 25 Feb 2008, at 21:27, ken carlberg wrote:

> John,
>
>> I think wee need to be able to support a few different scenarios  
>> and usages for the admission priority.  Is there a way that we  
>> could have a  common structure to hold the values, and the ability  
>> to set the values accordingly?
>
> we have one way, as described by Francois.
>
> however, if there is a segment that is absolutely adamant in having  
> a field reflect the defined values of Y.1541 or Y.2171bis in the  
> QSPEC, then I think a new field should be defined in that document  
> to contain those values.  The authors of the other documents can  
> decide if they too wish to add an ITU dependent field.
>
> the other option is to disregard any relation between the Admission  
> Priority field of the QSPEC and tsvwg-emergency-rsvp, which would  
> be a shame.

Perhaps another option could be for the Qspec document to state that  
the Admission Priority values MAY be set according to Y.2171 (but not  
mandate those are the only valid assignment and not request creation  
of a Qspec-specific IANA registry for those)?

Francois

>
> -ken
>
>
>
>


--Apple-Mail-8-228422149
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
<br><div><div>On 25 Feb 2008, at 21:27, ken carlberg wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">John,<br><div><div><br></div><blockquote type=3D"cite"><span=
 class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 255); font-family: Arial; font-size: 11px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; ">I think wee need to be able to =
support a few different scenarios and usages for=A0the admission =
priority.=A0 Is there a way that we could have a<span =
class=3D"Apple-converted-space">=A0</span> common structure to hold the =
values, and the ability to set the values =
accordingly?</span></blockquote></div><br><div>we have one way, as =
described by Francois. =A0</div><div><br =
class=3D"webkit-block-placeholder"></div><div>however, if there is a =
segment that is absolutely adamant in having a field reflect the defined =
values of Y.1541 or Y.2171bis in the QSPEC, then I think a new field =
should be defined in that document to contain those values. =A0The =
authors of the other documents can decide if they too wish to add an ITU =
dependent field.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>the other option is to =
disregard any relation between the Admission Priority field of the QSPEC =
and=A0<span class=3D"Apple-style-span" style=3D"font-family: Arial; =
">tsvwg-emergency-rsvp, which would be a =
shame.</span></div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>Perhaps another option =
could be for the Qspec document to state that the Admission Priority =
values MAY be set according to Y.2171 (but not mandate those are the =
only valid assignment and not request creation of a Qspec-specific IANA =
registry for those)?</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Francois</div><br><blockquot=
e type=3D"cite"><div><font class=3D"Apple-style-span" face=3D"Arial"><br =
class=3D"webkit-block-placeholder"></font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial">-ken</font></div><div><font =
class=3D"Apple-style-span" face=3D"Arial"><br =
class=3D"webkit-block-placeholder"></font></div><div><br =
class=3D"webkit-block-placeholder"></div><div><br></div><div><br =
class=3D"webkit-block-placeholder"></div></blockquote></div><br></body></h=
tml>=

--Apple-Mail-8-228422149--

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

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

--===============1249156338==--


From nsis-bounces@ietf.org  Wed Feb 27 01:38:54 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 54D6A28C70D;
	Wed, 27 Feb 2008 01:38:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.593
X-Spam-Level: 
X-Spam-Status: No, score=-0.593 tagged_above=-999 required=5
	tests=[AWL=-0.156, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, 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 2rtvZhYCd-VS; Wed, 27 Feb 2008 01:38:52 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E5B3328C478;
	Wed, 27 Feb 2008 01:38:52 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7AE8C28C547
	for <nsis@core3.amsl.com>; Wed, 27 Feb 2008 01:38:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 P8r2jULbux2D for <nsis@core3.amsl.com>;
	Wed, 27 Feb 2008 01:38:50 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id B419828C70D
	for <nsis@ietf.org>; Wed, 27 Feb 2008 01:38:23 -0800 (PST)
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 263422C002B4A
	for <nsis@ietf.org>; Wed, 27 Feb 2008 10:38:17 +0100 (CET)
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 H35yecaHHwno for <nsis@ietf.org>;
	Wed, 27 Feb 2008 10:38:17 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id 159672C000355
	for <nsis@ietf.org>; Wed, 27 Feb 2008 10:38:12 +0100 (CET)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 27 Feb 2008 10:38:11 +0100
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF53DEB5@mx1.office>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Draft agenda for IETF#71
Thread-Index: Ach5JHeSzr/qCAbzSymErdXRR8vnTg==
From: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>
To: "nsis" <nsis@ietf.org>
Subject: [NSIS] Draft agenda for IETF#71
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 all,

Attached the first draft agenda for the IETF#71 meeting.

IETF-71, Philadelphia, PA, USA

**Preliminary Agenda for NSIS WG**

WG Chair(s):
John Loughney <john.loughney@nokia.com>
Martin Stiemerling <stiemerling@nw.neclab.eu>

Send any agenda request to nsis-chairs@tools.ietf.org

* NOTE WELL  (1 minute)
* Agenda Bashing   (2 minutes)
* WG Status  (20 minutes)
  Milestones Review
  Document Status and Accomplishments

* Applicability Statement of NSIS Protocols in Mobile Environments -
  Takako Sanda (10 minutes)
https://datatracker.ietf.org/draft-ietf-nsis-applicability-mobility-signaling

* QSPEC - tbd (10 minutes) 
https://datatracker.ietf.org/drafts/draft-ietf-nsis-qspec

* GIST over SCTP - Xiaoming Fu (10 minutes)
https://datatracker.ietf.org/drafts/draft-ietf-nsis-ntlp-sctp

* NSIS Extensibility Model - tbd (5 minutes)
https://datatracker.ietf.org/drafts/draft-nsis-ext

* IANA Considerations for the IPv4 and IPv6 Router Alert Option -
  Jukka Manner (5 minutes)
https://datatracker.ietf.org/drafts/draft-manner-router-alert-iana

* Implementation reports: If any of the implementors can briefly report about their current implementations.
  * University of Coimbra Implementations status - Luis Cordeiro
  (5 minutes)

* if time permits: discussions of individual drafts.  

  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 
_______________________________________________
nsis mailing list
nsis@ietf.org
https://www.ietf.org/mailman/listinfo/nsis


From nsis-bounces@ietf.org  Wed Feb 27 08:28:55 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 705BE28C386;
	Wed, 27 Feb 2008 08:28:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.745
X-Spam-Level: 
X-Spam-Status: No, score=-0.745 tagged_above=-999 required=5
	tests=[AWL=-0.308, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, 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 sXOLv4TDGLTT; Wed, 27 Feb 2008 08:28:50 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 70E0E28C5DC;
	Wed, 27 Feb 2008 08:28:49 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D083C28C35A;
	Wed, 27 Feb 2008 08:28:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 6rKvLEd7Xgdp; Wed, 27 Feb 2008 08:28:43 -0800 (PST)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 52E8428C2BD;
	Wed, 27 Feb 2008 08:28:43 -0800 (PST)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	5C54F2087D; Wed, 27 Feb 2008 17:24:25 +0100 (CET)
X-AuditID: c1b4fb3c-b08c0bb000007e19-e7-47c58eb952e3
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	48F3320583; Wed, 27 Feb 2008 17:24:25 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Feb 2008 17:24:24 +0100
Received: from [127.0.0.1] ([147.214.30.103]) by esealmw129.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Feb 2008 17:24:24 +0100
Message-ID: <47C58EB8.1000203@ericsson.com>
Date: Wed, 27 Feb 2008 17:24:24 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: tsvwg <tsvwg@ietf.org>
X-OriginalArrivalTime: 27 Feb 2008 16:24:24.0722 (UTC)
	FILETIME=[3753D720:01C8795D]
X-Brightmail-Tracker: AAAAAA==
Cc: dime@ietf.org, NSIS <nsis@ietf.org>
Subject: [NSIS] WG last call on draft-ietf-tsvwg-emergency-rsvp-05
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

This announces the second WG last call on "Resource ReSerVation Protovol 
(RSVP) Extensions for Emergency Services" with the intended status of 
proposed standard:

http://tools.ietf.org/id/draft-ietf-tsvwg-emergency-rsvp-05.txt

This is the second one due to changes and the interaction with documents 
in the NSIS and DIME WG. Please provide any comments on the TSVWG 
mailing list no later than 28th of March. (Yes, it is long but that is 
due to the meeting and that we have several other WG last calls ongoing).

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | 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  Wed Feb 27 09:54:54 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1BD8528C2D0;
	Wed, 27 Feb 2008 09:54:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.414
X-Spam-Level: 
X-Spam-Status: No, score=-99.414 tagged_above=-999 required=5
	tests=[AWL=-0.205, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, MIME_HTML_MOSTLY=0.001,
	RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ivopcfdUfwZS; Wed, 27 Feb 2008 09:54:40 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6A3C13A6AA8;
	Wed, 27 Feb 2008 09:54:40 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 018213A6A54
	for <nsis@core3.amsl.com>; Wed, 27 Feb 2008 09:54:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 P14ycY7tQdIL for <nsis@core3.amsl.com>;
	Wed, 27 Feb 2008 09:54:25 -0800 (PST)
Received: from mail203.messagelabs.com (mail203.messagelabs.com
	[216.82.254.243])
	by core3.amsl.com (Postfix) with ESMTP id 2B1FD3A6A8B
	for <nsis@ietf.org>; Wed, 27 Feb 2008 09:54:25 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: tarapore@att.com
X-Msg-Ref: server-7.tower-203.messagelabs.com!1204134854!5622413!1
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [144.160.20.54]
Received: (qmail 18205 invoked from network); 27 Feb 2008 17:54:15 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpi135.enaf.sfdc.sbc.com)
	(144.160.20.54)
	by server-7.tower-203.messagelabs.com with AES256-SHA encrypted SMTP;
	27 Feb 2008 17:54:15 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m1RHsGoX002044; Wed, 27 Feb 2008 12:54:16 -0500
Received: from kcclust06evs1.ugd.att.com (kcst11.ugd.att.com [135.38.164.88])
	by mlpi135.enaf.sfdc.sbc.com (8.14.0/8.14.0) with ESMTP id
	m1RHsBMW001996; Wed, 27 Feb 2008 12:54:11 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 27 Feb 2008 11:54:11 -0600
Message-ID: <A1F50CB516D211409DFD05D6B3CE6D300CD2B744@KCCLUST06EVS1.ugd.att.com>
In-Reply-To: <379162.6526.qm@web63604.mail.re1.yahoo.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Review of draft-ietf-nsis-qspec-18.txt
Thread-Index: Ach4yHZ+fNunR1LYR4C4r317WiOPbgAoJrJw
References: <8235DDEA-6B91-4151-8E2F-E6EC01AD470D@g11.org.uk>
	<379162.6526.qm@web63604.mail.re1.yahoo.com>
From: "TARAPORE, PERCY S, ATTLABS" <tarapore@att.com>
To: "Gerald Ash" <gash5107@yahoo.com>, "ken carlberg" <carlberg@g11.org.uk>,
	"nsis ((E-mail))" <nsis@ietf.org>
Cc: john.loughney@nokia.com
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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>
Content-Type: multipart/mixed; boundary="===============1319092430=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1319092430==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C87969.C202C899"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C87969.C202C899
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Jerry correctly describes the situation re: Y.2171 versus Y.1571. Here
are some additional clarifications:
=20
1. The correct ITU-T Recommendation is Y.2171. Unfortunately, the ITU-T
initially assigned Y.1571 to this Recommendation; only later on they
changed it to Y.2171. So Y.1571 is not superseded by Y.2171; in fact
they are the same document.
=20
2. The total number of priority levels has not changed in the ongoing
Recommendation number change. There have always been 3 levels.
=20
3. The total number of priority levels were agreed to involving
extensive discussions with a number of major service providers. The
intent was to ensure that Priority Level 1 - the highest admission
control priority - was exclusively reserved for emergency
telecommunications. The discussions then focused on how many other
levels were needed. There was agreement that:
    - There is a broad class of traffic that can be considered "Best
Effort". This is priority level 3.
    - There is a broad class of traffic that was not as critical as
emergency telecommunications but required better than "Best Effort".
This is priority level 2.
Thus 3 broad levels were agreed upon. With one caveat for flexibility:
Individual provider domains are free to assign additional sub-levels of
priority within these broad priority levels. The choice is up to
individual provider domains.
=20
4. The above agreements were reached as I stated with several large
service providers participating: AT&T, Verizon, British Telecom, France
Telecom, Deutsche Telekom, NTT, KoreaTel, ZTE, China Tel.
=20
Here is the relevant Clause (Clause 6) from Y.2171:
=20
--------------------
 =20

Recommendation for admission control priority levels


Three admission control priority levels are recommended for
telecommunications services seeking entry into NGN:

*        Priority level 1: Traffic with this priority level receives the
highest assurance for admission to the network. This level is reserved
for emergency telecommunications over NGN.=20

*        Priority level 2: Traffic with this priority level will not
receive the same assurance for admission as that given to priority level
1 traffic, but will receive higher assurance for admission than that
given to priority level 3 traffic. Examples include real-time services
(VoIP, video), VPN and data services. The selection of this priority
level is expected to be determined by appropriate service level
agreements (SLA) between network operators and customers for the desired
service.

*        Priority level 3: Traffic with this priority level receives the
least assurance for admission to the network. Examples include
"traditional" Internet service provider (ISP) services (e-mail, web
surfing). The selection of this priority level is expected to be
determined by appropriate SLA agreements between network operators and
customers for the desired service.=20

Each network operator may adopt additional priority levels. The total
number of admission control priority levels may be extended in the
future.

The choice of priority implementation mechanisms in the transport
stratum is up to the network operator.
=20
--------------------
=20
Thanks,
=20
Percy

________________________________

From: Gerald Ash [mailto:gash5107@yahoo.com]=20
Sent: Tuesday, February 26, 2008 5:39 PM
To: ken carlberg; nsis ((E-mail))
Cc: Jerry Ash; TARAPORE, PERCY S, ATTLABS; Francois Le Faucheur IMAP;
john.loughney@nokia.com
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.txt


Ken,
=20
> Jerry,
=20
>> This is confusing to me because admission priority has nothing to do
with=20
>> Y.1541.  Y.1541 is associated with the <Y.1541.QoS Class> field (see
Section=20
>> 5.2.14 of the updated -19 QSPEC document or Section 6.2.14 of the=20
>> current -18 QSPEC document).
=20
> mea culpa!!!  in my ramblings, I meant Y.1571, so just swap all
reference of=20
> Y.1541 with Y.1571 from my previous postings
=20
There is no Y.1571, only Y.2171 (it was renumbered).
=20
>> QSPEC admission priority is simply using the 3 priority levels
already=20
>> standardized by Y.2171.  Admission priority is a generic concept, not

>> invented by the ITU, so this is not 'ITU admission priority', just
plain=20
>> ole' admission priority.
=20
> I beg to differ.  We are in agreement that admission priority is a
generic=20
> concept, but in Section 6.2.9 of the QSPEC you have bound an Admission

> Priority field with pre-existing values defined in Y.1571  as written
in the=20
> following:
>=20
> High priority flows, normal priority flows, and best-effort priority
> flows can have access to resources depending on their admission
> priority value, as described in [Y.1571], as follows:
>=20
> Admission Priority:
> 0 - best-effort priority flow
> 1 - normal priority flow
> 2 - high priority flow
>=20
> And now we're told these values are to be updated by Y.2171.  By the
way,=20
> could you tell us what these new values are?  Some of the members of
the=20
> NSIS list are not members of the ITU, and so don't have that
information on=20
> hand.
=20
The values are unchanged.  There is no Y.1571, it was renumbered Y.2171,
the reference has been corrected in QSPEC -19. =20
=20
You don't have to be a member of ITU to get a recommendation, they are
all freely available on the www.itu.int web-site.  Y.2171 can be
downloaded at http://www.itu.int/rec/T-REC-Y.2171/en. =20
=20
BTW, essentially all service providers and equipment vendors belong to
and participate in the ITU.  All these service providers and equipment
vendors have unanimously agreed to Y.2171.

>> What's missing here is an explanation of what the approach is in=20
>> [EMERGENCY-RSVP].  As I posted earlier in=20
>> http://www.ietf.org/mail-archive/web/nsis/current/msg08231.html
<mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000015/!x-usc:http:
//www.ietf.org/mail-archive/web/nsis/current/msg08231.html> :
=20


------_=_NextPart_001_01C87969.C202C899
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3268" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D871144917-27022008>Jerry correctly describes the situation re: =
Y.2171=20
versus Y.1571. Here are some additional =
clarifications:</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D871144917-27022008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D871144917-27022008>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D669010221-26022008>1. The =
correct ITU-T=20
Recommendation is Y.2171. Unfortunately, the ITU-T initially assigned =
Y.1571 to=20
this Recommendation; only later on they changed it to Y.2171. So Y.1571 =
is not=20
superseded by Y.2171; in fact they are the same document.</SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D669010221-26022008></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D669010221-26022008>2. The =
total number of=20
priority levels has not changed in the ongoing Recommendation number =
change.=20
There have always been 3 levels.</SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D669010221-26022008></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D669010221-26022008>3. The =
total number of=20
priority levels were agreed to involving extensive discussions with a =
number of=20
major service providers. The intent was to ensure that Priority Level 1 =
- the=20
highest admission control priority - was exclusively reserved for =
emergency=20
telecommunications. The discussions then focused on how many other =
levels were=20
needed. There was agreement that:</SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D669010221-26022008>&nbsp;&nbsp;&nbsp; -=20
There is&nbsp;<SPAN class=3D871144917-27022008>a </SPAN>broad class of =
traffic=20
that can be considered "Best Effort". This<SPAN =
class=3D871144917-27022008>=20
is</SPAN>&nbsp;priority level 3.</SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D669010221-26022008>&nbsp;&nbsp;&nbsp; -=20
There is a broad class of traffic that was not as critical as emergency=20
telecommunications but required better than "Best Effort". This is =
priority=20
level 2.</SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D669010221-26022008>Thus 3 =
broad levels were=20
agreed upon. With one caveat for flexibility: Individual provider =
domains are=20
free to assign additional sub-levels of priority within these broad =
priority=20
levels. The choice is up to individual provider domains.</SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D669010221-26022008></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D669010221-26022008>4. The =
above agreements=20
were reached as I stated with several large service providers =
participating:=20
AT&amp;T, Verizon, British Telecom, France Telecom, Deuts<SPAN=20
class=3D871144917-27022008>c</SPAN>h<SPAN =
class=3D871144917-27022008>e</SPAN>=20
Telekom, NTT, KoreaTel, ZTE, China Tel.</SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D669010221-26022008></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D669010221-26022008>Here is the =
relevant=20
Clause (Clause 6) from Y.2171:</SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D669010221-26022008></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN=20
class=3D669010221-26022008>--------------------</SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D669010221-26022008><FONT face=3D"Times New Roman"><SPAN=20
style=3D"FONT-SIZE: 14pt; mso-bidi-font-weight: bold"><SPAN=20
style=3D"mso-list: Ignore"><FONT color=3D#000000><SPAN=20
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;=20
<H1 style=3D"MARGIN: 12pt 0in 0pt; TEXT-INDENT: 0in"><SPAN=20
style=3D"FONT-SIZE: 14pt">Recommendation for admission control priority=20
levels</SPAN><SPAN=20
style=3D"FONT-SIZE: 14pt; mso-bidi-font-weight: bold"><?xml:namespace =
prefix =3D o=20
ns =3D "urn:schemas-microsoft-com:office:office" =
/><o:p></o:p></SPAN></H1>
<P class=3DMsoBodyText=20
style=3D"MARGIN: 6pt 0in 0pt; TEXT-ALIGN: left; tab-stops: 207.0pt =
6.25in"=20
align=3Dleft><SPAN=20
style=3D"mso-bidi-font-weight: bold; mso-bidi-font-size: 12.0pt"><FONT=20
size=3D3>Three admission control priority levels are recommended for=20
telecommunications services seeking entry into =
NGN:<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoBodyText=20
style=3D"MARGIN: 3pt 0in 0pt 35.7pt; TEXT-INDENT: -17.85pt; TEXT-ALIGN: =
left; mso-list: l0 level1 lfo2; tab-stops: list .5in left 207.0pt =
6.25in"=20
align=3Dleft><SPAN=20
style=3D"FONT-FAMILY: Symbol; mso-bidi-font-weight: bold; =
mso-bidi-font-size: 12.0pt; mso-fareast-font-family: Symbol; =
mso-bidi-font-family: Symbol"><SPAN=20
style=3D"mso-list: Ignore"><FONT size=3D3>&middot;</FONT><SPAN=20
style=3D"FONT: 7pt 'Times New =
Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN></SPAN><SPAN=20
style=3D"mso-bidi-font-weight: bold; mso-bidi-font-size: 12.0pt"><FONT=20
size=3D3>Priority level 1: Traffic with this priority level receives the =
highest=20
assurance for admission to the network. This level is reserved for =
emergency=20
telecommunications over NGN. <o:p></o:p></FONT></SPAN></P>
<P class=3DMsoBodyText=20
style=3D"MARGIN: 3pt 0in 0pt 35.7pt; TEXT-INDENT: -17.85pt; TEXT-ALIGN: =
left; mso-list: l0 level1 lfo2; tab-stops: list .5in left 207.0pt =
6.25in"=20
align=3Dleft><SPAN=20
style=3D"FONT-FAMILY: Symbol; mso-bidi-font-weight: bold; =
mso-bidi-font-size: 12.0pt; mso-fareast-font-family: Symbol; =
mso-bidi-font-family: Symbol"><SPAN=20
style=3D"mso-list: Ignore"><FONT size=3D3>&middot;</FONT><SPAN=20
style=3D"FONT: 7pt 'Times New =
Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN></SPAN><SPAN=20
style=3D"mso-bidi-font-weight: bold; mso-bidi-font-size: 12.0pt"><FONT=20
size=3D3>Priority level 2: Traffic with this priority level will not =
receive the=20
same assurance for admission as that given to priority level 1 traffic, =
but will=20
receive higher assurance for admission than that given to priority level =
3=20
traffic. Examples include real-time services (VoIP, video), VPN and data =

services. The selection of this priority level is expected to be =
determined by=20
appropriate service level agreements (<?xml:namespace prefix =3D st1 ns =
=3D=20
"urn:schemas-microsoft-com:office:smarttags" /><st1:place=20
w:st=3D"on">SLA</st1:place>) between network operators and customers for =
the=20
desired service.<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoBodyText=20
style=3D"MARGIN: 3pt 0in 0pt 35.7pt; TEXT-INDENT: -17.85pt; TEXT-ALIGN: =
left; mso-list: l0 level1 lfo2; tab-stops: list .5in left 207.0pt =
6.25in"=20
align=3Dleft><SPAN=20
style=3D"FONT-FAMILY: Symbol; mso-bidi-font-weight: bold; =
mso-bidi-font-size: 12.0pt; mso-fareast-font-family: Symbol; =
mso-bidi-font-family: Symbol"><SPAN=20
style=3D"mso-list: Ignore"><FONT size=3D3>&middot;</FONT><SPAN=20
style=3D"FONT: 7pt 'Times New =
Roman'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN></SPAN><SPAN=20
style=3D"mso-bidi-font-weight: bold; mso-bidi-font-size: 12.0pt"><FONT=20
size=3D3>Priority level 3: Traffic with this priority level receives the =
least=20
assurance for admission to the network. Examples include =
&#8220;traditional&#8221; Internet=20
service provider (ISP) services (e-mail, web surfing). The selection of =
this=20
priority level is expected to be determined by appropriate <st1:place=20
w:st=3D"on">SLA</st1:place> agreements between network operators and =
customers for=20
the desired service. <o:p></o:p></FONT></SPAN></P>
<P class=3DMsoBodyText=20
style=3D"MARGIN: 6pt 0in 0pt; TEXT-ALIGN: left; tab-stops: 207.0pt =
6.25in"=20
align=3Dleft><SPAN=20
style=3D"mso-bidi-font-weight: bold; mso-bidi-font-size: 12.0pt"><FONT =
size=3D3>Each=20
network operator may adopt additional priority levels. The total number =
of=20
admission control priority levels may be extended in the=20
future.<o:p></o:p></FONT></SPAN></P><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-bidi-font-weight: bold; mso-fareast-font-family: 'Times New Roman'; =
mso-fareast-language: EN-US; mso-ansi-language: EN-US; =
mso-bidi-language: AR-SA">The=20
choice of priority implementation mechanisms in the transport stratum is =
up to=20
the network=20
operator.</SPAN></SPAN></FONT></SPAN></SPAN></FONT></SPAN></FONT><SPAN=20
class=3D669010221-26022008></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D669010221-26022008></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN=20
class=3D669010221-26022008>--------------------</SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D669010221-26022008></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D669010221-26022008><SPAN=20
class=3D871144917-27022008>Thanks,</SPAN></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D669010221-26022008><SPAN=20
class=3D871144917-27022008></SPAN></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D669010221-26022008><SPAN=20
class=3D871144917-27022008>Percy</SPAN></SPAN></DIV></SPAN></FONT></DIV><=
BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Gerald Ash =
[mailto:gash5107@yahoo.com]=20
<BR><B>Sent:</B> Tuesday, February 26, 2008 5:39 PM<BR><B>To:</B> ken =
carlberg;=20
nsis ((E-mail))<BR><B>Cc:</B> Jerry Ash; TARAPORE, PERCY S, ATTLABS; =
Francois Le=20
Faucheur IMAP; john.loughney@nokia.com<BR><B>Subject:</B> Re: [NSIS] =
Review of=20
draft-ietf-nsis-qspec-18.txt<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Ken,</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt; Jerry,<BR>&nbsp;<BR>&gt;&gt; This is confusing to me because =
admission=20
priority has nothing to do with <BR>&gt;&gt; Y.1541.&nbsp; Y.1541 is =
associated=20
with the &lt;Y.1541.QoS Class&gt; field (see Section <BR>&gt;&gt; 5.2.14 =
of the=20
updated -19 QSPEC document or Section 6.2.14 of the <BR>&gt;&gt; current =
-18=20
QSPEC document).<BR>&nbsp;<BR>&gt; mea culpa!!!&nbsp; in my ramblings, I =
meant=20
Y.1571, so just swap all reference of <BR>&gt; Y.1541 with Y.1571 from =
my=20
previous postings</DIV>
<DIV>&nbsp;</DIV>
<DIV>There is no Y.1571, only Y.2171 (it was =
renumbered).<BR>&nbsp;<BR>&gt;&gt;=20
QSPEC admission priority is simply using the 3 priority levels already=20
<BR>&gt;&gt; standardized by Y.2171.&nbsp; Admission priority is a =
generic=20
concept, not <BR>&gt;&gt; invented by the ITU, so this is not 'ITU =
admission=20
priority', just plain <BR>&gt;&gt; ole' admission =
priority.<BR>&nbsp;<BR>&gt; I=20
beg to differ.&nbsp; We are in agreement that admission priority is a =
generic=20
<BR>&gt; concept, but in Section 6.2.9 of the QSPEC you have bound an =
Admission=20
<BR>&gt; Priority field with pre-existing values defined in Y.1571&nbsp; =
as=20
written in the <BR>&gt; following:<BR>&gt;&nbsp;<BR>&gt; High priority =
flows,=20
normal priority flows, and best-effort priority<BR>&gt; flows can have =
access to=20
resources depending on their admission<BR>&gt; priority value, as =
described in=20
[Y.1571], as follows:<BR>&gt; <BR>&gt; Admission Priority:<BR>&gt; 0 -=20
best-effort priority flow<BR>&gt; 1 - normal priority flow<BR>&gt; 2 - =
high=20
priority flow<BR>&gt; <BR>&gt; And now we're told these values are to be =
updated=20
by Y.2171.&nbsp; By the way, <BR>&gt; could you tell us what these new =
values=20
are?&nbsp; Some of the members of the <BR>&gt; NSIS list are not members =
of the=20
ITU, and so don't have that information on <BR>&gt; hand.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The values are unchanged.&nbsp; There is no Y.1571, it was =
renumbered=20
Y.2171, the reference has been corrected in QSPEC -19.&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>You don't have to be a member of ITU to get a recommendation, they =
are all=20
freely available on the <A href=3D"http://www.itu.int">www.itu.int</A>=20
web-site.&nbsp; Y.2171 can be downloaded&nbsp;at <A=20
href=3D"http://www.itu.int/rec/T-REC-Y.2171/en">http://www.itu.int/rec/T-=
REC-Y.2171/en</A>.&nbsp;=20
</DIV>
<DIV>&nbsp;</DIV>
<DIV>BTW,&nbsp;essentially all service providers and equipment vendors =
belong to=20
and participate in the ITU.&nbsp; All these service providers and =
equipment=20
vendors have unanimously agreed to Y.2171.</DIV>
<DIV><BR>&gt;&gt; What's missing here is an explanation of what the =
approach is=20
in <BR>&gt;&gt; [EMERGENCY-RSVP].&nbsp; As I posted earlier in =
<BR>&gt;&gt; <A=20
href=3D"mhtml:{B096A9AC-8D5F-4D5A-AACE-EC56A1B5E65A}mid://00000015/!x-usc=
:http://www.ietf.org/mail-archive/web/nsis/current/msg08231.html">http://=
www.ietf.org/mail-archive/web/nsis/current/msg08231.html</A>:<BR>&nbsp;<B=
R></DIV></BODY></HTML>

------_=_NextPart_001_01C87969.C202C899--

--===============1319092430==
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

--===============1319092430==--


From nsis-bounces@ietf.org  Wed Feb 27 09:56:28 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3935128C34F;
	Wed, 27 Feb 2008 09:56:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.026
X-Spam-Level: *
X-Spam-Status: No, score=1.026 tagged_above=-999 required=5 tests=[AWL=0.236,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_MESSAGE=1, RDNS_NONE=0.1, 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 2gVvK-VhlmOC; Wed, 27 Feb 2008 09:56:26 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A829428C19E;
	Wed, 27 Feb 2008 09:56:26 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 15CAE28C19E
	for <nsis@core3.amsl.com>; Wed, 27 Feb 2008 09:56:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 nGk2TlcG2KbT for <nsis@core3.amsl.com>;
	Wed, 27 Feb 2008 09:56:23 -0800 (PST)
Received: from web63601.mail.re1.yahoo.com (web63601.mail.re1.yahoo.com
	[69.147.97.71]) by core3.amsl.com (Postfix) with SMTP id 429A63A6A15
	for <nsis@ietf.org>; Wed, 27 Feb 2008 09:56:23 -0800 (PST)
Received: (qmail 94328 invoked by uid 60001); 27 Feb 2008 17:56:16 -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=CMBl32yuVCEEj+7a1XaeFFo+OXW1mCDFMBBZI6hg1O221D7kGOy4kWgKBDvOvX92XFzu8u+4xqBfRErbTr6eHWSw72Fjkq9GJe0ufkglRqMsV0oE6//nIZ6YS1voeSLvUIvSxitqTaSrP8QWP5AlAS+EoOQULbj+dVLiAOWTHYI=;
X-YMail-OSG: mKoLfi0VM1nWQHp_33iDRNoIY.ouKTyDeR0hflr2QiDKirL.lxvegdpH1v8zTm7sJQgBwKF2DnIcV2NJNw1GaH7X3Q--
Received: from [76.19.255.157] by web63601.mail.re1.yahoo.com via HTTP;
	Wed, 27 Feb 2008 09:56:16 PST
Date: Wed, 27 Feb 2008 09:56:16 -0800 (PST)
From: Gerald Ash <gash5107@yahoo.com>
To: nsis <nsis@ietf.org>
In-Reply-To: <ECC43666-5B8B-4CBE-9622-6E5F5DD4A9F5@cisco.com>
MIME-Version: 1.0
Message-ID: <350019.92229.qm@web63601.mail.re1.yahoo.com>
Cc: John Loughney <john.loughney@nokia.com>
Subject: Re: [NSIS] Admission field in QSPEC -- was RE: Review of
	draft-ietf-nsis-qspec-18.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>
Content-Type: multipart/mixed; boundary="===============1712171733=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

--===============1712171733==
Content-Type: multipart/alternative; boundary="0-1979085357-1204134976=:92229"
Content-Transfer-Encoding: 8bit

--0-1979085357-1204134976=:92229
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

All,
   
  John writes in http://www.ietf.org/mail-archive/web/nsis/current/msg08243.html:
   
  John> Just some background history.  There are 3 documents defining similar
  John> fields
  John>
  John> tsvwg-emergency-rsvp 
  John> nsis-qspec 
  John> dime-qos-parameters
  John>
  John> We discussed this on this list and at previous IETF meetings.
  John> My view of consensus was that...
   
  I've seen no discussion on the list either before or after the 'Proposed Resolution' was posted on 3 December at http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html.  This is just presented and not explained.  AFAICT no co-authors of the QSPEC document participated actively in the off-line discussion or explicitly agreed to the proposed resolution.  So I don't see that there was any 'consensus'.
   
  John> ... there should be some harmony and
  John> a common registry between these documents. 
   
  The proposed resolution says:
   
  "o Regarding Admission Priority:
* every protocol spec will only indicate that "higher value means higher priority".
* there is no attempt to define what specific values should be used for what. this is left outside the scope of the protocol specs.
* each protocol spec will add a statement clarifying that a given Admission Priority is to be encoded with the same value in each of the three protocol spec. For example, in tsvwg-emergency-rsvp, under section 3.1. we will add:
" A given Admission Priority is encoded in this information element
using the same value as when encoded in the Admission Priority
parameter defined in section 6.2.9 of [nsis-qspec], or in the Admission
Priority parameter defined in section 4.10 of [dime-qos-parameters].
In other words, a given value in any of the [emergency-rsvp] Admission
Priority information element, the [nsis-qspec] Admission Priority parameter
or the [dime-qos-parameters] Admission Priority parameter, refers to
the same Admission Priority.
"
* the mirror statement will be added in nsis-qspec (section 6.2.9) and dime-qos-parameters (section 4.10)"
   
  The above proposed resolution is very unclear and does not begin to explain that (apparently) what is proposed is to drop the QSPEC approach to admission priority and replace it with the emergency-rsvp approach.  
   
  Admission priority is a well defined concept supporting priority in flow admission control.  There are 3 priority levels defined in QSPEC, following the agreement standardized in Y.2171 http://www.itu.int/rec/T-REC-Y.2171/en.  The intent is that 'high admission priority' is reserved for emergency telecommunications.  'Normal admission priority' is reserved for traffic that is not as critical as emergency telecommunications but requires better than 'best effort admission priority'.  Examples include real-time services (VoIP, video), VPN and data services. 'Best effort admission' priority is reserved for a broad class of traffic that can be considered the lowest priority best effort flows.  Examples include “traditional” ISP services (e-mail, web surfing). 
   
  According to Francois (see http://www.ietf.org/mail-archive/web/nsis/current/msg08251.html), the emergency-rsvp approach is something aligned with preemption priority where no standard admission priority values are standardized in a registry.  However preemption priority works in a completely different way than admission priority; there are 2 values; 'defending priority' and 'preemption priority'.  These can be assigned somewhat arbitrarily since only the *relative* values have significance.  That is, the absolute values don't matter, it is only the relative value that matters.  In this way preemption can work across domains without standarding absolute values of defending priority and preemption priority.  It is unclear how such an approach can work for admission priority since the decision to admit or not admit a flow is done at the time of flow admission control and there is no prior 'defending priority' assigned to a flow when it first arrives for admission control. 
 So it unclear how the emergency-rsvp approach is aligned with the preemption priority approach.
   
  According to Ken (see http://www.ietf.org/mail-archive/web/nsis/current/msg08248.html), the emergency-rsvp approach involves using policy elements, PDPs doing 'mappings', preemption, and namespaces.  AFAIK preemption priority doesn't have namespaces, and what Ken describes looks different from what Francois describes.  
   
  In any case it appears that emergency-rsvp is doing something quite different from what QSPEC is doing.
   
  John> I think wee need to be able to support a few different scenarios and usages 
John> for the admission priority.
   
  I'm not sure what 'different scenarios' we're trying to support here?  As discussed above, admission priority is a well defined concept supporting priority in flow admission control.  I've seen no mention of any other 'different scenarios' for admission priority on the list.  Can you elaborate?
   
  John> Is there a way that we could have a  common structure to hold
  John> the values, and the ability to set the values accordingly?
 
Obviously one option is for emergency-rsvp to adopt the approach being taken all along in QSPEC.  We are not being told why this is not considered. 
  
Francois> Perhaps another option could be for the Qspec document to state
  Francois> that the Admission Priority values MAY be set according to Y.2171
  Francois> (but not mandate those are the only valid assignment and not
  Francois> request creation of a Qspec-specific IANA registry for those)?
   
  This is essentially the same as the 'proposed agreement', i.e. to drop the QSPEC approach to admission priority and do away with standardized admission priority values.  If we eliminate this standardization, then different admission priority values can be assigned in different Admin domains, and will have no end-to-end significance.  As such, each Admin domain has no idea how to treat the flow admission priority during flow admission since different domains are using different encodings of admission priority.
     

  IMO we should retain the standardized admission priority levels as included in QSPEC for a long time.  If emergency-rsvp cannot adopt the same approach, then for now retain 2 approaches.
   
  Jerry

       
---------------------------------
Never miss a thing.   Make Yahoo your homepage.
--0-1979085357-1204134976=:92229
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>All,</DIV>  <DIV>&nbsp;</DIV>  <DIV>John writes in <A href="http://www.ietf.org/mail-archive/web/nsis/current/msg08243.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08243.html</A>:</DIV>  <DIV>&nbsp;</DIV>  <DIV><SPAN class=044595419-25022008><FONT face=Arial>John&gt; Just some background history.&nbsp; There are 3 documents defining similar</FONT></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><FONT face=Arial>John&gt;&nbsp;fields</FONT></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><FONT face=Arial><SPAN class=044595419-25022008><FONT face=Arial>John&gt;</FONT></SPAN></FONT></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><FONT face=Arial><SPAN class=044595419-25022008><FONT face=Arial>John&gt;</FONT></SPAN>&nbsp;tsvwg-emergency-rsvp </FONT></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><FONT face=Arial><SPAN class=044595419-25022008><FONT face=Arial>John&gt;</FONT></SPAN>&nbsp;nsis-qspec </FONT></SPAN></DIV>  <DIV><SPAN
 class=044595419-25022008><FONT face=Arial><SPAN class=044595419-25022008><FONT face=Arial>John&gt;</FONT></SPAN>&nbsp;dime-qos-parameters</FONT></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><SPAN class=044595419-25022008><FONT face=Arial>John&gt;</FONT></SPAN></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><FONT face=Arial color=#0000ff><FONT color=#000000><SPAN class=044595419-25022008><FONT face=Arial>John&gt; </FONT></SPAN>We discussed this on this list and at previous IETF meetings.</FONT></FONT></SPAN></DIV>  <DIV><SPAN class=044595419-25022008>John&gt; My view<SPAN class=044595419-25022008><FONT face=Arial color=#0000ff><FONT color=#000000>&nbsp;of consensus was that...</FONT></FONT></SPAN></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><SPAN class=044595419-25022008></SPAN></SPAN>&nbsp;</DIV>  <DIV><FONT face=arial>I've seen no discussion on the list either before or after the 'Proposed Resolution' was posted on 3 December at&nbsp;</FONT><A
 href="http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html" rel=nofollow><FONT face=arial>http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html</FONT></A>.&nbsp; This is just presented and not explained.&nbsp; AFAICT no co-authors of the QSPEC document participated actively in the off-line discussion or explicitly&nbsp;agreed to the proposed resolution.&nbsp; So I don't see that&nbsp;there was any 'consensus'.</DIV>  <DIV>&nbsp;</DIV>  <DIV>John&gt;&nbsp;... <SPAN class=044595419-25022008><FONT face=Arial color=#0000ff><FONT color=#000000>there should be some harmony and</FONT></FONT></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><FONT face=Arial color=#0000ff><FONT color=#000000>John&gt;&nbsp;a common </FONT></FONT></SPAN><SPAN class=044595419-25022008><FONT face=Arial color=#0000ff><FONT color=#000000>registry between these documents</FONT>.&nbsp;</FONT></SPAN></DIV>  <DIV>&nbsp;</DIV>  <DIV>The proposed resolution&nbsp;says:</DIV> 
 <DIV>&nbsp;</DIV>  <DIV><FONT face=arial>"o Regarding Admission Priority:<BR>* every protocol spec will only indicate that "higher value means higher priority".<BR>* there is no attempt to define what specific values should be used for what. this is left outside the scope of the protocol specs.<BR>* each protocol spec will add a statement clarifying that a given Admission Priority is to be encoded with the same value in each of the three protocol spec. For example, in tsvwg-emergency-rsvp, under section 3.1. we will add:<BR>" A given Admission Priority is encoded in this information element<BR>using the same value as when encoded in the Admission Priority<BR>parameter defined in section 6.2.9 of [nsis-qspec], or in the Admission<BR>Priority parameter defined in section 4.10 of [dime-qos-parameters].<BR>In other words, a given value in any of the [emergency-rsvp] Admission<BR>Priority information element, the [nsis-qspec] Admission Priority parameter<BR>or the
 [dime-qos-parameters] Admission Priority parameter, refers to<BR>the same Admission Priority.<BR>"<BR>* the mirror statement will be added in nsis-qspec (section 6.2.9) and dime-qos-parameters (section 4.10)"</FONT></DIV>  <DIV><FONT face=arial></FONT>&nbsp;</DIV>  <DIV><FONT face=arial><FONT face=arial>The above proposed resolution&nbsp;is&nbsp;very unclear and does not begin to explain that (apparently) what is proposed is to drop the QSPEC approach to admission priority and replace it with&nbsp;the emergency-rsvp approach.&nbsp; </FONT></FONT></DIV>  <DIV><FONT face=arial><FONT face=arial></FONT></FONT>&nbsp;</DIV>  <DIV>Admission priority is a&nbsp;well defined concept supporting priority in flow admission control.&nbsp; There are 3 priority levels defined in QSPEC, following the agreement standardized in Y.2171 <A href="http://www.itu.int/rec/T-REC-Y.2171/en">http://www.itu.int/rec/T-REC-Y.2171/en</A>.&nbsp; The intent&nbsp;is&nbsp;that 'high admission
 priority'&nbsp;is reserved for emergency telecommunications.&nbsp;&nbsp;'Normal admission priority' is reserved for&nbsp;traffic <FONT face=arial>that&nbsp;is not as critical as emergency telecommunications but requires better than 'best effort admission priority'.&nbsp; <FONT face=arial>Examples include real-time services (VoIP, video), VPN and data services. </FONT>'Best effort admission' priority is&nbsp;reserved for a</FONT><FONT face=Arial size=2><SPAN class=669010221-26022008><FONT face=arial>&nbsp;broad class of traffic that can</FONT> be considered the lowest priority best effort flows.&nbsp; <FONT size=3><FONT size=2>Examples include “traditional” ISP services (e-mail, web surfing). </FONT></FONT></SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN class=669010221-26022008></SPAN></FONT>&nbsp;</DIV>  <DIV><FONT face=Arial size=2><SPAN class=669010221-26022008></SPAN></FONT><FONT face=arial><FONT face=arial>According to Francois (see <A
 href="http://www.ietf.org/mail-archive/web/nsis/current/msg08251.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08251.html</A>), the emergency-rsvp approach&nbsp;is something aligned with preemption priority where no standard admission priority values are standardized in a registry.&nbsp; </FONT></FONT><FONT face=arial><FONT face=arial>However preemption priority works in a completely different way than admission priority; there are 2 values; 'defending&nbsp;priority' and 'preemption priority'.&nbsp; These can be assigned somewhat arbitrarily since only the *relative* values have significance.&nbsp; That is, the absolute values don't matter, it is only the relative value that matters.&nbsp; In this way preemption can work across domains without standarding absolute values of defending priority and preemption priority.&nbsp; It is unclear how such an approach can work for admission priority since the decision to admit or not admit a flow is done&nbsp;at the time
 of flow&nbsp;admission control and there is no prior 'defending priority' assigned to a flow when it first arrives for admission control.&nbsp; So it unclear how the emergency-rsvp approach is aligned with the preemption priority approach.</DIV></FONT></FONT>  <DIV><FONT face=arial><FONT face=arial></FONT></FONT>&nbsp;</DIV>  <DIV><FONT face=arial><FONT face=arial>According to Ken (see <A href="http://www.ietf.org/mail-archive/web/nsis/current/msg08248.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08248.html</A>), the emergency-rsvp approach involves using&nbsp;policy elements, PDPs doing 'mappings', preemption, and namespaces.&nbsp; AFAIK preemption priority doesn't have namespaces, and what Ken describes looks different from what Francois describes.&nbsp; </FONT></FONT></DIV>  <DIV><FONT face=arial><FONT face=arial></FONT></FONT>&nbsp;</DIV>  <DIV><FONT face=arial><FONT face=arial>In any case it appears that&nbsp;emergency-rsvp is doing something quite
 different from what QSPEC is doing.</DIV></FONT></FONT>  <DIV>&nbsp;</DIV>  <DIV>John&gt; I think wee need to be able to support a few different scenarios and usages <BR>John&gt; for the admission priority.</DIV>  <DIV>&nbsp;</DIV>  <DIV>I'm not sure what 'different scenarios' we're trying to support here?&nbsp; As discussed above, admission priority is a&nbsp;well defined concept supporting priority in flow admission control.&nbsp; I've seen no mention of any other 'different scenarios'&nbsp;for admission priority on the list.&nbsp; Can you elaborate?</DIV>  <DIV>&nbsp;</DIV>  <DIV>John&gt; Is there a way that we could have a&nbsp; common&nbsp;structure to hold</DIV>  <DIV>John&gt;&nbsp;the values, and the ability to set the values accordingly?<BR>&nbsp;<BR>Obviously&nbsp;one option is for emergency-rsvp to adopt the approach&nbsp;being taken all along&nbsp;in QSPEC.&nbsp; We are not being told why this is not considered.&nbsp;</DIV>  <DIV><BR>Francois&gt; Perhaps another
 option could be for the Qspec document to state</DIV>  <DIV>Francois&gt;&nbsp;that the&nbsp;Admission Priority values MAY be set according to Y.2171</DIV>  <DIV>Francois&gt;&nbsp;(but not mandate&nbsp;those are the only valid assignment and not</DIV>  <DIV>Francois&gt;&nbsp;request creation of a&nbsp;Qspec-specific IANA registry for those)?</DIV>  <DIV>&nbsp;</DIV>  <DIV>This is essentially the same as&nbsp;the 'proposed agreement', i.e.&nbsp;to drop the QSPEC approach to admission priority&nbsp;and do away with standardized admission priority values.&nbsp; If we eliminate this standardization,&nbsp;then different admission priority values&nbsp;can be&nbsp;assigned in different Admin domains, and will&nbsp;have no end-to-end significance.&nbsp; As such, each Admin domain has no idea how to treat the flow admission priority during flow admission since&nbsp;different domains are using different encodings of&nbsp;admission priority.</DIV>  <DIV>  <DIV>&nbsp;</DIV></DIV> 
 <DIV>IMO we should retain the standardized admission priority levels&nbsp;as&nbsp;included in QSPEC for a long time.&nbsp; If emergency-rsvp cannot adopt the same approach, then for now retain 2 approaches.</DIV>  <DIV>&nbsp;</DIV>  <DIV>Jerry</DIV><p>&#32;

      <hr size=1>Never miss a thing.  <a href="http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs"> Make Yahoo your homepage.</a>


--0-1979085357-1204134976=:92229--

--===============1712171733==
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

--===============1712171733==--


From nsis-bounces@ietf.org  Wed Feb 27 11:13:52 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4EFBB3A6C6B;
	Wed, 27 Feb 2008 11:13:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.165
X-Spam-Level: 
X-Spam-Status: No, score=-0.165 tagged_above=-999 required=5 tests=[AWL=0.045,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	RDNS_NONE=0.1, 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 sxRVnq3HB1Vi; Wed, 27 Feb 2008 11:13:48 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 611A83A6E5D;
	Wed, 27 Feb 2008 11:13:48 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D7E843A6BE1
	for <nsis@core3.amsl.com>; Wed, 27 Feb 2008 11:13:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 Ed4i2Nu2HFI6 for <nsis@core3.amsl.com>;
	Wed, 27 Feb 2008 11:13:45 -0800 (PST)
Received: from QMTA07.emeryville.ca.mail.comcast.net
	(qmta07.emeryville.ca.mail.comcast.net [76.96.30.64])
	by core3.amsl.com (Postfix) with ESMTP id EFD1228C3C0
	for <nsis@ietf.org>; Wed, 27 Feb 2008 11:13:35 -0800 (PST)
Received: from OMTA04.emeryville.ca.mail.comcast.net ([76.96.30.35])
	by QMTA07.emeryville.ca.mail.comcast.net with comcast
	id ui7e1Y0720lTkoCA702b00; Wed, 27 Feb 2008 19:12:57 +0000
Received: from [192.168.1.120] ([69.255.66.123])
	by OMTA04.emeryville.ca.mail.comcast.net with comcast
	id ujDS1Y00B2fa1BZ8Q00000; Wed, 27 Feb 2008 19:13:27 +0000
X-Authority-Analysis: v=1.0 c=1 a=BqEg4_3jAAAA:8 a=7zBnw3VQYnFWEkK_g4oA:9
	a=oPKELbNKVWp8exg-F48A:7 a=5S5j-6t0UHkJ2-57BwcxmkUIKKgA:4
	a=M3PvEdNFSBYA:10
Message-Id: <98914694-41FB-4E74-98AB-80FA48FDF3C3@g11.org.uk>
From: ken carlberg <carlberg@g11.org.uk>
To: Gerald Ash <gash5107@yahoo.com>
In-Reply-To: <379162.6526.qm@web63604.mail.re1.yahoo.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 27 Feb 2008 14:13:26 -0500
References: <379162.6526.qm@web63604.mail.re1.yahoo.com>
X-Mailer: Apple Mail (2.919.2)
Cc: john.loughney@nokia.com, "nsis \(\(E-mail\)\)" <nsis@ietf.org>
Subject: Re: [NSIS] Review of draft-ietf-nsis-qspec-18.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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


> BTW, essentially all service providers and equipment vendors belong  
> to and participate in the ITU.  All these service providers and  
> equipment vendors have unanimously agreed to Y.2171.

(i'll bite my tongue a bit).... but of those that do participate in  
the ITU, do they all support Y.2171 and provide it as a contracted  
service?  As written in QSPEC, the Admin Priority field is bound to  
those providers/vendors that offer the Y.2171 service, meaning that  
only those domains that support the 3 defined levels of Y.2171 can  
support the Admission Priority field of the QSPEC.  Also, there is a  
big difference between those that agree on a standard and those that  
support it as a service.

> This is a very different approach to 'admission priority' from what  
> QSPEC is standardizing.  You are introducing policy elements, PDPs  
> doing 'mappings', preemption, and namespaces.  AFAIK preemption  
> priority doesn't have namespaces, are you perhaps referring to RPH  
> namespaces here?

I didn't suggest preemption priority has namespaces, I just said that  
the topic is discussed -- specifically in sections 1.1 and 2.0 of ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-tsvwg-emergency-rsvp-05.txt

> > now, I'll re-ask my question.  if we follow your original approach
> > concerning the Admission Priority field, how do we know what  
> priority set is
> > to be supported if the ITU comes back and updates Y.2171 with a  
> different
> > set of values?  the QSPEC document started with Y.1571, and now we  
> have
> > Y.2171.  Certainly a flag day is not what is expected as a  
> solution to
> > support Y.<next-priority-set>.
>
> There is only Y.2171 and no Y.1571.  If ITU modifies Y.2171 later,  
> say adds more values, IANA tracks those changes into the admission  
> priority registry defined in QSPEC.  This is standard IANA policy;  
> registries do not have to be based *only* on IETF standards, they  
> can be based on standards from other SDOs.  I pointed this out  
> earlier based on my discussion with IANA a while ago.

I believe we are talking past each other at this point.  As I said  
before, I have _no_ qualms about tying the values of a field (and I'll  
explicitly say, a field placed in the IANA registry) to the values set  
by another standards body.  My concern is that you have a taken a  
field representing a (in your own words) "generic concept" (and most  
importantly _shared_ by two other documents) and constrained it to the  
output of another standards body.  Notice that neither I nor Francois  
has said any word about the field in Section 5.2.14 of the QSPEC  
titled "Y.1541 QoS Class".  The name says it all in that it is tied  
directly to Y.1541.

If the name of the field in Section 5.2.9 of the QSPEC is changed to  
"Y.2171 Admission Priority", I'll be more than happy to drop the  
subject altogether, and suggest we'll note in [emergency-rsvp] draft  
that Admission Priority field is not directly comparable with that in  
the QSPEC so as to avoid confusion.

But if the NSIS group and the QSPEC authors choose to keep the name  
Admission Priority as is, I'll beat the dead horse one last time and  
ask what will you do if the ITU updates Y.2171 with a new set of  
values (and IANA registers them) in light on an installed base that  
supports the original set of Y.2171?  Do you not lose the continuity  
in your approach with a flag day change by the installed base?

regards,

-ken

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


From nsis-bounces@ietf.org  Wed Feb 27 11:58:52 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C35763A6C6B;
	Wed, 27 Feb 2008 11:58:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.315
X-Spam-Level: 
X-Spam-Status: No, score=0.315 tagged_above=-999 required=5 tests=[AWL=-0.475,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_MESSAGE=1, RDNS_NONE=0.1, 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 JxMUBBuJHcPu; Wed, 27 Feb 2008 11:58:51 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF4ED3A69E1;
	Wed, 27 Feb 2008 11:58:51 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 993A63A6929
	for <nsis@core3.amsl.com>; Wed, 27 Feb 2008 11:58:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 lWdKQ+FLTXCA for <nsis@core3.amsl.com>;
	Wed, 27 Feb 2008 11:58:45 -0800 (PST)
Received: from QMTA09.emeryville.ca.mail.comcast.net
	(qmta09.emeryville.ca.mail.comcast.net [76.96.30.96])
	by core3.amsl.com (Postfix) with ESMTP id 288113A6B00
	for <nsis@ietf.org>; Wed, 27 Feb 2008 11:58:45 -0800 (PST)
Received: from OMTA12.emeryville.ca.mail.comcast.net ([76.96.30.44])
	by QMTA09.emeryville.ca.mail.comcast.net with comcast
	id uaes1Y0020x6nqcA90df00; Wed, 27 Feb 2008 19:57:58 +0000
Received: from [192.168.1.120] ([69.255.66.123])
	by OMTA12.emeryville.ca.mail.comcast.net with comcast
	id ujyY1Y00L2fa1BZ8Y00000; Wed, 27 Feb 2008 19:58:34 +0000
X-Authority-Analysis: v=1.0 c=1 a=u874EDu-B64A:10 a=f-gx8SfH2Plneg7DZCIA:9
	a=tuv9HZEeBOVmkbyOy2YA:7 a=a-rfqxUNQrhvS67Kr9zl0GMbze0A:4
	a=WuK_CZDBSqoA:10
	a=UP_r64zuE79oV6JtwCIA:9 a=2SKHl9zL8lLjIAzUrIMA:7
	a=gioyNW46U2dXryAvdmFieL0bQSoA:4 a=37WNUvjkh6kA:10
Message-Id: <47E7E9D1-DAE6-4EF8-A08D-7C132A50E3F8@g11.org.uk>
From: ken carlberg <carlberg@g11.org.uk>
To: Gerald Ash <gash5107@yahoo.com>
In-Reply-To: <350019.92229.qm@web63601.mail.re1.yahoo.com>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 27 Feb 2008 14:58:32 -0500
References: <350019.92229.qm@web63601.mail.re1.yahoo.com>
X-Mailer: Apple Mail (2.919.2)
Cc: John Loughney <john.loughney@nokia.com>, nsis <nsis@ietf.org>
Subject: Re: [NSIS] Admission field in QSPEC -- was RE: Review of
	draft-ietf-nsis-qspec-18.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>
Content-Type: multipart/mixed; boundary="===============1882209792=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


--===============1882209792==
Content-Type: multipart/alternative; boundary=Apple-Mail-18-349329731


--Apple-Mail-18-349329731
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit


On Feb 27, 2008, at 12:56 PM, Gerald Ash wrote:

> Obviously one option is for emergency-rsvp to adopt the approach  
> being taken all along in QSPEC.  We are not being told why this is  
> not considered.

oh come on.  how many times must be said and in how many ways?  on  
February 25, 2008 2:50:24 PM EST I stated the following

"and as far as the current values set by Y.1541, I wish there was  
support for Scavenger Service, which is considered less than Best  
Effort (already defined as "0" in Y.1541).  Since I'm not a member of  
the ITU, I can't advocate this position nor accomplish it if the  
Admission field of all three drafts <emergency-rsvp>, <dime-qos- 
parameters> and <nsis-qspec> are subject to values defined by the ITU."

Put another way, Francois and I have said that we don't want an  
Admission Priority field to be constrained (limited, burdened,....pick  
the word of your choice) with pre-existing values, and in particular  
those that come from a different standards body.  And we are not  
condemning all other similar practices.  We are not even saying that  
those of Y.2171 cannot be used.

as for as the agreement that was passed around in nov/dec, you are not  
a newbie to think that agreements are etched in stone.  they exist to  
be commented on, hence our letting others on the diameter/tsvwg/nsis  
list know the results of private discussions.

> IMO we should retain the standardized admission priority levels as  
> included in QSPEC for a long time.  If emergency-rsvp cannot adopt  
> the same approach, then for now retain 2 approaches.

and I brought this up a while back as well.  we have no intention of  
steam rolling the agreement.  if part of the agreement breaks, it  
breaks and we'll go our separate ways.

and I apologize if this note is sounding a bit rude, but part of this  
is getting a bit much.

-ken


--Apple-Mail-18-349329731
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On Feb 27, 2008, =
at 12:56 PM, Gerald Ash wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; ">Obviously&nbsp;one option is for =
emergency-rsvp to adopt the approach&nbsp;being taken all along&nbsp;in =
QSPEC.&nbsp; We are not being told why this is not =
considered.&nbsp;</span></blockquote></div><br><div>oh come on. =
&nbsp;how many times must be said and in how many ways? =
&nbsp;on&nbsp;February 25, 2008 2:50:24 PM EST I stated the =
following</div><div><br =
class=3D"webkit-block-placeholder"></div><div><span =
class=3D"Apple-style-span" style=3D"font-family: Arial; font-size: 13px; =
">"and as far as the current values set by Y.1541, I wish there was =
support for Scavenger Service, which is considered less than Best Effort =
(already defined as "0" in Y.1541). &nbsp;Since I'm not a member of the =
ITU, I can't advocate this position nor accomplish it if the Admission =
field of all three drafts&nbsp;<span class=3D"Apple-style-span" =
style=3D"font-family: Times; font-size: 15px; ">&lt;emergency-rsvp&gt;, =
&lt;dime-qos-parameters&gt; and &lt;nsis-qspec&gt;</span>&nbsp;are =
subject to values defined by the ITU."</span></div><div><font =
class=3D"Apple-style-span" size=3D"3"><span class=3D"Apple-style-span" =
style=3D"font-size: 13px;"><br =
class=3D"webkit-block-placeholder"></span></font></div><div>Put another =
way, Francois and I have said that we don't want an Admission Priority =
field to be constrained (limited, burdened,....pick the word of your =
choice) with pre-existing values, and in particular those that come from =
a different standards body. &nbsp;And we are not condemning all other =
similar practices. &nbsp;We are not even saying that those of Y.2171 =
cannot be used.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>as for as the agreement =
that was passed around in nov/dec, you are not a newbie to think that =
agreements are etched in stone. &nbsp;they exist to be commented on, =
hence our letting others on the diameter/tsvwg/nsis list know the =
results of private discussions.</div><div><br></div><div><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"color: rgb(0, 0, =
0); "><div>IMO we should retain the standardized admission priority =
levels&nbsp;as&nbsp;included in QSPEC for a long time.&nbsp; If =
emergency-rsvp cannot adopt the same approach, then for now retain 2 =
approaches.</div></span></blockquote><br></div><div>and I brought this =
up a while back as well. &nbsp;we have no intention of steam rolling the =
agreement. &nbsp;if part of the agreement breaks, it breaks and we'll go =
our separate ways. &nbsp;</div><div><br =
class=3D"webkit-block-placeholder"></div><div>and I apologize if this =
note is sounding a bit rude, but part of this is getting a bit =
much.</div><div><br =
class=3D"webkit-block-placeholder"></div><div>-ken</div><div><br =
class=3D"webkit-block-placeholder"></div></body></html>=

--Apple-Mail-18-349329731--

--===============1882209792==
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

--===============1882209792==--


From nsis-bounces@ietf.org  Thu Feb 28 00:45:18 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF3EE28C19F;
	Thu, 28 Feb 2008 00:45:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.264
X-Spam-Level: 
X-Spam-Status: No, score=-0.264 tagged_above=-999 required=5 tests=[AWL=0.173,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	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 946LxgBmtxh2; Thu, 28 Feb 2008 00:45:13 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A44D43A6A76;
	Thu, 28 Feb 2008 00:45:13 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 320F23A6807
	for <nsis@core3.amsl.com>; Thu, 28 Feb 2008 00:45:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 7uKr8+MF7olF for <nsis@core3.amsl.com>;
	Thu, 28 Feb 2008 00:45:06 -0800 (PST)
Received: from smtp.mei.co.jp (smtp.mei.co.jp [133.183.100.20])
	by core3.amsl.com (Postfix) with ESMTP id EFB0A3A6B06
	for <nsis@ietf.org>; Thu, 28 Feb 2008 00:45:05 -0800 (PST)
Received: from mail-gw.jp.panasonic.com ([157.8.1.145])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/kc-maile14) with ESMTP id
	m1S8ivkC005934
	for <nsis@ietf.org>; Thu, 28 Feb 2008 17:44:57 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlb3) with ESMTP id
	m1S8iwp17214
	for <nsis@ietf.org>; Thu, 28 Feb 2008 17:44:58 +0900 (JST)
Received: from epochmail.jp.panasonic.com (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/kc-maili03) with ESMTP id
	m1S8iw711124
	for <nsis@ietf.org>; Thu, 28 Feb 2008 17:44:58 +0900 (JST)
Received: by epochmail.jp.panasonic.com (8.12.11.20060308/3.7W/somla7) id
	m1S8iwDh022939
	for nsis@ietf.org; Thu, 28 Feb 2008 17:44:58 +0900 (JST)
Received: from [10.68.136.102]
	by somla7.jp.panasonic.com (8.12.11.20060308/3.7W) with ESMTP id
	m1S8ivGN022918
	for <nsis@ietf.org>; Thu, 28 Feb 2008 17:44:57 +0900 (JST)
Date: Thu, 28 Feb 2008 17:48:46 +0900
From: Takako Sanda <sanda.takako@jp.panasonic.com>
To: nsis@ietf.org
Message-Id: <20080228172910.EC77.SANDA.TAKAKO@jp.panasonic.com>
MIME-Version: 1.0
X-Mailer: Becky! ver. 2.24.02 [ja]
Subject: [NSIS] Open issues for NSIS Applicability mobility draft
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 all,

Here is a new version of NSIS Applicability Mobility draft.

http://www.ietf.org/internet-drafts/draft-ietf-nsis-applicability-mobility-signaling-09.txt

In this version, 2 out of 3 open issues were closed. I.e.,
- Security Consideration part has been cleaned up
- NAT traversal issued has been concluded.

If you have any opinion for closing these issues, please send them to
the ML.

This draft still have one open issue regarding MIP interaction part
(section 5), i.e., this section needs to be cleaned up.
However, I believe this section is already good shape and does not need
to change.
If anyone feel this section still need clean up, please send your
comments to the ML by 21st March 2008.

BR,
Takako


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


From nsis-bounces@ietf.org  Thu Feb 28 04:26:21 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3C4A528C698;
	Thu, 28 Feb 2008 04:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.602
X-Spam-Level: 
X-Spam-Status: No, score=-0.602 tagged_above=-999 required=5
	tests=[AWL=-0.165, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, 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 79h9JEhFkIzL; Thu, 28 Feb 2008 04:26:15 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CC52728C4C7;
	Thu, 28 Feb 2008 04:26:15 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 2C47F3A6A40
	for <nsis@core3.amsl.com>; Thu, 28 Feb 2008 04:26:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 viCyE+znKg7K for <nsis@core3.amsl.com>;
	Thu, 28 Feb 2008 04:26:09 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id 77CB13A6DF3
	for <nsis@ietf.org>; Thu, 28 Feb 2008 04:26:09 -0800 (PST)
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 52A302C009E8F
	for <nsis@ietf.org>; Thu, 28 Feb 2008 13:26:02 +0100 (CET)
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 2Xci7aGowUMn for <nsis@ietf.org>;
	Thu, 28 Feb 2008 13:26:02 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id 4108C2C009E8D
	for <nsis@ietf.org>; Thu, 28 Feb 2008 13:25:57 +0100 (CET)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 28 Feb 2008 13:25:56 +0100
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF53E019@mx1.office>
In-Reply-To: <20080228172910.EC77.SANDA.TAKAKO@jp.panasonic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Open issues for NSIS Applicability mobility draft
Thread-Index: Ach55kaWVIj/AD9NSIua6nzHee13VgAHp7Sw
References: <20080228172910.EC77.SANDA.TAKAKO@jp.panasonic.com>
From: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>
To: <nsis@ietf.org>
Subject: Re: [NSIS] Open issues for NSIS Applicability mobility draft
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 all, 

The authors have updated the document a lot in the last few months. Therefore, I encourage the WG to give it a in-depth review until the coming IETF meeting. 

Thank you,

  Martin

> -----Original Message-----
> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On 
> Behalf Of Takako Sanda
> Sent: Thursday, February 28, 2008 9:49 AM
> To: nsis@ietf.org
> Subject: [NSIS] Open issues for NSIS Applicability mobility draft
> 
> Hi all,
> 
> Here is a new version of NSIS Applicability Mobility draft.
> 
> http://www.ietf.org/internet-drafts/draft-ietf-nsis-applicabil
ity-mobility-signaling-09.txt
> 
> In this version, 2 out of 3 open issues were closed. I.e.,
> - Security Consideration part has been cleaned up
> - NAT traversal issued has been concluded.
> 
> If you have any opinion for closing these issues, please send 
> them to the ML.
> 
> This draft still have one open issue regarding MIP 
> interaction part (section 5), i.e., this section needs to be 
> cleaned up.
> However, I believe this section is already good shape and 
> does not need to change.
> If anyone feel this section still need clean up, please send 
> your comments to the ML by 21st March 2008.
> 
> BR,
> Takako
> 
> 
> _______________________________________________
> nsis mailing list
> nsis@ietf.org
> https://www.ietf.org/mailman/listinfo/nsis
> 

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  
_______________________________________________
nsis mailing list
nsis@ietf.org
https://www.ietf.org/mailman/listinfo/nsis


From nsis-bounces@ietf.org  Thu Feb 28 04:45:42 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 04A0428C203;
	Thu, 28 Feb 2008 04:45:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.48
X-Spam-Level: 
X-Spam-Status: No, score=-0.48 tagged_above=-999 required=5 tests=[AWL=-0.270,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	RDNS_NONE=0.1, 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 TzjOiBw0PerC; Thu, 28 Feb 2008 04:45:36 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7764F3A693E;
	Thu, 28 Feb 2008 04:45:36 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 860EE3A6DA3
	for <nsis@core3.amsl.com>; Thu, 28 Feb 2008 04:45:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 pkF8KXQO9lIK for <nsis@core3.amsl.com>;
	Thu, 28 Feb 2008 04:45:30 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id C15FF3A6B6E
	for <nsis@ietf.org>; Thu, 28 Feb 2008 04:45:29 -0800 (PST)
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id 9AD902C009E8F;
	Thu, 28 Feb 2008 13:45:22 +0100 (CET)
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 f0ZgyL4wnbfH; Thu, 28 Feb 2008 13:45:22 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id 707782C009E8E;
	Thu, 28 Feb 2008 13:44:57 +0100 (CET)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 28 Feb 2008 13:44:56 +0100
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF53E026@mx1.office>
In-Reply-To: <47E7E9D1-DAE6-4EF8-A08D-7C132A50E3F8@g11.org.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Admission field in QSPEC -- was RE: Review
	ofdraft-ietf-nsis-qspec-18.txt
Thread-Index: Ach5ezeQxbOVD4YFSdq1bpoYfLdgHgAiZUfw
References: <350019.92229.qm@web63601.mail.re1.yahoo.com>
	<47E7E9D1-DAE6-4EF8-A08D-7C132A50E3F8@g11.org.uk>
From: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>
To: "ken carlberg" <carlberg@g11.org.uk>, "Gerald Ash" <gash5107@yahoo.com>,
	"Francois Le Faucheur IMAP" <flefauch@cisco.com>
Cc: John Loughney <john.loughney@nokia.com>, nsis <nsis@ietf.org>
Subject: Re: [NSIS] Admission field in QSPEC -- was RE: Review
	ofdraft-ietf-nsis-qspec-18.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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Hi all,

I'm jumping late to this discussion -- the IETF deadline and the aftermath kept me busy. Sorry for that. 

First of all, John and me believed to have rough consensus for the proposed change to the QSPEC draft. The proposed changed has been first discussed offline in end of Nov 2007 between the document authors of the involved drafts. On Dec 3, Francois sent an email to the dime, tsvwg and nsis list announcing the proposed changed. Nobody objected here. 

However, I have checked again and noted that Jerry was actually not listed as one of the email recipients in the offline conversation. Sorry for that, I personally have not noticed that earlier.

Given the state right now, I would not call it consensus. The discussions latetly on the nsis list have not reached consensus and further discussions are needed. I propose to discuss the issue further on the NSIS list and to definitely discuss this during the NSIS session (if possible for Ken and Francois to participate, otherwise off-session on the hallway). 

  Martin

> -----Original Message-----
> From: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On 
> Behalf Of ken carlberg
> Sent: Wednesday, February 27, 2008 8:59 PM
> To: Gerald Ash
> Cc: John Loughney; nsis
> Subject: Re: [NSIS] Admission field in QSPEC -- was RE: 
> Review ofdraft-ietf-nsis-qspec-18.txt
> 
> 
> On Feb 27, 2008, at 12:56 PM, Gerald Ash wrote:
> 
> 
> 	Obviously one option is for emergency-rsvp to adopt the 
> approach being taken all along in QSPEC.  We are not being 
> told why this is not considered. 
> 
> 
> oh come on.  how many times must be said and in how many 
> ways?  on February 25, 2008 2:50:24 PM EST I stated the following
> 
> "and as far as the current values set by Y.1541, I wish there 
> was support for Scavenger Service, which is considered less 
> than Best Effort (already defined as "0" in Y.1541).  Since 
> I'm not a member of the ITU, I can't advocate this position 
> nor accomplish it if the Admission field of all three drafts 
> <emergency-rsvp>, <dime-qos-parameters> and <nsis-qspec> are 
> subject to values defined by the ITU."
> 
> 
> Put another way, Francois and I have said that we don't want 
> an Admission Priority field to be constrained (limited, 
> burdened,....pick the word of your choice) with pre-existing 
> values, and in particular those that come from a different 
> standards body.  And we are not condemning all other similar 
> practices.  We are not even saying that those of Y.2171 
> cannot be used.
> 
> as for as the agreement that was passed around in nov/dec, 
> you are not a newbie to think that agreements are etched in 
> stone.  they exist to be commented on, hence our letting 
> others on the diameter/tsvwg/nsis list know the results of 
> private discussions.
> 
> 
> 	
> 	IMO we should retain the standardized admission 
> priority levels as included in QSPEC for a long time.  If 
> emergency-rsvp cannot adopt the same approach, then for now 
> retain 2 approaches.
> 
> 
> and I brought this up a while back as well.  we have no 
> intention of steam rolling the agreement.  if part of the 
> agreement breaks, it breaks and we'll go our separate ways.  
> 
> and I apologize if this note is sounding a bit rude, but part 
> of this is getting a bit much.
> 
> -ken
> 
> 

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  
_______________________________________________
nsis mailing list
nsis@ietf.org
https://www.ietf.org/mailman/listinfo/nsis


From nsis-bounces@ietf.org  Thu Feb 28 05:20:35 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4A0CA28C24E;
	Thu, 28 Feb 2008 05:20:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.644
X-Spam-Level: 
X-Spam-Status: No, score=-0.644 tagged_above=-999 required=5
	tests=[AWL=-0.434, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, 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 0f5vxM6UpqKq; Thu, 28 Feb 2008 05:20:29 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CF2C83A6E24;
	Thu, 28 Feb 2008 05:20:29 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id DA59E3A6D23
	for <nsis@core3.amsl.com>; Thu, 28 Feb 2008 05:20:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 lYyplfINHti4 for <nsis@core3.amsl.com>;
	Thu, 28 Feb 2008 05:20:28 -0800 (PST)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id C9D863A6C5C
	for <nsis@ietf.org>; Thu, 28 Feb 2008 05:20:27 -0800 (PST)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	3AF9421D0C; Thu, 28 Feb 2008 14:02:50 +0100 (CET)
X-AuditID: c1b4fb3c-ad8babb000007e19-6e-47c6b0fa1bdd
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	1779421CF7; Thu, 28 Feb 2008 14:02:50 +0100 (CET)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 28 Feb 2008 14:02:49 +0100
Received: from [127.0.0.1] ([147.214.30.103]) by esealmw126.eemea.ericsson.se
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 28 Feb 2008 14:02:49 +0100
Message-ID: <47C6B0F9.2010402@ericsson.com>
Date: Thu, 28 Feb 2008 14:02:49 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Martin Stiemerling <Stiemerling@nw.neclab.eu>
References: <350019.92229.qm@web63601.mail.re1.yahoo.com>	<47E7E9D1-DAE6-4EF8-A08D-7C132A50E3F8@g11.org.uk>
	<5F6519BF2DE0404D99B7C75607FF76FF53E026@mx1.office>
In-Reply-To: <5F6519BF2DE0404D99B7C75607FF76FF53E026@mx1.office>
X-OriginalArrivalTime: 28 Feb 2008 13:02:49.0095 (UTC)
	FILETIME=[382F6170:01C87A0A]
X-Brightmail-Tracker: AAAAAA==
Cc: John Loughney <john.loughney@nokia.com>, nsis <nsis@ietf.org>
Subject: Re: [NSIS] Admission field in QSPEC -- was RE:
	Review	ofdraft-ietf-nsis-qspec-18.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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Martin Stiemerling skrev:
> Hi all,
> 
> I'm jumping late to this discussion -- the IETF deadline and the aftermath kept me busy. Sorry for that. 
> 
> First of all, John and me believed to have rough consensus for the proposed change to the QSPEC draft. The proposed changed has been first discussed offline in end of Nov 2007 between the document authors of the involved drafts. On Dec 3, Francois sent an email to the dime, tsvwg and nsis list announcing the proposed changed. Nobody objected here. 
> 
> However, I have checked again and noted that Jerry was actually not listed as one of the email recipients in the offline conversation. Sorry for that, I personally have not noticed that earlier.
> 
> Given the state right now, I would not call it consensus. The discussions latetly on the nsis list have not reached consensus and further discussions are needed. I propose to discuss the issue further on the NSIS list and to definitely discuss this during the NSIS session (if possible for Ken and Francois to participate, otherwise off-session on the hallway). 
> 

Please resolve this as quickly as possible. And if it effects 
draft-ietf-tsvwg-emergency-rsvp then you better raise those issues in 
the WG last call currently being run. The last call ends: 28th of March.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | 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 Feb 28 05:40:54 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 788A328C431;
	Thu, 28 Feb 2008 05:40:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.48
X-Spam-Level: 
X-Spam-Status: No, score=-0.48 tagged_above=-999 required=5 tests=[AWL=-0.270,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	RDNS_NONE=0.1, 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 FE8AazO+8Nbk; Thu, 28 Feb 2008 05:40:53 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7342C28C0DA;
	Thu, 28 Feb 2008 05:40:53 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id E8E613A6961
	for <nsis@core3.amsl.com>; Thu, 28 Feb 2008 05:40:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 fHtvKbBRknXb for <nsis@core3.amsl.com>;
	Thu, 28 Feb 2008 05:40:46 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41])
	by core3.amsl.com (Postfix) with ESMTP id 20DD43A6927
	for <nsis@ietf.org>; Thu, 28 Feb 2008 05:40:46 -0800 (PST)
Received: from localhost (localhost.office [127.0.0.1])
	by smtp0.neclab.eu (Postfix) with ESMTP id C85842C002B4A;
	Thu, 28 Feb 2008 14:40:38 +0100 (CET)
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 eQulZNJ5fz0D; Thu, 28 Feb 2008 14:40:38 +0100 (CET)
Received: from mx1.office (mx1.office [10.1.1.23])
	by smtp0.neclab.eu (Postfix) with ESMTP id A4CD22C000355;
	Thu, 28 Feb 2008 14:40:18 +0100 (CET)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 28 Feb 2008 14:40:18 +0100
Message-ID: <5F6519BF2DE0404D99B7C75607FF76FF53E041@mx1.office>
In-Reply-To: <47E7E9D1-DAE6-4EF8-A08D-7C132A50E3F8@g11.org.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NSIS] Admission field in QSPEC -- was RE: Review
	ofdraft-ietf-nsis-qspec-18.txt
Thread-Index: Ach5ezeQxbOVD4YFSdq1bpoYfLdgHgAj8iSA
References: <350019.92229.qm@web63601.mail.re1.yahoo.com>
	<47E7E9D1-DAE6-4EF8-A08D-7C132A50E3F8@g11.org.uk>
From: "Martin Stiemerling" <Stiemerling@nw.neclab.eu>
To: "ken carlberg" <carlberg@g11.org.uk>,
	"Gerald Ash" <gash5107@yahoo.com>
Cc: John Loughney <john.loughney@nokia.com>, nsis <nsis@ietf.org>
Subject: Re: [NSIS] Admission field in QSPEC -- was RE: Review
	ofdraft-ietf-nsis-qspec-18.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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

[writing as WG member, i.e. WG chair's hat off]

Hi,

I took a while to wrap my head around it, as this touches not only NSIS' business but also other WG's business. 

I see the benefits of the end-to-end approach in general and also in particular for the QSPEC draft. The IETF is good in doing end-to-end protocols but has some issues in defining end-to-end QoS solutions (note the diffence between 'protocols' and 'solutions'). Having end-to-end QoS and signalling of it, is definitetly beneficially but is also troublesome.

We are doing protocols and not architectures, so it is hard to mandate which QoS scheme is used in the Internet or any other closed deployment. This lead to the concept of local QSPEC in the QSPEC draft which solves this at least on the signalling side but not on the semantics side (i.e., what do different bits mean in different domains).

ITU Y.2171 (Admission control priority levels in Next Generation Networks) is manadated for the admission priority in QSPEC regardless of the used admission priority scheme in a single domain. It is intended for NGN networks (which is ITU specific) but does not apply IMHO to the whole Internet as such. This does not excluded in general, but I don't regard ITU Y.2171 as the single scheme for all deployments.

The current definition of the Admission Priority in the QSPEC draft contradicts also the local QSPEC mechanism. A local domain that uses ITU Y.2171 can do this by using a local QSPEC. However, the general Admission Priority in the QSPEC must be free of ITU semantics, as this is from an IETF perspective just one of the possible admission schemes that can be used. 

Long story short: I'm in favour of Francois' proposal for the Admission Priority, posted on Dec 3, 2007:
http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html

  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: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On 
> Behalf Of ken carlberg
> Sent: Wednesday, February 27, 2008 8:59 PM
> To: Gerald Ash
> Cc: John Loughney; nsis
> Subject: Re: [NSIS] Admission field in QSPEC -- was RE: 
> Review ofdraft-ietf-nsis-qspec-18.txt
> 
> 
> On Feb 27, 2008, at 12:56 PM, Gerald Ash wrote:
> 
> 
> 	Obviously one option is for emergency-rsvp to adopt the 
> approach being taken all along in QSPEC.  We are not being 
> told why this is not considered. 
> 
> 
> oh come on.  how many times must be said and in how many 
> ways?  on February 25, 2008 2:50:24 PM EST I stated the following
> 
> "and as far as the current values set by Y.1541, I wish there 
> was support for Scavenger Service, which is considered less 
> than Best Effort (already defined as "0" in Y.1541).  Since 
> I'm not a member of the ITU, I can't advocate this position 
> nor accomplish it if the Admission field of all three drafts 
> <emergency-rsvp>, <dime-qos-parameters> and <nsis-qspec> are 
> subject to values defined by the ITU."
> 
> 
> Put another way, Francois and I have said that we don't want 
> an Admission Priority field to be constrained (limited, 
> burdened,....pick the word of your choice) with pre-existing 
> values, and in particular those that come from a different 
> standards body.  And we are not condemning all other similar 
> practices.  We are not even saying that those of Y.2171 
> cannot be used.
> 
> as for as the agreement that was passed around in nov/dec, 
> you are not a newbie to think that agreements are etched in 
> stone.  they exist to be commented on, hence our letting 
> others on the diameter/tsvwg/nsis list know the results of 
> private discussions.
> 
> 
> 	
> 	IMO we should retain the standardized admission 
> priority levels as included in QSPEC for a long time.  If 
> emergency-rsvp cannot adopt the same approach, then for now 
> retain 2 approaches.
> 
> 
> and I brought this up a while back as well.  we have no 
> intention of steam rolling the agreement.  if part of the 
> agreement breaks, it breaks and we'll go our separate ways.  
> 
> and I apologize if this note is sounding a bit rude, but part 
> of this is getting a bit much.
> 
> -ken
> 
> 
_______________________________________________
nsis mailing list
nsis@ietf.org
https://www.ietf.org/mailman/listinfo/nsis


From nsis-bounces@ietf.org  Thu Feb 28 06:09:46 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1EEA53A6E85;
	Thu, 28 Feb 2008 06:09:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.811
X-Spam-Level: 
X-Spam-Status: No, score=0.811 tagged_above=-999 required=5 tests=[AWL=0.648,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	J_CHICKENPOX_73=0.6, 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 L5g3Jtywysrm; Thu, 28 Feb 2008 06:09:45 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 361F03A6E95;
	Thu, 28 Feb 2008 06:09:45 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EB6613A6E95
	for <nsis@core3.amsl.com>; Thu, 28 Feb 2008 06:09:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 Q2B6fuOYmOUm for <nsis@core3.amsl.com>;
	Thu, 28 Feb 2008 06:09:39 -0800 (PST)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de
	[141.3.10.81]) by core3.amsl.com (Postfix) with ESMTP id 9E82E3A6E2F
	for <nsis@ietf.org>; Thu, 28 Feb 2008 06:09:38 -0800 (PST)
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 1JUjRt-0003Ej-O4; Thu, 28 Feb 2008 15:09:30 +0100
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 8DD6A2FC014;
	Thu, 28 Feb 2008 15:09:25 +0100 (CET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by vorta.tm.uka.de (Postfix) with ESMTP id 5F122100D4;
	Thu, 28 Feb 2008 15:10:59 +0100 (CET)
Message-ID: <47C6C073.1010403@tm.uka.de>
Date: Thu, 28 Feb 2008 15:08:51 +0100
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
X-Spam-Host: iramx2.ira.uni-karlsruhe.de
X-ATIS-Checksum: v3zoCAcc32ckk
Subject: [NSIS] Extension of NSLP Session Authorization
	(draft-manner-nsis-nslp-auth)
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,

just a few quick comments for extending the approach described in the
I-D draft-manner-nsis-nslp-auth,
http://tools.ietf.org/id/draft-manner-nsis-nslp-auth, which I
find very important for NSIS.
This draft proposes an object that can be embedded into NSLP
messages as an authorization token. User-based session authorization
is important for security-sensitive NAT/FW applications as well as
for QoS for secure accounting. However, we find the presented approach
a little bit too limited, since it mainly follows RFC3520.
The coupling between the authorization object and the NSLP
message is too weak in our opinion (basically only achieved by
the IP signaling source address).

Our idea is now, to actually "sign" NSLP messages by including
NSLP objects into the MAC. Thus, NSLP messages would be integrity
protected by an HMAC for example. So we could add a list of signed
NSLP object types, e.g.
                                       X-Type
      +--------------+--------------+--------------+--------------+
      | Length                      | NSLP_OBJ_LIST| SubType=0    |
      +--------------+--------------+--------------+--------------+
      |Number of NSLP signed objects|rsv |NSLP Signed Object (1)  |
      +--------------+--------------+--------------+--------------+
      |rsv |NSLP Signed Object (n)  |    (padding if required)    |
      +--------------+--------------+--------------+--------------+

So this list simply contains the object types of the NSLP message
that the MAC includes. Since NSLP object types have a common registry,
this can be used for every NSLP.
Furthermore, we propose that we try to consider "crypto agility" a
little bit, i.e., we want to include an identifier for the hash
algorithm etc.

Would this make sense to include such functionality into the nslp
session auth object?

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


From nsis-bounces@ietf.org  Thu Feb 28 06:14:45 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 860EA28C42E;
	Thu, 28 Feb 2008 06:14:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.325
X-Spam-Level: 
X-Spam-Status: No, score=-1.325 tagged_above=-999 required=5
	tests=[AWL=-1.715, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1,
	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 o-P2DEZ043za; Thu, 28 Feb 2008 06:14:39 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C339B3A6947;
	Thu, 28 Feb 2008 06:14:39 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 80D933A6A80
	for <nsis@core3.amsl.com>; Thu, 28 Feb 2008 06:14:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 peVC-FlYaaOl for <nsis@core3.amsl.com>;
	Thu, 28 Feb 2008 06:14:32 -0800 (PST)
Received: from mxoutps1.us.army.mil (mxoutps1.us.army.mil [143.69.250.38])
	by core3.amsl.com (Postfix) with ESMTP id 551E628C24E
	for <nsis@ietf.org>; Thu, 28 Feb 2008 06:14:30 -0800 (PST)
DomainKey-Signature: s=ako; d=us.army.mil; c=nofws; q=dns;
	h=From:X-AKO:X-IronPort-AV:Received:Received:To:Cc:
	Message-ID:Date:X-Mailer:MIME-Version:Content-Language:
	Subject:X-Accept-Language:Priority:In-Reply-To:References:
	Content-Type:Content-Disposition:
	Content-Transfer-Encoding;
	b=v1IGe4ydlje9BHzpDhO7sHZPDsW5wqUcCbkFL6yX7iOnR9itvb+gMxUj
	e4213EQTbIC7L7ufF9y0Fw2t+fecEg==;
From: "Roy, Radhika R Dr CTR USA USAMC" <radhika.r.roy@us.army.mil>
X-AKO: 124967455:10.224.36.65:28 Feb 2008 14:14:23 +0000:$Webmail:None
X-IronPort-AV: E=Sophos;i="4.25,419,1199664000"; d="scan'208";a="124967455"
Received: from mail5.int.ps1.us.army.mil (HELO us.army.mil) ([10.224.36.65])
	by mxoutps1.us.army.mil with ESMTP; 28 Feb 2008 14:14:21 +0000
Received: from [10.240.32.176] (Forwarded-For: 134.80.13.193,
	[10.240.32.176]) by mail5.int.ps1.us.army.mil (mshttpd); Thu, 28 Feb
	2008 09:14:21 -0500
To: Martin Stiemerling <Stiemerling@nw.neclab.eu>
Message-ID: <de9ecc6a7c0c.47c67b6d@us.army.mil>
Date: Thu, 28 Feb 2008 09:14:21 -0500
X-Mailer: Sun Java(tm) System Messenger Express 6.2-9.04 (built Jun 11
 2007)
MIME-Version: 1.0
Content-Language: en
X-Accept-Language: en
Priority: normal
In-Reply-To: <5F6519BF2DE0404D99B7C75607FF76FF53E041@mx1.office>
References: <350019.92229.qm@web63601.mail.re1.yahoo.com>
	<47E7E9D1-DAE6-4EF8-A08D-7C132A50E3F8@g11.org.uk>
	<5F6519BF2DE0404D99B7C75607FF76FF53E041@mx1.office>
Content-Disposition: inline
Cc: John Loughney <john.loughney@nokia.com>, nsis <nsis@ietf.org>
Subject: Re: [NSIS] Admission field in QSPEC -- was RE: Review
 ofdraft-ietf-nsis-qspec-18.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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

Martin and all:

I believe that the part of the problems of the QSPEC draft is mixing of two things: 1. A generalized QOS scheme that does not specify and particular "values" used by Y.xxx (ITU-T), MPLS QOS (IETF), etc. and 2. Implementation-specific schemes that mandate some specific values by ITU-T Y.xxx, IETF MPLS QOS, etc.

In the beginning, I already raised the same issue and proposed that the draft needs to be split into two parts: Part I: A generalized QSPEC draft that does not mandate any values in any fields and Part II: Implementation-specific QSPEC draft - a. IETF MPLS QOS Model, b. IETF DiffServ QOS Model, c. ITU-T Y.xxx models, etc.

Now, we are seeing that the discussions and proposals are bouncing back and forth between the two parts: Part I and Part II.

In the past, I also suggested that Part I QSPEC draft can be a standard-track RFC while Part II may have several "Informational RFCs."

I suggest that we have still time to follow the above guidance by splitting the draft. I would be extremely glad if people would prove that my suggestion is the wrong one.

Best regards,
Radhika

----- Original Message -----
From: Martin Stiemerling 
Date: Thursday, February 28, 2008 8:41
Subject: Re: [NSIS] Admission field in QSPEC -- was RE: Review ofdraft-ietf-nsis-qspec-18.txt
To: ken carlberg , Gerald Ash 
Cc: John Loughney , nsis 

> [writing as WG member, i.e. WG chair's hat off]
> 
> Hi,
> 
> I took a while to wrap my head around it, as this touches not only 
> NSIS' business but also other WG's business. 
> 
> I see the benefits of the end-to-end approach in general and also 
> in particular for the QSPEC draft. The IETF is good in doing end-
> to-end protocols but has some issues in defining end-to-end QoS 
> solutions (note the diffence between 'protocols' and 'solutions'). 
> Having end-to-end QoS and signalling of it, is definitetly 
> beneficially but is also troublesome.
> 
> We are doing protocols and not architectures, so it is hard to 
> mandate which QoS scheme is used in the Internet or any other 
> closed deployment. This lead to the concept of local QSPEC in the 
> QSPEC draft which solves this at least on the signalling side but 
> not on the semantics side (i.e., what do different bits mean in 
> different domains).
> 
> ITU Y.2171 (Admission control priority levels in Next Generation 
> Networks) is manadated for the admission priority in QSPEC 
> regardless of the used admission priority scheme in a single 
> domain. It is intended for NGN networks (which is ITU specific) 
> but does not apply IMHO to the whole Internet as such. This does 
> not excluded in general, but I don't regard ITU Y.2171 as the 
> single scheme for all deployments.
> 
> The current definition of the Admission Priority in the QSPEC 
> draft contradicts also the local QSPEC mechanism. A local domain 
> that uses ITU Y.2171 can do this by using a local QSPEC. However, 
> the general Admission Priority in the QSPEC must be free of ITU 
> semantics, as this is from an IETF perspective just one of the 
> possible admission schemes that can be used. 
> 
> Long story short: I'm in favour of Francois' proposal for the 
> Admission Priority, posted on Dec 3, 2007:
> http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html
> 
> 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: nsis-bounces@ietf.org [mailto:nsis-bounces@ietf.org] On 
> > Behalf Of ken carlberg
> > Sent: Wednesday, February 27, 2008 8:59 PM
> > To: Gerald Ash
> > Cc: John Loughney; nsis
> > Subject: Re: [NSIS] Admission field in QSPEC -- was RE: 
> > Review ofdraft-ietf-nsis-qspec-18.txt
> > 
> > 
> > On Feb 27, 2008, at 12:56 PM, Gerald Ash wrote:
> > 
> > 
> > Obviously one option is for emergency-rsvp to adopt the 
> > approach being taken all along in QSPEC. We are not being 
> > told why this is not considered. 
> > 
> > 
> > oh come on. how many times must be said and in how many 
> > ways? on February 25, 2008 2:50:24 PM EST I stated the following
> > 
> > "and as far as the current values set by Y.1541, I wish there 
> > was support for Scavenger Service, which is considered less 
> > than Best Effort (already defined as "0" in Y.1541). Since 
> > I'm not a member of the ITU, I can't advocate this position 
> > nor accomplish it if the Admission field of all three drafts 
> > , and are 
> > subject to values defined by the ITU."
> > 
> > 
> > Put another way, Francois and I have said that we don't want 
> > an Admission Priority field to be constrained (limited, 
> > burdened,....pick the word of your choice) with pre-existing 
> > values, and in particular those that come from a different 
> > standards body. And we are not condemning all other similar 
> > practices. We are not even saying that those of Y.2171 
> > cannot be used.
> > 
> > as for as the agreement that was passed around in nov/dec, 
> > you are not a newbie to think that agreements are etched in 
> > stone. they exist to be commented on, hence our letting 
> > others on the diameter/tsvwg/nsis list know the results of 
> > private discussions.
> > 
> > 
> > 
> > IMO we should retain the standardized admission 
> > priority levels as included in QSPEC for a long time. If 
> > emergency-rsvp cannot adopt the same approach, then for now 
> > retain 2 approaches.
> > 
> > 
> > and I brought this up a while back as well. we have no 
> > intention of steam rolling the agreement. if part of the 
> > agreement breaks, it breaks and we'll go our separate ways. 
> > 
> > and I apologize if this note is sounding a bit rude, but part 
> > of this is getting a bit much.
> > 
> > -ken
> > 
> > 
> _______________________________________________
> 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 Feb 29 10:27:08 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BF02D3A6D82;
	Fri, 29 Feb 2008 10:27:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.904
X-Spam-Level: 
X-Spam-Status: No, score=-0.904 tagged_above=-999 required=5
	tests=[AWL=-1.694, BAYES_00=-2.599, FH_RELAY_NODNS=1.451,
	HELO_MISMATCH_ORG=0.611, HTML_MESSAGE=1, RDNS_NONE=0.1,
	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 uhvxGBZdMpzp; Fri, 29 Feb 2008 10:27:03 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0C51C28C3B7;
	Fri, 29 Feb 2008 10:27:02 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 429D63A6D53
	for <nsis@core3.amsl.com>; Fri, 29 Feb 2008 10:27:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 CT-fXx6EwGra for <nsis@core3.amsl.com>;
	Fri, 29 Feb 2008 10:27:00 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id E7A4C3A6CD8
	for <nsis@ietf.org>; Fri, 29 Feb 2008 10:26:59 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.25,427,1199682000"; 
	d="scan'208,217";a="149487378"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 29 Feb 2008 13:26:52 -0500
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m1TIQqNd009738; 
	Fri, 29 Feb 2008 13:26:52 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m1TIQpjE017698; 
	Fri, 29 Feb 2008 18:26:52 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Feb 2008 13:26:47 -0500
Received: from [64.100.116.55] ([64.100.116.55]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Feb 2008 13:26:46 -0500
In-Reply-To: <350019.92229.qm@web63601.mail.re1.yahoo.com>
References: <350019.92229.qm@web63601.mail.re1.yahoo.com>
Mime-Version: 1.0 (Apple Message framework v753)
Message-Id: <0F183E58-6FBD-46F1-8200-8075F1B98DD3@cisco.com>
From: Francois Le Faucheur IMAP <flefauch@cisco.com>
Date: Fri, 29 Feb 2008 13:26:43 -0500
To: Gerald Ash <gash5107@yahoo.com>
X-Mailer: Apple Mail (2.753)
X-OriginalArrivalTime: 29 Feb 2008 18:26:46.0718 (UTC)
	FILETIME=[A45305E0:01C87B00]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5544; t=1204309612;
	x=1205173612; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=flefauch@cisco.com;
	z=From:=20Francois=20Le=20Faucheur=20IMAP=20<flefauch@cisco.
	com>
	|Subject:=20Re=3A=20Admission=20field=20in=20QSPEC=20--=20w
	as=20RE=3A=20[NSIS]=20Review=20of=20draft-ietf-nsis-qspec-18
	.txt |Sender:=20 |To:=20Gerald=20Ash=20<gash5107@yahoo.com>;
	bh=Wgoj3MvPhXovL3nsUznua4tyk+xhHatkm2zx52PUW0Q=;
	b=EijRTkPjPLvHR6Syxy1Q605GfD0oPesrdC3WEy9w2YDukn6nOSxxmrxbgo
	TXxHJM/7UCaBYmI30Cf277HJmfxwRG14/hskCQZZr7ckmjvGn9kgPYvSV+eR
	DyO+bP/YdF;
Authentication-Results: rtp-dkim-1; header.From=flefauch@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Cc: John Loughney <john.loughney@nokia.com>, nsis <nsis@ietf.org>,
	David R Oran <oran@cisco.com>
Subject: Re: [NSIS] Admission field in QSPEC -- was RE: Review of
	draft-ietf-nsis-qspec-18.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>
Content-Type: multipart/mixed; boundary="===============1187628481=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org


--===============1187628481==
Content-Type: multipart/alternative; boundary=Apple-Mail-3-516620772


--Apple-Mail-3-516620772
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

Hello Jerry,

On 27 Feb 2008, at 12:56, Gerald Ash wrote:

> All,
>
> John writes in http://www.ietf.org/mail-archive/web/nsis/current/ 
> msg08243.html:
>
> John> Just some background history.  There are 3 documents defining  
> similar
> John> fields
> John>
> John> tsvwg-emergency-rsvp
> John> nsis-qspec
> John> dime-qos-parameters
> John>
> John> We discussed this on this list and at previous IETF meetings.
> John> My view of consensus was that...
>
> I've seen no discussion on the list either before or after the  
> 'Proposed Resolution' was posted on 3 December at http:// 
> www.ietf.org/mail-archive/web/nsis/current/msg08155.html.

which suggested to us that the proposal was acceptable to the group.

> This is just presented and not explained.  AFAICT no co-authors of  
> the QSPEC document participated actively in the off-line discussion  
> or explicitly agreed to the proposed resolution.

Just for the records, all the qspec authors (but you) were part of  
the discussion that lead to this proposal. One of them (Dave)  
actually participated actively and contributed to the proposal. The  
only reason you were not in the list is because you were believed to  
be retired (and I think the only email address we had for you was no  
longer reaching you).

Have you considered the possible compromised approach to indicate in  
QSPEC that the ITU values/semantics  MAY be used (as opposed to MUST  
be used)?

Francois 
--Apple-Mail-3-516620772
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
 Hello Jerry,<div><br><div><div>On 27 Feb 2008, at 12:56, Gerald Ash =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>All,</div>  <div>=A0</div>  <div>John writes in <a =
href=3D"http://www.ietf.org/mail-archive/web/nsis/current/msg08243.html">h=
ttp://www.ietf.org/mail-archive/web/nsis/current/msg08243.html</a>:</div> =
 <div>=A0</div>  <div><span class=3D"044595419-25022008"><font =
face=3D"Arial">John&gt; Just some background history.=A0 There are 3 =
documents defining similar</font></span></div>  <div><span =
class=3D"044595419-25022008"><font =
face=3D"Arial">John&gt;=A0fields</font></span></div>  <div><span =
class=3D"044595419-25022008"><font face=3D"Arial"><span =
class=3D"044595419-25022008"><font =
face=3D"Arial">John&gt;</font></span></font></span></div>  <div><span =
class=3D"044595419-25022008"><font face=3D"Arial"><span =
class=3D"044595419-25022008"><font =
face=3D"Arial">John&gt;</font></span>=A0tsvwg-emergency-rsvp =
</font></span></div>  <div><span class=3D"044595419-25022008"><font =
face=3D"Arial"><span class=3D"044595419-25022008"><font =
face=3D"Arial">John&gt;</font></span>=A0nsis-qspec </font></span></div>  =
<div><span class=3D"044595419-25022008"><font face=3D"Arial"><span =
class=3D"044595419-25022008"><font =
face=3D"Arial">John&gt;</font></span>=A0dime-qos-parameters</font></span><=
/div>  <div><span class=3D"044595419-25022008"><span =
class=3D"044595419-25022008"><font =
face=3D"Arial">John&gt;</font></span></span></div>  <div><span =
class=3D"044595419-25022008"><font face=3D"Arial" color=3D"#0000ff"><font =
color=3D"#000000"><span class=3D"044595419-25022008"><font =
face=3D"Arial">John&gt; </font></span>We discussed this on this list and =
at previous IETF meetings.</font></font></span></div>  <div><span =
class=3D"044595419-25022008">John&gt; My view<span =
class=3D"044595419-25022008"><font face=3D"Arial" color=3D"#0000ff"><font =
color=3D"#000000">=A0of consensus was =
that...</font></font></span></span></div>  <div><span =
class=3D"044595419-25022008"><span =
class=3D"044595419-25022008"></span></span>=A0</div>  <div><font =
face=3D"arial">I've seen no discussion on the list either before or =
after the 'Proposed Resolution' was posted on 3 December at=A0</font><a =
href=3D"http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html" =
rel=3D"nofollow"><font =
face=3D"arial">http://www.ietf.org/mail-archive/web/nsis/current/msg08155.=
html</font></a>.=A0 </div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div><div>which suggested to us that =
the proposal was acceptable to the group.</div><br><blockquote =
type=3D"cite"><div>This is just presented and not explained.=A0 AFAICT =
no co-authors of the QSPEC document participated actively in the =
off-line discussion or explicitly=A0agreed to the proposed =
resolution.=A0</div></blockquote><div><br =
class=3D"webkit-block-placeholder"></div></div>Just for the records, all =
the qspec authors (but you) were part of the discussion that lead to =
this proposal. One of them (Dave) actually participated actively and =
contributed to the proposal. The only reason you were not in the list is =
because you were believed to be retired (and I think the only email =
address we had for you was no longer reaching you).</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Have you considered the =
possible compromised approach to indicate in QSPEC that the ITU =
values/semantics =A0MAY be used (as opposed to MUST be =
used)?=A0</div><div><br =
class=3D"webkit-block-placeholder"></div><div>Francois=A0</div></body></ht=
ml>=

--Apple-Mail-3-516620772--

--===============1187628481==
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

--===============1187628481==--


From nsis-bounces@ietf.org  Fri Feb 29 10:46:21 2008
Return-Path: <nsis-bounces@ietf.org>
X-Original-To: ietfarch-nsis-archive@core3.amsl.com
Delivered-To: ietfarch-nsis-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 691B93A6EF7;
	Fri, 29 Feb 2008 10:46:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.983
X-Spam-Level: 
X-Spam-Status: No, score=0.983 tagged_above=-999 required=5 tests=[AWL=0.192,
	BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611,
	HTML_MESSAGE=1, MIME_HTML_MOSTLY=0.001, RDNS_NONE=0.1,
	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 tFhlkIak3yDE; Fri, 29 Feb 2008 10:46:19 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3FBB728C1CD;
	Fri, 29 Feb 2008 10:46:19 -0800 (PST)
X-Original-To: nsis@core3.amsl.com
Delivered-To: nsis@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 0659D3A6E22
	for <nsis@core3.amsl.com>; Fri, 29 Feb 2008 10:46:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 gLgZrjBqSWHC for <nsis@core3.amsl.com>;
	Fri, 29 Feb 2008 10:46:15 -0800 (PST)
Received: from web63613.mail.re1.yahoo.com (web63613.mail.re1.yahoo.com
	[69.147.97.83]) by core3.amsl.com (Postfix) with SMTP id 7F1123A6E1A
	for <nsis@ietf.org>; Fri, 29 Feb 2008 10:46:15 -0800 (PST)
Received: (qmail 68246 invoked by uid 60001); 29 Feb 2008 18:46:07 -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=ATaZU0lfftnpkZL6f3StKN4CQNg34NKsdL1Foc18utnq+4kCdI1jltltJM1rnG12HxWpzN+jW6PJQcNRolOW/2tuzzYJrtboPI/WY8TLf6N7ctrjkKM8GuIR7ymEp8DsIMb/Shodg+UGN+KQ67SsLIPWETnAEGDPHdGqwTUzM0M=;
X-YMail-OSG: 8ivE6OEVM1k7d5BE0wnHqgnhhPj3aVr_bhXC7EkUWJOtYTDL1ir5E0bqy.dQ2hOyRQlze51k8Lx.uWsdyYW6ib41z_YT6Xmbo8dzN_ayD6VXeB4zVgmOGQ--
Received: from [76.19.255.157] by web63613.mail.re1.yahoo.com via HTTP;
	Fri, 29 Feb 2008 10:46:07 PST
Date: Fri, 29 Feb 2008 10:46:07 -0800 (PST)
From: Gerald Ash <gash5107@yahoo.com>
To: nsis <nsis@ietf.org>
In-Reply-To: <350019.92229.qm@web63601.mail.re1.yahoo.com>
MIME-Version: 1.0
Message-ID: <706743.66403.qm@web63613.mail.re1.yahoo.com>
Cc: John Loughney <john.loughney@nokia.com>
Subject: Re: [NSIS] Admission field in QSPEC -- was RE: Review of
	draft-ietf-nsis-qspec-18.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>
Content-Type: multipart/mixed; boundary="===============0347256836=="
Sender: nsis-bounces@ietf.org
Errors-To: nsis-bounces@ietf.org

--===============0347256836==
Content-Type: multipart/alternative; boundary="0-946362353-1204310767=:66403"
Content-Transfer-Encoding: 8bit

--0-946362353-1204310767=:66403
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

All,
   
  I agree with Ken that we are talking past each other at this point.  Magnus has requested to resolve this issue quickly, so I also agree with Ken to resolve the issue based on his suggestion in http://www.ietf.org/mail-archive/web/nsis/current/msg08257.html:
   
  "If the name of the field in Section 5.2.9 of the QSPEC is changed to  
"Y.2171 Admission Priority", I'll be more than happy to drop the  
subject altogether, and suggest we'll note in [emergency-rsvp] draft  
that Admission Priority field is not directly comparable with that in  
the QSPEC so as to avoid confusion."
   
  I agree that the qspec approach and emergency-rsvp approach are not directly comparable, in fact, they are very different.  At the risk of (again) 'being a bit much', let me elaborate one more time on the differences as I see them:
   
  As I've stated before, IMO admission priority should apply end-to-end and across administrative domains, and the only way to do that is to standardize the admission priority values in an IANA registry.  This is the approach taken in qspec, where the initial values to populate the admission priority registry have been taken from Y.2171 since AFAIK this is the only SDO to standardize admission priority levels so far.  The process to standardize these has been rigorous and agreed to by essentially all service providers (and equipment vendors).  However, these are only initial values to populate the registry and it does *not* mean that only the ITU can change the registry to include more or changed values.  E.g., Ken can propose his 'Scavenger Service' (less than Best Effort) through the standard IANA procedure specified in qspec Section 7 (IANA considerations):
   
    "Admission Priority Parameter (8 bits):
   The following values are allocated by this specification:
   0-2: assigned as specified in Section 6.2.9:
   Admission Priority 0: best-effort priority flow
                      1: normal priority flow
                      2: high priority flow
   The allocation policies for further values are as follows:
   3-63: Standards Action
   64-255: Reserved"
   
  In addition, the qspec approach is the same as used in practice today for emergency telecommunications services (ETS, e.g., GETS) to achieve end-to-end admission priority across domains.  One reference as how this approach operates in practice today for ETS/GETS can be found in http://www.amazon.com/Traffic-Engineering-Optimization-Integrated-Networks/dp/0123706254/ (apologies for self reference, but I'd be very happy to hear other references to implementation examples).  The same reference also presents extensive modeling & simulation analysis to show how this approach can operate across domains in the Internet.
   
  OTOH, the emergency-rsvp approach is very different.  It does not prescribe end-to-end cross domain consist treatment of admission priority.  As stated in Section 2 of emergency-rsvp:
   
    "As an example of operation across multiple administrative domains, a 
   first domain might decide to provide network layer admission priority 
   to calls of a given Application Level Resource Priority and map it 
   into a high RSVP admission control priority inside the Admission 
   Priority Policy Element; while a second domain may decide to not 
   provide admission priority to calls of this same Application Level 
   Resource Priority and hence map it into a low RSVP admission control 
   priority."
   
  So in this RSVP approach an ETS/GETS service might *not* get uniformly high admission priority treatment across administrative domains (ADs), depending on how the policy decision points (PDPs) in each AD decide to populate the RSVP Admission Priority element.  Furthermore, my understanding is that the PDP in each AD is expected to always key off the Application Level Resource Priority (based on the SIP resource priority header).  These are 2 major differences with the qspec approach.  I presume, however, that the RSVP admission priority approach is implemented (or planned to be implemented) in real network applications.  It would be nice to be enlightened RE implementations, existing or planned, if possible.
   
  A further suggestion is to re-name the RSVP approach <RSVP Admission Priority> to distinguish it from <Y.2171 Admission Priority>, so that neither approach should be considered a 'generic' approach.
   
  Barring any objection, I'll go ahead and modify the qspec draft to rename <Admission Priority> to <Y.2171 Admission Priority>, as agreed.
   
  Jerry
  

Gerald Ash <gash5107@yahoo.com> wrote: 
    All,
   
  John writes in http://www.ietf.org/mail-archive/web/nsis/current/msg08243.html:
   
  John> Just some background history.  There are 3 documents defining similar
  John> fields
  John>
  John> tsvwg-emergency-rsvp 
  John> nsis-qspec 
  John> dime-qos-parameters
  John>
  John> We discussed this on this list and at previous IETF meetings.
  John> My view of consensus was that...
   
  I've seen no discussion on the list either before or after the 'Proposed Resolution' was posted on 3 December at http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html.  This is just presented and not explained.  AFAICT no co-authors of the QSPEC document participated actively in the off-line discussion or explicitly agreed to the proposed resolution.  So I don't see that there was any 'consensus'.
   
  John> ... there should be some harmony and
  John> a common registry between these documents. 
   
  The proposed resolution says:
   
  "o Regarding Admission Priority:
* every protocol spec will only indicate that "higher value means higher priority".
* there is no attempt to define what specific values should be used for what. this is left outside the scope of the protocol specs.
* each protocol spec will add a statement clarifying that a given Admission Priority is to be encoded with the same value in each of the three protocol spec. For example, in tsvwg-emergency-rsvp, under section 3.1. we will add:
" A given Admission Priority is encoded in this information element
using the same value as when encoded in the Admission Priority
parameter defined in section 6.2.9 of [nsis-qspec], or in the Admission
Priority parameter defined in section 4.10 of [dime-qos-parameters].
In other words, a given value in any of the [emergency-rsvp] Admission
Priority information element, the [nsis-qspec] Admission Priority parameter
or the [dime-qos-parameters] Admission Priority parameter, refers to
the same Admission Priority.
"
* the mirror statement will be added in nsis-qspec (section 6.2.9) and dime-qos-parameters (section 4.10)"
   
  The above proposed resolution is very unclear and does not begin to explain that (apparently) what is proposed is to drop the QSPEC approach to admission priority and replace it with the emergency-rsvp approach.  
   
  Admission priority is a well defined concept supporting priority in flow admission control.  There are 3 priority levels defined in QSPEC, following the agreement standardized in Y.2171 http://www.itu.int/rec/T-REC-Y.2171/en.  The intent is that 'high admission priority' is reserved for emergency telecommunications.  'Normal admission priority' is reserved for traffic that is not as critical as emergency telecommunications but requires better than 'best effort admission priority'.  Examples include real-time services (VoIP, video), VPN and data services. 'Best effort admission' priority is reserved for a broad class of traffic that can be considered the lowest priority best effort flows.  Examples include “traditional” ISP services (e-mail, web surfing). 
   
  According to Francois (see http://www.ietf.org/mail-archive/web/nsis/current/msg08251.html), the emergency-rsvp approach is something aligned with preemption priority where no standard admission priority values are standardized in a registry.  However preemption priority works in a completely different way than admission priority; there are 2 values; 'defending priority' and 'preemption priority'.  These can be assigned somewhat arbitrarily since only the *relative* values have significance.  That is, the absolute values don't matter, it is only the relative value that matters.  In this way preemption can work across domains without standarding absolute values of defending priority and preemption priority.  It is unclear how such an approach can work for admission priority since the decision to admit or not admit a flow is done at the time of flow admission control and there is no prior 'defending priority' assigned to a flow when it first arrives for admission control. 
 So it unclear how the emergency-rsvp approach is aligned with the preemption priority approach.
   
  According to Ken (see http://www.ietf.org/mail-archive/web/nsis/current/msg08248.html), the emergency-rsvp approach involves using policy elements, PDPs doing 'mappings', preemption, and namespaces.  AFAIK preemption priority doesn't have namespaces, and what Ken describes looks different from what Francois describes.  
   
  In any case it appears that emergency-rsvp is doing something quite different from what QSPEC is doing.
   
  John> I think wee need to be able to support a few different scenarios and usages 
John> for the admission priority.
   
  I'm not sure what 'different scenarios' we're trying to support here?  As discussed above, admission priority is a well defined concept supporting priority in flow admission control.  I've seen no mention of any other 'different scenarios' for admission priority on the list.  Can you elaborate?
   
  John> Is there a way that we could have a  common structure to hold
  John> the values, and the ability to set the values accordingly?
 
Obviously one option is for emergency-rsvp to adopt the approach being taken all along in QSPEC.  We are not being told why this is not considered. 
  
Francois> Perhaps another option could be for the Qspec document to state
  Francois> that the Admission Priority values MAY be set according to Y.2171
  Francois> (but not mandate those are the only valid assignment and not
  Francois> request creation of a Qspec-specific IANA registry for those)?
   
  This is essentially the same as the 'proposed agreement', i.e. to drop the QSPEC approach to admission priority and do away with standardized admission priority values.  If we eliminate this standardization, then different admission priority values can be assigned in different Admin domains, and will have no end-to-end significance.  As such, each Admin domain has no idea how to treat the flow admission priority during flow admission since different domains are using different encodings of admission priority.
     

  IMO we should retain the standardized admission priority levels as included in QSPEC for a long time.  If emergency-rsvp cannot adopt the same approach, then for now retain 2 approaches.
   
  Jerry
    
---------------------------------
  Never miss a thing. Make Yahoo your homepage. 


       
---------------------------------
Never miss a thing.   Make Yahoo your homepage.
--0-946362353-1204310767=:66403
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div>All,</div>  <div>&nbsp;</div>  <div>I agree with Ken that we are talking past each other at this point.&nbsp;&nbsp;Magnus has requested to resolve this issue quickly, so I also agree with Ken to&nbsp;resolve the issue&nbsp;based on his suggestion in <A href="http://www.ietf.org/mail-archive/web/nsis/current/msg08257.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08257.html</A>:</div>  <div>&nbsp;</div>  <div>"If the name of the field in Section 5.2.9 of the QSPEC is changed to&nbsp; <BR>"Y.2171 Admission Priority", I'll be more than happy to drop the&nbsp; <BR>subject altogether, and suggest we'll note in [emergency-rsvp] draft&nbsp; <BR>that Admission Priority field is not directly comparable with that in&nbsp; <BR>the QSPEC so as to avoid confusion."</div>  <div>&nbsp;</div>  <div>I agree that the qspec approach and emergency-rsvp approach are not directly comparable, in fact, they are very different.&nbsp; At the risk of (again)&nbsp;'being a bit much',
 let me elaborate one more time on the differences as I see them:</div>  <div>&nbsp;</div>  <div>As I've stated before,&nbsp;IMO&nbsp;admission priority should apply end-to-end and across administrative domains, and the only way to do that is to standardize the admission priority values&nbsp;in an IANA&nbsp;registry.&nbsp; This is the approach taken in qspec, where the initial values to populate the admission priority registry have been taken from Y.2171 since AFAIK this is the only SDO to standardize admission priority levels&nbsp;so far.&nbsp;&nbsp;The process to standardize these has been rigorous and agreed to by essentially all service providers (and equipment vendors).&nbsp; However, these are only initial values to populate the registry and&nbsp;it does *not* mean that only the ITU can change the registry to include more or changed values.&nbsp; E.g., Ken can propose his&nbsp;'Scavenger Service' (less than Best Effort) through the standard IANA procedure specified in
 qspec Section 7 (IANA considerations):</div>  <div>&nbsp;</div>  <div>&nbsp;&nbsp;"Admission Priority Parameter (8 bits):<BR>&nbsp;&nbsp; The following values are allocated by this specification:<BR>&nbsp;&nbsp; 0-2: assigned as specified in Section 6.2.9:<BR>&nbsp;&nbsp; Admission Priority 0: best-effort priority flow<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1: normal priority flow<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2: high priority flow<BR>&nbsp;&nbsp; The allocation policies for further values are as follows:<BR>&nbsp;&nbsp; 3-63: Standards Action<BR>&nbsp;&nbsp; 64-255: Reserved"</div>  <div>&nbsp;</div>  <div>In addition, the qspec approach is the same as used in practice today for emergency telecommunications services&nbsp;(ETS, e.g., GETS) to achieve end-to-end admission priority
 across domains.&nbsp;&nbsp;One reference as how this approach operates in practice today for ETS/GETS can be found in&nbsp;<A href="http://www.amazon.com/Traffic-Engineering-Optimization-Integrated-Networks/dp/0123706254/">http://www.amazon.com/Traffic-Engineering-Optimization-Integrated-Networks/dp/0123706254/</A>&nbsp;(apologies for self reference, but I'd be very happy to hear&nbsp;other references to implementation examples).&nbsp; The same reference also presents extensive modeling &amp; simulation analysis&nbsp;to show&nbsp;how this approach can operate across domains in&nbsp;the Internet.</div>  <div>&nbsp;</div>  <div>OTOH, the emergency-rsvp approach is very different.&nbsp; It does not prescribe end-to-end cross domain consist treatment of admission priority.&nbsp; As stated in Section 2 of emergency-rsvp:</div>  <div>&nbsp;</div>  <div>&nbsp; "As an example of operation across multiple administrative domains, a <BR>&nbsp;&nbsp; first domain might decide to
 provide network layer admission priority <BR>&nbsp;&nbsp; to calls of a given Application Level Resource Priority and map it <BR>&nbsp;&nbsp; into a high RSVP admission control priority inside the Admission <BR>&nbsp;&nbsp; Priority Policy Element; while a second domain may decide to not <BR>&nbsp;&nbsp; provide admission priority to calls of this same Application Level <BR>&nbsp;&nbsp; Resource Priority and hence map it into a low RSVP admission control <BR>&nbsp;&nbsp; priority."</div>  <div>&nbsp;</div>  <div>So in this RSVP approach an ETS/GETS service might *not* get uniformly high admission priority treatment across administrative domains (ADs), depending on how the policy decision points (PDPs) in each AD decide to populate the RSVP Admission Priority element.&nbsp; Furthermore, my understanding is that the PDP in each AD is&nbsp;expected to&nbsp;always key off the Application Level Resource Priority (based on the SIP resource priority header).&nbsp; These are 2
 major differences with the qspec approach.&nbsp; I presume, however, that the RSVP admission priority approach is implemented (or planned to be implemented) in real network applications.&nbsp; It would be nice to be enlightened RE implementations, existing or planned,&nbsp;if possible.</div>  <div>&nbsp;</div>  <div>A further suggestion is to re-name the RSVP approach &lt;RSVP Admission Priority&gt; to distinguish it from &lt;Y.2171 Admission Priority&gt;, so that neither approach should be considered a 'generic' approach.</div>  <div>&nbsp;</div>  <div>Barring any objection, I'll go ahead and modify the qspec draft to rename &lt;Admission Priority&gt; to &lt;Y.2171 Admission Priority&gt;,&nbsp;as agreed.</div>  <div>&nbsp;</div>  <div>Jerry</div>  <div><BR><BR><B><I>Gerald Ash &lt;gash5107@yahoo.com&gt;</I></B> wrote: </div>  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">  <DIV>All,</DIV>  <DIV>&nbsp;</DIV>  <DIV>John
 writes in <A href="http://www.ietf.org/mail-archive/web/nsis/current/msg08243.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08243.html</A>:</DIV>  <DIV>&nbsp;</DIV>  <DIV><SPAN class=044595419-25022008><FONT face=Arial>John&gt; Just some background history.&nbsp; There are 3 documents defining similar</FONT></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><FONT face=Arial>John&gt;&nbsp;fields</FONT></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><FONT face=Arial><SPAN class=044595419-25022008><FONT face=Arial>John&gt;</FONT></SPAN></FONT></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><FONT face=Arial><SPAN class=044595419-25022008><FONT face=Arial>John&gt;</FONT></SPAN>&nbsp;tsvwg-emergency-rsvp </FONT></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><FONT face=Arial><SPAN class=044595419-25022008><FONT face=Arial>John&gt;</FONT></SPAN>&nbsp;nsis-qspec </FONT></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><FONT face=Arial><SPAN
 class=044595419-25022008><FONT face=Arial>John&gt;</FONT></SPAN>&nbsp;dime-qos-parameters</FONT></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><SPAN class=044595419-25022008><FONT face=Arial>John&gt;</FONT></SPAN></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><FONT face=Arial color=#0000ff><FONT color=#000000><SPAN class=044595419-25022008><FONT face=Arial>John&gt; </FONT></SPAN>We discussed this on this list and at previous IETF meetings.</FONT></FONT></SPAN></DIV>  <DIV><SPAN class=044595419-25022008>John&gt; My view<SPAN class=044595419-25022008><FONT face=Arial color=#0000ff><FONT color=#000000>&nbsp;of consensus was that...</FONT></FONT></SPAN></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><SPAN class=044595419-25022008></SPAN></SPAN>&nbsp;</DIV>  <DIV><FONT face=arial>I've seen no discussion on the list either before or after the 'Proposed Resolution' was posted on 3 December at&nbsp;</FONT><A
 href="http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html" rel=nofollow><FONT face=arial>http://www.ietf.org/mail-archive/web/nsis/current/msg08155.html</FONT></A>.&nbsp; This is just presented and not explained.&nbsp; AFAICT no co-authors of the QSPEC document participated actively in the off-line discussion or explicitly&nbsp;agreed to the proposed resolution.&nbsp; So I don't see that&nbsp;there was any 'consensus'.</DIV>  <DIV>&nbsp;</DIV>  <DIV>John&gt;&nbsp;... <SPAN class=044595419-25022008><FONT face=Arial color=#0000ff><FONT color=#000000>there should be some harmony and</FONT></FONT></SPAN></DIV>  <DIV><SPAN class=044595419-25022008><FONT face=Arial color=#0000ff><FONT color=#000000>John&gt;&nbsp;a common </FONT></FONT></SPAN><SPAN class=044595419-25022008><FONT face=Arial color=#0000ff><FONT color=#000000>registry between these documents</FONT>.&nbsp;</FONT></SPAN></DIV>  <DIV>&nbsp;</DIV>  <DIV>The proposed resolution&nbsp;says:</DIV> 
 <DIV>&nbsp;</DIV>  <DIV><FONT face=arial>"o Regarding Admission Priority:<BR>* every protocol spec will only indicate that "higher value means higher priority".<BR>* there is no attempt to define what specific values should be used for what. this is left outside the scope of the protocol specs.<BR>* each protocol spec will add a statement clarifying that a given Admission Priority is to be encoded with the same value in each of the three protocol spec. For example, in tsvwg-emergency-rsvp, under section 3.1. we will add:<BR>" A given Admission Priority is encoded in this information element<BR>using the same value as when encoded in the Admission Priority<BR>parameter defined in section 6.2.9 of [nsis-qspec], or in the Admission<BR>Priority parameter defined in section 4.10 of [dime-qos-parameters].<BR>In other words, a given value in any of the [emergency-rsvp] Admission<BR>Priority information element, the [nsis-qspec] Admission Priority parameter<BR>or the
 [dime-qos-parameters] Admission Priority parameter, refers to<BR>the same Admission Priority.<BR>"<BR>* the mirror statement will be added in nsis-qspec (section 6.2.9) and dime-qos-parameters (section 4.10)"</FONT></DIV>  <DIV><FONT face=arial></FONT>&nbsp;</DIV>  <DIV><FONT face=arial><FONT face=arial>The above proposed resolution&nbsp;is&nbsp;very unclear and does not begin to explain that (apparently) what is proposed is to drop the QSPEC approach to admission priority and replace it with&nbsp;the emergency-rsvp approach.&nbsp; </FONT></FONT></DIV>  <DIV><FONT face=arial><FONT face=arial></FONT></FONT>&nbsp;</DIV>  <DIV>Admission priority is a&nbsp;well defined concept supporting priority in flow admission control.&nbsp; There are 3 priority levels defined in QSPEC, following the agreement standardized in Y.2171 <A href="http://www.itu.int/rec/T-REC-Y.2171/en">http://www.itu.int/rec/T-REC-Y.2171/en</A>.&nbsp; The intent&nbsp;is&nbsp;that 'high admission
 priority'&nbsp;is reserved for emergency telecommunications.&nbsp;&nbsp;'Normal admission priority' is reserved for&nbsp;traffic <FONT face=arial>that&nbsp;is not as critical as emergency telecommunications but requires better than 'best effort admission priority'.&nbsp; <FONT face=arial>Examples include real-time services (VoIP, video), VPN and data services. </FONT>'Best effort admission' priority is&nbsp;reserved for a</FONT><FONT face=Arial size=2><SPAN class=669010221-26022008><FONT face=arial>&nbsp;broad class of traffic that can</FONT> be considered the lowest priority best effort flows.&nbsp; <FONT size=3><FONT size=2>Examples include “traditional” ISP services (e-mail, web surfing). </FONT></FONT></SPAN></FONT></DIV>  <DIV><FONT face=Arial size=2><SPAN class=669010221-26022008></SPAN></FONT>&nbsp;</DIV>  <DIV><FONT face=Arial size=2><SPAN class=669010221-26022008></SPAN></FONT><FONT face=arial><FONT face=arial>According to Francois (see <A
 href="http://www.ietf.org/mail-archive/web/nsis/current/msg08251.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08251.html</A>), the emergency-rsvp approach&nbsp;is something aligned with preemption priority where no standard admission priority values are standardized in a registry.&nbsp; </FONT></FONT><FONT face=arial><FONT face=arial>However preemption priority works in a completely different way than admission priority; there are 2 values; 'defending&nbsp;priority' and 'preemption priority'.&nbsp; These can be assigned somewhat arbitrarily since only the *relative* values have significance.&nbsp; That is, the absolute values don't matter, it is only the relative value that matters.&nbsp; In this way preemption can work across domains without standarding absolute values of defending priority and preemption priority.&nbsp; It is unclear how such an approach can work for admission priority since the decision to admit or not admit a flow is done&nbsp;at the time
 of flow&nbsp;admission control and there is no prior 'defending priority' assigned to a flow when it first arrives for admission control.&nbsp; So it unclear how the emergency-rsvp approach is aligned with the preemption priority approach.</DIV></FONT></FONT>  <DIV><FONT face=arial><FONT face=arial></FONT></FONT>&nbsp;</DIV>  <DIV><FONT face=arial><FONT face=arial>According to Ken (see <A href="http://www.ietf.org/mail-archive/web/nsis/current/msg08248.html">http://www.ietf.org/mail-archive/web/nsis/current/msg08248.html</A>), the emergency-rsvp approach involves using&nbsp;policy elements, PDPs doing 'mappings', preemption, and namespaces.&nbsp; AFAIK preemption priority doesn't have namespaces, and what Ken describes looks different from what Francois describes.&nbsp; </FONT></FONT></DIV>  <DIV><FONT face=arial><FONT face=arial></FONT></FONT>&nbsp;</DIV>  <DIV><FONT face=arial><FONT face=arial>In any case it appears that&nbsp;emergency-rsvp is doing something quite
 different from what QSPEC is doing.</DIV></FONT></FONT>  <DIV>&nbsp;</DIV>  <DIV>John&gt; I think wee need to be able to support a few different scenarios and usages <BR>John&gt; for the admission priority.</DIV>  <DIV>&nbsp;</DIV>  <DIV>I'm not sure what 'different scenarios' we're trying to support here?&nbsp; As discussed above, admission priority is a&nbsp;well defined concept supporting priority in flow admission control.&nbsp; I've seen no mention of any other 'different scenarios'&nbsp;for admission priority on the list.&nbsp; Can you elaborate?</DIV>  <DIV>&nbsp;</DIV>  <DIV>John&gt; Is there a way that we could have a&nbsp; common&nbsp;structure to hold</DIV>  <DIV>John&gt;&nbsp;the values, and the ability to set the values accordingly?<BR>&nbsp;<BR>Obviously&nbsp;one option is for emergency-rsvp to adopt the approach&nbsp;being taken all along&nbsp;in QSPEC.&nbsp; We are not being told why this is not considered.&nbsp;</DIV>  <DIV><BR>Francois&gt; Perhaps another
 option could be for the Qspec document to state</DIV>  <DIV>Francois&gt;&nbsp;that the&nbsp;Admission Priority values MAY be set according to Y.2171</DIV>  <DIV>Francois&gt;&nbsp;(but not mandate&nbsp;those are the only valid assignment and not</DIV>  <DIV>Francois&gt;&nbsp;request creation of a&nbsp;Qspec-specific IANA registry for those)?</DIV>  <DIV>&nbsp;</DIV>  <DIV>This is essentially the same as&nbsp;the 'proposed agreement', i.e.&nbsp;to drop the QSPEC approach to admission priority&nbsp;and do away with standardized admission priority values.&nbsp; If we eliminate this standardization,&nbsp;then different admission priority values&nbsp;can be&nbsp;assigned in different Admin domains, and will&nbsp;have no end-to-end significance.&nbsp; As such, each Admin domain has no idea how to treat the flow admission priority during flow admission since&nbsp;different domains are using different encodings of&nbsp;admission priority.</DIV>  <DIV>  <DIV>&nbsp;</DIV></DIV> 
 <DIV>IMO we should retain the standardized admission priority levels&nbsp;as&nbsp;included in QSPEC for a long time.&nbsp; If emergency-rsvp cannot adopt the same approach, then for now retain 2 approaches.</DIV>  <DIV>&nbsp;</DIV>  <DIV>Jerry</DIV>  <DIV>  <HR SIZE=1>  Never miss a thing. <A href="http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs">Make Yahoo your homepage.</A> </DIV></BLOCKQUOTE><BR><p>&#32;



      <hr size=1>Never miss a thing.  <a href="http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs"> Make Yahoo your homepage.</a>


--0-946362353-1204310767=:66403--

--===============0347256836==
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

--===============0347256836==--


