
From dwing@cisco.com  Tue Nov  1 08:47:59 2011
Return-Path: <dwing@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4513311E80A2 for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 08:47:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.536
X-Spam-Level: 
X-Spam-Status: No, score=-105.536 tagged_above=-999 required=5 tests=[AWL=1.063, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MBc40WCfQglW for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 08:47:58 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id A0C7A11E8094 for <tsvwg@ietf.org>; Tue,  1 Nov 2011 08:47:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=2769; q=dns/txt; s=iport; t=1320162478; x=1321372078; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=NsXRBSrFAtvM3z2AiHxxPV5MhKLh+UBC862lHUXzdYE=; b=g/jQwstxdBcN4BH5fy4LUzpe0dF+mDOfwICA1Y0HglvRbNcn4+w2o+aS TzK+whXNpq81StUwF6++aF9Sb0tCflouK//WlxI+4YegW24jXKtLbO57Q iIH7h/Psq+WWgWGp62Ap+0ssICOOKsyQjtDh8JEz8mYREV1q2sjF0DgeZ k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As4AAB4UsE6rRDoH/2dsb2JhbABCmWiBa41ogQWBcgEBAQMBCAoBFxA/BQcBAwIJDwIEAQEBJwcZIwoJCAEBBBMLF4dgCJZaAZ4ziQcEiAaeCA
X-IronPort-AV: E=Sophos;i="4.69,438,1315180800"; d="scan'208";a="10375072"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 01 Nov 2011 15:47:30 +0000
Received: from dwingWS ([10.32.240.194]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pA1FlUCB018166; Tue, 1 Nov 2011 15:47:30 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Michael Tuexen'" <tuexen@fh-muenster.de>
References: <193601cc9809$2ffa6b50$8fef41f0$@com> <C2980D8C-6CBF-4077-985C-70F4BE09D7C0@fh-muenster.de>
In-Reply-To: <C2980D8C-6CBF-4077-985C-70F4BE09D7C0@fh-muenster.de>
Subject: RE: SCTP-over-UDP and port 9899
Date: Tue, 1 Nov 2011 08:47:30 -0700
Message-ID: <1bbd01cc98ad$9099bb60$b1cd3220$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcyYE9hxtBY6P4LORg+FX1oy3AswoQAmRGRQ
Content-Language: en-us
Cc: tsvwg@ietf.org, randall@lakerest.net
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 15:47:59 -0000

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf
> Of Michael Tuexen
> Sent: Monday, October 31, 2011 2:27 PM
> To: Dan Wing
> Cc: tsvwg@ietf.org; randall@lakerest.net
> Subject: Re: SCTP-over-UDP and port 9899
> 
> On Oct 31, 2011, at 9:10 PM, Dan Wing wrote:
> 
> > http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-udp-encaps-01 and
> its
> > predecessor both say:
> >
> >  "When inserting the UDP header, the source port is 9899, the
> >   destination port is the one stored for the destination address the
> >   packet is sent to or 9899 if no destination address is stored."
> >
> > Why is it important to use a specific source port?  Does that not
> > cause difficulties if there are two (or more) instances of SCTP-
> > over-UDP applications running on the same host?  Does that not
> > cause difficulties, in implementation assumptions, if there are
> > two hosts behind the same NAPT and only one can get UDP/9899
> > forwarded to them?
> Hi Dan,
> 
> for sending out the initial packet of an association, the source
> port is not important.

Then can you strike "the source port is 9899" from the document?

> The peer will send back the response to any
> port. But the destination port of the initial packet is important.
> It must be the same port the peer is accepting UDP packets. It
> can be any port, but then it needs to be negotiated somehow.

Sure, of course.

The 32-bit or 128-bit IP address is already negotiated.  
Negotiating another 16 bits is not onerous.  It isn't easy
with DNS (because neither SRV records nor the ability to
update them is ubiquitous), but lots of protocols already
communicate IP address and port -- BitTorrent, Skype, SIP,
many others.

> Since there is one registered port for SCTP/UDP, I used that.
> But you can use a different one, if negotiated. If you want to
> run two hosts as servers behind a NAT, you need different UDP
> ports. If they are clients, you don't.
>
> > In short, what is the benefit of using 9899 as the source port?
> It is more a default, if nothing else is known. In the socketAPI
> section the remote port is configurable. The local port (at
> least in the FreeBSD/MacOS X implementation) is a parameter
> controller by a sysctl variable. So (currently) a single
> host uses a single port number for all associations.
> 
> Does this makes things clearer?

Not especially, no.

Let's look at, for example, SSH -- the SSH port is 22.   But
there is no need for the *source port* to be 22.  I'm trying
to understand why there is text mentioning anything about
the source port in draft-ietf-tsvwg-sctp-udp-encaps.

-d


> Best regards
> Michael
> >
> > -d
> >
> >
> >


From tuexen@fh-muenster.de  Tue Nov  1 09:50:16 2011
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E7CA21F84DB for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 09:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FTwtDHQKy6gM for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 09:50:15 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id E761C21F8541 for <tsvwg@ietf.org>; Tue,  1 Nov 2011 09:49:37 -0700 (PDT)
Received: from [192.168.1.200] (p508FC512.dip.t-dialin.net [80.143.197.18]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 2EEC31C0B461B; Tue,  1 Nov 2011 17:49:35 +0100 (CET)
Subject: Re: SCTP-over-UDP and port 9899
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <1bbd01cc98ad$9099bb60$b1cd3220$@com>
Date: Tue, 1 Nov 2011 17:49:34 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <FBB2B325-47B2-4EAF-AE52-5ED2233C1C57@fh-muenster.de>
References: <193601cc9809$2ffa6b50$8fef41f0$@com> <C2980D8C-6CBF-4077-985C-70F4BE09D7C0@fh-muenster.de> <1bbd01cc98ad$9099bb60$b1cd3220$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: tsvwg@ietf.org, randall@lakerest.net
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 16:50:16 -0000

On Nov 1, 2011, at 4:47 PM, Dan Wing wrote:

>> -----Original Message-----
>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf
>> Of Michael Tuexen
>> Sent: Monday, October 31, 2011 2:27 PM
>> To: Dan Wing
>> Cc: tsvwg@ietf.org; randall@lakerest.net
>> Subject: Re: SCTP-over-UDP and port 9899
>> 
>> On Oct 31, 2011, at 9:10 PM, Dan Wing wrote:
>> 
>>> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-udp-encaps-01 and
>> its
>>> predecessor both say:
>>> 
>>> "When inserting the UDP header, the source port is 9899, the
>>>  destination port is the one stored for the destination address the
>>>  packet is sent to or 9899 if no destination address is stored."
>>> 
>>> Why is it important to use a specific source port?  Does that not
>>> cause difficulties if there are two (or more) instances of SCTP-
>>> over-UDP applications running on the same host?  Does that not
>>> cause difficulties, in implementation assumptions, if there are
>>> two hosts behind the same NAPT and only one can get UDP/9899
>>> forwarded to them?
>> Hi Dan,
>> 
>> for sending out the initial packet of an association, the source
>> port is not important.
> 
> Then can you strike "the source port is 9899" from the document?
> 
>> The peer will send back the response to any
>> port. But the destination port of the initial packet is important.
>> It must be the same port the peer is accepting UDP packets. It
>> can be any port, but then it needs to be negotiated somehow.
> 
> Sure, of course.
> 
> The 32-bit or 128-bit IP address is already negotiated.  
> Negotiating another 16 bits is not onerous.  It isn't easy
> with DNS (because neither SRV records nor the ability to
> update them is ubiquitous), but lots of protocols already
> communicate IP address and port -- BitTorrent, Skype, SIP,
> many others.
> 
>> Since there is one registered port for SCTP/UDP, I used that.
>> But you can use a different one, if negotiated. If you want to
>> run two hosts as servers behind a NAT, you need different UDP
>> ports. If they are clients, you don't.
>> 
>>> In short, what is the benefit of using 9899 as the source port?
>> It is more a default, if nothing else is known. In the socketAPI
>> section the remote port is configurable. The local port (at
>> least in the FreeBSD/MacOS X implementation) is a parameter
>> controller by a sysctl variable. So (currently) a single
>> host uses a single port number for all associations.
>> 
>> Does this makes things clearer?
> 
> Not especially, no.
> 
> Let's look at, for example, SSH -- the SSH port is 22.   But
> there is no need for the *source port* to be 22.  I'm trying
> to understand why there is text mentioning anything about
> the source port in draft-ietf-tsvwg-sctp-udp-encaps.
OK, this is a good example. I want 9899 for SCTP/UDP be similar
to 22 for SSH. But there is a difference. I want to support the
case where I have one SCTP stack on a host and this stack uses
a single UDP port number shared between all associations, no
matter which side initiated them. I might not have made that
clear. So it different from SSH where the server binds to a
well known port (or not if otherwise negotiated), the client
uses an arbitrary one. Do you have a suggestion for the wording?

Best regards
Michael
> 
> -d
> 
> 
>> Best regards
>> Michael
>>> 
>>> -d
>>> 
>>> 
>>> 
> 
> 


From dwing@cisco.com  Tue Nov  1 10:16:47 2011
Return-Path: <dwing@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB44B11E8080 for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 10:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.578
X-Spam-Level: 
X-Spam-Status: No, score=-105.578 tagged_above=-999 required=5 tests=[AWL=1.021, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aYrqda5d5alH for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 10:16:46 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id A0F7511E80B0 for <tsvwg@ietf.org>; Tue,  1 Nov 2011 10:16:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=4745; q=dns/txt; s=iport; t=1320167806; x=1321377406; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=4yzVSl1l7pb1KQZZZb/1FwaII+o36z9UY1K5hvIQIAs=; b=d2/irl6zWv909CX5jDjeRd43lNHdGuhfXnP//q+8xA8WxskgPKMW2Gki OuQMAW7iYU7ZQuudvkPbEaYT9dyfq6anprncwZavxO462W77gi9yJO4Q8 8d86+xY8swGZGKSyfheLUNLI5kJ1ws6ZewUGtI5/9dQdXvIf57QNrN2GW M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AskAAOoosE6rRDoG/2dsb2JhbABCmWmBa4xHgSqBBYFyAQEBAwEICgEXED8FBwEDAgkPAgQBAQEnBxkjCgkIAQEEEwsXh2AIln4Bni6JBwSIBp4I
X-IronPort-AV: E=Sophos;i="4.69,439,1315180800"; d="scan'208";a="11700667"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 01 Nov 2011 17:15:39 +0000
Received: from dwingWS ([10.32.240.194]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pA1HFddE023311; Tue, 1 Nov 2011 17:15:39 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Michael Tuexen'" <tuexen@fh-muenster.de>
References: <193601cc9809$2ffa6b50$8fef41f0$@com> <C2980D8C-6CBF-4077-985C-70F4BE09D7C0@fh-muenster.de> <1bbd01cc98ad$9099bb60$b1cd3220$@com> <FBB2B325-47B2-4EAF-AE52-5ED2233C1C57@fh-muenster.de>
In-Reply-To: <FBB2B325-47B2-4EAF-AE52-5ED2233C1C57@fh-muenster.de>
Subject: RE: SCTP-over-UDP and port 9899
Date: Tue, 1 Nov 2011 10:15:39 -0700
Message-ID: <1c0401cc98b9$e0bdab40$a23901c0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcyYtkEQlvfClTxXSJu57Yke4Jr8dQAAllsw
Content-Language: en-us
Cc: tsvwg@ietf.org, randall@lakerest.net
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 17:16:47 -0000

> -----Original Message-----
> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> Sent: Tuesday, November 01, 2011 9:50 AM
> To: Dan Wing
> Cc: tsvwg@ietf.org; randall@lakerest.net
> Subject: Re: SCTP-over-UDP and port 9899
> 
> 
> On Nov 1, 2011, at 4:47 PM, Dan Wing wrote:
> 
> >> -----Original Message-----
> >> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On
> Behalf
> >> Of Michael Tuexen
> >> Sent: Monday, October 31, 2011 2:27 PM
> >> To: Dan Wing
> >> Cc: tsvwg@ietf.org; randall@lakerest.net
> >> Subject: Re: SCTP-over-UDP and port 9899
> >>
> >> On Oct 31, 2011, at 9:10 PM, Dan Wing wrote:
> >>
> >>> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-udp-encaps-01 and
> >> its
> >>> predecessor both say:
> >>>
> >>> "When inserting the UDP header, the source port is 9899, the
> >>>  destination port is the one stored for the destination address the
> >>>  packet is sent to or 9899 if no destination address is stored."
> >>>
> >>> Why is it important to use a specific source port?  Does that not
> >>> cause difficulties if there are two (or more) instances of SCTP-
> >>> over-UDP applications running on the same host?  Does that not
> >>> cause difficulties, in implementation assumptions, if there are
> >>> two hosts behind the same NAPT and only one can get UDP/9899
> >>> forwarded to them?
> >> Hi Dan,
> >>
> >> for sending out the initial packet of an association, the source
> >> port is not important.
> >
> > Then can you strike "the source port is 9899" from the document?
> >
> >> The peer will send back the response to any
> >> port. But the destination port of the initial packet is important.
> >> It must be the same port the peer is accepting UDP packets. It
> >> can be any port, but then it needs to be negotiated somehow.
> >
> > Sure, of course.
> >
> > The 32-bit or 128-bit IP address is already negotiated.
> > Negotiating another 16 bits is not onerous.  It isn't easy
> > with DNS (because neither SRV records nor the ability to
> > update them is ubiquitous), but lots of protocols already
> > communicate IP address and port -- BitTorrent, Skype, SIP,
> > many others.
> >
> >> Since there is one registered port for SCTP/UDP, I used that.
> >> But you can use a different one, if negotiated. If you want to
> >> run two hosts as servers behind a NAT, you need different UDP
> >> ports. If they are clients, you don't.
> >>
> >>> In short, what is the benefit of using 9899 as the source port?
> >> It is more a default, if nothing else is known. In the socketAPI
> >> section the remote port is configurable. The local port (at
> >> least in the FreeBSD/MacOS X implementation) is a parameter
> >> controller by a sysctl variable. So (currently) a single
> >> host uses a single port number for all associations.
> >>
> >> Does this makes things clearer?
> >
> > Not especially, no.
> >
> > Let's look at, for example, SSH -- the SSH port is 22.   But
> > there is no need for the *source port* to be 22.  I'm trying
> > to understand why there is text mentioning anything about
> > the source port in draft-ietf-tsvwg-sctp-udp-encaps.
> OK, this is a good example. I want 9899 for SCTP/UDP be similar
> to 22 for SSH. But there is a difference. I want to support the
> case where I have one SCTP stack on a host and this stack uses
> a single UDP port number shared between all associations, no
> matter which side initiated them.

But a major use-case for SCTP-over-UDP is when the application
itself has its own SCTP stack.  This is even mentioned in 
your I-D.  For that use-case, the two applications cannot
achieve your desired goal.

> I might not have made that
> clear. So it different from SSH where the server binds to a
> well known port (or not if otherwise negotiated), the client
> uses an arbitrary one. Do you have a suggestion for the wording?

Yes, remove the wording saying 9899 is the source port.  

Suggest:

  It can be advantageous for all SCTP-over-UDP traffic originated by a
  host to use the same source port (e.g., this reduces the number of
  mappings in firewalls and NATs, among other things).  It is possible
  to use the same UDP source port by using the SCTP header to
  demultiplex the incoming traffic (rather than demultiplexing solely
  on UDP port number). When SCTP-over-UDP is implemented by a shared
  library (e.g., a framework or by the OS itself), this optimization
  is possible.  When SCTP-over-UDP is implemented by an application,
  this optimization is usually not possible.

-d


> Best regards
> Michael
> >
> > -d
> >
> >
> >> Best regards
> >> Michael
> >>>
> >>> -d
> >>>
> >>>
> >>>
> >
> >


From touch@isi.edu  Tue Nov  1 11:19:02 2011
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 125271F0C6F for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 11:19:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.27
X-Spam-Level: 
X-Spam-Status: No, score=-103.27 tagged_above=-999 required=5 tests=[AWL=-0.671, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 94a50eIe4JKG for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 11:19:01 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 7D21211E80C7 for <tsvwg@ietf.org>; Tue,  1 Nov 2011 11:19:01 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id pA1IIEIP011046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 1 Nov 2011 11:18:15 -0700 (PDT)
Message-ID: <4EB037E6.6050809@isi.edu>
Date: Tue, 01 Nov 2011 11:18:14 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
Subject: Re: SCTP-over-UDP and port 9899
References: <193601cc9809$2ffa6b50$8fef41f0$@com> <C2980D8C-6CBF-4077-985C-70F4BE09D7C0@fh-muenster.de> <1bbd01cc98ad$9099bb60$b1cd3220$@com> <FBB2B325-47B2-4EAF-AE52-5ED2233C1C57@fh-muenster.de> <1c0401cc98b9$e0bdab40$a23901c0$@com>
In-Reply-To: <1c0401cc98b9$e0bdab40$a23901c0$@com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: 'Michael Tuexen' <tuexen@fh-muenster.de>, tsvwg@ietf.org, randall@lakerest.net
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 18:19:02 -0000

On 11/1/2011 10:15 AM, Dan Wing wrote:
...
>> I might not have made that
>> clear. So it different from SSH where the server binds to a
>> well known port (or not if otherwise negotiated), the client
>> uses an arbitrary one. Do you have a suggestion for the wording?
>
> Yes, remove the wording saying 9899 is the source port.

Agreed.

FWIW, 9899 is reserved in IANA, but IANA assigns only *destination* ports.

Source ports are not assigned. So just because a port is assigned does 
not mean it has any meaning solely as a source port. Source port meaning 
is based only on the socket-pair tuple (src addr, src port, dst addr, 
dst port).

Joe

From touch@isi.edu  Tue Nov  1 11:24:10 2011
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09C031F0C80 for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 11:24:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.232
X-Spam-Level: 
X-Spam-Status: No, score=-103.232 tagged_above=-999 required=5 tests=[AWL=-0.633, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hvp8LhXOgWtV for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 11:24:09 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 986E51F0C7D for <tsvwg@ietf.org>; Tue,  1 Nov 2011 11:24:09 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id pA1IKe3S011663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 1 Nov 2011 11:20:41 -0700 (PDT)
Message-ID: <4EB03878.20002@isi.edu>
Date: Tue, 01 Nov 2011 11:20:40 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
Subject: Re: SCTP-over-UDP and port 9899
References: <193601cc9809$2ffa6b50$8fef41f0$@com> <C2980D8C-6CBF-4077-985C-70F4BE09D7C0@fh-muenster.de> <1bbd01cc98ad$9099bb60$b1cd3220$@com> <FBB2B325-47B2-4EAF-AE52-5ED2233C1C57@fh-muenster.de> <1c0401cc98b9$e0bdab40$a23901c0$@com> <4EB037E6.6050809@isi.edu>
In-Reply-To: <4EB037E6.6050809@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: 'Michael Tuexen' <tuexen@fh-muenster.de>, tsvwg@ietf.org, randall@lakerest.net
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 18:24:10 -0000

On 11/1/2011 11:18 AM, Joe Touch wrote:
>
>
> On 11/1/2011 10:15 AM, Dan Wing wrote:
> ...
>>> I might not have made that
>>> clear. So it different from SSH where the server binds to a
>>> well known port (or not if otherwise negotiated), the client
>>> uses an arbitrary one. Do you have a suggestion for the wording?
>>
>> Yes, remove the wording saying 9899 is the source port.
>
> Agreed.
>
> FWIW, 9899 is reserved in IANA, but IANA assigns only *destination* ports.

Correction - "reserved" is not meant in the IANA sense. It is "assigned" 
(to SCTP over UDP), specifically.

>
> Source ports are not assigned. So just because a port is assigned does
> not mean it has any meaning solely as a source port. Source port meaning
> is based only on the socket-pair tuple (src addr, src port, dst addr,
> dst port).
>
> Joe

From tuexen@fh-muenster.de  Tue Nov  1 12:59:04 2011
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB6F111E8173 for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 12:59:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ARKVN6rfycqG for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 12:59:04 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 4DC6D11E812D for <tsvwg@ietf.org>; Tue,  1 Nov 2011 12:59:02 -0700 (PDT)
Received: from [192.168.1.200] (p508FC512.dip.t-dialin.net [80.143.197.18]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id C25E51C0B461B; Tue,  1 Nov 2011 20:58:56 +0100 (CET)
Subject: Re: SCTP-over-UDP and port 9899
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <1c0401cc98b9$e0bdab40$a23901c0$@com>
Date: Tue, 1 Nov 2011 20:58:55 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <1E7B798E-8AE2-4E2E-829E-1E7075D2C74E@fh-muenster.de>
References: <193601cc9809$2ffa6b50$8fef41f0$@com> <C2980D8C-6CBF-4077-985C-70F4BE09D7C0@fh-muenster.de> <1bbd01cc98ad$9099bb60$b1cd3220$@com> <FBB2B325-47B2-4EAF-AE52-5ED2233C1C57@fh-muenster.de> <1c0401cc98b9$e0bdab40$a23901c0$@com>
To: "Dan Wing" <dwing@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: tsvwg@ietf.org, randall@lakerest.net
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 19:59:05 -0000

On Nov 1, 2011, at 6:15 PM, Dan Wing wrote:

>> -----Original Message-----
>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>> Sent: Tuesday, November 01, 2011 9:50 AM
>> To: Dan Wing
>> Cc: tsvwg@ietf.org; randall@lakerest.net
>> Subject: Re: SCTP-over-UDP and port 9899
>> 
>> 
>> On Nov 1, 2011, at 4:47 PM, Dan Wing wrote:
>> 
>>>> -----Original Message-----
>>>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On
>> Behalf
>>>> Of Michael Tuexen
>>>> Sent: Monday, October 31, 2011 2:27 PM
>>>> To: Dan Wing
>>>> Cc: tsvwg@ietf.org; randall@lakerest.net
>>>> Subject: Re: SCTP-over-UDP and port 9899
>>>> 
>>>> On Oct 31, 2011, at 9:10 PM, Dan Wing wrote:
>>>> 
>>>>> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-udp-encaps-01 and
>>>> its
>>>>> predecessor both say:
>>>>> 
>>>>> "When inserting the UDP header, the source port is 9899, the
>>>>> destination port is the one stored for the destination address the
>>>>> packet is sent to or 9899 if no destination address is stored."
>>>>> 
>>>>> Why is it important to use a specific source port?  Does that not
>>>>> cause difficulties if there are two (or more) instances of SCTP-
>>>>> over-UDP applications running on the same host?  Does that not
>>>>> cause difficulties, in implementation assumptions, if there are
>>>>> two hosts behind the same NAPT and only one can get UDP/9899
>>>>> forwarded to them?
>>>> Hi Dan,
>>>> 
>>>> for sending out the initial packet of an association, the source
>>>> port is not important.
>>> 
>>> Then can you strike "the source port is 9899" from the document?
>>> 
>>>> The peer will send back the response to any
>>>> port. But the destination port of the initial packet is important.
>>>> It must be the same port the peer is accepting UDP packets. It
>>>> can be any port, but then it needs to be negotiated somehow.
>>> 
>>> Sure, of course.
>>> 
>>> The 32-bit or 128-bit IP address is already negotiated.
>>> Negotiating another 16 bits is not onerous.  It isn't easy
>>> with DNS (because neither SRV records nor the ability to
>>> update them is ubiquitous), but lots of protocols already
>>> communicate IP address and port -- BitTorrent, Skype, SIP,
>>> many others.
>>> 
>>>> Since there is one registered port for SCTP/UDP, I used that.
>>>> But you can use a different one, if negotiated. If you want to
>>>> run two hosts as servers behind a NAT, you need different UDP
>>>> ports. If they are clients, you don't.
>>>> 
>>>>> In short, what is the benefit of using 9899 as the source port?
>>>> It is more a default, if nothing else is known. In the socketAPI
>>>> section the remote port is configurable. The local port (at
>>>> least in the FreeBSD/MacOS X implementation) is a parameter
>>>> controller by a sysctl variable. So (currently) a single
>>>> host uses a single port number for all associations.
>>>> 
>>>> Does this makes things clearer?
>>> 
>>> Not especially, no.
>>> 
>>> Let's look at, for example, SSH -- the SSH port is 22.   But
>>> there is no need for the *source port* to be 22.  I'm trying
>>> to understand why there is text mentioning anything about
>>> the source port in draft-ietf-tsvwg-sctp-udp-encaps.
>> OK, this is a good example. I want 9899 for SCTP/UDP be similar
>> to 22 for SSH. But there is a difference. I want to support the
>> case where I have one SCTP stack on a host and this stack uses
>> a single UDP port number shared between all associations, no
>> matter which side initiated them.
> 
> But a major use-case for SCTP-over-UDP is when the application
> itself has its own SCTP stack.  This is even mentioned in 
> your I-D.  For that use-case, the two applications cannot
> achieve your desired goal.
I agree.
> 
>> I might not have made that
>> clear. So it different from SSH where the server binds to a
>> well known port (or not if otherwise negotiated), the client
>> uses an arbitrary one. Do you have a suggestion for the wording?
> 
> Yes, remove the wording saying 9899 is the source port.  
> 
> Suggest:
> 
>  It can be advantageous for all SCTP-over-UDP traffic originated by a
>  host to use the same source port (e.g., this reduces the number of
>  mappings in firewalls and NATs, among other things).  It is possible
>  to use the same UDP source port by using the SCTP header to
>  demultiplex the incoming traffic (rather than demultiplexing solely
>  on UDP port number). When SCTP-over-UDP is implemented by a shared
>  library (e.g., a framework or by the OS itself), this optimization
>  is possible.  When SCTP-over-UDP is implemented by an application,
>  this optimization is usually not possible.
OK. Thank you very much. What about the following changes:

Adding to the subsection 4.1 (Architectural Considerations):

   Each SCTP stack uses a single local UDP encapsulation port number as
   the source port for all of its outgoing SCTP packets and as the
   destination port for all its incoming SCTP packets.  The IANA
   assinged value of 9989 MAY be used as this port number.  If there is
   only a single SCTP implementation on a host (for example, a kernel
   implementation being part of the operating system), using a single
   UDP encapsulation port number per host can be advantageous (e.g.,
   this reduces the number of mappings in firewalls and NATs, among
   other things).  However, this is not possible if the SCTP stack is
   implemented as part of an application.

Changing the beginning of subsection 4.3 (Encapsulation Procedure):

   When inserting the UDP header, the source port is local UDP
   encapsulation port number of the SCTP stack, the destination port is
   the remote UDP encapsualtion port number stored for the destination
   address the packet is sent to (see Section 4.1).

Does this address your issue completely? I just want to mention that it
might be good to use the IANA assigned number when possible.

Best regards
Michael
> 
> -d
> 
> 
>> Best regards
>> Michael
>>> 
>>> -d
>>> 
>>> 
>>>> Best regards
>>>> Michael
>>>>> 
>>>>> -d
>>>>> 
>>>>> 
>>>>> 
>>> 
>>> 
> 
> 


From dwing@cisco.com  Tue Nov  1 14:56:45 2011
Return-Path: <dwing@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADB481F0C42 for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 14:56:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fQCDiYrkYcOW for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 14:56:44 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id DFFA41F0C36 for <tsvwg@ietf.org>; Tue,  1 Nov 2011 14:56:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=7039; q=dns/txt; s=iport; t=1320184605; x=1321394205; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=I05LMRu+tz8Ymq5nWiDnxEW306DLMPC3qkm1ohlu+mU=; b=eaylUUafTek9k35f1v3o48qyh4CCf/3PojKq8SnAnQ4oDgq/oX1SXn3h AN743/ITqH1dk12m2n+sEz2e2rfSk6pLdc9GYB/wvHidGxfg2UcguLfjp GE86ecXYIhAjaXqPgisBAYynLFTp/r9POYII51ZQMewbQC5dB8hHiltZA 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AskAADJqsE6rRDoH/2dsb2JhbABDmWyBa4xHgSuBBYFyAQEBAwEICgEXED8FBwEDAgkPAgQBAQEnBxkjCgkIAQEEEwsXh2AIlyABniaJBwSIBp4I
X-IronPort-AV: E=Sophos;i="4.69,440,1315180800"; d="scan'208";a="11748433"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 01 Nov 2011 21:56:44 +0000
Received: from dwingWS (dhcp-171-70-249-135.cisco.com [171.70.249.135]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pA1Lui8I015836; Tue, 1 Nov 2011 21:56:44 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Michael Tuexen'" <tuexen@fh-muenster.de>
References: <193601cc9809$2ffa6b50$8fef41f0$@com> <C2980D8C-6CBF-4077-985C-70F4BE09D7C0@fh-muenster.de> <1bbd01cc98ad$9099bb60$b1cd3220$@com> <FBB2B325-47B2-4EAF-AE52-5ED2233C1C57@fh-muenster.de> <1c0401cc98b9$e0bdab40$a23901c0$@com> <1E7B798E-8AE2-4E2E-829E-1E7075D2C74E@fh-muenster.de>
In-Reply-To: <1E7B798E-8AE2-4E2E-829E-1E7075D2C74E@fh-muenster.de>
Subject: RE: SCTP-over-UDP and port 9899
Date: Tue, 1 Nov 2011 14:56:44 -0700
Message-ID: <1df701cc98e1$25519970$6ff4cc50$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcyY0LOOof3wPJk9S+W5Wf5gtBy2oAAD8Xgg
Content-Language: en-us
Cc: tsvwg@ietf.org, randall@lakerest.net
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 21:56:45 -0000

> -----Original Message-----
> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> Sent: Tuesday, November 01, 2011 12:59 PM
> To: Dan Wing
> Cc: tsvwg@ietf.org; randall@lakerest.net
> Subject: Re: SCTP-over-UDP and port 9899
> 
> On Nov 1, 2011, at 6:15 PM, Dan Wing wrote:
> 
> >> -----Original Message-----
> >> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> >> Sent: Tuesday, November 01, 2011 9:50 AM
> >> To: Dan Wing
> >> Cc: tsvwg@ietf.org; randall@lakerest.net
> >> Subject: Re: SCTP-over-UDP and port 9899
> >>
> >>
> >> On Nov 1, 2011, at 4:47 PM, Dan Wing wrote:
> >>
> >>>> -----Original Message-----
> >>>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On
> >> Behalf
> >>>> Of Michael Tuexen
> >>>> Sent: Monday, October 31, 2011 2:27 PM
> >>>> To: Dan Wing
> >>>> Cc: tsvwg@ietf.org; randall@lakerest.net
> >>>> Subject: Re: SCTP-over-UDP and port 9899
> >>>>
> >>>> On Oct 31, 2011, at 9:10 PM, Dan Wing wrote:
> >>>>
> >>>>> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-udp-encaps-01
> and
> >>>> its
> >>>>> predecessor both say:
> >>>>>
> >>>>> "When inserting the UDP header, the source port is 9899, the
> >>>>> destination port is the one stored for the destination address
> the
> >>>>> packet is sent to or 9899 if no destination address is stored."
> >>>>>
> >>>>> Why is it important to use a specific source port?  Does that not
> >>>>> cause difficulties if there are two (or more) instances of SCTP-
> >>>>> over-UDP applications running on the same host?  Does that not
> >>>>> cause difficulties, in implementation assumptions, if there are
> >>>>> two hosts behind the same NAPT and only one can get UDP/9899
> >>>>> forwarded to them?
> >>>> Hi Dan,
> >>>>
> >>>> for sending out the initial packet of an association, the source
> >>>> port is not important.
> >>>
> >>> Then can you strike "the source port is 9899" from the document?
> >>>
> >>>> The peer will send back the response to any
> >>>> port. But the destination port of the initial packet is important.
> >>>> It must be the same port the peer is accepting UDP packets. It
> >>>> can be any port, but then it needs to be negotiated somehow.
> >>>
> >>> Sure, of course.
> >>>
> >>> The 32-bit or 128-bit IP address is already negotiated.
> >>> Negotiating another 16 bits is not onerous.  It isn't easy
> >>> with DNS (because neither SRV records nor the ability to
> >>> update them is ubiquitous), but lots of protocols already
> >>> communicate IP address and port -- BitTorrent, Skype, SIP,
> >>> many others.
> >>>
> >>>> Since there is one registered port for SCTP/UDP, I used that.
> >>>> But you can use a different one, if negotiated. If you want to
> >>>> run two hosts as servers behind a NAT, you need different UDP
> >>>> ports. If they are clients, you don't.
> >>>>
> >>>>> In short, what is the benefit of using 9899 as the source port?
> >>>> It is more a default, if nothing else is known. In the socketAPI
> >>>> section the remote port is configurable. The local port (at
> >>>> least in the FreeBSD/MacOS X implementation) is a parameter
> >>>> controller by a sysctl variable. So (currently) a single
> >>>> host uses a single port number for all associations.
> >>>>
> >>>> Does this makes things clearer?
> >>>
> >>> Not especially, no.
> >>>
> >>> Let's look at, for example, SSH -- the SSH port is 22.   But
> >>> there is no need for the *source port* to be 22.  I'm trying
> >>> to understand why there is text mentioning anything about
> >>> the source port in draft-ietf-tsvwg-sctp-udp-encaps.
> >> OK, this is a good example. I want 9899 for SCTP/UDP be similar
> >> to 22 for SSH. But there is a difference. I want to support the
> >> case where I have one SCTP stack on a host and this stack uses
> >> a single UDP port number shared between all associations, no
> >> matter which side initiated them.
> >
> > But a major use-case for SCTP-over-UDP is when the application
> > itself has its own SCTP stack.  This is even mentioned in
> > your I-D.  For that use-case, the two applications cannot
> > achieve your desired goal.
> I agree.
> >
> >> I might not have made that
> >> clear. So it different from SSH where the server binds to a
> >> well known port (or not if otherwise negotiated), the client
> >> uses an arbitrary one. Do you have a suggestion for the wording?
> >
> > Yes, remove the wording saying 9899 is the source port.
> >
> > Suggest:
> >
> >  It can be advantageous for all SCTP-over-UDP traffic originated by a
> >  host to use the same source port (e.g., this reduces the number of
> >  mappings in firewalls and NATs, among other things).  It is possible
> >  to use the same UDP source port by using the SCTP header to
> >  demultiplex the incoming traffic (rather than demultiplexing solely
> >  on UDP port number). When SCTP-over-UDP is implemented by a shared
> >  library (e.g., a framework or by the OS itself), this optimization
> >  is possible.  When SCTP-over-UDP is implemented by an application,
> >  this optimization is usually not possible.
> OK. Thank you very much. What about the following changes:
> 
> Adding to the subsection 4.1 (Architectural Considerations):
> 
>    Each SCTP stack uses a single local UDP encapsulation port number as
>    the source port for all of its outgoing SCTP packets and as the
>    destination port for all its incoming SCTP packets.  The IANA
..........................................................^^^^^^^^
>    assinged value of 9989 MAY be used as this port number.  If there is
.....^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>    only a single SCTP implementation on a host (for example, a kernel
>    implementation being part of the operating system), using a single
>    UDP encapsulation port number per host can be advantageous (e.g.,
>    this reduces the number of mappings in firewalls and NATs, among
>    other things).  However, this is not possible if the SCTP stack is
>    implemented as part of an application.

Remove the suggestion that the IANA port be used as the source port.

> Changing the beginning of subsection 4.3 (Encapsulation Procedure):
> 
>    When inserting the UDP header, the source port is local UDP
>    encapsulation port number of the SCTP stack, the destination port is
>    the remote UDP encapsualtion port number stored for the destination
>    address the packet is sent to (see Section 4.1).
> 
> Does this address your issue completely? I just want to mention that it
> might be good to use the IANA assigned number when possible.

But it is equally good to let the source UDP port be chosen by 
the operating system -- same as with nearly everything else.

-d

> Best regards
> Michael
> >
> > -d
> >
> >
> >> Best regards
> >> Michael
> >>>
> >>> -d
> >>>
> >>>
> >>>> Best regards
> >>>> Michael
> >>>>>
> >>>>> -d
> >>>>>
> >>>>>
> >>>>>
> >>>
> >>>
> >
> >


From tuexen@fh-muenster.de  Tue Nov  1 15:25:27 2011
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C95CA11E80AB for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 15:25:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F14IuNtUkvAT for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 15:25:27 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 5137711E80F7 for <tsvwg@ietf.org>; Tue,  1 Nov 2011 15:25:26 -0700 (PDT)
Received: from [192.168.1.124] (p508FAFBE.dip.t-dialin.net [80.143.175.190]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 26DA41C0C0BD9; Tue,  1 Nov 2011 23:25:25 +0100 (CET)
Subject: Re: SCTP-over-UDP and port 9899
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <1df701cc98e1$25519970$6ff4cc50$@com>
Date: Tue, 1 Nov 2011 23:25:24 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <6D907808-5797-47D7-AA92-F5B0C1EADB71@fh-muenster.de>
References: <193601cc9809$2ffa6b50$8fef41f0$@com> <C2980D8C-6CBF-4077-985C-70F4BE09D7C0@fh-muenster.de> <1bbd01cc98ad$9099bb60$b1cd3220$@com> <FBB2B325-47B2-4EAF-AE52-5ED2233C1C57@fh-muenster.de> <1c0401cc98b9$e0bdab40$a23901c0$@com> <1E7B798E-8AE2-4E2E-829E-1E7075D2C74E@fh-muenster.de> <1df701cc98e1$25519970$6ff4cc50$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: tsvwg@ietf.org, randall@lakerest.net
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 22:25:27 -0000

On Nov 1, 2011, at 10:56 PM, Dan Wing wrote:

>> -----Original Message-----
>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>> Sent: Tuesday, November 01, 2011 12:59 PM
>> To: Dan Wing
>> Cc: tsvwg@ietf.org; randall@lakerest.net
>> Subject: Re: SCTP-over-UDP and port 9899
>> 
>> On Nov 1, 2011, at 6:15 PM, Dan Wing wrote:
>> 
>>>> -----Original Message-----
>>>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>>>> Sent: Tuesday, November 01, 2011 9:50 AM
>>>> To: Dan Wing
>>>> Cc: tsvwg@ietf.org; randall@lakerest.net
>>>> Subject: Re: SCTP-over-UDP and port 9899
>>>> 
>>>> 
>>>> On Nov 1, 2011, at 4:47 PM, Dan Wing wrote:
>>>> 
>>>>>> -----Original Message-----
>>>>>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On
>>>> Behalf
>>>>>> Of Michael Tuexen
>>>>>> Sent: Monday, October 31, 2011 2:27 PM
>>>>>> To: Dan Wing
>>>>>> Cc: tsvwg@ietf.org; randall@lakerest.net
>>>>>> Subject: Re: SCTP-over-UDP and port 9899
>>>>>> 
>>>>>> On Oct 31, 2011, at 9:10 PM, Dan Wing wrote:
>>>>>> 
>>>>>>> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-udp-encaps-01
>> and
>>>>>> its
>>>>>>> predecessor both say:
>>>>>>> 
>>>>>>> "When inserting the UDP header, the source port is 9899, the
>>>>>>> destination port is the one stored for the destination address
>> the
>>>>>>> packet is sent to or 9899 if no destination address is stored."
>>>>>>> 
>>>>>>> Why is it important to use a specific source port?  Does that not
>>>>>>> cause difficulties if there are two (or more) instances of SCTP-
>>>>>>> over-UDP applications running on the same host?  Does that not
>>>>>>> cause difficulties, in implementation assumptions, if there are
>>>>>>> two hosts behind the same NAPT and only one can get UDP/9899
>>>>>>> forwarded to them?
>>>>>> Hi Dan,
>>>>>> 
>>>>>> for sending out the initial packet of an association, the source
>>>>>> port is not important.
>>>>> 
>>>>> Then can you strike "the source port is 9899" from the document?
>>>>> 
>>>>>> The peer will send back the response to any
>>>>>> port. But the destination port of the initial packet is important.
>>>>>> It must be the same port the peer is accepting UDP packets. It
>>>>>> can be any port, but then it needs to be negotiated somehow.
>>>>> 
>>>>> Sure, of course.
>>>>> 
>>>>> The 32-bit or 128-bit IP address is already negotiated.
>>>>> Negotiating another 16 bits is not onerous.  It isn't easy
>>>>> with DNS (because neither SRV records nor the ability to
>>>>> update them is ubiquitous), but lots of protocols already
>>>>> communicate IP address and port -- BitTorrent, Skype, SIP,
>>>>> many others.
>>>>> 
>>>>>> Since there is one registered port for SCTP/UDP, I used that.
>>>>>> But you can use a different one, if negotiated. If you want to
>>>>>> run two hosts as servers behind a NAT, you need different UDP
>>>>>> ports. If they are clients, you don't.
>>>>>> 
>>>>>>> In short, what is the benefit of using 9899 as the source port?
>>>>>> It is more a default, if nothing else is known. In the socketAPI
>>>>>> section the remote port is configurable. The local port (at
>>>>>> least in the FreeBSD/MacOS X implementation) is a parameter
>>>>>> controller by a sysctl variable. So (currently) a single
>>>>>> host uses a single port number for all associations.
>>>>>> 
>>>>>> Does this makes things clearer?
>>>>> 
>>>>> Not especially, no.
>>>>> 
>>>>> Let's look at, for example, SSH -- the SSH port is 22.   But
>>>>> there is no need for the *source port* to be 22.  I'm trying
>>>>> to understand why there is text mentioning anything about
>>>>> the source port in draft-ietf-tsvwg-sctp-udp-encaps.
>>>> OK, this is a good example. I want 9899 for SCTP/UDP be similar
>>>> to 22 for SSH. But there is a difference. I want to support the
>>>> case where I have one SCTP stack on a host and this stack uses
>>>> a single UDP port number shared between all associations, no
>>>> matter which side initiated them.
>>> 
>>> But a major use-case for SCTP-over-UDP is when the application
>>> itself has its own SCTP stack.  This is even mentioned in
>>> your I-D.  For that use-case, the two applications cannot
>>> achieve your desired goal.
>> I agree.
>>> 
>>>> I might not have made that
>>>> clear. So it different from SSH where the server binds to a
>>>> well known port (or not if otherwise negotiated), the client
>>>> uses an arbitrary one. Do you have a suggestion for the wording?
>>> 
>>> Yes, remove the wording saying 9899 is the source port.
>>> 
>>> Suggest:
>>> 
>>> It can be advantageous for all SCTP-over-UDP traffic originated by a
>>> host to use the same source port (e.g., this reduces the number of
>>> mappings in firewalls and NATs, among other things).  It is possible
>>> to use the same UDP source port by using the SCTP header to
>>> demultiplex the incoming traffic (rather than demultiplexing solely
>>> on UDP port number). When SCTP-over-UDP is implemented by a shared
>>> library (e.g., a framework or by the OS itself), this optimization
>>> is possible.  When SCTP-over-UDP is implemented by an application,
>>> this optimization is usually not possible.
>> OK. Thank you very much. What about the following changes:
>> 
>> Adding to the subsection 4.1 (Architectural Considerations):
>> 
>>   Each SCTP stack uses a single local UDP encapsulation port number as
>>   the source port for all of its outgoing SCTP packets and as the
>>   destination port for all its incoming SCTP packets.  The IANA
> ..........................................................^^^^^^^^
>>   assinged value of 9989 MAY be used as this port number.  If there is
> .....^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>   only a single SCTP implementation on a host (for example, a kernel
>>   implementation being part of the operating system), using a single
>>   UDP encapsulation port number per host can be advantageous (e.g.,
>>   this reduces the number of mappings in firewalls and NATs, among
>>   other things).  However, this is not possible if the SCTP stack is
>>   implemented as part of an application.
> 
> Remove the suggestion that the IANA port be used as the source port.
> 
>> Changing the beginning of subsection 4.3 (Encapsulation Procedure):
>> 
>>   When inserting the UDP header, the source port is local UDP
>>   encapsulation port number of the SCTP stack, the destination port is
>>   the remote UDP encapsualtion port number stored for the destination
>>   address the packet is sent to (see Section 4.1).
>> 
>> Does this address your issue completely? I just want to mention that it
>> might be good to use the IANA assigned number when possible.
> 
> But it is equally good to let the source UDP port be chosen by 
> the operating system -- same as with nearly everything else.
I do understand your point. However:

RFC 4253 (SSH) states:

When used over TCP/IP, the server normally listens for connections on
port 22.

RFC 2616 (HTTP) states:
HTTP communication usually takes place over TCP/IP connections. The
default port is TCP 80 [19], but other ports can be used.

Please note that the local UDP encapsulation port is the destination
port of the received packets. Similar to 80 for HTTP and 22 for SSH.
Since we have an IANA assigned port, I would like to encourage
people to use it when possible. I guess this is OK, or isn't it?

That is why I used a MAY. But I'm open to use any other formulation.
Do you have a suggestion?


Best regards
Michael
> 
> -d
> 
>> Best regards
>> Michael
>>> 
>>> -d
>>> 
>>> 
>>>> Best regards
>>>> Michael
>>>>> 
>>>>> -d
>>>>> 
>>>>> 
>>>>>> Best regards
>>>>>> Michael
>>>>>>> 
>>>>>>> -d
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>> 
>>>>> 
>>> 
>>> 
> 
> 


From dwing@cisco.com  Tue Nov  1 15:46:19 2011
Return-Path: <dwing@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 291F111E80BE for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 15:46:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hHpZU2fzeXEa for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 15:46:18 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 476A711E814A for <tsvwg@ietf.org>; Tue,  1 Nov 2011 15:46:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=8721; q=dns/txt; s=iport; t=1320187578; x=1321397178; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=EvefdsFIyjR3lk4To74/4xptG9U5fTE7BAOxPG0NL4U=; b=HZ4aG66mChxA5ALmK7tCuvhpXoKD+QBi2DEBFhsaGTtQGBdo03TGdu+7 /bETrTPwES4dpuwEjHDzC7JmVJeGhQZE+QdEcbB4Hp+W4feDecPVokRwZ X2253hBvx+cU54rZ4+7WHFaRcX3rmmBAEMC03osb15DYlCh407HvUjlYA o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AskAAE12sE6rRDoG/2dsb2JhbABDmWyBa4xHgSuBBYFyAQEBAwEICgEXED8FBwEDAgkPAgQBAQEnBxkjCgkIAQEEEwsXh2AIlyoBniaJBwSIBp4I
X-IronPort-AV: E=Sophos;i="4.69,440,1315180800"; d="scan'208";a="11760181"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 01 Nov 2011 22:46:18 +0000
Received: from dwingWS (dhcp-171-70-249-135.cisco.com [171.70.249.135]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pA1MkHen023844; Tue, 1 Nov 2011 22:46:17 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Michael Tuexen'" <tuexen@fh-muenster.de>
References: <193601cc9809$2ffa6b50$8fef41f0$@com>	<C2980D8C-6CBF-4077-985C-70F4BE09D7C0@fh-muenster.de>	<1bbd01cc98ad$9099bb60$b1cd3220$@com>	<FBB2B325-47B2-4EAF-AE52-5ED2233C1C57@fh-muenster.de>	<1c0401cc98b9$e0bdab40$a23901c0$@com>	<1E7B798E-8AE2-4E2E-829E-1E7075D2C74E@fh-muenster.de>	<1df701cc98e1$25519970$6ff4cc50$@com> <6D907808-5797-47D7-AA92-F5B0C1EADB71@fh-muenster.de>
In-Reply-To: <6D907808-5797-47D7-AA92-F5B0C1EADB71@fh-muenster.de>
Subject: RE: SCTP-over-UDP and port 9899
Date: Tue, 1 Nov 2011 15:46:17 -0700
Message-ID: <1e8301cc98e8$11713c10$3453b430$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcyY5SrOB/gKV9WJSyywLXWD/EWmkgAAsF8Q
Content-Language: en-us
Cc: tsvwg@ietf.org, randall@lakerest.net
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 22:46:19 -0000

> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf
> Of Michael Tuexen
> Sent: Tuesday, November 01, 2011 3:25 PM
> To: Dan Wing
> Cc: tsvwg@ietf.org; randall@lakerest.net
> Subject: Re: SCTP-over-UDP and port 9899
> 
> On Nov 1, 2011, at 10:56 PM, Dan Wing wrote:
> 
> >> -----Original Message-----
> >> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> >> Sent: Tuesday, November 01, 2011 12:59 PM
> >> To: Dan Wing
> >> Cc: tsvwg@ietf.org; randall@lakerest.net
> >> Subject: Re: SCTP-over-UDP and port 9899
> >>
> >> On Nov 1, 2011, at 6:15 PM, Dan Wing wrote:
> >>
> >>>> -----Original Message-----
> >>>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> >>>> Sent: Tuesday, November 01, 2011 9:50 AM
> >>>> To: Dan Wing
> >>>> Cc: tsvwg@ietf.org; randall@lakerest.net
> >>>> Subject: Re: SCTP-over-UDP and port 9899
> >>>>
> >>>>
> >>>> On Nov 1, 2011, at 4:47 PM, Dan Wing wrote:
> >>>>
> >>>>>> -----Original Message-----
> >>>>>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On
> >>>> Behalf
> >>>>>> Of Michael Tuexen
> >>>>>> Sent: Monday, October 31, 2011 2:27 PM
> >>>>>> To: Dan Wing
> >>>>>> Cc: tsvwg@ietf.org; randall@lakerest.net
> >>>>>> Subject: Re: SCTP-over-UDP and port 9899
> >>>>>>
> >>>>>> On Oct 31, 2011, at 9:10 PM, Dan Wing wrote:
> >>>>>>
> >>>>>>> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-udp-encaps-01
> >> and
> >>>>>> its
> >>>>>>> predecessor both say:
> >>>>>>>
> >>>>>>> "When inserting the UDP header, the source port is 9899, the
> >>>>>>> destination port is the one stored for the destination address
> >> the
> >>>>>>> packet is sent to or 9899 if no destination address is stored."
> >>>>>>>
> >>>>>>> Why is it important to use a specific source port?  Does that
> not
> >>>>>>> cause difficulties if there are two (or more) instances of
> SCTP-
> >>>>>>> over-UDP applications running on the same host?  Does that not
> >>>>>>> cause difficulties, in implementation assumptions, if there are
> >>>>>>> two hosts behind the same NAPT and only one can get UDP/9899
> >>>>>>> forwarded to them?
> >>>>>> Hi Dan,
> >>>>>>
> >>>>>> for sending out the initial packet of an association, the source
> >>>>>> port is not important.
> >>>>>
> >>>>> Then can you strike "the source port is 9899" from the document?
> >>>>>
> >>>>>> The peer will send back the response to any
> >>>>>> port. But the destination port of the initial packet is
> important.
> >>>>>> It must be the same port the peer is accepting UDP packets. It
> >>>>>> can be any port, but then it needs to be negotiated somehow.
> >>>>>
> >>>>> Sure, of course.
> >>>>>
> >>>>> The 32-bit or 128-bit IP address is already negotiated.
> >>>>> Negotiating another 16 bits is not onerous.  It isn't easy
> >>>>> with DNS (because neither SRV records nor the ability to
> >>>>> update them is ubiquitous), but lots of protocols already
> >>>>> communicate IP address and port -- BitTorrent, Skype, SIP,
> >>>>> many others.
> >>>>>
> >>>>>> Since there is one registered port for SCTP/UDP, I used that.
> >>>>>> But you can use a different one, if negotiated. If you want to
> >>>>>> run two hosts as servers behind a NAT, you need different UDP
> >>>>>> ports. If they are clients, you don't.
> >>>>>>
> >>>>>>> In short, what is the benefit of using 9899 as the source port?
> >>>>>> It is more a default, if nothing else is known. In the socketAPI
> >>>>>> section the remote port is configurable. The local port (at
> >>>>>> least in the FreeBSD/MacOS X implementation) is a parameter
> >>>>>> controller by a sysctl variable. So (currently) a single
> >>>>>> host uses a single port number for all associations.
> >>>>>>
> >>>>>> Does this makes things clearer?
> >>>>>
> >>>>> Not especially, no.
> >>>>>
> >>>>> Let's look at, for example, SSH -- the SSH port is 22.   But
> >>>>> there is no need for the *source port* to be 22.  I'm trying
> >>>>> to understand why there is text mentioning anything about
> >>>>> the source port in draft-ietf-tsvwg-sctp-udp-encaps.
> >>>> OK, this is a good example. I want 9899 for SCTP/UDP be similar
> >>>> to 22 for SSH. But there is a difference. I want to support the
> >>>> case where I have one SCTP stack on a host and this stack uses
> >>>> a single UDP port number shared between all associations, no
> >>>> matter which side initiated them.
> >>>
> >>> But a major use-case for SCTP-over-UDP is when the application
> >>> itself has its own SCTP stack.  This is even mentioned in
> >>> your I-D.  For that use-case, the two applications cannot
> >>> achieve your desired goal.
> >> I agree.
> >>>
> >>>> I might not have made that
> >>>> clear. So it different from SSH where the server binds to a
> >>>> well known port (or not if otherwise negotiated), the client
> >>>> uses an arbitrary one. Do you have a suggestion for the wording?
> >>>
> >>> Yes, remove the wording saying 9899 is the source port.
> >>>
> >>> Suggest:
> >>>
> >>> It can be advantageous for all SCTP-over-UDP traffic originated by
> a
> >>> host to use the same source port (e.g., this reduces the number of
> >>> mappings in firewalls and NATs, among other things).  It is
> possible
> >>> to use the same UDP source port by using the SCTP header to
> >>> demultiplex the incoming traffic (rather than demultiplexing solely
> >>> on UDP port number). When SCTP-over-UDP is implemented by a shared
> >>> library (e.g., a framework or by the OS itself), this optimization
> >>> is possible.  When SCTP-over-UDP is implemented by an application,
> >>> this optimization is usually not possible.
> >> OK. Thank you very much. What about the following changes:
> >>
> >> Adding to the subsection 4.1 (Architectural Considerations):
> >>
> >>   Each SCTP stack uses a single local UDP encapsulation port number
> as
> >>   the source port for all of its outgoing SCTP packets and as the
> >>   destination port for all its incoming SCTP packets.  The IANA
> > ..........................................................^^^^^^^^
> >>   assinged value of 9989 MAY be used as this port number.  If there
> is
> > .....^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >>   only a single SCTP implementation on a host (for example, a kernel
> >>   implementation being part of the operating system), using a single
> >>   UDP encapsulation port number per host can be advantageous (e.g.,
> >>   this reduces the number of mappings in firewalls and NATs, among
> >>   other things).  However, this is not possible if the SCTP stack is
> >>   implemented as part of an application.
> >
> > Remove the suggestion that the IANA port be used as the source port.
> >
> >> Changing the beginning of subsection 4.3 (Encapsulation Procedure):
> >>
> >>   When inserting the UDP header, the source port is local UDP
> >>   encapsulation port number of the SCTP stack, the destination port
> is
> >>   the remote UDP encapsualtion port number stored for the
> destination
> >>   address the packet is sent to (see Section 4.1).
> >>
> >> Does this address your issue completely? I just want to mention that
> it
> >> might be good to use the IANA assigned number when possible.
> >
> > But it is equally good to let the source UDP port be chosen by
> > the operating system -- same as with nearly everything else.
> I do understand your point. However:
> 
> RFC 4253 (SSH) states:
> 
> When used over TCP/IP, the server normally listens for connections on
> port 22.
> 
> RFC 2616 (HTTP) states:
> HTTP communication usually takes place over TCP/IP connections. The
> default port is TCP 80 [19], but other ports can be used.
> 
> Please note that the local UDP encapsulation port is the destination
> port of the received packets. Similar to 80 for HTTP and 22 for SSH.
> Since we have an IANA assigned port, I would like to encourage
> people to use it when possible. I guess this is OK, or isn't it?

For the server, yes, that's okay.  That is what IANA-registered
default ports are all about.

> That is why I used a MAY. But I'm open to use any other formulation.
> Do you have a suggestion?

Yes -- be silent about the source port.  Say nothing in the
document about the source port.

-d


> 
> Best regards
> Michael
> >
> > -d
> >
> >> Best regards
> >> Michael
> >>>
> >>> -d
> >>>
> >>>
> >>>> Best regards
> >>>> Michael
> >>>>>
> >>>>> -d
> >>>>>
> >>>>>
> >>>>>> Best regards
> >>>>>> Michael
> >>>>>>>
> >>>>>>> -d
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>>>
> >>>
> >>>
> >
> >


From tuexen@fh-muenster.de  Tue Nov  1 16:17:26 2011
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8810E11E80E2 for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 16:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nlUfBTe15-b9 for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 16:17:25 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 00A4911E80DC for <tsvwg@ietf.org>; Tue,  1 Nov 2011 16:17:23 -0700 (PDT)
Received: from [192.168.1.124] (p508FAFBE.dip.t-dialin.net [80.143.175.190]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 95AA81C0B461B; Wed,  2 Nov 2011 00:17:22 +0100 (CET)
Subject: Re: SCTP-over-UDP and port 9899
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <1e8301cc98e8$11713c10$3453b430$@com>
Date: Wed, 2 Nov 2011 00:17:21 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <4EC711E2-82E4-4BE1-806F-8C439B496FF8@fh-muenster.de>
References: <193601cc9809$2ffa6b50$8fef41f0$@com>	<C2980D8C-6CBF-4077-985C-70F4BE09D7C0@fh-muenster.de>	<1bbd01cc98ad$9099bb60$b1cd3220$@com>	<FBB2B325-47B2-4EAF-AE52-5ED2233C1C57@fh-muenster.de>	<1c0401cc98b9$e0bdab40$a23901c0$@com>	<1E7B798E-8AE2-4E2E-829E-1E7075D2C74E@fh-muenster.de>	<1df701cc98e1$25519970$6ff4cc50$@com> <6D907808-5797-47D7-AA92-F5B0C1EADB71@fh-muenster.de> <1e8301cc98e8$11713c10$3453b430$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: tsvwg@ietf.org, randall@lakerest.net
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Nov 2011 23:17:26 -0000

On Nov 1, 2011, at 11:46 PM, Dan Wing wrote:

>> -----Original Message-----
>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf
>> Of Michael Tuexen
>> Sent: Tuesday, November 01, 2011 3:25 PM
>> To: Dan Wing
>> Cc: tsvwg@ietf.org; randall@lakerest.net
>> Subject: Re: SCTP-over-UDP and port 9899
>> 
>> On Nov 1, 2011, at 10:56 PM, Dan Wing wrote:
>> 
>>>> -----Original Message-----
>>>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>>>> Sent: Tuesday, November 01, 2011 12:59 PM
>>>> To: Dan Wing
>>>> Cc: tsvwg@ietf.org; randall@lakerest.net
>>>> Subject: Re: SCTP-over-UDP and port 9899
>>>> 
>>>> On Nov 1, 2011, at 6:15 PM, Dan Wing wrote:
>>>> 
>>>>>> -----Original Message-----
>>>>>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>>>>>> Sent: Tuesday, November 01, 2011 9:50 AM
>>>>>> To: Dan Wing
>>>>>> Cc: tsvwg@ietf.org; randall@lakerest.net
>>>>>> Subject: Re: SCTP-over-UDP and port 9899
>>>>>> 
>>>>>> 
>>>>>> On Nov 1, 2011, at 4:47 PM, Dan Wing wrote:
>>>>>> 
>>>>>>>> -----Original Message-----
>>>>>>>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On
>>>>>> Behalf
>>>>>>>> Of Michael Tuexen
>>>>>>>> Sent: Monday, October 31, 2011 2:27 PM
>>>>>>>> To: Dan Wing
>>>>>>>> Cc: tsvwg@ietf.org; randall@lakerest.net
>>>>>>>> Subject: Re: SCTP-over-UDP and port 9899
>>>>>>>> 
>>>>>>>> On Oct 31, 2011, at 9:10 PM, Dan Wing wrote:
>>>>>>>> 
>>>>>>>>> http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-udp-encaps-01
>>>> and
>>>>>>>> its
>>>>>>>>> predecessor both say:
>>>>>>>>> 
>>>>>>>>> "When inserting the UDP header, the source port is 9899, the
>>>>>>>>> destination port is the one stored for the destination address
>>>> the
>>>>>>>>> packet is sent to or 9899 if no destination address is stored."
>>>>>>>>> 
>>>>>>>>> Why is it important to use a specific source port?  Does that
>> not
>>>>>>>>> cause difficulties if there are two (or more) instances of
>> SCTP-
>>>>>>>>> over-UDP applications running on the same host?  Does that not
>>>>>>>>> cause difficulties, in implementation assumptions, if there are
>>>>>>>>> two hosts behind the same NAPT and only one can get UDP/9899
>>>>>>>>> forwarded to them?
>>>>>>>> Hi Dan,
>>>>>>>> 
>>>>>>>> for sending out the initial packet of an association, the source
>>>>>>>> port is not important.
>>>>>>> 
>>>>>>> Then can you strike "the source port is 9899" from the document?
>>>>>>> 
>>>>>>>> The peer will send back the response to any
>>>>>>>> port. But the destination port of the initial packet is
>> important.
>>>>>>>> It must be the same port the peer is accepting UDP packets. It
>>>>>>>> can be any port, but then it needs to be negotiated somehow.
>>>>>>> 
>>>>>>> Sure, of course.
>>>>>>> 
>>>>>>> The 32-bit or 128-bit IP address is already negotiated.
>>>>>>> Negotiating another 16 bits is not onerous.  It isn't easy
>>>>>>> with DNS (because neither SRV records nor the ability to
>>>>>>> update them is ubiquitous), but lots of protocols already
>>>>>>> communicate IP address and port -- BitTorrent, Skype, SIP,
>>>>>>> many others.
>>>>>>> 
>>>>>>>> Since there is one registered port for SCTP/UDP, I used that.
>>>>>>>> But you can use a different one, if negotiated. If you want to
>>>>>>>> run two hosts as servers behind a NAT, you need different UDP
>>>>>>>> ports. If they are clients, you don't.
>>>>>>>> 
>>>>>>>>> In short, what is the benefit of using 9899 as the source port?
>>>>>>>> It is more a default, if nothing else is known. In the socketAPI
>>>>>>>> section the remote port is configurable. The local port (at
>>>>>>>> least in the FreeBSD/MacOS X implementation) is a parameter
>>>>>>>> controller by a sysctl variable. So (currently) a single
>>>>>>>> host uses a single port number for all associations.
>>>>>>>> 
>>>>>>>> Does this makes things clearer?
>>>>>>> 
>>>>>>> Not especially, no.
>>>>>>> 
>>>>>>> Let's look at, for example, SSH -- the SSH port is 22.   But
>>>>>>> there is no need for the *source port* to be 22.  I'm trying
>>>>>>> to understand why there is text mentioning anything about
>>>>>>> the source port in draft-ietf-tsvwg-sctp-udp-encaps.
>>>>>> OK, this is a good example. I want 9899 for SCTP/UDP be similar
>>>>>> to 22 for SSH. But there is a difference. I want to support the
>>>>>> case where I have one SCTP stack on a host and this stack uses
>>>>>> a single UDP port number shared between all associations, no
>>>>>> matter which side initiated them.
>>>>> 
>>>>> But a major use-case for SCTP-over-UDP is when the application
>>>>> itself has its own SCTP stack.  This is even mentioned in
>>>>> your I-D.  For that use-case, the two applications cannot
>>>>> achieve your desired goal.
>>>> I agree.
>>>>> 
>>>>>> I might not have made that
>>>>>> clear. So it different from SSH where the server binds to a
>>>>>> well known port (or not if otherwise negotiated), the client
>>>>>> uses an arbitrary one. Do you have a suggestion for the wording?
>>>>> 
>>>>> Yes, remove the wording saying 9899 is the source port.
>>>>> 
>>>>> Suggest:
>>>>> 
>>>>> It can be advantageous for all SCTP-over-UDP traffic originated by
>> a
>>>>> host to use the same source port (e.g., this reduces the number of
>>>>> mappings in firewalls and NATs, among other things).  It is
>> possible
>>>>> to use the same UDP source port by using the SCTP header to
>>>>> demultiplex the incoming traffic (rather than demultiplexing solely
>>>>> on UDP port number). When SCTP-over-UDP is implemented by a shared
>>>>> library (e.g., a framework or by the OS itself), this optimization
>>>>> is possible.  When SCTP-over-UDP is implemented by an application,
>>>>> this optimization is usually not possible.
>>>> OK. Thank you very much. What about the following changes:
>>>> 
>>>> Adding to the subsection 4.1 (Architectural Considerations):
>>>> 
>>>>  Each SCTP stack uses a single local UDP encapsulation port number
>> as
>>>>  the source port for all of its outgoing SCTP packets and as the
>>>>  destination port for all its incoming SCTP packets.  The IANA
>>> ..........................................................^^^^^^^^
>>>>  assinged value of 9989 MAY be used as this port number.  If there
>> is
>>> .....^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>>  only a single SCTP implementation on a host (for example, a kernel
>>>>  implementation being part of the operating system), using a single
>>>>  UDP encapsulation port number per host can be advantageous (e.g.,
>>>>  this reduces the number of mappings in firewalls and NATs, among
>>>>  other things).  However, this is not possible if the SCTP stack is
>>>>  implemented as part of an application.
>>> 
>>> Remove the suggestion that the IANA port be used as the source port.
>>> 
>>>> Changing the beginning of subsection 4.3 (Encapsulation Procedure):
>>>> 
>>>>  When inserting the UDP header, the source port is local UDP
>>>>  encapsulation port number of the SCTP stack, the destination port
>> is
>>>>  the remote UDP encapsualtion port number stored for the
>> destination
>>>>  address the packet is sent to (see Section 4.1).
>>>> 
>>>> Does this address your issue completely? I just want to mention that
>> it
>>>> might be good to use the IANA assigned number when possible.
>>> 
>>> But it is equally good to let the source UDP port be chosen by
>>> the operating system -- same as with nearly everything else.
>> I do understand your point. However:
>> 
>> RFC 4253 (SSH) states:
>> 
>> When used over TCP/IP, the server normally listens for connections on
>> port 22.
>> 
>> RFC 2616 (HTTP) states:
>> HTTP communication usually takes place over TCP/IP connections. The
>> default port is TCP 80 [19], but other ports can be used.
>> 
>> Please note that the local UDP encapsulation port is the destination
>> port of the received packets. Similar to 80 for HTTP and 22 for SSH.
>> Since we have an IANA assigned port, I would like to encourage
>> people to use it when possible. I guess this is OK, or isn't it?
> 
> For the server, yes, that's okay.  That is what IANA-registered
> default ports are all about.
But the SCTP stack is neither a client nor a server...
> 
>> That is why I used a MAY. But I'm open to use any other formulation.
>> Do you have a suggestion?
> 
> Yes -- be silent about the source port.  Say nothing in the
> document about the source port.
I just talk about the local UDP encapsulation port...
However, it is the destination port of incoming packets and
the source port of outgoing packets (as every local port
number is).

Would it be acceptable for you if I replace

Each SCTP stack uses a single local UDP encapsulation port number
as the source port for all of its outgoing SCTP packets
and as the destination port for all its incoming SCTP packets.

by

Each SCTP stack uses a single local UDP encapsulation port number.

However, later on I'm saying that the local UDP port is used
as the source port for outgoing packets. I think I have to say
that, since I need to say what the source and destination port
of the inserted UDP are.

Best regards
Michael
> 
> -d
> 
> 
>> 
>> Best regards
>> Michael
>>> 
>>> -d
>>> 
>>>> Best regards
>>>> Michael
>>>>> 
>>>>> -d
>>>>> 
>>>>> 
>>>>>> Best regards
>>>>>> Michael
>>>>>>> 
>>>>>>> -d
>>>>>>> 
>>>>>>> 
>>>>>>>> Best regards
>>>>>>>> Michael
>>>>>>>>> 
>>>>>>>>> -d
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>> 
>>>>> 
>>> 
>>> 
> 
> 


From dwing@cisco.com  Tue Nov  1 19:27:50 2011
Return-Path: <dwing@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E01DA1F0C54 for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 19:27:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.597
X-Spam-Level: 
X-Spam-Status: No, score=-105.597 tagged_above=-999 required=5 tests=[AWL=1.002, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cjdmf0w06+7D for <tsvwg@ietfa.amsl.com>; Tue,  1 Nov 2011 19:27:50 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 20F4A1F0C41 for <tsvwg@ietf.org>; Tue,  1 Nov 2011 19:27:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1896; q=dns/txt; s=iport; t=1320200870; x=1321410470; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=EgTw+h3da6+ubIIteEQ0IYlWa+7aRUlPfbi5TG5fgHk=; b=MRPLHlSuDSZr4njpWDor9Kuo3JYh83YyEiWJSGdKVm665wcw1VKy/scA VhCHrVychzBen3s2SvQK4XATcIcKdBWox0grhycL5CcO1HPEuvxg/ESlB PDfbs2n+AFH7uDAKYLWB/VqOlmGuIHKK+e/VsUV9S21OlERe2oRPVNTfp 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAOypsE6rRDoI/2dsb2JhbABDm1iNeYEFgXIBAQEDAQgKARcQPwUIAwIJDzcZIxsBAQQeF4dglw0BniaJCASIBp4M
X-IronPort-AV: E=Sophos;i="4.69,441,1315180800"; d="scan'208";a="11795039"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-2.cisco.com with ESMTP; 02 Nov 2011 02:27:39 +0000
Received: from dwingWS ([10.32.240.194]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pA22Rdtr007151; Wed, 2 Nov 2011 02:27:39 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Michael Tuexen'" <tuexen@fh-muenster.de>
References: <193601cc9809$2ffa6b50$8fef41f0$@com>	<C2980D8C-6CBF-4077-985C-70F4BE09D7C0@fh-muenster.de>	<1bbd01cc98ad$9099bb60$b1cd3220$@com>	<FBB2B325-47B2-4EAF-AE52-5ED2233C1C57@fh-muenster.de>	<1c0401cc98b9$e0bdab40$a23901c0$@com>	<1E7B798E-8AE2-4E2E-829E-1E7075D2C74E@fh-muenster.de>	<1df701cc98e1$25519970$6ff4cc50$@com> <6D907808-5797-47D7-AA92-F5B0C1EADB71@fh-muenster.de> <1e8301cc98e8$11713c10$3453b430$@com> <4EC711E2-82E4-4BE1-806F-8C439B496FF8@fh-muenster.de>
In-Reply-To: <4EC711E2-82E4-4BE1-806F-8C439B496FF8@fh-muenster.de>
Subject: RE: SCTP-over-UDP and port 9899
Date: Tue, 1 Nov 2011 19:27:39 -0700
Message-ID: <1f2501cc9906$fe116c70$fa344550$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcyY7Gt91y38WEqVQeuOHGecLlzklwAGkI9g
Content-Language: en-us
Cc: tsvwg@ietf.org, randall@lakerest.net
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Nov 2011 02:27:51 -0000

> > For the server, yes, that's okay.  That is what IANA-registered
> > default ports are all about.
> But the SCTP stack is neither a client nor a server...

"Bullpucky".  Next you're going to say that "peer to peer" 
doesn't have a client and a server.

> >> That is why I used a MAY. But I'm open to use any other formulation.
> >> Do you have a suggestion?
> >
> > Yes -- be silent about the source port.  Say nothing in the
> > document about the source port.
> I just talk about the local UDP encapsulation port...
> However, it is the destination port of incoming packets and
> the source port of outgoing packets (as every local port
> number is).
> 
> Would it be acceptable for you if I replace
> 
> Each SCTP stack uses a single local UDP encapsulation port number
> as the source port for all of its outgoing SCTP packets
> and as the destination port for all its incoming SCTP packets.
> 
> by
> 
> Each SCTP stack uses a single local UDP encapsulation port number.
> 
> However, later on I'm saying that the local UDP port is used
> as the source port for outgoing packets. I think I have to say
> that, since I need to say what the source and destination port
> of the inserted UDP are.

Do you understand why I am concerned with specifying the 
source UDP port number?  It gets re-written by NATs, and
the primary reason for this draft is to allow SCTP to work
when behind a NAT.

-d


> Best regards
> Michael
> >
> > -d
> >
> >
> >>
> >> Best regards
> >> Michael
> >>>
> >>> -d
> >>>
> >>>> Best regards
> >>>> Michael
> >>>>>
> >>>>> -d
> >>>>>
> >>>>>
> >>>>>> Best regards
> >>>>>> Michael
> >>>>>>>
> >>>>>>> -d
> >>>>>>>
> >>>>>>>
> >>>>>>>> Best regards
> >>>>>>>> Michael
> >>>>>>>>>
> >>>>>>>>> -d
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>>>
> >>>
> >>>
> >
> >


From tuexen@fh-muenster.de  Wed Nov  2 04:35:06 2011
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 538161F0CA2 for <tsvwg@ietfa.amsl.com>; Wed,  2 Nov 2011 04:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7CLlDp5n+sd5 for <tsvwg@ietfa.amsl.com>; Wed,  2 Nov 2011 04:35:05 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 443F81F0C8E for <tsvwg@ietf.org>; Wed,  2 Nov 2011 04:35:05 -0700 (PDT)
Received: from [192.168.1.200] (p508FAFBE.dip.t-dialin.net [80.143.175.190]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id CA40E1C0B4622; Wed,  2 Nov 2011 12:35:02 +0100 (CET)
Subject: Re: SCTP-over-UDP and port 9899
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <1f2501cc9906$fe116c70$fa344550$@com>
Date: Wed, 2 Nov 2011 12:35:01 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <1C060940-B69C-4FE7-8A59-6A86375BF25A@fh-muenster.de>
References: <193601cc9809$2ffa6b50$8fef41f0$@com>	<C2980D8C-6CBF-4077-985C-70F4BE09D7C0@fh-muenster.de>	<1bbd01cc98ad$9099bb60$b1cd3220$@com>	<FBB2B325-47B2-4EAF-AE52-5ED2233C1C57@fh-muenster.de>	<1c0401cc98b9$e0bdab40$a23901c0$@com>	<1E7B798E-8AE2-4E2E-829E-1E7075D2C74E@fh-muenster.de>	<1df701cc98e1$25519970$6ff4cc50$@com> <6D907808-5797-47D7-AA92-F5B0C1EADB71@fh-muenster.de> <1e8301cc98e8$11713c10$3453b430$@com> <4EC711E2-82E4-4BE1-806F-8C439B496FF8@fh-muenster.de> <1f2501cc9906$fe116c70$fa344550$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: tsvwg@ietf.org, randall@lakerest.net
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Nov 2011 11:35:06 -0000

On Nov 2, 2011, at 3:27 AM, Dan Wing wrote:

>>> For the server, yes, that's okay.  That is what IANA-registered
>>> default ports are all about.
>> But the SCTP stack is neither a client nor a server...
> 
> "Bullpucky".  Next you're going to say that "peer to peer" 
> doesn't have a client and a server.
No, I mean it seriously: The local UDP encapsulation port number
is a variable of the stack (for example in the FreeBSD kernel
configurable via a sysctl variable). If you want to use one
number if the application will ever call listen() and a different
one it it calls never listen(), how should the stack decide that?
Same for a userland stack...
> 
>>>> That is why I used a MAY. But I'm open to use any other formulation.
>>>> Do you have a suggestion?
>>> 
>>> Yes -- be silent about the source port.  Say nothing in the
>>> document about the source port.
>> I just talk about the local UDP encapsulation port...
>> However, it is the destination port of incoming packets and
>> the source port of outgoing packets (as every local port
>> number is).
>> 
>> Would it be acceptable for you if I replace
>> 
>> Each SCTP stack uses a single local UDP encapsulation port number
>> as the source port for all of its outgoing SCTP packets
>> and as the destination port for all its incoming SCTP packets.
>> 
>> by
>> 
>> Each SCTP stack uses a single local UDP encapsulation port number.
>> 
>> However, later on I'm saying that the local UDP port is used
>> as the source port for outgoing packets. I think I have to say
>> that, since I need to say what the source and destination port
>> of the inserted UDP are.
> 
> Do you understand why I am concerned with specifying the 
> source UDP port number?  It gets re-written by NATs, and
> the primary reason for this draft is to allow SCTP to work
> when behind a NAT.
I'm not sure why you are concerned.
The ID says: Use 9899 when possible as the local encapsulation
port (I'm using MAY). For outgoing packets this local encapsulation
port number is use as the source port by the sending host.
Of course, it can be rewritten on the path to the receiver and
that is fine. The peer will store the possibly changed source
port as its remote encapsulation port number. This is (at least
I think) described in the ID. This is the processing which
you want to be supported, I think, and of course it is.

Just to be clear: If the sender puts some number in the source
port field, it can not be assumed that the same value is there
when the packet is received. I know that and that is handled.

Put it in other words:
* Each SCTP stack chooses a local encapsulation port. Right?
* Why not choose, when possible, the 9899. Possible or not?
I don't see that anything breaks.

Best regards
Michael
> 
> -d
> 
> 
>> Best regards
>> Michael
>>> 
>>> -d
>>> 
>>> 
>>>> 
>>>> Best regards
>>>> Michael
>>>>> 
>>>>> -d
>>>>> 
>>>>>> Best regards
>>>>>> Michael
>>>>>>> 
>>>>>>> -d
>>>>>>> 
>>>>>>> 
>>>>>>>> Best regards
>>>>>>>> Michael
>>>>>>>>> 
>>>>>>>>> -d
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>>> Best regards
>>>>>>>>>> Michael
>>>>>>>>>>> 
>>>>>>>>>>> -d
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>> 
>>>>> 
>>> 
>>> 
> 
> 


From jmpolk@cisco.com  Wed Nov  2 21:51:54 2011
Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 114FC1F0C7A for <tsvwg@ietfa.amsl.com>; Wed,  2 Nov 2011 21:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.508
X-Spam-Level: 
X-Spam-Status: No, score=-106.508 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MlXjwNgdxsDJ for <tsvwg@ietfa.amsl.com>; Wed,  2 Nov 2011 21:51:53 -0700 (PDT)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 4BBA81F0C74 for <tsvwg@ietf.org>; Wed,  2 Nov 2011 21:51:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=692; q=dns/txt; s=iport; t=1320295913; x=1321505513; h=message-id:date:to:from:subject:mime-version; bh=Uue+W4LwO/Fe6kbcVJ7WyapQz02HQJdQ7FYWkrwCOHc=; b=mmHTVueKiqf/o7QSv3X65VlSdpfe9OG0M1B7fajOfZFgzmMEV4lBL1pi HI3H66sgIWvzGTMVLFFcf0i15OBXrO861+9uAQRQFdH6O2HdaFcv+lVJo ILPmSGqa56NU6ZOAjp7lHH0gwBCFqJqzCe9PqbzjaAR/bksslX8AO0zeB o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAI8dsk6rRDoG/2dsb2JhbABEqXeBBYILAQobAlY6KUQ1nFaBJgGeeIg9YQSICJ4R
X-IronPort-AV: E=Sophos;i="4.69,447,1315180800"; d="scan'208";a="10650140"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 03 Nov 2011 04:51:53 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8713.cisco.com [10.99.80.20]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pA34pqIA005100 for <tsvwg@ietf.org>; Thu, 3 Nov 2011 04:51:52 GMT
Message-Id: <201111030451.pA34pqIA005100@mtv-core-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 02 Nov 2011 23:51:45 -0500
To: tsvwg <tsvwg@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Call for agenda items in TSVWG for Taipei
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2011 04:51:54 -0000

TSVWG

This is a late call for agenda items for Taipei. I think I only have 
two (soft) requests, but could be wrong (RSVP-PCN and ECN for RTP).

We only have a 1 hour slot this meeting, as I know most of the normal 
WG isn't planning on attending, including both chairs and the SCTP 
guys. That covers most of what we're had for presentations the last 
couple of years, so we felt it best not to ask for our regular 150 minute slot.

We're meeting Monday afternoon of the IETF week at 1510 I think, for 
60 minutes.

PLEASE send me (James) your agenda requests ASAP.

Our AD Wes will be chairing this meeting, and we thank him for doing 
it in our absence.

James & Gorry


From gorry@erg.abdn.ac.uk  Fri Nov  4 19:23:04 2011
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A19311E80B5; Fri,  4 Nov 2011 19:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.481
X-Spam-Level: 
X-Spam-Status: No, score=-102.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3D03eHXxFSkC; Fri,  4 Nov 2011 19:23:03 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by ietfa.amsl.com (Postfix) with ESMTP id 4038011E8087; Fri,  4 Nov 2011 19:22:59 -0700 (PDT)
Received: from ra-gorry.erg.abdn.ac.uk (ra-gorry.erg.abdn.ac.uk [139.133.204.42]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id pA52Mo6L002172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 5 Nov 2011 02:22:53 GMT
Message-ID: <4EB49DFB.60309@erg.abdn.ac.uk>
Date: Sat, 05 Nov 2011 02:22:51 +0000
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: TSVWG Status at 5th November 2011
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Nov 2011 02:23:04 -0000

Here is a brief summary of the status of TSVWG drafts as we see it. If 
there are any changes/updates to this list please do let us know.

Gorry & James
TSVWG Chairs

===================================================================


TSVWG Status Nov 2011

---

Recently published I-Ds:

draft-ietf-tsvwg-iana-ports was published as RFC 6335.	
draft-ietf-tsvwg-emergency-rsvp-15 was published as RFC 6401
draft-ietf-tsvwg-rsvp-security-groupkeying was published as RFC 6411.


IDs in RFC Editor Queue:

draft-ietf-tsvwg-sctpsocket
    James is Shepherd.
    RFC-ED.

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

IDs in IESG processing:

draft-ietf-tsvwg-sctp-strrst
      Dependency on this for IPFIX document with RFC-Ed.
      Benoit Claise to review for IPFIX
      New revision (-08) 25 Oct 2010.
          Text on race-condition to be updated before WGLC.
      New text to address this in revision 04/01/2011.
      draft-stewart-tsvwg-reconfuse-sctp to assist in consensus
      IETF-80: need to discus whether one in-band mechanism is viable.
      IETF-81: discussed this and concluded no changes needed.
      WGLC completed.
    James is Shepherd.
    DUE: AD Feedback

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

WG Drafts with Chairs:
     None.

-------------------------------------------------------------------
WG Drafts:

draft-ietf-tsvwg-source-quench
       (Replaced: draft-gont-tsvwg-source-quench-01.txt)
       IETF-79 suggested there was interest in this topic.
       Comments to list in 2010 from: Fred Baker, Antonio DeSimone,
          James Polk, Gorry Fairhurst, Andrew Yourtchenko, and others.
       WG agreed the draft should be a work item.
         More motivation needed to justify the SHOULD cases.
	  New revision to clarify keywords.
	  WGLC started October 18, 2011.
	  WGLC has completed.
	  - Outcome to be confirmed with list:
	  - Update section 6 to say UDP receiver MUST ignore SQ ?
	  - Update section 3 a host SHOULD NOT send ICMP ?
    Gorry is Shepherd.
    DUE: New revision expected (following WGLC)

draft-ietf-tsvwg-byte-pkt-congest
      New editor added Jul 2010.
      New revision 25 Oct 2010.
      WG -01, June 10, 2011
     Previous: Update needed before deciding if ready for WGLC.
     Review sent by Gorry Fairhurst.
      IETF-81: discussed whether this should be BCP.
      Intended status changed to BCP.
	 WG -05, 2011-10-31
    Gorry is Shepherd.
    DUE: Reviewers need to volunteer for LC
    DUE: Please comment on list.
    - Please check suitability for publication.

draft-ietf-tsvwg-natsupp-tsvwg
      (Replaced: draft-stewart-natsupp-tsvw)
      Dependency from BEHAVE WG.
      Adopted as a work item 21 Sept 2010 (Gorry), intended as PS.
         WG -00, 29/11/2010
         WG -01, June 1, 2011
       DUE: Reviews need.

draft-ietf-tsvwg-sctp-udp-encap
      (Replaced: draft-tuexen-sctp-udp-encap)
      Lars sent a note as AD agreeing to progress this work.
	 Work to be coordinated with DCCP work on encaps.
      draft-tuexen-sctp-udp-encaps-06, January 10, 2011
      Adopted as a work item (Gorry).
	 Intended to publish April 2012, as a PS
          WG -00, 2011-07-25
	 WG -01, 2011-10-29
	 - Document suggested complete by authors.
      DUE: Please comment on list.

draft-ietf-tsvwg-intserv-multiple-tspec
       WG interest in this topic recorded at IETF-78.
      Charter update would be needed to progress this work.
      5 Reviews needed to determine energy/technical direction.
      Version -05 (presented in Beijing, IETF-79)
      Version -06 (presented in Prague, IETF-80)
      RSVP directorate was consulted.
         2 reviews from RSVP-DIR received (Bruce Davie, ?).
         2 additional reviews promised (Ken Carlberg, Francois LeF).
         Chairs asked AD for a Charter update (IESG agreed).
      Draft discussed at IETF-80, and request to update charter agreed.
      - AD advised 4 named reviewers will be required.
      Adopted for progression as PS, for May 2012.

draft-ietf-tsvwg-rsvp-pcn
	  (Replaced: draft-karagiannis-pcn-tsvwg-rsvp-pcn)
	   WG interest in this topic recorded at IETF-81.
        -01, 2011-07-11
	   Adopted by TSVWG and added to Charter as PS Sept 2011.
	   WG-00, 2011-10-08
      DUE: Please comment on list.

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

WG action required:

draft-touch-tsvwg-port-use-00
       - Intended to be advice to protocol designers needing a port.
         5 people have looked at this document, Prague IETF-80
      -01 July 2011
      IETF-81 insufficient feedback from WG at this time.
       WG needs to assess if the new draft should be a work item.
     DUE: Chairs need to assess energy for work on this topic.
     DUE: Please comment on list.
	
draft-tuexen-tsvwg-sctp-sack-immediately
        -05, 2011-01-02
        - Aug 2011, discussed on list and issues raised.
	   -08, 2011-10-29
	   - Use cases discussed on list.
     DUE: Chairs need to discuss adoption (Chairs need to do work).

draft-nishida-tsvwg-sctp-failover
       -00 Presented in Prague, IETF-80.
       - understood not to conflict with draft-tuexen-tsvwg-sctp-multipath
     DUE: New revision need.
     DUE: Chairs to start adoption call on list (Chairs need to do work).

draft-tuexen-tsvwg-sctp-multipath
       -00 Presented in Prague, IETF-80.
       - understood not to conflict with draft-nishida-tsvwg-sctp-failover
       -01, 2010-12-27
       Adoption call discussed by WG.
     DUE: Please comment to list.

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

The following have received recent discussion at TSVWG meetings or on
the list. Inclusion in the list below does not indicate support for
these specific drafts and other contributions are also warmly welcomed.

   draft-stewart-tsvwg-sctpecn-00
       Partially replaces (draft-stewart-tsvwg-sctp-nonce)
       IETF-78 suggested there was interest in this topic.
       Please comment to list.
       Revised uploaded with new name.
         - The draft needs to be updated for multihoming (IETF-80)
         - new revision expected April 2011 (IETF-80)
       DUE: WG needs to assess if the new draft should be a work item.

  draft-briscoe-tsvwg-ecn-encap-guidelines
       -00 Presented in Prague, IETF-80.
       - comments at IETF-80 (see minutes)
       WG needs to assess if the new draft should be a work item.
       Please comment on list.
      DUE: Chairs to check liaison status with other SDOs.

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

    draft-polk-tsvwg-rsvp-app-id-vv-profiles
       -01 Presented in Beijing, IETF-79.
       -02, 14-Mar-2011
       Presented IET-80.
       WG needs to assess if the new draft should be a work item.
       Seek to coordinate with mmusic.
       (partner ID draft-ietf-mmusic-traffic-class-for-sdp)
       Please comment on list.
       DUE: Chairs to liaise with MMUSIC WG (Gorry).

   draft-lefaucheur-tsvwg-rsvp-multiple-preemption
       RSVP directorate to be consulted.
	  - Reviewers: Bruce Davie (awaiting other reviews)
       DUE: Please comment to list.

   draft-wing-tsvwg-happy-eyeballs-sctp
       - Appears dead.

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

Related non-WG items:

draft-ietf-behave-sctpnat-03.txt
       BEHAVE WG item linked to SCTP encapsulation work.

draft-ietf-6man-udpzero
       was: draft-fairhurst-tsvwg-6man-udpzero
       Draft was adopted by 6man, please discuss on the 6man list.
       A WGLC of this draft is expected in 6MAN WG.
         related draft: draft-ietf-6man-udpchecksums-00
       Waiting for related update to IPv6 base spec.
       This draft will be LC'ed in TSVWG also.

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

Other news:

   RSVP Directorate (formed in May 2010)
   Charter updated Sept 2011.

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


From iesg-secretary@ietf.org  Mon Nov  7 07:05:10 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BDF921F8BF4; Mon,  7 Nov 2011 07:05:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.348
X-Spam-Level: 
X-Spam-Status: No, score=-102.348 tagged_above=-999 required=5 tests=[AWL=-0.105, BAYES_00=-2.599, SARE_SUB_6CONS_WORD=0.356, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y62sfH0+NUeX; Mon,  7 Nov 2011 07:05:06 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4755B21F8BFB; Mon,  7 Nov 2011 07:05:06 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-tsvwg-sctp-strrst-12.txt> (Stream Control Transmission Protocol (SCTP) Stream Reconfiguration) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 3.63
Message-ID: <20111107150506.20675.99950.idtracker@ietfa.amsl.com>
Date: Mon, 07 Nov 2011 07:05:06 -0800
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Nov 2011 15:05:10 -0000

The IESG has received a request from the Transport Area Working Group WG
(tsvwg) to consider the following document:
- 'Stream Control Transmission Protocol (SCTP) Stream Reconfiguration'
  <draft-ietf-tsvwg-sctp-strrst-12.txt> as a Proposed Standard

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

Abstract


   Many applications that use SCTP want the ability to "reset" a stream.
   The intention of resetting a stream is to set the numbering sequence
   of the stream back to 'zero' with a corresponding notification to the
   upper layer that this has been performed.  The applications that want
   this feature want it so that they can "re-use" streams for different
   purposes but still utilize the stream sequence number so that the
   application can track the message flows.  Thus, without this feature,
   a new use of an old stream would result in message numbers greater
   than expected unless there is a protocol mechanism to "reset the
   streams back to zero".  This document also includes methods for
   resetting the transport sequence numbers, adding additional streams
   and resetting all stream sequence numbers.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-strrst/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-strrst/


No IPR declarations have been submitted directly on this I-D.



From jmpolk@cisco.com  Wed Nov  9 18:33:35 2011
Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3642B21F84F9 for <tsvwg@ietfa.amsl.com>; Wed,  9 Nov 2011 18:33:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.525
X-Spam-Level: 
X-Spam-Status: No, score=-106.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nJbaNgPQWBUV for <tsvwg@ietfa.amsl.com>; Wed,  9 Nov 2011 18:33:34 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id CC91921F84F8 for <tsvwg@ietf.org>; Wed,  9 Nov 2011 18:33:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=392; q=dns/txt; s=iport; t=1320892414; x=1322102014; h=message-id:date:to:from:subject:mime-version; bh=SYl8LcZil84R8zTLlFfYocDlvTJKDJJGviy7jIcZhzo=; b=kdK4ge3AdmcDwlNT1gFjVAnUFQX87Cy7/PUlQYsi6fXsgc+G1vH3HQMa yjfjgEYhTXVMeNhTCw8dAETyGN2R2gNwrDOxnjXpfCzKriewvYYJJtx8/ oBFm1LNr/m+Wy8nlmxRTRmGfmU736aWFdsG/jQHBrMenDn4MiUwyyPTg7 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAA03u06rRDoG/2dsb2JhbABDqiWBBYILASUCVjopRBwZh2iXaoEmAZ8LiRxjBIgMnio
X-IronPort-AV: E=Sophos;i="4.69,486,1315180800"; d="scan'208";a="13336538"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 10 Nov 2011 02:33:33 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8713.cisco.com [10.99.80.20]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAA2XW0D007401 for <tsvwg@ietf.org>; Thu, 10 Nov 2011 02:33:32 GMT
Message-Id: <201111100233.pAA2XW0D007401@mtv-core-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 09 Nov 2011 20:34:19 -0600
To: tsvwg <tsvwg@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: IETF 82 TSVWG meeting agenda (admittedly very late)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Nov 2011 02:33:35 -0000

TSVWG

Here is a link to the TSVWG meeting agenda when in Taiwan

http://www.ietf.org/proceedings/82/agenda/tsvwg.txt

There's only 3 presos, with a 4th if there's time.

TSVWG is meeting in on Monday from 1510-1610 which is the
Afternoon Session II, in room 101B.

Neither James nor Gorry will be at this meeting, so Wes Eddy (TSV AD) 
will chair in our place.

James & Gorry





From wes@mti-systems.com  Sun Nov 13 17:40:39 2011
Return-Path: <wes@mti-systems.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C4FA21F893C for <tsvwg@ietfa.amsl.com>; Sun, 13 Nov 2011 17:40:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level: 
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bJCOisF519nk for <tsvwg@ietfa.amsl.com>; Sun, 13 Nov 2011 17:40:38 -0800 (PST)
Received: from omr3.networksolutionsemail.com (omr3.networksolutionsemail.com [205.178.146.53]) by ietfa.amsl.com (Postfix) with ESMTP id 9976E11E80B0 for <tsvwg@ietf.org>; Sun, 13 Nov 2011 17:40:38 -0800 (PST)
Received: from cm-omr12 (mail.networksolutionsemail.com [205.178.146.50]) by omr3.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id pAE1eZAa015405 for <tsvwg@ietf.org>; Sun, 13 Nov 2011 20:40:36 -0500
Authentication-Results: cm-omr12 smtp.user=wes@mti-systems.com; auth=pass (PLAIN)
X-Authenticated-UID: wes@mti-systems.com
Received: from [94.75.220.253] ([94.75.220.253:18220] helo=[10.8.0.14]) by cm-omr12 (envelope-from <wes@mti-systems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 49/64-03697-29170CE4; Sun, 13 Nov 2011 20:40:35 -0500
Message-ID: <4EC07197.6000402@mti-systems.com>
Date: Mon, 14 Nov 2011 09:40:39 +0800
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: note-taker for IETF-82 TSVWG meeting
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 01:40:39 -0000

Since we only have an hour-long timeslot for TSVWG this afternoon, would
anyone like to volunteer in advance to take notes, so we don't waste too
much time starting up?

You'll earn 100 IETF points (okay, not really).

-- 
Wes Eddy
MTI Systems

From fred@cisco.com  Sun Nov 13 23:53:05 2011
Return-Path: <fred@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5C9411E81E5 for <tsvwg@ietfa.amsl.com>; Sun, 13 Nov 2011 23:53:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.813
X-Spam-Level: 
X-Spam-Status: No, score=-109.813 tagged_above=-999 required=5 tests=[AWL=0.786, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z443mpaykrPu for <tsvwg@ietfa.amsl.com>; Sun, 13 Nov 2011 23:53:02 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 3A91B11E81F1 for <tsvwg@ietf.org>; Sun, 13 Nov 2011 23:53:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=5657; q=dns/txt; s=iport; t=1321257181; x=1322466781; h=from:subject:date:message-id:to:mime-version: content-transfer-encoding; bh=GtAlGeHDnsorJMDb24D9yTFUihRplT7nUPxqw4CFsg0=; b=Cbf82NGyIDicuday13t+xo4mtTYP/pShqE/9YmSH46pLmYTWoX2VCAUy eMYLY2BV4EjqjWdV73qiLp1ZwfoQ8a43S9iSbOHU4U5DXRTW8LgbH9Pzy U2u8XJt8GzZ56+rpY591lZv8Byb+11fGmnNNc6d0QAJNQDkBJrtEGjeQ/ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAGHIwE5Io8UT/2dsb2JhbABCqX2BBYFyAQEBAxMBJzYECoE5NYdgmAeBJgGdVIkcYwSIDowghTuMSw
X-IronPort-AV: E=Sophos;i="4.69,507,1315180800"; d="scan'208";a="121511697"
Received: from bgl-core-4.cisco.com ([72.163.197.19]) by ams-iport-1.cisco.com with ESMTP; 14 Nov 2011 07:52:46 +0000
Received: from dhcp-57cd.meeting.ietf.org (hkidc-vpn-client-233-43.cisco.com [10.75.233.43]) by bgl-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAE7qht2010421 for <tsvwg@ietf.org>; Mon, 14 Nov 2011 07:52:44 GMT
Received: from [127.0.0.1] by dhcp-57cd.meeting.ietf.org (PGP Universal service); Mon, 14 Nov 2011 15:52:44 +0800
X-PGP-Universal: processed; by dhcp-57cd.meeting.ietf.org on Mon, 14 Nov 2011 15:52:44 +0800
From: Fred Baker <fred@cisco.com>
Subject: Comment on draft-ietf-tsvwg-byte-pkt-congest-05.txt 
Date: Mon, 14 Nov 2011 15:52:06 +0800
Message-Id: <CA11D312-2132-49F0-A3CF-0A3049010BF8@cisco.com>
To: tsvwg list <tsvwg@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 07:53:07 -0000

May I make one more comment on this document?

I came into the twvwg meeting today to be present for the discussion, =
which turned out to mostly not happen - there was a slide and a comment =
from the mike, and that was the summary of the discussion.

So...

Grepping for the word "consensus", I find:

>    Consensus has emerged over the years concerning the first stage:
>    whether queues are measured in bytes or packets, termed byte-mode
>    queue measurement or packet-mode queue measurement.  Section 2.1 of
>    this memo records this consensus in the RFC Series.  In summary the
>    choice solely depends on whether the resource is congested by bytes
>    or packets.
> ...
>    The IRTF Internet congestion control research group (ICCRG) has set
>    itself the task of reaching consensus on generic forwarding
>    mechanisms that are necessary and sufficient to support the
>    Internet's future congestion control requirements (the first
>    challenge in [RFC6077]).  Therefore, we defer the question of =
whether
>    packet congestion might become common and what to do if it does to
>    the IRTF (the 'Small Packets' challenge in [RFC6077]).
> ...
>       *  Removed language about consensus

Did we really remove the language about consensus?

In the section pointed to, it reports this consensus:

> 2.1.  Recommendation on Queue Measurement
>=20
>    Queue length is usually the most correct and simplest way to =
measure
>    congestion of a resource.  To avoid the pathological effects of =
drop
>    tail, an AQM function can then be used to transform queue length =
into
>    the probability of dropping or marking a packet (e.g.  RED's
>    piecewise linear function between thresholds).
>=20
>    If the resource is bit-congestible, the implementation SHOULD =
measure
>    the length of the queue in bytes.  If the resource is packet-
>    congestible, the implementation SHOULD measure the length of the
>    queue in packets.  No other choice makes sense, because the number =
of
>    packets waiting in the queue isn't relevant if the resource gets
>    congested by bytes and vice versa.
>=20
>    Corollaries:
>=20
>    1.  A RED implementation SHOULD use byte mode queue measurement for
>        measuring the congestion of bit-congestible resources and =
packet
>        mode queue measurement for packet-congestible resources.
>=20
>    2.  An implementation SHOULD NOT make it possible to configure the
>        way a queue measures itself, because whether a queue is bit-
>        congestible or packet-congestible is an inherent property of =
the
>        queue.
>=20
>    The recommended approach in less straightforward scenarios, such as
>    fixed size buffers, and resources without a queue, is discussed in
>    Section 4.1.

I think the statement is fine as far as it goes, but it has two =
remaining issues. One is the question of when an interface is bit/byte =
congestible and when it is packet-congestible; I'm sure that means =
something specific to the authors, but will be far less clear to an =
implementer - every interface has a rate, and few if any measure their =
rates in packets per unit time, so specifically what is in view as a =
"packet-congestible interface"? The other is that it only really applies =
to interfaces to a unique and non-blocking channel, like a serial line. =
When the congestible interface or queue is on a shared resource such as =
the fabric in an input-queued switch, an 802.11 interface, etc, the =
mathematics really involves two queues - the interface queues (in a =
statistical sense if not a hardware version) for access to the channel, =
and the packet is enqueued toward the interface, and both =
arrival/departure distributions are important.=20

Consider, for example, an AQM implementation on a WiFi channel. We have =
all been on busy 802.11 networks; we have this experience in our own =
history at the IETF. The dynamics are fairly strange. At the IP layer, =
sessions are generally between hosts on the WiFi network and hosts =
somewhere else. At the WiFi layer the AP is a proxy for the remote =
hosts, and is therefore in essence an extremely busy member of the WiFi =
system that otherwise operates in an approximation to a round-robin =
fashion. The effect is to build a bufferbloat scenario into the AP. Due =
to the shared nature of the medium and the fact that retransmissions are =
driven by absolute time (an RTO happens after a certain point in time), =
what one is really looking for is a packet's queue occupancy being =
measured in time. Bytes are a reasonable analog to time (which is what =
makes bytes reasonable for a bit-congestible interface) for noncontested =
interfaces, but a shared interface can fail to emit a transmission for =
an arbitrary time interval. So I might find myself, if some variant on =
Blue is in use, bumping the mark/drop probability when the queue becomes =
full and *also* any time one dequeues a packet that has been waiting =
longer than some time interval.

As to the "SHOULD NOT" regarding configuration, this probably makes a =
lot of sense in academic circles. Speaking as a vendor, I'm going to do =
what my customers tell me to. I'm happy enough with a default =
configuration following this recommendation, but if my customer wants it =
different, I'm not going to slap his hands.

As a side note, I would generally suggest that we step aside from "RED" =
and talk about "AQM". Blue, SFQ-Blue, and AVP are AQM algorithms that =
are likely superior to RED from an operational viewpoint.

From touch@isi.edu  Mon Nov 14 02:01:23 2011
Return-Path: <touch@isi.edu>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA3B121F8F89 for <tsvwg@ietfa.amsl.com>; Mon, 14 Nov 2011 02:00:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.2
X-Spam-Level: 
X-Spam-Status: No, score=-102.2 tagged_above=-999 required=5 tests=[AWL=0.400,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NCcaCA-x-jsD for <tsvwg@ietfa.amsl.com>; Mon, 14 Nov 2011 02:00:37 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 37F9021F8F5A for <tsvwg@ietf.org>; Mon, 14 Nov 2011 01:51:47 -0800 (PST)
Received: from [130.129.66.136] (dhcp-4288.meeting.ietf.org [130.129.66.136]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id pAE9nejs008616 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 14 Nov 2011 01:49:51 -0800 (PST)
Message-ID: <4EC0E434.1090107@isi.edu>
Date: Mon, 14 Nov 2011 01:49:40 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: Comment on draft-ietf-tsvwg-byte-pkt-congest-05.txt
References: <CA11D312-2132-49F0-A3CF-0A3049010BF8@cisco.com>
In-Reply-To: <CA11D312-2132-49F0-A3CF-0A3049010BF8@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tsvwg list <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Nov 2011 10:01:23 -0000

Hi, Fred,

On 11/13/2011 11:52 PM, Fred Baker wrote:
...
(existing text about bit/byte vs. packet congestion)
> I think the statement is fine as far as it goes, but it has two
> remaining issues. One is the question of when an interface is
> bit/byte congestible and when it is packet-congestible; I'm sure that
> means something specific to the authors, but will be far less clear
> to an implementer - every interface has a rate, and few if any
> measure their rates in packets per unit time, so specifically what is
> in view as a "packet-congestible interface"?

Some examples in the text might be useful.

Bit/byte congestion:
	- storage that assigns space based on the packet size
	- interfaces whose output bandwidth is overloaded
	- processing that is length-dependent (e.g., full packet
	hashes or encryption)

Packet congestion:
	- storage that assigns space on a per-packet basis,
	i.e., that has fixed slots (for max packets)
	- interfaces whose output slots are overloaded
	(with fixed slots per packet)
	- processing that is per-packet dependent (e.g.,
	header processing, header hashing, tunneling)

It is useful to note that there are some variants of these, e.g., where 
there are a small number of different buffer sizes (coarsely 
per-bit/byte), or ones with combined bottlenecks (there can be multiple 
places where resources are under contention!)

It's useful to explain what to do when there are combined bottlenecks in 
both places (alleviating only one might not suffice). I wonder what the 
algorithm should be in that case...

 > The other is that it
> only really applies to interfaces to a unique and non-blocking
> channel, like a serial line. When the congestible interface or queue
> is on a shared resource such as the fabric in an input-queued switch,
> an 802.11 interface, etc, the mathematics really involves two queues
> - the interface queues (in a statistical sense if not a hardware
> version) for access to the channel, and the packet is enqueued toward
> the interface, and both arrival/departure distributions are
> important.
>
> Consider, for example, an AQM implementation on a WiFi channel. We
> have all been on busy 802.11 networks; we have this experience in our
> own history at the IETF. The dynamics are fairly strange. At the IP
> layer, sessions are generally between hosts on the WiFi network and
> hosts somewhere else. At the WiFi layer the AP is a proxy for the
> remote hosts, and is therefore in essence an extremely busy member of
> the WiFi system that otherwise operates in an approximation to a
> round-robin fashion. The effect is to build a bufferbloat scenario
> into the AP. Due to the shared nature of the medium and the fact that
> retransmissions are driven by absolute time (an RTO happens after a
> certain point in time), what one is really looking for is a packet's
> queue occupancy being measured in time. Bytes are a reasonable analog
> to time (which is what makes bytes reasonable for a bit-congestible
> interface) for noncontested interfaces, but a shared interface can
> fail to emit a transmission for an arbitrary time interval. So I
> might find myself, if some variant on Blue is in use, bumping the
> mark/drop probability when the queue becomes full and *also* any time
> one dequeues a packet that has been waiting longer than some time
> interval.

This is the combined example I suggested above AFAICT.

Joe

> As to the "SHOULD NOT" regarding configuration, this probably makes a
> lot of sense in academic circles. Speaking as a vendor, I'm going to
> do what my customers tell me to. I'm happy enough with a default
> configuration following this recommendation, but if my customer wants
> it different, I'm not going to slap his hands.
>
> As a side note, I would generally suggest that we step aside from
> "RED" and talk about "AQM". Blue, SFQ-Blue, and AVP are AQM
> algorithms that are likely superior to RED from an operational
> viewpoint.

From bob.briscoe@bt.com  Wed Nov 30 02:51:43 2011
Return-Path: <bob.briscoe@bt.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 157D621F8A64 for <tsvwg@ietfa.amsl.com>; Wed, 30 Nov 2011 02:51:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GNjDEpmWP9er for <tsvwg@ietfa.amsl.com>; Wed, 30 Nov 2011 02:51:42 -0800 (PST)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137]) by ietfa.amsl.com (Postfix) with ESMTP id 2DC1F21F8A62 for <tsvwg@ietf.org>; Wed, 30 Nov 2011 02:51:40 -0800 (PST)
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 30 Nov 2011 10:51:39 +0000
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by i2kc08-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 30 Nov 2011 10:51:38 +0000
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1322650298994; Wed, 30 Nov 2011 10:51:38 +0000
Received: from MUT.jungle.bt.co.uk ([10.215.131.152]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id pAUApWd1032027; Wed, 30 Nov 2011 10:51:32 GMT
Message-Id: <201111301051.pAUApWd1032027@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 30 Nov 2011 10:51:34 +0000
To: Fred Baker <fred@cisco.com>
From: Bob Briscoe <bob.briscoe@bt.com>
Subject: Re: Comment on draft-ietf-tsvwg-byte-pkt-congest-05.txt 
In-Reply-To: <CA11D312-2132-49F0-A3CF-0A3049010BF8@cisco.com>
References: <CA11D312-2132-49F0-A3CF-0A3049010BF8@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 30 Nov 2011 10:51:38.0809 (UTC) FILETIME=[09784A90:01CCAF4E]
Cc: tsvwg list <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2011 10:51:43 -0000

Fred,

Sorry for the (very) belated reply.

You're right we didn't remove all occurrences of the consensus word 
(deliberately). The summary of changes should have been more specific.

We removed the language about consensus solely over whether byte-size 
should be taken account of in the network or at the end-systems, 
which is what I thought you & David Black thought was overstepping the mark.

The other two occurrences of the word 'consensus' I think are valid 
and can remain.
- Once Sally had pointed out (1997) that there's a distinction 
between i) using bytes to measure the queue and ii) whether you 
drop/mark a particular packet because of its byte-size, there has 
been no controversy on the issue #i. So the role of this RFC is 
indeed to declare consensus on issue #i.
- The IRTF having set itself the task of reaching consensus on 
something is surely a perfectly OK use of the word consensus.

I'll answer the second part of your email along with a response to 
Joe's follow-up.


Bob

At 07:52 14/11/2011, Fred Baker wrote:
>May I make one more comment on this document?
>
>I came into the twvwg meeting today to be present for the 
>discussion, which turned out to mostly not happen - there was a 
>slide and a comment from the mike, and that was the summary of the discussion.
>
>So...
>
>Grepping for the word "consensus", I find:
>
> >    Consensus has emerged over the years concerning the first stage:
> >    whether queues are measured in bytes or packets, termed byte-mode
> >    queue measurement or packet-mode queue measurement.  Section 2.1 of
> >    this memo records this consensus in the RFC Series.  In summary the
> >    choice solely depends on whether the resource is congested by bytes
> >    or packets.
> > ...
> >    The IRTF Internet congestion control research group (ICCRG) has set
> >    itself the task of reaching consensus on generic forwarding
> >    mechanisms that are necessary and sufficient to support the
> >    Internet's future congestion control requirements (the first
> >    challenge in [RFC6077]).  Therefore, we defer the question of whether
> >    packet congestion might become common and what to do if it does to
> >    the IRTF (the 'Small Packets' challenge in [RFC6077]).
> > ...
> >       *  Removed language about consensus
>
>Did we really remove the language about consensus?

________________________________________________________________
Bob Briscoe,                                BT Innovate & Design 


From bob.briscoe@bt.com  Wed Nov 30 04:49:29 2011
Return-Path: <bob.briscoe@bt.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88DAD21F8B26 for <tsvwg@ietfa.amsl.com>; Wed, 30 Nov 2011 04:49:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.099
X-Spam-Level: 
X-Spam-Status: No, score=-1.099 tagged_above=-999 required=5 tests=[AWL=-2.501, BAYES_00=-2.599, GB_SUMOF=5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jtOsJB5K8Vc8 for <tsvwg@ietfa.amsl.com>; Wed, 30 Nov 2011 04:49:27 -0800 (PST)
Received: from smtp3.smtp.bt.com (smtp3.smtp.bt.com [217.32.164.138]) by ietfa.amsl.com (Postfix) with ESMTP id 3BCB421F8B20 for <tsvwg@ietf.org>; Wed, 30 Nov 2011 04:49:26 -0800 (PST)
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 30 Nov 2011 12:49:24 +0000
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by i2kc08-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.4675); Wed, 30 Nov 2011 12:49:24 +0000
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1322657363826; Wed, 30 Nov 2011 12:49:23 +0000
Received: from MUT.jungle.bt.co.uk ([10.215.131.152]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id pAUCnL8u032441; Wed, 30 Nov 2011 12:49:21 GMT
Message-Id: <201111301249.pAUCnL8u032441@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 30 Nov 2011 12:49:20 +0000
To: Joe Touch <touch@isi.edu>, Fred Baker <fred@cisco.com>
From: Bob Briscoe <bob.briscoe@bt.com>
Subject: Re: Comment on draft-ietf-tsvwg-byte-pkt-congest-05.txt
In-Reply-To: <4EC0E434.1090107@isi.edu>
References: <CA11D312-2132-49F0-A3CF-0A3049010BF8@cisco.com> <4EC0E434.1090107@isi.edu>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_619688534==.ALT"
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 30 Nov 2011 12:49:24.0200 (UTC) FILETIME=[7CC56680:01CCAF5E]
Cc: tsvwg list <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2011 12:49:29 -0000

--=====================_619688534==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Joe & Fred,

At 09:49 14/11/2011, Joe Touch wrote:
>Hi, Fred,
>
>On 11/13/2011 11:52 PM, Fred Baker wrote:
>...

(I've added the this context, given I've taken so long to reply - sorry):
 >    If the resource is bit-congestible, the implementation SHOULD measure
 >    the length of the queue in bytes.  If the resource is packet-
 >    congestible, the implementation SHOULD measure the length of the
 >    queue in packets.

>>I think the statement is fine as far as it goes, but it has two
>>remaining issues. One is the question of when an interface is
>>bit/byte congestible and when it is packet-congestible; I'm sure that
>>means something specific to the authors, but will be far less clear
>>to an implementer - every interface has a rate, and few if any
>>measure their rates in packets per unit time, so specifically what is
>>in view as a "packet-congestible interface"?
>
>Some examples in the text might be useful.


We did give examples at the point where we define 
'packet-congestible' earlier (pasted below).

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
1.1. Terminology and Scoping

    Bit-congestible vs. Packet-congestible:

       Examples of packet-congestible resources are route look-up engines
       and firewalls, because load depends on how many packet headers
       they have to process.  Examples of bit-congestible resources are
       transmission links, radio power and most buffer memory, because
       the load depends on how many bits they have to transmit or store.
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

>Bit/byte congestion:        - storage that assigns space based on 
>the packet size
>         - interfaces whose output bandwidth is overloaded
>         - processing that is length-dependent (e.g., full packet
>         hashes or encryption)
>
>Packet congestion:
>         - storage that assigns space on a per-packet basis,
>         i.e., that has fixed slots (for max packets)
>         - interfaces whose output slots are overloaded
>         (with fixed slots per packet)
>         - processing that is per-packet dependent (e.g.,
>         header processing, header hashing, tunneling)
>
>It is useful to note that there are some variants of these, e.g., 
>where there are a small number of different buffer sizes (coarsely 
>per-bit/byte), or ones with combined bottlenecks (there can be 
>multiple places where resources are under contention!)

[BB]: To help implementers understand how to interpret the guidance 
in a more complex cases like this we talk about both cases as 
specific examples in the text. Search for 'buffer carving' and 
'hybrid forwarding system' respectively.


>It's useful to explain what to do when there are combined 
>bottlenecks in both places (alleviating only one might not suffice). 
>I wonder what the algorithm should be in that case...

[BB]: To avoid making the draft too complicated, we fudged a bit by 
saying the following:

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
    If we now imagine a hybrid forwarding system with transmission delay
    largely dependent on the byte-size of packets but buffers of one MTU
    per packet, it should strictly require a more complex algorithm to
    determine the probability of congestion.  It should be treated as two
    resources in sequence, where the sum of the byte-sizes of the packets
    within each packet buffer models congestion of the line while the
    length of the queue in packets models congestion of the queue.  Then
    the probability of congesting the forwarding buffer would be a
    conditional probability--conditional on the previously calculated
    probability of congesting the line.
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

Given Fred's request for clearer advice to implementers, I would like 
to replace the above para with the following (Jukaa might be able to 
shorten it - he's better than me at brevity):

"If we now consider a hybrid forwarding system with transmission 
congestion dependent on the byte-size of packets but fixed-size 
buffers of one MTU per packet, the queue length can still simply be 
measured in bytes, based on the following reasoning.

When an interface buffers packets, we need to ask what is the root 
cause of the congestion: the line or the buffer? In this case, the 
line is the root of the congestion. Packets temporarily back-up into 
the buffer because more bits are arriving than departing. Even though 
a run of small packets would fill MTU-sized buffers more quickly, the 
line will also drain them more quickly. Therefore, the queue is 
always merely a symptom of how congested the line is. Certainly, once 
the buffer gets full, we could say the buffer has become congested 
too. But reducing the arriving bit-rate would clear congestion of the 
line, which in turn would empty the buffer.

Theoretically, congestion in this hybrid could be treated as the 
probability of congestion of the buffer conditional on congestion of 
the line, where the sum of bytes in the buffers measures congestion 
of the line while the length of the queue in packets measures 
congestion of the queue. In practice, however, just measuring the 
bytes queued gets at the root cause: congestion of the line.

If the queue were building up behind forwarding look-ups or a 
firewall, then the problem would be the number of packets headers, 
not bits. But if it is a queue into a transmission line, the problem is bits.

In summary, for these hybrid cases, whether to measure the queue 
length in bits or packets depends primarily on whether the process in 
front of the queue is bit-congestible (e.g. a transmission line) or 
packet-congestible (e.g. forwarding look-ups). The internals of the 
buffer can usefully be ignored.
"


> > The other is that it
>>only really applies to interfaces to a unique and non-blocking
>>channel, like a serial line. When the congestible interface or queue
>>is on a shared resource such as the fabric in an input-queued switch,
>>an 802.11 interface, etc, the mathematics really involves two queues
>>- the interface queues (in a statistical sense if not a hardware
>>version) for access to the channel, and the packet is enqueued toward
>>the interface, and both arrival/departure distributions are
>>important.
>>
>>Consider, for example, an AQM implementation on a WiFi channel. We
>>have all been on busy 802.11 networks; we have this experience in our
>>own history at the IETF. The dynamics are fairly strange. At the IP
>>layer, sessions are generally between hosts on the WiFi network and
>>hosts somewhere else. At the WiFi layer the AP is a proxy for the
>>remote hosts, and is therefore in essence an extremely busy member of
>>the WiFi system that otherwise operates in an approximation to a
>>round-robin fashion. The effect is to build a bufferbloat scenario
>>into the AP. Due to the shared nature of the medium and the fact that
>>retransmissions are driven by absolute time (an RTO happens after a
>>certain point in time), what one is really looking for is a packet's
>>queue occupancy being measured in time. Bytes are a reasonable analog
>>to time (which is what makes bytes reasonable for a bit-congestible
>>interface) for noncontested interfaces, but a shared interface can
>>fail to emit a transmission for an arbitrary time interval. So I
>>might find myself, if some variant on Blue is in use, bumping the
>>mark/drop probability when the queue becomes full and *also* any time
>>one dequeues a packet that has been waiting longer than some time
>>interval.

Yes, you have to find something that approximates to a model of the 
sequence of congested resources. In byte-pkt we decided not to go 
deeply into this as another example. We felt the previous hybrid 
example had already covered the byte-vs-pkt issue sufficiently, and a 
wireless example might say a lot more about how to design a wireless 
AQM, but not a lot more about byte-v-pkt. Instead we referred to a 
Mobicom paper by Vasilios Siris on this 
<http://tools.ietf.org/html/draft-ietf-tsvwg-byte-pkt-congest-05#ref-ECNFixedWireless> 
(see Section 4.1.2. Congestion Measurement without a Queue).

That reference focuses on CDMA, but I chose it because it combines 
many forms of congestion you can get on an e2e fixed/wireless path. 
You can find other papers, including one on correctly signalling WiFi 
congestion here:
<http://www.ics.forth.gr/netlab/future_wireless.html>


>This is the combined example I suggested above AFAICT.

Yup.


Bob


>Joe
>
>>As to the "SHOULD NOT" regarding configuration, this probably makes a
>>lot of sense in academic circles. Speaking as a vendor, I'm going to
>>do what my customers tell me to. I'm happy enough with a default
>>configuration following this recommendation, but if my customer wants
>>it different, I'm not going to slap his hands.
>>
>>As a side note, I would generally suggest that we step aside from
>>"RED" and talk about "AQM". Blue, SFQ-Blue, and AVP are AQM
>>algorithms that are likely superior to RED from an operational
>>viewpoint.
>
>________________________________________________________________
>Bob Briscoe,                                BT Innovate & Design 
--=====================_619688534==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
Joe &amp; Fred,<br><br>
At 09:49 14/11/2011, Joe Touch wrote:<br>
<blockquote type=cite class=cite cite="">Hi, Fred,<br><br>
On 11/13/2011 11:52 PM, Fred Baker wrote:<br>
...</blockquote><br>
(I've added the this context, given I've taken so long to reply -
sorry):<br>
&gt;&nbsp;&nbsp;&nbsp; If the resource is bit-congestible, the
implementation SHOULD measure<br>
&gt;&nbsp;&nbsp;&nbsp; the length of the queue in bytes.&nbsp; If the
resource is packet-<br>
&gt;&nbsp;&nbsp;&nbsp; congestible, the implementation SHOULD measure the
length of the<br>
&gt;&nbsp;&nbsp;&nbsp; queue in packets.&nbsp; <br><br>
<blockquote type=cite class=cite cite="">
<blockquote type=cite class=cite cite="">I think the statement is fine as
far as it goes, but it has two<br>
remaining issues. One is the question of when an interface is<br>
bit/byte congestible and when it is packet-congestible; I'm sure
that<br>
means something specific to the authors, but will be far less clear<br>
to an implementer - every interface has a rate, and few if any<br>
measure their rates in packets per unit time, so specifically what
is<br>
in view as a &quot;packet-congestible interface&quot;?</blockquote><br>
Some examples in the text might be useful.</blockquote><br><br>
<pre>We did give examples at the point where we define
'packet-congestible' earlier (pasted below). 

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
1.1. Terminology and Scoping

&nbsp;&nbsp; Bit-congestible vs. Packet-congestible:&nbsp; 

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Examples of packet-congestible resources
are route look-up engines
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and firewalls, because load depends on how
many packet headers
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; they have to process.&nbsp; Examples of
bit-congestible resources are
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; transmission links, radio power and most
buffer memory, because
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the load depends on how many bits they
have to transmit or store.
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

</pre><blockquote type=cite class=cite cite="">Bit/byte
congestion:<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>
- storage that assigns space based on the packet size<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>-
interfaces whose output bandwidth is overloaded<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>-
processing that is length-dependent (e.g., full packet<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>hashes or
encryption)<br><br>
Packet congestion:<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>- storage
that assigns space on a per-packet basis,<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>i.e., that
has fixed slots (for max packets)<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>-
interfaces whose output slots are overloaded<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>(with
fixed slots per packet)<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>-
processing that is per-packet dependent (e.g.,<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>header
processing, header hashing, tunneling)<br><br>
It is useful to note that there are some variants of these, e.g., where
there are a small number of different buffer sizes (coarsely
per-bit/byte), or ones with combined bottlenecks (there can be multiple
places where resources are under contention!)</blockquote><br>
[BB]: To help implementers understand how to interpret the guidance in a
more complex cases like this we talk about both cases as specific
examples in the text. Search for 'buffer carving' and '<pre>hybrid
forwarding system' respectively.


</pre><blockquote type=cite class=cite cite="">It's useful to explain
what to do when there are combined bottlenecks in both places
(alleviating only one might not suffice). I wonder what the algorithm
should be in that case...</blockquote><br>
[BB]: To avoid making the draft too complicated, we fudged a bit by
saying the following:<br><br>
<pre>
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
&nbsp;&nbsp; If we now imagine a hybrid forwarding system with
transmission delay
&nbsp;&nbsp; largely dependent on the byte-size of packets but buffers of
one MTU
&nbsp;&nbsp; per packet, it should strictly require a more complex
algorithm to
&nbsp;&nbsp; determine the probability of congestion.&nbsp; It should be
treated as two
&nbsp;&nbsp; resources in sequence, where the sum of the byte-sizes of
the packets
&nbsp;&nbsp; within each packet buffer models congestion of the line
while the
&nbsp;&nbsp; length of the queue in packets models congestion of the
queue.&nbsp; Then
&nbsp;&nbsp; the probability of congesting the forwarding buffer would be
a
&nbsp;&nbsp; conditional probability--conditional on the previously
calculated
&nbsp;&nbsp; probability of congesting the line.
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

</pre>Given Fred's request for clearer advice to implementers, I would
like to replace the above para with the following (Jukaa might be able to
shorten it - he's better than me at brevity):<br><br>
&quot;If we now consider a hybrid forwarding system with transmission
congestion dependent on the byte-size of packets but fixed-size buffers
of one MTU per packet, the queue length can still simply be measured in
bytes, based on the following reasoning.<br><br>
When an interface buffers packets, we need to ask what is the root cause
of the congestion: the line or the buffer? In this case, the line is the
root of the congestion. Packets temporarily back-up into the buffer
because more bits are arriving than departing. Even though a run of small
packets would fill MTU-sized buffers more quickly, the line will also
drain them more quickly. Therefore, the queue is always merely a symptom
of how congested the line is. Certainly, once the buffer gets full, we
could say the buffer has become congested too. But reducing the arriving
bit-rate would clear congestion of the line, which in turn would empty
the buffer. <br><br>
Theoretically, congestion in this hybrid could be treated as the
probability of congestion of the buffer conditional on congestion of the
line, where the sum of bytes in the buffers measures congestion of the
line while the length of the queue in packets measures congestion of the
queue. In practice, however, just measuring the bytes queued gets at the
root cause: congestion of the line.<br><br>
If the queue were building up behind forwarding look-ups or a firewall,
then the problem would be the number of packets headers, not bits. But if
it is a queue into a transmission line, the problem is bits. <br><br>
In summary, for these hybrid cases, whether to measure the queue length
in bits or packets depends primarily on whether the process in front of
the queue is bit-congestible (e.g. a transmission line) or
packet-congestible (e.g. forwarding look-ups). The internals of the
buffer can usefully be ignored. <br>
&quot;<br><br>
<br>
<blockquote type=cite class=cite cite="">&gt; The other is that it<br>
<blockquote type=cite class=cite cite="">only really applies to
interfaces to a unique and non-blocking<br>
channel, like a serial line. When the congestible interface or queue<br>
is on a shared resource such as the fabric in an input-queued
switch,<br>
an 802.11 interface, etc, the mathematics really involves two queues<br>
- the interface queues (in a statistical sense if not a hardware<br>
version) for access to the channel, and the packet is enqueued
toward<br>
the interface, and both arrival/departure distributions are<br>
important.<br><br>
Consider, for example, an AQM implementation on a WiFi channel. We<br>
have all been on busy 802.11 networks; we have this experience in
our<br>
own history at the IETF. The dynamics are fairly strange. At the IP<br>
layer, sessions are generally between hosts on the WiFi network and<br>
hosts somewhere else. At the WiFi layer the AP is a proxy for the<br>
remote hosts, and is therefore in essence an extremely busy member
of<br>
the WiFi system that otherwise operates in an approximation to a<br>
round-robin fashion. The effect is to build a bufferbloat scenario<br>
into the AP. Due to the shared nature of the medium and the fact
that<br>
retransmissions are driven by absolute time (an RTO happens after a<br>
certain point in time), what one is really looking for is a packet's<br>
queue occupancy being measured in time. Bytes are a reasonable
analog<br>
to time (which is what makes bytes reasonable for a bit-congestible<br>
interface) for noncontested interfaces, but a shared interface can<br>
fail to emit a transmission for an arbitrary time interval. So I<br>
might find myself, if some variant on Blue is in use, bumping the<br>
mark/drop probability when the queue becomes full and *also* any
time<br>
one dequeues a packet that has been waiting longer than some time<br>
interval.</blockquote></blockquote><br>
Yes, you have to find something that approximates to a model of the
sequence of congested resources. In byte-pkt we decided not to go deeply
into this as another example. We felt the previous hybrid example had
already covered the byte-vs-pkt issue sufficiently, and a wireless
example might say a lot more about how to design a wireless AQM, but not
a lot more about byte-v-pkt. Instead we referred to a Mobicom paper by
Vasilios Siris on this
&lt;<a href="http://tools.ietf.org/html/draft-ietf-tsvwg-byte-pkt-congest-05#ref-ECNFixedWireless" eudora="autourl">
http://tools.ietf.org/html/draft-ietf-tsvwg-byte-pkt-congest-05#ref-ECNFixedWireless</a>
&gt; (see Section 4.1.2. Congestion Measurement without a
Queue).<br><br>
That reference focuses on CDMA, but I chose it because it combines many
forms of congestion you can get on an e2e fixed/wireless path. You can
find other papers, including one on correctly signalling WiFi congestion
here:<br>
&lt;<a href="http://www.ics.forth.gr/netlab/future_wireless.html" eudora="autourl">
http://www.ics.forth.gr/netlab/future_wireless.html</a>&gt;<br><br>
<br>
<blockquote type=cite class=cite cite="">This is the combined example I
suggested above AFAICT.</blockquote><br>
Yup.<br><br>
<br>
Bob<br><br>
<br>
<blockquote type=cite class=cite cite="">Joe<br><br>
<blockquote type=cite class=cite cite="">As to the &quot;SHOULD NOT&quot;
regarding configuration, this probably makes a<br>
lot of sense in academic circles. Speaking as a vendor, I'm going to<br>
do what my customers tell me to. I'm happy enough with a default<br>
configuration following this recommendation, but if my customer
wants<br>
it different, I'm not going to slap his hands.<br><br>
As a side note, I would generally suggest that we step aside from<br>
&quot;RED&quot; and talk about &quot;AQM&quot;. Blue, SFQ-Blue, and AVP
are AQM<br>
algorithms that are likely superior to RED from an operational<br>
viewpoint.</blockquote>
<x-sigsep><p></x-sigsep>
________________________________________________________________<br>
Bob
Briscoe,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
BT Innovate &amp; Design</body>
</html>

--=====================_619688534==.ALT--


From jukka.manner@aalto.fi  Wed Nov 30 05:36:38 2011
Return-Path: <jukka.manner@aalto.fi>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C50B621F87D3 for <tsvwg@ietfa.amsl.com>; Wed, 30 Nov 2011 05:36:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.401
X-Spam-Level: **
X-Spam-Status: No, score=2.401 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_SUMOF=5]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aEwMC9Xo2kvU for <tsvwg@ietfa.amsl.com>; Wed, 30 Nov 2011 05:36:37 -0800 (PST)
Received: from mx03.aalto.fi (mx03.aalto.fi [130.233.222.102]) by ietfa.amsl.com (Postfix) with ESMTP id 617F121F85FF for <tsvwg@ietf.org>; Wed, 30 Nov 2011 05:36:37 -0800 (PST)
Received: from mx03.aalto.fi (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 12D6C28772; Wed, 30 Nov 2011 15:36:36 +0200 (EET)
Received: from EXHUB02.org.aalto.fi (ex-hub02.org.aalto.fi [130.233.222.119]) by mx03.aalto.fi (Postfix) with ESMTP id C58C6282C4; Wed, 30 Nov 2011 15:36:35 +0200 (EET)
Received: from EXMDB04.org.aalto.fi ([169.254.1.248]) by EXHUB02.org.aalto.fi ([130.233.222.119]) with mapi id 14.01.0339.001; Wed, 30 Nov 2011 15:36:35 +0200
From: Manner Jukka <jukka.manner@aalto.fi>
To: Bob Briscoe <bob.briscoe@bt.com>
Subject: Re: Comment on draft-ietf-tsvwg-byte-pkt-congest-05.txt
Thread-Topic: Comment on draft-ietf-tsvwg-byte-pkt-congest-05.txt
Thread-Index: AQHMr16KfrTYsEomSkC9nO4wDoaR3JXFSeGA
Date: Wed, 30 Nov 2011 13:36:35 +0000
Message-ID: <AF6BE23E-6D01-4044-8E5D-E476F4E1F956@aalto.fi>
References: <CA11D312-2132-49F0-A3CF-0A3049010BF8@cisco.com> <4EC0E434.1090107@isi.edu> <13338_1322657386_4ED62669_13338_27_4_201111301249.pAUCnL8u032441@bagheera.jungle.bt.co.uk>
In-Reply-To: <13338_1322657386_4ED62669_13338_27_4_201111301249.pAUCnL8u032441@bagheera.jungle.bt.co.uk>
Accept-Language: en-US, fi-FI
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [193.64.22.59]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <93DA50FD94969348975658D8D327F15E@aalto.fi>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: tsvwg list <tsvwg@ietf.org>, Fred Baker <fred@cisco.com>, Joe Touch <touch@isi.edu>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2011 13:36:38 -0000

Hi, as a sort of side note, I had a chat with Fred in Taipei and gave an ex=
ample of the packet-congestible resource: WLAN. (Fred had a concern/questio=
n about what is packet-congestible in the real world)

WLAN is in theory bit-congestible but WLAN also has an upper limit of packe=
ts/second and with small packets, it actually becomes packet-congestible. Y=
et, as a caveat, the packet-congestion is not really visible to the impleme=
nter of AQM, this was pointed out by Fred.

Jukka

On Nov 30, 2011, at 2:49 PM, Bob Briscoe wrote:

> Joe & Fred,
>=20
> At 09:49 14/11/2011, Joe Touch wrote:
>> Hi, Fred,
>>=20
>> On 11/13/2011 11:52 PM, Fred Baker wrote:
>> ...
>=20
> (I've added the this context, given I've taken so long to reply - sorry):
> >    If the resource is bit-congestible, the implementation SHOULD measur=
e
> >    the length of the queue in bytes.  If the resource is packet-
> >    congestible, the implementation SHOULD measure the length of the
> >    queue in packets. =20
>=20
>>> I think the statement is fine as far as it goes, but it has two
>>> remaining issues. One is the question of when an interface is
>>> bit/byte congestible and when it is packet-congestible; I'm sure that
>>> means something specific to the authors, but will be far less clear
>>> to an implementer - every interface has a rate, and few if any
>>> measure their rates in packets per unit time, so specifically what is
>>> in view as a "packet-congestible interface"?
>>=20
>> Some examples in the text might be useful.
>=20
>=20
> We did give examples at the point where we define
> 'packet-congestible' earlier (pasted below).=20
>=20
> /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
> 1.1. Terminology and Scoping
>=20
>    Bit-congestible vs. Packet-congestible: =20
>=20
>       Examples of packet-congestible resources
> are route look-up engines
>       and firewalls, because load depends on how
> many packet headers
>       they have to process.  Examples of
> bit-congestible resources are
>       transmission links, radio power and most
> buffer memory, because
>       the load depends on how many bits they
> have to transmit or store.
> /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
>=20
>=20
>> Bit/byte congestion:         - storage that assigns space based on the p=
acket size
>>         - interfaces whose output bandwidth is overloaded
>>         - processing that is length-dependent (e.g., full packet
>>         hashes or encryption)
>>=20
>> Packet congestion:
>>         - storage that assigns space on a per-packet basis,
>>         i.e., that has fixed slots (for max packets)
>>         - interfaces whose output slots are overloaded
>>         (with fixed slots per packet)
>>         - processing that is per-packet dependent (e.g.,
>>         header processing, header hashing, tunneling)
>>=20
>> It is useful to note that there are some variants of these, e.g., where =
there are a small number of different buffer sizes (coarsely per-bit/byte),=
 or ones with combined bottlenecks (there can be multiple places where reso=
urces are under contention!)
>=20
> [BB]: To help implementers understand how to interpret the guidance in a =
more complex cases like this we talk about both cases as specific examples =
in the text. Search for 'buffer carving' and '
> hybrid
> forwarding system' respectively.
>=20
>=20
>=20
>> It's useful to explain what to do when there are combined bottlenecks in=
 both places (alleviating only one might not suffice). I wonder what the al=
gorithm should be in that case...
>=20
> [BB]: To avoid making the draft too complicated, we fudged a bit by sayin=
g the following:
>=20
> /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
>    If we now imagine a hybrid forwarding system with
> transmission delay
>    largely dependent on the byte-size of packets but buffers of
> one MTU
>    per packet, it should strictly require a more complex
> algorithm to
>    determine the probability of congestion.  It should be
> treated as two
>    resources in sequence, where the sum of the byte-sizes of
> the packets
>    within each packet buffer models congestion of the line
> while the
>    length of the queue in packets models congestion of the
> queue.  Then
>    the probability of congesting the forwarding buffer would be
> a
>    conditional probability--conditional on the previously
> calculated
>    probability of congesting the line.
> /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
>=20
>=20
> Given Fred's request for clearer advice to implementers, I would like to =
replace the above para with the following (Jukaa might be able to shorten i=
t - he's better than me at brevity):
>=20
> "If we now consider a hybrid forwarding system with transmission congesti=
on dependent on the byte-size of packets but fixed-size buffers of one MTU =
per packet, the queue length can still simply be measured in bytes, based o=
n the following reasoning.
>=20
> When an interface buffers packets, we need to ask what is the root cause =
of the congestion: the line or the buffer? In this case, the line is the ro=
ot of the congestion. Packets temporarily back-up into the buffer because m=
ore bits are arriving than departing. Even though a run of small packets wo=
uld fill MTU-sized buffers more quickly, the line will also drain them more=
 quickly. Therefore, the queue is always merely a symptom of how congested =
the line is. Certainly, once the buffer gets full, we could say the buffer =
has become congested too. But reducing the arriving bit-rate would clear co=
ngestion of the line, which in turn would empty the buffer.=20
>=20
> Theoretically, congestion in this hybrid could be treated as the probabil=
ity of congestion of the buffer conditional on congestion of the line, wher=
e the sum of bytes in the buffers measures congestion of the line while the=
 length of the queue in packets measures congestion of the queue. In practi=
ce, however, just measuring the bytes queued gets at the root cause: conges=
tion of the line.
>=20
> If the queue were building up behind forwarding look-ups or a firewall, t=
hen the problem would be the number of packets headers, not bits. But if it=
 is a queue into a transmission line, the problem is bits.=20
>=20
> In summary, for these hybrid cases, whether to measure the queue length i=
n bits or packets depends primarily on whether the process in front of the =
queue is bit-congestible (e.g. a transmission line) or packet-congestible (=
e.g. forwarding look-ups). The internals of the buffer can usefully be igno=
red.=20
> "
>=20
>=20
>> > The other is that it
>>> only really applies to interfaces to a unique and non-blocking
>>> channel, like a serial line. When the congestible interface or queue
>>> is on a shared resource such as the fabric in an input-queued switch,
>>> an 802.11 interface, etc, the mathematics really involves two queues
>>> - the interface queues (in a statistical sense if not a hardware
>>> version) for access to the channel, and the packet is enqueued toward
>>> the interface, and both arrival/departure distributions are
>>> important.
>>>=20
>>> Consider, for example, an AQM implementation on a WiFi channel. We
>>> have all been on busy 802.11 networks; we have this experience in our
>>> own history at the IETF. The dynamics are fairly strange. At the IP
>>> layer, sessions are generally between hosts on the WiFi network and
>>> hosts somewhere else. At the WiFi layer the AP is a proxy for the
>>> remote hosts, and is therefore in essence an extremely busy member of
>>> the WiFi system that otherwise operates in an approximation to a
>>> round-robin fashion. The effect is to build a bufferbloat scenario
>>> into the AP. Due to the shared nature of the medium and the fact that
>>> retransmissions are driven by absolute time (an RTO happens after a
>>> certain point in time), what one is really looking for is a packet's
>>> queue occupancy being measured in time. Bytes are a reasonable analog
>>> to time (which is what makes bytes reasonable for a bit-congestible
>>> interface) for noncontested interfaces, but a shared interface can
>>> fail to emit a transmission for an arbitrary time interval. So I
>>> might find myself, if some variant on Blue is in use, bumping the
>>> mark/drop probability when the queue becomes full and *also* any time
>>> one dequeues a packet that has been waiting longer than some time
>>> interval.
>=20
> Yes, you have to find something that approximates to a model of the seque=
nce of congested resources. In byte-pkt we decided not to go deeply into th=
is as another example. We felt the previous hybrid example had already cove=
red the byte-vs-pkt issue sufficiently, and a wireless example might say a =
lot more about how to design a wireless AQM, but not a lot more about byte-=
v-pkt. Instead we referred to a Mobicom paper by Vasilios Siris on this < h=
ttp://tools.ietf.org/html/draft-ietf-tsvwg-byte-pkt-congest-05#ref-ECNFixed=
Wireless > (see Section 4.1.2. Congestion Measurement without a Queue).
>=20
> That reference focuses on CDMA, but I chose it because it combines many f=
orms of congestion you can get on an e2e fixed/wireless path. You can find =
other papers, including one on correctly signalling WiFi congestion here:
> < http://www.ics.forth.gr/netlab/future_wireless.html>
>=20
>=20
>> This is the combined example I suggested above AFAICT.
>=20
> Yup.
>=20
>=20
> Bob
>=20
>=20
>> Joe
>>=20
>>> As to the "SHOULD NOT" regarding configuration, this probably makes a
>>> lot of sense in academic circles. Speaking as a vendor, I'm going to
>>> do what my customers tell me to. I'm happy enough with a default
>>> configuration following this recommendation, but if my customer wants
>>> it different, I'm not going to slap his hands.
>>>=20
>>> As a side note, I would generally suggest that we step aside from
>>> "RED" and talk about "AQM". Blue, SFQ-Blue, and AVP are AQM
>>> algorithms that are likely superior to RED from an operational
>>> viewpoint.
>> ________________________________________________________________
>> Bob Briscoe,                                BT Innovate & Design
>>=20


From john@jlc.net  Wed Nov 30 09:22:46 2011
Return-Path: <john@jlc.net>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4FA221F8B45 for <tsvwg@ietfa.amsl.com>; Wed, 30 Nov 2011 09:22:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5zHuYkWl4LXt for <tsvwg@ietfa.amsl.com>; Wed, 30 Nov 2011 09:22:46 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 5BBD921F8B15 for <tsvwg@ietf.org>; Wed, 30 Nov 2011 09:22:46 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 9B4F933C20; Wed, 30 Nov 2011 12:22:45 -0500 (EST)
Date: Wed, 30 Nov 2011 12:22:45 -0500
From: John Leslie <john@jlc.net>
To: tsvwg list <tsvwg@ietf.org>
Subject: Re: Comment on draft-ietf-tsvwg-byte-pkt-congest-05.txt
Message-ID: <20111130172245.GC36242@verdi>
References: <CA11D312-2132-49F0-A3CF-0A3049010BF8@cisco.com> <201111301051.pAUApWd1032027@bagheera.jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201111301051.pAUApWd1032027@bagheera.jungle.bt.co.uk>
User-Agent: Mutt/1.4.1i
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Nov 2011 17:22:47 -0000

   Apologies up-front: I thought I was subscribed to this list and only
recently _actually_ subscribed.

   Further, searching the archives, I didn't find the answer to this
question...

   Could somebody point me at a particular post explaining why this
I-D is seeking BCP status?

--
John Leslie <john@jlc.net>
