From tsvwg-bounces@ietf.org  Wed Dec  1 01:12:36 2004
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 BAA06040;
	Wed, 1 Dec 2004 01:12:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZNoQ-0007Yh-Ez; Wed, 01 Dec 2004 01:18:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZNez-00017g-9h; Wed, 01 Dec 2004 01:08:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZNbW-0007jW-UZ
	for tsvwg@megatron.ietf.org; Wed, 01 Dec 2004 01:04:46 -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 BAA05670
	for <tsvwg@ietf.org>; Wed, 1 Dec 2004 01:04:42 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZNgm-0007Px-5A
	for tsvwg@ietf.org; Wed, 01 Dec 2004 01:10:09 -0500
Received: from [70.212.14.123] (123.sub-70-212-14.myvzw.com [70.212.14.123])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id iB162pQ24204;
	Tue, 30 Nov 2004 22:02:51 -0800 (PST)
Message-ID: <41AD5E85.2030102@isi.edu>
Date: Tue, 30 Nov 2004 22:02:45 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Joe Touch <touch@ISI.EDU>
Subject: Re: [Tsvwg] multiaddressing
References: <6938661A6EDA8A4EA8D1419BCE46F24C0406092E@xch-nw-27.nw.nos.boeing.com>
	<20041130030000.GE9132@pun.isi.edu> <41AC2C4F.9050905@isi.edu>
In-Reply-To: <41AC2C4F.9050905@isi.edu>
X-Enigmail-Version: 0.86.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>, tsvwg@ietf.org,
        Janardhan Iyengar <iyengar@mail.eecis.udel.edu>,
        Ted Faber <faber@ISI.EDU>,
        Randall Stewart <randall@stewart.chicago.il.us>,
        Mark Allman <mallman@icir.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>
Content-Type: multipart/mixed; boundary="===============0415815896=="
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0415815896==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig6A4AF5C0E70D398CFAAD0F2A"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig6A4AF5C0E70D398CFAAD0F2A
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



Joe Touch wrote:
> 
> 
> Ted Faber wrote:
> ...
> 
>> Why *not* DNS?  It's a distributed replicated 1-to-many database.  It
>> already returns lists of network addresses associated with a string, and
>> there's a well-known API to get at those.  I don't understand the
>> additional dependency created here unless the endpoints were not
>> exchanging DNS names to begin with. 
> 
> 
> When DNS returning multiple RRs it doesn't mean they're on the same 
> host; they are just 'equivalent' in some fuzzy sense, e.g., replica 
> servers of a database, alternate gateways to a VPN, etc.

s/RRs/records in a reply/

I confused the first R with "rotation" (brain cloud). I'm referring to 
rotation of multiple A record replies, ala RFC1794, FWIW.

Joe

> There would need to be a different record to indicate records that go to 
> the same 'box' (i.e., we could call them WH for 'weak host').
> 
> Joe

--------------enig6A4AF5C0E70D398CFAAD0F2A
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iD8DBQFBrV6FE5f5cImnZrsRAi1NAJ4ybwm19DmpwaaJRNy39lkgDsIrOQCgyVNs
eFQxBcbtYfNBicOnsfqs1sA=
=YzBm
-----END PGP SIGNATURE-----

--------------enig6A4AF5C0E70D398CFAAD0F2A--


--===============0415815896==
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

--===============0415815896==--



From mailman-bounces@ietf.org  Wed Dec  1 08:04:37 2004
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 IAA25244
	for <tsvwg-archive@ietf.org>; Wed, 1 Dec 2004 08:04:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZUFG-00084F-1Q
	for tsvwg-archive@ietf.org; Wed, 01 Dec 2004 08:10:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZSSs-0007F8-Ud
	for tsvwg-archive@ietf.org; Wed, 01 Dec 2004 06:16:06 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: tsvwg-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.16863.1101897762.3553.mailman@lists.ietf.org>
Date: Wed, 01 Dec 2004 05:42:42 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit

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

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

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

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


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

Passwords for tsvwg-archive@ietf.org:

List                                     Password // URL
----                                     --------  
tsvwg@ietf.org                           xeowbe    
https://www1.ietf.org/mailman/options/tsvwg/tsvwg-archive%40ietf.org


From tsvwg-bounces@ietf.org  Wed Dec  1 12:23:06 2004
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 MAA29033;
	Wed, 1 Dec 2004 12:23:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZYHQ-0005KU-DE; Wed, 01 Dec 2004 12:28:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZXBV-0005NU-1i; Wed, 01 Dec 2004 11:18:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZUod-0006SF-6E
	for tsvwg@megatron.ietf.org; Wed, 01 Dec 2004 08:46:44 -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 IAA28807
	for <tsvwg@ietf.org>; Wed, 1 Dec 2004 08:46:40 -0500 (EST)
Received: from dpc674425142.direcpc.com ([67.44.25.142]
	helo=stewart.chicago.il.us)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZUtv-0000Nf-Cs
	for tsvwg@ietf.org; Wed, 01 Dec 2004 08:52:13 -0500
Received: from stewart.chicago.il.us (localhost [127.0.0.1])
	by stewart.chicago.il.us (8.12.9p2/8.12.8) with ESMTP id iB1DkM84016995
	for <tsvwg@ietf.org>; Wed, 1 Dec 2004 08:46:24 -0500 (EST)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <41ADCAC0.7000906@stewart.chicago.il.us>
Date: Wed, 01 Dec 2004 08:44:32 -0500
From: Randall Stewart <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: Re: [Tsvwg] multiaddressing
References: <5B58696DB20B9140AD20E0685C573A6404FDDA2E@xch-nw-09.nw.nos.boeing.com>
	<20041130210905.GG15528@pun.isi.edu>
In-Reply-To: <20041130210905.GG15528@pun.isi.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 963faf56c3a5b6715f0b71b66181e01a
Content-Transfer-Encoding: 7bit
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: 43317e64100dd4d87214c51822b582d1
Content-Transfer-Encoding: 7bit

Ted/All:

First I am removing all the "cc's and to's" I think we are
all on the list and I don't want to cause multiple copies to
be recieved...:-D

Now, I have kept silent on this for a while now trying to
contemplate my reply so that it might be consistent  and
grokable if thats possible :-D

I am not going to touch the mobility aspect of this since
I have never been a supporter of the use of the SCTP-ADDIP
document as a mobility crutch. The idea is interesting.. don't
get me wrong.. but the document was NOT intended for that purpose.
(Note also that if I remember right from my last peruseal of the
  IPR page both Siemens and Cisco have IPR in for use of
  transport protocols in mobility.. DCCP and SCTP.. might
  want to check that page if you are a fan of this concept).

So I will exclude mobility from my discussion of multi-addressing.
Maybe in the future we can do something for mobility.. but I thought
we did that with mobile IP, maybe working at the lower layers does
not always work.. I don't know  :-/

Now, why does SCTP have multiple addresses... (in
priority order)

1) Fault-tolerance - When the design team for SCTP worked
    on SCTP we wanted to be able to get a message from sender
    to receiver with as much fault tolerance as we could. This is
    why we had all transmissions going to alternates, which work
    by Armando Caro at the U-D has shown is ok, but for performance
    you are better to fast-retransmit to the same destination and
    only move timeout's to the alternates... which makes sense
    if you think about it :-D

2) Load-balancing - Yep, sigtran wanted that.. but we were told
    that we would need to take it out since not enough research
    had been done on it. And what they wanted it for is exactly
    what most apps I have ever worked on have wanted it for, throughput
    plain and simple.


Now, why did we get ADD-IP in the picture then? And why has
it been floating around since October of 2000??

Well the third item on the list for sigtran was to dynamically
add and delete the addresses. Why, because a sigtran association
was envisioned to be up for months and maybe even years without
coming down. So I have this wonderful fault tolerant server
and I plug in a new NIC card and do "ifconfig new-card some-address"
and I DON'T want to take down the association, instead I want it
to silently add to the existing association. And for IPV6 you have
the re-number case to deal with.. yeah I know they keep the
old address for a while.. but eventually it is un-useable .. so
having add-ip helps here too.. (remember the association is up
for a year or more...hopefully).. Thats the why, and
the agreement that was made is to spin it into a seperate draft
along with the PR-SCTP draft as well and work on them so that
we could at least get the base protocol out. Scott also arranged
for these drafts to move to TSV since sigtran was 'closing' :-> and
besides transport extensions are to be done in tsv.... at least
at the time (tcpm did not exist yet).

Now why has ADD-IP "treaded water"? Because we (the authors) realized
that there is a security issue with it. Its not that it has not been
implemented.. most every SCTP stack at the last inter-op supported
BOTH PR-SCTP(RFC3758) and ADD-IP.. and in fact,
more supported ADD-IP then PR-SCTP (and its been that way all along).

So whats the hold up? Security plain and simple...
how do I reasonably know that the  guy I started talking to is
the guy that sent me this add/delete IP address thingy?
We are now about throught that problem in that
the auth draft for SCTP (modeled after the pbk draft) adds the
needed security and ADD-IP will require the implementation
and use of the auth draft (of course users will probably
be able to turn it off.. but it will be on by default).

That being done, sigtran will finally get the ADD-IP draft
finished.. gee.. only 4 years :-D

But what about all this other cruft... load balancing
for one?

Well, Jana's work has shown that doing load balancing
in the transport is most efficient for throughput. Does
this handle every case.. I don't think so.. I know
folks have mentioned doing prioritization and other
funky things.. but IMO the reality is throughput
is the major reason folks want loadbalancing... not
the other side issues. IMO we optimize for the majority
and provide a turn-off knob so that the few apps that
want to do some special thingy can... Of course there
is still some more work that needs to be completed
until CMT can be made available in a draft form.. so
we are not there yet IMO but we are getting closer
(research first, engineering later) :-D

So, how do we proceed? It seems to me a Shim layer
will not work very well unless you so intergrate
it with the transport that it becomes part of the transport.
Is the shim going to have to start tracking its own PCB, it
would if it wants to do something like the AUTH draft, that
was a fundamental problem of the old crocker draft IMO. So
you end up having this shim either have a pcb per transport
connection or it gets its hooks deeper and deeper into
the transport's and merges in sort of...

In that case .. sure I can call a section of the
SCTP stack the "shim" but I just don't see it
working very well seperated out.. not without opening
up major interfaces between the new shim and transport and
that does not even account for the state thats needed.

Look how well congestion manager has worked.. its the
same issue.. its concept was to tease out the congestion
managment into a sub-layer.. as yet I see no deployment
of CM and I, for one, will not hold my breath waiting
for it :-D Good idea its just not making its way
out into the world (sorta like mobile IP I guess)...

So where does that leave things?

I think that DCCP and SCTP handle the multi-homing for
now. Lets use these for those app's that need multi-homing
(including in the future load balancing if that work
  pans out) and let those that don't need it continue
to use TCP or UDP. If an app is over TCP that needs the feature its
quite easy to migrate to SCTP.. usually only a couple
of lines of code. Hopefully DCCP will have a similar
API that makes UDP easy to migrate to DCPP..

DCCP and SCTP have solved these
problems lets use these solutions as an encouragment
to use the new protocols... If you need the features
use the existing tools... If you don't stick with TCP
and UDP



R



Ted Faber wrote:
> 
> Despite my testy reply, I think we agree a bunch more than we disagree.
> I understand what you're saying and I apologize for snapping.
> 
> As I'm sure you know, there's quite a bit to worry about beyond naming
> when you consider endpoints that move often and need to maintain
> communications when they do so.  You can constrain yourself into an
> unsolvable problem pretty quickly.  IMHO, one should grab at tradeoffs
> when they appear.  For example, the scale of most of the proposed MANETs
> I've seen (other than sensor networks) means you can trade scope for
> consistency in the naming system.  A small (by Internet standards)
> network of endpoints that change their name-to-address mappings
> frequently is a lousy fit for DNS, and there's no good reason to use it
> there.  (Though having a name system tuned for that environment repsond
> to DNS queries might be of practical use.)
> 
> The more of these sorts of discussions I have, the less I think that the
> various uses of multi-homing (e.g., mobility, availability, load balancing)
> are all that closely related.  I'm less optimisitic that there is a
> single "multi-homing" solution that will scratch all those itches.  In
> any case I think that it's an area in which people should tread
> carefully and precisely.
> 
> I'm also concerned about making transport level changes without a clear
> need or at least a clear indication of the tradeoffs.  I've yet to see a
> case where a system is impossible without moving multihoming into the
> transport or where all the hard parts are solved and the extra
> kernel/layer crossings are the only think keeping the system from being
> efficient.  I'm not saying that they don't exist, just that I haven't
> seen clear demonstrations.
> 
> Finally endpoint to endpoint transport where both endpoints have static
> single identifiers is tricky.  Building on that rather than complicating
> it seems like the way to go.  I recognize that's an opinion, but it's
> one that I hold pretty strongly.
> 


-- 
Randall Stewart
803-345-0369 <or> 815-342-5222(cell)

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


From tsvwg-bounces@ietf.org  Thu Dec  2 03:04:13 2004
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 DAA17528;
	Thu, 2 Dec 2004 03:04:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZm2E-00034X-Q8; Thu, 02 Dec 2004 03:09:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZlYP-0008M9-8E; Thu, 02 Dec 2004 02:39:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZkvB-0001G9-UA
	for tsvwg@megatron.ietf.org; Thu, 02 Dec 2004 01:58:34 -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 BAA27158
	for <tsvwg@ietf.org>; Thu, 2 Dec 2004 01:58:32 -0500 (EST)
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZl0c-0001b9-1j
	for tsvwg@ietf.org; Thu, 02 Dec 2004 02:04:13 -0500
Received: from slb-av-01.boeing.com ([129.172.13.4])
	by blv-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id
	WAA17480 for <tsvwg@ietf.org>; Wed, 1 Dec 2004 22:57:58 -0800 (PST)
Received: from XCH-NWBH-02.nw.nos.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id
	iB26vvi08188
	for <tsvwg@ietf.org>; Wed, 1 Dec 2004 22:57:57 -0800 (PST)
Received: from XCH-NW-27.nw.nos.boeing.com ([192.48.4.101]) by
	XCH-NWBH-02.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 1 Dec 2004 22:57:57 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Tsvwg] multiaddressing
Date: Wed, 1 Dec 2004 22:57:57 -0800
Message-ID: <6938661A6EDA8A4EA8D1419BCE46F24C0406093E@xch-nw-27.nw.nos.boeing.com>
Thread-Topic: [Tsvwg] multiaddressing
Thread-Index: AcTXynhMl46wufGRTUi5Ewp+E3rfZwAbIZzg
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: <tsvwg@ietf.org>
X-OriginalArrivalTime: 02 Dec 2004 06:57:57.0568 (UTC)
	FILETIME=[41233400:01C4D83C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: quoted-printable
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: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: quoted-printable

Randall, I agree with you on many points of your argument,
but I think the problem is more general than you stated and
will require multiple solutions.  In particular,

> Now, why does SCTP have multiple addresses... (in
> priority order)
>=20
> 1) Fault-tolerance -=20
> 2) Load-balancing -=20

Fault tolerance is an interesting case, because (as it is defined
in SCTP) it means that certain transport PDUs have different
priority or delivery semantics than others.  In particular,=20
you want to force timeout retransmissions onto a different path.=20
I agree here that if you put this kind of function in a multihoming
shim layer, it makes the interface more complicated to transport--
in this case, you want transport to be able to specify which TPDU
goes where, and to know where TPDUs came from, etc.  So I would
agree that SCTP, being oriented towards signaling transport, has
particular signaling fault tolerance requirements in mind (the
requirements may extend beyond signaling and be generally=20
applicable), and it makes sense to try to solve it in SCTP.

For load-balancing, it is not as clear to me-- it could be in
a shim, it could be in transport, it could be in session layer. =20
It seems to make sense to integrate it with congestion control,
which might lean it towards transport again, but if it is not
in transport, then I don't believe that the interface is necessarily
that complex.

But there are also the site multihoming requirements in RFC3582
for multi6.  I do not think there is a general consensus in multi6
that migration of all apps to DCCP and SCTP is the answer.

In the future, wireless systems with multiple radios will become
more prevalent.  These radios may connect to different providers.
Additional considerations that may arise are energy consumption,
link or network layer indicators of path performance, and relative
monetary costs that may favor one path over another. It is not clear
to me that transport is where the path selection decisions over those
kinds of disparate paths must reside.

I'd like to keep more options open for the future, including
considering whether shims might make congestion manager
more deployable, and multihoming more widely applicable, and even
handle mobility.  In the near term, it seems like the multi6 work
will pick up in another (to be chartered) working group, and if so,
it will probably be a good time for tsvwg to start thinking about
how transport will be affected by such a solution.

Tom=20

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


From tsvwg-bounces@ietf.org  Thu Dec  2 07:29:48 2004
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 HAA08162;
	Thu, 2 Dec 2004 07:29:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CZqBI-0000dI-4i; Thu, 02 Dec 2004 07:35:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CZpXC-0000gT-KZ; Thu, 02 Dec 2004 06:54:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CZpOM-0003X0-Pj
	for tsvwg@megatron.ietf.org; Thu, 02 Dec 2004 06:44:58 -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 GAA04676
	for <tsvwg@ietf.org>; Thu, 2 Dec 2004 06:44:55 -0500 (EST)
Received: from dpc674425142.direcpc.com ([67.44.25.142]
	helo=stewart.chicago.il.us)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZpTr-00088O-9Z
	for tsvwg@ietf.org; Thu, 02 Dec 2004 06:50:41 -0500
Received: from stewart.chicago.il.us (localhost [127.0.0.1])
	by stewart.chicago.il.us (8.12.9p2/8.12.8) with ESMTP id iB2BiZ84019356;
	Thu, 2 Dec 2004 06:44:37 -0500 (EST)
	(envelope-from randall@stewart.chicago.il.us)
Message-ID: <41AEFFAF.1060908@stewart.chicago.il.us>
Date: Thu, 02 Dec 2004 06:42:39 -0500
From: Randall Stewart <randall@stewart.chicago.il.us>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040429
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
Subject: Re: [Tsvwg] multiaddressing
References: <6938661A6EDA8A4EA8D1419BCE46F24C0406093E@xch-nw-27.nw.nos.boeing.com>
In-Reply-To: <6938661A6EDA8A4EA8D1419BCE46F24C0406093E@xch-nw-27.nw.nos.boeing.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
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: 2beba50d0fcdeee5f091c59f204d4365
Content-Transfer-Encoding: 7bit

Henderson, Thomas R wrote:
> Randall, I agree with you on many points of your argument,
> but I think the problem is more general than you stated and
> will require multiple solutions.  In particular,
> 
> 
>>Now, why does SCTP have multiple addresses... (in
>>priority order)
>>
>>1) Fault-tolerance - 
>>2) Load-balancing - 
> 
> 
> Fault tolerance is an interesting case, because (as it is defined
> in SCTP) it means that certain transport PDUs have different
> priority or delivery semantics than others.  In particular, 
> you want to force timeout retransmissions onto a different path. 
> I agree here that if you put this kind of function in a multihoming
> shim layer, it makes the interface more complicated to transport--
> in this case, you want transport to be able to specify which TPDU
> goes where, and to know where TPDUs came from, etc.  So I would
> agree that SCTP, being oriented towards signaling transport, has
> particular signaling fault tolerance requirements in mind (the
> requirements may extend beyond signaling and be generally 
> applicable), and it makes sense to try to solve it in SCTP.

Two comments to the above point. A) SCTP has a broader
scope then its initial signalling world. and B) I am a bit
unclear on how one gets differetn priority's. If you do the
currently recommend approach, retransmissons at timeout goes
to the alternate. Then all data in queue, unack'd, when the
timeout happens moves to the alternate. These will arrive
in the same order ... so I don't think I see your point...


> 
> For load-balancing, it is not as clear to me-- it could be in
> a shim, it could be in transport, it could be in session layer.  
> It seems to make sense to integrate it with congestion control,
> which might lean it towards transport again, but if it is not
> in transport, then I don't believe that the interface is necessarily
> that complex.

You can in theory do load-balancing with SCTP in an upper
layer today. However there are issues with it... i.e. see
Jana's papers on CMT and his previous ones. I agree that
for the upper layers the interface is NOT complex.. I was
thinking more lower layers.. i.e. moving it to a shim....

> 
> But there are also the site multihoming requirements in RFC3582
> for multi6.  I do not think there is a general consensus in multi6
> that migration of all apps to DCCP and SCTP is the answer.
> 

The goals set forth in RFC3582 may or may-not be reachable...note
the word goals.. they are not requirements IMO if they are then
the RFC should state they are requirements instead of goals :-0

> In the future, wireless systems with multiple radios will become
> more prevalent.  These radios may connect to different providers.
> Additional considerations that may arise are energy consumption,
> link or network layer indicators of path performance, and relative
> monetary costs that may favor one path over another. It is not clear
> to me that transport is where the path selection decisions over those
> kinds of disparate paths must reside.

And there is where having switches in the transport to turn
those decisions off is a good thing. That way the application
or layer that is aware of the costs etc can take these into
account. I agree wireless and future radio systems will become
available.. but I don't see them as pre-dominant. While driving
in my car I am not going to do a lot of web-browsing.. its
cheaper for me to do it at home.. and until the radio world
realizes that I will not pay X$ per minute.. when I can have
unlimited use at home.. thats going to stay I think... When
I worked at Mot I always heard how radio IP would sweep the
world ... and that was quite a few years ago.. I agree it
will have its place.. but i dont see it as predominant until
major changes in pricing and policy happen.. and that is blocked
by all the govt's that like to get rich on spectrum and of
course the cost and recovery that the company's want..

But I digress and go down a rat hole :->

Lets just say, yep I agree, but it won't be the primary method
of attachment for quite some time... :-D

> 
> I'd like to keep more options open for the future, including
> considering whether shims might make congestion manager
> more deployable, and multihoming more widely applicable, and even
> handle mobility.  In the near term, it seems like the multi6 work
> will pick up in another (to be chartered) working group, and if so,
> it will probably be a good time for tsvwg to start thinking about
> how transport will be affected by such a solution.

Maybe... I have my doubts on the sucess of a shim. It just seems
to me that all this multi-homing/mobility glock is just trying
to take the things done in DCCP and SCTP and re-do them
in another layer to keep us all busy working on things... and
at the same time (like nat) gut some of the incentives to go
to the next newer technology... Until the IETF stops this type
of stuff (which won't happen) it will get harder and harder
to roll out any technology... just wait a new one will come
out...


R

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


-- 
Randall Stewart
803-345-0369 <or> 815-342-5222(cell)

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


From tsvwg-bounces@ietf.org  Mon Dec  6 10:33:38 2004
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 KAA22083;
	Mon, 6 Dec 2004 10:33:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbKyF-0007ZP-Jd; Mon, 06 Dec 2004 10:40:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbKpv-0001fx-CU; Mon, 06 Dec 2004 10:31:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbKnb-00013o-Oc
	for tsvwg@megatron.ietf.org; Mon, 06 Dec 2004 10:29:20 -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 KAA21745
	for <tsvwg@ietf.org>; Mon, 6 Dec 2004 10:29:13 -0500 (EST)
Received: from zcars04e.nortelnetworks.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbKty-0007Re-Rf
	for tsvwg@ietf.org; Mon, 06 Dec 2004 10:35:51 -0500
Received: from zbl6c002.us.nortel.com (zbl6c002.corpeast.baynetworks.com
	[132.245.205.52])
	by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP
	id iB6FSD007117; Mon, 6 Dec 2004 10:28:13 -0500 (EST)
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 WKL3NDWG; Mon, 6 Dec 2004 10:28:12 -0500
Message-Id: <6.0.3.0.0.20041206094719.047a2a08@zbl6c002.corpeast.baynetworks.com>
X-Sender: khchan@zbl6c002.corpeast.baynetworks.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
Date: Mon, 06 Dec 2004 10:28:11 -0500
To: =?gb2312?B?sszd7d3t?= <cbeibei@263.net>
From: Kwok Ho Chan <khchan@nortelnetworks.com>
Subject: Re: Re: Re: [Tsvwg] some problems
	aboutdraft-baker-diffserv-basic -classes-0 4
In-Reply-To: <20041205034105.3A64934708@smtp.263.net>
References: <20041205034105.3A64934708@smtp.263.net>
Mime-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6a817af60e4281a101681ecb646dffff
Cc: Kwok-Ho Chan <khchan@nortelnetworks.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>
Content-Type: multipart/mixed; boundary="===============0040854595=="
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f3b9db08b8c0fe2301a77f547096e31

--===============0040854595==
Content-Type: multipart/alternative;
	boundary="=====================_212776286==.ALT"

--=====================_212776286==.ALT
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable

Bei-Bei:
Please notice I have added this thread to the TSVWG mailing list.
Please see response embedded below.
Any additional input are welcomed.
Thanks!
-- Kwok Ho --

At 10:39 PM 12/4/2004, =3D?gb2312?B?sszd7d3t?=3D wrote:
>Kwok Ho:
>
>Thank you very much for your so detailed answer.
>Your help have resolved some questions I had.
>Of course,you can put this conversation back onto the TSVWG mailing list.:)
>
>And,may I understand the draft as follow : the gradation of traffic=20
>priority from high to low is
>  CS7,CS6.EF,CS5.AF4,CS4,AF3,CS3,AF2,CS2,AF1,CS0(DF),CS1?

I think you can say that.  But in reality, IMHO, the network needs to make=
=20
sure it
upholds the promise it gave to its customer, no matter which service class=
=20
it is.
This may mean the network needs to admit less traffic that goes into=20
service class using
EF so the service classes using CS4 and AF4x will still uphold the promise=
=20
to its users.
The decision is on which service classes a network supports (they don't=20
need to support
all the service classes) and how much of each.

