From tsvwg-bounces@ietf.org  Fri Apr  1 09:04:16 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27661;
	Fri, 1 Apr 2005 09:04:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHMsN-0003U6-7j; Fri, 01 Apr 2005 09:11:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHMf1-00073Q-5E; Fri, 01 Apr 2005 08:58:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHMez-00073I-Ic; Fri, 01 Apr 2005 08:58:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27047;
	Fri, 1 Apr 2005 08:58:01 -0500 (EST)
Received: from wyvern.icir.org ([192.150.187.14])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHMmJ-0003Du-0f; Fri, 01 Apr 2005 09:05:40 -0500
Received: from guns.icir.org (adsl-68-76-113-50.dsl.bcvloh.ameritech.net
	[68.76.113.50])
	by wyvern.icir.org (8.12.11/8.12.8) with ESMTP id j31Dvmq4037140;
	Fri, 1 Apr 2005 05:57:48 -0800 (PST) (envelope-from mallman@icir.org)
Received: from lawyers.icir.org (guns.icir.org [68.76.113.50])
	by guns.icir.org (Postfix) with ESMTP
	id F368977A6FB; Fri,  1 Apr 2005 08:57:46 -0500 (EST)
Received: from lawyers.icir.org (localhost [127.0.0.1])
	by lawyers.icir.org (Postfix) with ESMTP
	id 058042595AA; Fri,  1 Apr 2005 08:57:40 -0500 (EST)
To: Sally Floyd <floyd@icir.org>
From: Mark Allman <mallman@icir.org>
In-Reply-To: <200503312307.j2VN7QEa090898@cougar.icir.org> 
Organization: ICSI Center for Internet Research (ICIR)
Song-of-the-Day: Ain't Even Done With the Night
MIME-Version: 1.0
Date: Fri, 01 Apr 2005 08:57:40 -0500
Message-Id: <20050401135741.058042595AA@lawyers.icir.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: sumitha@tamu.edu, reddy@ee.tamu.edu, eblanton@cs.purdue.edu, tcpm@ietf.org,
        tsvwg@ietf.org
Subject: [Tsvwg] Re: a review for draft-ietf-tcpm-tcp-dcr-03.txt 
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mallman@icir.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2049269795=="
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3

--===============2049269795==
Content-Type: multipart/signed; boundary="=_bOundary";
	micalg=pgp-sha1; protocol="application/pgp-signature"

--=_bOundary
Content-Type: text/plain


Sally-

> I have one suggestion for presentation (a SHOULD, not a MUST), and
> that is that the document include an overview of the algorithm before
> jumping into the details of Sections 2.1, 2.2, 2.3, and 2.4.  That
> suggestion, and a few nits, are in the review below.

We have received a number of private comments that are similar to this
suggestion for a big picture explanation.  It's a good idea and we'll
endeavor to add such text.  We'll also address your smaller issues in
our next pass.  Thanks a ton for your careful read of the document!

allman



-- 
Mark Allman -- ICIR -- http://www.icir.org/mallman/




--=_bOundary
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Darwin)

iD8DBQFCTVNUWyrrWs4yIs4RAknKAJwKAdPWD7C8PIOljKfJmvqlRx1VhQCfXhSn
c9DfIDSzFvpK6ELDgUNlqFQ=
=Z3lM
-----END PGP SIGNATURE-----
--=_bOundary--


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

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg

--===============2049269795==--



From tsvwg-bounces@ietf.org  Fri Apr  1 11:45:05 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13779;
	Fri, 1 Apr 2005 11:45:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHPNz-0001Sa-Nq; Fri, 01 Apr 2005 11:52:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHPEr-0007NZ-NO; Fri, 01 Apr 2005 11:43:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHPEq-0007LQ-4Y
	for tsvwg@megatron.ietf.org; Fri, 01 Apr 2005 11:43:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13653
	for <tsvwg@ietf.org>; Fri, 1 Apr 2005 11:43:13 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHPMB-0001NJ-GJ
	for tsvwg@ietf.org; Fri, 01 Apr 2005 11:50:52 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 01 Apr 2005 08:43:06 -0800
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j31Gh3ZV022355
	for <tsvwg@ietf.org>; Fri, 1 Apr 2005 08:43:04 -0800 (PST)
Received: from [10.32.244.218] (stealth-10-32-244-218.cisco.com
	[10.32.244.218]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR)
	with SMTP id BDO08491; Fri, 1 Apr 2005 08:43:03 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Transfer-Encoding: 7bit
Message-Id: <b81ef65b304db9584e061f87e4714468@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: tsvwg@ietf.org
From: Baker Fred <fred@cisco.com>
Date: Fri, 1 Apr 2005 08:43:02 -0800
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d62ab47271805379d7172ee693a45db
Content-Transfer-Encoding: 7bit
Subject: [Tsvwg] RFC 4041 Requirements
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit

I note that RFC 4041 declares that discrimination among packets on the 
basis of color is no longer to be tolerated in the network. Does this 
mean that we need to withdraw proposals related to that?

:^)

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Fri Apr  1 14:52:20 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00207;
	Fri, 1 Apr 2005 14:52:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHSJF-0000Nm-BS; Fri, 01 Apr 2005 15:00:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHS97-0005z6-8X; Fri, 01 Apr 2005 14:49:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHS95-0005z1-CO
	for tsvwg@megatron.ietf.org; Fri, 01 Apr 2005 14:49:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00012
	for <tsvwg@ietf.org>; Fri, 1 Apr 2005 14:49:27 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHSGR-0000HY-5A
	for tsvwg@ietf.org; Fri, 01 Apr 2005 14:57:09 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 01 Apr 2005 11:49:18 -0800
X-IronPort-AV: i="3.91,141,1110182400"; 
	d="scan'208"; a="625127608:sNHT29504720"
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j31JnGZV005353;
	Fri, 1 Apr 2005 11:49:16 -0800 (PST)
Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com
	[171.68.225.134]) by wells.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id LAA14575;
	Fri, 1 Apr 2005 11:49:15 -0800 (PST)
Message-Id: <4.3.2.7.2.20050401134709.03aa3510@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 01 Apr 2005 13:49:15 -0600
To: Baker Fred <fred@cisco.com>, tsvwg@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Tsvwg] RFC 4041 Requirements
In-Reply-To: <b81ef65b304db9584e061f87e4714468@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22

At 08:43 AM 4/1/2005 -0800, Baker Fred wrote:
>I note that RFC 4041 declares that discrimination among packets on the 
>basis of color is no longer to be tolerated in the network. Does this mean 
>that we need to withdraw proposals related to that?

I think affects optical transport more than anything, as they will have to 
solve for putting all their bandwidth into a single lambda, thus preventing 
preferential treatments based on the color of the lasers.


>:^)
>
>_______________________________________________
>tsvwg mailing list
>tsvwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/tsvwg


cheers,
James

                                *******************
                 Truth is not to be argued... it is to be presented

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Fri Apr  1 15:58:41 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16308;
	Fri, 1 Apr 2005 15:58:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHTLR-0005dM-0z; Fri, 01 Apr 2005 16:06:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHTA2-0005uo-C9; Fri, 01 Apr 2005 15:54:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHTA0-0005tt-46
	for tsvwg@megatron.ietf.org; Fri, 01 Apr 2005 15:54:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14853
	for <tsvwg@ietf.org>; Fri, 1 Apr 2005 15:54:30 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHTHN-00055J-L1
	for tsvwg@ietf.org; Fri, 01 Apr 2005 16:02:11 -0500
Received: from [128.9.168.55] (upn.isi.edu [128.9.168.55])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j31Kqf606141;
	Fri, 1 Apr 2005 12:52:41 -0800 (PST)
Message-ID: <424DB50C.7000304@isi.edu>
Date: Fri, 01 Apr 2005 12:54:36 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Tsvwg] RFC 4041 Requirements
References: <4.3.2.7.2.20050401134709.03aa3510@localhost>
In-Reply-To: <4.3.2.7.2.20050401134709.03aa3510@localhost>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: Baker Fred <fred@cisco.com>, tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



James M. Polk wrote:
> At 08:43 AM 4/1/2005 -0800, Baker Fred wrote:
> 
>> I note that RFC 4041 declares that discrimination among packets on the
>> basis of color is no longer to be tolerated in the network. Does this
>> mean that we need to withdraw proposals related to that?
> 
> I think affects optical transport more than anything, as they will have
> to solve for putting all their bandwidth into a single lambda, thus
> preventing preferential treatments based on the color of the lasers.

Agreed. WDM could be seen as revisiting "separate but equal" ;-)

It might affect military nets, though, too - the whole red/black thing
becomes moot in achromatic networks ;-)

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCTbUME5f5cImnZrsRAtqxAJ0UX2LWz47Nv9hjs4miGACXlhhVzgCfX4gK
Z/0ccPg40WSSd/dnytQ5Z6U=
=Nl47
-----END PGP SIGNATURE-----

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Fri Apr  1 16:36:05 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23783;
	Fri, 1 Apr 2005 16:36:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHTvd-00006m-D2; Fri, 01 Apr 2005 16:43:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHTnK-0000KM-UH; Fri, 01 Apr 2005 16:35:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHTnI-0000KD-UI
	for tsvwg@megatron.ietf.org; Fri, 01 Apr 2005 16:35:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23679
	for <tsvwg@ietf.org>; Fri, 1 Apr 2005 16:35:06 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHTug-00005C-Nr
	for tsvwg@ietf.org; Fri, 01 Apr 2005 16:42:48 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-5.cisco.com with ESMTP; 01 Apr 2005 13:34:56 -0800
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j31LYs3S025498;
	Fri, 1 Apr 2005 13:34:54 -0800 (PST)
Received: from [10.32.244.218] (stealth-10-32-244-218.cisco.com
	[10.32.244.218]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR)
	with SMTP id BDO42638; Fri, 1 Apr 2005 13:34:53 -0800 (PST)
In-Reply-To: <200504010025.j310Prj2092458@cougar.icir.org>
References: <200504010025.j310Prj2092458@cougar.icir.org>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <af5cb36f3c5e9a801d67ae1d0ec26b77@cisco.com>
Content-Transfer-Encoding: 7bit
From: Baker Fred <fred@cisco.com>
Subject: Re: [Tsvwg] Specifying Alternate Semantics for the ECN Field
Date: Fri, 1 Apr 2005 13:34:52 -0800
To: Sally Floyd <floyd@icir.org>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit

On Mar 31, 2005, at 4:25 PM, Sally Floyd wrote:
> http://www.icir.org/floyd/papers/draft-floyd-ecn-alternates-00a.txt

thanks for your considerations. I think you're pretty much dead on.