>I have cleared about those service classes except for the Broadcast Video=
=20
>Service Class.
>Based on the draft,Broadcast video is inelastic traffic,and Multimedia=20
>Streaming is elastic.
>Why do the former use CS3 and the latter use AF3?
>And in 4.2.1 part of draft-baker-diffserv-basic-classes-02, the Multimedia=
=20
>Streaming class include
>the Broadcast video service.What is the reason for separating the=20
>broadcast video from the multimedia streaming
>in draft-baker-diffserv-basic-classes-03(and 04) ?

Broadcast Video service class is meant for High Definition broadcasts and=20
the likes.
We have found that the Loss Tolerance for these traffic is relatively lower=
=20
than Multimedia
Streaming service class.  Hence its separation.  Again this is based on=20
what the application
requires of the network.  At low loss high capacity parts of the network,=20
both of these
service classes may get treated together without impact to the promises=20
made to the
user of each service class (discussion for the service class aggregation=20
draft).

>
>Thank you very much!
>
>
>
>                                                                   Cai=
 bei-bei
>ps:Best wishes to you!
>=A1=A1=A1=A1
>
>
>=3D=3D=3D=3D=3D=3D=3D=3D 2004-12-02 23:49:52 =C4=FA=D4=DA=C0=B4=D0=C5=D6=D0=
=D0=B4=B5=C0=A3=BA =3D=3D=3D=3D=3D=3D=3D=3D
>
>>Bei-Bei:
>>Agree that they all need low delay, low jitter.
>>Other factors that affects the service classes placement are loss=20
>>tolerance, traffic elasticity,
>>and packet size (and its variation).
>>
>>Telephony uses EF. the Multimedia Conferencing uses AF because it is=20
>>elastic traffic.
>>There is also the Real-Time Interactive class using CS4 that handles=20
>>inelastic video traffic.
>>Please reference Figure 1 of
>>=20
>>http://www.ietf.org/internet-drafts/draft-baker-diffserv-basic-classes-04.=
txt
>>
>>EF PHB normally get deployed with some kind of upper limit on the traffic=
=20
>>it treats, either
>>with some policer, rate limiter, and/or some other admission control=
 methods.
>>With this in mind, the EF traffic should not starve the AF4x and CS4=20
>>traffic.  Each should
>>forward the traffic as configured (one may not want to have too much EF=20
>>traffic that will
>>add too much delay to the CS4 and AF4x traffic making them=20
>>un-acceptable).  Without
>>having the elastic traffic adversely affecting the inelastic traffic.  Or=
=20
>>having large packets
>>adding too much jitter to small inelastic traffic.
>>
>>This draft takes the points of view of how each application using the=20
>>different service classes
>>will receive the network treatment it requires (end to end), when traffic=
=20
>>in multiple service classes
>>need to share the network.  When these traffic traverse both low and high=
=20
>>capacity networks/links.
>>
>>There is another draft that discusses how in high capacity=20
>>networks/links, multiple service classes
>>can be aggregated together.  I have published -00 version of this draft=20
>>but I am in the process of
>>updating this draft to add more content and making changes based on the=20
>>comments received.
>>I would advise to wait for the -01 of=
 draft-chan-tsvwg-diffserv-class-aggr.
>>
>>I hope this help to answer/resolve the questions/issues you have.
>>
>>Also, can I put this conversation back onto the TSVWG mailing list?
>>
>>Thank you!
>>-- Kwok Ho --
>>
>>
>>At 08:17 AM 12/2/2004, =3D?gb2312?B?sszd7d3t?=3D wrote:
>>>Kwok Ho Chan:
>>>
>>>Thank you for your answers.
>>>Yes,I am a student of Nanjing University of Posts and Telecommunications=
=20
>>>of China.
>>>Now we are doing a project about end-to-end IP QoS.
>>>
>>>Every service has different QoS requirement.So it will be classed, and=20
>>>deployed with DSCP, then be treated differently based on the different=
 class.
>>>Voice and Vedio require real-time, very low delay, very low jitter,which=
=20
>>>must use EF PHB.So I am
>>>puzzled that Multimedia Conferencing use AF PHB. Services have lower=20
>>>priority ,they may wait in a queue for a longer time, which will bring=20
>>>higher delay. The same question exist between multimedia  streaming and=
=20
>>>broadcast video and so on.
>>>
>>>We want to use the draft to class services, and deal with these based on=
=20
>>>the DSCP.
>>>
>>>=A1=A1=A1=A1Thank you very much!!
>>>
>>>=3D=3D=3D=3D=3D=3D=3D=3D 2004-11-24 22:54:53 =C4=FA=D4=DA=C0=B4=D0=C5=D6=
=D0=D0=B4=B5=C0=A3=BA =3D=3D=3D=3D=3D=3D=3D=3D
>>>
>>>>Bei-Bei:
>>>>Thank you for your comments.
>>>>I think you mis-understood the concepts.
>>>>The basic-classes draft separates the traffic into different classes
>>>>based on their traffic characteristics.
>>>>It does not necessarily mean Multimedia Conferencing is lower than=20
>>>>Telephony,
>>>>they just needs to be separated.
>>>>We also recommend some treatment approaches for each Service Class based
>>>>on each of their traffic characteristics.
>>>>Please look at (read) the draft this way and let us know if think=20
>>>>differently.
>>>>Thanks!
>>>>-- Kwok Ho Chan --
>>>>p.s. Are you based in China?  It looks like a Chinese name to me.
>>>>       How may you want to use this draft?
>>>>
>>>>
>>>>At 09:18 AM 11/24/2004, =3D?gb2312?B?sszd7d3t?=3D wrote:
>>>>
>>>>>Hi:
>>>>>
>>>>>   I have some problems about draft-baker-diffserv-basic-classes-04.
>>>>>
>>>>>   1.Why is the priority of Multimedia Conferencing(eg.H.323/V2 Video=
=20
>>>>> conferencing) lower than telephone? The former(video) sometimes need=
=20
>>>>> very low delay,eg.CBR video.
>>>>>
>>>>>   2 Usually,the signalling precede the corresponding service. Why=20
>>>>> does the service class signalling have a lower priority than=20
>>>>> telephone? And i also don't know why the QAM is behind Low=20
>>>>> Latency  data,and the broadcast video is behind multimedia=20
>>>>> streaming?In my concepte,broadcast video is include in multimeida=20
>>>>> streaming and need less delay.
>>>>>
>>>>>
>>>>>
>>>>>   Thank you very much!!
>>>>>
>>>>>
>>>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1
>>>>>
>>>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1Cai Bei-bei
>>>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1cbeibei@263.net
>>>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12004-11-24
>>>>>
>>>>>
>>>
>>>=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D
>>>
>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=D6=C2
>>>=C0=F1=A3=A1
>>>
>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=B2=CC=DD=ED=DD=ED
>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1<mailto:cbeibei@263.net>cbeibei@263.net
>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A1=A12004-12-02
>>>
>
>=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D=
 =3D =3D =3D
>
>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=D6=C2
>=C0=F1=A3=A1
>
>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=B2=CC=DD=ED=DD=ED
>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1<mailto:cbeibei@263.net>cbeibei@263.net
>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A12004-12-03
>

--=====================_212776286==.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<body>
Bei-Bei:<br>
Please notice I have added this thread to the TSVWG mailing list.<br>
Please see response embedded below.<br>
Any additional input are welcomed.<br>
Thanks!<br>
-- Kwok Ho --<br><br>
At 10:39 PM 12/4/2004, =3D?gb2312?B?sszd7d3t?=3D wrote:<br>
<blockquote type=3Dcite class=3Dcite cite><font size=3D2>Kwok Ho:<br>
</font>&nbsp;<br>
<font size=3D2>Thank you very much for your so detailed answer.<br>
Your help have resolved some questions I had.<br>
Of course,you can put this conversation back onto the TSVWG mailing
list.:)<br>
</font>&nbsp;<br>
And,may I understand the draft as follow : the gradation of traffic
priority from high to low is<br>
&nbsp;CS7,CS6.EF,CS5.AF4,CS4,AF3,CS3,AF2,CS2,AF1,CS0(DF),CS1?</blockquote><b=
r>
I think you can say that.&nbsp; But in reality, IMHO, the network needs
to make sure it<br>
upholds the promise it gave to its customer, no matter which service
class it is.<br>
This may mean the network needs to admit less traffic that goes into
service class using<br>
EF so the service classes using CS4 and AF4x will still uphold the
promise to its users.<br>
The decision is on which service classes a network supports (they don't
need to support<br>
all the service classes) and how much of each.<br><br>
<blockquote type=3Dcite class=3Dcite cite>I have cleared about those service
classes except for the Broadcast Video Service Class.<br>
Based on the draft,Broadcast video is inelastic traffic,and Multimedia
Streaming is elastic.<br>
Why do the former use CS3 and the latter use AF3?<br>
And in 4.2.1 part of <i>draft-baker-diffserv-basic-classes-02</i>, the
Multimedia Streaming class include<br>
the Broadcast video service.What is the reason for separating the
broadcast video from the multimedia streaming <br>
in <i>draft-baker-diffserv-basic-classes-03(and 04)
</i>?</blockquote><br>
Broadcast Video service class is meant for High Definition broadcasts and
the likes.<br>
We have found that the Loss Tolerance for these traffic is relatively
lower than Multimedia<br>
Streaming service class.&nbsp; Hence its separation.&nbsp; Again this is
based on what the application<br>
requires of the network.&nbsp; At low loss high capacity parts of the
network, both of these<br>
service classes may get treated together without impact to the promises
made to the<br>
user of each service class (discussion for the service class aggregation
draft).&nbsp; <br><br>
<blockquote type=3Dcite class=3Dcite cite>&nbsp;<br>
Thank you very much!<br>
&nbsp;<br>
&nbsp;<br>
&nbsp;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
Cai bei-bei<br>
ps:Best wishes to you!<br>
<font size=3D2>=A1=A1=A1=A1<br>
</font>&nbsp;<br>
&nbsp;<br>
<font size=3D2>=3D=3D=3D=3D=3D=3D=3D=3D 2004-12-02 23:49:52 =C4=FA=D4=DA=C0=
=B4=D0=C5=D6=D0=D0=B4=B5=C0=A3=BA =3D=3D=3D=3D=3D=3D=3D=3D<br>
</font>&nbsp;<br>
<blockquote type=3Dcite class=3Dcite cite><font size=3D2>Bei-Bei:<br>
Agree that they all need low delay, low jitter.<br>
Other factors that affects the service classes placement are loss
tolerance, traffic elasticity,<br>
and packet size (and its variation). <br><br>
Telephony uses EF. the Multimedia Conferencing uses AF because it is
elastic traffic.<br>
There is also the Real-Time Interactive class using CS4 that handles
inelastic video traffic.<br>
Please reference Figure 1 of<br>
&nbsp;
<a=
 href=3D"http://www.ietf.org/internet-drafts/draft-baker-diffserv-basic-clas=
ses-04.txt"=
 eudora=3D"autourl">http://www.ietf.org/internet-drafts/draft-baker-diffserv=
-basic-classes-04.txt</a><br><br>
EF PHB normally get deployed with some kind of upper limit on the traffic
it treats, either<br>
with some policer, rate limiter, and/or some other admission control
methods.<br>
With this in mind, the EF traffic should not starve the AF4x and CS4
traffic.&nbsp; Each should<br>
forward the traffic as configured (one may not want to have too much EF
traffic that will<br>
add too much delay to the CS4 and AF4x traffic making them
un-acceptable).&nbsp; Without<br>
having the elastic traffic adversely affecting the inelastic
traffic.&nbsp; Or having large packets<br>
adding too much jitter to small inelastic traffic.<br><br>
This draft takes the points of view of how each application using the
different service classes<br>
will receive the network treatment it requires (end to end), when traffic
in multiple service classes<br>
need to share the network.&nbsp; When these traffic traverse both low and
high capacity networks/links. <br><br>
There is another draft that discusses how in high capacity
networks/links, multiple service classes<br>
can be aggregated together.&nbsp; I have published -00 version of this
draft but I am in the process of<br>
updating this draft to add more content and making changes based on the
comments received.<br>
I would advise to wait for the -01 of
draft-chan-tsvwg-diffserv-class-aggr.<br><br>
I hope this help to answer/resolve the questions/issues you
have.<br><br>
Also, can I put this conversation back onto the TSVWG mailing
list?<br><br>
Thank you!<br>
-- Kwok Ho --<br><br>
<br>
At 08:17 AM 12/2/2004, =3D?gb2312?B?sszd7d3t?=3D wrote:<br>
<blockquote type=3Dcite class=3Dcite cite>Kwok Ho Chan:<br>
&nbsp;<br>
Thank you for your answers.<br>
Yes,I am a student of Nanjing University of Posts and Telecommunications
of China.<br>
Now we are doing a project about end-to-end IP QoS.<br>
&nbsp;<br>
Every service has different QoS requirement.So it will be classed, and
deployed with DSCP, then be treated differently based on the different
class.<br>
Voice and Vedio require real-time, very low delay, very low jitter,which
must use EF PHB.So I am <br>
puzzled that Multimedia Conferencing use AF PHB. Services have lower
priority ,they may wait in a queue for a longer time, which will bring
higher delay. The same question exist between multimedia&nbsp; streaming
and broadcast video and so on.<br>
&nbsp;<br>
We want to use the draft to class services, and deal with these based on
the DSCP.&nbsp; <br>
&nbsp;<br>
=A1=A1=A1=A1Thank you very much!! <br>
&nbsp;<br>
=3D=3D=3D=3D=3D=3D=3D=3D 2004-11-24 22:54:53 =C4=FA=D4=DA=C0=B4=D0=C5=D6=D0=
=D0=B4=B5=C0=A3=BA =3D=3D=3D=3D=3D=3D=3D=3D<br>
&nbsp;<br>
<blockquote type=3Dcite class=3Dcite cite>Bei-Bei:<br>
Thank you for your comments.<br>
I think you mis-understood the concepts.<br>
The basic-classes draft separates the traffic into different=20
classes<br>
based on their traffic characteristics.<br>
It does not necessarily mean Multimedia Conferencing is lower than
Telephony,<br>
they just needs to be separated.<br>
We also recommend some treatment approaches for each Service Class
based<br>
on each of their traffic characteristics.<br>
Please look at (read) the draft this way and let us know if think
differently.<br>
Thanks!<br>
-- Kwok Ho Chan --<br>
p.s. Are you based in China?&nbsp; It looks like a Chinese name to
me.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; How may you want to use this
draft?<br><br>
<br>
At 09:18 AM 11/24/2004, =3D?gb2312?B?sszd7d3t?=3D wrote:<br><br>
<blockquote type=3Dcite class=3Dcite cite>Hi: <br><br>
&nbsp; I have some problems about draft-baker-diffserv-basic-classes-04.
<br><br>
&nbsp; 1.Why is the priority of Multimedia Conferencing(eg.H.323/V2 Video
conferencing) lower than telephone? The former(video) sometimes need very
low delay,eg.CBR video. <br><br>
&nbsp; 2 Usually,the signalling precede the corresponding service. Why
does the service class signalling have a lower priority than telephone?
And i also don't know why the QAM is behind Low Latency&nbsp; data,and
the broadcast video is behind multimedia streaming?In my
concepte,broadcast video is include in multimeida streaming and need less
delay.<br><br>
&nbsp; <br>
&nbsp; <br>
&nbsp; Thank you very much!! <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br><br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1 <br><br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1Cai Bei-bei <br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1cbeibei@263.net <br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12004-11-24=
 <br><br>
&nbsp; </blockquote></blockquote><br>
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D=
 =3D =3D =3D <br><br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=D6=C2<br>
=C0=F1=A3=A1<br>
&nbsp;<br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=B2=CC=DD=ED=DD=ED<br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1<a href=3D"mailto:cbeibei@263.net">cbeibei@263.net</a><br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A12004-12-02<br>
&nbsp;</font></blockquote></blockquote><br>
<font size=3D2>=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D <br>
</font><br>
<font size=3D2>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=D6=C2<br>
=C0=F1=A3=A1<br>
</font>&nbsp;<br>
<font size=3D2>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A1=A1=A1=A1=B2=CC=DD=ED=DD=ED<br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1<a href=3D"mailto:cbeibei@263.net">cbeibei@263.net</a><br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A12004-12-03<br>
</font>&nbsp;</blockquote></body>
</html>

--=====================_212776286==.ALT--



--===============0040854595==
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

--===============0040854595==--




From tsvwg-bounces@ietf.org  Tue Dec  7 04:56:10 2004
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 EAA07556;
	Tue, 7 Dec 2004 04:56:10 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbcBO-0006kc-Cm; Tue, 07 Dec 2004 05:02:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cbc2O-0003YV-TI; Tue, 07 Dec 2004 04:53:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cbby2-0002cB-F3
	for tsvwg@megatron.ietf.org; Tue, 07 Dec 2004 04:49:10 -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 EAA06766
	for <tsvwg@ietf.org>; Tue, 7 Dec 2004 04:49:08 -0500 (EST)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbc4X-0006Yg-0O
	for tsvwg@ietf.org; Tue, 07 Dec 2004 04:55:56 -0500
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 07 Dec 2004 11:01:16 +0100
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
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
	iB79leHF014774; Tue, 7 Dec 2004 10:48:32 +0100 (MET)
Received: from xmb-ams-333.cisco.com ([144.254.231.78]) by
	xbh-ams-331.cisco.com with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 7 Dec 2004 10:48:31 +0100
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
Subject: RE: [Tsvwg] Reviews of RSVP extensions (here, there, or ... ?)
Date: Tue, 7 Dec 2004 10:48:22 +0100
Message-ID: <A05118C6DF9320488C77F3D5459B17B7357467@xmb-ams-333.emea.cisco.com>
Thread-Topic: [Tsvwg] Reviews of RSVP extensions (here, there, or ... ?)
Thread-Index: AcTXLat7sPz0bPkCSMG6oUgMMnO95gFEk7pg
From: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>
To: "Ted Faber" <faber@ISI.EDU>, "Jukka MJ Manner" <jmanner@cs.Helsinki.FI>
X-OriginalArrivalTime: 07 Dec 2004 09:48:31.0877 (UTC)
	FILETIME=[E9539350:01C4DC41]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: quoted-printable
Cc: "James Polk \(jmpolk\)" <jmpolk@cisco.com>, tsvwg <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: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: quoted-printable

Hello,
=20
>> My impression hasn't been that there's been a shortage of time to
>> present or discuss these drafts in TSVWG, but a low interest=20
>> level.  I'm
>> not sure that a new group would address that.
>>=20
>> That's an impression; I could be way off.

I remember a "Hum-test" was run during the WG.
Although I can't remember the exat words, I believe the question was
something like "is the RSVP work discussed in the TSVWG useful?"  or "is
the RSVP work discussed in the TSVWG of interest to this audience?".
I thought the "Hum-level" was clearly quite high. So my impression is
that we had settled on that question and that there is agreement in
progressing this work.
Am I missing something?

I think James' question is rather about whether this should be done
under TSVWG or in some other group. Personally, I would suggest keeping
it under TSVWG until there is a specific reason to change (e.g. there is
a shortage of time to present/discuss all the items under TSVWG).

Cheers

Francois

>>=20
>> --=20
>> Ted Faber
>> http://www.isi.edu/~faber           PGP:=20
>> http://www.isi.edu/~faber/pubkeys.asc
>> Unexpected attachment on this mail? See=20
>> http://www.isi.edu/~faber/FAQ.html#SIG=20
>>=20

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


From tsvwg-bounces@ietf.org  Tue Dec  7 13:26:50 2004
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 NAA03060;
	Tue, 7 Dec 2004 13:26:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cbk9e-0002RN-OG; Tue, 07 Dec 2004 13:33:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cbjnd-0003nW-F3; Tue, 07 Dec 2004 13:10:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbjcG-0001j8-E3
	for tsvwg@megatron.ietf.org; Tue, 07 Dec 2004 12:59:12 -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 MAA29881
	for <tsvwg@ietf.org>; Tue, 7 Dec 2004 12:59:09 -0500 (EST)
Received: from mailgw3a.lmco.com ([192.35.35.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbjis-0001n1-9D
	for tsvwg@ietf.org; Tue, 07 Dec 2004 13:06:02 -0500
Received: from emss04g01.ems.lmco.com (relay4.ems.lmco.com [166.17.13.122])
	by mailgw3a.lmco.com (8.12.10/8.12.10) with ESMTP id iB7HvwSD024529;
	Tue, 7 Dec 2004 12:57:58 -0500 (EST)
Received: from CONVERSION-DAEMON.lmco.com by lmco.com (PMDF V6.1-1X6 #30884)
	id <0I8D00F015WM0Z@lmco.com>; Tue, 07 Dec 2004 12:57:58 -0500 (EST)
Received: from EMSS04I00.us.lmco.com ([166.17.13.135]) by lmco.com (PMDF
	V6.1-1X6 #30884) with ESMTP id <0I8D00C6Q5WJCA@lmco.com>;
	Tue, 07 Dec 2004 12:57:58 -0500 (EST)
Received: from EMSS04M14.us.lmco.com ([162.16.20.50]) by EMSS04I00.us.lmco.com
	with Microsoft SMTPSVC(5.0.2195.6713); Tue,
	07 Dec 2004 12:57:55 -0500
Date: Tue, 07 Dec 2004 12:57:50 -0500
From: "Bose, Pratik" <pratik.bose@lmco.com>
Subject: RE: [Tsvwg] Reviews of RSVP extensions (here, there, or ... ?)
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>,
        Ted Faber <faber@ISI.EDU>, Jukka MJ Manner <jmanner@cs.Helsinki.FI>
Message-id: <37B6F612D86CA143B5F965E9EE8BD7AA09C03154@emss04m14.us.lmco.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6603.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-Topic: [Tsvwg] Reviews of RSVP extensions (here, there, or ... ?)
Thread-Index: AcTXLat7sPz0bPkCSMG6oUgMMnO95gFEk7pgABF76EA=
content-class: urn:content-classes:message
X-OriginalArrivalTime: 07 Dec 2004 17:57:55.0801 (UTC)
	FILETIME=[4796CC90:01C4DC86]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7BIT
Cc: "James Polk \(jmpolk\)" <jmpolk@cisco.com>, tsvwg <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
Content-Transfer-Encoding: 7BIT

Actually I do remember the hum-test that Francois mentions, and I also
recall that a counter hum-test was taken for the same question below
(for those in favor of not supporting this work here) and there was
barely a hum for that - so I am not sure whether the interest being low
is really correct. I am sure the minutes can confirm this info....

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] 
> On Behalf Of Francois Le Faucheur (flefauch)
> Sent: Tuesday, December 07, 2004 4:48 AM
> To: Ted Faber; Jukka MJ Manner
> Cc: James Polk (jmpolk); tsvwg
> Subject: RE: [Tsvwg] Reviews of RSVP extensions (here, there, 
> or ... ?)
> 
> Hello,
>  
> >> My impression hasn't been that there's been a shortage of time to 
> >> present or discuss these drafts in TSVWG, but a low 
> interest level.  
> >> I'm not sure that a new group would address that.
> >> 
> >> That's an impression; I could be way off.
> 
> I remember a "Hum-test" was run during the WG.
> Although I can't remember the exat words, I believe the 
> question was something like "is the RSVP work discussed in 
> the TSVWG useful?"  or "is the RSVP work discussed in the 
> TSVWG of interest to this audience?".
> I thought the "Hum-level" was clearly quite high. So my 
> impression is that we had settled on that question and that 
> there is agreement in progressing this work.
> Am I missing something?
> 
> I think James' question is rather about whether this should 
> be done under TSVWG or in some other group. Personally, I 
> would suggest keeping it under TSVWG until there is a 
> specific reason to change (e.g. there is a shortage of time 
> to present/discuss all the items under TSVWG).
> 
> Cheers
> 
> Francois
> 
> >> 
> >> --
> >> Ted Faber
> >> http://www.isi.edu/~faber           PGP: 
> >> http://www.isi.edu/~faber/pubkeys.asc
> >> Unexpected attachment on this mail? See 
> >> http://www.isi.edu/~faber/FAQ.html#SIG
> >> 
> 
> _______________________________________________
> 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  Tue Dec  7 13:28:39 2004
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 NAA03313;
	Tue, 7 Dec 2004 13:28:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbkBQ-0002UL-HK; Tue, 07 Dec 2004 13:35:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cbjnu-0003qp-Eq; Tue, 07 Dec 2004 13:11:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cbjcm-0001m9-8H
	for tsvwg@megatron.ietf.org; Tue, 07 Dec 2004 12:59:44 -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 MAA29893
	for <tsvwg@ietf.org>; Tue, 7 Dec 2004 12:59:40 -0500 (EST)
Received: from zcars04e.nortelnetworks.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbjjM-0001n0-H3
	for tsvwg@ietf.org; Tue, 07 Dec 2004 13:06:33 -0500
Received: from zbl6c002.us.nortel.com (zbl6c002.corpeast.baynetworks.com
	[132.245.205.52])
	by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP
	id iB7Hw9e25082; Tue, 7 Dec 2004 12:58:09 -0500 (EST)
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 WKL3NZGY; Tue, 7 Dec 2004 12:58:08 -0500
Message-Id: <6.0.3.0.0.20041207124216.04c1bfd8@zbl6c002.corpeast.baynetworks.com>
X-Sender: khchan@zbl6c002.corpeast.baynetworks.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
Date: Tue, 07 Dec 2004 12:58:08 -0500
To: =?gb2312?B?sszd7d3t?= <cbeibei@263.net>
From: Kwok Ho Chan <khchan@nortelnetworks.com>
Subject: Re: Re: Re: Re: [Tsvwg] some
	problemsaboutdraft-baker-diffserv-ba sic -classes-0 4
In-Reply-To: <20041207144422.235F2317D9@smtp.263.net>
References: <20041207144422.235F2317D9@smtp.263.net>
Mime-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9361ae25efd9cff62e36f70ef966350e
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>
Content-Type: multipart/mixed; boundary="===============0663358374=="
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e9051aca6d23a9cf6df09e1ef4738712

--===============0663358374==
Content-Type: multipart/alternative;
	boundary="=====================_10731340==.ALT"

--=====================_10731340==.ALT
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable

Cai Bei-Bei:
We are not saying AF3x is "higher priority" than CS3.
We are just indicating that the 2 service classes need to be treated=20
differently
in parts of the end-to-end path.
We are not saying how many queues and what the queue scheduling algorithm=20
must be.
Hence we are not saying AF3x must be scheduled ahead of CS3.
-- Kwok Ho --

At 09:43 AM 12/7/2004, =3D?gb2312?B?sszd7d3t?=3D wrote:
>Kwok Ho :
>
>Thank your help!
>
>In your previous letter, you said :"We have found that the Loss Tolerance=
=20
>for these traffic(Broadcast Video service)
>  is relatively lower than Multimedia Streaming service class." Does this=
=20
> sentence mean that the broadcast video service need
>lower packet loss than Multimedia Streaming service class? If it is yes, I=
=20
>think it is more reasonable that
>broadcast video service have a higher priority. But broadcast video servie=
=20
>is CS3,whose priority is lower than
>than Multimedia Streaming service(AF3).Do it have some antinomy?
>
>Thanks a lot!
>best regards!
>                                                                   cai=
 Bei-Bei
>
>=A1=A1=A1=A1
>
>=3D=3D=3D=3D=3D=3D=3D=3D 2004-12-06 23:28:11 =C4=FA=D4=DA=C0=B4=D0=C5=D6=D0=
=D0=B4=B5=C0=A3=BA =3D=3D=3D=3D=3D=3D=3D=3D
>
>>Bei-Bei:
>>Please notice I have added this thread to the TSVWG mailing list.
>>Please see response embedded below.
>>Any additional input are welcomed.
>>Thanks!
>>-- Kwok Ho --
>>
>>At 10:39 PM 12/4/2004, =3D?gb2312?B?sszd7d3t?=3D wrote:
>>>Kwok Ho:
>>>
>>>Thank you very much for your so detailed answer.
>>>Your help have resolved some questions I had.
>>>Of course,you can put this conversation back onto the TSVWG mailing=
 list.:)
>>>
>>>And,may I understand the draft as follow : the gradation of traffic=20
>>>priority from high to low is
>>>  CS7,CS6.EF,CS5.AF4,CS4,AF3,CS3,AF2,CS2,AF1,CS0(DF),CS1?
>>
>>I think you can say that.  But in reality, IMHO, the network needs to=20
>>make sure it
>>upholds the promise it gave to its customer, no matter which service=20
>>class it is.
>>This may mean the network needs to admit less traffic that goes into=20
>>service class using
>>EF so the service classes using CS4 and AF4x will still uphold the=20
>>promise to its users.
>>The decision is on which service classes a network supports (they don't=20
>>need to support
>>all the service classes) and how much of each.
>>
>>>I have cleared about those service classes except for the Broadcast=20
>>>Video Service Class.
>>>Based on the draft,Broadcast video is inelastic traffic,and Multimedia=20
>>>Streaming is elastic.
>>>Why do the former use CS3 and the latter use AF3?
>>>And in 4.2.1 part of draft-baker-diffserv-basic-classes-02, the=20
>>>Multimedia Streaming class include
>>>the Broadcast video service.What is the reason for separating the=20
>>>broadcast video from the multimedia streaming
>>>in draft-baker-diffserv-basic-classes-03(and 04) ?
>>
>>Broadcast Video service class is meant for High Definition broadcasts and=
=20
>>the likes.
>>We have found that the Loss Tolerance for these traffic is relatively=20
>>lower than Multimedia
>>Streaming service class.  Hence its separation.  Again this is based on=20
>>what the application
>>requires of the network.  At low loss high capacity parts of the network,=
=20
>>both of these
>>service classes may get treated together without impact to the promises=20
>>made to the
>>user of each service class (discussion for the service class aggregation=
=20
>>draft).
>>
>>>
>>>Thank you very much!
>>>
>>>
>>>
>>>                                                                   Cai=20
>>> bei-bei
>>>ps:Best wishes to you!
>>>=A1=A1=A1=A1
>>>
>>>
>>>=3D=3D=3D=3D=3D=3D=3D=3D 2004-12-02 23:49:52 =C4=FA=D4=DA=C0=B4=D0=C5=D6=
=D0=D0=B4=B5=C0=A3=BA =3D=3D=3D=3D=3D=3D=3D=3D
>>>
>>>>Bei-Bei:
>>>>Agree that they all need low delay, low jitter.
>>>>Other factors that affects the service classes placement are loss=20
>>>>tolerance, traffic elasticity,
>>>>and packet size (and its variation).
>>>>
>>>>Telephony uses EF. the Multimedia Conferencing uses AF because it is=20
>>>>elastic traffic.
>>>>There is also the Real-Time Interactive class using CS4 that handles=20
>>>>inelastic video traffic.
>>>>Please reference Figure 1 of
>>>>=20
>>>>http://www.ietf.org/internet-drafts/draft-baker-diffserv-basic-classes-0=
4.txt
>>>>
>>>>EF PHB normally get deployed with some kind of upper limit on the=20
>>>>traffic it treats, either
>>>>with some policer, rate limiter, and/or some other admission control=20
>>>>methods.
>>>>With this in mind, the EF traffic should not starve the AF4x and CS4=20
>>>>traffic.  Each should
>>>>forward the traffic as configured (one may not want to have too much EF=
=20
>>>>traffic that will
>>>>add too much delay to the CS4 and AF4x traffic making them=20
>>>>un-acceptable).  Without
>>>>having the elastic traffic adversely affecting the inelastic=20
>>>>traffic.  Or having large packets
>>>>adding too much jitter to small inelastic traffic.
>>>>
>>>>This draft takes the points of view of how each application using the=20
>>>>different service classes
>>>>will receive the network treatment it requires (end to end), when=20
>>>>traffic in multiple service classes
>>>>need to share the network.  When these traffic traverse both low and=20
>>>>high capacity networks/links.
>>>>
>>>>There is another draft that discusses how in high capacity=20
>>>>networks/links, multiple service classes
>>>>can be aggregated together.  I have published -00 version of this draft=
=20
>>>>but I am in the process of
>>>>updating this draft to add more content and making changes based on the=
=20
>>>>comments received.
>>>>I would advise to wait for the -01 of=
 draft-chan-tsvwg-diffserv-class-aggr.
>>>>
>>>>I hope this help to answer/resolve the questions/issues you have.
>>>>
>>>>Also, can I put this conversation back onto the TSVWG mailing list?
>>>>
>>>>Thank you!
>>>>-- Kwok Ho --
>>>>
>>>>
>>>>At 08:17 AM 12/2/2004, =3D?gb2312?B?sszd7d3t?=3D wrote:
>>>>>Kwok Ho Chan:
>>>>>
>>>>>Thank you for your answers.
>>>>>Yes,I am a student of Nanjing University of Posts and=20
>>>>>Telecommunications of China.
>>>>>Now we are doing a project about end-to-end IP QoS.
>>>>>
>>>>>Every service has different QoS requirement.So it will be classed, and=
=20
>>>>>deployed with DSCP, then be treated differently based on the different=
 class.
>>>>>Voice and Vedio require real-time, very low delay, very low=20
>>>>>jitter,which must use EF PHB.So I am
>>>>>puzzled that Multimedia Conferencing use AF PHB. Services have lower=20
>>>>>priority ,they may wait in a queue for a longer time, which will bring=
=20
>>>>>higher delay. The same question exist between multimedia  streaming=20
>>>>>and broadcast video and so on.
>>>>>
>>>>>We want to use the draft to class services, and deal with these based=
=20
>>>>>on the DSCP.
>>>>>
>>>>>=A1=A1=A1=A1Thank you very much!!
>>>>>
>>>>>=3D=3D=3D=3D=3D=3D=3D=3D 2004-11-24 22:54:53 =C4=FA=D4=DA=C0=B4=D0=C5=
=D6=D0=D0=B4=B5=C0=A3=BA =3D=3D=3D=3D=3D=3D=3D=3D
>>>>>
>>>>>>Bei-Bei:
>>>>>>Thank you for your comments.
>>>>>>I think you mis-understood the concepts.
>>>>>>The basic-classes draft separates the traffic into different classes
>>>>>>based on their traffic characteristics.
>>>>>>It does not necessarily mean Multimedia Conferencing is lower than=20
>>>>>>Telephony,
>>>>>>they just needs to be separated.
>>>>>>We also recommend some treatment approaches for each Service Class=
 based
>>>>>>on each of their traffic characteristics.
>>>>>>Please look at (read) the draft this way and let us know if think=20
>>>>>>differently.
>>>>>>Thanks!
>>>>>>-- Kwok Ho Chan --
>>>>>>p.s. Are you based in China?  It looks like a Chinese name to me.
>>>>>>       How may you want to use this draft?
>>>>>>
>>>>>>
>>>>>>At 09:18 AM 11/24/2004, =3D?gb2312?B?sszd7d3t?=3D wrote:
>>>>>>
>>>>>>>Hi:
>>>>>>>
>>>>>>>   I have some problems about draft-baker-diffserv-basic-classes-04.
>>>>>>>
>>>>>>>   1.Why is the priority of Multimedia Conferencing(eg.H.323/V2=20
>>>>>>> Video conferencing) lower than telephone? The former(video)=20
>>>>>>> sometimes need very low delay,eg.CBR video.
>>>>>>>
>>>>>>>   2 Usually,the signalling precede the corresponding service. Why=20
>>>>>>> does the service class signalling have a lower priority than=20
>>>>>>> telephone? And i also don't know why the QAM is behind Low=20
>>>>>>> Latency  data,and the broadcast video is behind multimedia=20
>>>>>>> streaming?In my concepte,broadcast video is include in multimeida=20
>>>>>>> streaming and need less delay.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>   Thank you very much!!
>>>>>>>
>>>>>>>
>>>>>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1
>>>>>>>
>>>>>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1Cai Bei-bei
>>>>>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1cbeibei@263.net
>>>>>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12004-11-2=
4
>>>>>>>
>>>>>>>
>>>>>
>>>>>=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D=
 =3D =3D =3D =3D
>>>>>
>>>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=D6=C2
>>>>>=C0=F1=A3=A1
>>>>>
>>>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A1=B2=CC=DD=ED=DD=ED
>>>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A1<mailto:cbeibei@263.net>cbeibei@263.net
>>>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A1=A1=A12004-12-02
>>>>>
>>>
>>>=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D
>>>
>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=D6=C2
>>>=C0=F1=A3=A1
>>>
>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=B2=CC=DD=ED=DD=ED
>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1<mailto:cbeibei@263.net>cbeibei@263.net
>>>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A1=A12004-12-03
>>>
>
>=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D=
 =3D =3D =3D
>
>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=D6=C2
>=C0=F1=A3=A1
>
>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=B2=CC=DD=ED=DD=ED
>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1<mailto:cbeibei@263.net>cbeibei@263.net
>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A12004-12-07
>

--=====================_10731340==.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<body>
Cai Bei-Bei:<br>
We are not saying AF3x is &quot;higher priority&quot; than CS3.<br>
We are just indicating that the 2 service classes need to be treated
differently<br>
in parts of the end-to-end path.<br>
We are not saying how many queues and what the queue scheduling algorithm
must be.<br>
Hence we are not saying AF3x must be scheduled ahead of CS3.<br>
-- Kwok Ho --<br><br>
At 09:43 AM 12/7/2004, =3D?gb2312?B?sszd7d3t?=3D wrote:<br>
<blockquote type=3Dcite class=3Dcite cite><font size=3D2>Kwok Ho :<br>
</font>&nbsp;<br>
<font size=3D2>Thank your help!<br>
</font>&nbsp;<br>
<font size=3D2>In your previous letter, you said :&quot;We have found that
the Loss Tolerance for these traffic(Broadcast Video service)<br>
&nbsp;is relatively lower than Multimedia Streaming service class.&quot;
Does this sentence mean that the broadcast video service need<br>
lower packet loss than Multimedia Streaming service class? If it is yes,
I think it is more reasonable that<br>
broadcast video service have a higher priority. But broadcast video
servie is CS3,whose priority is lower than <br>
than Multimedia Streaming service(AF3).Do it have some antinomy?<br>
</font>&nbsp;<br>
<font size=3D2>Thanks a lot!<br>
best regards!<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
cai Bei-Bei<br>
</font>&nbsp;<br>
<font size=3D2>=A1=A1=A1=A1<br>
</font>&nbsp;<br>
<font size=3D2>=3D=3D=3D=3D=3D=3D=3D=3D 2004-12-06 23:28:11 =C4=FA=D4=DA=C0=
=B4=D0=C5=D6=D0=D0=B4=B5=C0=A3=BA =3D=3D=3D=3D=3D=3D=3D=3D<br>
</font>&nbsp;<br>
<blockquote type=3Dcite class=3Dcite cite><font size=3D2>Bei-Bei:<br>
Please notice I have added this thread to the TSVWG mailing list.<br>
Please see response embedded below.<br>
Any additional input are welcomed.<br>
Thanks!<br>
-- Kwok Ho --<br><br>
At 10:39 PM 12/4/2004, =3D?gb2312?B?sszd7d3t?=3D wrote:<br>
<blockquote type=3Dcite class=3Dcite cite>Kwok Ho:<br>
&nbsp;<br>
Thank you very much for your so detailed answer.<br>
Your help have resolved some questions I had.<br>
Of course,you can put this conversation back onto the TSVWG mailing
list.:)<br>
&nbsp;<br>
And,may I understand the draft as follow : the gradation of traffic
priority from high to low is<br>
&nbsp;CS7,CS6.EF,CS5.AF4,CS4,AF3,CS3,AF2,CS2,AF1,CS0(DF),CS1?</blockquote><b=
r>
I think you can say that.&nbsp; But in reality, IMHO, the network needs
to make sure it<br>
upholds the promise it gave to its customer, no matter which service
class it is.<br>
This may mean the network needs to admit less traffic that goes into
service class using<br>
EF so the service classes using CS4 and AF4x will still uphold the
promise to its users.<br>
The decision is on which service classes a network supports (they don't
need to support<br>
all the service classes) and how much of each.<br><br>
<blockquote type=3Dcite class=3Dcite cite>I have cleared about those service
classes except for the Broadcast Video Service Class.<br>
Based on the draft,Broadcast video is inelastic traffic,and Multimedia
Streaming is elastic.<br>
Why do the former use CS3 and the latter use AF3?<br>
And in 4.2.1 part of <i>draft-baker-diffserv-basic-classes-02</i>, the
Multimedia Streaming class include<br>
the Broadcast video service.What is the reason for separating the
broadcast video from the multimedia streaming <br>
in <i>draft-baker-diffserv-basic-classes-03(and 04)
</i>?</blockquote><br>
Broadcast Video service class is meant for High Definition broadcasts and
the likes.<br>
We have found that the Loss Tolerance for these traffic is relatively
lower than Multimedia<br>
Streaming service class.&nbsp; Hence its separation.&nbsp; Again this is
based on what the application<br>
requires of the network.&nbsp; At low loss high capacity parts of the
network, both of these<br>
service classes may get treated together without impact to the promises
made to the<br>
user of each service class (discussion for the service class aggregation
draft).&nbsp; <br><br>
<blockquote type=3Dcite class=3Dcite cite><br>
Thank you very much!<br>
&nbsp;<br>
&nbsp;<br>
&nbsp;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;
Cai bei-bei<br>
ps:Best wishes to you!<br>
=A1=A1=A1=A1<br>
&nbsp;<br>
&nbsp;<br>
=3D=3D=3D=3D=3D=3D=3D=3D 2004-12-02 23:49:52 =C4=FA=D4=DA=C0=B4=D0=C5=D6=D0=
=D0=B4=B5=C0=A3=BA =3D=3D=3D=3D=3D=3D=3D=3D<br>
&nbsp;<br>
<blockquote type=3Dcite class=3Dcite cite>Bei-Bei:<br>
Agree that they all need low delay, low jitter.<br>
Other factors that affects the service classes placement are loss
tolerance, traffic elasticity,<br>
and packet size (and its variation). <br><br>
Telephony uses EF. the Multimedia Conferencing uses AF because it is
elastic traffic.<br>
There is also the Real-Time Interactive class using CS4 that handles
inelastic video traffic.<br>
Please reference Figure 1 of<br>
&nbsp;
<a=
 href=3D"http://www.ietf.org/internet-drafts/draft-baker-diffserv-basic-clas=
ses-04.txt"=
 eudora=3D"autourl">http://www.ietf.org/internet-drafts/draft-baker-diffserv=
-basic-classes-04.txt</a><br><br>
EF PHB normally get deployed with some kind of upper limit on the traffic
it treats, either<br>
with some policer, rate limiter, and/or some other admission control
methods.<br>
With this in mind, the EF traffic should not starve the AF4x and CS4
traffic.&nbsp; Each should<br>
forward the traffic as configured (one may not want to have too much EF
traffic that will<br>
add too much delay to the CS4 and AF4x traffic making them
un-acceptable).&nbsp; Without<br>
having the elastic traffic adversely affecting the inelastic
traffic.&nbsp; Or having large packets<br>
adding too much jitter to small inelastic traffic.<br><br>
This draft takes the points of view of how each application using the
different service classes<br>
will receive the network treatment it requires (end to end), when traffic
in multiple service classes<br>
need to share the network.&nbsp; When these traffic traverse both low and
high capacity networks/links. <br><br>
There is another draft that discusses how in high capacity
networks/links, multiple service classes<br>
can be aggregated together.&nbsp; I have published -00 version of this
draft but I am in the process of<br>
updating this draft to add more content and making changes based on the
comments received.<br>
I would advise to wait for the -01 of
draft-chan-tsvwg-diffserv-class-aggr.<br><br>
I hope this help to answer/resolve the questions/issues you
have.<br><br>
Also, can I put this conversation back onto the TSVWG mailing
list?<br><br>
Thank you!<br>
-- Kwok Ho --<br><br>
<br>
At 08:17 AM 12/2/2004, =3D?gb2312?B?sszd7d3t?=3D wrote:<br>
<blockquote type=3Dcite class=3Dcite cite>Kwok Ho Chan:<br>
&nbsp;<br>
Thank you for your answers.<br>
Yes,I am a student of Nanjing University of Posts and Telecommunications
of China.<br>
Now we are doing a project about end-to-end IP QoS.<br>
&nbsp;<br>
Every service has different QoS requirement.So it will be classed, and
deployed with DSCP, then be treated differently based on the different
class.<br>
Voice and Vedio require real-time, very low delay, very low jitter,which
must use EF PHB.So I am <br>
puzzled that Multimedia Conferencing use AF PHB. Services have lower
priority ,they may wait in a queue for a longer time, which will bring
higher delay. The same question exist between multimedia&nbsp; streaming
and broadcast video and so on.<br>
&nbsp;<br>
We want to use the draft to class services, and deal with these based on
the DSCP.&nbsp; <br>
&nbsp;<br>
=A1=A1=A1=A1Thank you very much!! <br>
&nbsp;<br>
=3D=3D=3D=3D=3D=3D=3D=3D 2004-11-24 22:54:53 =C4=FA=D4=DA=C0=B4=D0=C5=D6=D0=
=D0=B4=B5=C0=A3=BA =3D=3D=3D=3D=3D=3D=3D=3D<br>
&nbsp;<br>
<blockquote type=3Dcite class=3Dcite cite>Bei-Bei:<br>
Thank you for your comments.<br>
I think you mis-understood the concepts.<br>
The basic-classes draft separates the traffic into different=20
classes<br>
based on their traffic characteristics.<br>
It does not necessarily mean Multimedia Conferencing is lower than
Telephony,<br>
they just needs to be separated.<br>
We also recommend some treatment approaches for each Service Class
based<br>
on each of their traffic characteristics.<br>
Please look at (read) the draft this way and let us know if think
differently.<br>
Thanks!<br>
-- Kwok Ho Chan --<br>
p.s. Are you based in China?&nbsp; It looks like a Chinese name to
me.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; How may you want to use this
draft?<br><br>
<br>
At 09:18 AM 11/24/2004, =3D?gb2312?B?sszd7d3t?=3D wrote:<br><br>
<blockquote type=3Dcite class=3Dcite cite>Hi: <br><br>
&nbsp; I have some problems about draft-baker-diffserv-basic-classes-04.
<br><br>
&nbsp; 1.Why is the priority of Multimedia Conferencing(eg.H.323/V2 Video
conferencing) lower than telephone? The former(video) sometimes need very
low delay,eg.CBR video. <br><br>
&nbsp; 2 Usually,the signalling precede the corresponding service. Why
does the service class signalling have a lower priority than telephone?
And i also don't know why the QAM is behind Low Latency&nbsp; data,and
the broadcast video is behind multimedia streaming?In my
concepte,broadcast video is include in multimeida streaming and need less
delay.<br><br>
&nbsp; <br>
&nbsp; <br>
&nbsp; Thank you very much!! <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br><br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1 <br><br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1Cai Bei-bei <br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1cbeibei@263.net <br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12004-11-24=
 <br><br>
&nbsp; </blockquote></blockquote><br>
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D=
 =3D =3D =3D <br><br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=D6=C2<br>
=C0=F1=A3=A1<br>
&nbsp;<br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=B2=CC=DD=ED=DD=ED<br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1<a href=3D"mailto:cbeibei@263.net">cbeibei@263.net</a><br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A12004-12-02<br>
&nbsp;</blockquote></blockquote><br>
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D=
 =3D =3D =3D <br><br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=D6=C2<br>
=C0=F1=A3=A1<br>
&nbsp;<br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=B2=CC=DD=ED=DD=ED<br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1<a href=3D"mailto:cbeibei@263.net">cbeibei@263.net</a><br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A12004-12-03<br>
&nbsp;</font></blockquote></blockquote><br>
<font size=3D2>=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D <br>
</font><br>
<font size=3D2>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=D6=C2<br>
=C0=F1=A3=A1<br>
</font>&nbsp;<br>
<font size=3D2>=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A1=A1=A1=A1=B2=CC=DD=ED=DD=ED<br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1<a href=3D"mailto:cbeibei@263.net">cbeibei@263.net</a><br>
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A12004-12-07<br>
</font>&nbsp;</blockquote></body>
</html>

--=====================_10731340==.ALT--



--===============0663358374==
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

--===============0663358374==--




From tsvwg-bounces@ietf.org  Wed Dec  8 02:19:37 2004
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 CAA14155;
	Wed, 8 Dec 2004 02:19:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbwDa-0006E1-9L; Wed, 08 Dec 2004 02:26:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cbw2g-0003H0-Mo; Wed, 08 Dec 2004 02:15:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbvyR-0001uF-35
	for tsvwg@megatron.ietf.org; Wed, 08 Dec 2004 02:10: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 CAA06254
	for <tsvwg@ietf.org>; Wed, 8 Dec 2004 02:10:53 -0500 (EST)
From: rezhirpavai@hssworld.com
Received: from spark.hss.co.in ([203.200.71.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbw51-000618-EK
	for tsvwg@ietf.org; Wed, 08 Dec 2004 02:17:52 -0500
Received: from spark.hss.co.in (localhost [127.0.0.1])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iB8779pT027554
	for <tsvwg@ietf.org>; Wed, 8 Dec 2004 12:37:09 +0530 (IST)
Received: from sandesh.hss.hns.com (sandesh [172.16.32.19])
	by spark.hss.co.in (8.12.10/8.12.10) with ESMTP id iB8778I4027544
	for <tsvwg@ietf.org>; Wed, 8 Dec 2004 12:37:08 +0530 (IST)
To: tsvwg@ietf.org
X-Mailer: Lotus Notes Release 6.5 September 26, 2003
Message-ID: <OFCDFADDF2.61919843-ON65256F64.0027179F-65256F64.0027919B@hssworld.com>
Date: Wed, 8 Dec 2004 12:38:01 +0530
X-MIMETrack: Serialize by Router on Sandesh/HSS(Release 6.0|September 26,
	2002) at 08/12/2004 01:00:43 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: rezhirpavai@hssworld.com, vibansal@hssworld.com
Subject: [Tsvwg] New SCTP Socket API extension draft for congestion handling
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.5 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c






Hello,
      We have submitted the following draft as an extension to SCTP
   socket API draft - draft-ietf-tsvwg-sctpsocket-09.txt.

   This draft defines SCTP Socket API to notify SCTP applications about
   SCTP association being congested. SCTP Protocol has been widely
   accepted by the VoIP forum. SIGTRAN protocols
   (M3UA/SUA/M2UA/M2PA etc) provide procedures for handling
   congestion notification from the SCTP Stack layer.

   This draft provides mechanism for SCTP applications to enable/
   disable notification of congestion indications over SCTP Socket
   Interface. This draft suggests notification to application at onset
   and abatement of congestion.

   The draft is available at:

http://www.ietf.org/internet-drafts/draft-vibansal-sctpsocket-congestion-00.txt

    Would request the members of Transport Area Working group to review the

    contents of the extension draft for completeness and correctness.

    This SCTP Socket API extension draft for congestion handling will
     definetely help any SCTP application in controlling the congestion by
     initiating flow control on occurance of congestion.

    Regards,
    - R. Ezhirpavai
   Hughes Software Systems - A Flextronics Company
   (www.hssworld.com)


***********************  HSS-Unclassified   ***********************
"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended solely for the use of the individual to whom it is
addressed. It may contain  privileged or confidential information and
should not be circulated or used for any purpose other than for what it is
intended. If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient, you are
notified that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. HSS accepts no responsibility for
loss or damage arising from the use of the information transmitted by this
email including damage from virus."


"Please note:The email domain of Hughes Software Systems Ltd. has been changed to "hssworld.com" from hss.hns.com"

"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended 
solely for the use of the individual to whom it is addressed. It may contain  privileged or 
confidential information and should not be circulated or used for any purpose other than for 
what it is intended. If you have received this message in error, please notify the originator 
immediately. If you are not the intended recipient, you are notified that you are strictly 
prohibited from using, copying, altering, or disclosing the contents of this message. HSS 
accepts no responsibility for loss or damage arising from the use of the information transmitted 
by this email including damage from virus."

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


From tsvwg-bounces@ietf.org  Fri Dec 10 07:09:48 2004
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 HAA08437;
	Fri, 10 Dec 2004 07:09:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ccji0-0003Ep-Ek; Fri, 10 Dec 2004 07:17:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcjXC-00035y-IN; Fri, 10 Dec 2004 07:06:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcjTD-0002W7-NN
	for tsvwg@megatron.ietf.org; Fri, 10 Dec 2004 07:02:00 -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 HAA08070
	for <tsvwg@ietf.org>; Fri, 10 Dec 2004 07:01:56 -0500 (EST)
From: louise.burness@bt.com
Received: from smtp1.smtp.bt.com ([217.32.164.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcjaO-00036p-U0
	for tsvwg@ietf.org; Fri, 10 Dec 2004 07:09:25 -0500
Received: from i2km97-ukbr.domain1.systemhost.net ([193.113.197.30]) by
	smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.80); 
	Fri, 10 Dec 2004 12:02:45 +0000
Received: from i2km41-ukdy.domain1.systemhost.net ([193.113.30.29]) by
	i2km97-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(5.0.2195.6713); Fri, 10 Dec 2004 12:02:44 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Tsvwg] Reviews of RSVP extensions (here, there, or ... ?)
Date: Fri, 10 Dec 2004 12:02:44 -0000
Message-ID: <0AAF93247C75E3408638B965DEE11A700BABB21C@i2km41-ukdy.domain1.systemhost.net>
Thread-Topic: [Tsvwg] Reviews of RSVP extensions (here, there, or ... ?)
Thread-Index: AcTXLat7sPz0bPkCSMG6oUgMMnO95gFEk7pgABF76EAAimx4YA==
To: <pratik.bose@lmco.com>, <flefauch@cisco.com>, <faber@ISI.EDU>,
        <jmanner@cs.Helsinki.FI>
X-OriginalArrivalTime: 10 Dec 2004 12:02:44.0754 (UTC)
	FILETIME=[28745720:01C4DEB0]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: quoted-printable
Cc: nitin@jungle.bt.co.uk, jmpolk@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.3 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: quoted-printable


So, there is interest (well I might be interested anyway) and the
suggestion is that discussion should be via TSVWG to start with at
least?

OK then James, what extensions to RSVP are you wanting to be looked at?

Louise

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org]=20
> On Behalf Of Bose, Pratik
> Sent: 07 December 2004 17:58
> To: Francois Le Faucheur (flefauch); Ted Faber; Jukka MJ Manner
> Cc: James Polk (jmpolk); tsvwg
> Subject: RE: [Tsvwg] Reviews of RSVP extensions (here, there,=20
> or ... ?)
>=20
>=20
> Actually I do remember the hum-test that Francois mentions,=20
> and I also recall that a counter hum-test was taken for the=20
> same question below (for those in favor of not supporting=20
> this work here) and there was barely a hum for that - so I am=20
> not sure whether the interest being low is really correct. I=20
> am sure the minutes can confirm this info....
>=20
> > -----Original Message-----
> > From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org]
> > On Behalf Of Francois Le Faucheur (flefauch)
> > Sent: Tuesday, December 07, 2004 4:48 AM
> > To: Ted Faber; Jukka MJ Manner
> > Cc: James Polk (jmpolk); tsvwg
> > Subject: RE: [Tsvwg] Reviews of RSVP extensions (here, there,=20
> > or ... ?)
> >=20
> > Hello,
> > =20
> > >> My impression hasn't been that there's been a shortage of time to
> > >> present or discuss these drafts in TSVWG, but a low=20
> > interest level.
> > >> I'm not sure that a new group would address that.
> > >>=20
> > >> That's an impression; I could be way off.
> >=20
> > I remember a "Hum-test" was run during the WG.
> > Although I can't remember the exat words, I believe the
> > question was something like "is the RSVP work discussed in=20
> > the TSVWG useful?"  or "is the RSVP work discussed in the=20
> > TSVWG of interest to this audience?".
> > I thought the "Hum-level" was clearly quite high. So my=20
> > impression is that we had settled on that question and that=20
> > there is agreement in progressing this work.
> > Am I missing something?
> >=20
> > I think James' question is rather about whether this should
> > be done under TSVWG or in some other group. Personally, I=20
> > would suggest keeping it under TSVWG until there is a=20
> > specific reason to change (e.g. there is a shortage of time=20
> > to present/discuss all the items under TSVWG).
> >=20
> > Cheers
> >=20
> > Francois
> >=20
> > >>=20
> > >> --
> > >> Ted Faber
> > >> http://www.isi.edu/~faber           PGP:=20
> > >> http://www.isi.edu/~faber/pubkeys.asc
> > >> Unexpected attachment on this mail? See
> > >> http://www.isi.edu/~faber/FAQ.html#SIG
> > >>=20
> >=20
> > _______________________________________________
> > tsvwg mailing list
> > tsvwg@ietf.org
> > https://www1.ietf.org/mailman/listinfo/tsvwg
> >=20
>=20
> _______________________________________________
> tsvwg mailing list
> tsvwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/tsvwg
>=20

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


From tsvwg-bounces@ietf.org  Fri Dec 10 13:30:25 2004
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 NAA05108;
	Fri, 10 Dec 2004 13:30:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcpeP-0002Iz-Ab; Fri, 10 Dec 2004 13:37:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcpMJ-00066K-Vd; Fri, 10 Dec 2004 13:19:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcpFQ-0003kN-J9
	for tsvwg@megatron.ietf.org; Fri, 10 Dec 2004 13:12:08 -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 NAA03612
	for <tsvwg@ietf.org>; Fri, 10 Dec 2004 13:12:05 -0500 (EST)
Message-Id: <200412101812.NAA03612@ietf.org>
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcpMe-0001tW-Rt
	for tsvwg@ietf.org; Fri, 10 Dec 2004 13:19:37 -0500
Received: from localhost ([127.0.0.1] helo=psg.com)
	by psg.com with esmtp (Exim 4.43 (FreeBSD))
	id 1CcpFO-000EGs-M1; Fri, 10 Dec 2004 18:12:06 +0000
To: tsvwg@ietf.org
Date: Fri, 10 Dec 2004 10:12:01 -0800
From: Allison Mankin <mankin@psg.com>
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 65215b440f7ab00ca9514de4a7a89926
Cc: jon.peterson@neustar.biz
Subject: [Tsvwg] draft TSVWG Minutes - IETF 61
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: 3b8eea209b62bd15620865bc4fbef8cd

Hi, TSVWG folks,

Here are the minutesfrom the DC meeting - we can update them in
the proceedings, so please send any items for update.  Thank you to
Gorry for the great notes, which I edited only lightly.

Are you "?" in the discussions below?  Identities welcome.

Now the actions from these notes need doing - Jon
and I are reviewing the charter actions; we can't take new working
group drafts without IESG/IAB review, after the WG recommends.  

Allison and Jon

-------- draft ----------

Transport Area WG (tsvwg)

These notes were kindly and expertly scribed by Gorry Fairhurst.
Any errors have been edited in by the Chairs, of course.

TSVWG Wednesday, November 10 at 1530-1730
=========================================

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

* Agenda bashing/Notetaker/Intro (chairs)
JP: No changes.
-------

* RSVP Bandwidth reduction
http://www.ietf.org/internet-drafts/draft-polk-tsvwg-rsvp-bw-reduction-00.txt
James Polk 

RSVP sets up reservations based on many properties. Presentation shows how
to reduce the bandwidth of an allocated flow. Open issues - what happens if
ResvErr is not responded to?

Aaron: Why RSVP rather than NSIS?
James Polk: RSVP has running code.
Fred Baker (FB): NSIS has not chosen to work on these issues.
AM: What are the issues we need to work on in NSIS?
FB: Ability to pre-empt, etc.

JP: How many people have read this ID?
A few people.
JP: How many neglected to put their hands up?
None.
AM: I'd like more people to read things.
?: How many people have read the prior version?
Few.
JP: Hum called (among those who had read this).
There was a substantial hum supporting this proposal to the IESG as a
TSVWG work item.

-------

* Wide-Area Network
http://www.ietf.org/internet-drafts/
draft-baker-tsvwg-vpn-signaled-preemption-01.txt

Fred Baker (FB)
Tunnels are common in military networks, and multiple layered tunnels
between enclaves are common. There is a real need to do pre-emption here.
The problem with RSVP is that you would have to traditionally remove the
flow (from a crypto), and all the calls would suffer. Race conditions occur
too. We'd be interested in this also being a WG document.
Joe Touch (JT): In slide 3, you have tunnels over tunnels - and this is
something I am familiar with in the Xbone. In the next slide, this layering
doesn't appear?
FB: This diagram is simpler, read the document, it's recursive.
JT: This has 2 levels?
FB: Yes, this slide. I am telling you the environment that is the reason for
doing what James wants to.

JP: How many people have read the ID?
10 or so.
AM/JP: Would anyone like to support this? Does anyone have views?
?: I have not read this, but from what I see, I would support this.
Jacob: Is the ID in the repository?
JP: Yes, it's there - see the URL on the list. (There was a line-break in
the URL.)