My belief is that re-interpreting a field in a manner differently than 
it has previously been defined makes life pretty difficult.. We chose 
to do that once in redefining the TOS byte from a precedence field and 
a set of bit flags to the DSCP and ECN fields; when we did so, we did 
so with great care, and only after significant research into what was 
actually used in the TOS byte in real networks, and provided for 
backwards compatibility with what we found to exist. My concern with 
the other ECN proposals I have seen is that they do not take that care. 
As such, they can only be used in a manner consistent with the RFC 
status "experimental use" as described in RFC 2026.

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Fri Apr  1 16:41:19 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24583;
	Fri, 1 Apr 2005 16:41:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHU0h-0000SR-VV; Fri, 01 Apr 2005 16:49:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHTqD-0000pv-0f; Fri, 01 Apr 2005 16:38:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHTqB-0000pG-7C; Fri, 01 Apr 2005 16:38:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24134;
	Fri, 1 Apr 2005 16:38:04 -0500 (EST)
Received: from amer-mta02.csc.com ([20.137.2.248])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHTxZ-0000G7-Pi; Fri, 01 Apr 2005 16:45:46 -0500
Received: from amer-gw09.csc.com (amer-gw09.csc.com [20.6.39.245])
	by amer-mta02.csc.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id
	j31LaxPa010755; Fri, 1 Apr 2005 16:36:59 -0500 (EST)
Subject: Re: [Tsvwg] RFC 4041 Requirements
To: Joe Touch <touch@ISI.EDU>
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
Message-ID: <OFC566700C.789F5F66-ON85256FD6.00766EB5-85256FD6.0076C960@csc.com>
From: Janet P Gunn <jgunn6@csc.com>
Date: Fri, 1 Apr 2005 16:35:45 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 6.5.3|September
	14, 2004) at 04/01/2005 04:37:13 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: "James M. Polk" <jmpolk@cisco.com>, tsvwg-bounces@ietf.org,
        Baker Fred <fred@cisco.com>, tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248





Can we discriminate based on age?  And if not, what happens to FIFO queues,
which CLEARLY discriminate on packet age?


----------------------------------------------------------------------------------------

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------




                                                                                                                                 
                      Joe Touch <touch                                                                                           
                      @ISI.EDU>                To:      "James M. Polk" <jmpolk@cisco.com>                                       
                      Sent by:                 cc:      Baker Fred <fred@cisco.com>, tsvwg@ietf.org                              
                      tsvwg-bounces            Subject: Re: [Tsvwg] RFC 4041 Requirements                                        
                                                                                                                                 
                                                                                                                                 
                      04/01/2005 03:54                                                                                           
                      PM                                                                                                         
                                                                                                                                 
                                                                                                                                 




-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



James M. Polk wrote:
> At 08:43 AM 4/1/2005 -0800, Baker Fred wrote:
>
>> I note that RFC 4041 declares that discrimination among packets on the
>> basis of color is no longer to be tolerated in the network. Does this
>> mean that we need to withdraw proposals related to that?
>
> I think affects optical transport more than anything, as they will have
> to solve for putting all their bandwidth into a single lambda, thus
> preventing preferential treatments based on the color of the lasers.

Agreed. WDM could be seen as revisiting "separate but equal" ;-)

It might affect military nets, though, too - the whole red/black thing
becomes moot in achromatic networks ;-)

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCTbUME5f5cImnZrsRAtqxAJ0UX2LWz47Nv9hjs4miGACXlhhVzgCfX4gK
Z/0ccPg40WSSd/dnytQ5Z6U=
=Nl47
-----END PGP SIGNATURE-----

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg




_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Fri Apr  1 17:04:39 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26273;
	Fri, 1 Apr 2005 17:04:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHUNJ-0001Iq-Cs; Fri, 01 Apr 2005 17:12:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHU8r-0005e9-Ie; Fri, 01 Apr 2005 16:57:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHU8o-0005e1-TN
	for tsvwg@megatron.ietf.org; Fri, 01 Apr 2005 16:57:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25850
	for <tsvwg@ietf.org>; Fri, 1 Apr 2005 16:57:20 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHUGD-00014M-2k
	for tsvwg@ietf.org; Fri, 01 Apr 2005 17:05:02 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 01 Apr 2005 13:57:13 -0800
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j31Lv8ZV008736;
	Fri, 1 Apr 2005 13:57:08 -0800 (PST)
Received: from [10.32.244.218] (stealth-10-32-244-218.cisco.com
	[10.32.244.218]) by mira-sjc5-b.cisco.com (MOS 3.4.5-GR)
	with SMTP id BDO44889; Fri, 1 Apr 2005 13:57:06 -0800 (PST)
In-Reply-To: <OFC566700C.789F5F66-ON85256FD6.00766EB5-85256FD6.0076C960@csc.com>
References: <OFC566700C.789F5F66-ON85256FD6.00766EB5-85256FD6.0076C960@csc.com>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <2d43289410e84915cda98fd31de5d3b4@cisco.com>
Content-Transfer-Encoding: 7bit
From: Baker Fred <fred@cisco.com>
Subject: Re: [Tsvwg] RFC 4041 Requirements
Date: Fri, 1 Apr 2005 13:57:05 -0800
To: Janet P Gunn <jgunn6@csc.com>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit

On Apr 1, 2005, at 1:35 PM, Janet P Gunn wrote:
> Can we discriminate based on age?  And if not, what happens to FIFO 
> queues, which CLEARLY discriminate on packet age?

Age isn't mentioned in the RFC that I saw. So we can still do that - at 
least until the right to life crowd gets hold of the TTL field. They 
will be happy with RFC 2304, though. It preserves the randomness 
inherent in the system.

I just noticed, in investigating that, that there remains a really odd 
case of discrimination present even in the RFC decrying it. The first 
bullet of section 2.2 indicates that any RFC describing a way to carry 
images must give careful consideration to the implications of carrying 
blue images.

Having recently thought long and deep about inter-SDO protocols, I was 
also struck by the fifth bullet (it wasn't painful). It may not be 
important, given that participants are doomed to spend eternity on 
dial-up links, but one wonders what the implications are if the 
messages exchanged propose liaisons or are statements relevant to such 
liaisons.

> On Apr 1, 2005, at 12:54 PM, Joe Touch wrote:
>> James M. Polk wrote:
>>> At 08:43 AM 4/1/2005 -0800, Baker Fred wrote:
>>>> I note that RFC 4041 declares that discrimination among packets on 
>>>> the basis of color is no longer to be tolerated in the network. 
>>>> Does this mean that we need to withdraw proposals related to that?
>>>
>>> I think affects optical transport more than anything, as they will 
>>> have to solve for putting all their bandwidth into a single lambda, 
>>> thus preventing preferential treatments based on the color of the 
>>> lasers.
>>
>> Agreed. WDM could be seen as revisiting "separate but equal" ;-)
>>
>> It might affect military nets, though, too - the whole red/black 
>> thing becomes moot in achromatic networks ;-)

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Fri Apr  1 18:09:24 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01219;
	Fri, 1 Apr 2005 18:09:24 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHVNx-0003XI-L5; Fri, 01 Apr 2005 18:17:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHVFe-00018H-MP; Fri, 01 Apr 2005 18:08:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHVFc-000189-Ic; Fri, 01 Apr 2005 18:08:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01064;
	Fri, 1 Apr 2005 18:08:25 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHVN1-0003Vc-9a; Fri, 01 Apr 2005 18:16:08 -0500
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j31N7S609443;
	Fri, 1 Apr 2005 15:07:28 -0800 (PST)
From: Bob Braden <braden@ISI.EDU>
Received: (from braden@localhost) by gra.isi.edu (8.9.3/8.8.6) id PAA25588;
	Fri, 1 Apr 2005 15:07:28 -0800 (PST)
Date: Fri, 1 Apr 2005 15:07:28 -0800 (PST)
Message-Id: <200504012307.PAA25588@gra.isi.edu>
To: touch@ISI.EDU, jgunn6@csc.com
Subject: Re: [Tsvwg] RFC 4041 Requirements
X-Sun-Charset: US-ASCII
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: tsvwg@ietf.org, jmpolk@cisco.com, tsvwg-bounces@ietf.org, fred@cisco.com
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad

  *> 
  *> 
  *> Can we discriminate based on age?


Only if you set the Evil Bit.

Bob Braden

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Fri Apr  1 18:15:03 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02087;
	Fri, 1 Apr 2005 18:15:03 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHVTS-0003lf-9n; Fri, 01 Apr 2005 18:22:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHVKv-0002ob-FZ; Fri, 01 Apr 2005 18:13:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHVKt-0002oU-HM
	for tsvwg@megatron.ietf.org; Fri, 01 Apr 2005 18:13:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01937
	for <tsvwg@ietf.org>; Fri, 1 Apr 2005 18:13:52 -0500 (EST)
Received: from cougar.icir.org ([192.150.187.76])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHVSI-0003jt-3f
	for tsvwg@ietf.org; Fri, 01 Apr 2005 18:21:35 -0500
Received: from cougar.icir.org (localhost [127.0.0.1])
	by cougar.icir.org (8.12.11/8.12.8) with ESMTP id j31NCqlm013008;
	Fri, 1 Apr 2005 15:12:52 -0800 (PST)
	(envelope-from floyd@cougar.icir.org)
Message-Id: <200504012312.j31NCqlm013008@cougar.icir.org>
To: Baker Fred <fred@cisco.com>
From: Sally Floyd <floyd@icir.org>
Subject: Re: [Tsvwg] Specifying Alternate Semantics for the ECN Field 
Date: Fri, 01 Apr 2005 15:12:52 -0800
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a

>On Mar 31, 2005, at 4:25 PM, Sally Floyd wrote:
>> http://www.icir.org/floyd/papers/draft-floyd-ecn-alternates-00a.txt
>
>thanks for your considerations. I think you're pretty much dead on.

Many thanks for the feedback.

>My belief is that re-interpreting a field in a manner differently than 
>it has previously been defined makes life pretty difficult.
>...
>
>My concern with 
>the other ECN proposals I have seen is that they do not take that care. 
>As such, they can only be used in a manner consistent with the RFC 
>status "experimental use" as described in RFC 2026.

I am mostly neutral about the various proposals, and about whether
they go as "experimental use" or as something else.  But it seems
to me that the RTECN proposal *could* end up being defined consistently
with draft-floyd-ecn-alternates, in a way that was safe to deploy
in the Internet.  It is not there yet, however, I would say...

- Sally



_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Mon Apr  4 11:19:33 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17325;
	Mon, 4 Apr 2005 11:19:32 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DITUR-0002B4-Kz; Mon, 04 Apr 2005 11:27:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DITJx-0005gv-2G; Mon, 04 Apr 2005 11:16:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DITJv-0005go-LC
	for tsvwg@megatron.ietf.org; Mon, 04 Apr 2005 11:16:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17153
	for <tsvwg@ietf.org>; Mon, 4 Apr 2005 11:16:53 -0400 (EDT)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DITRr-0001vN-Jo
	for tsvwg@ietf.org; Mon, 04 Apr 2005 11:25:08 -0400
Received: from zbl6c002.us.nortel.com (zbl6c002.corpeast.baynetworks.com
	[132.245.205.52])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP
	id j34FGTO14571; Mon, 4 Apr 2005 11:16:29 -0400 (EDT)
Received: from KCHAN-2K3.nortelnetworks.com (kchan-2k3.us.nortel.com
	[47.16.72.114]) by zbl6c002.us.nortel.com with SMTP (Microsoft
	Exchange Internet Mail Service Version 5.5.2653.13)
	id G4PJP2JY; Mon, 4 Apr 2005 11:16:28 -0400
Message-Id: <6.0.3.0.0.20050404105445.04d3eff8@zbl6c002.corpeast.baynetworks.com>
X-Sender: khchan@zbl6c002.corpeast.baynetworks.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
Date: Mon, 04 Apr 2005 11:15:58 -0400
To: Sally Floyd <floyd@icir.org>
From: Kwok Ho Chan <khchan@nortel.com>
Subject: Re: [Tsvwg] Specifying Alternate Semantics for the ECN Field 
In-Reply-To: <200504012312.j31NCqlm013008@cougar.icir.org>
References: <200504012312.j31NCqlm013008@cougar.icir.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: Baker Fred <fred@cisco.com>, tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe

Sally:
Thank you very much for the draft-floyd-ecn-alternates-00a.txt.
We greatly appreciate all the guidance and advice you have provided.

With respect to RTECN proposal:
We have been listening and improving on how to accomplish a goal with a 
simpler method.
As many of us are engineers, we continue to make trade-offs trying to 
provide the best
possible solutions.  We are trying to have the method we pick being lesser 
of the evils.

We are still making improvements to the RTECN proposal and the co-authors
don't think it is ready for the judgement call of which track it should be 
on and
have not indicated that we want such judgement be made at this time.
During the 62nd IETF in Minneapolis, we are asking for additional comments
so that we can improve this draft.
We are still keeping this draft as an individual contribution until it is 
ready.

We understand what we are doing and trying our best for the benefit of the 
Internet.
Thanks!
-- Kwok --

At 07:12 PM 4/1/2005, Sally Floyd wrote:
> >On Mar 31, 2005, at 4:25 PM, Sally Floyd wrote:
> >> http://www.icir.org/floyd/papers/draft-floyd-ecn-alternates-00a.txt
> >
> >thanks for your considerations. I think you're pretty much dead on.
>
>Many thanks for the feedback.
>
> >My belief is that re-interpreting a field in a manner differently than
> >it has previously been defined makes life pretty difficult.
> >...
> >
> >My concern with
> >the other ECN proposals I have seen is that they do not take that care.
> >As such, they can only be used in a manner consistent with the RFC
> >status "experimental use" as described in RFC 2026.
>
>I am mostly neutral about the various proposals, and about whether
>they go as "experimental use" or as something else.  But it seems
>to me that the RTECN proposal *could* end up being defined consistently
>with draft-floyd-ecn-alternates, in a way that was safe to deploy
>in the Internet.  It is not there yet, however, I would say...
>
>- Sally
>
>
>
>_______________________________________________
>tsvwg mailing list
>tsvwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/tsvwg


_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Thu Apr  7 13:27:46 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16927;
	Thu, 7 Apr 2005 13:27:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJavr-0003Xs-4g; Thu, 07 Apr 2005 13:36:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJadW-0003HL-Ha; Thu, 07 Apr 2005 13:17:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJadV-0003HG-9y
	for tsvwg@megatron.ietf.org; Thu, 07 Apr 2005 13:17:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16174
	for <tsvwg@ietf.org>; Thu, 7 Apr 2005 13:17:41 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJam6-0003BX-B5
	for tsvwg@ietf.org; Thu, 07 Apr 2005 13:26:38 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 07 Apr 2005 19:17:35 +0200
Received: from xbh-ams-331.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
	j37HHUt7007152; Thu, 7 Apr 2005 19:17:32 +0200 (MEST)
Received: from xmb-ams-333.cisco.com ([144.254.231.78]) by
	xbh-ams-331.cisco.com with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 7 Apr 2005 19:17:31 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 7 Apr 2005 19:17:27 +0200
Message-ID: <A05118C6DF9320488C77F3D5459B17B7764F61@xmb-ams-333.emea.cisco.com>
Thread-Topic: RSVP Aggregation over MPLS TE tunnels
Thread-Index: AcU7F5MFmbWjis5DRbGTTFyErVhchgAfIirQ
From: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>
To: "Drake, John E" <John.E.Drake2@boeing.com>,
        "Bruce Davie \(bdavie\)" <bdavie@cisco.com>
X-OriginalArrivalTime: 07 Apr 2005 17:17:31.0644 (UTC)
	FILETIME=[AEA98BC0:01C53B95]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: quoted-printable
Cc: tsvwg@ietf.org
Subject: [Tsvwg] RE: RSVP Aggregation over MPLS TE tunnels
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: quoted-printable

>> -----Original Message-----
>> From: Drake, John E [mailto:John.E.Drake2@boeing.com]=20
>> Sent: jeudi 7 avril 2005 04:15
>> To: Francois Le Faucheur (flefauch); Bruce Davie (bdavie)
>> Subject: RSVP Aggregation over MPLS TE tunnels
>>=20
>> Francois and Bruce,
>>=20
>> Does your I-D handle the case of placing aggregate=20
>> reservations, rather
>> than individual reservations, over an MPLS TE LSP?

Hello John,

Yes, it covers that case.

Specifically, section 5 "E2E Reservations Applicability" says:
   =20
"
   The procedures defined in this document are applicable to many types=20
   of E2E RSVP reservations including the following cases:=20
      (1)  the E2E RSVP reservation is a per-flow reservation where the=20
           flow is characterized by the usual 5-tuple=20
      (2)  the E2E reservation is an aggregate reservation for multiple=20
           flows as described in [RSVP-AGG] where the set of flows is=20
           characterized by the <source address, destination address,=20
           DSCP> =20
      (3)  the E2E reservation is a reservation for an IPSec protected=20
           flow. For example, where the flow is characterized by the=20
           <source address, destination address, SPI> as described in=20
           [RSVP-IPSEC]=20
      (4)  the E2E reservation is an aggregate reservation for multiple=20
           flows and where the set of flows are protected by IPSec=20
      (5)  the E2E RSVP reservation is itself an RSVP-TE reservation=20
           for an E2E TE tunnel, so that LSP Hierarchy is achieved=20
           [LSP-HIER]=20
"

I believe (2) would be the case you are refering to, right?

Cheers

Francois

>>=20
>> Thanks,
>>=20
>> John=20
>>=20
>> John Drake
>> Boeing Satellite Systems
>> 2300 East Imperial Highway
>> El Segundo, CA 90245
>> john.e.drake2@boeing.com
>> (412) 370-3108
>>=20

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Thu Apr  7 21:52:54 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29166;
	Thu, 7 Apr 2005 21:52:54 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJiok-0003MZ-Pg; Thu, 07 Apr 2005 22:01:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJibe-0001mB-4X; Thu, 07 Apr 2005 21:48:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJiUr-0000Om-42
	for tsvwg@megatron.ietf.org; Thu, 07 Apr 2005 21:41:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28285
	for <tsvwg@ietf.org>; Thu, 7 Apr 2005 21:41:18 -0400 (EDT)
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJidW-0002yc-82
	for tsvwg@ietf.org; Thu, 07 Apr 2005 21:50:18 -0400
Received: from stl-av-01.boeing.com ([192.76.190.6])
	by stl-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id
	UAA13213; Thu, 7 Apr 2005 20:41:06 -0500 (CDT)
Received: from XCH-SWBH-04.sw.nos.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id
	j381f6708008; Thu, 7 Apr 2005 20:41:06 -0500 (CDT)
Received: from XCH-SW-42.sw.nos.boeing.com ([192.79.11.43]) by
	XCH-SWBH-04.sw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.211); 
	Thu, 7 Apr 2005 18:41:05 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 7 Apr 2005 18:41:05 -0700
Message-ID: <626FC7C6A97381468FB872072AB5DDC815BD5F@XCH-SW-42.sw.nos.boeing.com>
Thread-Topic: RSVP Aggregation over MPLS TE tunnels
Thread-Index: AcU7F5MFmbWjis5DRbGTTFyErVhchgAfIirQAA1prZA=
From: "Drake, John E" <John.E.Drake2@boeing.com>
To: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>,
        "Bruce Davie \(bdavie\)" <bdavie@cisco.com>