JP: How do we proceed?
?: VPNs are common - both in military and civil nets. RSVP is also becoming
more common.
Aaron Falk (AF): So, here is a process comment: A similar issue came up in
the TCPM WG with an ID and there was a small number of supporters - we
considered a possibility of getting reviewers to assess and report on the
draft, to see if the document was useful to pursue in the group.
?2: There are a small set of people building real solutions, and this
community will benefit from tackling these issues.
JT: If there are not that many people interested in this at this meeting, it
means the IETF is not involved in the issues.
AF: Is this informed apathy or ... apathy?
JT: You're getting a signal that this is not in that interest (so the
document could be informational).
Melissa Shore (MS): I think this is Informational. It's here in tsvwg,
because RSVP expertise is here, although what worries me is it is a complex
architecture - there is a judgment call on complexity. I'm nervous on IPSsec
with different applications and mixing features in a short document - I want
many reviewers.
JP: The IETF is a community of volunteers. Where there is energy, we do
work, and help this to become a productive work.
MS: It's nearly impossible to stop bad work. It shouldn't be this easy to
kill good work.
MS: This merits a WG review and process time.
Tom Henderson (TH): I'd like to support this - it is an important problem
with my company (Boeing). RFCs help prevent peculiar solutions to problems.
AM: We can work on this problem in TSVWG, but we should ensure the NSIS WG
is fully aware of this work.

Jose Bart (JB): Scott Bradner said that pre-emption was a bad concept, in a
previous meeting.
FB: In this particular case, pre-emption is going to happen: There are
important critical (life-saving) cases.
JT: This work is relevant to a large customer (military).
AM: Hard pre-emption on a global inter-domain case is a hard problem. Can't
we do something at the link-layer to get some of this support? -
Implementing inter-domain pre-emption needs to address many problems. We
could do several sessions at the IETF on this.
?: Should we hold a BoF on pre-emption?
AM: No.  [I think I tried to say because it needs to be cross-area].
?: If we go this way, this will in future become an interoperable problem.
JP: RSVP already supports pre-emption.
AM: RSVP put pre-emption in where COPS used RSVP in a third-party, policy
managed manner - it was not generic.
Ted: What is the case against doing this?
JP: The ADs wanted this WG to open-up and do some thinking, we've done this:
The can is open now.
JT: Can we organise a WG meeting for the people who care and avoid the tsvwg
getting bogged down.
JP: I think it is important for these issues to go in front of the people in
the tsvwg.
JP: I'd like to call a hum on doing this work?
Hum, in favour.

-------

* Diffserv Basic Classes
http://www.ietf.org/internet-drafts/draft-baker-diffserv-basic-classes-04.tx
t
Kok Ho Chan (KC)
Reviewers comments have been received - and there will be a new rev soon.
This document is close to completion - comments are requested from the WG.
Should this document be a BCP or INFO (WG or Individual)?

JP: Opinions please?
AM: The applications user community was asked for opinions on whether this
should become a BCP v. INFO and they will respond to the list.

JP: The IESG will ask us if the methods in the ID are a required way to do
these things: do we need to make this a BCP?
?: This draft is well written. Diffserv is being deployed. Can the carriers
using DS validate the classes, to make sure this makes sense.
FB: I've been to a variety of carriers and large enterprises to look at
this. The document was valuable to them - no one said they did not want the
document.
David Black: This is a well-written document, all my review comments have
been addressed. I don't know if the text is prescriptive or there may be
alternative ways of doing this.
?: I've been working with people who work with VoIP and knew nothing about
the networking aspects, and when shown this, they stopped asking stupid
questions...
JP: It certainly has informational value.
?: This is better published as informational, because it defines many
classes (a large set could cause confusions).
We got this feedback in a previous rev. The latest rev says you don't need
to support all the classes (you can aggregate several classes to a single
treatment).
Bruce Davie: Even if the text says so, people tend to jump straight to the
contents of a table. Publishing as INFO is a good warning to such people.
JP: I agree with Bruce, the warning text surrounding a table is often loss
when people cite a reference - this offers good guidance.
FB: We would like to prepare another rev.
JP: Is this next rev suitable for a WG document (as INFO)?
Humm - in favour of adopting this.

-------

* Quickstart
http://www.ietf.org/internet-drafts/draft-amit-quick-start-03.txt

Sally Floyd.
This draft was previously presented to the WG and expired. A fair amount of
work has been done since then, and this is now brought back to tsvwg. Data
was presented showing NS behaviour. A case made for using an IP-option.

JT: Would this be a good mechanism that could also be tied to XCP - so that
this becomes a mode.
SF: Quickstart is not a congestion control measure - the use is occasional,
normally at the start of a session. Quickstart is good at figuring out what
to do in starting conditions. XCP has more parts (and more power).
JT: If I run Quickstart now, and then later XCP is deployed, we could use
the XCP mechanisms with these methods. I'd rather see a single TCP
mechanism, if this can be done.
SF: XCP offers much more info. If you just want a larger initial window, you
don't need this info.
?: What does change when you do Active Queue Management (AQM)? Oscillation,
worse?
SF: No, there are no complications - You only say yes, if the AQM say there
is no standing queue.
Mark Handley (MH): Could we have a worse than best effort case using
diffserv, that would have the same benefit?
SF: You'd need to know that this code-point was supported, when the host
sends.
MH: If you know this, it should serve the same purpose.
SF: Lower than best effort has differences.
?: Lower than best effort can end up with head-of-line blocking, that would
cause an impact even with the lower class.

Gorry Fairhurst (GF): We need to consider tunnels that hide lower layer
router behaviours (see earlier talks on VPNs), and it's hard to know what
happens in tunnels.
SF: There are some mechanisms described to help this, if there are problems,
tell us.
GF: Will do, would be useful to talk about on the list.

JT: Two questions: Is this a Work item for tsvwg? Is it for PS?
JT: I'm hesitant at going to PS with things that modify TCP. I am in favour
of this being Experimental.
MH: This is an IP change *AND* a transport change - it needs wider review.
JP: Is this good for a WG work item?
Hummm 
JP: In favour of proposing this to IESG as a WG Item.
JP: Is this good for a PS?
Small Hummm 
JP: In favour of adopting as a PS, so it seems more feasible for taking
forward for Experimental.

-------

* Transport Mobility
http://www.ietf.org/internet-drafts/draft-eddy-tlmarch-00.txt

Wesley Eddy (WE)
This uses existing protocols for mobility using SIP, DNS, etc. Is there room
for another mobile IP protocol in the IETF?
Is this good for an Informational document?

JT: This does not cite any documents from the multi-6 WG, which did review
and document why this was not the way to this - because of the
shifting-sands problem with lower-layer decisions. This ID conflicts with
this.
WE: Yes, thanks for pointing this out.
TH: There are issues that need to change things at the transport layer -
this keeps coming up - this could be implementation specific, there's also
binding issues, do you need a general mechanism?
?: There is a (mobile-sctp) ID that describes the case where both end-points
are moving at the same time. You need a daemon to scan interfaces. The
Transport Layer is normally implemented in the Kernel.
?: Transport mobility is cheap to deploy.
JP: Several action items have been raised, please address these on on the
list.

-------

* XCP
http://www.ietf.org/internet-drafts/draft-falk-xcp-spec-00.txt

Aaron Falk
This is a research project, it is not an intended WG item. There is ns code,
web pages, and a mailing list that are open to discuss this topic. XCP uses
explicit signaling from XCP routers to find congestion in the network. A
feedback loop returns the discovered bottleneck allocation. There is work on
fair-sharing with TCP; split connections; etc. This ID is to make the
community aware of current work, and invite contributions.

-------

* SCTP NAT Traversal
http://www.ietf.org/internet-drafts/draft-xie-tsvwg-sctp-nat-00.txt

Qiaobing  Xie (QX)
Presentation reviewing guidelines and solutions for dealing with SCTP
association transversing NAT and similar middleboxes, and discussing
implications of traversing several NATs. Is this a good candidate for an
INFO document?

MS: If you are multi-homed - is a chunk sent on each address?
QX: No, only once.
MS: An inter-NAT protocol is really not a good idea.
QX: This is for future study.
MS: Just say, "don't do this" rather than "for future study".
JP: Please also send this to the behave WG (who know and are interested in
NATs) - you may receive good feedback.

-------

* RSVP for MPLS-TE
http://www.ietf.org/internet-drafts/draft-lefaucheur-rsvp-dste-01.txt
Francois Le Faucheur (FLF)
Presentation describing admission control for flows within MPLS Traffic
Engineering (TE) tunnels or MPLS Diffserv-aware MPLS Traffic Engineering
(DS-TE) Tunnels. The ID discusses aggregation of RSVP end-to-end
reservations. Reviewed changes from -00 to -01, including use of a RSVP
proxy to aggregate ingress to the tunnel. Open issues were described and
will align with Hierarchical LSP work. The authors would like to progress
this work in TSVWG. We should send a note to MPLS WG to ensure visibility of
this work within TSVWG.

AM: This (tsvwg) is the place were MPLS and Transport meet. My opinion is
that it is right to work on this here. Some clarifications are needed, for
different cases, etc. A new rev will help this to be clearer, and then the
transport area can better understand the issue. TSVWG'ers please do ASK
questions about this.
?: I don't understand what RSVP-TE is, and how this relates to RSVP - Since
RSVP-TE is not a product of TSVWG.
JP: No time to answer in the tsvwg meeting...
?: What is the difference with TE and DS?
FLF: The core is an MPLS DS core. MPLS did not create a new QoS mechanism in
the data plane.
?: This is good work.


JP: Meeting closed at 17:30.





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


From tsvwg-bounces@ietf.org  Fri Dec 10 16:39:55 2004
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 QAA00482;
	Fri, 10 Dec 2004 16:39:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ccsbo-000147-Ms; Fri, 10 Dec 2004 16:47:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcsOZ-00074U-IT; Fri, 10 Dec 2004 16:33:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcsGK-0000lK-2t
	for tsvwg@megatron.ietf.org; Fri, 10 Dec 2004 16:25: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 QAA26490
	for <tsvwg@ietf.org>; Fri, 10 Dec 2004 16:25:14 -0500 (EST)
Received: from nak.isi.edu ([128.9.168.79])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcsNa-0000H5-5g
	for tsvwg@ietf.org; Fri, 10 Dec 2004 16:32:46 -0500
Received: by nak.isi.edu (Postfix, from userid 3494)
	id 7D7A25BACC1; Fri, 10 Dec 2004 13:24:43 -0800 (PST)
Date: Fri, 10 Dec 2004 13:24:43 -0800
From: Aaron Falk <falk@isi.edu>
To: Allison Mankin <mankin@psg.com>
Subject: Re: [Tsvwg] draft TSVWG Minutes - IETF 61
Message-ID: <20041210212441.GE849@isi.edu>
Mail-Followup-To: Allison Mankin <mankin@psg.com>, tsvwg@ietf.org,
	jon.peterson@neustar.biz
References: <200412101812.NAA03612@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200412101812.NAA03612@ietf.org>
User-Agent: Mutt/1.4.2.1i
X-Cynicism-Level: 3
Organization: USC ISI
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: tsvwg@ietf.org, jon.peterson@neustar.biz
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

Al, Jon, Gorry-

Nice minutes.

Allison Mankin wrote:
> * XCP
> http://www.ietf.org/internet-drafts/draft-falk-xcp-spec-00.txt
> 
> Aaron Falk
> This is a research project, it is not an intended WG item. There is
> ns code,

insert: a BSD kernel implementation,

> web pages, and a mailing list that are open to discuss this topic. XCP uses
> explicit signaling from XCP routers to find congestion in the network. A
> feedback loop returns the discovered bottleneck allocation. There is work on
> fair-sharing with TCP; split connections; etc. This ID is to make the
> community aware of current work, and invite contributions.

please add: More info is available at http://www.isi.edu/isi-xcp

Many thanks,

--aaron

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


From tsvwg-bounces@ietf.org  Mon Dec 13 16:32:48 2004
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 QAA26479;
	Mon, 13 Dec 2004 16:32:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cdxw9-0003Aw-4K; Mon, 13 Dec 2004 16:40:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CdxZs-0001p2-Hx; Mon, 13 Dec 2004 16:17:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cdx2g-0006YW-Lk
	for tsvwg@megatron.ietf.org; Mon, 13 Dec 2004 15:43:39 -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 PAA16821
	for <tsvwg@ietf.org>; Mon, 13 Dec 2004 15:43:37 -0500 (EST)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdxAZ-000091-9Z
	for tsvwg@ietf.org; Mon, 13 Dec 2004 15:51:47 -0500
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 13 Dec 2004 21:50:41 +0100
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
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
	iBDKgvGd025007; Mon, 13 Dec 2004 21:43:01 +0100 (MET)
Received: from xmb-ams-333.cisco.com ([144.254.231.78]) by
	xbh-ams-331.cisco.com with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 13 Dec 2004 21:42:59 +0100
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
Subject: RE: [Tsvwg] draft TSVWG Minutes - IETF 61
Date: Mon, 13 Dec 2004 21:42:55 +0100
Message-ID: <A05118C6DF9320488C77F3D5459B17B7764A56@xmb-ams-333.emea.cisco.com>
Thread-Topic: [Tsvwg] draft TSVWG Minutes - IETF 61
Thread-Index: AcTe5nH6tNUHCJuNTcOcuLcREuGgYQCbOTXw
From: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>
To: <mankin@psg.com>, <jon.peterson@neustar.biz>
X-OriginalArrivalTime: 13 Dec 2004 20:42:59.0651 (UTC)
	FILETIME=[5538E130:01C4E154]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: quoted-printable
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: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: quoted-printable

Jon, Allison,

Regarding :=20
>> * RSVP for MPLS-TE
>> http://www.ietf.org/internet-drafts/draft-lefaucheur-rsvp-dste-01.txt


>> * RSVP for MPLS-TE:
I would suggest using the phrase "RSVP over MPLS-TE" instead of "RSVP
for MPLS-TE". MPLS-TE uses RSVP for establishment of TE tunnels; this is
a given. What we are talking about here is doing RSVP for end-to-end
flows "over" MPLS TE Tunnels.

>> ?: What is the difference with TE and DS?
I think it was Bob Braden who raised that question.

>> ?: This is good work.
I believe this refers to Jerry Ash's comment.

Cheers

Francois

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


From tsvwg-bounces@ietf.org  Mon Dec 13 20:58:49 2004
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 UAA18414;
	Mon, 13 Dec 2004 20:58:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ce25c-0000uV-QJ; Mon, 13 Dec 2004 21:07:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ce1ss-0004xF-7u; Mon, 13 Dec 2004 20:53:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ce1re-0004VZ-KL
	for tsvwg@megatron.ietf.org; Mon, 13 Dec 2004 20:52:34 -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 UAA18038
	for <tsvwg@ietf.org>; Mon, 13 Dec 2004 20:52:33 -0500 (EST)
Received: from pun.isi.edu ([128.9.160.150])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ce1zY-0000kJ-LW
	for tsvwg@ietf.org; Mon, 13 Dec 2004 21:00:46 -0500
Received: from pun.isi.edu (localhost [127.0.0.1])
	by pun.isi.edu (8.13.1/8.13.1) with ESMTP id iBE1qGtX001086;
	Mon, 13 Dec 2004 17:52:16 -0800 (PST)
	(envelope-from faber@pun.isi.edu)
Received: (from faber@localhost)
	by pun.isi.edu (8.13.1/8.13.1/Submit) id iBE1qGVR001085;
	Mon, 13 Dec 2004 17:52:16 -0800 (PST) (envelope-from faber)