X-OriginalArrivalTime: 08 Apr 2005 01:41:05.0801 (UTC)
	FILETIME=[07B40790:01C53BDC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 07 Apr 2005 21:48:20 -0400
Cc: tsvwg@ietf.org
Subject: [Tsvwg] RE: RSVP Aggregation over MPLS TE tunnels
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Content-Transfer-Encoding: quoted-printable

Francois,

Very good, thanks.  I skimmed sections 3.1 and 3.2 and misunderstood
what you meant by E2E reservation.

Section 5 defines what you mean by E2E reservation and my one suggestion
would be to consider moving the material in section 5 into section 2
(Definitions).

Thanks,

John=20

> -----Original Message-----
> From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> Sent: Thursday, April 07, 2005 10:17 AM
> To: Drake, John E; Bruce Davie (bdavie)
> Cc: Francois Le Faucheur (flefauch); tsvwg@ietf.org
> Subject: RE: RSVP Aggregation over MPLS TE tunnels
>=20
> >> -----Original Message-----
> >> From: Drake, John E [mailto:John.E.Drake2@boeing.com]
> >> Sent: jeudi 7 avril 2005 04:15
> >> To: Francois Le Faucheur (flefauch); Bruce Davie (bdavie)
> >> Subject: RSVP Aggregation over MPLS TE tunnels
> >>
> >> Francois and Bruce,
> >>
> >> Does your I-D handle the case of placing aggregate
> >> reservations, rather
> >> than individual reservations, over an MPLS TE LSP?
>=20
> Hello John,
>=20
> Yes, it covers that case.
>=20
> Specifically, section 5 "E2E Reservations Applicability" says:
>=20
> "
>    The procedures defined in this document are applicable to many
types
>    of E2E RSVP reservations including the following cases:
>       (1)  the E2E RSVP reservation is a per-flow reservation where
the
>            flow is characterized by the usual 5-tuple
>       (2)  the E2E reservation is an aggregate reservation for
multiple
>            flows as described in [RSVP-AGG] where the set of flows is
>            characterized by the <source address, destination address,
>            DSCP>
>       (3)  the E2E reservation is a reservation for an IPSec protected
>            flow. For example, where the flow is characterized by the
>            <source address, destination address, SPI> as described in
>            [RSVP-IPSEC]
>       (4)  the E2E reservation is an aggregate reservation for
multiple
>            flows and where the set of flows are protected by IPSec
>       (5)  the E2E RSVP reservation is itself an RSVP-TE reservation
>            for an E2E TE tunnel, so that LSP Hierarchy is achieved
>            [LSP-HIER]
> "
>=20
> I believe (2) would be the case you are refering to, right?
>=20
> Cheers
>=20
> Francois
>=20
> >>
> >> Thanks,
> >>
> >> John
> >>
> >> John Drake
> >> Boeing Satellite Systems
> >> 2300 East Imperial Highway
> >> El Segundo, CA 90245
> >> john.e.drake2@boeing.com
> >> (412) 370-3108
> >>

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Fri Apr  8 05:17:09 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21206;
	Fri, 8 Apr 2005 05:17:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJpki-0000H1-CW; Fri, 08 Apr 2005 05:26:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJpZm-0006F8-Ca; Fri, 08 Apr 2005 05:14:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJpZk-0006Dr-1D
	for tsvwg@megatron.ietf.org; Fri, 08 Apr 2005 05:14:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21098
	for <tsvwg@ietf.org>; Fri, 8 Apr 2005 05:14:50 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJpiS-0000BV-Sw
	for tsvwg@ietf.org; Fri, 08 Apr 2005 05:23:53 -0400
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 08 Apr 2005 11:14:42 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j389E9tX000298; 
	Fri, 8 Apr 2005 11:14:39 +0200 (MEST)
Received: from xmb-ams-333.cisco.com ([144.254.231.78]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.0); 
	Fri, 8 Apr 2005 11:14:35 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 8 Apr 2005 11:14:29 +0200
Message-ID: <A05118C6DF9320488C77F3D5459B17B7764F6A@xmb-ams-333.emea.cisco.com>
Thread-Topic: RSVP Aggregation over MPLS TE tunnels
Thread-Index: AcU7F5MFmbWjis5DRbGTTFyErVhchgAfIirQAA1prZAAFFxhcA==
From: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>
To: "Drake, John E" <John.E.Drake2@boeing.com>,
        "Bruce Davie \(bdavie\)" <bdavie@cisco.com>
X-OriginalArrivalTime: 08 Apr 2005 09:14:35.0712 (UTC)
	FILETIME=[6212F400:01C53C1B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Content-Transfer-Encoding: quoted-printable
Cc: tsvwg@ietf.org
Subject: [Tsvwg] RE: RSVP Aggregation over MPLS TE tunnels
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Content-Transfer-Encoding: quoted-printable

John,
I see. We will look at how to make the notion of "E2E" reservation clear
upfront in the document. Thanks.
Francois

>> -----Original Message-----
>> From: Drake, John E [mailto:John.E.Drake2@boeing.com]=20
>> Sent: vendredi 8 avril 2005 03:41
>> To: Francois Le Faucheur (flefauch); Bruce Davie (bdavie)
>> Cc: tsvwg@ietf.org
>> Subject: RE: RSVP Aggregation over MPLS TE tunnels
>>=20
>> Francois,
>>=20
>> Very good, thanks.  I skimmed sections 3.1 and 3.2 and misunderstood
>> what you meant by E2E reservation.
>>=20
>> Section 5 defines what you mean by E2E reservation and my=20
>> one suggestion
>> would be to consider moving the material in section 5 into section 2
>> (Definitions).
>>=20
>> Thanks,
>>=20
>> John=20
>>=20
>> > -----Original Message-----
>> > From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
>> > Sent: Thursday, April 07, 2005 10:17 AM
>> > To: Drake, John E; Bruce Davie (bdavie)
>> > Cc: Francois Le Faucheur (flefauch); tsvwg@ietf.org
>> > Subject: RE: RSVP Aggregation over MPLS TE tunnels
>> >=20
>> > >> -----Original Message-----
>> > >> From: Drake, John E [mailto:John.E.Drake2@boeing.com]
>> > >> Sent: jeudi 7 avril 2005 04:15
>> > >> To: Francois Le Faucheur (flefauch); Bruce Davie (bdavie)
>> > >> Subject: RSVP Aggregation over MPLS TE tunnels
>> > >>
>> > >> Francois and Bruce,
>> > >>
>> > >> Does your I-D handle the case of placing aggregate
>> > >> reservations, rather
>> > >> than individual reservations, over an MPLS TE LSP?
>> >=20
>> > Hello John,
>> >=20
>> > Yes, it covers that case.
>> >=20
>> > Specifically, section 5 "E2E Reservations Applicability" says:
>> >=20
>> > "
>> >    The procedures defined in this document are applicable to many
>> types
>> >    of E2E RSVP reservations including the following cases:
>> >       (1)  the E2E RSVP reservation is a per-flow reservation where
>> the
>> >            flow is characterized by the usual 5-tuple
>> >       (2)  the E2E reservation is an aggregate reservation for
>> multiple
>> >            flows as described in [RSVP-AGG] where the set=20
>> of flows is
>> >            characterized by the <source address,=20
>> destination address,
>> >            DSCP>
>> >       (3)  the E2E reservation is a reservation for an=20
>> IPSec protected
>> >            flow. For example, where the flow is=20
>> characterized by the
>> >            <source address, destination address, SPI> as=20
>> described in
>> >            [RSVP-IPSEC]
>> >       (4)  the E2E reservation is an aggregate reservation for
>> multiple
>> >            flows and where the set of flows are protected by IPSec
>> >       (5)  the E2E RSVP reservation is itself an RSVP-TE=20
>> reservation
>> >            for an E2E TE tunnel, so that LSP Hierarchy is achieved
>> >            [LSP-HIER]
>> > "
>> >=20
>> > I believe (2) would be the case you are refering to, right?
>> >=20
>> > Cheers
>> >=20
>> > Francois
>> >=20
>> > >>
>> > >> Thanks,
>> > >>
>> > >> John
>> > >>
>> > >> John Drake
>> > >> Boeing Satellite Systems
>> > >> 2300 East Imperial Highway
>> > >> El Segundo, CA 90245
>> > >> john.e.drake2@boeing.com
>> > >> (412) 370-3108
>> > >>
>>=20

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Fri Apr  8 14:49:33 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22012;
	Fri, 8 Apr 2005 14:49:33 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJygi-0005Lp-RP; Fri, 08 Apr 2005 14:58:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJyXD-0000FG-Eg; Fri, 08 Apr 2005 14:48:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJyXA-0000FB-36
	for tsvwg@megatron.ietf.org; Fri, 08 Apr 2005 14:48:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21966
	for <tsvwg@ietf.org>; Fri, 8 Apr 2005 14:48:46 -0400 (EDT)
Message-Id: <200504081848.OAA21966@ietf.org>
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJyfx-0005LC-Ku
	for tsvwg@ietf.org; Fri, 08 Apr 2005 14:57:54 -0400
Received: from localhost ([127.0.0.1] helo=psg.com)
	by psg.com with esmtp (Exim 4.44 (FreeBSD))
	id 1DJyX2-0008sX-HC; Fri, 08 Apr 2005 18:48:40 +0000
To: tsvwg@ietf.org
Date: Fri, 08 Apr 2005 11:48:39 -0700
From: Allison Mankin <mankin@psg.com>
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 0807e85f6792b2e267100df15b13cd9b
Cc: jon.peterson@neustar.biz, mankin@psg.com
Subject: [Tsvwg] IETF 62 Proceedings - TSVWG meeting (can be updated)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mankin@psg.com
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 1.5 (+)
X-Scan-Signature: 441502cf25997484ff0b8b79626c6b69


Transport Area WG (tsvwg)

Monday, March 7 at 1530-1730
=============================

CHAIRS:	Allison Mankin <mankin@psg.com> 
        Jon Peterson   <jon.peterson@neustar.biz>

Matt Zekauskas acted as scribe and produced these minutes.
Thank you to Matt for the usual excellent reporting.

A prize to the first person who finds the message about
Paris hidden in the minutes below (by this co-chair).

AGENDA
  Charter Discussion (chairs)
  Quickstart Update (Sally Floyd) (5 mins)
   draft-amit-quick-start-04.txt
  RSVP over MPLS-TE/DS-TE (Bruce Davie) (10 mins)
    draft-lefaucheur-rsvp-dste-01.txt
  RSVP IPSec (Bruce Davie) (10 mins)
    draft-lefaucheur-rsvp-ipsec-00.txt
  SCTP Chunk Authentication and Threats (Michael Tuexen) (20 mins)
    draft-tuexen-sctp-auth-chunk-03.txt
    draft-stewart-tsvwg-sctpthreat-02.txt
  SCTP Implementer's Guide (Randall Stewart) (10 mins)
    draft-ietf-tsvwg-sctpimpguide-13.txt
  TCP MIB (Matt Mathis) (10 mins)
    draft-ietf-tsvwg-tcp-mib-extension-06.txt
  Real-time Congestion Notification (Jozef Babiarz) (10 mins)
    draft-babiarz-tsvwg-rtecn-03.txt
  Diffserv Service Class (Kwok Ho Chan) (10 mins)
    draft-ietf-tsvwg-diffserv-service-classes-00.txt
  Diffserv Service Class Aggregation (Kwok Ho Chan) (10 mins)
    draft-chan-tsvwg-diffserv-class-aggr-01.txt
  MLPP Update (Fred Baker/James Polk) (15 mins)
    draft-ietf-tsvwg-mlpp-that-works-00.txt
    draft-ietf-tsvwg-mlef-concerns-00.txt
    draft-ietf-tsvwg-rsvp-bw-reduction-00.txt
    draft-baker-tsvwg-vpn-signaled-preemption.02.txt



Quickstart Update (Sally Floyd)

Sally quickly reviewed Quickstart.  Quickstart IP option, requested
rate & TTL in SYN.  Routers may decrement request, and decrement
RTT if they understand.  SYNACK has RTT measurement and rate.  The
sender knows if all routers approve of the rate request.  There were
three main changes: the addition of a citation (discussion of router
algorithms), and a discussion of misbehaving middleboxes, and a section
on attacks on quickstart.

The citation is for a paper that evaluates a whole range of router algorithms,
from a minimum algorithm, to "extreme Quickstart", as well as a discussion
of how to size your bandwidth request at the start.

The attacks on Quickstart include attacking a router by bombarding it
with many packets with Quickstart requests (router can rate-limit);
Attack Quickstart itself by sending many requests that are not used
(again, the router must have a mechanism to limit requests); won't
hurt folks that don't want to use Quickstart.

If have a misbehaving middlebox, something that rewrites the IP TTL,
it will interfere with Quickstart (you can't tell if all routers
agree to the request).  There's no good answer to this one, it's
just noted in the draft.

Sally asked for feedback, and thinks it can be WGLC as experimental.
There were a couple of "ship it"s from the audience.  Jon said that
if no other feedback, will issue WGLC.

Allison said that they would like to see a couple of reviews from
the WG during WGLC on the mailing list.  Please contribute to
the value of the WGLC.





RSVP over MPLS-TE/DS-TE (Francois LeFaucheur) (10 mins)

The key change to the draft is a closer alignment with the LSP hierarchy
draft in the MPLS WG, which we agreed to do at the last meeting.

They requested feedback from MPLS WG. They got some feedback, but
at this stage, mostly suggestion for clarifications, nothing major.

An appendix was added for informational purposes.  A use case, how
the aggregation solution can fit together with a VOIP architecture.

The authors want to have accepted as a WG document; they feel it is
pretty stable now.

Jon asked for opinions.  Fred Baker and James Polk both said they thought
it should be a WG document.

Jon asked for a hum.
In favor of adopting: <major>
opposed:  <fewer>
Jon declared a consensus to adopt this document as a working group item.

Francois asked what were the concerns of those opposed.  Joe Touch
said that given silence of the room, individual submission seems in
order instead of a working group submission.  It's hard to say the
document came out of the WG, if there is no support.

Jon felt that there was substantial enough response to the hum that
it should be a WG item.  Any other opinions?

Joe commented that the apathy is deafening.

Allison proposed making a review group for RSVP.  TSVWG is a big catch-all
group, and so there can be a majority that doesn't care.  However, we
don't want to do a lot of work in an ad-hoc manner.  RSVP also has some
legacy issues, and Allison isn't comfortable spinning up a WG for this.

In the use of this review group, we can do better than the
not long enough face-to-face meeting sessions and times.
Presentations have been more devoted to discussion of
apathy than necessarily getting at the needed comment and
review so one hopes that a review group will elicit the
in depth consideration that is sought, while also 
sending onto the mailing list the public results in summary,
very promptly.  If this is useful, we might choose to create
in addition review groups for other topics, for instance for the
next up SCTP implementation guide.   Rsvps for rsvp group a moi...

People that are interested in working on RSVP should send a message to
the chairs.  There are a lot of RSVP workers around, some from NSIS.
This is not the best environment for active discussion, and we need
to improve.  So identify yourself in person over the next few
days or by email to the chairs.  The chairs will name an RSVP review
group of the active RSVP people, and get you activated.

Melinda Shore said that she wasn't apathetic; wasn't sure what to say except
"uh huh".  She thinks this work should be done.  Why?  To get through IESG,
has to go through WGLC.  There were calls of "not trues" from audience.

Joe wanted to know if there were any standards here, or was this document
informational?  He thought Allison's point was well taken; get a group
of people, and show that there is energy.  if so, then we can make a
decision about it being a working group document.  If no one reads
it except the authors, and there is no one to review the document
it shouldn't be here.

Tom Phelan said that he was not apathetic, not an author, and has
given lots of feedback to the authors.  Like Melinda, he didn't know
what to say except uhhuh.   

Francois noted that many others outside group have read the document
and commented on it.

Allison noted that there has been discussion both in past meetings and 
on the mailing list.  There are a lot of different topics in the group,
and an a RSVP discussion group is one way to move forward; she didn't think
there was a big problem.





RSVP IPSec (Francois LeFaucheur) (10 mins)

See slides.  Looking for aggregation solutions for RSVP, in the context
of IPSEC VPNs.  Hide and aggregate reservations on IPSEC tunnels, given
a core cloud that supports diffserv.

We want end-to-end RSVP reservations.  These must be hidden in core inside
IPsec tunnels.  But once you hide them, to support right e2e reservation,
need to reserve resource for aggregate traffic carried over the IPsec tunnels.

They thought problem was solved with existing RFCs - 2207 & 3175.  Looking
harder, that is not the case.  2207 is RSVP extensions for IPSec flows, but
it doesn't address aggregation.  3175 describes aggregation of RSVP.
However, it doesn't support IPSec between aggregator and deaggregator.
This draft: do both at same time.

Francois showed a picture, and a new packet format that has both bits of
information necessary. (See slides.)

The remaining open items:

* Add text delineating the responsibilities of aggregators & deaggregators.
  There are no specific issues, there is only some explanation needed.

* Add text about how to handle dynamic updates of security associations.  There
  may be an elegant solution: change the SPI to renew the association.  Give
  a mechanism to do it without deallocating and reallocating resources.
  Right now there is a discussion in the middle of the security section,
  and it needs to be moved.

This is new work, the authors would like feedback.  They would also like
to progress the work, hopefully here.

Allison asked if the authors had ever viewed the RSVP security analysis 
document from the NSIS group.  They should review it, and look at the
security piece.  2207 was done a while ago, and it's security review
might not be good enough.

Allison asked for the issues to be put onto the mailing list, and get
discussion going.




SCTP Chunk Authentication and Threats (Michael Tuexen) (20 mins)

The origin of document is a paper by T. Aura P. Nikander and G Camarillo
analyzing SCTP from protocol point of view, and looking at implementations.

Given that paper, we changed some things in the protocol, and listed these
threads in the ID, and added some other possible attacks.  Michael
then went through the threats at high level.

* Address camping or stealing.  Attacker guesses port number the victim will
  use next, and the victim must be multihomed.

  Path verification procedure in the implementation guide will prevent,
  and random port number selection makes it harder.

* Association hijacking.  Attacker must take over IP addresses.  Gets a
  VTAGs in cookie according to the original RFC 2960.
  Implementer's guide now requires what is in cookie are random numbers,
  not real tags, so vtags still protect against blind attacker.

* Association hijacking #2.  If application doesn't pay attention to restart,
  it doesn't realize endpoint may have changed.

  Pay attention to notifications.

* Bombing attack (1).  Trick server into sending packets to a victim.
  Only works if victim doesn't understand SCTP.  (If it did, it will
  send an ABORT.)  Server isn't paying attention to ICMP.  Attacker
  is also spoofing acknowledgements.

  The implementer's guide now says how to handle ICMP messages.
  If you get acks for data you have never sent, abort the association.
  Finally, do the path verification procedure to make sure the IP
  address is correct.

* Bombing II.  Send INIT give address of victim.  Get cookie that
  you send to endpoint.  Now the path verification mechanism is itself
  used as an attack.

  Have a low number of heartbeats that send at any time.  Want a high number
  for preventing attacks, but here want to limit.  The Implementer's guide
  says to limit the hartbeats to a "maxburst" parameter.

* Association redirection.  Same info in two different places in the
  packet... but some implementations only use the common header.  Can
  get receiver of the packet into an unstable state.  The implementer's
  guide says to drop the packet if the numbers don't match.

In summary, some attacks are not possible if you implement new procedures.
Some can be limited in time  by tuning appropriate parameters.
The authors are interested in if someone has more attacks or ideas... such that
we can list and analyze.  They are not interested in attacks against 
implementations (bugs) all protocol related.  any questions...

Jon asked if Gonzalo (who has written a lot on SCTP) thinks it is good.  He
gave it a thumbs up :)





Next Michael turned to the chunk authentication draft.

An SCTP extension on dynamic IP (LIP) has been stable for 2 years,  but 
not progressed due to security concerns.  This draft is the missing
security part.

With LIP one can change the address of an association.  This draft
provides a mechanism to ensure that chunks have been sent from an
endpoint that you think they came from.  At the beginning of the
SCTP association, exchange some material so can verify.  This does
not address man-in-the-middle attacks from the beginning of the
connection (but that is true without LIP too).  LIP will be required
to use this extension.  (See slides.)

Michael asked if we can we adopt this draft.  It is needed to progress
the other document.  There were no comments.

Jon asked for a hum, in favor of adoption as an official working group
document.
  <moderate>
opposed?
  <none>

Jon declares consensus (within room) to adopt.




SCTP Implementer's Guide (Randall Stewart) (10 mins)

There are two outstanding issues.  First, one that is just
on the implementer's list: PPID field, and text change for byte order.
There was lots of discussion, and we have a wording proposal.
Second, Armando and Randy (Stewart) were supposed to put in a note
regarding Karn's algorithm and RTT.  Doing that now.

After both of these go in it's ready for WGLC.  It is an informational
document.  Original idea with Scott Bradner, is that it's a way forward
to get a 2960bis.  Start up a bis once this gets into the RFC Editor's
queue.

We'd like to set up some RFC2960bis ground rules.  It's up to the ADs,
but what we'd prefer, is that when we open up the bis (after the implementer's
guide is in the RFC Editor's queue), only changes in the implementer's
guide are applied to 2960.  E.g.: wording, missed references to
adler-32 checksum.  But no field day on let's add "X".
At end result would be obsolete 2960 and 3309 (the checksum
change), and the new draft would cycle back at Proposed.
We would move it forward after a couple of more interops (but
not until the implementer's guide is in the RFC Editor's queue).

Jon felt that, speaking personally, it was a well thought out way
to go forward.  Randy said he had lived through three WGLC and
three IESG LC, and he doesn't want to do it again.

Jon said that if there are any outstanding issues, get them to Randy
quickly.




TCP ESTATS MIB (Matt Mathis) (10 mins)

Matt reviewed the motivation for the MIB.

TCP already measures lots of stuff, and knows where bottlenecks are.
We added explicit instrumentation on what causes TCP to stop sending data
controls to support useful workarounds.  The big motivation is a
hard end-to-end diagnostic problem.  With TCP, symptoms scale with
RTT.  Tests in local paths pass, move to longer paths and they can fail.
This leads to false logic and lots of "buck passing".
The ESTATS MIB would let you rescale properties of short path to longer path.
(See slides for details.)

The latest revision is 06.  We haven't changed details of objects,
but did change the structure of the MIB.  There are three sets
of required variables:
 * state vars
 * performance instrumentation
 * first tier diagnostic instrumentation

There are also three sets of optional variables (focus on where problems are).
 * path (loss, reordering, dup, etc)
 * stack (impact and state of control algs)  e.g. for cwnd validation
 * app (is app stalling or tcp?)