Date: Mon, 13 Dec 2004 17:52:15 -0800
From: Ted Faber <faber@isi.edu>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: Re: [Tsvwg] Reviews of RSVP extensions (here, there, or ... ?)
Message-ID: <20041214015215.GA1033@pun.isi.edu>
References: <A05118C6DF9320488C77F3D5459B17B7357467@xmb-ams-333.emea.cisco.com>
Mime-Version: 1.0
In-Reply-To: <A05118C6DF9320488C77F3D5459B17B7357467@xmb-ams-333.emea.cisco.com>
User-Agent: Mutt/1.4.2.1i
X-url: http://www.isi.edu/~faber
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: "James Polk \(jmpolk\)" <jmpolk@cisco.com>,
        Jukka MJ Manner <jmanner@cs.Helsinki.FI>, tsvwg <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>
Content-Type: multipart/mixed; boundary="===============0353357194=="
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab


--===============0353357194==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="pf9I7BMVVzbSWLtt"
Content-Disposition: inline


--pf9I7BMVVzbSWLtt
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Dec 07, 2004 at 10:48:22AM +0100, Francois Le Faucheur (flefauch) wrote:
> Hello,
>  
> >> My impression hasn't been that there's been a shortage of time to
> >> present or discuss these drafts in TSVWG, but a low interest 
> >> level.  I'm
> >> not sure that a new group would address that.
> >> 
> >> That's an impression; I could be way off.
> 
> I remember a "Hum-test" was run during the WG.

The minutes support your position.  I plead poor memory and bias. :-)


-- 
Ted Faber
http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.asc
Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG 

--pf9I7BMVVzbSWLtt
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFBvkdPaUz3f+Zf+XsRAgoRAKDKV25ZptUM+tKrEOSY/x+il/hvGgCeNjkm
0vLCN9aFIwpTBFMN3qMhPBc=
=cvvm
-----END PGP SIGNATURE-----

--pf9I7BMVVzbSWLtt--


--===============0353357194==
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

--===============0353357194==--



From tsvwg-bounces@ietf.org  Tue Dec 14 14:08:51 2004
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 OAA05435;
	Tue, 14 Dec 2004 14:08:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeIAa-0002dj-6X; Tue, 14 Dec 2004 14:17:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeHtr-0003ru-9H; Tue, 14 Dec 2004 13:59:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeHsz-0003gu-8T
	for tsvwg@megatron.ietf.org; Tue, 14 Dec 2004 13:59:01 -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 NAA04257
	for <tsvwg@ietf.org>; Tue, 14 Dec 2004 13:59:00 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeI11-0002Js-8h
	for tsvwg@ietf.org; Tue, 14 Dec 2004 14:07:22 -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 iBEIsSQ27481;
	Tue, 14 Dec 2004 10:54:28 -0800 (PST)
Message-ID: <41BF375D.3080405@isi.edu>
Date: Tue, 14 Dec 2004 10:56:29 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ted Faber <faber@ISI.EDU>
Subject: Re: [Tsvwg] Reviews of RSVP extensions (here, there, or ... ?)
References: <A05118C6DF9320488C77F3D5459B17B7357467@xmb-ams-333.emea.cisco.com>
	<20041214015215.GA1033@pun.isi.edu>
In-Reply-To: <20041214015215.GA1033@pun.isi.edu>
X-Enigmail-Version: 0.86.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit
Cc: "James Polk \(jmpolk\)" <jmpolk@cisco.com>,
        Jukka MJ Manner <jmanner@cs.Helsinki.FI>, tsvwg <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: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit

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



Ted Faber wrote:
| On Tue, Dec 07, 2004 at 10:48:22AM +0100, Francois Le Faucheur
(flefauch) wrote:
|
|>Hello,
|>
|>
|>>>My impression hasn't been that there's been a shortage of time to
|>>>present or discuss these drafts in TSVWG, but a low interest
|>>>level.  I'm
|>>>not sure that a new group would address that.
|>>>
|>>>That's an impression; I could be way off.
|>
|>I remember a "Hum-test" was run during the WG.
|
|
| The minutes support your position.  I plead poor memory and bias. :-)

It's been confusing that so many people are interested in having this
work be part of TSVWG (the hum test succeeded), but that so few people
read the documents.

Perhaps we need an additional "did anyone read the drafts" test. Humming
alone is too low-effort as a metric of interest in new work.

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

iD8DBQFBvzddE5f5cImnZrsRArc5AKC6cy84cjwNvvbt08+H/mG9QtRrRgCfd4lK
q1KjrNIZI9NrNjNpV7ROtRw=
=qok1
-----END PGP SIGNATURE-----

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


From tsvwg-bounces@ietf.org  Tue Dec 14 18:51:36 2004
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 SAA06074;
	Tue, 14 Dec 2004 18:51:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeMaH-0002ug-Dq; Tue, 14 Dec 2004 19: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 1CeMNa-0004LM-8h; Tue, 14 Dec 2004 18:46:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeMJX-0003Xa-Co
	for tsvwg@megatron.ietf.org; Tue, 14 Dec 2004 18:42:43 -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 SAA05633
	for <tsvwg@ietf.org>; Tue, 14 Dec 2004 18:42:40 -0500 (EST)
Received: from pun.isi.edu ([128.9.160.150])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeMRe-0002jG-8V
	for tsvwg@ietf.org; Tue, 14 Dec 2004 18:51:06 -0500
Received: from pun.isi.edu (localhost [127.0.0.1])
	by pun.isi.edu (8.13.1/8.13.1) with ESMTP id iBENgBdH049441;
	Tue, 14 Dec 2004 15:42:11 -0800 (PST)
	(envelope-from faber@pun.isi.edu)
Received: (from faber@localhost)
	by pun.isi.edu (8.13.1/8.13.1/Submit) id iBENgBhb049440;
	Tue, 14 Dec 2004 15:42:11 -0800 (PST) (envelope-from faber)
Date: Tue, 14 Dec 2004 15:42:11 -0800
From: Ted Faber <faber@ISI.EDU>
To: Joe Touch <touch@ISI.EDU>
Subject: Re: [Tsvwg] Reviews of RSVP extensions (here, there, or ... ?)
Message-ID: <20041214234211.GD965@pun.isi.edu>
References: <A05118C6DF9320488C77F3D5459B17B7357467@xmb-ams-333.emea.cisco.com>
	<20041214015215.GA1033@pun.isi.edu> <41BF375D.3080405@isi.edu>
Mime-Version: 1.0
In-Reply-To: <41BF375D.3080405@isi.edu>
User-Agent: Mutt/1.4.2.1i
X-url: http://www.isi.edu/~faber
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: tsvwg <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>
Content-Type: multipart/mixed; boundary="===============0328038734=="
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135


--===============0328038734==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="uCPdOCrL+PnN2Vxy"
Content-Disposition: inline


--uCPdOCrL+PnN2Vxy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

cc s trimmed.

On Tue, Dec 14, 2004 at 10:56:29AM -0800, Joe Touch wrote:
[attribs lost]
> |>I remember a "Hum-test" was run during the WG.
> | The minutes support your position.  I plead poor memory and bias. :-)
> 
> It's been confusing that so many people are interested in having this
> work be part of TSVWG (the hum test succeeded), but that so few people
> read the documents.
> 
> Perhaps we need an additional "did anyone read the drafts" test. Humming
> alone is too low-effort as a metric of interest in new work.

My reading of the minutes was that both those points were raised and
that a general hum, not restricted to those having read the documents,
indicated support for doing the work in TSVWG.

My bias was toward the position you're advocating, but that's not what I
read in the minutes.  I didn't take my own notes and don't have a
distinct recollection of the meeting, so I have to trust the minutes.

Have I misread them?

-- 
Ted Faber
http://www.isi.edu/~faber           PGP: http://www.isi.edu/~faber/pubkeys.asc
Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG 

--uCPdOCrL+PnN2Vxy
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFBv3pTaUz3f+Zf+XsRAoiaAKDjO/WF1v+mTLUqF+EJwjxDiqAWBQCgpOBt
frhcx5X4YAI3/9w/iEcWz54=
=BfsJ
-----END PGP SIGNATURE-----

--uCPdOCrL+PnN2Vxy--


--===============0328038734==
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

--===============0328038734==--



From tsvwg-bounces@ietf.org  Tue Dec 14 19:04:42 2004
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 TAA06888;
	Tue, 14 Dec 2004 19:04:42 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeMmy-0003F5-8v; Tue, 14 Dec 2004 19:13:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeMcB-0006ll-BC; Tue, 14 Dec 2004 19:01:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeMXv-0005b9-E5
	for tsvwg@megatron.ietf.org; Tue, 14 Dec 2004 18:57:35 -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 SAA06402
	for <tsvwg@ietf.org>; Tue, 14 Dec 2004 18:57:32 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeMg1-00032o-K4
	for tsvwg@ietf.org; Tue, 14 Dec 2004 19:05:58 -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 iBENsiQ24415;
	Tue, 14 Dec 2004 15:54:44 -0800 (PST)
Message-ID: <41BF7DBE.5090602@isi.edu>
Date: Tue, 14 Dec 2004 15:56:46 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ted Faber <faber@ISI.EDU>
Subject: Re: [Tsvwg] Reviews of RSVP extensions (here, there, or ... ?)
References: <A05118C6DF9320488C77F3D5459B17B7357467@xmb-ams-333.emea.cisco.com>
	<20041214015215.GA1033@pun.isi.edu> <41BF375D.3080405@isi.edu>
	<20041214234211.GD965@pun.isi.edu>
In-Reply-To: <20041214234211.GD965@pun.isi.edu>
X-Enigmail-Version: 0.86.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit
Cc: tsvwg <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: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: 7bit

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



Ted Faber wrote:
| cc s trimmed.
|
| On Tue, Dec 14, 2004 at 10:56:29AM -0800, Joe Touch wrote:
| [attribs lost]
|
|>|>I remember a "Hum-test" was run during the WG.
|>| The minutes support your position.  I plead poor memory and bias. :-)
|>
|>It's been confusing that so many people are interested in having this
|>work be part of TSVWG (the hum test succeeded), but that so few people
|>read the documents.
|>
|>Perhaps we need an additional "did anyone read the drafts" test. Humming
|>alone is too low-effort as a metric of interest in new work.
|
|
| My reading of the minutes was that both those points were raised and
| that a general hum, not restricted to those having read the documents,
| indicated support for doing the work in TSVWG.
|
| My bias was toward the position you're advocating, but that's not what I
| read in the minutes.  I didn't take my own notes and don't have a
| distinct recollection of the meeting, so I have to trust the minutes.
|
| Have I misread them?

IMO the minutes are correct.

However, IMO the process needs to be adjusted ;-)

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

iD8DBQFBv32+E5f5cImnZrsRAjABAJ9xhkC7tDiDNc2/YtJLzIeFkoMOmACgyRDB
EOHBtsT6c8B6sQ32ImuAs+U=
=K06C
-----END PGP SIGNATURE-----

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


From tsvwg-bounces@ietf.org  Mon Dec 20 12:57:01 2004
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 MAA19742;
	Mon, 20 Dec 2004 12:57:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgRvd-0007Je-Bb; Mon, 20 Dec 2004 13:06:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgRkJ-0005ha-UN; Mon, 20 Dec 2004 12:54:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgRiM-0005Mg-Ve
	for tsvwg@megatron.ietf.org; Mon, 20 Dec 2004 12:52:58 -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 MAA19350
	for <tsvwg@ietf.org>; Mon, 20 Dec 2004 12:52:55 -0500 (EST)
Received: from rproxy.gmail.com ([64.233.170.206])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgRrc-0007Bq-Og
	for tsvwg@ietf.org; Mon, 20 Dec 2004 13:02:35 -0500
Received: by rproxy.gmail.com with SMTP id r35so475895rna
	for <tsvwg@ietf.org>; Mon, 20 Dec 2004 09:52:54 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding;
	b=XA0/PWH83bNYgDNqEJ8J6hwjY9A7yPO7wWpKmHOM3dVYU/Kz6ai694n++9sXf2kZvV8MGXRsuRFEZHxgYYoNwedYMBCOtFXWSjygZcCaVw5H8KNdCUAZdL48SDTVaxCAeNNeEcK5RUPjPs9xMOf1DJXHWqX1MqxS+vjbVfFHmCM=
Received: by 10.38.162.15 with SMTP id k15mr79112rne;
	Mon, 20 Dec 2004 09:52:54 -0800 (PST)
Received: by 10.38.149.43 with HTTP; Mon, 20 Dec 2004 09:52:54 -0800 (PST)
Message-ID: <45b19bd704122009521c39e20e@mail.gmail.com>
Date: Mon, 20 Dec 2004 23:22:54 +0530
From: Manikanda Prabhu <manik.mit@gmail.com>
To: tsvwg@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit
Subject: [Tsvwg] Load balancing with SCTP Multihoming doubt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Manikanda Prabhu <manik.mit@gmail.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.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit

Hi 

Does  ' transport layer load balancing ' covers balancing load between
multiple associations ? ie if I'm using two applications say http and
ftp, and i have access to 3 networks , could that be possible to
dynamically schedule those two associations on 3 networks based on
priority or something ?  (i may want to give more bandwidth for my ftp
transfer)

Thanks in advance
manik

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


From tsvwg-bounces@ietf.org  Mon Dec 20 17:05:48 2004
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 RAA16470;
	Mon, 20 Dec 2004 17:05:48 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgVoQ-0007Yp-6s; Mon, 20 Dec 2004 17:15:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgVIP-0008E1-HO; Mon, 20 Dec 2004 16:42:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgVBy-0003B8-J9
	for tsvwg@megatron.ietf.org; Mon, 20 Dec 2004 16:35:47 -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 QAA11181
	for <tsvwg@ietf.org>; Mon, 20 Dec 2004 16:35:43 -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 1CgVLI-0005l0-Vp
	for tsvwg@ietf.org; Mon, 20 Dec 2004 16:45:25 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 20 Dec 2004 13:40:18 -0800
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iBKLZ6o9003596;
	Mon, 20 Dec 2004 13:35:11 -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 NAA11904;
	Mon, 20 Dec 2004 13:35:04 -0800 (PST)
Message-Id: <4.3.2.7.2.20041220152502.0268a768@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 20 Dec 2004 15:35:21 -0600
To: louise.burness@bt.com, <pratik.bose@lmco.com>, <flefauch@cisco.com>,
        <faber@ISI.EDU>, <jmanner@cs.Helsinki.FI>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: RE: [Tsvwg] Reviews of RSVP extensions (here, there, or ... ?)
In-Reply-To: <0AAF93247C75E3408638B965DEE11A700BABB21C@i2km41-ukdy.domai
	n1.systemhost.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Cc: nitin@jungle.bt.co.uk, 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: 1.1 (+)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0

At 12:02 PM 12/10/2004 +0000, louise.burness@bt.com wrote:

>So, there is interest (well I might be interested anyway) and the
>suggestion is that discussion should be via TSVWG to start with at
>least?
>
>OK then James, what extensions to RSVP are you wanting to be looked at?

At least the following IDs:

1 Extension (for now):
http://www.ietf.org/internet-drafts/draft-polk-tsvwg-rsvp-bw-reduction-00.txt

1 use-case of the previous ID:
http://www.ietf.org/internet-drafts/draft-baker-tsvwg-vpn-signaled-preemption-01.txt

1 (probably) BCP type ID:
http://www.ietf.org/internet-drafts/draft-baker-tsvwg-mlpp-that-works-02.txt

This next ID isn't really RSVP related (but is TSV related); however, 
reading it before the MLPP-That-Works ID (above) will make the MLPP ID's 
references less confusing.
http://www.ietf.org/internet-drafts/draft-baker-tsvwg-mlef-concerns-02.txt

Francois probably has one or more to add to this list.

comments on all of these are encouraged



>Louise
>
> > -----Original Message-----
> > From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org]
> > On Behalf Of Bose, Pratik
> > Sent: 07 December 2004 17:58
> > To: Francois Le Faucheur (flefauch); Ted Faber; Jukka MJ Manner
> > Cc: James Polk (jmpolk); tsvwg
> > Subject: RE: [Tsvwg] Reviews of RSVP extensions (here, there,
> > or ... ?)
> >
> >
> > Actually I do remember the hum-test that Francois mentions,
> > and I also recall that a counter hum-test was taken for the
> > same question below (for those in favor of not supporting
> > this work here) and there was barely a hum for that - so I am
> > not sure whether the interest being low is really correct. I
> > am sure the minutes can confirm this info....
> >
> > > -----Original Message-----
> > > From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org]
> > > On Behalf Of Francois Le Faucheur (flefauch)
> > > Sent: Tuesday, December 07, 2004 4:48 AM
> > > To: Ted Faber; Jukka MJ Manner
> > > Cc: James Polk (jmpolk); tsvwg
> > > Subject: RE: [Tsvwg] Reviews of RSVP extensions (here, there,
> > > or ... ?)
> > >
> > > Hello,
> > >
> > > >> My impression hasn't been that there's been a shortage of time to
> > > >> present or discuss these drafts in TSVWG, but a low
> > > interest level.
> > > >> I'm not sure that a new group would address that.
> > > >>
> > > >> That's an impression; I could be way off.
> > >
> > > I remember a "Hum-test" was run during the WG.
> > > Although I can't remember the exat words, I believe the
> > > question was something like "is the RSVP work discussed in
> > > the TSVWG useful?"  or "is the RSVP work discussed in the
> > > TSVWG of interest to this audience?".
> > > I thought the "Hum-level" was clearly quite high. So my
> > > impression is that we had settled on that question and that
> > > there is agreement in progressing this work.
> > > Am I missing something?
> > >
> > > I think James' question is rather about whether this should
> > > be done under TSVWG or in some other group. Personally, I
> > > would suggest keeping it under TSVWG until there is a
> > > specific reason to change (e.g. there is a shortage of time
> > > to present/discuss all the items under TSVWG).
> > >
> > > Cheers
> > >
> > > Francois
> > >
> > > >>
> > > >> --
> > > >> Ted Faber
> > > >> http://www.isi.edu/~faber           PGP:
> > > >> http://www.isi.edu/~faber/pubkeys.asc
> > > >> Unexpected attachment on this mail? See
> > > >> http://www.isi.edu/~faber/FAQ.html#SIG
> > > >>
> > >
> > > _______________________________________________
> > > 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
> >


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  Tue Dec 21 04:42:45 2004
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 EAA20720;
	Tue, 21 Dec 2004 04:42:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cgggy-00073a-La; Tue, 21 Dec 2004 04:52:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CggUx-0004vN-4o; Tue, 21 Dec 2004 04:40:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CggSo-0003zw-BY
	for tsvwg@megatron.ietf.org; Tue, 21 Dec 2004 04:37:54 -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 EAA20482
	for <tsvwg@ietf.org>; Tue, 21 Dec 2004 04:37:52 -0500 (EST)
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CggcE-0006wU-Is
	for tsvwg@ietf.org; Tue, 21 Dec 2004 04:47:39 -0500
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 21 Dec 2004 10:47:15 +0100
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
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
	iBL9b0fw000044; Tue, 21 Dec 2004 10:37:18 +0100 (MET)
Received: from xmb-ams-333.cisco.com ([144.254.231.78]) by
	xbh-ams-331.cisco.com with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 21 Dec 2004 10:37:16 +0100
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
Subject: RE: [Tsvwg] Reviews of RSVP extensions (here, there, or ... ?)
Date: Tue, 21 Dec 2004 10:37:15 +0100
Message-ID: <A05118C6DF9320488C77F3D5459B17B77DEB44@xmb-ams-333.emea.cisco.com>
Thread-Topic: [Tsvwg] Reviews of RSVP extensions (here, there, or ... ?)
Thread-Index: AcTm28tsbALkZqs6Re+WN6ztRy1haQAY1Ljw
From: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>
To: "James Polk \(jmpolk\)" <jmpolk@cisco.com>, <louise.burness@bt.com>,
        <pratik.bose@lmco.com>, <faber@ISI.EDU>, <jmanner@cs.Helsinki.FI>
X-OriginalArrivalTime: 21 Dec 2004 09:37:16.0848 (UTC)
	FILETIME=[A8C2D300:01C4E740]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: quoted-printable
Cc: nitin@jungle.bt.co.uk, 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: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: quoted-printable

Hi,

>> Francois probably has one or more to add to this list.
>>=20

http://www.ietf.org/internet-drafts/draft-lefaucheur-rsvp-dste-01.txt

http://www.ietf.org/internet-drafts/draft-manner-lrsvp-04.txt

Cheers

Francois

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


From tsvwg-bounces@ietf.org  Tue Dec 21 19:48:47 2004
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 TAA27897;
	Tue, 21 Dec 2004 19:48:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cgupu-0001zQ-Tp; Tue, 21 Dec 2004 19:58:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgucM-0000LM-Lu; Tue, 21 Dec 2004 19:44:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cguad-0007so-MJ
	for tsvwg@megatron.ietf.org; Tue, 21 Dec 2004 19:42: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 TAA26936
	for <tsvwg@ietf.org>; Tue, 21 Dec 2004 19:42:52 -0500 (EST)