And a little table of writeable controls
 * limit cwnd and limit rwind: can do instead of starving tcp for buffer space.
     (starving: interferes with recovery alg, retrans, and app that doesn't
      have stable perf (eg disk seeks causing dry spells)
 * ssthresh: for slow-start.  like limited sstart.

The TCP roadmap was helpful in this rewrite.

The big open tech issue:  there have been two Industrial implementers
looking at the MIB.  They have commented that there is too
much required, that may make it unimplemented in practice.
It's easy to juggle variables between tables.

There are also SMI representation issues.  We need help - the duration
object has proven problematic.  Want high precision for short flows.
MIB uses 0 based counters.  All counters start at O; can always look
at stats,  but then need duration object, which could be around for
weeks and months.  Need more than 32 bits of microseconds, anyway.
We also want to delta on duration, so compute rates.  That means no
time-of-day numbers in duration... because of discontinuities in clock
adjustments.

Allison: do you have an SNMP expert?  Should we ask for volunteers here?
Dan Romascanu volunteers.

In addition, big worry is if we have overlooked something obvious.
65 page MIB, and description is terse. Allison mentions that Dan Romascanu
has experience writing for extension in the future.

Fred Baker noted that he doesn't know anything about mibs, but if you have
a 65 page MIB, and descriptions are terse, this causes concern.  If I can
think of algorithm that can be described, and want... can mail in object.
Find myself wondering how many objects are specific to one implementation
or another, and not general.

Matt said they are pretty careful about that.  My background is BSD, and
this was done with Linux, so we believe it can be done at least twice.
As much as possible, objects are described in terms of standards (RFCs)
or TCP state vars.

Fred said that older TCPs had SRTT... more recent ones keep mean RTT
and variance in RTT. There are differences in way mean and variance
are calculated. Start high and average down, or start at initial RTT
of SYN/ACK, and end up with different things.  He's concerned.  How
standardize something like that?

The RTO calculation is on standards track, the MIB refers to that RFC. 
Ones that do something different are not compliant.

Matt is getting tired of this project; he will get more implementer's
experience, and get MIB doctor review, and hopes to have WGLC sometime
this summer.

Allison thought that we need MIB advice right now.  We've go a volunteer
to help with MIB formalisms;  do that in parallel with additional 
implementers and researchers.  There is a formal thing called
"MIB doctor review", which happens after WGLC; a second round.
So, take Dan's advice now, and go through a round of MIB formalism
first.

There were no other comments.






Real-time Congestion Notification (Jozef Babiarz) (10 mins)

Jozef started with a quick status update.  Sally is reviewing.
The semantics have been changed to align with 3168.  Added
a token bucket example, but it is an example; vendors are
free to use whatever they want for marking.  A description
of ECN marking behavior has been added.  A description of
mis-marking or cheating detection was added.

Jozef then compared 3168 semantics to what is proposed in
this draft.  (See slides.)  Two levels of congestion versus
1 level in 3168.  Use a real-time measurement technique to
detect congestion, versus AQM in 3168.

The next steps include cleaning up the text so that ECN semantics
are uniformly described; describe how ECN capable and non-ECN
capable endpoints interact; address how real-time inelastic
ECN-capable flow will react when it encounters a non-diffserv
router that supports 3168.

Looking for feedback and comments.

David Black volunteered to be a reviewer.  This draft is related to
trouble he's making in NSIS.  NSIS has draft that is proposing to
signal and react to congestion.  He thinks the use cases are RT,
but it's not clear.  ECN is a candidate mechanism for what they want to do,
and this may be related.  The draft is the RMD draft in NSIS.  Look
for the congestion signaling support in it.  Second Sally's comment:
figuring  out how this works when you have just 3168 in a router
is crucial.

Sally followed up, and said she needed to get back to an old chore,
writing an ID for requirements for alternate semantics to ECN.
There have been a number of proposals.
Think that the requirements are one of
(1) only deployable in closed environment (and not safe for general use)
(2) provide some mechanism that makes sure that traffic that requires
    alternate ECN semantics only encounters routers that support semantics
    (perhaps something like Quickstart)
(3) if traffic happens to encounter older router 3168... that the end node
    response is TCP-friendly.

Colin Perkins noted that a companion draft was mentioned that tried to
define an RTP payload format for ECN.  Will that go to AVT, or discuss here.

Jozef was not planning to bring the draft forward at this time; he wants to
"socialize it" and decide.  If there is interest, let's talk offline.
Colin mentioned that he was AVT co-chair.  He wanted to make sure that
it was reviewed by people that understood RTP as well as the TSV
community.

Brian Carpenter, as the guardian of the "diffserv flame", said that
way the draft is written it is not immediately apparent that it is
intimately associated with diffserv; but the draft only makes sense
in a diffserv context.  The presumption is that EF DS is being used
for this traffic.  That's part of the mechanism for knowing that it is
not regular ECN.  However, it could also could be a new PHB
(association of a diffserv codepoint with the new ECN behavior).  The
discussion of that issue should be in this draft, and if you can run
this simultaneously with EF PHB and no ECN.  It gets complicated needs
a discussion.  Also realize that we mucked around with transport
philosophy in DS... the TOS byte doesn't exist.  If David becomes a
reviewer, he would find that.

Gorry Fairhust didn't quite get a strong case for 2 levels, which
seems to be main point.  Is there a use case?  Jozef said that the
companion draft describes how to use it for admission control.
There are a bunch of uses:  admission control, calls with high precedence,
preemption, ... and we felt that 2 levels would address.   Perhaps
we need text to say how someone would use this if they only 
want one level.

Fred Baker asked if Jozef had followed a comment related to this
that he made on the mailing list.  Jozef said that he got part,
had a partial response, and wanted to talk. Fred said that he
was wondering how to use this in a world with different people
having different policies.  It gives us a measurement, but what
do we do with the measurement.  It may be that someone else needs
to do something -- a different SIP proxy, or in some different space.
It's not clear how the application can be depended on to handle that.
This is something that draft needs to go into, and not just say 
"application's problem".  Jozef asked if it's more appropriate for
a separate draft, describing use.  There is mechanism here.  Policy
will depend on the application, and how to use.  This needs to
be stated and guidance given, but a separate draft seems more appropriate.

Fred thought that might be, but RFC 3247 has updates to EF to make
it predictable.  If traffic is experiencing marks, predictability
goes away.  Perhaps a different draft, or an appendix, but there
must be guidance for real applications.

James Polk agreed.  You've mentioned that one or more of these indications
could provide for session pre-emption.  How?  Jozef stated that the marking
is passed to the end points.   They can send to the network manager controlling
preemption.  Flows indicate that they have reached the 2nd level of congestion.
The manager can select those flows, and check policy.  If they can be 
preempted, then they can be removed.

James asked if a interface has 1000 flows, and reaches capacity, is this
second level?  If all those flows are marked, all endpoints may react at
the same time.  Tell server to tell router?

Jozef says that one way with a centralized manager that gets all these,
and it can then decide which to kill.

David said that is exactly where NSIS RMD is headed; we need to rationalize
and do it once.

Stephen Norys from BT had another question about 2 levels.  In particular,
how do you cope with toggling between levels?  If the algorithm is
vendor dependent; different vendors could produce different answers,
and the stream may switch back and forth between the two levels.
Think you want some kind of ramp effect, rather than just 2 levels.

Georgios Karagiannis, an author of the NSIS draft resource management
in diffserv:  Related to David's remark... on Thursday we will discuss
different alternatives, only one of them is this one.

Allison noted that it is reasonable for people to go to NSIS on Thursday. 
It would be good to have more discussion.  This is only part of the RMD work.

Resolved:  Jozef and the RMD folks are to talk about their work's 
potential overlap.





Diffserv Service Class (Kwok Ho Chan) (10 mins)

This is the fourth version, but first as WG item.  The notion of
administrative service classes has been removed; the network control
class (because of the first change) is now just routing and network control,
everything else is just a standard class; the multimedia conferencing
discussion changed from "elastic flows" to rate-adaptive flows, since
they are really inelastic flows that can change rate; the ring clipping
discussion has been moved to the appendix.  Updated references.

The authors feel all outstanding issues have been resolved, and
would like to start WGLC.

No comments.

Allison asked for the opinion of group on this, by a hum.
Jon and Allison reserve right to review it prior to WGLC,
because they haven't done the chairs' review yet.  

Those that support WGLC at this time for this document, which
has been at four or five meetings now, please hum:
<loud>

Those that don't support, or oppose it, please hum:
<none>

Allison declares consensus towards moving to LC
good.  Will review it, and look towards moving it forward.





Diffserv Service Class Aggregation (Kwok Ho Chan) (10 mins)

This is an extension of the last draft: how to aggregate service
classes if you don't need detail.

Want to allow less-granular treatment where not needed, but preserve
end-to-end notion of service requirements that application wants.
After discussions, think four treatment aggregates are the right number.
Network control, real time, assured elastic, and elastic.

Would like feedback on the number, and the names.

The draft would provide guidance as to how perform aggregation,
and could be used as a foundation for indications between providers.
Not sure how yet...

See slides for detail.

Next steps are to cleanup guidelines on aggregation, and add a discussion
about using MPLS to express aggregates.  We would like comments back.

Jon said it would be good to see mailing list discussion.






MLPP Update (Fred Baker/James Polk) (15 mins)

Four drafts.  

First, the MLEF concerns draft has been posted as a WG document
pursuant to discussion last time.  This changed the draft handle only.

Second, our MLPP proposal which is RSVP based.  We did a minor update
and submitted as a WG draft.  There were errors in the appendix with
respect to SIP call flows; they have been fixed.  Other than that
it's the same.

Third, at last meeting, James talked about RSVP bandwidth reduction thing.
This identified a bug in RFC 3181 when it comes to dealing with aggregate
reservations.   If I need to preempt call within reservation, it has me
tear down and set up with new number.  This has a giant hole...
this draft suggests that one simply reduce bandwidth.  "accept if doesn't
exceed X", and the endpoint changes codec or whatever is the right thing.
This draft considers backwards compatibility.

Fourth, the last draft, is a use case for bw reduction thing.
A VPN network with multiple levels of VPNing.  This is still
an individual submission.    The draft posits that VPN router
might be two boxes.  Talk about what crosses the private interface
between them.


The other 3 pretty sure about.  This one needs work; dinner tomorrow
night is a discussion of this draft with others that are interested.

we want:

We want the first three to move forward.
mlef-concerns -> informational
mlpp that works: informational or BCP
bw-reduction -> proposed.  it's a protocol.

As to the last one... If the way we get people to read & comment
is to go to last call, I would like to go to last call.  We
want people to read & comment.  So LC to informational?

Mike Pierce: object vehemently to MLEF concerns going anywhere.
The MLEF concerns document is to object to and provide comments on draft
that myself and Steve Silverman wrote on MLEF.  We have seen it..
and responded to it two years ago.  We have made changes.
To show you how bad it is... look in the draft reference section.
It references the Jan. 2004 version that has concerns with.
However, the MLEF document has been revised twice, and this draft
doesn't reference updates, much less recognize modifications made to MLEF.

The MLEF concerns actual title is
"MLEF without capacity admission does not satisfy MLPP requirements",
but we said that from the beginning.
The version from way back when that was referred to... included
explicit statement that it would not work without call admission control.
We strengthened that statement.  Yet this doc keeps arguing that point.

In addition, this document contains a large number of technical inaccuracies.
For example, g709 increasing throughput in face of loss.
It is theoretically possible for a codec to do that, but this one doesn't.
It talks about having 3 specific rates...

Jon: don't want to take exception, but this is a more detailed discussion
than we have time for.

But we need to have the discussion.  Mike objects to the document
proceeding, and is not sure how it to WG status; his recollection is
that there was no agreement.

Jon believe there was consensus, and the first time that Mr. Baker
spoke to us about it, there was strong consensus for this work.

James Polk: to last point, about ILBC not being variable... 
Alan Durek wrote part of that.  He is the author of that protocol.
He is who helped write section.

Mike said it's not in rfcs, though.

Scott Bradner agreed that this particular document that was reviewed
at ieprep was a very important document in it's day.  However, he's
not sure if needs to be RFC, unless it is recast as
"concerns about non-admission controlled attempts at priority".
It is an instructive document, but not sure it deals with the alternatives
on table today.  Would agree that it should fade out, but strongly support
moving the others forward.

Jon asked for Fred to comment.  Fred stated that when the
document was first published, he didn't expect it to be an RFC.
He could go either way.

James said that one of reasons why we regenerated  this six months
ago or so is that we had a couple other customers, other than us government,
that wanted to promote diffserv-based QoS using that mechanism.  So we wanted
to have the concerns documented.  He agreed with Scott that the
scope ought to be broader.

Fred said that he heard that if this document is to become an RFC at all,
the working group must tell him what to see.

Jon said that he believed the working group requested that rather than
document the problems with a specific proposal, speak to general design
principles that are objectionable.

Scott agreed.

Jon noted that we are out of time; clearly there should be more discussion
on issues.  Jon invited Mike to bring technical objections to list.  Jon
then declared the meeting to be closed.



------- End of Forwarded Message


_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Fri Apr  8 16:00:16 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06874;
	Fri, 8 Apr 2005 16:00:15 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJznA-00035T-Cr; Fri, 08 Apr 2005 16:09:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJzRn-00071N-Tg; Fri, 08 Apr 2005 15:47:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJzRm-00071A-H5
	for tsvwg@megatron.ietf.org; Fri, 08 Apr 2005 15:47:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02210
	for <tsvwg@ietf.org>; Fri, 8 Apr 2005 15:47:16 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJzab-00016w-1h
	for tsvwg@ietf.org; Fri, 08 Apr 2005 15:56:25 -0400
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 08 Apr 2005 12:47:08 -0700
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j38Jl6ZV006704;
	Fri, 8 Apr 2005 12:47:07 -0700 (PDT)
Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com
	[171.68.225.134]) by wells.cisco.com (8.8.6
	(PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id MAA21147;
	Fri, 8 Apr 2005 12:47:05 -0700 (PDT)
Message-Id: <4.3.2.7.2.20050408144050.03444f00@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 08 Apr 2005 14:47:05 -0600
To: mankin@psg.com, tsvwg@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Tsvwg] IETF 62 Proceedings - TSVWG meeting (can be
  updated)
In-Reply-To: <200504081848.OAA21966@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 1.9 (+)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198
Cc: jon.peterson@neustar.biz, mankin@psg.com
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 6ba8aaf827dcb437101951262f69b3de

Chairs

I'm not sure I agree with the minutes regarding the (heated) MLEF Concerns 
discussion. I believe I agreed with Scott when he said this is a worthy 
document to move forward *IF* it were broadened to a larger problem area 
than just the US Gov's desire for MLEF for MLPP networks.

I believe what was agreed was that I (with Fred) would rewrite the Intro 
and conclusion sections of the ID to make its applicability wider, but that 
the core of the ID was on the right track. Obviously there will need to be 
a review of the core of the ID if the rewritten sections change what should 
be in the core of the doc.

comments

BTW - you hid the Paris comment well, as I haven't found it yet

At 11:48 AM 4/8/2005 -0700, Allison Mankin wrote:

>Transport Area WG (tsvwg)
>
>Monday, March 7 at 1530-1730
>=============================
>
>CHAIRS: Allison Mankin <mankin@psg.com>
>         Jon Peterson   <jon.peterson@neustar.biz>
>
>
>MLPP Update (Fred Baker/James Polk) (15 mins)
>
>Four drafts.
>
>First, the MLEF concerns draft has been posted as a WG document
>pursuant to discussion last time.  This changed the draft handle only.
>
>Second, our MLPP proposal which is RSVP based.  We did a minor update
>and submitted as a WG draft.  There were errors in the appendix with
>respect to SIP call flows; they have been fixed.  Other than that
>it's the same.
>
>Third, at last meeting, James talked about RSVP bandwidth reduction thing.
>This identified a bug in RFC 3181 when it comes to dealing with aggregate
>reservations.   If I need to preempt call within reservation, it has me
>tear down and set up with new number.  This has a giant hole...
>this draft suggests that one simply reduce bandwidth.  "accept if doesn't
>exceed X", and the endpoint changes codec or whatever is the right thing.
>This draft considers backwards compatibility.
>
>Fourth, the last draft, is a use case for bw reduction thing.
>A VPN network with multiple levels of VPNing.  This is still
>an individual submission.    The draft posits that VPN router
>might be two boxes.  Talk about what crosses the private interface
>between them.
>
>
>The other 3 pretty sure about.  This one needs work; dinner tomorrow
>night is a discussion of this draft with others that are interested.
>
>we want:
>
>We want the first three to move forward.
>mlef-concerns -> informational
>mlpp that works: informational or BCP
>bw-reduction -> proposed.  it's a protocol.
>
>As to the last one... If the way we get people to read & comment
>is to go to last call, I would like to go to last call.  We
>want people to read & comment.  So LC to informational?
>
>Mike Pierce: object vehemently to MLEF concerns going anywhere.
>The MLEF concerns document is to object to and provide comments on draft
>that myself and Steve Silverman wrote on MLEF.  We have seen it..
>and responded to it two years ago.  We have made changes.
>To show you how bad it is... look in the draft reference section.
>It references the Jan. 2004 version that has concerns with.
>However, the MLEF document has been revised twice, and this draft
>doesn't reference updates, much less recognize modifications made to MLEF.
>
>The MLEF concerns actual title is
>"MLEF without capacity admission does not satisfy MLPP requirements",
>but we said that from the beginning.
>The version from way back when that was referred to... included
>explicit statement that it would not work without call admission control.
>We strengthened that statement.  Yet this doc keeps arguing that point.
>
>In addition, this document contains a large number of technical inaccuracies.
>For example, g709 increasing throughput in face of loss.
>It is theoretically possible for a codec to do that, but this one doesn't.
>It talks about having 3 specific rates...
>
>Jon: don't want to take exception, but this is a more detailed discussion
>than we have time for.
>
>But we need to have the discussion.  Mike objects to the document
>proceeding, and is not sure how it to WG status; his recollection is
>that there was no agreement.
>
>Jon believe there was consensus, and the first time that Mr. Baker
>spoke to us about it, there was strong consensus for this work.
>
>James Polk: to last point, about ILBC not being variable...
>Alan Durek wrote part of that.  He is the author of that protocol.
>He is who helped write section.
>
>Mike said it's not in rfcs, though.
>
>Scott Bradner agreed that this particular document that was reviewed
>at ieprep was a very important document in it's day.  However, he's
>not sure if needs to be RFC, unless it is recast as
>"concerns about non-admission controlled attempts at priority".
>It is an instructive document, but not sure it deals with the alternatives
>on table today.  Would agree that it should fade out, but strongly support
>moving the others forward.
>
>Jon asked for Fred to comment.  Fred stated that when the
>document was first published, he didn't expect it to be an RFC.
>He could go either way.
>
>James said that one of reasons why we regenerated  this six months
>ago or so is that we had a couple other customers, other than us government,
>that wanted to promote diffserv-based QoS using that mechanism.  So we wanted
>to have the concerns documented.  He agreed with Scott that the
>scope ought to be broader.
>
>Fred said that he heard that if this document is to become an RFC at all,
>the working group must tell him what to see.
>
>Jon said that he believed the working group requested that rather than
>document the problems with a specific proposal, speak to general design
>principles that are objectionable.
>
>Scott agreed.
>
>Jon noted that we are out of time; clearly there should be more discussion
>on issues.  Jon invited Mike to bring technical objections to list.  Jon
>then declared the meeting to be closed.
>
>
>
>------- End of Forwarded Message
>
>
>_______________________________________________
>tsvwg mailing list
>tsvwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/tsvwg


cheers,
James

                                *******************
                 Truth is not to be argued... it is to be presented

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Fri Apr  8 16:14:14 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08599;
	Fri, 8 Apr 2005 16:14:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DK00g-00044N-4q; Fri, 08 Apr 2005 16:23:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJzrj-0007SN-UP; Fri, 08 Apr 2005 16:14:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJzrh-0007SI-Ru
	for tsvwg@megatron.ietf.org; Fri, 08 Apr 2005 16:14:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08580
	for <tsvwg@ietf.org>; Fri, 8 Apr 2005 16:14:04 -0400 (EDT)
Message-Id: <200504082014.QAA08580@ietf.org>
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DK00X-00043y-7z
	for tsvwg@ietf.org; Fri, 08 Apr 2005 16:23:13 -0400
Received: from localhost ([127.0.0.1] helo=psg.com)
	by psg.com with esmtp (Exim 4.44 (FreeBSD))
	id 1DJzrg-000KqV-1c; Fri, 08 Apr 2005 20:14:04 +0000
To: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Tsvwg] IETF 62 Proceedings - TSVWG meeting (can be updated) 
In-reply-to: Your message of Fri, 08 Apr 2005 14:47:05 -0600.
	<4.3.2.7.2.20050408144050.03444f00@localhost> 
Date: Fri, 08 Apr 2005 13:14:04 -0700
From: Allison Mankin <mankin@psg.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: tsvwg@ietf.org, jon.peterson@neustar.biz, mankin@psg.com
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mankin@psg.com
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9

James,

> I'm not sure I agree with the minutes regarding the (heated) MLEF Concerns 
> discussion. I believe I agreed with Scott when he said this is a worthy 
> document to move forward *IF* it were broadened to a larger problem area 
> than just the US Gov's desire for MLEF for MLPP networks.
> 
> I believe what was agreed was that I (with Fred) would rewrite the Intro 
> and conclusion sections of the ID to make its applicability wider, but that 
> the core of the ID was on the right track. Obviously there will need to be 
> a review of the core of the ID if the rewritten sections change what should 
> be in the core of the doc.

> comments
> 

I think the minutes words are *consistent with your recollection
of not killing the draft, but broadening its applicability.

While doing that, it needs to have some specific technical points 
in the interior addressed as well -
Mike was supposed to send specific points to the list in
the form of a constructive document review.

But if others think we need the minutes to say so (instead of
just this email thread), we could add that "It was resolved James
would revise the draft to give it applicability to a larger problem
area, and to update it - in addition a constructive document review
was promised from Mike Pierce."

> BTW - you hid the Paris comment well, as I haven't found it yet

It's like a puzzle message, not really a comment.

Allison




_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Fri Apr  8 17:24:29 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13517;
	Fri, 8 Apr 2005 17:24:29 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DK16h-0007Sv-7V; Fri, 08 Apr 2005 17:33:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DK0uY-0005NF-9w; Fri, 08 Apr 2005 17:21:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DK0uU-0005N6-JZ
	for tsvwg@megatron.ietf.org; Fri, 08 Apr 2005 17:21:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13367
	for <tsvwg@ietf.org>; Fri, 8 Apr 2005 17:20:59 -0400 (EDT)
Received: from amer-mta01.csc.com ([20.137.2.247])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DK13I-0007Fu-NL
	for tsvwg@ietf.org; Fri, 08 Apr 2005 17:30:10 -0400
Received: from amer-gw09.csc.com (amer-gw09.csc.com [20.6.39.245])
	by amer-mta01.csc.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id
	j38LKmxZ007886; Fri, 8 Apr 2005 17:20:54 -0400 (EDT)
Subject: Re: [Tsvwg] IETF 62 Proceedings - TSVWG meeting (can be  updated)
To: jon.peterson@neustar.biz, mankin@psg.com, tsvwg@ietf.org, jmpolk@cisco.com
X-Mailer: Lotus Notes Release 5.0.11   July 24, 2002
Message-ID: <OF1328D80C.6375C64B-ON85256FDD.0074DF00-85256FDD.00754A71@csc.com>
From: Janet P Gunn <jgunn6@csc.com>
Date: Fri, 8 Apr 2005 17:19:25 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 6.5.3|September
	14, 2004) at 04/08/2005 05:21:06 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 0.8 (/)