Received: from vscan.fit.ac.jp ([150.43.1.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cguk0-0001eR-41
	for tsvwg@ietf.org; Tue, 21 Dec 2004 19:52:37 -0500
Received: from dontaku.fit.ac.jp (localhost [127.0.0.1])
	by vscan.fit.ac.jp (8.12.5/8.12.5) with ESMTP id iBM0g2rv022004
	for <tsvwg@ietf.org>; Wed, 22 Dec 2004 09:42:02 +0900 (JST)
Received: from [150.43.233.162] (nausica.ce.fit.ac.jp [150.43.233.162])
	by dontaku.fit.ac.jp (8.11.6/3.7W03112810) with ESMTP id iBM0g2I28235
	for <tsvwg@ietf.org>; Wed, 22 Dec 2004 09:42:02 +0900
Message-ID: <41C8C2E3.3040500@unisa.it>
Date: Wed, 22 Dec 2004 09:42:11 +0900
From: giuseppe <gdemarco@unisa.it>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: tsvwg@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Subject: [Tsvwg] Two addresses
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: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit

But, is it a realistic scenario thinking that in WLAN we can use two 
addresses at the same time? Even if we could use SCTP with ADD-IP extensions
to use two IP add. from two subnet, how a nowday WLAN could furnish 
them? I read that standards do not permit to use two or more access 
point at the same time.
ANy reply appre

-- 
----------------------
----------------------
Giuseppe De Marco, Ph.D.

Dipartimento di Ingegneria 
dell'Informazione e Ingegneria Elettrica
DIIIE, University of Salerno
via ponte don Melillo 1, Fisciano, Salerno
tel: +39 089 964012
email: gdemarco@unisa.it

Department of Information and 
Communication Engineering 
Faculty of Information Engineering 
Fukuoka Institute of Technology (FIT)
3-30-1 Wajiro-Higashi, Higashi-ku, Fukuoka 811-0295 
Japan
email: demarco@fit.ac.jp
--------------------


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


From tsvwg-bounces@ietf.org  Tue Dec 21 22:53:15 2004
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 WAA14692;
	Tue, 21 Dec 2004 22:53:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgxiS-0007Tt-84; Tue, 21 Dec 2004 23:03:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgxRk-000303-43; Tue, 21 Dec 2004 22:45:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgxQh-0002bV-L5
	for tsvwg@megatron.ietf.org; Tue, 21 Dec 2004 22:44:53 -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 WAA14241
	for <tsvwg@ietf.org>; Tue, 21 Dec 2004 22:44:49 -0500 (EST)
Received: from gw.openss7.com ([142.179.199.224]
	ident=[RDV0rI4l+Y+tULBEL9fIX3bCyVorkUqn])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cgxa8-0007Gw-7z
	for tsvwg@ietf.org; Tue, 21 Dec 2004 22:54:46 -0500
Received: from ns.pigworks.openss7.net
	(IDENT:rS346zY7nWkL1h272A+MHVbdNc2a3N+E@ns1.evil.openss7.net
	[192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id iBM3iRi17846;
	Tue, 21 Dec 2004 20:44:27 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id iBM3iRR29897;
	Tue, 21 Dec 2004 20:44:27 -0700
Date: Tue, 21 Dec 2004 20:44:27 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: giuseppe <gdemarco@unisa.it>
Subject: Re: [Tsvwg] Two addresses
Message-ID: <20041221204427.A29879@openss7.org>
References: <41C8C2E3.3040500@unisa.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <41C8C2E3.3040500@unisa.it>;
	from gdemarco@unisa.it on Wed, Dec 22, 2004 at 09:42:11AM +0900
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id
	iBM3iRi17846
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: quoted-printable
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bidulock@openss7.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>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: quoted-printable

giuseppe,

The second access could be other than WLAN, couldn't it?

--brian

On Wed, 22 Dec 2004, giuseppe wrote:

> But, is it a realistic scenario thinking that in WLAN we can use two=20
> addresses at the same time? Even if we could use SCTP with ADD-IP exten=
sions
> to use two IP add. from two subnet, how a nowday WLAN could furnish=20
> them? I read that standards do not permit to use two or more access=20
> point at the same time.
> ANy reply appre
>=20
> --=20
> ----------------------
> ----------------------
> Giuseppe De Marco, Ph.D.
>=20
> Dipartimento di Ingegneria=20
> dell'Informazione e Ingegneria Elettrica
> DIIIE, University of Salerno
> via ponte don Melillo 1, Fisciano, Salerno
> tel: +39 089 964012
> email: gdemarco@unisa.it
>=20
> Department of Information and=20
> Communication Engineering=20
> Faculty of Information Engineering=20
> Fukuoka Institute of Technology (FIT)
> 3-30-1 Wajiro-Higashi, Higashi-ku, Fukuoka 811-0295=20
> Japan
> email: demarco@fit.ac.jp
> --------------------
>=20
>=20
> _______________________________________________
> tsvwg mailing list
> tsvwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/tsvwg

--=20
Brian F. G. Bidulock    =A6 The reasonable man adapts himself to the =A6
bidulock@openss7.org    =A6 world; the unreasonable one persists in  =A6
http://www.openss7.org/ =A6 trying  to adapt the  world  to himself. =A6
                        =A6 Therefore  all  progress  depends on the =A6
                        =A6 unreasonable man. -- George Bernard Shaw =A6

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


From tsvwg-bounces@ietf.org  Wed Dec 22 01:28:02 2004
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 BAA24578;
	Wed, 22 Dec 2004 01:28:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ch08G-00035m-Ps; Wed, 22 Dec 2004 01:38:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cgzts-0006b9-LD; Wed, 22 Dec 2004 01:23:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cgzrm-00059J-RX
	for tsvwg@megatron.ietf.org; Wed, 22 Dec 2004 01:20:58 -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 BAA24068
	for <tsvwg@ietf.org>; Wed, 22 Dec 2004 01:20:57 -0500 (EST)
Received: from vscan.fit.ac.jp ([150.43.1.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ch01N-0002tE-U5
	for tsvwg@ietf.org; Wed, 22 Dec 2004 01:30:55 -0500
Received: from dontaku.fit.ac.jp (localhost [127.0.0.1])
	by vscan.fit.ac.jp (8.12.5/8.12.5) with ESMTP id iBM6KNYT007899
	for <tsvwg@ietf.org>; Wed, 22 Dec 2004 15:20:24 +0900 (JST)
Received: from [150.43.233.162] (nausica.ce.fit.ac.jp [150.43.233.162])
	by dontaku.fit.ac.jp (8.11.6/3.7W03112810) with ESMTP id iBM6KNI20724
	for <tsvwg@ietf.org>; Wed, 22 Dec 2004 15:20:23 +0900
Message-ID: <41C91230.4090506@unisa.it>
Date: Wed, 22 Dec 2004 15:20:32 +0900
From: giuseppe <gdemarco@unisa.it>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: tsvwg@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Subject: [Tsvwg] 2 add. with  WLAN
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: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit

I just read a paper where the authors claim that is possible use two AP 
in IEEE802.11b.
In a IEEE Transactio I read the contrary. Somebody could explain if it 
is possible or not with IEEE802.11
communicate with two or more APs?
G


-- 
----------------------
----------------------
Giuseppe De Marco, Ph.D.

Dipartimento di Ingegneria 
dell'Informazione e Ingegneria Elettrica
DIIIE, University of Salerno
via ponte don Melillo 1, Fisciano, Salerno
tel: +39 089 964012
email: gdemarco@unisa.it

Department of Information and 
Communication Engineering 
Faculty of Information Engineering 
Fukuoka Institute of Technology (FIT)
3-30-1 Wajiro-Higashi, Higashi-ku, Fukuoka 811-0295 
Japan
email: demarco@fit.ac.jp
--------------------


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


From tsvwg-bounces@ietf.org  Wed Dec 22 01:30:44 2004
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 BAA24697;
	Wed, 22 Dec 2004 01:30:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ch0Ar-00039H-OL; Wed, 22 Dec 2004 01:40:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ch009-00019y-Lp; Wed, 22 Dec 2004 01:29:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgzuW-0006n5-JY
	for tsvwg@megatron.ietf.org; Wed, 22 Dec 2004 01:23:48 -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 BAA24238
	for <tsvwg@ietf.org>; Wed, 22 Dec 2004 01:23:47 -0500 (EST)
Received: from vscan.fit.ac.jp ([150.43.1.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ch048-0002xf-Kj
	for tsvwg@ietf.org; Wed, 22 Dec 2004 01:33:45 -0500
Received: from dontaku.fit.ac.jp (localhost [127.0.0.1])
	by vscan.fit.ac.jp (8.12.5/8.12.5) with ESMTP id iBM6NGv2007991
	for <tsvwg@ietf.org>; Wed, 22 Dec 2004 15:23:16 +0900 (JST)
Received: from [150.43.233.162] (nausica.ce.fit.ac.jp [150.43.233.162])
	by dontaku.fit.ac.jp (8.11.6/3.7W03112810) with ESMTP id iBM6NGI20920
	for <tsvwg@ietf.org>; Wed, 22 Dec 2004 15:23:16 +0900
Message-ID: <41C912DC.8070501@unisa.it>
Date: Wed, 22 Dec 2004 15:23:24 +0900
From: giuseppe <gdemarco@unisa.it>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: tsvwg@ietf.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Subject: [Tsvwg] 2 add. WLAN ...
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: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit

More, I cite textual words...>" Current commer-
cial 802.11 cards allow simultaneous communication via multiple
APs only using ad-hoc mode, however it appears that this capa-
bility may be possible in infrastructure mode using only software
changes."

G.

-- 
----------------------
----------------------
Giuseppe De Marco, Ph.D.

Dipartimento di Ingegneria 
dell'Informazione e Ingegneria Elettrica
DIIIE, University of Salerno
via ponte don Melillo 1, Fisciano, Salerno
tel: +39 089 964012
email: gdemarco@unisa.it

Department of Information and 
Communication Engineering 
Faculty of Information Engineering 
Fukuoka Institute of Technology (FIT)
3-30-1 Wajiro-Higashi, Higashi-ku, Fukuoka 811-0295 
Japan
email: demarco@fit.ac.jp
--------------------


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


From tsvwg-bounces@ietf.org  Wed Dec 22 02:57:19 2004
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 CAA28950;
	Wed, 22 Dec 2004 02:57:19 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ch1Wf-0005EW-9x; Wed, 22 Dec 2004 03:07:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ch1JX-0001gU-4I; Wed, 22 Dec 2004 02:53:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ch1Gd-0000tf-Cp
	for tsvwg@megatron.ietf.org; Wed, 22 Dec 2004 02:50:43 -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 CAA28482
	for <tsvwg@ietf.org>; Wed, 22 Dec 2004 02:50:41 -0500 (EST)
Received: from gw.openss7.com ([142.179.199.224]
	ident=[iMWR4TSiPUaOpUe9b4LcVxO+mc3PIBQI])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ch1QF-00054Q-EH
	for tsvwg@ietf.org; Wed, 22 Dec 2004 03:00:40 -0500
Received: from ns.pigworks.openss7.net
	(IDENT:TmpVzqNne8LjIstjX5JsC7UOBz597kPk@ns1.evil.openss7.net
	[192.168.9.1])
	by gw.openss7.com (8.11.6/8.11.6) with ESMTP id iBM7oei21640;
	Wed, 22 Dec 2004 00:50:40 -0700
Received: (from brian@localhost)
	by ns.pigworks.openss7.net (8.11.6/8.11.6) id iBM7oeH31366;
	Wed, 22 Dec 2004 00:50:40 -0700
Date: Wed, 22 Dec 2004 00:50:39 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: giuseppe <gdemarco@unisa.it>
Subject: Re: [Tsvwg] 2 add. with  WLAN
Message-ID: <20041222005039.A31331@openss7.org>
References: <41C91230.4090506@unisa.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <41C91230.4090506@unisa.it>;
	from gdemarco@unisa.it on Wed, Dec 22, 2004 at 03:20:32PM +0900
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by gw.openss7.com id
	iBM7oei21640
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: quoted-printable
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bidulock@openss7.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>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: quoted-printable

giuseppe,

IEEE !=3D IETF

--brian

On Wed, 22 Dec 2004, giuseppe wrote:

> I just read a paper where the authors claim that is possible use two AP=
=20
> in IEEE802.11b.
> In a IEEE Transactio I read the contrary. Somebody could explain if it=20
> is possible or not with IEEE802.11
> communicate with two or more APs?
> G
>=20
>=20
> --=20
> ----------------------
> ----------------------
> Giuseppe De Marco, Ph.D.
>=20
> Dipartimento di Ingegneria=20
> dell'Informazione e Ingegneria Elettrica
> DIIIE, University of Salerno
> via ponte don Melillo 1, Fisciano, Salerno
> tel: +39 089 964012
> email: gdemarco@unisa.it
>=20
> Department of Information and=20
> Communication Engineering=20
> Faculty of Information Engineering=20
> Fukuoka Institute of Technology (FIT)
> 3-30-1 Wajiro-Higashi, Higashi-ku, Fukuoka 811-0295=20
> Japan
> email: demarco@fit.ac.jp
> --------------------
>=20
>=20
> _______________________________________________
> tsvwg mailing list
> tsvwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/tsvwg

--=20
Brian F. G. Bidulock    =A6 The reasonable man adapts himself to the =A6
bidulock@openss7.org    =A6 world; the unreasonable one persists in  =A6
http://www.openss7.org/ =A6 trying  to adapt the  world  to himself. =A6
                        =A6 Therefore  all  progress  depends on the =A6
                        =A6 unreasonable man. -- George Bernard Shaw =A6

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


From tsvwg-bounces@ietf.org  Wed Dec 22 13:26:47 2004
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 NAA20122;
	Wed, 22 Dec 2004 13:26:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChBLy-00071c-CW; Wed, 22 Dec 2004 13:36:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChB8o-0006h3-M1; Wed, 22 Dec 2004 13:23:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ChB7f-0006FR-8K
	for tsvwg@megatron.ietf.org; Wed, 22 Dec 2004 13:22: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 NAA19939
	for <tsvwg@ietf.org>; Wed, 22 Dec 2004 13:22:03 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ChBHM-0006t1-S5
	for tsvwg@ietf.org; Wed, 22 Dec 2004 13:32:10 -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 iBMIKNQ29923;
	Wed, 22 Dec 2004 10:20:23 -0800 (PST)
Message-ID: <41C9BAE7.8010509@isi.edu>
Date: Wed, 22 Dec 2004 10:20:23 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: bidulock@openss7.org
Subject: Re: [Tsvwg] 2 add. with  WLAN
References: <41C91230.4090506@unisa.it> <20041222005039.A31331@openss7.org>
In-Reply-To: <20041222005039.A31331@openss7.org>
X-Enigmail-Version: 0.86.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
Cc: tsvwg@ietf.org, giuseppe <gdemarco@unisa.it>
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: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit

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

The card would need two MAC addresses; otherwise, advertising a single
MAC address on multiple APs would cause problems with bridging (if the
two APs were ever bridged elsewhere).

As to the IETF, IMO we'd care w.r.t. ARP; ARP might not react well to
reusing the same MAC address with multiple IP addresses as well.

Joe

Brian F. G. Bidulock wrote:
| giuseppe,
|
| IEEE != IETF
|
| --brian
|
| On Wed, 22 Dec 2004, giuseppe wrote:
|
|
|>I just read a paper where the authors claim that is possible use two AP
|>in IEEE802.11b.
|>In a IEEE Transactio I read the contrary. Somebody could explain if it
|>is possible or not with IEEE802.11
|>communicate with two or more APs?
|>G
|>
|>
|>--
|>----------------------
|>----------------------
|>Giuseppe De Marco, Ph.D.
|>
|>Dipartimento di Ingegneria
|>dell'Informazione e Ingegneria Elettrica
|>DIIIE, University of Salerno
|>via ponte don Melillo 1, Fisciano, Salerno
|>tel: +39 089 964012
|>email: gdemarco@unisa.it
|>
|>Department of Information and
|>Communication Engineering
|>Faculty of Information Engineering
|>Fukuoka Institute of Technology (FIT)
|>3-30-1 Wajiro-Higashi, Higashi-ku, Fukuoka 811-0295
|>Japan
|>email: demarco@fit.ac.jp
|>--------------------
|>
|>
|>_______________________________________________
|>tsvwg mailing list
|>tsvwg@ietf.org
|>https://www1.ietf.org/mailman/listinfo/tsvwg
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBybrnE5f5cImnZrsRAjWAAJ4yKlSXTqTOObSPPf3QLYTbpNhI/ACcDDZ9
oQjxo8Q//0NV5ymG9ojuWF4=
=iV1m
-----END PGP SIGNATURE-----

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


From tsvwg-bounces@ietf.org  Thu Dec 23 04:14:20 2004
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 EAA20575;
	Thu, 23 Dec 2004 04:14:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChPCy-0004k8-IY; Thu, 23 Dec 2004 04:24:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChOv2-0000P9-3c; Thu, 23 Dec 2004 04:06:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ChOtk-0008T3-2R
	for tsvwg@megatron.ietf.org; Thu, 23 Dec 2004 04:04:42 -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 EAA20099
	for <tsvwg@ietf.org>; Thu, 23 Dec 2004 04:04:37 -0500 (EST)
From: louise.burness@bt.com
Received: from smtp5.smtp.bt.com ([217.32.164.139])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ChP3Z-0004VD-2n
	for tsvwg@ietf.org; Thu, 23 Dec 2004 04:14:50 -0500
Received: from i2km98-ukbr.domain1.systemhost.net ([193.113.197.85]) by
	smtp5.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.80); 
	Thu, 23 Dec 2004 09:05:25 +0000
Received: from i2km41-ukdy.domain1.systemhost.net ([193.113.30.29]) by
	i2km98-ukbr.domain1.systemhost.net with Microsoft
	SMTPSVC(5.0.2195.6713); Thu, 23 Dec 2004 09:05:25 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Tsvwg] 2 add. with  WLAN
Date: Thu, 23 Dec 2004 09:05:25 -0000
Message-ID: <0AAF93247C75E3408638B965DEE11A70084ED968@i2km41-ukdy.domain1.systemhost.net>
Thread-Topic: [Tsvwg] 2 add. with  WLAN
Thread-Index: AcToVBzzLgOw0WBAR5262DhLqp8O8QAePSHQ
To: <touch@ISI.EDU>, <bidulock@openss7.org>
X-OriginalArrivalTime: 23 Dec 2004 09:05:25.0441 (UTC)
	FILETIME=[8A4CC310:01C4E8CE]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Content-Transfer-Encoding: quoted-printable
Cc: tsvwg@ietf.org, gdemarco@unisa.it
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.3 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Content-Transfer-Encoding: quoted-printable

It depends if you are running in managed or ad hoc mode.=20

In ad hoc mode you can hear everything together with one card and one
mac address per card. In managed mode, you can't.

You might get into terminology debate about what an AP really is in ad
hoc mode ......But certainly, people have run nodes in ad hoc mode which
act as IP routers and provide connectivity to the Internet. One reason
is that it enables a mobile node to chose its own access point based on
signal strength etc and do seamless mobile IP handover. If nodes are in
managed mode, you get fast handover when you have it managed by the
access points, but get big timeouts if you move to a different wireless
domain.

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org]=20
> On Behalf Of Joe Touch
> Sent: 22 December 2004 18:20
> To: bidulock@openss7.org
> Cc: tsvwg@ietf.org; giuseppe
> Subject: Re: [Tsvwg] 2 add. with WLAN
>=20
>=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> The card would need two MAC addresses; otherwise, advertising=20
> a single MAC address on multiple APs would cause problems=20
> with bridging (if the two APs were ever bridged elsewhere).
>=20
> As to the IETF, IMO we'd care w.r.t. ARP; ARP might not react=20
> well to reusing the same MAC address with multiple IP=20
> addresses as well.
>=20
> Joe
>=20
> Brian F. G. Bidulock wrote:
> | giuseppe,
> |
> | IEEE !=3D IETF
> |
> | --brian
> |
> | On Wed, 22 Dec 2004, giuseppe wrote:
> |
> |
> |>I just read a paper where the authors claim that is=20
> possible use two=20
> |>AP in IEEE802.11b. In a IEEE Transactio I read the=20
> contrary. Somebody=20
> |>could explain if it is possible or not with IEEE802.11
> |>communicate with two or more APs?
> |>G
> |>
> |>
> |>--
> |>----------------------
> |>----------------------
> |>Giuseppe De Marco, Ph.D.
> |>
> |>Dipartimento di Ingegneria
> |>dell'Informazione e Ingegneria Elettrica
> |>DIIIE, University of Salerno
> |>via ponte don Melillo 1, Fisciano, Salerno
> |>tel: +39 089 964012
> |>email: gdemarco@unisa.it
> |>
> |>Department of Information and
> |>Communication Engineering
> |>Faculty of Information Engineering
> |>Fukuoka Institute of Technology (FIT)
> |>3-30-1 Wajiro-Higashi, Higashi-ku, Fukuoka 811-0295
> |>Japan
> |>email: demarco@fit.ac.jp
> |>--------------------
> |>
> |>
> |>_______________________________________________
> |>tsvwg mailing list
> |>tsvwg@ietf.org
> |>https://www1.ietf.org/mailman/listinfo/tsvwg
> |
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>=20
> iD8DBQFBybrnE5f5cImnZrsRAjWAAJ4yKlSXTqTOObSPPf3QLYTbpNhI/ACcDDZ9
> oQjxo8Q//0NV5ymG9ojuWF4=3D
> =3DiV1m
> -----END PGP SIGNATURE-----
>=20
> _______________________________________________
> tsvwg mailing list
> tsvwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/tsvwg
>=20

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


From tsvwg-bounces@ietf.org  Thu Dec 23 13:31:01 2004
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 NAA06066;
	Thu, 23 Dec 2004 13:31:01 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1ChXto-0003NB-Id; Thu, 23 Dec 2004 13:41:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChXg4-0006pb-Mn; Thu, 23 Dec 2004 13:27:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ChXXZ-0004zw-CF
	for tsvwg@megatron.ietf.org; Thu, 23 Dec 2004 13:18:21 -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 NAA05532
	for <tsvwg@ietf.org>; Thu, 23 Dec 2004 13:18:18 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ChXhU-00039S-Qf
	for tsvwg@ietf.org; Thu, 23 Dec 2004 13:28:37 -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 iBNIGGQ11959;
	Thu, 23 Dec 2004 10:16:16 -0800 (PST)
Message-ID: <41CB0B72.7010508@isi.edu>
Date: Thu, 23 Dec 2004 10:16:18 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: louise.burness@bt.com
Subject: Re: [Tsvwg] 2 add. with  WLAN
References: <0AAF93247C75E3408638B965DEE11A70084ED968@i2km41-ukdy.domain1.systemhost.net>
In-Reply-To: <0AAF93247C75E3408638B965DEE11A70084ED968@i2km41-ukdy.domain1.systemhost.net>
X-Enigmail-Version: 0.86.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Content-Transfer-Encoding: 7bit
Cc: bidulock@openss7.org, tsvwg@ietf.org, gdemarco@unisa.it
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: 37af5f8fbf6f013c5b771388e24b09e7
Content-Transfer-Encoding: 7bit

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



louise.burness@bt.com wrote:
| It depends if you are running in managed or ad hoc mode.
|
| In ad hoc mode you can hear everything together with one card and one
| mac address per card. In managed mode, you can't.
|
| You might get into terminology debate about what an AP really is in ad
| hoc mode ......But certainly, people have run nodes in ad hoc mode which
| act as IP routers and provide connectivity to the Internet. One reason
| is that it enables a mobile node to chose its own access point based on
| signal strength etc and do seamless mobile IP handover.

That's one of the cases that concerns me. Having one MAC on two APs
doesn't play well with spanning-tree.

| If nodes are in
| managed mode, you get fast handover when you have it managed by the
| access points, but get big timeouts if you move to a different wireless
| domain.

It takes time for spanning-tree to converge after a move anyway. I'm not
sure 'seamless handover' is a reasonable goal for a bridged 802 network.

Joe


|>-----Original Message-----
|>From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org]
|>On Behalf Of Joe Touch
|>Sent: 22 December 2004 18:20
|>To: bidulock@openss7.org
|>Cc: tsvwg@ietf.org; giuseppe
|>Subject: Re: [Tsvwg] 2 add. with WLAN
|>
|>
| The card would need two MAC addresses; otherwise, advertising
| a single MAC address on multiple APs would cause problems
| with bridging (if the two APs were ever bridged elsewhere).
|
| As to the IETF, IMO we'd care w.r.t. ARP; ARP might not react
| well to reusing the same MAC address with multiple IP
| addresses as well.
|
| Joe
|
| Brian F. G. Bidulock wrote:
| | giuseppe,
| |
| | IEEE != IETF
| |
| | --brian
| |
| | On Wed, 22 Dec 2004, giuseppe wrote:
| |
| |
| |>I just read a paper where the authors claim that is
| possible use two
| |>AP in IEEE802.11b. In a IEEE Transactio I read the
| contrary. Somebody
| |>could explain if it is possible or not with IEEE802.11
| |>communicate with two or more APs?
| |>G
| |>
| |>
| |>--
| |>----------------------
| |>----------------------
| |>Giuseppe De Marco, Ph.D.
| |>
| |>Dipartimento di Ingegneria
| |>dell'Informazione e Ingegneria Elettrica
| |>DIIIE, University of Salerno
| |>via ponte don Melillo 1, Fisciano, Salerno
| |>tel: +39 089 964012
| |>email: gdemarco@unisa.it
| |>
| |>Department of Information and
| |>Communication Engineering
| |>Faculty of Information Engineering
| |>Fukuoka Institute of Technology (FIT)
| |>3-30-1 Wajiro-Higashi, Higashi-ku, Fukuoka 811-0295
| |>Japan
| |>email: demarco@fit.ac.jp
| |>--------------------
| |>
| |>
| |>_______________________________________________
| |>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

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

iD8DBQFBywtxE5f5cImnZrsRAhGYAKD3cBR3cpJrmPnr4vXWH3OB3+8CVwCfU7ps
b1Cw54j8CePvemRhmabZsKc=
=AQnp
-----END PGP SIGNATURE-----

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


From tsvwg-bounces@ietf.org  Tue Dec 28 10:03:08 2004
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 KAA01376;
	Tue, 28 Dec 2004 10:03:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjJ3M-0004Ww-HM; Tue, 28 Dec 2004 10:14:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjImY-0003s3-Js; Tue, 28 Dec 2004 09:57:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjIin-0002zk-FR
	for tsvwg@megatron.ietf.org; Tue, 28 Dec 2004 09:53:15 -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 JAA00778
	for <tsvwg@ietf.org>; Tue, 28 Dec 2004 09:53:11 -0500 (EST)
Received: from mulder.f5.com ([205.229.151.150])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjIti-0004Ix-R1
	for tsvwg@ietf.org; Tue, 28 Dec 2004 10:04:31 -0500
Received: from exchfour.olympus.f5net.com ([192.168.11.152]) by mulder.f5.com
	with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 28 Dec 2004 06:53:10 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: Re: [Tsvwg] Looking for feedback on DTLS 
Date: Tue, 28 Dec 2004 06:53:08 -0800
Message-ID: <3D8E54E3CAA3864295233C618F53F2ADC819C6@exchfour.olympus.f5net.com>
Thread-Topic: Re: [Tsvwg] Looking for feedback on DTLS 
Thread-Index: AcTs7PHxUEvxtQPwTtWFnlENO3x+Qw==
From: "Amit Jain" <a.jain@f5.com>
To: <tsvwg@ietf.org>
X-OriginalArrivalTime: 28 Dec 2004 14:53:10.0873 (UTC)
	FILETIME=[F321C490:01C4ECEC]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 54f716cba2c98b25bc07e094cc18394c
Cc: nagendra@cs.standford.edu.cnri.reston.va.us, ietf-tls@lists.certicom.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>
Content-Type: multipart/mixed; boundary="===============0639213529=="
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 210770d71723b650f9c8e3db4e95b596

This is a multi-part message in MIME format.

--===============0639213529==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4ECEC.F2DF6217"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4ECEC.F2DF6217
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I would like to submit following inputs as the feedback:
=20
Current draft proposes to add fragmentation, reliability and in-order
delivery to handshake layer while keeping the record layer mostly
unchanged.=20
=20
Draft seems to imply that the handshake layer sends a collection of
handshake messages (referred as flight) and then waits for the other end
to respond. The timeout causes all the messages in flight to be
retransmitted.=20
=20
Here the reliability is being tracked for a complete flight of messages
as a single unit. Given that a flight can have considerable amount of
data, the probability of packet loss seems to be high. And since each
packet loss causes complete flight to be retransmitted, this may be a
large retransmission again. And this may again suffer a packet loss. I
think tracking reliability on per flight and retransmitting complete
flight as a response to packet loss may not be an efficient approach.
=20
Also building the reliability and in-order delivery into handshake layer
makes handshake state machine complicated.
=20
=20
I think another approach worth considering may be to introduce a thin
layer inside record layer which takes care of fragmentation,
reliability, in-order delivery to record layer. In this approach:
=20
1: A Handshake message can never span multiple records. A record can
contain multiple handshake messages though.
=20
This will eliminate the need of handshake message re-assembly.
Assembling a record will always result in at least one complete
handshake message or multiple complete handshake messages.
=20
This is different from the current specification where the handshake can
span multiple records. And will need the change in length field of
record layer (it'll have to be extended to 3 bytes)
=20
=20
2: Records are fragmented and is converted to UDP datagram.=20
=20
These UDP data-grams are then transmitted reliably to other end in the
handshake phase using a very thin layer (built into record layer). It
may be analogous to a simple reliable variant of UDP (something like
TFTP). Here the reliability is tracked for each UDP datagram and only
the missing UDP datagram is re-transmitted.
=20
=20
This may provide following advantages:
=20
1: Handshake layer will be similar to the TLS. There won't be any change
needed in the implementation of state machine and the specification of
handshake messages.
=20
2: A Record can span multiple UDP packets; this will free DTLS from
strict need of having a correct path MTU.
=20
2: Record layer will consist of a thin reliability layer; this layer
will be active during handshake phase and will make sure the reliable
ordered delivery of the handshake messages. During application data
transfer the reliability part of the record layer is switched off.
(Actually this'll mostly depend on the application, and if application
wants to use reliability mode of record layer, that should be possible
too.)
=20
3: Having a thin reliability layer in Record layer will allow greater
flexibility and extensibility. Reliability layer can be replaced with
other reliability mechanism like DCCP in future for providing
reliability/congestion control.
=20
=20
Thanks,
-amit
=20
> Eric Rescorla wrote:

=20

> As we all know, TLS is popular but is only compatible with reliable
> transports. Unfortunately, a number of important protocols (SIP in
> particular) run over datagram transport and therefore cannot use TLS.
In
> response, Nagendra Modadugu and I have designed a variant of TLS which
> we call Datagram TLS (DTLS).  DTLS consists of only the minimal
changes
> required to TLS to make it operate on datagram transport.

=20

> We've submitted DTLS as an I-D which you can find at:
> draft-rescorla-dtls-01.txt

=20

> You can also read our paper on DTLS from ISOC NDSS at:
> http://crypto.stanford.edu/~nagendra/papers/dtls.pdf

=20

> We've already gotten some useful comments from PMTUD people about
> handling PMTU but any comments TSV people have on the protocol would
be
> appreciated.

=20

> Best,
 >-Ekr










=20
_______________________________________________
tsvwg mailing list
tsvwg at ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg

=20

=20

=20






=20
_______________________________________________
tsvwg mailing list
tsvwg at ietf.org
https://www1.ietf.org/mailman/listinfo/tsvwg

=20

=20






------_=_NextPart_001_01C4ECEC.F2DF6217
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1><pre><font size=3D2 face=3D"Courier New"><span
style=3D'font-size:10.0pt'>I would like to submit following inputs as =
the feedback:<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Current =
draft proposes to add fragmentation, reliability and in-order delivery =
to handshake layer while keeping the record layer mostly unchanged. =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Draft =
seems to imply that the handshake layer sends a collection of handshake =
messages (referred as flight) and then waits for the other end to =
respond. The timeout causes all the messages in flight to be =
retransmitted. <o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Here the =
reliability is being tracked for a complete flight of messages as a =
single unit. Given that a flight can have considerable amount of data, =
the probability of packet loss seems to be high. And since each packet =
loss causes complete flight to be retransmitted, this may be a large =
retransmission again. And this may again suffer a packet loss. I think =
tracking reliability on per flight and retransmitting complete flight as =
a response to packet loss may not be an efficient =
approach.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Also =
building the reliability and in-order delivery into handshake layer =
makes handshake state machine =
complicated.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>I think =
another approach worth considering may be to introduce a thin layer =
inside record layer which takes care of fragmentation, reliability, =
in-order delivery to record layer. In this =
approach:<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>1: A =
Handshake message can never span multiple records. A record can contain =
multiple handshake messages =
though.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>This will =
eliminate the need of handshake message re-assembly. Assembling a record =
will always result in at least one complete handshake message or =
multiple complete handshake =
messages.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>This is =
different from the current specification where the handshake can span =
multiple records. And will need the change in length field of record =
layer (it&#8217;ll have to be extended to 3 =
bytes)<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>2: =
Records are fragmented and is converted to UDP datagram. =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>These UDP =
data-grams are then transmitted reliably to other end in the handshake =
phase using a very thin layer (built into record layer). It may be =
analogous to a simple reliable variant of UDP (something like TFTP). =
Here the reliability is tracked for each UDP datagram and only the =
missing UDP datagram is =
re-transmitted.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>This may =
provide following advantages:<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>1: =
Handshake layer will be similar to the TLS. There won&#8217;t be any =
change needed in the implementation of state machine and the =
specification of handshake =
messages.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>2: A =
Record can span multiple UDP packets; this will free DTLS from strict =
need of having a correct path =
MTU.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>2: Record =
layer will consist of a thin reliability layer; this layer will be =
active during handshake phase and will make sure the reliable ordered =
delivery of the handshake messages. During application data transfer the =
reliability part of the record layer is switched off. (Actually =
this&#8217;ll mostly depend on the application, and if application wants =
to use reliability mode of record layer, that should be possible =
too.)<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>3: Having =
a thin reliability layer in Record layer will allow greater flexibility =
and extensibility. Reliability layer can be replaced with other =
reliability mechanism like DCCP in future for providing =
reliability/congestion control.<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Thanks,<o:p></o:p></span></font></pre><pre><fo=
nt
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>-amit<o:p></o:p></span></font></pre><pre><font=

size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; Eric =
Rescorla wrote:<o:p></o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt; As we all know, TLS is popular but is =
only compatible with reliable<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
transports. Unfortunately, a number of important protocols (SIP =
in<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
particular) run over datagram transport and therefore cannot use TLS. =
In<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
response, Nagendra Modadugu and I have designed a variant of TLS =
which<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; we =
call Datagram TLS (DTLS).&nbsp; DTLS consists of only the minimal =
changes<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
required to TLS to make it operate on datagram =
transport.<o:p></o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt; We've submitted DTLS as an I-D which you =
can find at:<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
draft-rescorla-dtls-01.txt<o:p></o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt; You can also read our paper on DTLS from =
ISOC NDSS at:<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; <a
href=3D"http://crypto.stanford.edu/~nagendra/papers/dtls.pdf">http://cryp=
to.stanford.edu/~nagendra/papers/dtls.pdf</a><o:p></o:p></span></font></p=
re>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt; We've already gotten some useful =
comments from PMTUD people =
about<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
handling PMTU but any comments TSV people have on the protocol would =
be<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>&gt; =
appreciated.<o:p></o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>&gt; =
Best,<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'> =
&gt;-Ekr<o:p></o:p></span></font></pre>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'><br>
<br>
<o:p></o:p></span></font></p>

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><br>
<br>
<o:p></o:p></span></font></pre><pre><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>______________________________________________=
_<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>tsvwg =
mailing list<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>tsvwg at =
ietf.org<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'><a
href=3D"https://www1.ietf.org/mailman/listinfo/tsvwg">https://www1.ietf.o=
rg/mailman/listinfo/tsvwg</a><o:p></o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><br>
<br>
<o:p></o:p></span></font></pre><pre><font size=3D2 face=3D"Courier =
New"><span
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>______________________________________________=
_<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>tsvwg =
mailing list<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>tsvwg at =
ietf.org<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'><a
href=3D"https://www1.ietf.org/mailman/listinfo/tsvwg">https://www1.ietf.o=
rg/mailman/listinfo/tsvwg</a><o:p></o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
<br>
</span></font><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial'><o:p></o:p></span></font></p>

</div>

<!--X-Body-of-Message-End--><!--X-MsgBody-End--><!--X-Follow-Ups-->
</body>

</html>

------_=_NextPart_001_01C4ECEC.F2DF6217--


--===============0639213529==
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

--===============0639213529==--



From tsvwg-bounces@ietf.org  Tue Dec 28 12:47:05 2004
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 MAA12542;
	Tue, 28 Dec 2004 12:47:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjLc4-0000Dl-7P; Tue, 28 Dec 2004 12:58:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjLH4-0001NQ-Lv; Tue, 28 Dec 2004 12:36:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjLC3-0000BP-8Y
	for tsvwg@megatron.ietf.org; Tue, 28 Dec 2004 12:31:35 -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 MAA11774
	for <tsvwg@ietf.org>; Tue, 28 Dec 2004 12:31:32 -0500 (EST)
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjLMz-0008Ho-5r
	for tsvwg@ietf.org; Tue, 28 Dec 2004 12:42:54 -0500
Received: by romeo.rtfm.com (Postfix, from userid 1001)
	id CC1F81702B; Tue, 28 Dec 2004 09:31:12 -0800 (PST)
To: "Amit Jain" <a.jain@f5.com>
Subject: Re: [Tsvwg] Looking for feedback on DTLS
References: <3D8E54E3CAA3864295233C618F53F2ADC819C6@exchfour.olympus.f5net.com>
From: EKR <ekr@rtfm.com>
Date: Tue, 28 Dec 2004 09:31:12 -0800
In-Reply-To: <3D8E54E3CAA3864295233C618F53F2ADC819C6@exchfour.olympus.f5net.com>
	(Amit Jain's message of "Tue, 28 Dec 2004 06:53:08 -0800")
Message-ID: <86d5wugwin.fsf@romeo.rtfm.com>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Security Through
	Obscurity, berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Cc: nagendra@cs.standford.edu.cnri.reston.va.us, ietf-tls@lists.certicom.com,
        tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: EKR <ekr@rtfm.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.0 (/)
X-Scan-Signature: cd3fc8e909678b38737fc606dec187f0

"Amit Jain" <a.jain@f5.com> writes:
> I would like to submit following inputs as the feedback:
Amit,

Thanks for your comments. Responses below.

> Current draft proposes to add fragmentation, reliability and in-order
> delivery to handshake layer while keeping the record layer mostly
> unchanged. 
That's a fair summary, yes.

> Draft seems to imply that the handshake layer sends a collection of
> handshake messages (referred as flight) and then waits for the other end
> to respond. The timeout causes all the messages in flight to be
> retransmitted. 

Yes, that's correct. We considered a cumulative ACK as in TCP
(see Section 4.4 of the DTLS paper) but we ultimately decided that
it wouldn't add that much efficiency improvement and it of
course makes life more complicated. Our initial measurements
seem to support that, but it would of course be very easy to
add ACKs later.

> Here the reliability is being tracked for a complete flight of messages
> as a single unit. Given that a flight can have considerable amount of
> data, the probability of packet loss seems to be high. And since each
> packet loss causes complete flight to be retransmitted, this may be a
> large retransmission again. And this may again suffer a packet loss.

Yes, that's correct, but it's fairly unlikely to be the SAME packet.
You keep going until you've received all the bytes at least once,
not until a given flight comes through intact.

> Also building the reliability and in-order delivery into handshake layer
> makes handshake state machine complicated.
Yes, that's correct. However, the complexity is relatively minimal,
at least in our implementation. 


> I think another approach worth considering may be to introduce a thin
> layer inside record layer which takes care of fragmentation,
> reliability, in-order delivery to record layer. In this approach:
Yes. We considered this approach.  However, we were concerned about
designing a generic reliability layer. Designing reliable transport
protocols is difficult, as evidenced by the fact that we're still
working on TCP after 20+ years. Our feeling was that as the only real
requirement was to make the handshake reliable it was best to tie the
reliability into the handshake process and thus avoid the complexity
and rathole potential of trying to design something more
general. Moreover, there is experience with this kind of state machine
from IKE and other similar protocols.

> 1: A Handshake message can never span multiple records. A record can
> contain multiple handshake messages though.
>  
> This will eliminate the need of handshake message re-assembly.
> Assembling a record will always result in at least one complete
> handshake message or multiple complete handshake messages.

Of course. But it will replace it with record reassembly, which
is basically the same problem.


> This is different from the current specification where the handshake can
> span multiple records. And will need the change in length field of
> record layer (it'll have to be extended to 3 bytes)

Just a clarification: you mean "the current TLS specification" here,
correct? TLS currently has this feature. 


> 2: Records are fragmented and is converted to UDP datagram. 
>  
> These UDP data-grams are then transmitted reliably to other end in the
> handshake phase using a very thin layer (built into record layer). It
> may be analogous to a simple reliable variant of UDP (something like
> TFTP). Here the reliability is tracked for each UDP datagram and only
> the missing UDP datagram is re-transmitted.
>
> This may provide following advantages:
>  
> 1: Handshake layer will be similar to the TLS. There won't be any change
> needed in the implementation of state machine and the specification of
> handshake messages.
That's sort of correct, except that the handshake state machine
will need to do signalling to the record layer about when it wants
reliability. It's also important to note that the DTLS handshake
reliability layer lives mostly at the level of the DTLS handshake
wrapper. The handshake payloads themselves don't change.

> 2: A Record can span multiple UDP packets; this will free DTLS from
> strict need of having a correct path MTU.
Not really. The DTLS handshake doesn't need an exact PMTU. It
just needs an approximate PMTU estimate to make sure that its own
messages get through. Typically it's the applications which need
a PMTU estimate because they actually want to send data in
a single UDP datagram. That's what their non-DTLS behavior
is, after all.

Actually, the approach you suggest makes the PTMU problem
worse in some ways. In the current design, the DTLS implementation
can mostly punt the process of PMTU discovery off to the application.
Because the HS is fairly short, it can use a safe PMTU for its
own traffic and then let the application send large messages until
it becomes clear that it can't. This lets the app use PMTU
discovery mechanisms that are better than those described in
RFC 1191. (Note that this isn't exactly what the DTLS draft
says because I just worked it out recently, but it's a fairly
minor change that doesn't affect interop).

By contrast, if DTLS is in the business of fragmenting data
records, then it has to do so efficiently, which means that
it really needs to know the PMTU. Otherwise, it's at risk
of making fragments that are way too small. I suppose you
could say you'll only fragment handshake records, but that's
kind of a layer violation inside TLS.


> 2: Record layer will consist of a thin reliability layer; this layer
> will be active during handshake phase and will make sure the reliable
> ordered delivery of the handshake messages. During application data
> transfer the reliability part of the record layer is switched off.
This is actually fairly problematic. Remember that in TLS the
handshake and application data can be interlaced during the
rehandshake process. So, it's not a simple matter of reliability
being "on" or "off". You certainly don't want to suddenly
turn applications that expect unreliable semantics into reliable
ones just because they're rehandshaking. (This is a special
problem if the reliability layer provides in-order delivery as
well, which is what's required if you want to not change the
handshake layer at all).

> (Actually this'll mostly depend on the application, and if application
> wants to use reliability mode of record layer, that should be possible
> too.)
I think this illustrates the point I made above about genericity.
The transport requirements for the handshake phase of TLS, which
is short and doesn't move a lot of data, are very different from
the requirements for a generic data transport protocol such as
is provided by the DTLS/TLS record layer. If you're going to
use your reliability layer for data, you're going to want much
better efficiency and congestion control guarantees and suddenly
you're reinventing TCP and SCTP.

> 3: Having a thin reliability layer in Record layer will allow greater
> flexibility and extensibility. Reliability layer can be replaced with
> other reliability mechanism like DCCP in future for providing
> reliability/congestion control.

Well, DCCP wouldn't do the job here since it ONLY provides congestion
control and not reliability. DTLS will of course run fine over DCCP.
It just doesn't make the problem any easier. Michael Tuexen and I
are currently talking about the interaction of DTLS and SCTP, but
I don't think that's a universal solution.
   
-Ekr


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


From tsvwg-bounces@ietf.org  Tue Dec 28 17:20:29 2004
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 RAA08271;
	Tue, 28 Dec 2004 17:20:29 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjPsf-0000vY-O0; Tue, 28 Dec 2004 17:31:54 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjPdW-0000kw-Dz; Tue, 28 Dec 2004 17:16:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjPRW-0006r9-EH
	for tsvwg@megatron.ietf.org; Tue, 28 Dec 2004 17:03:50 -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 RAA06494
	for <tsvwg@ietf.org>; Tue, 28 Dec 2004 17:03:47 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjPcV-0000S9-Aw
	for tsvwg@ietf.org; Tue, 28 Dec 2004 17:15:12 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-5.cisco.com with ESMTP; 28 Dec 2004 14:03:40 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-b.cisco.com (IDENT:mirapoint@mira-sjc5-b.cisco.com
	[171.71.163.14])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iBSM3B05026971;
	Tue, 28 Dec 2004 14:03:13 -0800 (PST)
Received: from cisco.com ([171.69.42.231])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id BAD56290;
	Tue, 28 Dec 2004 13:05:40 -0800 (PST)
Message-ID: <41D1C7DE.6020208@cisco.com>
Date: Tue, 28 Dec 2004 12:53:50 -0800
From: Murali Bashyam <mbashyam@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.0.1) Gecko/20020823
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: EKR <ekr@rtfm.com>
Subject: Re: [Tsvwg] Looking for feedback on DTLS
References: <3D8E54E3CAA3864295233C618F53F2ADC819C6@exchfour.olympus.f5net.com>
	<86d5wugwin.fsf@romeo.rtfm.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 22f8e36c8d8be0bcbb9bf02fb6ce7335
Cc: nagendra@cs.standford.edu.cnri.reston.va.us, ietf-tls@lists.certicom.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>
Content-Type: multipart/mixed; boundary="===============1035402954=="
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 2ed9477f79f24ff120e9894ad9dc9cb5


--===============1035402954==
Content-Type: multipart/alternative;
	boundary="------------080407050208020609030607"


--------------080407050208020609030607
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Hi

I had a question on the congestion control aspect of the handshake 
protocol in DTLS. The draft doesn't seem to address the congestion 
control requirements of the handshake protocol such as how soon is it 
okay to send an entire flight of packets into the network without 
overloading it. I think there's also a problem in retransmitting the 
entire flight when 1 packet in that flight from the original 
transmission got dropped because it starts burdening an already 
congested network. And it's clear from simulation and experience that 
it's more efficient to use TCP mechanisms such  as SACK/NewReno/Reno  to 
recover from scenarios where multiple packets/single packet drop occurs 
in that flight of packets.

Are we really convinced that the amount of code in terms of development 
effort, testing, risk etc to add to handshake protocol to bring in 
in-order delivery, reliability, congestion control etc is less than 
simply addressing the issues that arise as a result of doing split 
channel? It wasn't clear to me that the draft compared the details 
involved in the two approaches.

Murali

EKR wrote:

>"Amit Jain" <a.jain@f5.com> writes:
>  
>
>>I would like to submit following inputs as the feedback:
>>    
>>
>Amit,
>
>Thanks for your comments. Responses below.
>
>  
>
>>Current draft proposes to add fragmentation, reliability and in-order
>>delivery to handshake layer while keeping the record layer mostly
>>unchanged. 
>>    
>>
>That's a fair summary, yes.
>
>  
>
>>Draft seems to imply that the handshake layer sends a collection of
>>handshake messages (referred as flight) and then waits for the other end
>>to respond. The timeout causes all the messages in flight to be
>>retransmitted. 
>>    
>>
>
>Yes, that's correct. We considered a cumulative ACK as in TCP
>(see Section 4.4 of the DTLS paper) but we ultimately decided that
>it wouldn't add that much efficiency improvement and it of
>course makes life more complicated. Our initial measurements
>seem to support that, but it would of course be very easy to
>add ACKs later.
>
>  
>
>>Here the reliability is being tracked for a complete flight of messages
>>as a single unit. Given that a flight can have considerable amount of
>>data, the probability of packet loss seems to be high. And since each
>>packet loss causes complete flight to be retransmitted, this may be a
>>large retransmission again. And this may again suffer a packet loss.
>>    
>>
>
>Yes, that's correct, but it's fairly unlikely to be the SAME packet.
>You keep going until you've received all the bytes at least once,
>not until a given flight comes through intact.
>
>  
>
>>Also building the reliability and in-order delivery into handshake layer
>>makes handshake state machine complicated.
>>    
>>
>Yes, that's correct. However, the complexity is relatively minimal,
>at least in our implementation. 
>
>
>  
>
>>I think another approach worth considering may be to introduce a thin
>>layer inside record layer which takes care of fragmentation,
>>reliability, in-order delivery to record layer. In this approach:
>>    
>>
>Yes. We considered this approach.  However, we were concerned about
>designing a generic reliability layer. Designing reliable transport
>protocols is difficult, as evidenced by the fact that we're still
>working on TCP after 20+ years. Our feeling was that as the only real
>requirement was to make the handshake reliable it was best to tie the
>reliability into the handshake process and thus avoid the complexity
>and rathole potential of trying to design something more
>general. Moreover, there is experience with this kind of state machine
>from IKE and other similar protocols.
>
>  
>
>>1: A Handshake message can never span multiple records. A record can
>>contain multiple handshake messages though.
>> 
>>This will eliminate the need of handshake message re-assembly.
>>Assembling a record will always result in at least one complete
>>handshake message or multiple complete handshake messages.
>>    
>>
>
>Of course. But it will replace it with record reassembly, which
>is basically the same problem.
>
>
>  
>
>>This is different from the current specification where the handshake can
>>span multiple records. And will need the change in length field of
>>record layer (it'll have to be extended to 3 bytes)
>>    
>>
>
>Just a clarification: you mean "the current TLS specification" here,
>correct? TLS currently has this feature. 
>
>
>  
>
>>2: Records are fragmented and is converted to UDP datagram. 
>> 
>>These UDP data-grams are then transmitted reliably to other end in the
>>handshake phase using a very thin layer (built into record layer). It
>>may be analogous to a simple reliable variant of UDP (something like
>>TFTP). Here the reliability is tracked for each UDP datagram and only
>>the missing UDP datagram is re-transmitted.
>>
>>This may provide following advantages:
>> 
>>1: Handshake layer will be similar to the TLS. There won't be any change
>>needed in the implementation of state machine and the specification of
>>handshake messages.
>>    
>>
>That's sort of correct, except that the handshake state machine
>will need to do signalling to the record layer about when it wants
>reliability. It's also important to note that the DTLS handshake
>reliability layer lives mostly at the level of the DTLS handshake
>wrapper. The handshake payloads themselves don't change.
>
>  
>
>>2: A Record can span multiple UDP packets; this will free DTLS from
>>strict need of having a correct path MTU.
>>    
>>
>Not really. The DTLS handshake doesn't need an exact PMTU. It
>just needs an approximate PMTU estimate to make sure that its own
>messages get through. Typically it's the applications which need
>a PMTU estimate because they actually want to send data in
>a single UDP datagram. That's what their non-DTLS behavior
>is, after all.
>
>Actually, the approach you suggest makes the PTMU problem
>worse in some ways. In the current design, the DTLS implementation
>can mostly punt the process of PMTU discovery off to the application.
>Because the HS is fairly short, it can use a safe PMTU for its
>own traffic and then let the application send large messages until
>it becomes clear that it can't. This lets the app use PMTU
>discovery mechanisms that are better than those described in
>RFC 1191. (Note that this isn't exactly what the DTLS draft
>says because I just worked it out recently, but it's a fairly
>minor change that doesn't affect interop).
>
>By contrast, if DTLS is in the business of fragmenting data
>records, then it has to do so efficiently, which means that
>it really needs to know the PMTU. Otherwise, it's at risk
>of making fragments that are way too small. I suppose you
>could say you'll only fragment handshake records, but that's
>kind of a layer violation inside TLS.
>
>
>  
>
>>2: Record layer will consist of a thin reliability layer; this layer
>>will be active during handshake phase and will make sure the reliable
>>ordered delivery of the handshake messages. During application data
>>transfer the reliability part of the record layer is switched off.
>>    
>>
>This is actually fairly problematic. Remember that in TLS the
>handshake and application data can be interlaced during the
>rehandshake process. So, it's not a simple matter of reliability
>being "on" or "off". You certainly don't want to suddenly
>turn applications that expect unreliable semantics into reliable
>ones just because they're rehandshaking. (This is a special
>problem if the reliability layer provides in-order delivery as
>well, which is what's required if you want to not change the
>handshake layer at all).
>
>  
>
>>(Actually this'll mostly depend on the application, and if application
>>wants to use reliability mode of record layer, that should be possible
>>too.)
>>    
>>
>I think this illustrates the point I made above about genericity.
>The transport requirements for the handshake phase of TLS, which
>is short and doesn't move a lot of data, are very different from
>the requirements for a generic data transport protocol such as
>is provided by the DTLS/TLS record layer. If you're going to
>use your reliability layer for data, you're going to want much
>better efficiency and congestion control guarantees and suddenly
>you're reinventing TCP and SCTP.
>
>  
>
>>3: Having a thin reliability layer in Record layer will allow greater
>>flexibility and extensibility. Reliability layer can be replaced with
>>other reliability mechanism like DCCP in future for providing
>>reliability/congestion control.
>>    
>>
>
>Well, DCCP wouldn't do the job here since it ONLY provides congestion
>control and not reliability. DTLS will of course run fine over DCCP.
>It just doesn't make the problem any easier. Michael Tuexen and I
>are currently talking about the interaction of DTLS and SCTP, but
>I don't think that's a universal solution.
>   
>-Ekr
>
>
>_______________________________________________
>tsvwg mailing list
>tsvwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/tsvwg
>  
>


--------------080407050208020609030607
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body>
Hi<br>
<br>
I had a question on the congestion control aspect of the handshake protocol
in DTLS. The draft doesn't seem to address the congestion control requirements
of the handshake protocol such as how soon is it okay to send an entire flight
of packets into the network without overloading it. I think there's also
a problem in retransmitting the entire flight when 1 packet in that flight
from the original transmission got dropped because it starts burdening an
already congested network. And it's clear from simulation and experience
that it's more efficient to use TCP mechanisms such &nbsp;as SACK/NewReno/Reno
&nbsp;to recover from scenarios where multiple packets/single packet drop occurs
in that flight of packets.<br>
<br>
Are we really convinced that the amount of code in terms of development effort,
testing, risk etc to add to handshake protocol to bring in in-order delivery,
reliability, congestion control etc is less than simply addressing the issues
that arise as a result of doing split channel? It wasn't clear to me that
the draft compared the details involved in the two approaches.<br>
<br>
Murali <br>
<br>
EKR wrote:<br>
<blockquote type="cite" cite="mid86d5wugwin.fsf@romeo.rtfm.com">
  <pre wrap="">"Amit Jain" <a class="moz-txt-link-rfc2396E" href="mailto:a.jain@f5.com">&lt;a.jain@f5.com&gt;</a> writes:
  </pre>
  <blockquote type="cite">
    <pre wrap="">I would like to submit following inputs as the feedback:
    </pre>
  </blockquote>
  <pre wrap=""><!---->Amit,

Thanks for your comments. Responses below.

  </pre>
  <blockquote type="cite">
    <pre wrap="">Current draft proposes to add fragmentation, reliability and in-order
delivery to handshake layer while keeping the record layer mostly
unchanged. 
    </pre>
  </blockquote>
  <pre wrap=""><!---->That's a fair summary, yes.

  </pre>
  <blockquote type="cite">
    <pre wrap="">Draft seems to imply that the handshake layer sends a collection of
handshake messages (referred as flight) and then waits for the other end
to respond. The timeout causes all the messages in flight to be
retransmitted. 
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Yes, that's correct. We considered a cumulative ACK as in TCP
(see Section 4.4 of the DTLS paper) but we ultimately decided that
it wouldn't add that much efficiency improvement and it of
course makes life more complicated. Our initial measurements
seem to support that, but it would of course be very easy to
add ACKs later.

  </pre>
  <blockquote type="cite">
    <pre wrap="">Here the reliability is being tracked for a complete flight of messages
as a single unit. Given that a flight can have considerable amount of
data, the probability of packet loss seems to be high. And since each
packet loss causes complete flight to be retransmitted, this may be a
large retransmission again. And this may again suffer a packet loss.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Yes, that's correct, but it's fairly unlikely to be the SAME packet.
You keep going until you've received all the bytes at least once,
not until a given flight comes through intact.

  </pre>
  <blockquote type="cite">
    <pre wrap="">Also building the reliability and in-order delivery into handshake layer
makes handshake state machine complicated.
    </pre>
  </blockquote>
  <pre wrap=""><!---->Yes, that's correct. However, the complexity is relatively minimal,
at least in our implementation. 


  </pre>
  <blockquote type="cite">
    <pre wrap="">I think another approach worth considering may be to introduce a thin
layer inside record layer which takes care of fragmentation,
reliability, in-order delivery to record layer. In this approach:
    </pre>
  </blockquote>
  <pre wrap=""><!---->Yes. We considered this approach.  However, we were concerned about
designing a generic reliability layer. Designing reliable transport
protocols is difficult, as evidenced by the fact that we're still
working on TCP after 20+ years. Our feeling was that as the only real
requirement was to make the handshake reliable it was best to tie the
reliability into the handshake process and thus avoid the complexity
and rathole potential of trying to design something more
general. Moreover, there is experience with this kind of state machine
from IKE and other similar protocols.

  </pre>
  <blockquote type="cite">
    <pre wrap="">1: A Handshake message can never span multiple records. A record can
contain multiple handshake messages though.
 
This will eliminate the need of handshake message re-assembly.
Assembling a record will always result in at least one complete
handshake message or multiple complete handshake messages.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Of course. But it will replace it with record reassembly, which
is basically the same problem.


  </pre>
  <blockquote type="cite">
    <pre wrap="">This is different from the current specification where the handshake can
span multiple records. And will need the change in length field of
record layer (it'll have to be extended to 3 bytes)
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Just a clarification: you mean "the current TLS specification" here,
correct? TLS currently has this feature. 


  </pre>
  <blockquote type="cite">
    <pre wrap="">2: Records are fragmented and is converted to UDP datagram. 
 
These UDP data-grams are then transmitted reliably to other end in the
handshake phase using a very thin layer (built into record layer). It
may be analogous to a simple reliable variant of UDP (something like
TFTP). Here the reliability is tracked for each UDP datagram and only
the missing UDP datagram is re-transmitted.

This may provide following advantages:
 
1: Handshake layer will be similar to the TLS. There won't be any change
needed in the implementation of state machine and the specification of
handshake messages.
    </pre>
  </blockquote>
  <pre wrap=""><!---->That's sort of correct, except that the handshake state machine
will need to do signalling to the record layer about when it wants
reliability. It's also important to note that the DTLS handshake
reliability layer lives mostly at the level of the DTLS handshake
wrapper. The handshake payloads themselves don't change.

  </pre>
  <blockquote type="cite">
    <pre wrap="">2: A Record can span multiple UDP packets; this will free DTLS from
strict need of having a correct path MTU.
    </pre>
  </blockquote>
  <pre wrap=""><!---->Not really. The DTLS handshake doesn't need an exact PMTU. It
just needs an approximate PMTU estimate to make sure that its own
messages get through. Typically it's the applications which need
a PMTU estimate because they actually want to send data in
a single UDP datagram. That's what their non-DTLS behavior
is, after all.

Actually, the approach you suggest makes the PTMU problem
worse in some ways. In the current design, the DTLS implementation
can mostly punt the process of PMTU discovery off to the application.
Because the HS is fairly short, it can use a safe PMTU for its
own traffic and then let the application send large messages until
it becomes clear that it can't. This lets the app use PMTU
discovery mechanisms that are better than those described in
RFC 1191. (Note that this isn't exactly what the DTLS draft
says because I just worked it out recently, but it's a fairly
minor change that doesn't affect interop).

By contrast, if DTLS is in the business of fragmenting data
records, then it has to do so efficiently, which means that
it really needs to know the PMTU. Otherwise, it's at risk
of making fragments that are way too small. I suppose you
could say you'll only fragment handshake records, but that's
kind of a layer violation inside TLS.


  </pre>
  <blockquote type="cite">
    <pre wrap="">2: Record layer will consist of a thin reliability layer; this layer
will be active during handshake phase and will make sure the reliable
ordered delivery of the handshake messages. During application data
transfer the reliability part of the record layer is switched off.
    </pre>
  </blockquote>
  <pre wrap=""><!---->This is actually fairly problematic. Remember that in TLS the
handshake and application data can be interlaced during the
rehandshake process. So, it's not a simple matter of reliability
being "on" or "off". You certainly don't want to suddenly
turn applications that expect unreliable semantics into reliable
ones just because they're rehandshaking. (This is a special
problem if the reliability layer provides in-order delivery as
well, which is what's required if you want to not change the
handshake layer at all).

  </pre>
  <blockquote type="cite">
    <pre wrap="">(Actually this'll mostly depend on the application, and if application
wants to use reliability mode of record layer, that should be possible
too.)
    </pre>
  </blockquote>
  <pre wrap=""><!---->I think this illustrates the point I made above about genericity.
The transport requirements for the handshake phase of TLS, which
is short and doesn't move a lot of data, are very different from
the requirements for a generic data transport protocol such as
is provided by the DTLS/TLS record layer. If you're going to
use your reliability layer for data, you're going to want much
better efficiency and congestion control guarantees and suddenly
you're reinventing TCP and SCTP.

  </pre>
  <blockquote type="cite">
    <pre wrap="">3: Having a thin reliability layer in Record layer will allow greater
flexibility and extensibility. Reliability layer can be replaced with
other reliability mechanism like DCCP in future for providing
reliability/congestion control.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Well, DCCP wouldn't do the job here since it ONLY provides congestion
control and not reliability. DTLS will of course run fine over DCCP.
It just doesn't make the problem any easier. Michael Tuexen and I
are currently talking about the interaction of DTLS and SCTP, but
I don't think that's a universal solution.
   
-Ekr


_______________________________________________
tsvwg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/tsvwg">https://www1.ietf.org/mailman/listinfo/tsvwg</a>
  </pre>
</blockquote>
<br>
</body>
</html>

--------------080407050208020609030607--


--===============1035402954==
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

--===============1035402954==--



From tsvwg-bounces@ietf.org  Tue Dec 28 17:40:43 2004
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 RAA09654;
	Tue, 28 Dec 2004 17:40:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjQCG-0001TB-B4; Tue, 28 Dec 2004 17:52:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjQ06-0005Wb-8C; Tue, 28 Dec 2004 17:39:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjPpP-0003gD-QG
	for tsvwg@megatron.ietf.org; Tue, 28 Dec 2004 17:28: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 RAA08948
	for <tsvwg@ietf.org>; Tue, 28 Dec 2004 17:28:28 -0500 (EST)
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjQ0J-0001AI-JG
	for tsvwg@ietf.org; Tue, 28 Dec 2004 17:39:54 -0500
Received: by romeo.rtfm.com (Postfix, from userid 1001)
	id C7D6917025; Tue, 28 Dec 2004 14:27:35 -0800 (PST)
To: Murali Bashyam <mbashyam@cisco.com>
Subject: Re: [Tsvwg] Looking for feedback on DTLS
References: <3D8E54E3CAA3864295233C618F53F2ADC819C6@exchfour.olympus.f5net.com>
	<86d5wugwin.fsf@romeo.rtfm.com> <41D1C7DE.6020208@cisco.com>
From: EKR <ekr@rtfm.com>
Date: Tue, 28 Dec 2004 14:27:35 -0800
In-Reply-To: <41D1C7DE.6020208@cisco.com> (Murali Bashyam's message of "Tue,
	28 Dec 2004 12:53:50 -0800")
Message-ID: <86k6r2f488.fsf@romeo.rtfm.com>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Security Through
	Obscurity, berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: nagendra@cs.standford.edu.cnri.reston.va.us, ietf-tls@lists.certicom.com,
        tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: EKR <ekr@rtfm.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.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5

Murali Bashyam <mbashyam@cisco.com> writes:
> I had a question on the congestion control aspect of the handshake
> protocol in DTLS. The draft doesn't seem to address the congestion
> control requirements of the handshake protocol such as how soon is it
> okay to send an entire flight of packets into the network without
> overloading it.
We suggest a retransmit timer on the order of 500-1000 ms.

> I think there's also a problem in retransmitting the
> entire flight when 1 packet in that flight from the original
> transmission got dropped because it starts burdening an already
> congested network. And it's clear from simulation and experience that
> it's more efficient to use TCP mechanisms such  as SACK/NewReno/Reno
> to recover from scenarios where multiple packets/single packet drop
> occurs in that flight of packets.

Of course, but we're talking extremely small amounts of data here.
It's important to remember that in your average SSL handshake the
total number of bytes exchanged is generally less than 3k and that
the largest single flight (ServerHello ... ServerHelloDone) is
typically less than 2k [1]. In most cases it will fit in 1-2 MTUs.

Obviously, one could optimize this interaction some, but if you're
in a situation where DTLS handshakes represent a significant fraction
of your network congestion, you've got some really serious problems
that marginally better retransmission response is not going to fix.

> Are we really convinced that the amount of code in terms of
> development effort, testing, risk etc to add to handshake protocol to
> bring in in-order delivery, reliability, congestion control etc is
> less than simply addressing the issues that arise as a result of doing
> split channel? It wasn't clear to me that the draft compared the
> details involved in the two approaches.

It's not addressed in the draft, however we do discuss this point in
S 2.2 of our ISOC NDSS paper[2]. The implementation cost of
adding the timeout and retransmission is relatively small and there
are a number of significant difficulties with using multiple channels,
in particular wrt. during-connection rehandshake.

-Ekr


[1] D. Boneh, H. Shacham, E. Rescorla, "Client Side Caching for TLS",
to appear in ACM TISSEC. 
http://crypto.stanford.edu/~dabo/papers/fasttrack.pdf

[2] N. Modadugu and E. Rescorla, "The Design and Implementation of
Datagram TLS", Proc ISOC NDSS 2004.
http://crypto.stanford.edu/~nagendra/papers/dtls.pdf

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


From tsvwg-bounces@ietf.org  Tue Dec 28 18:01:38 2004
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 SAA10831;
	Tue, 28 Dec 2004 18:01:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjQWV-0001w8-NG; Tue, 28 Dec 2004 18:13:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjQI7-0001Jm-Hf; Tue, 28 Dec 2004 17:58:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjQFc-0000vK-M7
	for tsvwg@megatron.ietf.org; Tue, 28 Dec 2004 17:55:36 -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 RAA10558
	for <tsvwg@ietf.org>; Tue, 28 Dec 2004 17:55:33 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjQQc-0001ok-JA
	for tsvwg@ietf.org; Tue, 28 Dec 2004 18:06:59 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
	by sj-iport-4.cisco.com with ESMTP; 28 Dec 2004 14:55:50 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
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 iBSMt1e6023059;
	Tue, 28 Dec 2004 14:55:02 -0800 (PST)
Received: from cisco.com ([171.69.42.231])
	by mira-sjc5-b.cisco.com (MOS 3.4.5-GR) with ESMTP id BAD64374;
	Tue, 28 Dec 2004 15:06:52 -0800 (PST)
Message-ID: <41D1E445.1000805@cisco.com>
Date: Tue, 28 Dec 2004 14:55:01 -0800
From: Murali Bashyam <mbashyam@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.0.1) Gecko/20020823
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: EKR <ekr@rtfm.com>
Subject: Re: [Tsvwg] Looking for feedback on DTLS
References: <3D8E54E3CAA3864295233C618F53F2ADC819C6@exchfour.olympus.f5net.com>	<86d5wugwin.fsf@romeo.rtfm.com>
	<41D1C7DE.6020208@cisco.com> <86k6r2f488.fsf@romeo.rtfm.com>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 8b6657e60309a1317174c9db2ae5f227
Cc: nagendra@cs.standford.edu.cnri.reston.va.us, ietf-tls@lists.certicom.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>
Content-Type: multipart/mixed; boundary="===============0596072416=="
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: a069a8e8835d39ce36e425c148267a7b


--===============0596072416==
Content-Type: multipart/alternative;
	boundary="------------010006020508060300010608"


--------------010006020508060300010608
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



EKR wrote:

>Murali Bashyam <mbashyam@cisco.com> writes:
>  
>
>>I had a question on the congestion control aspect of the handshake
>>protocol in DTLS. The draft doesn't seem to address the congestion
>>control requirements of the handshake protocol such as how soon is it
>>okay to send an entire flight of packets into the network without
>>overloading it.
>>    
>>
>We suggest a retransmit timer on the order of 500-1000 ms.
>
I was referring more to the TCP capability of slow-start, where TCP 
tries to probe the network
and expands its flight of packets gradually as opposed to sending the 
entire flight in 1 shot. Of course the point which u bring up that the 
flight typically fits in 1-2 packets is true for 1500 MSS probably but 
when MSS is 512 (the common MSS value on the Internet), this immediately 
becomes 6 packets.  I just want to highlight that by avoiding TCP for 
handshaking and implementing retransmissions and timers solves only the 
reliability problem but doesn't address congestion control including 
efficient retransmission possibilities too.

>
>  
>
>>I think there's also a problem in retransmitting the
>>entire flight when 1 packet in that flight from the original
>>transmission got dropped because it starts burdening an already
>>congested network. And it's clear from simulation and experience that
>>it's more efficient to use TCP mechanisms such  as SACK/NewReno/Reno
>>to recover from scenarios where multiple packets/single packet drop
>>occurs in that flight of packets.
>>    
>>
>
>Of course, but we're talking extremely small amounts of data here.
>It's important to remember that in your average SSL handshake the
>total number of bytes exchanged is generally less than 3k and that
>the largest single flight (ServerHello ... ServerHelloDone) is
>typically less than 2k [1]. In most cases it will fit in 1-2 MTUs.
>
True when the MSS is 1500, not when the MSS is negotiated to be 512. 
What about large certificates being sent by the server, that would 
increase the number of messages?

Murali

>
>Obviously, one could optimize this interaction some, but if you're
>in a situation where DTLS handshakes represent a significant fraction
>of your network congestion, you've got some really serious problems
>that marginally better retransmission response is not going to fix.
>
>  
>
>>Are we really convinced that the amount of code in terms of
>>development effort, testing, risk etc to add to handshake protocol to
>>bring in in-order delivery, reliability, congestion control etc is
>>less than simply addressing the issues that arise as a result of doing
>>split channel? It wasn't clear to me that the draft compared the
>>details involved in the two approaches.
>>    
>>
>
>It's not addressed in the draft, however we do discuss this point in
>S 2.2 of our ISOC NDSS paper[2]. The implementation cost of
>adding the timeout and retransmission is relatively small and there
>are a number of significant difficulties with using multiple channels,
>in particular wrt. during-connection rehandshake.
>
>-Ekr
>
>
>[1] D. Boneh, H. Shacham, E. Rescorla, "Client Side Caching for TLS",
>to appear in ACM TISSEC. 
>http://crypto.stanford.edu/~dabo/papers/fasttrack.pdf
>
>[2] N. Modadugu and E. Rescorla, "The Design and Implementation of
>Datagram TLS", Proc ISOC NDSS 2004.
>http://crypto.stanford.edu/~nagendra/papers/dtls.pdf
>  
>


--------------010006020508060300010608
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body>
<br>
<br>
EKR wrote:<br>
<blockquote type="cite" cite="mid86k6r2f488.fsf@romeo.rtfm.com">
  <pre wrap="">Murali Bashyam <a class="moz-txt-link-rfc2396E" href="mailto:mbashyam@cisco.com">&lt;mbashyam@cisco.com&gt;</a> writes:
  </pre>
  <blockquote type="cite">
    <pre wrap="">I had a question on the congestion control aspect of the handshake
protocol in DTLS. The draft doesn't seem to address the congestion
control requirements of the handshake protocol such as how soon is it
okay to send an entire flight of packets into the network without
overloading it.
    </pre>
  </blockquote>
  <pre wrap=""><!---->We suggest a retransmit timer on the order of 500-1000 ms.</pre>
</blockquote>
I was referring more to the TCP capability of slow-start, where TCP tries
to probe the network<br>
and expands its flight of packets gradually as opposed to sending the entire
flight in 1 shot. Of course the point which u bring up that the flight typically
fits in 1-2 packets is true for 1500 MSS probably but when MSS is 512 (the
common MSS value on the Internet), this immediately becomes 6 packets. &nbsp;I
just want to highlight that by avoiding TCP for handshaking and implementing
retransmissions and timers solves only the reliability problem but doesn't
address congestion control including efficient retransmission possibilities
too.<br>
<blockquote type="cite" cite="mid86k6r2f488.fsf@romeo.rtfm.com">
  <pre wrap="">

  </pre>
  <blockquote type="cite">
    <pre wrap="">I think there's also a problem in retransmitting the
entire flight when 1 packet in that flight from the original
transmission got dropped because it starts burdening an already
congested network. And it's clear from simulation and experience that
it's more efficient to use TCP mechanisms such  as SACK/NewReno/Reno
to recover from scenarios where multiple packets/single packet drop
occurs in that flight of packets.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Of course, but we're talking extremely small amounts of data here.
It's important to remember that in your average SSL handshake the
total number of bytes exchanged is generally less than 3k and that
the largest single flight (ServerHello ... ServerHelloDone) is
typically less than 2k [1]. In most cases it will fit in 1-2 MTUs.</pre>
</blockquote>
True when the MSS is 1500, not when the MSS is negotiated to be 512. What
about large certificates being sent by the server, that would increase the
number of messages?<br>
<br>
Murali<br>
<blockquote type="cite" cite="mid86k6r2f488.fsf@romeo.rtfm.com">
  <pre wrap="">

Obviously, one could optimize this interaction some, but if you're
in a situation where DTLS handshakes represent a significant fraction
of your network congestion, you've got some really serious problems
that marginally better retransmission response is not going to fix.

  </pre>
  <blockquote type="cite">
    <pre wrap="">Are we really convinced that the amount of code in terms of
development effort, testing, risk etc to add to handshake protocol to
bring in in-order delivery, reliability, congestion control etc is
less than simply addressing the issues that arise as a result of doing
split channel? It wasn't clear to me that the draft compared the
details involved in the two approaches.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
It's not addressed in the draft, however we do discuss this point in
S 2.2 of our ISOC NDSS paper[2]. The implementation cost of
adding the timeout and retransmission is relatively small and there
are a number of significant difficulties with using multiple channels,
in particular wrt. during-connection rehandshake.

-Ekr


[1] D. Boneh, H. Shacham, E. Rescorla, "Client Side Caching for TLS",
to appear in ACM TISSEC. 
<a class="moz-txt-link-freetext" href="http://crypto.stanford.edu/~dabo/papers/fasttrack.pdf">http://crypto.stanford.edu/~dabo/papers/fasttrack.pdf</a>

[2] N. Modadugu and E. Rescorla, "The Design and Implementation of
Datagram TLS", Proc ISOC NDSS 2004.
<a class="moz-txt-link-freetext" href="http://crypto.stanford.edu/~nagendra/papers/dtls.pdf">http://crypto.stanford.edu/~nagendra/papers/dtls.pdf</a>
  </pre>
</blockquote>
<br>
</body>
</html>

--------------010006020508060300010608--


--===============0596072416==
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

--===============0596072416==--



From tsvwg-bounces@ietf.org  Wed Dec 29 00:04:58 2004
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 AAA04130;
	Wed, 29 Dec 2004 00:04:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjWCB-0002Mu-JB; Wed, 29 Dec 2004 00:16:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjVxm-0004sz-8M; Wed, 29 Dec 2004 00:01:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjVwZ-0004SA-Bu
	for tsvwg@megatron.ietf.org; Wed, 29 Dec 2004 00:00:19 -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 AAA03895
	for <tsvwg@ietf.org>; Wed, 29 Dec 2004 00:00:15 -0500 (EST)
Received: from romeo.rtfm.com ([198.144.203.242])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjW7Y-0002FU-HN
	for tsvwg@ietf.org; Wed, 29 Dec 2004 00:11:44 -0500
Received: by romeo.rtfm.com (Postfix, from userid 1001)
	id 2FA0A17025; Tue, 28 Dec 2004 20:59:54 -0800 (PST)
To: Murali Bashyam <mbashyam@cisco.com>
Subject: Re: [Tsvwg] Looking for feedback on DTLS
References: <3D8E54E3CAA3864295233C618F53F2ADC819C6@exchfour.olympus.f5net.com>
	<86d5wugwin.fsf@romeo.rtfm.com> <41D1C7DE.6020208@cisco.com>
	<86k6r2f488.fsf@romeo.rtfm.com> <41D1E445.1000805@cisco.com>
From: EKR <ekr@rtfm.com>
Date: Tue, 28 Dec 2004 20:59:54 -0800
In-Reply-To: <41D1E445.1000805@cisco.com> (Murali Bashyam's message of "Tue,
	28 Dec 2004 14:55:01 -0800")
Message-ID: <868y7hg0mt.fsf@romeo.rtfm.com>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Security Through
	Obscurity, berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: nagendra@cs.standford.edu.cnri.reston.va.us, ietf-tls@lists.certicom.com,
        tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: EKR <ekr@rtfm.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.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b

Murali Bashyam <mbashyam@cisco.com> writes:

> EKR wrote:
>
>>Murali Bashyam <mbashyam@cisco.com> writes:
>>
>>>I had a question on the congestion control aspect of the handshake
>>>protocol in DTLS. The draft doesn't seem to address the congestion
>>>control requirements of the handshake protocol such as how soon is it
>>>okay to send an entire flight of packets into the network without
>>>overloading it.
>>>
>>We suggest a retransmit timer on the order of 500-1000 ms.
>>
> I was referring more to the TCP capability of slow-start, where TCP
> tries to probe the network
> and expands its flight of packets gradually as opposed to sending the
> entire flight in 1 shot.
That's true, but note that the current TCP initial window
as specified in RFC 3390 is 3 packets with a 1460-byte MSS
and 4 packets with a 512-byte MSS. This looks pretty similar
to what you would see out of a DTLS implementation initially
(though the TCP implementation would back off faster).

> Of course the point which u bring up that the
> flight typically fits in 1-2 packets is true for 1500 MSS probably but
> when MSS is 512 (the common MSS value on the Internet), this
> immediately becomes 6 packets. 

Well, since we're talking about 2k-sized flights here, it's 4 packets,
not 6 for a 512-byte MSS. 512 bytes is actually fairly conservative
in the modern network. According to CAIDA's measurements [1],
over half the TCP traffic by volume uses a 1500-byte packet size:

     The primary features of this distribution originate in the way
     common TCP implementations divide a data stream into
     packets. Approximately 85% of the traffic in these traces is TCP,
     and a large proportion of this TCP traffic is generated by bulk
     transfer applications such as HTTP and FTP. Consequently, the
     majority of the packets seen are one of three sizes: 40 byte
     packets (the minimum packet size for TCP) which carry TCP
     acknowledgments but no payload; 1500 byte packets (the maximum
     Ethernet payload size) from TCP implementations that use path MTU
     discovery; and 552 byte and 576 byte packets from TCP
     implementations that do not use path MTU discovery.


> I just want to highlight that by
> avoiding TCP for handshaking and implementing retransmissions and
> timers solves only the reliability problem but doesn't address
> congestion control including efficient retransmission possibilities
> too.
I don't agree that we're not addressing congestion control.  We
recommend an initial timer value of 500 ms with a typical doubling
exponential backoff with each retransmit. (I know this isn't exactly
what I said earlier, but I had to look it up to refresh my
memory). Given the small amounts of data involved here, I think that's
fairly congestion friendly.

As for efficient retransmission, it's true that DTLS could be smarter
(though with 1500 byte packets and medium-sized (order 1k) server cert
payloads, there's not really much room for improvement) 
but the overall improvement would be fairly modest and would introduce
substantial additional complexity.

>>Of course, but we're talking extremely small amounts of data here.
>>It's important to remember that in your average SSL handshake the
>>total number of bytes exchanged is generally less than 3k and that
>>the largest single flight (ServerHello ... ServerHelloDone) is
>>typically less than 2k [1]. In most cases it will fit in 1-2 MTUs.
>>
> True when the MSS is 1500, not when the MSS is negotiated to be
> 512. What about large certificates being sent by the server, that
> would increase the number of messages?

1k is a fairly large certificate. It's quite uncommon to see a certificate
chain larger than two certificates. That's where I got 2k from.

-Ekr

[1] http://www.caida.org/outreach/papers/2000/AIX0005/AIX0005.html#plen_hist

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