X-Scan-Signature: d9238570526f12788af3d33c67f37625
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96





As an "interested observer", I definitely remember an agreement to remove
the direct references to Mike and Steve's document.

My notes at the time say:
"As expected, Mike Pierce objected vehemently to  "What's wrong with MLEF"
being a working group draft.  Scott suggested retitling it and rewording it
to address "what;'s wrong with addressing per hop behavior without
addressing call admission".  Everyone seemed satisfied with that."

Janet


----------------------------------------------------------------------------------------

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------




                                                                                                                                 
                      "James M. Polk"                                                                                            
                      <jmpolk                  To:      mankin@psg.com, tsvwg@ietf.org                                           
                      @cisco.com>              cc:      jon.peterson@neustar.biz, mankin@psg.com                                 
                      Sent by:                 Subject: Re: [Tsvwg] IETF 62 Proceedings - TSVWG meeting (can be  updated)        
                      tsvwg-bounces                                                                                              
                                                                                                                                 
                                                                                                                                 
                      04/08/2005 04:47                                                                                           
                      PM                                                                                                         
                                                                                                                                 
                                                                                                                                 




Chairs

I'm not sure I agree with the minutes regarding the (heated) MLEF Concerns
discussion. I believe I agreed with Scott when he said this is a worthy
document to move forward *IF* it were broadened to a larger problem area
than just the US Gov's desire for MLEF for MLPP networks.

I believe what was agreed was that I (with Fred) would rewrite the Intro
and conclusion sections of the ID to make its applicability wider, but that

the core of the ID was on the right track. Obviously there will need to be
a review of the core of the ID if the rewritten sections change what should

be in the core of the doc.

comments

BTW - you hid the Paris comment well, as I haven't found it yet

At 11:48 AM 4/8/2005 -0700, Allison Mankin wrote:

>Transport Area WG (tsvwg)
>
>Monday, March 7 at 1530-1730
>=============================
>
>CHAIRS: Allison Mankin <mankin@psg.com>
>         Jon Peterson   <jon.peterson@neustar.biz>
>
>
>MLPP Update (Fred Baker/James Polk) (15 mins)
>
>Four drafts.
>
>First, the MLEF concerns draft has been posted as a WG document
>pursuant to discussion last time.  This changed the draft handle only.
>
>Second, our MLPP proposal which is RSVP based.  We did a minor update
>and submitted as a WG draft.  There were errors in the appendix with
>respect to SIP call flows; they have been fixed.  Other than that
>it's the same.
>
>Third, at last meeting, James talked about RSVP bandwidth reduction thing.
>This identified a bug in RFC 3181 when it comes to dealing with aggregate
>reservations.   If I need to preempt call within reservation, it has me
>tear down and set up with new number.  This has a giant hole...
>this draft suggests that one simply reduce bandwidth.  "accept if doesn't
>exceed X", and the endpoint changes codec or whatever is the right thing.
>This draft considers backwards compatibility.
>
>Fourth, the last draft, is a use case for bw reduction thing.
>A VPN network with multiple levels of VPNing.  This is still
>an individual submission.    The draft posits that VPN router
>might be two boxes.  Talk about what crosses the private interface
>between them.
>
>
>The other 3 pretty sure about.  This one needs work; dinner tomorrow
>night is a discussion of this draft with others that are interested.
>
>we want:
>
>We want the first three to move forward.
>mlef-concerns -> informational
>mlpp that works: informational or BCP
>bw-reduction -> proposed.  it's a protocol.
>
>As to the last one... If the way we get people to read & comment
>is to go to last call, I would like to go to last call.  We
>want people to read & comment.  So LC to informational?
>
>Mike Pierce: object vehemently to MLEF concerns going anywhere.
>The MLEF concerns document is to object to and provide comments on draft
>that myself and Steve Silverman wrote on MLEF.  We have seen it..
>and responded to it two years ago.  We have made changes.
>To show you how bad it is... look in the draft reference section.
>It references the Jan. 2004 version that has concerns with.
>However, the MLEF document has been revised twice, and this draft
>doesn't reference updates, much less recognize modifications made to MLEF.
>
>The MLEF concerns actual title is
>"MLEF without capacity admission does not satisfy MLPP requirements",
>but we said that from the beginning.
>The version from way back when that was referred to... included
>explicit statement that it would not work without call admission control.
>We strengthened that statement.  Yet this doc keeps arguing that point.
>
>In addition, this document contains a large number of technical
inaccuracies.
>For example, g709 increasing throughput in face of loss.
>It is theoretically possible for a codec to do that, but this one doesn't.
>It talks about having 3 specific rates...
>
>Jon: don't want to take exception, but this is a more detailed discussion
>than we have time for.
>
>But we need to have the discussion.  Mike objects to the document
>proceeding, and is not sure how it to WG status; his recollection is
>that there was no agreement.
>
>Jon believe there was consensus, and the first time that Mr. Baker
>spoke to us about it, there was strong consensus for this work.
>
>James Polk: to last point, about ILBC not being variable...
>Alan Durek wrote part of that.  He is the author of that protocol.
>He is who helped write section.
>
>Mike said it's not in rfcs, though.
>
>Scott Bradner agreed that this particular document that was reviewed
>at ieprep was a very important document in it's day.  However, he's
>not sure if needs to be RFC, unless it is recast as
>"concerns about non-admission controlled attempts at priority".
>It is an instructive document, but not sure it deals with the alternatives
>on table today.  Would agree that it should fade out, but strongly support
>moving the others forward.
>
>Jon asked for Fred to comment.  Fred stated that when the
>document was first published, he didn't expect it to be an RFC.
>He could go either way.
>
>James said that one of reasons why we regenerated  this six months
>ago or so is that we had a couple other customers, other than us
government,
>that wanted to promote diffserv-based QoS using that mechanism.  So we
wanted
>to have the concerns documented.  He agreed with Scott that the
>scope ought to be broader.
>
>Fred said that he heard that if this document is to become an RFC at all,
>the working group must tell him what to see.
>
>Jon said that he believed the working group requested that rather than
>document the problems with a specific proposal, speak to general design
>principles that are objectionable.
>
>Scott agreed.
>
>Jon noted that we are out of time; clearly there should be more discussion
>on issues.  Jon invited Mike to bring technical objections to list.  Jon
>then declared the meeting to be closed.
>
>
>
>------- End of Forwarded Message
>
>
>_______________________________________________
>tsvwg mailing list
>tsvwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/tsvwg


cheers,
James

                                *******************
                 Truth is not to be argued... it is to be presented

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg





_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Fri Apr  8 23:06:49 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05763;
	Fri, 8 Apr 2005 23:06:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DK6S1-0005Dm-An; Fri, 08 Apr 2005 23:16:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DK6Iq-0006Op-7e; Fri, 08 Apr 2005 23:06:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DK6HH-00066x-4r
	for tsvwg@megatron.ietf.org; Fri, 08 Apr 2005 23:04:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05603
	for <tsvwg@ietf.org>; Fri, 8 Apr 2005 23:04:53 -0400 (EDT)
Message-Id: <200504090304.XAA05603@ietf.org>
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DK6Q9-00056S-4a
	for tsvwg@ietf.org; Fri, 08 Apr 2005 23:14:06 -0400
Received: from localhost ([127.0.0.1] helo=psg.com)
	by psg.com with esmtp (Exim 4.44 (FreeBSD))
	id 1DK6HE-000L2C-Q7; Sat, 09 Apr 2005 03:04:52 +0000
To: tsvwg@ietf.org
Date: Fri, 08 Apr 2005 20:04:52 -0700
From: Allison Mankin <mankin@psg.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: Matthew Luckie <mjl@luckie.org.nz>
Subject: [Tsvwg] re: IETF 62 Proceedings - TSVWG meeting (can be updated)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mankin@psg.com
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906

Allison Mankin wrote:

> A prize to the first person who finds the message about
> Paris hidden in the minutes below (by this co-chair).

A number of people found there was a pretty obvious clue
to the location of the hidden message, the French phrase  
"Rsvps for rsvp group a moi.." in the very wordy paragraph 
on the RSVP review group.  But the actual message about Paris
mentions Paris, and it is hidden in the first letter of
each line of that paragraph.

Matthew Luckie wins a glass of wine in Paris (or next
IETF he makes it to) for finding it.  See the message.

Allison                

P.S. Think about joining the RSVP review group.  

_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


From tsvwg-bounces@ietf.org  Thu Apr 14 09:43:16 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12056;
	Thu, 14 Apr 2005 09:43:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DM4mo-0007tk-HE; Thu, 14 Apr 2005 09:53:38 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DM4az-00025D-UE; Thu, 14 Apr 2005 09:41:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DM4ay-00023W-Hn
	for tsvwg@megatron.ietf.org; Thu, 14 Apr 2005 09:41:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11765
	for <tsvwg@ietf.org>; Thu, 14 Apr 2005 09:41:06 -0400 (EDT)
Received: from atlrel7.hp.com ([156.153.255.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM4kh-0007mT-8N
	for tsvwg@ietf.org; Thu, 14 Apr 2005 09:51:28 -0400
Received: from taynzmail03.nz-tay.cpqcorp.net (taynzmail03.nz-tay.cpqcorp.net
	[16.47.4.103]) by atlrel7.hp.com (Postfix) with ESMTP id 127F71B8A3
	for <tsvwg@ietf.org>; Thu, 14 Apr 2005 09:41:04 -0400 (EDT)
Received: from kitche.zk3.dec.com (kitche2.zk3.dec.com [16.140.160.162])
	by taynzmail03.nz-tay.cpqcorp.net (Postfix) with ESMTP id B2C602336;
	Thu, 14 Apr 2005 09:41:03 -0400 (EDT)
Received: from galen.zko.hp.com by kitche.zk3.dec.com
	(8.11.1/1.1.27.5/27Oct00-1235PM)
	id j3EDf3d0001319747; Thu, 14 Apr 2005 09:41:03 -0400 (EDT)
From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: tsvwg@ietf.org
Content-Type: text/plain
Organization: Linux and Open Source Lab
Date: Thu, 14 Apr 2005 09:41:03 -0400
Message-Id: <1113486063.20830.105.camel@galen.zko.hp.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Subject: [Tsvwg] SCTP API Q: sctp_sendmsg and association id
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>,
	<mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit

Hello all

I was curious why was sctp_sendmsg() defined such that a user can't use
sctp association id instead of the destination address and port?

The current definition of sctp_sendmsg() as defined is sctpsocket draft
does not take association id as an argument, while sctp_recvmsg() can
return it as part of sctp_sndrcvinfo() structure.

I found that when writing cross-platform applications, it is easier to
use the library functions instead of system calls as it makes
portability simpler.  However, I found that this useful feature was
missing.

Additionally, sometimes it is much easier to track and use association
ids what sending and receiving messages instead of the address/port
pairs.  Also, on some implementaions, using association ID improves
performance when using a lot (1000+) associations on a single endpoint.

-vlad


_______________________________________________
tsvwg mailing list
tsvwg@ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg


