
From dwing@cisco.com  Fri Dec  2 22:41:48 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 2757111E8081 for <tsvwg@ietfa.amsl.com>; Fri,  2 Dec 2011 22:41:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.542
X-Spam-Level: 
X-Spam-Status: No, score=-106.542 tagged_above=-999 required=5 tests=[AWL=0.057, 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 IMMzsc-kBh1s for <tsvwg@ietfa.amsl.com>; Fri,  2 Dec 2011 22:41:47 -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 851F511E8073 for <tsvwg@ietf.org>; Fri,  2 Dec 2011 22:41:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=4470; q=dns/txt; s=iport; t=1322894507; x=1324104107; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=PSBtoDjYK6KrVnypiiXtXTKJBFtR/sKMB5Ib/WH9hvk=; b=CM0lbhDlaWZz+GeRs3K7qA7Ma+uSteLLRXl6TNLOyk9qtxfZ/mNyjgi7 sk7MA/Yb3OjvMwIsq37gYS0TAZjrK9JVAX6MHiMcnD286g1pu8aoeXwob ValTcmiQGviwnuvfJ/C0xBFDzqC3AMpw2XSFp7CrhzH4A6aLT9NFxelij 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqcAAJrD2U6rRDoI/2dsb2JhbABEmgWBao4+gQWBcgEBAQECAQgKARcQPwUHAQMCCQ8CBAEBAScHGSMKCQgBAQQTCxeHZZgkAZ4eiyEEiCuERCcBmXk
X-IronPort-AV: E=Sophos;i="4.71,288,1320624000"; d="scan'208";a="17581423"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 03 Dec 2011 06:41:47 +0000
Received: from dwingWS ([10.32.240.195]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pB36fkcY031166; Sat, 3 Dec 2011 06:41:47 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> <1f2501cc9906$fe116c70$fa344550$@com> <1C060940-B69C-4FE7-8A59-6A86375BF25A@fh-muenster.de>
In-Reply-To: <1C060940-B69C-4FE7-8A59-6A86375BF25A@fh-muenster.de>
Subject: RE: SCTP-over-UDP and port 9899
Date: Fri, 2 Dec 2011 22:41:46 -0800
Message-ID: <018201ccb186$a10ed6a0$e32c83e0$@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: AcyZU3kaPQc6i+yBSNyi62RJ3heJgwYMqHBg
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: Sat, 03 Dec 2011 06:41:48 -0000

> -----Original Message-----
> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> Sent: Wednesday, November 02, 2011 4:35 AM
> To: Dan Wing
> Cc: tsvwg@ietf.org; randall@lakerest.net
> Subject: Re: SCTP-over-UDP and port 9899
> 
> 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...

Probably just a terminology disagreement.  To my mind, everything
is client/server, based on who sends the first packet (the client)
and who receives the first packet (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.
> I'm not sure why you are concerned.

Because I don't understand why the I-D insists on specifying
the source port (no other protocol does, that I'm aware of),
and it will cause problems when multiple SCTP-over-UDP
clients are running on the same host.  One of them will likely
be written to insist, strongly, that it get port 9899. 

If there is no reason/benefit/value/advantage to use source 
port 9899, then please remove the text from the I-D.  This
follows the dictum that a standard is finished when everything
unnecessary has been removed and it still works. 

> 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.

-d

> 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 hannes.tschofenig@nsn.com  Sun Dec  4 01:37:54 2011
Return-Path: <hannes.tschofenig@nsn.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 84D6321F8462 for <tsvwg@ietfa.amsl.com>; Sun,  4 Dec 2011 01:37:54 -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 Aa3h7fVR0yVF for <tsvwg@ietfa.amsl.com>; Sun,  4 Dec 2011 01:37:53 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 9056C21F845F for <tsvwg@ietf.org>; Sun,  4 Dec 2011 01:37:53 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id pB49bVgC009864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 4 Dec 2011 10:37:31 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id pB49bVms006571; Sun, 4 Dec 2011 10:37:31 +0100
Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 4 Dec 2011 10:37:31 +0100
Received: from 10.144.243.246 ([10.144.243.246]) by FIESEXC035.nsn-intra.net ([10.159.0.182]) via Exchange Front-End Server webmail.nsn-intra.net ([10.150.128.36]) with Microsoft Exchange Server HTTP-DAV ; Sun,  4 Dec 2011 09:37:30 +0000
User-Agent: Microsoft-Entourage/12.31.0.110725
Date: Sun, 04 Dec 2011 11:37:28 +0200
Subject: Re: SCTP-over-UDP and port 9899
From: Hannes Tschofenig <hannes.tschofenig@nsn.com>
To: Dan Wing <dwing@cisco.com>, "'Michael Tuexen'" <tuexen@fh-muenster.de>
Message-ID: <CB010BF8.83D6%hannes.tschofenig@nsn.com>
Thread-Topic: SCTP-over-UDP and port 9899
Thread-Index: AcyyaFY7LEwaxQZn6kyVczK/PtqOcQ==
In-Reply-To: <018201ccb186$a10ed6a0$e32c83e0$@com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 04 Dec 2011 09:37:31.0141 (UTC) FILETIME=[581B0350:01CCB268]
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: Sun, 04 Dec 2011 09:37:54 -0000

I agree with Dan. Using a fixed source port does not appear to be useful.


On 12/3/11 8:41 AM, "Dan Wing" <dwing@cisco.com> wrote:

>> -----Original Message-----
>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>> Sent: Wednesday, November 02, 2011 4:35 AM
>> To: Dan Wing
>> Cc: tsvwg@ietf.org; randall@lakerest.net
>> Subject: Re: SCTP-over-UDP and port 9899
>> 
>> 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...
> 
> Probably just a terminology disagreement.  To my mind, everything
> is client/server, based on who sends the first packet (the client)
> and who receives the first packet (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.
>> I'm not sure why you are concerned.
> 
> Because I don't understand why the I-D insists on specifying
> the source port (no other protocol does, that I'm aware of),
> and it will cause problems when multiple SCTP-over-UDP
> clients are running on the same host.  One of them will likely
> be written to insist, strongly, that it get port 9899.
> 
> If there is no reason/benefit/value/advantage to use source
> port 9899, then please remove the text from the I-D.  This
> follows the dictum that a standard is finished when everything
> unnecessary has been removed and it still works.
> 
>> 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.
> 
> -d
> 
>> 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 tuexen@fh-muenster.de  Sun Dec  4 02:34:07 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 4953B21F8663 for <tsvwg@ietfa.amsl.com>; Sun,  4 Dec 2011 02:34:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.421
X-Spam-Level: 
X-Spam-Status: No, score=-2.421 tagged_above=-999 required=5 tests=[AWL=0.178,  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 Knb0ss+2Ocwp for <tsvwg@ietfa.amsl.com>; Sun,  4 Dec 2011 02:34:06 -0800 (PST)
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 A1C3421F85A4 for <tsvwg@ietf.org>; Sun,  4 Dec 2011 02:34:05 -0800 (PST)
Received: from [192.168.1.200] (p508FBF8C.dip.t-dialin.net [80.143.191.140]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 0D1E01C0B4610; Sun,  4 Dec 2011 11:34: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: <018201ccb186$a10ed6a0$e32c83e0$@com>
Date: Sun, 4 Dec 2011 11:34:01 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6AF71C60-CA88-4BE0-86F2-0840AA447614@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> <1C060940-B69C-4FE7-8A59-6A86375BF25A@fh-muenster.de> <018201ccb186$a10ed6a0$e32c83e0$@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: Sun, 04 Dec 2011 10:34:07 -0000

On Dec 3, 2011, at 7:41 AM, Dan Wing wrote:

>> -----Original Message-----
>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>> Sent: Wednesday, November 02, 2011 4:35 AM
>> To: Dan Wing
>> Cc: tsvwg@ietf.org; randall@lakerest.net
>> Subject: Re: SCTP-over-UDP and port 9899
>>=20
>> On Nov 2, 2011, at 3:27 AM, Dan Wing wrote:
>>=20
>>>>> 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...
>>>=20
>>> "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...
>=20
> Probably just a terminology disagreement.  To my mind, everything
> is client/server, based on who sends the first packet (the client)
> and who receives the first packet (server).
>=20
>=20
>>>>>> That is why I used a MAY. But I'm open to use any other
>> formulation.
>>>>>> Do you have a suggestion?
>>>>>=20
>>>>> 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).
>>>>=20
>>>> Would it be acceptable for you if I replace
>>>>=20
>>>> 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.
>>>>=20
>>>> by
>>>>=20
>>>> Each SCTP stack uses a single local UDP encapsulation port number.
>>>>=20
>>>> 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.
>>>=20
>>> 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.
>=20
> Because I don't understand why the I-D insists on specifying
> the source port (no other protocol does, that I'm aware of),
> and it will cause problems when multiple SCTP-over-UDP
> clients are running on the same host.  One of them will likely
> be written to insist, strongly, that it get port 9899.=20
The text I have in the CVS version reads:

<t>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 assigned 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.</t>

I think we agree on the section except for the sentence:

The IANA assigned value of 9989 MAY be used as this port number.

I think this is as weak as possible.

It is already made clear that running multiple SCTP stacks on a
host make it not possible to use the same port for all stacks.
>=20
> If there is no reason/benefit/value/advantage to use source=20
> port 9899, then please remove the text from the I-D.  This
> follows the dictum that a standard is finished when everything
> unnecessary has been removed and it still works.=20
I agree with this statement. However, I think there is some value:

sctp.fh-muenster.de runs a stack with UDP encapsulation with a public =
address.
So I can reach that machine from home (behind a NAT) without any =
negotiation by
assuming/hoping that it uses 9989. Also multiple  local boxes (behind a =
NAT)
each use 9989 as the local bound port. But the point here is that I'm =
only running one
stack per host.

If we remove the above sentence, I have no idea which port to try and
can only use UDP encapsulation in combination with some other protocol
giving me the port number.

Would you find the following be acceptable for you:

<t>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.
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) and the IANA assigned value of 9989 MAY
be used as this port number.
However, this is not possible if the SCTP stack is implemented as
part of an application.</t>

This only mentions 9989 in case of running a single stack...

So do you see any value in my above usage scenario?

Sorry for insisting on this... I do see some value and would like to
understand what I'm misunderstanding...

Best regards
Michael
>=20
>> 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.
>>=20
>> 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.
>>=20
>> 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.
>=20
> -d
>=20
>> Best regards
>> Michael
>>>=20
>>> -d
>>>=20
>>>=20
>>>> Best regards
>>>> Michael
>>>>>=20
>>>>> -d
>>>>>=20
>>>>>=20
>>>>>>=20
>>>>>> Best regards
>>>>>> Michael
>>>>>>>=20
>>>>>>> -d
>>>>>>>=20
>>>>>>>> Best regards
>>>>>>>> Michael
>>>>>>>>>=20
>>>>>>>>> -d
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>> Best regards
>>>>>>>>>> Michael
>>>>>>>>>>>=20
>>>>>>>>>>> -d
>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>>>> Best regards
>>>>>>>>>>>> Michael
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> -d
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>=20
>>>>>=20
>>>=20
>>>=20
>=20
>=20


From tuexen@fh-muenster.de  Sun Dec  4 03:24: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 A7ED821F8876 for <tsvwg@ietfa.amsl.com>; Sun,  4 Dec 2011 03:24:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level: 
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[AWL=0.163,  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 NI4w8+KfWVbL for <tsvwg@ietfa.amsl.com>; Sun,  4 Dec 2011 03:24:04 -0800 (PST)
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 6072D21F86A4 for <tsvwg@ietf.org>; Sun,  4 Dec 2011 03:24:03 -0800 (PST)
Received: from [192.168.1.200] (p508FBF8C.dip.t-dialin.net [80.143.191.140]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 397A61C0C0BD8; Sun,  4 Dec 2011 12:23:46 +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: <CB010BF8.83D6%hannes.tschofenig@nsn.com>
Date: Sun, 4 Dec 2011 12:23:44 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <DED3E0A2-2775-4876-AB9E-771413061BE1@fh-muenster.de>
References: <CB010BF8.83D6%hannes.tschofenig@nsn.com>
To: Hannes Tschofenig <hannes.tschofenig@nsn.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: tsvwg@ietf.org, Dan Wing <dwing@cisco.com>, 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: Sun, 04 Dec 2011 11:24:04 -0000

On Dec 4, 2011, at 10:37 AM, Hannes Tschofenig wrote:

> I agree with Dan. Using a fixed source port does not appear to be useful.
I'm not suggesting a fixed port. I'm only suggesting that when the stack
(possibly under the assumption that there is only one on the host, i. e.
a kernel based) binds a UDP socket, it MAY use 9989.

Best regards
Michael
> 
> 
> On 12/3/11 8:41 AM, "Dan Wing" <dwing@cisco.com> wrote:
> 
>>> -----Original Message-----
>>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>>> Sent: Wednesday, November 02, 2011 4:35 AM
>>> To: Dan Wing
>>> Cc: tsvwg@ietf.org; randall@lakerest.net
>>> Subject: Re: SCTP-over-UDP and port 9899
>>> 
>>> 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...
>> 
>> Probably just a terminology disagreement.  To my mind, everything
>> is client/server, based on who sends the first packet (the client)
>> and who receives the first packet (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.
>>> I'm not sure why you are concerned.
>> 
>> Because I don't understand why the I-D insists on specifying
>> the source port (no other protocol does, that I'm aware of),
>> and it will cause problems when multiple SCTP-over-UDP
>> clients are running on the same host.  One of them will likely
>> be written to insist, strongly, that it get port 9899.
>> 
>> If there is no reason/benefit/value/advantage to use source
>> port 9899, then please remove the text from the I-D.  This
>> follows the dictum that a standard is finished when everything
>> unnecessary has been removed and it still works.
>> 
>>> 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.
>> 
>> -d
>> 
>>> 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 randall@lakerest.net  Sun Dec  4 08:03:56 2011
Return-Path: <randall@lakerest.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 0438121F8538 for <tsvwg@ietfa.amsl.com>; Sun,  4 Dec 2011 08:03:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n33y1i8fQRZq for <tsvwg@ietfa.amsl.com>; Sun,  4 Dec 2011 08:03:55 -0800 (PST)
Received: from lakerest.net (lakerest.net [70.155.160.98]) by ietfa.amsl.com (Postfix) with ESMTP id E08A321F84D5 for <tsvwg@ietf.org>; Sun,  4 Dec 2011 08:03:54 -0800 (PST)
Received: from [10.1.1.141] (bsd3.lakerest.net [70.155.160.101]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id pB4G2LHd087641 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 4 Dec 2011 11:02:21 -0500 (EST) (envelope-from randall@lakerest.net)
Subject: Re: SCTP-over-UDP and port 9899
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=windows-1252
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <DED3E0A2-2775-4876-AB9E-771413061BE1@fh-muenster.de>
Date: Sun, 4 Dec 2011 11:02:23 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2460FAF-EA78-4AC7-8025-B57E4A80F7C9@lakerest.net>
References: <CB010BF8.83D6%hannes.tschofenig@nsn.com> <DED3E0A2-2775-4876-AB9E-771413061BE1@fh-muenster.de>
To: Michael Tuexen <tuexen@fh-muenster.de>
X-Mailer: Apple Mail (2.1251.1)
Cc: tsvwg@ietf.org, Dan Wing <dwing@cisco.com>
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: Sun, 04 Dec 2011 16:03:56 -0000

I agree with Michael here. Having the port assigned by IANA as a MAY
is only a weak reference. It does *not* restrict anyone from using any
port. His argument is sound, in the lack of any other knowledge  you =
should try
the IANA port.

I would imagine the http document *probably* mentions the IANA assigned =
port 80, not
saying you *must* use it=85 but mentioning it so that apps have a choice =
of port of
last resort so to speak.

I see no difference here.. and think the current wording makes sense=85

R
On Dec 4, 2011, at 6:23 AM, Michael Tuexen wrote:

> On Dec 4, 2011, at 10:37 AM, Hannes Tschofenig wrote:
>=20
>> I agree with Dan. Using a fixed source port does not appear to be =
useful.
> I'm not suggesting a fixed port. I'm only suggesting that when the =
stack
> (possibly under the assumption that there is only one on the host, i. =
e.
> a kernel based) binds a UDP socket, it MAY use 9989.
>=20
> Best regards
> Michael
>>=20
>>=20
>> On 12/3/11 8:41 AM, "Dan Wing" <dwing@cisco.com> wrote:
>>=20
>>>> -----Original Message-----
>>>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>>>> Sent: Wednesday, November 02, 2011 4:35 AM
>>>> To: Dan Wing
>>>> Cc: tsvwg@ietf.org; randall@lakerest.net
>>>> Subject: Re: SCTP-over-UDP and port 9899
>>>>=20
>>>> On Nov 2, 2011, at 3:27 AM, Dan Wing wrote:
>>>>=20
>>>>>>> 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...
>>>>>=20
>>>>> "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...
>>>=20
>>> Probably just a terminology disagreement.  To my mind, everything
>>> is client/server, based on who sends the first packet (the client)
>>> and who receives the first packet (server).
>>>=20
>>>=20
>>>>>>>> That is why I used a MAY. But I'm open to use any other
>>>> formulation.
>>>>>>>> Do you have a suggestion?
>>>>>>>=20
>>>>>>> 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).
>>>>>>=20
>>>>>> Would it be acceptable for you if I replace
>>>>>>=20
>>>>>> 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.
>>>>>>=20
>>>>>> by
>>>>>>=20
>>>>>> Each SCTP stack uses a single local UDP encapsulation port =
number.
>>>>>>=20
>>>>>> 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.
>>>>>=20
>>>>> 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.
>>>=20
>>> Because I don't understand why the I-D insists on specifying
>>> the source port (no other protocol does, that I'm aware of),
>>> and it will cause problems when multiple SCTP-over-UDP
>>> clients are running on the same host.  One of them will likely
>>> be written to insist, strongly, that it get port 9899.
>>>=20
>>> If there is no reason/benefit/value/advantage to use source
>>> port 9899, then please remove the text from the I-D.  This
>>> follows the dictum that a standard is finished when everything
>>> unnecessary has been removed and it still works.
>>>=20
>>>> 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.
>>>>=20
>>>> 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.
>>>>=20
>>>> 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.
>>>=20
>>> -d
>>>=20
>>>> Best regards
>>>> Michael
>>>>>=20
>>>>> -d
>>>>>=20
>>>>>=20
>>>>>> Best regards
>>>>>> Michael
>>>>>>>=20
>>>>>>> -d
>>>>>>>=20
>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Best regards
>>>>>>>> Michael
>>>>>>>>>=20
>>>>>>>>> -d
>>>>>>>>>=20
>>>>>>>>>> Best regards
>>>>>>>>>> Michael
>>>>>>>>>>>=20
>>>>>>>>>>> -d
>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>>>> Best regards
>>>>>>>>>>>> Michael
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> -d
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>> Michael
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> -d
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>=20
>>>>>=20
>>>=20
>>=20
>>=20
>=20

-----
Randall Stewart
randall@lakerest.net





From randall@lakerest.net  Sun Dec  4 08:25:47 2011
Return-Path: <randall@lakerest.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 D8D6721F8551 for <tsvwg@ietfa.amsl.com>; Sun,  4 Dec 2011 08:25:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wZmOY509CZOC for <tsvwg@ietfa.amsl.com>; Sun,  4 Dec 2011 08:25:47 -0800 (PST)
Received: from lakerest.net (lakerest.net [70.155.160.98]) by ietfa.amsl.com (Postfix) with ESMTP id C7F5A21F8549 for <tsvwg@ietf.org>; Sun,  4 Dec 2011 08:25:46 -0800 (PST)
Received: from [10.1.1.141] (bsd3.lakerest.net [70.155.160.101]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id pB4GOFrg087791 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 4 Dec 2011 11:24:15 -0500 (EST) (envelope-from randall@lakerest.net)
Subject: Re: SCTP-over-UDP and port 9899
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=windows-1252
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <F2460FAF-EA78-4AC7-8025-B57E4A80F7C9@lakerest.net>
Date: Sun, 4 Dec 2011 11:24:19 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E5A087C-A0E8-4024-AB39-18B0B9F212FB@lakerest.net>
References: <CB010BF8.83D6%hannes.tschofenig@nsn.com> <DED3E0A2-2775-4876-AB9E-771413061BE1@fh-muenster.de> <F2460FAF-EA78-4AC7-8025-B57E4A80F7C9@lakerest.net>
To: Randy Stewart <randall@lakerest.net>
X-Mailer: Apple Mail (2.1251.1)
Cc: Michael Tuexen <tuexen@fh-muenster.de>, tsvwg@ietf.org, Dan Wing <dwing@cisco.com>
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: Sun, 04 Dec 2011 16:25:48 -0000

one follow up here, when I say the current wording, I mean
whats in the current draft as put by Michael in this thread=85

R
On Dec 4, 2011, at 11:02 AM, Randy Stewart wrote:

> I agree with Michael here. Having the port assigned by IANA as a MAY
> is only a weak reference. It does *not* restrict anyone from using any
> port. His argument is sound, in the lack of any other knowledge  you =
should try
> the IANA port.
>=20
> I would imagine the http document *probably* mentions the IANA =
assigned port 80, not
> saying you *must* use it=85 but mentioning it so that apps have a =
choice of port of
> last resort so to speak.
>=20
> I see no difference here.. and think the current wording makes sense=85
>=20
> R
> On Dec 4, 2011, at 6:23 AM, Michael Tuexen wrote:
>=20
>> On Dec 4, 2011, at 10:37 AM, Hannes Tschofenig wrote:
>>=20
>>> I agree with Dan. Using a fixed source port does not appear to be =
useful.
>> I'm not suggesting a fixed port. I'm only suggesting that when the =
stack
>> (possibly under the assumption that there is only one on the host, i. =
e.
>> a kernel based) binds a UDP socket, it MAY use 9989.
>>=20
>> Best regards
>> Michael
>>>=20
>>>=20
>>> On 12/3/11 8:41 AM, "Dan Wing" <dwing@cisco.com> wrote:
>>>=20
>>>>> -----Original Message-----
>>>>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>>>>> Sent: Wednesday, November 02, 2011 4:35 AM
>>>>> To: Dan Wing
>>>>> Cc: tsvwg@ietf.org; randall@lakerest.net
>>>>> Subject: Re: SCTP-over-UDP and port 9899
>>>>>=20
>>>>> On Nov 2, 2011, at 3:27 AM, Dan Wing wrote:
>>>>>=20
>>>>>>>> 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...
>>>>>>=20
>>>>>> "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...
>>>>=20
>>>> Probably just a terminology disagreement.  To my mind, everything
>>>> is client/server, based on who sends the first packet (the client)
>>>> and who receives the first packet (server).
>>>>=20
>>>>=20
>>>>>>>>> That is why I used a MAY. But I'm open to use any other
>>>>> formulation.
>>>>>>>>> Do you have a suggestion?
>>>>>>>>=20
>>>>>>>> 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).
>>>>>>>=20
>>>>>>> Would it be acceptable for you if I replace
>>>>>>>=20
>>>>>>> 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.
>>>>>>>=20
>>>>>>> by
>>>>>>>=20
>>>>>>> Each SCTP stack uses a single local UDP encapsulation port =
number.
>>>>>>>=20
>>>>>>> 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.
>>>>>>=20
>>>>>> 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.
>>>>=20
>>>> Because I don't understand why the I-D insists on specifying
>>>> the source port (no other protocol does, that I'm aware of),
>>>> and it will cause problems when multiple SCTP-over-UDP
>>>> clients are running on the same host.  One of them will likely
>>>> be written to insist, strongly, that it get port 9899.
>>>>=20
>>>> If there is no reason/benefit/value/advantage to use source
>>>> port 9899, then please remove the text from the I-D.  This
>>>> follows the dictum that a standard is finished when everything
>>>> unnecessary has been removed and it still works.
>>>>=20
>>>>> 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.
>>>>>=20
>>>>> 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.
>>>>>=20
>>>>> 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.
>>>>=20
>>>> -d
>>>>=20
>>>>> Best regards
>>>>> Michael
>>>>>>=20
>>>>>> -d
>>>>>>=20
>>>>>>=20
>>>>>>> Best regards
>>>>>>> Michael
>>>>>>>>=20
>>>>>>>> -d
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> Best regards
>>>>>>>>> Michael
>>>>>>>>>>=20
>>>>>>>>>> -d
>>>>>>>>>>=20
>>>>>>>>>>> Best regards
>>>>>>>>>>> Michael
>>>>>>>>>>>>=20
>>>>>>>>>>>> -d
>>>>>>>>>>>>=20
>>>>>>>>>>>>=20
>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>> Michael
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> -d
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>>> Michael
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> -d
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>=20
>>>>>>>>>>>>=20
>>>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>=20
>>>=20
>>>=20
>>=20
>=20
> -----
> Randall Stewart
> randall@lakerest.net
>=20
>=20
>=20
>=20
>=20

-----
Randall Stewart
randall@lakerest.net





From bidulock@openss7.org  Sun Dec  4 15:16:54 2011
Return-Path: <bidulock@openss7.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 9DB6521F8B36 for <tsvwg@ietfa.amsl.com>; Sun,  4 Dec 2011 15:16:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vV7lHyZSWE0C for <tsvwg@ietfa.amsl.com>; Sun,  4 Dec 2011 15:16:54 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [206.75.117.178]) by ietfa.amsl.com (Postfix) with ESMTP id E781021F8483 for <tsvwg@ietf.org>; Sun,  4 Dec 2011 15:16:53 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id pB4NG77S030864; Sun, 4 Dec 2011 16:16:07 -0700
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id pB4NG6tc028585; Sun, 4 Dec 2011 16:16:06 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id pB4NFwmg028548; Sun, 4 Dec 2011 16:15:58 -0700
Date: Sun, 4 Dec 2011 16:15:58 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Hannes Tschofenig <hannes.tschofenig@nsn.com>
Subject: Re: SCTP-over-UDP and port 9899
Message-ID: <20111204231558.GA26648@openss7.org>
Mail-Followup-To: Hannes Tschofenig <hannes.tschofenig@nsn.com>, Dan Wing <dwing@cisco.com>, 'Michael Tuexen' <tuexen@fh-muenster.de>, tsvwg@ietf.org, randall@lakerest.net
References: <018201ccb186$a10ed6a0$e32c83e0$@com> <CB010BF8.83D6%hannes.tschofenig@nsn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CB010BF8.83D6%hannes.tschofenig@nsn.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: 'Michael Tuexen' <tuexen@fh-muenster.de>, tsvwg@ietf.org, Dan Wing <dwing@cisco.com>, randall@lakerest.net
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: bidulock@openss7.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: Sun, 04 Dec 2011 23:16:54 -0000

+1

Hannes Tschofenig wrote:                                 (Sun, 04 Dec 2011 11:37:28)
> I agree with Dan. Using a fixed source port does not appear to be useful.
> 

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

From cbenson@adax.com  Tue Dec  6 12:39:58 2011
Return-Path: <cbenson@adax.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 0E01721F8BC3 for <tsvwg@ietfa.amsl.com>; Tue,  6 Dec 2011 12:39:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_12=0.6]
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 jNUW8Rk+sesc for <tsvwg@ietfa.amsl.com>; Tue,  6 Dec 2011 12:39:57 -0800 (PST)
Received: from mail1.adax.com (mail1.adax.com [70.36.226.176]) by ietfa.amsl.com (Postfix) with ESMTP id 0A27A21F8531 for <tsvwg@ietf.org>; Tue,  6 Dec 2011 12:39:56 -0800 (PST)
Received: from adax (adax [12.0.0.88]) by mail1.adax.com (Postfix) with ESMTP id 60D251E1133; Tue,  6 Dec 2011 12:39:56 -0800 (PST)
Received: by adax (Postfix, from userid 243) id A61358EE9E; Tue,  6 Dec 2011 12:39:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by adax (Postfix) with ESMTP id 9CB5D8EE9D; Tue,  6 Dec 2011 12:39:04 -0800 (PST)
Date: Tue, 6 Dec 2011 12:39:04 -0800 (PST)
From: Chris Benson <cbenson@adax.com>
X-X-Sender: cbenson@adax.adax
To: Michael Tuexen <tuexen@fh-muenster.de>
Subject: Re: SCTP-over-UDP and port 9899
In-Reply-To: <F2460FAF-EA78-4AC7-8025-B57E4A80F7C9@lakerest.net>
Message-ID: <Pine.LNX.4.64.1112061151450.4491@adax.adax>
References: <CB010BF8.83D6%hannes.tschofenig@nsn.com> <DED3E0A2-2775-4876-AB9E-771413061BE1@fh-muenster.de> <F2460FAF-EA78-4AC7-8025-B57E4A80F7C9@lakerest.net>
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="808960-1108703357-1323203944=:4491"
Cc: tsvwg@ietf.org, Dan Wing <dwing@cisco.com>, Randy Stewart <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, 06 Dec 2011 20:39:58 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--808960-1108703357-1323203944=:4491
Content-Type: TEXT/PLAIN; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

Hi folks,

I believe that Michael's statement regarding port number is=20
not restrictive, and contains a possibly useful suggestion=20
for a port number.

I think Michael's I-D is clearer for containing a suggestion
of using its own IANA assigned port number than it would be=20
without mentioning it.  To me it is clear that the specified
port number isn't REQUIRED, but is just a SUGGESTION.  It is
necessary to choose one local encapsulation port number=20
(assuming one local SCTP).  I'd be happy to use the IANA=20
assigned port 9989, because there possibly a better chance=20
that it will be available to me, and not already in use as
a fixed port number of some other unrelated protocol.

There are plenty of protocols with similar or analogous=20
statements, usually for recommended listener server port=20
selection, which is another way of saying that HTTP servers=20
SHOULD use port 80 as their source port etc.  M3UA, SUA, M2PA=20
etc. all specify [recommend] one "source port" for data sent
from the role of server.

It shouldn't cause too much grief, because as a suggestion=20
only, it can safely be ignored by any 9989-haters.

With thanks, from Chris.


On Sun, 4 Dec 2011, Randy Stewart wrote:

>>  Date: Sun, 4 Dec 2011 11:02:23 -0500
>>  From: Randy Stewart <randall@lakerest.net>
>>  To: Michael Tuexen <tuexen@fh-muenster.de>
>>  Cc:  <tsvwg@ietf.org>, Dan Wing <dwing@cisco.com>
>>  Subject: Re: SCTP-over-UDP and port 9899
>> =20
>>  I agree with Michael here. Having the port assigned by IANA as a MAY
>>  is only a weak reference. It does *not* restrict anyone from using any
>>  port. His argument is sound, in the lack of any other knowledge  you sh=
ould try
>>  the IANA port.
>> =20
>>  I would imagine the http document *probably* mentions the IANA assigned=
 port 80, not
>>  saying you *must* use it=E2=80=A6 but mentioning it so that apps have a=
 choice of port of
>>  last resort so to speak.
>> =20
>>  I see no difference here.. and think the current wording makes sense=E2=
=80=A6
>> =20
>>  R
>>  On Dec 4, 2011, at 6:23 AM, Michael Tuexen wrote:
>> =20
>>  > On Dec 4, 2011, at 10:37 AM, Hannes Tschofenig wrote:
>>  >=20
>>  >> I agree with Dan. Using a fixed source port does not appear to be us=
eful.
>>  > I'm not suggesting a fixed port. I'm only suggesting that when the st=
ack
>>  > (possibly under the assumption that there is only one on the host, i.=
 e.
>>  > a kernel based) binds a UDP socket, it MAY use 9989.
>>  >=20
>>  > Best regards
>>  > Michael
>>  >>=20
>>  >>=20
>>  >> On 12/3/11 8:41 AM, "Dan Wing" <dwing@cisco.com> wrote:
>>  >>=20
>>  >>>> -----Original Message-----
>>  >>>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>>  >>>> Sent: Wednesday, November 02, 2011 4:35 AM
>>  >>>> To: Dan Wing
>>  >>>> Cc: tsvwg@ietf.org; randall@lakerest.net
>>  >>>> Subject: Re: SCTP-over-UDP and port 9899
>>  >>>>=20
>>  >>>> On Nov 2, 2011, at 3:27 AM, Dan Wing wrote:
>>  >>>>=20
>>  >>>>>>> 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...
>>  >>>>>=20
>>  >>>>> "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...
>>  >>>=20
>>  >>> Probably just a terminology disagreement.  To my mind, everything
>>  >>> is client/server, based on who sends the first packet (the client)
>>  >>> and who receives the first packet (server).
>>  >>>=20
>>  >>>=20
>>  >>>>>>>> That is why I used a MAY. But I'm open to use any other
>>  >>>> formulation.
>>  >>>>>>>> Do you have a suggestion?
>>  >>>>>>>=20
>>  >>>>>>> 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).
>>  >>>>>>=20
>>  >>>>>> Would it be acceptable for you if I replace
>>  >>>>>>=20
>>  >>>>>> Each SCTP stack uses a single local UDP encapsulation port numbe=
r
>>  >>>>>> as the source port for all of its outgoing SCTP packets
>>  >>>>>> and as the destination port for all its incoming SCTP packets.
>>  >>>>>>=20
>>  >>>>>> by
>>  >>>>>>=20
>>  >>>>>> Each SCTP stack uses a single local UDP encapsulation port numbe=
r.
>>  >>>>>>=20
>>  >>>>>> 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.
>>  >>>>>=20
>>  >>>>> 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.
>>  >>>=20
>>  >>> Because I don't understand why the I-D insists on specifying
>>  >>> the source port (no other protocol does, that I'm aware of),
>>  >>> and it will cause problems when multiple SCTP-over-UDP
>>  >>> clients are running on the same host.  One of them will likely
>>  >>> be written to insist, strongly, that it get port 9899.
>>  >>>=20
>>  >>> If there is no reason/benefit/value/advantage to use source
>>  >>> port 9899, then please remove the text from the I-D.  This
>>  >>> follows the dictum that a standard is finished when everything
>>  >>> unnecessary has been removed and it still works.
>>  >>>=20
>>  >>>> The ID says: Use 9899 when possible as the local encapsulation
>>  >>>> port (I'm using MAY). For outgoing packets this local encapsulatio=
n
>>  >>>> 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.
>>  >>>>=20
>>  >>>> 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.
>>  >>>>=20
>>  >>>> 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.
>>  >>>=20
>>  >>> -d
>>  >>>=20
>>  >>>> Best regards
>>  >>>> Michael
>>  >>>>>=20
>>  >>>>> -d
>>  >>>>>=20
>>  >>>>>=20
>>  >>>>>> Best regards
>>  >>>>>> Michael
>>  >>>>>>>=20
>>  >>>>>>> -d
>>  >>>>>>>=20
>>  >>>>>>>=20
>>  >>>>>>>>=20
>>  >>>>>>>> Best regards
>>  >>>>>>>> Michael
>>  >>>>>>>>>=20
>>  >>>>>>>>> -d
>>  >>>>>>>>>=20
>>  >>>>>>>>>> Best regards
>>  >>>>>>>>>> Michael
>>  >>>>>>>>>>>=20
>>  >>>>>>>>>>> -d
>>  >>>>>>>>>>>=20
>>  >>>>>>>>>>>=20
>>  >>>>>>>>>>>> Best regards
>>  >>>>>>>>>>>> Michael
>>  >>>>>>>>>>>>>=20
>>  >>>>>>>>>>>>> -d
>>  >>>>>>>>>>>>>=20
>>  >>>>>>>>>>>>>=20
>>  >>>>>>>>>>>>>> Best regards
>>  >>>>>>>>>>>>>> Michael
>>  >>>>>>>>>>>>>>=20
>>  >>>>>>>>>>>>>> -d
>>  >>>>>>>>>>>>>>=20
>>  >>>>>>>>>>>>>>=20
>>  >>>>>>>>>>>>>>=20
>>  >>>>>>>>>>>>>=20
>>  >>>>>>>>>>>>>=20
>>  >>>>>>>>>>>=20
>>  >>>>>>>>>>>=20
>>  >>>>>>>>>=20
>>  >>>>>>>>>=20
>>  >>>>>>>=20
>>  >>>>>>>=20
>>  >>>>>=20
>>  >>>>>=20
>>  >>>=20
>>  >>=20
>>  >>=20
>>  >=20
>> =20
>>  -----
>>  Randall Stewart
>>  randall@lakerest.net
>> =20
>> =20
>> =20
>> =20
--808960-1108703357-1323203944=:4491--

From dwing@cisco.com  Tue Dec  6 15:11:02 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 7F05921F8B6D for <tsvwg@ietfa.amsl.com>; Tue,  6 Dec 2011 15:11:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, 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 E0kh-wKLOTb7 for <tsvwg@ietfa.amsl.com>; Tue,  6 Dec 2011 15:10:57 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 3BD4121F8B68 for <tsvwg@ietf.org>; Tue,  6 Dec 2011 15:10:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=10002; q=dns/txt; s=iport; t=1323213057; x=1324422657; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=+/A34cu7tF/uGXlcTriChlKN2UTtFGrYi26nB1EmIrY=; b=MAhGR9BhZvWloPfVUGiVKRD3DnqNwfL6lWl7/+HUwYR3AkU9l5/TVvcm i0idnYW2GeztH/uif8Jws/iu5EL//ijBRmnlrpEYZov0pzWTkl/jRuS0N SuyAHdIuzvwWsoE+Kz16hCdEh9pYmdyEQtJlBTzZJEn4XOPrv0+Gn+XF5 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmYAAOig3k6rRDoG/2dsb2JhbABDhQaVGIFqjlaBBYFyAQEBAwEICgEQB08FBwEDAgkOAQIDAQEBAQICIwMCAhkjCgkIAQEEARILF4dllysBjFuRcoEyiGqBFgSILoREKAGaDA
X-IronPort-AV: E=Sophos;i="4.71,309,1320624000"; d="scan'208";a="16404560"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 06 Dec 2011 23:10:40 +0000
Received: from dwingWS ([10.32.240.195]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pB6NAe7P021938; Tue, 6 Dec 2011 23:10:40 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Chris Benson'" <cbenson@adax.com>, "'Michael Tuexen'" <tuexen@fh-muenster.de>
References: <CB010BF8.83D6%hannes.tschofenig@nsn.com> <DED3E0A2-2775-4876-AB9E-771413061BE1@fh-muenster.de> <F2460FAF-EA78-4AC7-8025-B57E4A80F7C9@lakerest.net> <Pine.LNX.4.64.1112061151450.4491@adax.adax>
In-Reply-To: <Pine.LNX.4.64.1112061151450.4491@adax.adax>
Subject: RE: SCTP-over-UDP and port 9899
Date: Tue, 6 Dec 2011 15:10:38 -0800
Message-ID: <013701ccb46c$462ccab0$d2866010$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acy0VzpKTnmrDI/HQJqEa/ZrcGaS3QAFDoiw
Content-Language: en-us
Cc: tsvwg@ietf.org, 'Randy Stewart' <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, 06 Dec 2011 23:11:02 -0000

> -----Original Message-----
> From: Chris Benson [mailto:cbenson@adax.com]
> Sent: Tuesday, December 06, 2011 12:39 PM
> To: Michael Tuexen
> Cc: tsvwg@ietf.org; Dan Wing; Randy Stewart
> Subject: Re: SCTP-over-UDP and port 9899
>=20
> Hi folks,
>=20
> I believe that Michael's statement regarding port number is
> not restrictive, and contains a possibly useful suggestion
> for a port number.
>=20
> I think Michael's I-D is clearer for containing a suggestion
> of using its own IANA assigned port number than it would be
> without mentioning it.  To me it is clear that the specified
> port number isn't REQUIRED, but is just a SUGGESTION.  It is
> necessary to choose one local encapsulation port number
> (assuming one local SCTP).=20

Maybe we are finally getting to the root of the problem.  I
hope so.

I will ask:  why is it necessary to have one local encapsulation
port number?

For example, why can't I use source port 5555 from my IPv4
interface and use source port 8888 from IPv6 interface?  What
breaks?

Afterall, a NAT44 or NAT64 (and 4rd, Dual-IVI, and SD-NAT,
and every other IPv4 address sharing technique on the table)
will rewrite whatever local UDP encapsulation port that is=20
chosen by the application developer, anyway. =20

> I'd be happy to use the IANA
> assigned port 9989, because there possibly a better chance
> that it will be available to me, and not already in use as
> a fixed port number of some other unrelated protocol.

An ephemeral, chosen by the operating system, will always
be free and available to be used.


> There are plenty of protocols with similar or analogous
> statements, usually for recommended listener server port
> selection, which is another way of saying that HTTP servers
> SHOULD use port 80 as their source port etc.=20

RFC1945, which I believe is the canonical and earliest=20
HTTP reference, only says:

   On the Internet, HTTP communication generally takes place over TCP/IP
   connections. The default port is TCP 80 [15], but other ports can be
   used.

It says nothing about the source port.=20

No HTTP browser, that I have ever encountered, uses a source
port of 80.  Can you cite one?


> M3UA, SUA, M2PA
> etc. all specify [recommend] one "source port" for data sent
> from the role of server.
>=20
> It shouldn't cause too much grief, because as a suggestion
> only, it can safely be ignored by any 9989-haters.

It's not that I hate 9989.  It's that I want to understand why
the document is making any sort of statement or recommendation
for the source port. =20

-d


> With thanks, from Chris.
>=20
>=20
> On Sun, 4 Dec 2011, Randy Stewart wrote:
>=20
> >>  Date: Sun, 4 Dec 2011 11:02:23 -0500
> >>  From: Randy Stewart <randall@lakerest.net>
> >>  To: Michael Tuexen <tuexen@fh-muenster.de>
> >>  Cc:  <tsvwg@ietf.org>, Dan Wing <dwing@cisco.com>
> >>  Subject: Re: SCTP-over-UDP and port 9899
> >>
> >>  I agree with Michael here. Having the port assigned by IANA as a
> MAY
> >>  is only a weak reference. It does *not* restrict anyone from using
> any
> >>  port. His argument is sound, in the lack of any other knowledge
> you should try
> >>  the IANA port.
> >>
> >>  I would imagine the http document *probably* mentions the IANA
> assigned port 80, not
> >>  saying you *must* use it=E2=80=A6 but mentioning it so that apps =
have a
> choice of port of
> >>  last resort so to speak.
> >>
> >>  I see no difference here.. and think the current wording makes
> sense=E2=80=A6
> >>
> >>  R
> >>  On Dec 4, 2011, at 6:23 AM, Michael Tuexen wrote:
> >>
> >>  > On Dec 4, 2011, at 10:37 AM, Hannes Tschofenig wrote:
> >>  >
> >>  >> I agree with Dan. Using a fixed source port does not appear to
> be useful.
> >>  > I'm not suggesting a fixed port. I'm only suggesting that when
> the stack
> >>  > (possibly under the assumption that there is only one on the
> host, i. e.
> >>  > a kernel based) binds a UDP socket, it MAY use 9989.
> >>  >
> >>  > Best regards
> >>  > Michael
> >>  >>
> >>  >>
> >>  >> On 12/3/11 8:41 AM, "Dan Wing" <dwing@cisco.com> wrote:
> >>  >>
> >>  >>>> -----Original Message-----
> >>  >>>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> >>  >>>> Sent: Wednesday, November 02, 2011 4:35 AM
> >>  >>>> To: Dan Wing
> >>  >>>> Cc: tsvwg@ietf.org; randall@lakerest.net
> >>  >>>> Subject: Re: SCTP-over-UDP and port 9899
> >>  >>>>
> >>  >>>> 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...
> >>  >>>
> >>  >>> Probably just a terminology disagreement.  To my mind,
> everything
> >>  >>> is client/server, based on who sends the first packet (the
> client)
> >>  >>> and who receives the first packet (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.
> >>  >>>> I'm not sure why you are concerned.
> >>  >>>
> >>  >>> Because I don't understand why the I-D insists on specifying
> >>  >>> the source port (no other protocol does, that I'm aware of),
> >>  >>> and it will cause problems when multiple SCTP-over-UDP
> >>  >>> clients are running on the same host.  One of them will likely
> >>  >>> be written to insist, strongly, that it get port 9899.
> >>  >>>
> >>  >>> If there is no reason/benefit/value/advantage to use source
> >>  >>> port 9899, then please remove the text from the I-D.  This
> >>  >>> follows the dictum that a standard is finished when everything
> >>  >>> unnecessary has been removed and it still works.
> >>  >>>
> >>  >>>> 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.
> >>  >>>
> >>  >>> -d
> >>  >>>
> >>  >>>> Best regards
> >>  >>>> Michael
> >>  >>>>>
> >>  >>>>> -d
> >>  >>>>>
> >>  >>>>>
> >>  >>>>>> Best regards
> >>  >>>>>> Michael
> >>  >>>>>>>
> >>  >>>>>>> -d
> >>  >>>>>>>
> >>  >>>>>>>
> >>  >>>>>>>>
> >>  >>>>>>>> Best regards
> >>  >>>>>>>> Michael
> >>  >>>>>>>>>
> >>  >>>>>>>>> -d
> >>  >>>>>>>>>
> >>  >>>>>>>>>> Best regards
> >>  >>>>>>>>>> Michael
> >>  >>>>>>>>>>>
> >>  >>>>>>>>>>> -d
> >>  >>>>>>>>>>>
> >>  >>>>>>>>>>>
> >>  >>>>>>>>>>>> Best regards
> >>  >>>>>>>>>>>> Michael
> >>  >>>>>>>>>>>>>
> >>  >>>>>>>>>>>>> -d
> >>  >>>>>>>>>>>>>
> >>  >>>>>>>>>>>>>
> >>  >>>>>>>>>>>>>> Best regards
> >>  >>>>>>>>>>>>>> Michael
> >>  >>>>>>>>>>>>>>
> >>  >>>>>>>>>>>>>> -d
> >>  >>>>>>>>>>>>>>
> >>  >>>>>>>>>>>>>>
> >>  >>>>>>>>>>>>>>
> >>  >>>>>>>>>>>>>
> >>  >>>>>>>>>>>>>
> >>  >>>>>>>>>>>
> >>  >>>>>>>>>>>
> >>  >>>>>>>>>
> >>  >>>>>>>>>
> >>  >>>>>>>
> >>  >>>>>>>
> >>  >>>>>
> >>  >>>>>
> >>  >>>
> >>  >>
> >>  >>
> >>  >
> >>
> >>  -----
> >>  Randall Stewart
> >>  randall@lakerest.net
> >>
> >>
> >>
> >>


From tuexen@fh-muenster.de  Wed Dec  7 01:35:19 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 0B49321F8770 for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 01:35:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_12=0.6]
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 slKnHLE2De20 for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 01:35:18 -0800 (PST)
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 7F2A621F85F1 for <tsvwg@ietf.org>; Wed,  7 Dec 2011 01:35:16 -0800 (PST)
Received: from [212.201.127.231] (unknown [212.201.127.231]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 53C831C0C0BD4; Wed,  7 Dec 2011 10:35:14 +0100 (CET)
Subject: Re: SCTP-over-UDP and port 9899
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=windows-1252
From: Michael Tuexen <tuexen@fh-muenster.de>
In-Reply-To: <013701ccb46c$462ccab0$d2866010$@com>
Date: Wed, 7 Dec 2011 10:35:13 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F14A81FF-D879-4B6E-A7B8-0E66300A0644@fh-muenster.de>
References: <CB010BF8.83D6%hannes.tschofenig@nsn.com> <DED3E0A2-2775-4876-AB9E-771413061BE1@fh-muenster.de> <F2460FAF-EA78-4AC7-8025-B57E4A80F7C9@lakerest.net> <Pine.LNX.4.64.1112061151450.4491@adax.adax> <013701ccb46c$462ccab0$d2866010$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: tsvwg@ietf.org, 'Randy Stewart' <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, 07 Dec 2011 09:35:19 -0000

On Dec 7, 2011, at 12:10 AM, Dan Wing wrote:

>> -----Original Message-----
>> From: Chris Benson [mailto:cbenson@adax.com]
>> Sent: Tuesday, December 06, 2011 12:39 PM
>> To: Michael Tuexen
>> Cc: tsvwg@ietf.org; Dan Wing; Randy Stewart
>> Subject: Re: SCTP-over-UDP and port 9899
>>=20
>> Hi folks,
>>=20
>> I believe that Michael's statement regarding port number is
>> not restrictive, and contains a possibly useful suggestion
>> for a port number.
>>=20
>> I think Michael's I-D is clearer for containing a suggestion
>> of using its own IANA assigned port number than it would be
>> without mentioning it.  To me it is clear that the specified
>> port number isn't REQUIRED, but is just a SUGGESTION.  It is
>> necessary to choose one local encapsulation port number
>> (assuming one local SCTP).=20
>=20
> Maybe we are finally getting to the root of the problem.  I
> hope so.
>=20
> I will ask:  why is it necessary to have one local encapsulation
> port number?
Interesting question.
>=20
> For example, why can't I use source port 5555 from my IPv4
> interface and use source port 8888 from IPv6 interface?  What
> breaks?
Nothing. We can do that. However, the sending stack must know which
local port to use. Basing this decision on IPv4/IPv6 works.
If you prefer, we can use a port per protocol family. That might
help if you use per protocol UDP sockets and does not make things
much more complex. I'm willing to include that in the next revision
if you like.
However, would you agree with it? Or do you have a local port
per association / per association/path in mind? That would be
much more complex to implement...
>=20
> Afterall, a NAT44 or NAT64 (and 4rd, Dual-IVI, and SD-NAT,
> and every other IPv4 address sharing technique on the table)
> will rewrite whatever local UDP encapsulation port that is=20
> chosen by the application developer, anyway. =20
And that is not a problem, even with one port per stack.
>=20
>> I'd be happy to use the IANA
>> assigned port 9989, because there possibly a better chance
>> that it will be available to me, and not already in use as
>> a fixed port number of some other unrelated protocol.
>=20
> An ephemeral, chosen by the operating system, will always
> be free and available to be used.
>=20
>=20
>> There are plenty of protocols with similar or analogous
>> statements, usually for recommended listener server port
>> selection, which is another way of saying that HTTP servers
>> SHOULD use port 80 as their source port etc.=20
>=20
> RFC1945, which I believe is the canonical and earliest=20
> HTTP reference, only says:
>=20
>   On the Internet, HTTP communication generally takes place over =
TCP/IP
>   connections. The default port is TCP 80 [15], but other ports can be
>   used.
>=20
> It says nothing about the source port.=20
True it does. It is about the source port of the server....
>=20
> No HTTP browser, that I have ever encountered, uses a source
> port of 80.  Can you cite one?
But would break anything if a browser would do it?
It wouldn't help, since the client is always initiating the
TCP communication. But for an SCTP you don't know which side
your application will be. So does it hurt?
>=20
>=20
>> M3UA, SUA, M2PA
>> etc. all specify [recommend] one "source port" for data sent
>> from the role of server.
>>=20
>> It shouldn't cause too much grief, because as a suggestion
>> only, it can safely be ignored by any 9989-haters.
>=20
> It's not that I hate 9989.  It's that I want to understand why
> the document is making any sort of statement or recommendation
> for the source port. =20
Let me phrase it differently (to avoid that the wording is a problem):

Currently the stack uses one UDP socket. The stack has to bind a local
port. Under the condition that the is only one stack per host, what
is bad to suggest to use 9989, but not require it?

Best regards
Michael
>=20
> -d
>=20
>=20
>> With thanks, from Chris.
>>=20
>>=20
>> On Sun, 4 Dec 2011, Randy Stewart wrote:
>>=20
>>>> Date: Sun, 4 Dec 2011 11:02:23 -0500
>>>> From: Randy Stewart <randall@lakerest.net>
>>>> To: Michael Tuexen <tuexen@fh-muenster.de>
>>>> Cc:  <tsvwg@ietf.org>, Dan Wing <dwing@cisco.com>
>>>> Subject: Re: SCTP-over-UDP and port 9899
>>>>=20
>>>> I agree with Michael here. Having the port assigned by IANA as a
>> MAY
>>>> is only a weak reference. It does *not* restrict anyone from using
>> any
>>>> port. His argument is sound, in the lack of any other knowledge
>> you should try
>>>> the IANA port.
>>>>=20
>>>> I would imagine the http document *probably* mentions the IANA
>> assigned port 80, not
>>>> saying you *must* use it=85 but mentioning it so that apps have a
>> choice of port of
>>>> last resort so to speak.
>>>>=20
>>>> I see no difference here.. and think the current wording makes
>> sense=85
>>>>=20
>>>> R
>>>> On Dec 4, 2011, at 6:23 AM, Michael Tuexen wrote:
>>>>=20
>>>>> On Dec 4, 2011, at 10:37 AM, Hannes Tschofenig wrote:
>>>>>=20
>>>>>> I agree with Dan. Using a fixed source port does not appear to
>> be useful.
>>>>> I'm not suggesting a fixed port. I'm only suggesting that when
>> the stack
>>>>> (possibly under the assumption that there is only one on the
>> host, i. e.
>>>>> a kernel based) binds a UDP socket, it MAY use 9989.
>>>>>=20
>>>>> Best regards
>>>>> Michael
>>>>>>=20
>>>>>>=20
>>>>>> On 12/3/11 8:41 AM, "Dan Wing" <dwing@cisco.com> wrote:
>>>>>>=20
>>>>>>>> -----Original Message-----
>>>>>>>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>>>>>>>> Sent: Wednesday, November 02, 2011 4:35 AM
>>>>>>>> To: Dan Wing
>>>>>>>> Cc: tsvwg@ietf.org; randall@lakerest.net
>>>>>>>> Subject: Re: SCTP-over-UDP and port 9899
>>>>>>>>=20
>>>>>>>> On Nov 2, 2011, at 3:27 AM, Dan Wing wrote:
>>>>>>>>=20
>>>>>>>>>>> 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...
>>>>>>>>>=20
>>>>>>>>> "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...
>>>>>>>=20
>>>>>>> Probably just a terminology disagreement.  To my mind,
>> everything
>>>>>>> is client/server, based on who sends the first packet (the
>> client)
>>>>>>> and who receives the first packet (server).
>>>>>>>=20
>>>>>>>=20
>>>>>>>>>>>> That is why I used a MAY. But I'm open to use any other
>>>>>>>> formulation.
>>>>>>>>>>>> Do you have a suggestion?
>>>>>>>>>>>=20
>>>>>>>>>>> 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).
>>>>>>>>>>=20
>>>>>>>>>> Would it be acceptable for you if I replace
>>>>>>>>>>=20
>>>>>>>>>> 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.
>>>>>>>>>>=20
>>>>>>>>>> by
>>>>>>>>>>=20
>>>>>>>>>> Each SCTP stack uses a single local UDP encapsulation port
>> number.
>>>>>>>>>>=20
>>>>>>>>>> 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.
>>>>>>>>>=20
>>>>>>>>> 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.
>>>>>>>=20
>>>>>>> Because I don't understand why the I-D insists on specifying
>>>>>>> the source port (no other protocol does, that I'm aware of),
>>>>>>> and it will cause problems when multiple SCTP-over-UDP
>>>>>>> clients are running on the same host.  One of them will likely
>>>>>>> be written to insist, strongly, that it get port 9899.
>>>>>>>=20
>>>>>>> If there is no reason/benefit/value/advantage to use source
>>>>>>> port 9899, then please remove the text from the I-D.  This
>>>>>>> follows the dictum that a standard is finished when everything
>>>>>>> unnecessary has been removed and it still works.
>>>>>>>=20
>>>>>>>> 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.
>>>>>>>>=20
>>>>>>>> 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.
>>>>>>>>=20
>>>>>>>> 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.
>>>>>>>=20
>>>>>>> -d
>>>>>>>=20
>>>>>>>> Best regards
>>>>>>>> Michael
>>>>>>>>>=20
>>>>>>>>> -d
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>> Best regards
>>>>>>>>>> Michael
>>>>>>>>>>>=20
>>>>>>>>>>> -d
>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>>>>=20
>>>>>>>>>>>> Best regards
>>>>>>>>>>>> Michael
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> -d
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>> Michael
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> -d
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>>>> Michael
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> -d
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>>>>>> Michael
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> -d
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>=20
>>>> -----
>>>> Randall Stewart
>>>> randall@lakerest.net
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>=20
>=20


From randall@lakerest.net  Wed Dec  7 02:56:20 2011
Return-Path: <randall@lakerest.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 3828321F8B02 for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 02:56:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_12=0.6]
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 MBibbs50gys9 for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 02:56:19 -0800 (PST)
Received: from lakerest.net (lakerest.net [70.155.160.98]) by ietfa.amsl.com (Postfix) with ESMTP id DEECA21F899F for <tsvwg@ietf.org>; Wed,  7 Dec 2011 02:56:18 -0800 (PST)
Received: from proxy.surfnet.iacbox ([62.218.228.7]) (authenticated bits=0) by lakerest.net (8.14.4/8.14.3) with ESMTP id pB7AsjsC016622 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 7 Dec 2011 05:54:47 -0500 (EST) (envelope-from randall@lakerest.net)
Subject: Re: SCTP-over-UDP and port 9899
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=windows-1252
From: Randy Stewart <randall@lakerest.net>
In-Reply-To: <013701ccb46c$462ccab0$d2866010$@com>
Date: Wed, 7 Dec 2011 05:54:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D2A9C70-21B5-448B-8EA5-185D94922EF9@lakerest.net>
References: <CB010BF8.83D6%hannes.tschofenig@nsn.com> <DED3E0A2-2775-4876-AB9E-771413061BE1@fh-muenster.de> <F2460FAF-EA78-4AC7-8025-B57E4A80F7C9@lakerest.net> <Pine.LNX.4.64.1112061151450.4491@adax.adax> <013701ccb46c$462ccab0$d2866010$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: 'Michael Tuexen' <tuexen@fh-muenster.de>, 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, 07 Dec 2011 10:56:20 -0000

Dan:

In-line=85

On Dec 6, 2011, at 6:10 PM, Dan Wing wrote:

>> -----Original Message-----
>> From: Chris Benson [mailto:cbenson@adax.com]
>> Sent: Tuesday, December 06, 2011 12:39 PM
>> To: Michael Tuexen
>> Cc: tsvwg@ietf.org; Dan Wing; Randy Stewart
>> Subject: Re: SCTP-over-UDP and port 9899
>>=20
>> Hi folks,
>>=20
>> I believe that Michael's statement regarding port number is
>> not restrictive, and contains a possibly useful suggestion
>> for a port number.
>>=20
>> I think Michael's I-D is clearer for containing a suggestion
>> of using its own IANA assigned port number than it would be
>> without mentioning it.  To me it is clear that the specified
>> port number isn't REQUIRED, but is just a SUGGESTION.  It is
>> necessary to choose one local encapsulation port number
>> (assuming one local SCTP).=20
>=20
> Maybe we are finally getting to the root of the problem.  I
> hope so.
>=20
> I will ask:  why is it necessary to have one local encapsulation
> port number?
>=20
> For example, why can't I use source port 5555 from my IPv4
> interface and use source port 8888 from IPv6 interface?  What
> breaks?
>=20
> Afterall, a NAT44 or NAT64 (and 4rd, Dual-IVI, and SD-NAT,
> and every other IPv4 address sharing technique on the table)
> will rewrite whatever local UDP encapsulation port that is=20
> chosen by the application developer, anyway. =20
>=20
>> I'd be happy to use the IANA
>> assigned port 9989, because there possibly a better chance
>> that it will be available to me, and not already in use as
>> a fixed port number of some other unrelated protocol.
>=20
> An ephemeral, chosen by the operating system, will always
> be free and available to be used.
>=20
>=20
>> There are plenty of protocols with similar or analogous
>> statements, usually for recommended listener server port
>> selection, which is another way of saying that HTTP servers
>> SHOULD use port 80 as their source port etc.=20
>=20
> RFC1945, which I believe is the canonical and earliest=20
> HTTP reference, only says:
>=20
>   On the Internet, HTTP communication generally takes place over =
TCP/IP
>   connections. The default port is TCP 80 [15], but other ports can be
>   used.
>=20
> It says nothing about the source port.=20
>=20
> No HTTP browser, that I have ever encountered, uses a source
> port of 80.  Can you cite one?
>=20


Dan, this seems the root of the problem for you. I.e. the document
suggests using this as a source port. I guess I have always thought
of it as a destination port=85. since you have to have the stack
listen on one port for incoming data. And once the stack receives
a packet from a peer on that port, it must reply using that same port
as the source right?

I don't know of any HTTP server that is listening on port 80 that does
not, after accepting the connection, send reply messages with a source
address of port 80.

Could a stack initiate outbound INIT's on various UDP ports, sure, but =
where
would it send to if it knew nothing else? the defined IANA port=85 =
unless the
user specified some other port.

Now the down side, if its a kernel stack, of using multiple ports would =
be of
course you are burning up UDP ports in conjunction with every SCTP =
port.. which makes
no sense. for an O/S stack you are going to pick one port and use it. It =
does not
have to be the IANA port, but 99.99% of implementations that are in the =
kernel *will* use
the IANA port by default I bet. Which means they create one and only one =
socket inside
the kernel and send and receive *all* in and outbound SCTP packets =
to/from that port.

I just don't see why you are so concerned over such loose wording in the =
document.=20

Michael wrote it was currently:

<t>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 assigned 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.</t>


in the document.=20

Would you be happier with the following?


<t>Each SCTP stack uses a single local UDP encapsulation port number
 as the destination port for all its incoming SCTP packets.
The IANA assigned 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.</t>


I think it boils down to the same thing.. since if its a single =
implementation
on a O/S its only going to have one port. I guess if you wanted to use =
up
UDP ports for no reason you could use different ports as well but that =
would
be rather silly IMO.

R


>=20
>> M3UA, SUA, M2PA
>> etc. all specify [recommend] one "source port" for data sent
>> from the role of server.
>>=20
>> It shouldn't cause too much grief, because as a suggestion
>> only, it can safely be ignored by any 9989-haters.
>=20
> It's not that I hate 9989.  It's that I want to understand why
> the document is making any sort of statement or recommendation
> for the source port. =20
>=20
> -d
>=20
>=20
>> With thanks, from Chris.
>>=20
>>=20
>> On Sun, 4 Dec 2011, Randy Stewart wrote:
>>=20
>>>> Date: Sun, 4 Dec 2011 11:02:23 -0500
>>>> From: Randy Stewart <randall@lakerest.net>
>>>> To: Michael Tuexen <tuexen@fh-muenster.de>
>>>> Cc:  <tsvwg@ietf.org>, Dan Wing <dwing@cisco.com>
>>>> Subject: Re: SCTP-over-UDP and port 9899
>>>>=20
>>>> I agree with Michael here. Having the port assigned by IANA as a
>> MAY
>>>> is only a weak reference. It does *not* restrict anyone from using
>> any
>>>> port. His argument is sound, in the lack of any other knowledge
>> you should try
>>>> the IANA port.
>>>>=20
>>>> I would imagine the http document *probably* mentions the IANA
>> assigned port 80, not
>>>> saying you *must* use it=85 but mentioning it so that apps have a
>> choice of port of
>>>> last resort so to speak.
>>>>=20
>>>> I see no difference here.. and think the current wording makes
>> sense=85
>>>>=20
>>>> R
>>>> On Dec 4, 2011, at 6:23 AM, Michael Tuexen wrote:
>>>>=20
>>>>> On Dec 4, 2011, at 10:37 AM, Hannes Tschofenig wrote:
>>>>>=20
>>>>>> I agree with Dan. Using a fixed source port does not appear to
>> be useful.
>>>>> I'm not suggesting a fixed port. I'm only suggesting that when
>> the stack
>>>>> (possibly under the assumption that there is only one on the
>> host, i. e.
>>>>> a kernel based) binds a UDP socket, it MAY use 9989.
>>>>>=20
>>>>> Best regards
>>>>> Michael
>>>>>>=20
>>>>>>=20
>>>>>> On 12/3/11 8:41 AM, "Dan Wing" <dwing@cisco.com> wrote:
>>>>>>=20
>>>>>>>> -----Original Message-----
>>>>>>>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>>>>>>>> Sent: Wednesday, November 02, 2011 4:35 AM
>>>>>>>> To: Dan Wing
>>>>>>>> Cc: tsvwg@ietf.org; randall@lakerest.net
>>>>>>>> Subject: Re: SCTP-over-UDP and port 9899
>>>>>>>>=20
>>>>>>>> On Nov 2, 2011, at 3:27 AM, Dan Wing wrote:
>>>>>>>>=20
>>>>>>>>>>> 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...
>>>>>>>>>=20
>>>>>>>>> "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...
>>>>>>>=20
>>>>>>> Probably just a terminology disagreement.  To my mind,
>> everything
>>>>>>> is client/server, based on who sends the first packet (the
>> client)
>>>>>>> and who receives the first packet (server).
>>>>>>>=20
>>>>>>>=20
>>>>>>>>>>>> That is why I used a MAY. But I'm open to use any other
>>>>>>>> formulation.
>>>>>>>>>>>> Do you have a suggestion?
>>>>>>>>>>>=20
>>>>>>>>>>> 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).
>>>>>>>>>>=20
>>>>>>>>>> Would it be acceptable for you if I replace
>>>>>>>>>>=20
>>>>>>>>>> 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.
>>>>>>>>>>=20
>>>>>>>>>> by
>>>>>>>>>>=20
>>>>>>>>>> Each SCTP stack uses a single local UDP encapsulation port
>> number.
>>>>>>>>>>=20
>>>>>>>>>> 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.
>>>>>>>>>=20
>>>>>>>>> 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.
>>>>>>>=20
>>>>>>> Because I don't understand why the I-D insists on specifying
>>>>>>> the source port (no other protocol does, that I'm aware of),
>>>>>>> and it will cause problems when multiple SCTP-over-UDP
>>>>>>> clients are running on the same host.  One of them will likely
>>>>>>> be written to insist, strongly, that it get port 9899.
>>>>>>>=20
>>>>>>> If there is no reason/benefit/value/advantage to use source
>>>>>>> port 9899, then please remove the text from the I-D.  This
>>>>>>> follows the dictum that a standard is finished when everything
>>>>>>> unnecessary has been removed and it still works.
>>>>>>>=20
>>>>>>>> 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.
>>>>>>>>=20
>>>>>>>> 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.
>>>>>>>>=20
>>>>>>>> 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.
>>>>>>>=20
>>>>>>> -d
>>>>>>>=20
>>>>>>>> Best regards
>>>>>>>> Michael
>>>>>>>>>=20
>>>>>>>>> -d
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>> Best regards
>>>>>>>>>> Michael
>>>>>>>>>>>=20
>>>>>>>>>>> -d
>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>>>>=20
>>>>>>>>>>>> Best regards
>>>>>>>>>>>> Michael
>>>>>>>>>>>>>=20
>>>>>>>>>>>>> -d
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>> Michael
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>> -d
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>>>> Michael
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>> -d
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>>>>>> Michael
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>> -d
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>>>=20
>>>>>>>>>>>>>=20
>>>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>=20
>>>> -----
>>>> Randall Stewart
>>>> randall@lakerest.net
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>=20
>=20

-----
Randall Stewart
randall@lakerest.net





From dwing@cisco.com  Wed Dec  7 11:55:11 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 498E611E80B0 for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 11:55:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.229
X-Spam-Level: 
X-Spam-Status: No, score=-106.229 tagged_above=-999 required=5 tests=[AWL=-0.230, BAYES_00=-2.599, J_CHICKENPOX_12=0.6, 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 HXWiZR9I++D5 for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 11:55:10 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 2309011E80A6 for <tsvwg@ietf.org>; Wed,  7 Dec 2011 11:55:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=14489; q=dns/txt; s=iport; t=1323287710; x=1324497310; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=6M9d5DYI3nyXdghejlZVsa5ILiKad3Uhc7pHL1f4X08=; b=BLa5I7SxrSX/NuEc0m2ftJOd+6xB6YJfNr6oD8NnyzDog38fL4xl3drE +yy4594DVg8rzgL/EwcZe9OVlAId7bUAb3Lj4QPVvfc7n8y1/6yKyR/fK i9L39gkswgnZlsa1O+8KWxpoNjRzOOCw8z/ZdC/bepIeSon4PYJO2Ru9p g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnIAAJPD306rRDoJ/2dsb2JhbABDmiOBao5IgQWBcgEBAQMBCAoBFxA/BQcBAwIJDgECAwEBAQEnBxkjCgkIAQEEEwsXh2WYSQGeLIs0BIguhEYoAZoS
X-IronPort-AV: E=Sophos;i="4.71,315,1320624000"; d="scan'208";a="16585318"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 07 Dec 2011 19:55:08 +0000
Received: from dwingWS ([10.154.160.138]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pB7Jt8fA024951; Wed, 7 Dec 2011 19:55:08 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Randy Stewart'" <randall@lakerest.net>
References: <CB010BF8.83D6%hannes.tschofenig@nsn.com> <DED3E0A2-2775-4876-AB9E-771413061BE1@fh-muenster.de> <F2460FAF-EA78-4AC7-8025-B57E4A80F7C9@lakerest.net> <Pine.LNX.4.64.1112061151450.4491@adax.adax> <013701ccb46c$462ccab0$d2866010$@com> <5D2A9C70-21B5-448B-8EA5-185D94922EF9@lakerest.net>
In-Reply-To: <5D2A9C70-21B5-448B-8EA5-185D94922EF9@lakerest.net>
Subject: RE: SCTP-over-UDP and port 9899
Date: Wed, 7 Dec 2011 11:55:08 -0800
Message-ID: <048901ccb51a$1f79b9b0$5e6d2d10$@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: Acy0zqpHBJ1f9Z6IQL6PUiXMk32dggASrr0g
Content-Language: en-us
Cc: 'Michael Tuexen' <tuexen@fh-muenster.de>, 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, 07 Dec 2011 19:55:11 -0000

> -----Original Message-----
> From: Randy Stewart [mailto:randall@lakerest.net]
> Sent: Wednesday, December 07, 2011 2:55 AM
> To: Dan Wing
> Cc: 'Chris Benson'; 'Michael Tuexen'; tsvwg@ietf.org
> Subject: Re: SCTP-over-UDP and port 9899
> 
> Dan:
> 
> In-line.
> 
> On Dec 6, 2011, at 6:10 PM, Dan Wing wrote:
> 
> >> -----Original Message-----
> >> From: Chris Benson [mailto:cbenson@adax.com]
> >> Sent: Tuesday, December 06, 2011 12:39 PM
> >> To: Michael Tuexen
> >> Cc: tsvwg@ietf.org; Dan Wing; Randy Stewart
> >> Subject: Re: SCTP-over-UDP and port 9899
> >>
> >> Hi folks,
> >>
> >> I believe that Michael's statement regarding port number is
> >> not restrictive, and contains a possibly useful suggestion
> >> for a port number.
> >>
> >> I think Michael's I-D is clearer for containing a suggestion
> >> of using its own IANA assigned port number than it would be
> >> without mentioning it.  To me it is clear that the specified
> >> port number isn't REQUIRED, but is just a SUGGESTION.  It is
> >> necessary to choose one local encapsulation port number
> >> (assuming one local SCTP).
> >
> > Maybe we are finally getting to the root of the problem.  I
> > hope so.
> >
> > I will ask:  why is it necessary to have one local encapsulation
> > port number?
> >
> > For example, why can't I use source port 5555 from my IPv4
> > interface and use source port 8888 from IPv6 interface?  What
> > breaks?
> >
> > Afterall, a NAT44 or NAT64 (and 4rd, Dual-IVI, and SD-NAT,
> > and every other IPv4 address sharing technique on the table)
> > will rewrite whatever local UDP encapsulation port that is
> > chosen by the application developer, anyway.
> >
> >> I'd be happy to use the IANA
> >> assigned port 9989, because there possibly a better chance
> >> that it will be available to me, and not already in use as
> >> a fixed port number of some other unrelated protocol.
> >
> > An ephemeral, chosen by the operating system, will always
> > be free and available to be used.
> >
> >
> >> There are plenty of protocols with similar or analogous
> >> statements, usually for recommended listener server port
> >> selection, which is another way of saying that HTTP servers
> >> SHOULD use port 80 as their source port etc.
> >
> > RFC1945, which I believe is the canonical and earliest
> > HTTP reference, only says:
> >
> >   On the Internet, HTTP communication generally takes place over
> TCP/IP
> >   connections. The default port is TCP 80 [15], but other ports can
> be
> >   used.
> >
> > It says nothing about the source port.
> >
> > No HTTP browser, that I have ever encountered, uses a source
> > port of 80.  Can you cite one?
> >
> 
> 
> Dan, this seems the root of the problem for you. I.e. the document
> suggests using this as a source port. 

Yes, that is the root of the problem.

> I guess I have always thought
> of it as a destination port..  since you have to have the stack
> listen on one port for incoming data. And once the stack receives
> a packet from a peer on that port, it must reply using that same port
> as the source right?

Yes, it has to reply on the same port.  It cannot reply on the
source port 9899.  Or else things will break.  TFTP does that sort
of thing with its port 69, which doesn't work so hot for TFTP 
across a NAT.

I don't want the same kind of breakage with SCTP-over-UDP.  I
want SCTP-over-UDP to work across a NAT.


> I don't know of any HTTP server that is listening on port 80 that does
> not, after accepting the connection, send reply messages with a source
> address of port 80.

The I-D's current text does not make such a distinction.


> Could a stack initiate outbound INIT's on various UDP ports, sure, but
> where
> would it send to if it knew nothing else? the defined IANA port. unless
> the
> user specified some other port.
> 
> Now the down side, if its a kernel stack, of using multiple ports would
> be of
> course you are burning up UDP ports in conjunction with every SCTP
> port.. which makes
> no sense. for an O/S stack you are going to pick one port and use it.
> It does not
> have to be the IANA port, but 99.99% of implementations that are in the
> kernel *will* use
> the IANA port by default I bet. Which means they create one and only
> one socket inside
> the kernel and send and receive *all* in and outbound SCTP packets
> to/from that port.
> 
> I just don't see why you are so concerned over such loose wording in
> the document.

Because it has caused problems for NAT traversal with other protocols,
and I do not want it to cause problems for SCTP-over-UDP.


> Michael wrote it was currently:
> 
> <t>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 assigned 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.</t>
> 
> 
> in the document.
> 
> Would you be happier with the following?
> 
> 
> <t>Each SCTP stack uses a single local UDP encapsulation port number
>  as the destination port for all its incoming SCTP packets.
> The IANA assigned 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.</t>

That text looks great -- it removes any mention of the source
port, which has been my concern.  Thanks.

-d


> 
> I think it boils down to the same thing.. since if its a single
> implementation
> on a O/S its only going to have one port. I guess if you wanted to use
> up
> UDP ports for no reason you could use different ports as well but that
> would
> be rather silly IMO.
> 
> R
> 
> 
> >
> >> M3UA, SUA, M2PA
> >> etc. all specify [recommend] one "source port" for data sent
> >> from the role of server.
> >>
> >> It shouldn't cause too much grief, because as a suggestion
> >> only, it can safely be ignored by any 9989-haters.
> >
> > It's not that I hate 9989.  It's that I want to understand why
> > the document is making any sort of statement or recommendation
> > for the source port.
> >
> > -d
> >
> >
> >> With thanks, from Chris.
> >>
> >>
> >> On Sun, 4 Dec 2011, Randy Stewart wrote:
> >>
> >>>> Date: Sun, 4 Dec 2011 11:02:23 -0500
> >>>> From: Randy Stewart <randall@lakerest.net>
> >>>> To: Michael Tuexen <tuexen@fh-muenster.de>
> >>>> Cc:  <tsvwg@ietf.org>, Dan Wing <dwing@cisco.com>
> >>>> Subject: Re: SCTP-over-UDP and port 9899
> >>>>
> >>>> I agree with Michael here. Having the port assigned by IANA as a
> >> MAY
> >>>> is only a weak reference. It does *not* restrict anyone from using
> >> any
> >>>> port. His argument is sound, in the lack of any other knowledge
> >> you should try
> >>>> the IANA port.
> >>>>
> >>>> I would imagine the http document *probably* mentions the IANA
> >> assigned port 80, not
> >>>> saying you *must* use it. but mentioning it so that apps have a
> >> choice of port of
> >>>> last resort so to speak.
> >>>>
> >>>> I see no difference here.. and think the current wording makes
> >> sense.
> >>>>
> >>>> R
> >>>> On Dec 4, 2011, at 6:23 AM, Michael Tuexen wrote:
> >>>>
> >>>>> On Dec 4, 2011, at 10:37 AM, Hannes Tschofenig wrote:
> >>>>>
> >>>>>> I agree with Dan. Using a fixed source port does not appear to
> >> be useful.
> >>>>> I'm not suggesting a fixed port. I'm only suggesting that when
> >> the stack
> >>>>> (possibly under the assumption that there is only one on the
> >> host, i. e.
> >>>>> a kernel based) binds a UDP socket, it MAY use 9989.
> >>>>>
> >>>>> Best regards
> >>>>> Michael
> >>>>>>
> >>>>>>
> >>>>>> On 12/3/11 8:41 AM, "Dan Wing" <dwing@cisco.com> wrote:
> >>>>>>
> >>>>>>>> -----Original Message-----
> >>>>>>>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> >>>>>>>> Sent: Wednesday, November 02, 2011 4:35 AM
> >>>>>>>> To: Dan Wing
> >>>>>>>> Cc: tsvwg@ietf.org; randall@lakerest.net
> >>>>>>>> Subject: Re: SCTP-over-UDP and port 9899
> >>>>>>>>
> >>>>>>>> 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...
> >>>>>>>
> >>>>>>> Probably just a terminology disagreement.  To my mind,
> >> everything
> >>>>>>> is client/server, based on who sends the first packet (the
> >> client)
> >>>>>>> and who receives the first packet (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.
> >>>>>>>> I'm not sure why you are concerned.
> >>>>>>>
> >>>>>>> Because I don't understand why the I-D insists on specifying
> >>>>>>> the source port (no other protocol does, that I'm aware of),
> >>>>>>> and it will cause problems when multiple SCTP-over-UDP
> >>>>>>> clients are running on the same host.  One of them will likely
> >>>>>>> be written to insist, strongly, that it get port 9899.
> >>>>>>>
> >>>>>>> If there is no reason/benefit/value/advantage to use source
> >>>>>>> port 9899, then please remove the text from the I-D.  This
> >>>>>>> follows the dictum that a standard is finished when everything
> >>>>>>> unnecessary has been removed and it still works.
> >>>>>>>
> >>>>>>>> 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.
> >>>>>>>
> >>>>>>> -d
> >>>>>>>
> >>>>>>>> Best regards
> >>>>>>>> Michael
> >>>>>>>>>
> >>>>>>>>> -d
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> Best regards
> >>>>>>>>>> Michael
> >>>>>>>>>>>
> >>>>>>>>>>> -d
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Best regards
> >>>>>>>>>>>> Michael
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> -d
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> Best regards
> >>>>>>>>>>>>>> Michael
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> -d
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Best regards
> >>>>>>>>>>>>>>>> Michael
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> -d
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Best regards
> >>>>>>>>>>>>>>>>>> Michael
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> -d
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>> -----
> >>>> Randall Stewart
> >>>> randall@lakerest.net
> >>>>
> >>>>
> >>>>
> >>>>
> >
> >
> 
> -----
> Randall Stewart
> randall@lakerest.net
> 
> 



From tuexen@fh-muenster.de  Wed Dec  7 12:24:44 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 5A65F11E80D9 for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 12:24:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.148
X-Spam-Level: 
X-Spam-Status: No, score=-2.148 tagged_above=-999 required=5 tests=[AWL=-0.149, BAYES_00=-2.599, J_CHICKENPOX_12=0.6]
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 Cvf5vVPWJexb for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 12:24:43 -0800 (PST)
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 803FE11E80D3 for <tsvwg@ietf.org>; Wed,  7 Dec 2011 12:24:42 -0800 (PST)
Received: from [192.168.1.200] (p508FAD9B.dip.t-dialin.net [80.143.173.155]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 310F31C0C0BCC; Wed,  7 Dec 2011 21:24:40 +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: <048901ccb51a$1f79b9b0$5e6d2d10$@com>
Date: Wed, 7 Dec 2011 21:24:38 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <431E9126-67CB-47FF-8F7D-A3A312D9C018@fh-muenster.de>
References: <CB010BF8.83D6%hannes.tschofenig@nsn.com> <DED3E0A2-2775-4876-AB9E-771413061BE1@fh-muenster.de> <F2460FAF-EA78-4AC7-8025-B57E4A80F7C9@lakerest.net> <Pine.LNX.4.64.1112061151450.4491@adax.adax> <013701ccb46c$462ccab0$d2866010$@com> <5D2A9C70-21B5-448B-8EA5-185D94922EF9@lakerest.net> <048901ccb51a$1f79b9b0$5e6d2d10$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: tsvwg@ietf.org, 'Randy Stewart' <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, 07 Dec 2011 20:24:44 -0000

On Dec 7, 2011, at 8:55 PM, Dan Wing wrote:

>> -----Original Message-----
>> From: Randy Stewart [mailto:randall@lakerest.net]
>> Sent: Wednesday, December 07, 2011 2:55 AM
>> To: Dan Wing
>> Cc: 'Chris Benson'; 'Michael Tuexen'; tsvwg@ietf.org
>> Subject: Re: SCTP-over-UDP and port 9899
>> 
>> Dan:
>> 
>> In-line.
>> 
>> On Dec 6, 2011, at 6:10 PM, Dan Wing wrote:
>> 
>>>> -----Original Message-----
>>>> From: Chris Benson [mailto:cbenson@adax.com]
>>>> Sent: Tuesday, December 06, 2011 12:39 PM
>>>> To: Michael Tuexen
>>>> Cc: tsvwg@ietf.org; Dan Wing; Randy Stewart
>>>> Subject: Re: SCTP-over-UDP and port 9899
>>>> 
>>>> Hi folks,
>>>> 
>>>> I believe that Michael's statement regarding port number is
>>>> not restrictive, and contains a possibly useful suggestion
>>>> for a port number.
>>>> 
>>>> I think Michael's I-D is clearer for containing a suggestion
>>>> of using its own IANA assigned port number than it would be
>>>> without mentioning it.  To me it is clear that the specified
>>>> port number isn't REQUIRED, but is just a SUGGESTION.  It is
>>>> necessary to choose one local encapsulation port number
>>>> (assuming one local SCTP).
>>> 
>>> Maybe we are finally getting to the root of the problem.  I
>>> hope so.
>>> 
>>> I will ask:  why is it necessary to have one local encapsulation
>>> port number?
>>> 
>>> For example, why can't I use source port 5555 from my IPv4
>>> interface and use source port 8888 from IPv6 interface?  What
>>> breaks?
>>> 
>>> Afterall, a NAT44 or NAT64 (and 4rd, Dual-IVI, and SD-NAT,
>>> and every other IPv4 address sharing technique on the table)
>>> will rewrite whatever local UDP encapsulation port that is
>>> chosen by the application developer, anyway.
>>> 
>>>> I'd be happy to use the IANA
>>>> assigned port 9989, because there possibly a better chance
>>>> that it will be available to me, and not already in use as
>>>> a fixed port number of some other unrelated protocol.
>>> 
>>> An ephemeral, chosen by the operating system, will always
>>> be free and available to be used.
>>> 
>>> 
>>>> There are plenty of protocols with similar or analogous
>>>> statements, usually for recommended listener server port
>>>> selection, which is another way of saying that HTTP servers
>>>> SHOULD use port 80 as their source port etc.
>>> 
>>> RFC1945, which I believe is the canonical and earliest
>>> HTTP reference, only says:
>>> 
>>>  On the Internet, HTTP communication generally takes place over
>> TCP/IP
>>>  connections. The default port is TCP 80 [15], but other ports can
>> be
>>>  used.
>>> 
>>> It says nothing about the source port.
>>> 
>>> No HTTP browser, that I have ever encountered, uses a source
>>> port of 80.  Can you cite one?
>>> 
>> 
>> 
>> Dan, this seems the root of the problem for you. I.e. the document
>> suggests using this as a source port. 
> 
> Yes, that is the root of the problem.
> 
>> I guess I have always thought
>> of it as a destination port..  since you have to have the stack
>> listen on one port for incoming data. And once the stack receives
>> a packet from a peer on that port, it must reply using that same port
>> as the source right?
> 
> Yes, it has to reply on the same port.  It cannot reply on the
> source port 9899.  Or else things will break.  TFTP does that sort
> of thing with its port 69, which doesn't work so hot for TFTP 
> across a NAT.
> 
> I don't want the same kind of breakage with SCTP-over-UDP.  I
> want SCTP-over-UDP to work across a NAT.
> 
> 
>> I don't know of any HTTP server that is listening on port 80 that does
>> not, after accepting the connection, send reply messages with a source
>> address of port 80.
> 
> The I-D's current text does not make such a distinction.
> 
> 
>> Could a stack initiate outbound INIT's on various UDP ports, sure, but
>> where
>> would it send to if it knew nothing else? the defined IANA port. unless
>> the
>> user specified some other port.
>> 
>> Now the down side, if its a kernel stack, of using multiple ports would
>> be of
>> course you are burning up UDP ports in conjunction with every SCTP
>> port.. which makes
>> no sense. for an O/S stack you are going to pick one port and use it.
>> It does not
>> have to be the IANA port, but 99.99% of implementations that are in the
>> kernel *will* use
>> the IANA port by default I bet. Which means they create one and only
>> one socket inside
>> the kernel and send and receive *all* in and outbound SCTP packets
>> to/from that port.
>> 
>> I just don't see why you are so concerned over such loose wording in
>> the document.
> 
> Because it has caused problems for NAT traversal with other protocols,
> and I do not want it to cause problems for SCTP-over-UDP.
> 
> 
>> Michael wrote it was currently:
>> 
>> <t>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 assigned 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.</t>
>> 
>> 
>> in the document.
>> 
>> Would you be happier with the following?
>> 
>> 
>> <t>Each SCTP stack uses a single local UDP encapsulation port number
>> as the destination port for all its incoming SCTP packets.
>> The IANA assigned 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.</t>
> 
> That text looks great -- it removes any mention of the source
> port, which has been my concern.  Thanks.
Fine great, I'm happy with the text.
But it is clear to you that

the source port of outgoing packets is the same as the destination
port of incoming packets.

Or do you think that this is not true?

Best regards
Michael
> 
> -d
> 
> 
>> 
>> I think it boils down to the same thing.. since if its a single
>> implementation
>> on a O/S its only going to have one port. I guess if you wanted to use
>> up
>> UDP ports for no reason you could use different ports as well but that
>> would
>> be rather silly IMO.
>> 
>> R
>> 
>> 
>>> 
>>>> M3UA, SUA, M2PA
>>>> etc. all specify [recommend] one "source port" for data sent
>>>> from the role of server.
>>>> 
>>>> It shouldn't cause too much grief, because as a suggestion
>>>> only, it can safely be ignored by any 9989-haters.
>>> 
>>> It's not that I hate 9989.  It's that I want to understand why
>>> the document is making any sort of statement or recommendation
>>> for the source port.
>>> 
>>> -d
>>> 
>>> 
>>>> With thanks, from Chris.
>>>> 
>>>> 
>>>> On Sun, 4 Dec 2011, Randy Stewart wrote:
>>>> 
>>>>>> Date: Sun, 4 Dec 2011 11:02:23 -0500
>>>>>> From: Randy Stewart <randall@lakerest.net>
>>>>>> To: Michael Tuexen <tuexen@fh-muenster.de>
>>>>>> Cc:  <tsvwg@ietf.org>, Dan Wing <dwing@cisco.com>
>>>>>> Subject: Re: SCTP-over-UDP and port 9899
>>>>>> 
>>>>>> I agree with Michael here. Having the port assigned by IANA as a
>>>> MAY
>>>>>> is only a weak reference. It does *not* restrict anyone from using
>>>> any
>>>>>> port. His argument is sound, in the lack of any other knowledge
>>>> you should try
>>>>>> the IANA port.
>>>>>> 
>>>>>> I would imagine the http document *probably* mentions the IANA
>>>> assigned port 80, not
>>>>>> saying you *must* use it. but mentioning it so that apps have a
>>>> choice of port of
>>>>>> last resort so to speak.
>>>>>> 
>>>>>> I see no difference here.. and think the current wording makes
>>>> sense.
>>>>>> 
>>>>>> R
>>>>>> On Dec 4, 2011, at 6:23 AM, Michael Tuexen wrote:
>>>>>> 
>>>>>>> On Dec 4, 2011, at 10:37 AM, Hannes Tschofenig wrote:
>>>>>>> 
>>>>>>>> I agree with Dan. Using a fixed source port does not appear to
>>>> be useful.
>>>>>>> I'm not suggesting a fixed port. I'm only suggesting that when
>>>> the stack
>>>>>>> (possibly under the assumption that there is only one on the
>>>> host, i. e.
>>>>>>> a kernel based) binds a UDP socket, it MAY use 9989.
>>>>>>> 
>>>>>>> Best regards
>>>>>>> Michael
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On 12/3/11 8:41 AM, "Dan Wing" <dwing@cisco.com> wrote:
>>>>>>>> 
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>>>>>>>>>> Sent: Wednesday, November 02, 2011 4:35 AM
>>>>>>>>>> To: Dan Wing
>>>>>>>>>> Cc: tsvwg@ietf.org; randall@lakerest.net
>>>>>>>>>> Subject: Re: SCTP-over-UDP and port 9899
>>>>>>>>>> 
>>>>>>>>>> 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...
>>>>>>>>> 
>>>>>>>>> Probably just a terminology disagreement.  To my mind,
>>>> everything
>>>>>>>>> is client/server, based on who sends the first packet (the
>>>> client)
>>>>>>>>> and who receives the first packet (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.
>>>>>>>>>> I'm not sure why you are concerned.
>>>>>>>>> 
>>>>>>>>> Because I don't understand why the I-D insists on specifying
>>>>>>>>> the source port (no other protocol does, that I'm aware of),
>>>>>>>>> and it will cause problems when multiple SCTP-over-UDP
>>>>>>>>> clients are running on the same host.  One of them will likely
>>>>>>>>> be written to insist, strongly, that it get port 9899.
>>>>>>>>> 
>>>>>>>>> If there is no reason/benefit/value/advantage to use source
>>>>>>>>> port 9899, then please remove the text from the I-D.  This
>>>>>>>>> follows the dictum that a standard is finished when everything
>>>>>>>>> unnecessary has been removed and it still works.
>>>>>>>>> 
>>>>>>>>>> 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.
>>>>>>>>> 
>>>>>>>>> -d
>>>>>>>>> 
>>>>>>>>>> Best regards
>>>>>>>>>> Michael
>>>>>>>>>>> 
>>>>>>>>>>> -d
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>> Best regards
>>>>>>>>>>>> Michael
>>>>>>>>>>>>> 
>>>>>>>>>>>>> -d
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>> Michael
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> -d
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>>>> Michael
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> -d
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>>>>>> Michael
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> -d
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>>>>>>>>> Michael
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> -d
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> -----
>>>>>> Randall Stewart
>>>>>> randall@lakerest.net
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>> 
>>> 
>> 
>> -----
>> Randall Stewart
>> randall@lakerest.net
>> 
>> 
> 
> 
> 


From dwing@cisco.com  Wed Dec  7 12:35:02 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 DAE1611E80E8 for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 12:35:02 -0800 (PST)
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 2OcKpR8AsS+o for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 12:35:02 -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 5F7A211E80C0 for <tsvwg@ietf.org>; Wed,  7 Dec 2011 12:35:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=238; q=dns/txt; s=iport; t=1323290102; x=1324499702; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=oM6wGEDoRC+N+2+sqHH8I9o7HqvhWrJkaJ3UbcBn5Nc=; b=lqt61mZTIkoEatvePYTmJqsK/XmaKoRewWCweqBAZqHdliC96dlhGOHa RzIuq5LRCQ6M6uDkIzzvHNRiLwGTiHGTP+cOv/lZLsE9V5XC1VS7bQ9B9 BAlOlttsp+AJF8nqlenBL5SUtihTXS9rZ5WHPz2SQElatPYJC8lcDDGoH 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAKAF/N306rRDoI/2dsb2JhbABDnA2NKYEggQWBcgEBAQMBCAoBFxA/BQgDAgkPNxkjGwEBBB4Xh2WYSQGeKos0BIguhEYoAZoS
X-IronPort-AV: E=Sophos;i="4.71,315,1320624000"; d="scan'208";a="18358351"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 07 Dec 2011 20:35:02 +0000
Received: from dwingWS ([10.154.160.138]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pB7KZ2bL004209; Wed, 7 Dec 2011 20:35:02 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Michael Tuexen'" <tuexen@fh-muenster.de>
References: <CB010BF8.83D6%hannes.tschofenig@nsn.com> <DED3E0A2-2775-4876-AB9E-771413061BE1@fh-muenster.de> <F2460FAF-EA78-4AC7-8025-B57E4A80F7C9@lakerest.net> <Pine.LNX.4.64.1112061151450.4491@adax.adax> <013701ccb46c$462ccab0$d2866010$@com> <5D2A9C70-21B5-448B-8EA5-185D94922EF9@lakerest.net> <048901ccb51a$1f79b9b0$5e6d2d10$@com> <431E9126-67CB-47FF-8F7D-A3A312D9C018@fh-muenster.de>
In-Reply-To: <431E9126-67CB-47FF-8F7D-A3A312D9C018@fh-muenster.de>
Subject: RE: SCTP-over-UDP and port 9899
Date: Wed, 7 Dec 2011 12:35:02 -0800
Message-ID: <04ce01ccb51f$b200c3f0$16024bd0$@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: Acy1HkNSJsRX2xSQQEiKcoipYEfklAAAUP7g
Content-Language: en-us
Cc: tsvwg@ietf.org, 'Randy Stewart' <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, 07 Dec 2011 20:35:03 -0000

> Fine great, I'm happy with the text.

Great.

> But it is clear to you that
> 
> the source port of outgoing packets is the same as the destination
> port of incoming packets.
> 
> Or do you think that this is not true?

-d



From tuexen@fh-muenster.de  Wed Dec  7 12:48: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 E602A21F8A55 for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 12:48:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[AWL=0.161,  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 XQ5A8I4yll11 for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 12:48:27 -0800 (PST)
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 4338821F8876 for <tsvwg@ietf.org>; Wed,  7 Dec 2011 12:48:27 -0800 (PST)
Received: from [192.168.1.200] (p508FAD9B.dip.t-dialin.net [80.143.173.155]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id A93341C0B4610; Wed,  7 Dec 2011 21:48: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: <04ce01ccb51f$b200c3f0$16024bd0$@com>
Date: Wed, 7 Dec 2011 21:48:24 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <1D4F18A7-AABF-4E39-951E-BC80DBBB45F5@fh-muenster.de>
References: <CB010BF8.83D6%hannes.tschofenig@nsn.com> <DED3E0A2-2775-4876-AB9E-771413061BE1@fh-muenster.de> <F2460FAF-EA78-4AC7-8025-B57E4A80F7C9@lakerest.net> <Pine.LNX.4.64.1112061151450.4491@adax.adax> <013701ccb46c$462ccab0$d2866010$@com> <5D2A9C70-21B5-448B-8EA5-185D94922EF9@lakerest.net> <048901ccb51a$1f79b9b0$5e6d2d10$@com> <431E9126-67CB-47FF-8F7D-A3A312D9C018@fh-muenster.de> <04ce01ccb51f$b200c3f0$16024bd0$@com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: tsvwg@ietf.org, 'Randy Stewart' <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, 07 Dec 2011 20:48:28 -0000

On Dec 7, 2011, at 9:35 PM, Dan Wing wrote:

>> Fine great, I'm happy with the text.
> 
> Great.
Is it acceptable for you that the SCTP stack uses only
a single UDP port or do you want a single port per
protocol family or even more ports?

Best regards
Michael
> 
>> But it is clear to you that
>> 
>> the source port of outgoing packets is the same as the destination
>> port of incoming packets.
>> 
>> Or do you think that this is not true?
> 
> -d
> 
> 
> 


From dwing@cisco.com  Wed Dec  7 13:10:14 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 D53CA21F8BCB for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 13:10:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.516
X-Spam-Level: 
X-Spam-Status: No, score=-106.516 tagged_above=-999 required=5 tests=[AWL=0.083, 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 adeVgy-bMDgn for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 13:10:13 -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 13CB221F8BCD for <tsvwg@ietf.org>; Wed,  7 Dec 2011 13:10:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=1512; q=dns/txt; s=iport; t=1323292213; x=1324501813; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=znVSCoNFbGlPmCP6uQp3Qi34sb8mQQUO2Zr1aRLNIxw=; b=IpLMl19qZm1rqJftMAgZX65es6pXMdPxL01A2Bcfc5rlyGRm2c0Ts/Ft qRCloIc07KB3qqnH3EhLt27Cpd/6M36rvjOhWkV1kbX5jU60RVvFjfeJs 3QLiS8M1EUsKjKVglac4oYO+eXWFWg0DiqpDwu0rKZvJBNke1YtN75e6F w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApYAAJLV306rRDoH/2dsb2JhbABDmiOBao5JgQWBcgEBAQMBCAoBFxA/BQcBAwIJDwIEAQEBJwcZIwoJCAEBBBMLF4dlmFIBnimLNASILoRGKAGaEg
X-IronPort-AV: E=Sophos;i="4.71,316,1320624000"; d="scan'208";a="18364167"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-4.cisco.com with ESMTP; 07 Dec 2011 21:10:13 +0000
Received: from dwingWS ([10.154.160.138]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pB7LACBQ015691; Wed, 7 Dec 2011 21:10:12 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Michael Tuexen'" <tuexen@fh-muenster.de>
References: <CB010BF8.83D6%hannes.tschofenig@nsn.com> <DED3E0A2-2775-4876-AB9E-771413061BE1@fh-muenster.de> <F2460FAF-EA78-4AC7-8025-B57E4A80F7C9@lakerest.net> <Pine.LNX.4.64.1112061151450.4491@adax.adax> <013701ccb46c$462ccab0$d2866010$@com> <5D2A9C70-21B5-448B-8EA5-185D94922EF9@lakerest.net> <048901ccb51a$1f79b9b0$5e6d2d10$@com> <431E9126-67CB-47FF-8F7D-A3A312D9C018@fh-muenster.de> <04ce01ccb51f$b200c3f0$16024bd0$@com> <1D4F18A7-AABF-4E39-951E-BC80DBBB45F5@fh-muenster.de>
In-Reply-To: <1D4F18A7-AABF-4E39-951E-BC80DBBB45F5@fh-muenster.de>
Subject: RE: SCTP-over-UDP and port 9899
Date: Wed, 7 Dec 2011 13:10:12 -0800
Message-ID: <04dc01ccb524$9c069930$d413cb90$@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: Acy1IZSv3yfBk8pNTxKBl+RwaGp+JwAAgoag
Content-Language: en-us
Cc: tsvwg@ietf.org, 'Randy Stewart' <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, 07 Dec 2011 21:10:14 -0000

> -----Original Message-----
> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> Sent: Wednesday, December 07, 2011 12:48 PM
> To: Dan Wing
> Cc: 'Randy Stewart'; 'Chris Benson'; tsvwg@ietf.org
> Subject: Re: SCTP-over-UDP and port 9899
> 
> On Dec 7, 2011, at 9:35 PM, Dan Wing wrote:
> 
> >> Fine great, I'm happy with the text.
> >
> > Great.
> Is it acceptable for you that the SCTP stack uses only
> a single UDP port or do you want a single port per
> protocol family or even more ports?

I assume you're asking because you're thinking of SCTP
running on those several interfaces.  With that in mind,
whatever port a SCTP-over-UDP is listening on is likely
to be rewritten by NAT (or other address sharing, e.g.,
dIVI, 4rd, etc.).  So, the SCTP-over-UDP clients cannot
require that a single SCTP-over-UDP server have the
same UDP port from the perspective of the SCTP-over-UDP
client.  Instead, the server's UDP port needs to be 
communicated to the SCTP-over-UDP client within SCTP 
itself using either (a) SCTP's existing AddAddress mechanism 
-- which would need to be extended to accomodate/know/learn 
of the UDP rewriting that occurred on that pathor some, or
(b) other means such as DNS SRV records.

-d


> Best regards
> Michael
> >
> >> But it is clear to you that
> >>
> >> the source port of outgoing packets is the same as the destination
> >> port of incoming packets.
> >>
> >> Or do you think that this is not true?
> >
> > -d
> >
> >
> >


From tuexen@fh-muenster.de  Wed Dec  7 13:25:05 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 F341A21F8C67 for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 13:25:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[AWL=0.151,  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 VnLFl9muDd9r for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 13:25:04 -0800 (PST)
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 2FF3A21F8C66 for <tsvwg@ietf.org>; Wed,  7 Dec 2011 13:25:04 -0800 (PST)
Received: from [192.168.1.200] (p508FAD9B.dip.t-dialin.net [80.143.173.155]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 172511C0C0BCC; Wed,  7 Dec 2011 22:25:03 +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: <04dc01ccb524$9c069930$d413cb90$@com>
Date: Wed, 7 Dec 2011 22:25:01 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <5F609D19-D0C0-4AC8-8EEA-FCEC095415D9@fh-muenster.de>
References: <CB010BF8.83D6%hannes.tschofenig@nsn.com> <DED3E0A2-2775-4876-AB9E-771413061BE1@fh-muenster.de> <F2460FAF-EA78-4AC7-8025-B57E4A80F7C9@lakerest.net> <Pine.LNX.4.64.1112061151450.4491@adax.adax> <013701ccb46c$462ccab0$d2866010$@com> <5D2A9C70-21B5-448B-8EA5-185D94922EF9@lakerest.net> <048901ccb51a$1f79b9b0$5e6d2d10$@com> <431E9126-67CB-47FF-8F7D-A3A312D9C018@fh-muenster.de> <04ce01ccb51f$b200c3f0$16024bd0$@com> <1D4F18A7-AABF-4E39-951E-BC80DBBB45F5@fh-muenster.de> <04dc01ccb524$9c069930$d413cb90$@com>
To: "Dan Wing" <dwing@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: tsvwg@ietf.org, 'Randy Stewart' <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, 07 Dec 2011 21:25:05 -0000

On Dec 7, 2011, at 10:10 PM, Dan Wing wrote:

>> -----Original Message-----
>> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
>> Sent: Wednesday, December 07, 2011 12:48 PM
>> To: Dan Wing
>> Cc: 'Randy Stewart'; 'Chris Benson'; tsvwg@ietf.org
>> Subject: Re: SCTP-over-UDP and port 9899
>> 
>> On Dec 7, 2011, at 9:35 PM, Dan Wing wrote:
>> 
>>>> Fine great, I'm happy with the text.
>>> 
>>> Great.
>> Is it acceptable for you that the SCTP stack uses only
>> a single UDP port or do you want a single port per
>> protocol family or even more ports?
> 
> I assume you're asking because you're thinking of SCTP
> running on those several interfaces.  With that in mind,
Well, I'm thinking about SCTP/UDP/IPv4 and SCTP/UDP/IPv6.
Do you have any other stack in mind? I think the ID only
talks about these two above stacks.
> whatever port a SCTP-over-UDP is listening on is likely
> to be rewritten by NAT (or other address sharing, e.g.,
> dIVI, 4rd, etc.).  So, the SCTP-over-UDP clients cannot
I don't care about any rewriting by NATs. This is already
covered by the ID. I'm thinking about how many UDP sockets
you expect an SCTP stack to use for en/decapsulation.
One socket dealing with IPv4 and IPv6? Then one port is enough.
One for IPv4 and another one for IPv6? Then you have
2 bind calls which might make is hard to bind the same
port number.
Currently on Mac OS X I bind both sockets (kernel sockets)
to the same port. If one binding fails I close the other one
and report an error.
> require that a single SCTP-over-UDP server have the
> same UDP port from the perspective of the SCTP-over-UDP
> client.  Instead, the server's UDP port needs to be 
> communicated to the SCTP-over-UDP client within SCTP 
> itself using either (a) SCTP's existing AddAddress mechanism 
> -- which would need to be extended to accomodate/know/learn 
> of the UDP rewriting that occurred on that pathor some, or
> (b) other means such as DNS SRV records.
Hmmm. I have the feeling that I'm missing something? How can you
put the UDP port number into the SCTP payload? The port numbers
might get rewritten by a NAT box and this wouldn't rewrite the
SCTP payload. That is why the SCTP just uses as the destination
port of outgoing packets what the source port of incoming packets was.

Best regards
Michael
> 
> -d
> 
> 
>> Best regards
>> Michael
>>> 
>>>> But it is clear to you that
>>>> 
>>>> the source port of outgoing packets is the same as the destination
>>>> port of incoming packets.
>>>> 
>>>> Or do you think that this is not true?
>>> 
>>> -d
>>> 
>>> 
>>> 
> 
> 


From dwing@cisco.com  Wed Dec  7 15:40:10 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 9752011E808B for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 15:40:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.372
X-Spam-Level: 
X-Spam-Status: No, score=-105.372 tagged_above=-999 required=5 tests=[AWL=-1.073, BAYES_00=-2.599, MANGLED_CABLE=2.3, 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 r4+paYcDS6NM for <tsvwg@ietfa.amsl.com>; Wed,  7 Dec 2011 15:40:09 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id C619D21F86DD for <tsvwg@ietf.org>; Wed,  7 Dec 2011 15:40:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=3921; q=dns/txt; s=iport; t=1323301209; x=1324510809; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=lBTm4UmgxaQbpVHtj39GgZHcb3eqwTrKD3frHDj4EB0=; b=Aw3jw2Bk6ffF5RPtdVCJ9Hm0pIeHcA/ugz3XT6D/AkCvrelnabX4H5Vl 6I1lH4IAoDIm4DDruNvVdHBFW3N8N1ZPI+PwlZSZe2Q6cOT6wMvWTbPUV MDxEcnC+EdiicwqOnrymWzHBVrhlfJlEicHjqopRWV3qr9cxJqDnqiILF s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApYAAKz4306rRDoJ/2dsb2JhbABDmiOBao5JgQWBcgEBAQMBCAoBFxA/BQcBAwIJDwIEAQEBJwcZIwoJCAEBBBMLF4dlmEgBnieLNASILoRGKAGaEg
X-IronPort-AV: E=Sophos;i="4.71,316,1320624000"; d="scan'208";a="18338812"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 07 Dec 2011 23:40:09 +0000
Received: from dwingWS ([10.32.240.195]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pB7Ne99m018678; Wed, 7 Dec 2011 23:40:09 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Michael Tuexen'" <tuexen@fh-muenster.de>
References: <CB010BF8.83D6%hannes.tschofenig@nsn.com> <DED3E0A2-2775-4876-AB9E-771413061BE1@fh-muenster.de> <F2460FAF-EA78-4AC7-8025-B57E4A80F7C9@lakerest.net> <Pine.LNX.4.64.1112061151450.4491@adax.adax> <013701ccb46c$462ccab0$d2866010$@com> <5D2A9C70-21B5-448B-8EA5-185D94922EF9@lakerest.net> <048901ccb51a$1f79b9b0$5e6d2d10$@com> <431E9126-67CB-47FF-8F7D-A3A312D9C018@fh-muenster.de> <04ce01ccb51f$b200c3f0$16024bd0$@com> <1D4F18A7-AABF-4E39-951E-BC80DBBB45F5@fh-muenster.de> <04dc01ccb524$9c069930$d413cb90$@com> <5F609D19-D0C0-4AC8-8EEA-FCEC095415D9@fh-muenster.de>
In-Reply-To: <5F609D19-D0C0-4AC8-8EEA-FCEC095415D9@fh-muenster.de>
Subject: RE: SCTP-over-UDP and port 9899
Date: Wed, 7 Dec 2011 15:40:08 -0800
Message-ID: <05be01ccb539$8e672730$ab357590$@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: Acy1JrGatL7Eg2bwSD2REiuCTOeUqgAEHVqA
Content-Language: en-us
Cc: tsvwg@ietf.org, 'Randy Stewart' <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, 07 Dec 2011 23:40:10 -0000

> -----Original Message-----
> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> Sent: Wednesday, December 07, 2011 1:25 PM
> To: Dan Wing
> Cc: 'Randy Stewart'; 'Chris Benson'; tsvwg@ietf.org
> Subject: Re: SCTP-over-UDP and port 9899
> 
> 
> On Dec 7, 2011, at 10:10 PM, Dan Wing wrote:
> 
> >> -----Original Message-----
> >> From: Michael Tuexen [mailto:tuexen@fh-muenster.de]
> >> Sent: Wednesday, December 07, 2011 12:48 PM
> >> To: Dan Wing
> >> Cc: 'Randy Stewart'; 'Chris Benson'; tsvwg@ietf.org
> >> Subject: Re: SCTP-over-UDP and port 9899
> >>
> >> On Dec 7, 2011, at 9:35 PM, Dan Wing wrote:
> >>
> >>>> Fine great, I'm happy with the text.
> >>>
> >>> Great.
> >> Is it acceptable for you that the SCTP stack uses only
> >> a single UDP port or do you want a single port per
> >> protocol family or even more ports?
> >
> > I assume you're asking because you're thinking of SCTP
> > running on those several interfaces.  With that in mind,
> Well, I'm thinking about SCTP/UDP/IPv4 and SCTP/UDP/IPv6.
> Do you have any other stack in mind? I think the ID only
> talks about these two above stacks.
> > whatever port a SCTP-over-UDP is listening on is likely
> > to be rewritten by NAT (or other address sharing, e.g.,
> > dIVI, 4rd, etc.).  So, the SCTP-over-UDP clients cannot
> I don't care about any rewriting by NATs. This is already
> covered by the ID. I'm thinking about how many UDP sockets
> you expect an SCTP stack to use for en/decapsulation.
> One socket dealing with IPv4 and IPv6? Then one port is enough.

Yep, agreed.

> One for IPv4 and another one for IPv6? Then you have
> 2 bind calls which might make is hard to bind the same
> port number.
> Currently on Mac OS X I bind both sockets (kernel sockets)
> to the same port.

Ok.

> If one binding fails I close the other one
> and report an error.

That seems problematic.  What do you expect the caller to
do when it receives that error?  Give up and go home, or 
call you again?

> > require that a single SCTP-over-UDP server have the
> > same UDP port from the perspective of the SCTP-over-UDP
> > client.  Instead, the server's UDP port needs to be
> > communicated to the SCTP-over-UDP client within SCTP
> > itself using either (a) SCTP's existing AddAddress mechanism
> > -- which would need to be extended to accomodate/know/learn
> > of the UDP rewriting that occurred on that pathor some, or
> > (b) other means such as DNS SRV records.
> Hmmm. I have the feeling that I'm missing something?

What you have in the I-D (with the text change Randall suggested)
will work fine when the SCTP-over-UDP server has a publicly-
routed IP address and lovely things like that.

If, in the future, we have SCTP-over-UDP servers that are
behind their own NAT, things get more complicated.  I am
thinking of this complication, and thinking of ways to solve
it.  It's something we don't necessarily need to write down
yet, and certainly don't need to fix yet.  

But, we may.  It depends on if IPv4 really go away.

> How can you
> put the UDP port number into the SCTP payload?

That's a separate(able) problem.  Answers can include UPnP 
IGD, PCP, STUN, and other spiffy protocols for NAT traversal.

> The port numbers
> might get rewritten by a NAT box and this wouldn't rewrite the
> SCTP payload. That is why the SCTP just uses as the destination
> port of outgoing packets what the source port of incoming packets was.

Yeah, somewhere around 99% of transport protocols do that, too.

-d


> Best regards
> Michael
> >
> > -d
> >
> >
> >> Best regards
> >> Michael
> >>>
> >>>> But it is clear to you that
> >>>>
> >>>> the source port of outgoing packets is the same as the destination
> >>>> port of incoming packets.
> >>>>
> >>>> Or do you think that this is not true?
> >>>
> >>> -d
> >>>
> >>>
> >>>
> >
> >


From internet-drafts@ietf.org  Wed Dec  7 23:43:58 2011
Return-Path: <internet-drafts@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 2FF7911E809F; Wed,  7 Dec 2011 23:43:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, 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 vDSAJJwX3Tbg; Wed,  7 Dec 2011 23:43:52 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9565A11E8080; Wed,  7 Dec 2011 23:43:52 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-tsvwg-sctp-udp-encaps-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111208074352.13850.53178.idtracker@ietfa.amsl.com>
Date: Wed, 07 Dec 2011 23:43:52 -0800
Cc: 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: Thu, 08 Dec 2011 07:43:58 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Transport Area Working Group Working =
Group of the IETF.

	Title           : UDP Encapsulation of SCTP Packets
	Author(s)       : Michael Tuexen
                          Randall R. Stewart
	Filename        : draft-ietf-tsvwg-sctp-udp-encaps-02.txt
	Pages           : 10
	Date            : 2011-12-07

   This document describes a simple method of encapsulating SCTP Packets
   into UDP packets and its limitations.  This allows the usage of SCTP
   in networks with legacy NAT not supporting SCTP.  It can also be used
   to implement SCTP on hosts without directly accessing the IP-layer,
   for example implementing it as part of the application without
   requiring special privileges.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctp-udp-encaps-02.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-tsvwg-sctp-udp-encaps-02.txt


From Karen.Nielsen@tieto.com  Thu Dec  8 03:52:10 2011
Return-Path: <Karen.Nielsen@tieto.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 4525C21F87D6 for <tsvwg@ietfa.amsl.com>; Thu,  8 Dec 2011 03:52:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 HBFSb7-cQ9DT for <tsvwg@ietfa.amsl.com>; Thu,  8 Dec 2011 03:52:09 -0800 (PST)
Received: from ebb06.tieto.com (ebb06.tieto.com [131.207.168.38]) by ietfa.amsl.com (Postfix) with ESMTP id 6645B21F84BA for <tsvwg@ietf.org>; Thu,  8 Dec 2011 03:52:09 -0800 (PST)
X-AuditID: 83cfa826-b7b5bae000001ca6-89-4ee0a4e66830
Received: from FIHGA-EXHUB01.eu.tieto.com ( [131.207.136.34]) by ebb06.tieto.com (SMTP Mailer) with SMTP id F7.20.07334.6E4A0EE4; Thu,  8 Dec 2011 13:52:06 +0200 (EET)
Received: from EXMB03.eu.tieto.com ([169.254.1.127]) by FIHGA-EXHUB01.eu.tieto.com ([131.207.136.34]) with mapi; Thu, 8 Dec 2011 13:52:05 +0200
From: <Karen.Nielsen@tieto.com>
To: <nishida@sfc.wide.ad.jp>, <tsvwg@ietf.org>
Date: Thu, 8 Dec 2011 13:52:04 +0200
Subject: RE: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt
Thread-Topic: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt
Thread-Index: Acx0ScS6O/e5brZKRfezgpNBqPFrThBVWdDg
Message-ID: <CF340E42AED0874C81947E18863DE77B13340F715E@EXMB03.eu.tieto.com>
References: <20110916075854.4673.6360.idtracker@ietfa.amsl.com> <CABxaRLET3w_MhRtakjuA1Mc4sXd1-FpmorSgjK78K_6WjOX-Qg@mail.gmail.com>
In-Reply-To: <CABxaRLET3w_MhRtakjuA1Mc4sXd1-FpmorSgjK78K_6WjOX-Qg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
X-Mailman-Approved-At: Thu, 08 Dec 2011 12:12:27 -0800
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, 08 Dec 2011 11:52:10 -0000

Hi,

One additional comment to the draft.
Not sure about whether it has been raised already though.

The aggressive HBs sent on a potentially failed destination address should =
not contribute
to the association overall error counter. I.e., a failed HB should not incr=
ement the associations error counter.

At least that it how I firmly believe that things should be as the robustne=
ss of the=20
association error count should not be impacted by the more aggressive HB pr=
obing
(Also simply following the approach of RFC4960 Path Verification. 5.4 of RF=
C4960)

Would it be possible to have this explicitly clarified in the draft ?

Thanks.
BR, Karen

-----Original Message-----
From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of Y=
oshifumi Nishida
Sent: 16. september 2011 10:22
To: tsvwg
Subject: Re: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt

Hi folks,

Based on the michael's review, we have updated the sctp failover draft.
We believe we addressed the comments we got so far.

Please let us know if we overlook something or if you have more comments.

Thanks,
--
Yoshifumi Nishida
nishida@sfc.wide.ad.jp


2011/9/16  <internet-drafts@ietf.org>:
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>
> =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : Quick Failover Algorithm in SC=
TP
> =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : Yoshifumi Nishida
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Preethi Natarajan
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Armando Caro
> =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-nishida-tsvwg-sctp-failove=
r-04.txt
> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 16
> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-09-16
>
> =A0 One of the major advantages in SCTP is supporting multi-homing
> =A0 communication. =A0If a multi-homed end-point has redundant network
> =A0 connections, SCTP sessions can have a good chance to survive from
> =A0 network failures by migrating inactive network to active one.
> =A0 However, if we follow the SCTP standard, there can be significant
> =A0 delay for the network migration. =A0During this migration period, SCT=
P
> =A0 cannot transmit much data to the destination. =A0This issue drastical=
ly
> =A0 impairs the usability of SCTP in some situations. =A0This memo
> =A0 describes the issue of SCTP failover mechanism and discuss its
> =A0 solutions which require minimal modification to the current standard.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-nishida-tsvwg-sctp-failover-04.=
txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-nishida-tsvwg-sctp-failover-04.t=
xt
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>

From internet-drafts@ietf.org  Thu Dec  8 12:34:35 2011
Return-Path: <internet-drafts@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 1AD0621F84B7; Thu,  8 Dec 2011 12:34:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.401
X-Spam-Level: 
X-Spam-Status: No, score=-102.401 tagged_above=-999 required=5 tests=[AWL=-0.158, 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 CPUXQBFH+GdJ; Thu,  8 Dec 2011 12:34:34 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF87F21F84A0; Thu,  8 Dec 2011 12:34:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-tsvwg-sctp-strrst-13.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111208203434.1214.33347.idtracker@ietfa.amsl.com>
Date: Thu, 08 Dec 2011 12:34:34 -0800
Cc: 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: Thu, 08 Dec 2011 20:34:35 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Transport Area Working Group Working =
Group of the IETF.

	Title           : Stream Control Transmission Protocol (SCTP) Stream Recon=
figuration
	Author(s)       : Randall R. Stewart
                          Michael Tuexen
                          Peter Lei
	Filename        : draft-ietf-tsvwg-sctp-strrst-13.txt
	Pages           : 33
	Date            : 2011-12-08

   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
   application layer that the reset has been performed.  Applications
   requiring 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.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctp-strrst-13.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-tsvwg-sctp-strrst-13.txt


From mvproshin@gmail.com  Thu Dec  8 23:27:25 2011
Return-Path: <mvproshin@gmail.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 38FBE11E808C for <tsvwg@ietfa.amsl.com>; Thu,  8 Dec 2011 23:27:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 gPnT7kE-B2cn for <tsvwg@ietfa.amsl.com>; Thu,  8 Dec 2011 23:27:24 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0192D11E808B for <tsvwg@ietf.org>; Thu,  8 Dec 2011 23:27:23 -0800 (PST)
Received: by wgbdr13 with SMTP id dr13so3971701wgb.13 for <tsvwg@ietf.org>; Thu, 08 Dec 2011 23:27:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=lFfB4uE4EwGnwFsZEF/byBotklbFKkTzoIXfboeKNj0=; b=UXPtQaTc/+aaN06ykQp3wkmktdCUdgUJzPrJ3IoMtwPMl9yoB5+xhgEa18To+97Z6F QAwIBSV/aaffLpORodIIEWqYMepUk3wKVnSTxEAnxugy6e/gqZdIiAKmj1cwle8HgSE6 K0CFGd19upNXiPl3irgwyEk2d9XlW8pjf/rac=
MIME-Version: 1.0
Received: by 10.180.102.233 with SMTP id fr9mr9471361wib.40.1323415643182; Thu, 08 Dec 2011 23:27:23 -0800 (PST)
Received: by 10.216.173.69 with HTTP; Thu, 8 Dec 2011 23:27:23 -0800 (PST)
Date: Fri, 9 Dec 2011 11:27:23 +0400
Message-ID: <CA+-pjPzogR5VLVOqX0H1jfw-CgB_CDLH1Zc=MAq0qCVoYETq-g@mail.gmail.com>
Subject: Fast Retransmission in SCTP
From: Maxim Proshin <mvproshin@gmail.com>
To: tsvwg@ietf.org
Content-Type: multipart/alternative; boundary=f46d04451a274d566904b3a3b71b
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: Fri, 09 Dec 2011 07:27:25 -0000

--f46d04451a274d566904b3a3b71b
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi experts,

here I would like to discuss the Fast Retransmission algorithm in RFC 4960.
Frankly this RFC does not describe clearly how to send (to which
destination) fast retransmissions but we can find some information in RFC
4460 which says:

"
*2.39. Retransmission Policy

2.39.1. Description of the Problem

The current retransmission policy (send all retransmissions an
alternate destination) in the specification has performance issues
under certain loss conditions with multihomed endpoints. Instead,
fast retransmissions should be sent to the same destination, and only
timeout retransmissions should be sent to an alternate destination [4].*
"

Reading this article my first feeling was that *fast retransmissions should
be sent to the same destination where initial transmissions were sent*.

So my first question is
 *is my RFC interpretation correct or not?*

Meanwhile, there are some more articles about retransmision policies where
RFC's authors also participated. For instance, "Retransmission Policies
With Transport Layer Multihoming" describes some improvements in fast
retransmission policy in respect to RFC 2960 and I think that they were
considered during RFC 4960 preparation. This analysis also proposes to send
fast retransmissions to the same destination:
"
*In this solution, all retransmissions are sent to the*
*same destination as their original transmissions.*
*...*
*Instead of all*
*retransmissions following the Retransmit to Same Destination*
*policy of Solution 1, only Fast Retransmissions*
*should follow this policy.*
"

It seems that this statement confirms my initial feeling described above.
But at the same time it says about primary path:
"
*Using the same destination for retransmissions has*
*the added advantage that the primary destination's cwnd*
*bene=02ts from successful retransmissions.*
"
and it results is some doubts. On the one hand fast retransmissions should
be sent to the same destination, on the other it should be sent to the
primary destination.
In usual case "the same" and primary destinations are equal. But RFC 4960
doesn't prevent primary destination changing by the user so it can be
changed in run-time.

So my second question is
 *if the primary destination is changed in run-time, where SCTP should sent
fast retransmissions which were detected for the previous primary
destination?*

The mentioned above article describes one advantage in respect to sending
to the primay destination, this is about cwnd benets from successful
retransmission. But I think that in case of fast retransmission it will not
be observed or the advantage is very very low.

At the same time sending to the primary destination results in a big
disadvantage: SCTP should recalculate cwnd if it sends fast retransmissions
to the primary destination because RFC 4960 says:
"
When a Fast Retransmit is being performed, the sender SHOULD ignore the
value of cwnd
"
I think the reason is that it was considered during initial transmission.

*What do you think about this?*

I'm not sure whether it was discussed already or not. If yes, please
provide me with discussion's results.

--=20
BR, Maxim

--f46d04451a274d566904b3a3b71b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi experts,<div><br></div><div>here I would like to discuss the Fast Retran=
smission algorithm in RFC 4960.</div><div>Frankly this RFC does not describ=
e clearly how to send (to which destination) fast retransmissions but we ca=
n find some information in RFC 4460 which says:</div>
<div><br></div><div>&quot;</div><div><i>2.39. Retransmission Policy<br><br>=
2.39.1.  Description of the Problem<br><br>   The current retransmission po=
licy (send all retransmissions an<br>   alternate destination) in the speci=
fication has performance issues<br>
   under certain loss conditions with multihomed endpoints.  Instead,<br><b=
>   fast retransmissions should be sent <u>to the same destination</u></b>,=
 and only<br>   timeout retransmissions should be sent to an alternate dest=
ination=A0[4].</i></div>
<div>&quot;=A0</div><div><br></div><div>Reading this article my first feeli=
ng was that <b>fast retransmissions should be sent to the same destination =
<u>where initial transmissions were sent</u></b>.</div><div><div><br></div>
<div>So my first question is=A0</div><div>=A0<u>is my RFC interpretation co=
rrect or not?</u></div><div><br></div><div>Meanwhile, there are some more a=
rticles about retransmision policies where RFC&#39;s authors also participa=
ted. For instance, &quot;Retransmission Policies With Transport Layer Multi=
homing&quot; describes some improvements in fast retransmission policy in r=
espect to RFC 2960 and I think that they were considered during RFC 4960 pr=
eparation. This analysis also proposes to send fast retransmissions to the =
same destination:</div>
<div>&quot;</div><div><div><i>In this solution,<b> </b>all retransmissions =
are sent <b>to the</b></i></div><div><i><b>same destination</b> as their or=
iginal transmissions.</i></div></div><div><i>...</i></div><div><div><i>Inst=
ead of all</i></div>
<div><i>retransmissions following the Retransmit to Same Destination</i></d=
iv><div><i>policy of Solution 1, only Fast Retransmissions</i></div><div><i=
>should follow this policy.</i></div></div><div>&quot;</div><div><br></div>
<div>It seems that this statement confirms my initial feeling described abo=
ve. But at the same time it says about primary path:</div><div>&quot;</div>=
<div><i>Using the same destination for retransmissions has</i></div><div>
<i>the added advantage that <b>the primary destination</b>&#39;s cwnd</i></=
div><div><i>bene=02ts from successful retransmissions.</i></div><div>&quot;=
</div><div>and it results is some doubts. On the one hand fast retransmissi=
ons should be sent to the same destination, on the other it should be sent =
to the primary destination.=A0</div>
<div>In usual case &quot;the same&quot; and primary destinations are equal.=
 But RFC 4960 doesn&#39;t prevent primary destination changing by the user =
so it can be changed in run-time.</div><div><br></div><div>So my second que=
stion is</div>
<div>=A0<u>if the primary destination is changed in run-time, where SCTP sh=
ould sent fast retransmissions which were detected for the previous primary=
 destination?</u></div><div><br></div><div>The mentioned above article desc=
ribes one advantage in respect to sending to the primay destination, this i=
s about cwnd benets from successful retransmission. But I think that in cas=
e of fast retransmission it will not be observed or the advantage is very v=
ery low.</div>
<div><br></div><div>At the same time sending to the primary destination res=
ults in a big disadvantage: SCTP should recalculate cwnd if it sends fast r=
etransmissions to the primary destination because RFC 4960 says:</div><div>
&quot;</div>When a Fast Retransmit is being performed, the sender SHOULD ig=
nore the value of cwnd<div>&quot;=A0</div><div>I think the reason is that i=
t was considered during initial transmission.</div><div><br></div><div><u>W=
hat do you think about this?</u></div>
<div><br></div><div>I&#39;m not sure whether it was discussed already or no=
t. If yes, please provide me with discussion&#39;s results.</div><div><br><=
/div>-- <br>BR, Maxim<br>
</div>

--f46d04451a274d566904b3a3b71b--

From yoshifumi.nishida@gmail.com  Fri Dec  9 01:05:39 2011
Return-Path: <yoshifumi.nishida@gmail.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 7989C21F84B3 for <tsvwg@ietfa.amsl.com>; Fri,  9 Dec 2011 01:05:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.657
X-Spam-Level: 
X-Spam-Status: No, score=-102.657 tagged_above=-999 required=5 tests=[AWL=0.320, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 LILfwvwuDY+U for <tsvwg@ietfa.amsl.com>; Fri,  9 Dec 2011 01:05:38 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id BBD3621F84B0 for <tsvwg@ietf.org>; Fri,  9 Dec 2011 01:05:38 -0800 (PST)
Received: by iaek3 with SMTP id k3so4601110iae.31 for <tsvwg@ietf.org>; Fri, 09 Dec 2011 01:05:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=LsHjoMShz1DcNE+9s01rFRRH563L4nQse5nbni6f7ms=; b=dg+l+bBGxj0GxahavSH8gXemPt6hjQwLeJhNdaGcWr3aRkJpGuNXQvLvo9KIJBOdxP o3TuLid5BorrZw2XrN0+EMtG+qIHg2bmpu3VluHACbmSw8ldtv4zxejn9sH11VE/TM5K KfreKZDnC2hDDKIsbPAlnfPZwdyaKdAJmOg7c=
MIME-Version: 1.0
Received: by 10.50.197.167 with SMTP id iv7mr2746067igc.46.1323421538312; Fri, 09 Dec 2011 01:05:38 -0800 (PST)
Sender: yoshifumi.nishida@gmail.com
Received: by 10.42.240.74 with HTTP; Fri, 9 Dec 2011 01:05:38 -0800 (PST)
In-Reply-To: <CF340E42AED0874C81947E18863DE77B13340F715E@EXMB03.eu.tieto.com>
References: <20110916075854.4673.6360.idtracker@ietfa.amsl.com> <CABxaRLET3w_MhRtakjuA1Mc4sXd1-FpmorSgjK78K_6WjOX-Qg@mail.gmail.com> <CF340E42AED0874C81947E18863DE77B13340F715E@EXMB03.eu.tieto.com>
Date: Fri, 9 Dec 2011 01:05:38 -0800
X-Google-Sender-Auth: 6_vk4Fw7XgMnuK-P6pXBRpsQ6cI
Message-ID: <CABxaRLHFc5jin9tfjQxZV2SH-yMW80x0goe1QiOVSS7fynq_kA@mail.gmail.com>
Subject: Re: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Karen.Nielsen@tieto.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: 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: Fri, 09 Dec 2011 09:05:39 -0000

Hi Karen, thanks for the comment.

I think PF is not aggressive on the point you mentioned. Please point
out if I miss something.
In RFC4960, retransmitted data packets are sent to the failed
destination address and it will contribute to the
Association.Max.Retrans.
In PF, HBs are sent to the failed destination address instead of data
packets. The interval of HBs for the destination is RTO, which will be
the same as those of the retransmitted packets.
So, I believe both approach will have similar results on the
robustness of the association error count.

Thanks,
--
Yoshifumi Nishida
nishida@sfc.wide.ad.jp


2011/12/8  <Karen.Nielsen@tieto.com>:
> Hi,
>
> One additional comment to the draft.
> Not sure about whether it has been raised already though.
>
> The aggressive HBs sent on a potentially failed destination address shoul=
d not contribute
> to the association overall error counter. I.e., a failed HB should not in=
crement the associations error counter.
>
> At least that it how I firmly believe that things should be as the robust=
ness of the
> association error count should not be impacted by the more aggressive HB =
probing
> (Also simply following the approach of RFC4960 Path Verification. 5.4 of =
RFC4960)
>
> Would it be possible to have this explicitly clarified in the draft ?
>
> Thanks.
> BR, Karen
>
> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of=
 Yoshifumi Nishida
> Sent: 16. september 2011 10:22
> To: tsvwg
> Subject: Re: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt
>
> Hi folks,
>
> Based on the michael's review, we have updated the sctp failover draft.
> We believe we addressed the comments we got so far.
>
> Please let us know if we overlook something or if you have more comments.
>
> Thanks,
> --
> Yoshifumi Nishida
> nishida@sfc.wide.ad.jp
>
>
> 2011/9/16 =A0<internet-drafts@ietf.org>:
>> A New Internet-Draft is available from the on-line Internet-Drafts direc=
tories.
>>
>> =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : Quick Failover Algorithm in S=
CTP
>> =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : Yoshifumi Nishida
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Preethi Natarajan
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Armando Caro
>> =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-nishida-tsvwg-sctp-failov=
er-04.txt
>> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 16
>> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-09-16
>>
>> =A0 One of the major advantages in SCTP is supporting multi-homing
>> =A0 communication. =A0If a multi-homed end-point has redundant network
>> =A0 connections, SCTP sessions can have a good chance to survive from
>> =A0 network failures by migrating inactive network to active one.
>> =A0 However, if we follow the SCTP standard, there can be significant
>> =A0 delay for the network migration. =A0During this migration period, SC=
TP
>> =A0 cannot transmit much data to the destination. =A0This issue drastica=
lly
>> =A0 impairs the usability of SCTP in some situations. =A0This memo
>> =A0 describes the issue of SCTP failover mechanism and discuss its
>> =A0 solutions which require minimal modification to the current standard=
.
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-nishida-tsvwg-sctp-failover-04=
.txt
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-nishida-tsvwg-sctp-failover-04.=
txt
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>

From Michael.Tuexen@lurchi.franken.de  Fri Dec  9 02:34:41 2011
Return-Path: <Michael.Tuexen@lurchi.franken.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 6A0CC21F84BC for <tsvwg@ietfa.amsl.com>; Fri,  9 Dec 2011 02:34:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 3u+LlEM1+SIo for <tsvwg@ietfa.amsl.com>; Fri,  9 Dec 2011 02:34:40 -0800 (PST)
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 6AD7521F84B4 for <tsvwg@ietf.org>; Fri,  9 Dec 2011 02:34:40 -0800 (PST)
Received: from [192.168.1.200] (p5481AC1F.dip.t-dialin.net [84.129.172.31]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 711AB1C0B4612; Fri,  9 Dec 2011 11:34:37 +0100 (CET)
Subject: Re: Fast Retransmission in SCTP
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <CA+-pjPzogR5VLVOqX0H1jfw-CgB_CDLH1Zc=MAq0qCVoYETq-g@mail.gmail.com>
Date: Fri, 9 Dec 2011 11:34:34 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B21E99E1-05EC-42DA-A3DF-E91FB207453A@lurchi.franken.de>
References: <CA+-pjPzogR5VLVOqX0H1jfw-CgB_CDLH1Zc=MAq0qCVoYETq-g@mail.gmail.com>
To: Maxim Proshin <mvproshin@gmail.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: 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: Fri, 09 Dec 2011 10:34:41 -0000

On Dec 9, 2011, at 8:27 AM, Maxim Proshin wrote:

> Hi experts,
>=20
> here I would like to discuss the Fast Retransmission algorithm in RFC =
4960.
> Frankly this RFC does not describe clearly how to send (to which =
destination) fast retransmissions but we can find some information in =
RFC 4460 which says:
>=20
> "
> 2.39. Retransmission Policy
>=20
> 2.39.1. Description of the Problem
>=20
> The current retransmission policy (send all retransmissions an
> alternate destination) in the specification has performance issues
> under certain loss conditions with multihomed endpoints. Instead,
> fast retransmissions should be sent to the same destination, and only
> timeout retransmissions should be sent to an alternate destination =
[4].
> "=20
>=20
> Reading this article my first feeling was that fast retransmissions =
should be sent to the same destination where initial transmissions were =
sent.
>=20
> So my first question is=20
>  is my RFC interpretation correct or not?
Yes. Fast retransmissions should be send to the same destination as the =
initial transmission.
Timer based retransmissions should use an alternate destination.
>=20
> Meanwhile, there are some more articles about retransmision policies =
where RFC's authors also participated. For instance, "Retransmission =
Policies With Transport Layer Multihoming" describes some improvements =
in fast retransmission policy in respect to RFC 2960 and I think that =
they were considered during RFC 4960 preparation. This analysis also =
proposes to send fast retransmissions to the same destination:
> "
> In this solution, all retransmissions are sent to the
> same destination as their original transmissions.
> ...
> Instead of all
> retransmissions following the Retransmit to Same Destination
> policy of Solution 1, only Fast Retransmissions
> should follow this policy.
> "
>=20
> It seems that this statement confirms my initial feeling described =
above. But at the same time it says about primary path:
> "
> Using the same destination for retransmissions has
> the added advantage that the primary destination's cwnd
> bene=02ts from successful retransmissions.
> "
> and it results is some doubts. On the one hand fast retransmissions =
should be sent to the same destination, on the other it should be sent =
to the primary destination.=20
> In usual case "the same" and primary destinations are equal. But RFC =
4960 doesn't prevent primary destination changing by the user so it can =
be changed in run-time.
>=20
> So my second question is
>  if the primary destination is changed in run-time, where SCTP should =
sent fast retransmissions which were detected for the previous primary =
destination?
Changing the primary is normally not done at a high rate. So you are =
looking at the
case where fast retransmission occur and the user changed the primary in =
between.

I guess there is no special case on the RFC for that. So the fast =
retransmission would
go to the destination to which it was initially sent. The same applies =
if the user
specified a destination and therefore the primary was not used.
>=20
> The mentioned above article describes one advantage in respect to =
sending to the primay destination, this is about cwnd benets from =
successful retransmission. But I think that in case of fast =
retransmission it will not be observed or the advantage is very very =
low.
>=20
> At the same time sending to the primary destination results in a big =
disadvantage: SCTP should recalculate cwnd if it sends fast =
retransmissions to the primary destination because RFC 4960 says:
> "
> When a Fast Retransmit is being performed, the sender SHOULD ignore =
the value of cwnd
> "=20
> I think the reason is that it was considered during initial =
transmission.
If you do a fast retransmit, you assume that the packet has left the =
network.
So you would have to subtract and add it. This means ignoring...

Best regards
Michael
>=20
> What do you think about this?
>=20
> I'm not sure whether it was discussed already or not. If yes, please =
provide me with discussion's results.
>=20
> --=20
> BR, Maxim


From yoshifumi.nishida@gmail.com  Fri Dec  9 03:40:00 2011
Return-Path: <yoshifumi.nishida@gmail.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 DE9E321F85FF for <tsvwg@ietfa.amsl.com>; Fri,  9 Dec 2011 03:40:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.71
X-Spam-Level: 
X-Spam-Status: No, score=-102.71 tagged_above=-999 required=5 tests=[AWL=0.267, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 8cXxU0W4VmoR for <tsvwg@ietfa.amsl.com>; Fri,  9 Dec 2011 03:40:00 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4781521F85F1 for <tsvwg@ietf.org>; Fri,  9 Dec 2011 03:40:00 -0800 (PST)
Received: by iaek3 with SMTP id k3so4837494iae.31 for <tsvwg@ietf.org>; Fri, 09 Dec 2011 03:39:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=fPS4Wj6FK/3KAB7hmBrcrt7iGSE9HTKuawvXRTGqu34=; b=CqeG6u1VJdzfMUj/j8mCla5Aue/j++G9kS42yIzFb6mz1REsAtaJJHn4RuGAgaluLO cS1UKqNBHl9PbbCcy+wL3kV5ZYv5puLqAGXg8yhoMnMgcFoQ6TrlsMcAflP/3AIKZKmS Gl9Lih7X4dNttwb3I3v0hLxLGY682xRJb85HE=
MIME-Version: 1.0
Received: by 10.50.197.167 with SMTP id iv7mr3175827igc.46.1323430798915; Fri, 09 Dec 2011 03:39:58 -0800 (PST)
Sender: yoshifumi.nishida@gmail.com
Received: by 10.42.240.74 with HTTP; Fri, 9 Dec 2011 03:39:58 -0800 (PST)
In-Reply-To: <CF340E42AED0874C81947E18863DE77B13340F741E@EXMB03.eu.tieto.com>
References: <20110916075854.4673.6360.idtracker@ietfa.amsl.com> <CABxaRLET3w_MhRtakjuA1Mc4sXd1-FpmorSgjK78K_6WjOX-Qg@mail.gmail.com> <CF340E42AED0874C81947E18863DE77B13340F715E@EXMB03.eu.tieto.com> <CABxaRLHFc5jin9tfjQxZV2SH-yMW80x0goe1QiOVSS7fynq_kA@mail.gmail.com> <CF340E42AED0874C81947E18863DE77B13340F741E@EXMB03.eu.tieto.com>
Date: Fri, 9 Dec 2011 03:39:58 -0800
X-Google-Sender-Auth: YEazK2PXISGW2-2hVAWYaK9g--E
Message-ID: <CABxaRLF2t=a8yD3T6HOL2YQ1r8jLR-BpVB4wUsdumbC_P50tnw@mail.gmail.com>
Subject: Re: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Karen.Nielsen@tieto.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: 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: Fri, 09 Dec 2011 11:40:01 -0000

Hi Karen,

2011/12/9  <Karen.Nielsen@tieto.com>:
> Hi,
>
> Please accept the follow up below.
>
>
> Hi Karen, thanks for the comment.
>
> I think PF is not aggressive on the point you mentioned. Please point
> out if I miss something.
> In RFC4960, retransmitted data packets are sent to the failed
> destination address and it will contribute to the
> Association.Max.Retrans.
>
> [Karen] In RFC4960 retransmitted packets will be send to most divergent p=
ath. Not to the PF path. But I suppose that you mean that as new data conti=
nues to be send on "PF" path in RFC4960, then the association error count w=
ill be hurt by the failure of these like it may be hurt
> by the failure of the aggressive HBs.

Sorry, that's what I meant. Thanks for the correction.

> In PF, HBs are sent to the failed destination address instead of data
> packets. The interval of HBs for the destination is RTO, which will be
> the same as those of the retransmitted packets.
> So, I believe both approach will have similar results on the
> robustness of the association error count.
>
> [Karen] I agree for the case where there continuously is data flowing.
> But when there is not such data, then the aggressive HBs will impact the =
robustness of
> the association error count as there is no successful data that will rese=
t it, as the successful retransmissions of data would.

Hmm. I see your point. In case where all path's status are active, but
somehow all of them become unavailable and one packet is sent. PF can
aggressively increase error count than RFC4960.. I would like to think
about how bad this is more.

>
> Generally, I have never understood why the faith of HBs should EVER contr=
ibute to the
> association error counter, EXCEPT when in idle state. And in this case, t=
hen in my opinion,
> it would suffice if it was the HBs on the primary path which were allowed=
 to contribute to the association error counter. Indeed the association err=
or counter is not there to ascertain whether all paths are available, only =
it should be there to ascertain whether some path of the association is ava=
ilable. In that respect HBs on non working (auxiliary) paths impacts the ro=
bustness of the association error counter.

It might be an interesting point. But, I'm not sure how much impact
this has. To make this effective, we need to presume the case where
all paths become unavailable, but at least one path comes back within
a certain amount of time. If this duration is too long or too short,
there'll be no difference even if we exclude HB's contributions. In
case of RFC4960, HB's contribution seems to be minor to me.

Thanks,
--
Yoshifumi Nishida
nishida@sfc.wide.ad.jp

From alcortesm.uc3m@gmail.com  Fri Dec  9 04:51:47 2011
Return-Path: <alcortesm.uc3m@gmail.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 2A0CD21F8573 for <tsvwg@ietfa.amsl.com>; Fri,  9 Dec 2011 04:51:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.077
X-Spam-Level: 
X-Spam-Status: No, score=-2.077 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_21=0.6, MIME_8BIT_HEADER=0.3, 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 8l1R57a402wf for <tsvwg@ietfa.amsl.com>; Fri,  9 Dec 2011 04:51:46 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 50A3221F856F for <tsvwg@ietf.org>; Fri,  9 Dec 2011 04:51:46 -0800 (PST)
Received: by iaek3 with SMTP id k3so4944002iae.31 for <tsvwg@ietf.org>; Fri, 09 Dec 2011 04:51:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=OmYA59mlpVwZZ+5PmcQvLy5tEoKwx2EXLyF3Ot9qSJ8=; b=QRANCQN8eBZX9XzLCPq0KZZVJbURhuzQS5POhm3PVbyTanK4LbkzW2spP9no8+8qhF eGNyoi6Jfg+1+eenbYYmoyYbEkENrwH8AnUAHuWyG5iinkqA9XbviJBLVSLC21epOCUx Es0+14KtRBwJseiJcQBnumIk5DAtKZS91gpFg=
Received: by 10.50.217.195 with SMTP id pa3mr3738210igc.12.1323435103242; Fri, 09 Dec 2011 04:51:43 -0800 (PST)
MIME-Version: 1.0
Sender: alcortesm.uc3m@gmail.com
Received: by 10.231.134.129 with HTTP; Fri, 9 Dec 2011 04:51:21 -0800 (PST)
In-Reply-To: <CABxaRLHFc5jin9tfjQxZV2SH-yMW80x0goe1QiOVSS7fynq_kA@mail.gmail.com>
References: <20110916075854.4673.6360.idtracker@ietfa.amsl.com> <CABxaRLET3w_MhRtakjuA1Mc4sXd1-FpmorSgjK78K_6WjOX-Qg@mail.gmail.com> <CF340E42AED0874C81947E18863DE77B13340F715E@EXMB03.eu.tieto.com> <CABxaRLHFc5jin9tfjQxZV2SH-yMW80x0goe1QiOVSS7fynq_kA@mail.gmail.com>
From: =?UTF-8?Q?Alberto_Cort=C3=A9s?= <alcortes@it.uc3m.es>
Date: Fri, 9 Dec 2011 13:51:21 +0100
X-Google-Sender-Auth: RJmm2OQp1zkobRt1RHKG-ITq90Y
Message-ID: <CAGK4rN=SjvJ4o70hEFKGNeSU=L1ZzS46F_6Oh0Nbnoa46gOCHQ@mail.gmail.com>
Subject: Re: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt
To: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Karen.Nielsen@tieto.com, 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: Fri, 09 Dec 2011 12:51:47 -0000

On Fri, Dec 9, 2011 at 10:05 AM, Yoshifumi Nishida
<nishida@sfc.wide.ad.jp> wrote:
> Hi Karen, thanks for the comment.
>
> I think PF is not aggressive on the point you mentioned. Please point
> out if I miss something.
> In RFC4960, retransmitted data packets are sent to the failed
> destination address and it will contribute to the
> Association.Max.Retrans.

I would like to point out that in RFC4960, retransmissions SHOULD be
sent to a different address than the one that failed (section 6.4),
and as far as I know, that's generally the case in all
implementations.

The probing of the failed address is performed by fresh, new
transmissions, not by retransmissions.


> In PF, HBs are sent to the failed destination address instead of data
> packets. The interval of HBs for the destination is RTO, which will be
> the same as those of the retransmitted packets.
> So, I believe both approach will have similar results on the
> robustness of the association error count.
>
> Thanks,
> --
> Yoshifumi Nishida
> nishida@sfc.wide.ad.jp
>
>
> 2011/12/8 =C2=A0<Karen.Nielsen@tieto.com>:
>> Hi,
>>
>> One additional comment to the draft.
>> Not sure about whether it has been raised already though.
>>
>> The aggressive HBs sent on a potentially failed destination address shou=
ld not contribute
>> to the association overall error counter. I.e., a failed HB should not i=
ncrement the associations error counter.
>>
>> At least that it how I firmly believe that things should be as the robus=
tness of the
>> association error count should not be impacted by the more aggressive HB=
 probing
>> (Also simply following the approach of RFC4960 Path Verification. 5.4 of=
 RFC4960)
>>
>> Would it be possible to have this explicitly clarified in the draft ?
>>
>> Thanks.
>> BR, Karen
>>
>> -----Original Message-----
>> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf O=
f Yoshifumi Nishida
>> Sent: 16. september 2011 10:22
>> To: tsvwg
>> Subject: Re: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt
>>
>> Hi folks,
>>
>> Based on the michael's review, we have updated the sctp failover draft.
>> We believe we addressed the comments we got so far.
>>
>> Please let us know if we overlook something or if you have more comments=
.
>>
>> Thanks,
>> --
>> Yoshifumi Nishida
>> nishida@sfc.wide.ad.jp
>>
>>
>> 2011/9/16 =C2=A0<internet-drafts@ietf.org>:
>>> A New Internet-Draft is available from the on-line Internet-Drafts dire=
ctories.
>>>
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0Title =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Q=
uick Failover Algorithm in SCTP
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0Author(s) =C2=A0 =C2=A0 =C2=A0 : Yoshifumi N=
ishida
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0Preethi Natarajan
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0Armando Caro
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0Filename =C2=A0 =C2=A0 =C2=A0 =C2=A0: draft-=
nishida-tsvwg-sctp-failover-04.txt
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0Pages =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : 1=
6
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0Date =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0: 2011-09-16
>>>
>>> =C2=A0 One of the major advantages in SCTP is supporting multi-homing
>>> =C2=A0 communication. =C2=A0If a multi-homed end-point has redundant ne=
twork
>>> =C2=A0 connections, SCTP sessions can have a good chance to survive fro=
m
>>> =C2=A0 network failures by migrating inactive network to active one.
>>> =C2=A0 However, if we follow the SCTP standard, there can be significan=
t
>>> =C2=A0 delay for the network migration. =C2=A0During this migration per=
iod, SCTP
>>> =C2=A0 cannot transmit much data to the destination. =C2=A0This issue d=
rastically
>>> =C2=A0 impairs the usability of SCTP in some situations. =C2=A0This mem=
o
>>> =C2=A0 describes the issue of SCTP failover mechanism and discuss its
>>> =C2=A0 solutions which require minimal modification to the current stan=
dard.
>>>
>>>
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-nishida-tsvwg-sctp-failover-0=
4.txt
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>> This Internet-Draft can be retrieved at:
>>> ftp://ftp.ietf.org/internet-drafts/draft-nishida-tsvwg-sctp-failover-04=
.txt
>>> _______________________________________________
>>> I-D-Announce mailing list
>>> I-D-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>



--=20
Alberto Cort=C3=A9s-Mart=C3=ADn
Telematic Engineering Dept. at UC3M
http://www.it.uc3m.es/alcortes/index.html

From mvproshin@gmail.com  Sat Dec 10 23:37:04 2011
Return-Path: <mvproshin@gmail.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 3394F21F8B25 for <tsvwg@ietfa.amsl.com>; Sat, 10 Dec 2011 23:37:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.448
X-Spam-Level: 
X-Spam-Status: No, score=-3.448 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 DxI24Kkh0mHN for <tsvwg@ietfa.amsl.com>; Sat, 10 Dec 2011 23:37:03 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 16E0C21F8B17 for <tsvwg@ietf.org>; Sat, 10 Dec 2011 23:36:58 -0800 (PST)
Received: by wgbdr13 with SMTP id dr13so6751256wgb.13 for <tsvwg@ietf.org>; Sat, 10 Dec 2011 23:36:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/94Dzei9pDW7N5/boZHWmkiChKYQQQgcttdhRqr9M8Q=; b=f5aQhzp4e7msgRzZVqDRohroZkwqW3t2bsckASGaRJZN6lWX8PBMIffVTDcPXpjNYP c11qXwQ9gi9ZpHHJNImf7cz3oJ29e3IbfhjTzdoFnKkafrhi8SgYNSLQ1Ln4EmyRviFi CSi1YsjwwAm3XFMuf1AEf+w0LsOZ+UxTEYLiw=
MIME-Version: 1.0
Received: by 10.216.71.14 with SMTP id q14mr1235926wed.3.1323589018311; Sat, 10 Dec 2011 23:36:58 -0800 (PST)
Received: by 10.216.173.69 with HTTP; Sat, 10 Dec 2011 23:36:58 -0800 (PST)
In-Reply-To: <B21E99E1-05EC-42DA-A3DF-E91FB207453A@lurchi.franken.de>
References: <CA+-pjPzogR5VLVOqX0H1jfw-CgB_CDLH1Zc=MAq0qCVoYETq-g@mail.gmail.com> <B21E99E1-05EC-42DA-A3DF-E91FB207453A@lurchi.franken.de>
Date: Sun, 11 Dec 2011 11:36:58 +0400
Message-ID: <CA+-pjPyRv1UMU4MnfPtNu8gK3E9so5zkLJQXJ+cGiN9ZjBpmGQ@mail.gmail.com>
Subject: Re: Fast Retransmission in SCTP
From: Maxim Proshin <mvproshin@gmail.com>
To: =?ISO-8859-1?Q?Michael_T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
Content-Type: multipart/alternative; boundary=00504502c64c43dd8204b3cc159f
Cc: 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: Sun, 11 Dec 2011 07:37:04 -0000

--00504502c64c43dd8204b3cc159f
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Michael,

Thank you! You confirmed my initial feeling that FR should not be based on
the primary destination and now it is clear.
Regarding your last answer I think you meant that sending FR to the same
destination we should not change cwnd because adding and substraction means
ignoring. But if FR were based on the primary destination we would have to
recalculate it in case "the same" and primary destinations would be
different.

BR, Maxim


2011/12/9 Michael T=FCxen <Michael.Tuexen@lurchi.franken.de>

> On Dec 9, 2011, at 8:27 AM, Maxim Proshin wrote:
>
> > Hi experts,
> >
> > here I would like to discuss the Fast Retransmission algorithm in RFC
> 4960.
> > Frankly this RFC does not describe clearly how to send (to which
> destination) fast retransmissions but we can find some information in RFC
> 4460 which says:
> >
> > "
> > 2.39. Retransmission Policy
> >
> > 2.39.1. Description of the Problem
> >
> > The current retransmission policy (send all retransmissions an
> > alternate destination) in the specification has performance issues
> > under certain loss conditions with multihomed endpoints. Instead,
> > fast retransmissions should be sent to the same destination, and only
> > timeout retransmissions should be sent to an alternate destination [4].
> > "
> >
> > Reading this article my first feeling was that fast retransmissions
> should be sent to the same destination where initial transmissions were
> sent.
> >
> > So my first question is
> >  is my RFC interpretation correct or not?
> Yes. Fast retransmissions should be send to the same destination as the
> initial transmission.
> Timer based retransmissions should use an alternate destination.
> >
> > Meanwhile, there are some more articles about retransmision policies
> where RFC's authors also participated. For instance, "Retransmission
> Policies With Transport Layer Multihoming" describes some improvements in
> fast retransmission policy in respect to RFC 2960 and I think that they
> were considered during RFC 4960 preparation. This analysis also proposes =
to
> send fast retransmissions to the same destination:
> > "
> > In this solution, all retransmissions are sent to the
> > same destination as their original transmissions.
> > ...
> > Instead of all
> > retransmissions following the Retransmit to Same Destination
> > policy of Solution 1, only Fast Retransmissions
> > should follow this policy.
> > "
> >
> > It seems that this statement confirms my initial feeling described
> above. But at the same time it says about primary path:
> > "
> > Using the same destination for retransmissions has
> > the added advantage that the primary destination's cwnd
> > bene ts from successful retransmissions.
> > "
> > and it results is some doubts. On the one hand fast retransmissions
> should be sent to the same destination, on the other it should be sent to
> the primary destination.
> > In usual case "the same" and primary destinations are equal. But RFC
> 4960 doesn't prevent primary destination changing by the user so it can b=
e
> changed in run-time.
> >
> > So my second question is
> >  if the primary destination is changed in run-time, where SCTP should
> sent fast retransmissions which were detected for the previous primary
> destination?
> Changing the primary is normally not done at a high rate. So you are
> looking at the
> case where fast retransmission occur and the user changed the primary in
> between.
>
> I guess there is no special case on the RFC for that. So the fast
> retransmission would
> go to the destination to which it was initially sent. The same applies if
> the user
> specified a destination and therefore the primary was not used.
> >
> > The mentioned above article describes one advantage in respect to
> sending to the primay destination, this is about cwnd benets from
> successful retransmission. But I think that in case of fast retransmissio=
n
> it will not be observed or the advantage is very very low.
> >
> > At the same time sending to the primary destination results in a big
> disadvantage: SCTP should recalculate cwnd if it sends fast retransmissio=
ns
> to the primary destination because RFC 4960 says:
> > "
> > When a Fast Retransmit is being performed, the sender SHOULD ignore the
> value of cwnd
> > "
> > I think the reason is that it was considered during initial transmissio=
n.
> If you do a fast retransmit, you assume that the packet has left the
> network.
> So you would have to subtract and add it. This means ignoring...
>
> Best regards
> Michael
> >
> > What do you think about this?
> >
> > I'm not sure whether it was discussed already or not. If yes, please
> provide me with discussion's results.
> >
> > --
> > BR, Maxim
>
>


--=20
BR, Max

--00504502c64c43dd8204b3cc159f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Michael,<div><br></div><div>Thank you! You confirmed my initial feeling =
that FR should not be based on the primary destination and now it is clear.=
</div><div>Regarding your last answer I think you meant that sending FR to =
the same destination we should not change cwnd because adding and substract=
ion means ignoring. But if FR were based on the primary destination we woul=
d have to recalculate it in case &quot;the same&quot; and primary destinati=
ons would be different.</div>
<div><br></div><div>BR, Maxim</div><div><br><br><div class=3D"gmail_quote">=
2011/12/9 Michael T=FCxen <span dir=3D"ltr">&lt;<a href=3D"mailto:Michael.T=
uexen@lurchi.franken.de">Michael.Tuexen@lurchi.franken.de</a>&gt;</span><br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
<div class=3D"im">On Dec 9, 2011, at 8:27 AM, Maxim Proshin wrote:<br>
<br>
&gt; Hi experts,<br>
&gt;<br>
&gt; here I would like to discuss the Fast Retransmission algorithm in RFC =
4960.<br>
&gt; Frankly this RFC does not describe clearly how to send (to which desti=
nation) fast retransmissions but we can find some information in RFC 4460 w=
hich says:<br>
&gt;<br>
&gt; &quot;<br>
&gt; 2.39. Retransmission Policy<br>
&gt;<br>
&gt; 2.39.1. Description of the Problem<br>
&gt;<br>
&gt; The current retransmission policy (send all retransmissions an<br>
&gt; alternate destination) in the specification has performance issues<br>
&gt; under certain loss conditions with multihomed endpoints. Instead,<br>
&gt; fast retransmissions should be sent to the same destination, and only<=
br>
&gt; timeout retransmissions should be sent to an alternate destination [4]=
.<br>
&gt; &quot;<br>
&gt;<br>
&gt; Reading this article my first feeling was that fast retransmissions sh=
ould be sent to the same destination where initial transmissions were sent.=
<br>
&gt;<br>
&gt; So my first question is<br>
&gt; =A0is my RFC interpretation correct or not?<br>
</div>Yes. Fast retransmissions should be send to the same destination as t=
he initial transmission.<br>
Timer based retransmissions should use an alternate destination.<br>
<div class=3D"im">&gt;<br>
&gt; Meanwhile, there are some more articles about retransmision policies w=
here RFC&#39;s authors also participated. For instance, &quot;Retransmissio=
n Policies With Transport Layer Multihoming&quot; describes some improvemen=
ts in fast retransmission policy in respect to RFC 2960 and I think that th=
ey were considered during RFC 4960 preparation. This analysis also proposes=
 to send fast retransmissions to the same destination:<br>

&gt; &quot;<br>
&gt; In this solution, all retransmissions are sent to the<br>
&gt; same destination as their original transmissions.<br>
&gt; ...<br>
&gt; Instead of all<br>
&gt; retransmissions following the Retransmit to Same Destination<br>
&gt; policy of Solution 1, only Fast Retransmissions<br>
&gt; should follow this policy.<br>
&gt; &quot;<br>
&gt;<br>
&gt; It seems that this statement confirms my initial feeling described abo=
ve. But at the same time it says about primary path:<br>
&gt; &quot;<br>
&gt; Using the same destination for retransmissions has<br>
&gt; the added advantage that the primary destination&#39;s cwnd<br>
&gt; bene ts from successful retransmissions.<br>
&gt; &quot;<br>
&gt; and it results is some doubts. On the one hand fast retransmissions sh=
ould be sent to the same destination, on the other it should be sent to the=
 primary destination.<br>
&gt; In usual case &quot;the same&quot; and primary destinations are equal.=
 But RFC 4960 doesn&#39;t prevent primary destination changing by the user =
so it can be changed in run-time.<br>
&gt;<br>
&gt; So my second question is<br>
&gt; =A0if the primary destination is changed in run-time, where SCTP shoul=
d sent fast retransmissions which were detected for the previous primary de=
stination?<br>
</div>Changing the primary is normally not done at a high rate. So you are =
looking at the<br>
case where fast retransmission occur and the user changed the primary in be=
tween.<br>
<br>
I guess there is no special case on the RFC for that. So the fast retransmi=
ssion would<br>
go to the destination to which it was initially sent. The same applies if t=
he user<br>
specified a destination and therefore the primary was not used.<br>
<div class=3D"im">&gt;<br>
&gt; The mentioned above article describes one advantage in respect to send=
ing to the primay destination, this is about cwnd benets from successful re=
transmission. But I think that in case of fast retransmission it will not b=
e observed or the advantage is very very low.<br>

&gt;<br>
&gt; At the same time sending to the primary destination results in a big d=
isadvantage: SCTP should recalculate cwnd if it sends fast retransmissions =
to the primary destination because RFC 4960 says:<br>
&gt; &quot;<br>
&gt; When a Fast Retransmit is being performed, the sender SHOULD ignore th=
e value of cwnd<br>
&gt; &quot;<br>
&gt; I think the reason is that it was considered during initial transmissi=
on.<br>
</div>If you do a fast retransmit, you assume that the packet has left the =
network.<br>
So you would have to subtract and add it. This means ignoring...<br>
<br>
Best regards<br>
<font color=3D"#888888">Michael<br>
</font><div><div></div><div class=3D"h5">&gt;<br>
&gt; What do you think about this?<br>
&gt;<br>
&gt; I&#39;m not sure whether it was discussed already or not. If yes, plea=
se provide me with discussion&#39;s results.<br>
&gt;<br>
&gt; --<br>
&gt; BR, Maxim<br>
<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
BR, Max<br>
</div>

--00504502c64c43dd8204b3cc159f--

From wwwrun@rfc-editor.org  Sun Dec 11 14:19:18 2011
Return-Path: <wwwrun@rfc-editor.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 BCC0721F84C2; Sun, 11 Dec 2011 14:19:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.241
X-Spam-Level: 
X-Spam-Status: No, score=-105.241 tagged_above=-999 required=5 tests=[AWL=0.436, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, 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 dIlfWuMvGUx7; Sun, 11 Dec 2011 14:19:18 -0800 (PST)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id E729321F84CE; Sun, 11 Dec 2011 14:19:13 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DA1A472E004; Sun, 11 Dec 2011 14:18:24 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6458 on Sockets API Extensions for the Stream Control Transmission Protocol (SCTP)
From: rfc-editor@rfc-editor.org
Message-Id: <20111211221824.DA1A472E004@rfc-editor.org>
Date: Sun, 11 Dec 2011 14:18:24 -0800 (PST)
Cc: tsvwg@ietf.org, rfc-editor@rfc-editor.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: Sun, 11 Dec 2011 22:19:18 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6458

        Title:      Sockets API Extensions for the 
                    Stream Control Transmission Protocol (SCTP) 
        Author:     R. Stewart, M. Tuexen,
                    K. Poon, P. Lei,
                    V. Yasevich
        Status:     Informational
        Stream:     IETF
        Date:       December 2011
        Mailbox:    randall@lakerest.net, 
                    tuexen@fh-muenster.de, 
                    ka-cheong.poon@oracle.com,
                    peterlei@cisco.com, 
                    vladislav.yasevich@hp.com
        Pages:      115
        Characters: 237112
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-sctpsocket-32.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6458.txt

This document describes a mapping of the Stream Control Transmission
Protocol (SCTP) into a sockets API.  The benefits of this mapping
include compatibility for TCP applications, access to new SCTP
features, and a consolidated error and event notification scheme.
This document is not an Internet Standards Track specification; it is
published for informational purposes.

This document is a product of the Transport Area Working Group Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From Karen.Nielsen@tieto.com  Fri Dec  9 01:23:22 2011
Return-Path: <Karen.Nielsen@tieto.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 B8A8B21F842D for <tsvwg@ietfa.amsl.com>; Fri,  9 Dec 2011 01:23:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 6yOWpiI1oOgP for <tsvwg@ietfa.amsl.com>; Fri,  9 Dec 2011 01:23:22 -0800 (PST)
Received: from ebb05.tieto.com (ebb05.tieto.com [131.207.168.36]) by ietfa.amsl.com (Postfix) with ESMTP id 8C4D021F842B for <tsvwg@ietf.org>; Fri,  9 Dec 2011 01:23:21 -0800 (PST)
X-AuditID: 83cfa824-b7cebae0000004d2-47-4ee1d3886705
Received: from FIHGA-EXHUB01.eu.tieto.com ( [131.207.136.34]) by ebb05.tieto.com (SMTP Mailer) with SMTP id 20.4D.01234.783D1EE4; Fri,  9 Dec 2011 11:23:20 +0200 (EET)
Received: from EXMB03.eu.tieto.com ([169.254.1.127]) by FIHGA-EXHUB01.eu.tieto.com ([131.207.136.34]) with mapi; Fri, 9 Dec 2011 11:23:19 +0200
From: <Karen.Nielsen@tieto.com>
To: <nishida@sfc.wide.ad.jp>
Date: Fri, 9 Dec 2011 11:23:16 +0200
Subject: RE: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt
Thread-Topic: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt
Thread-Index: Acy2UbmA3f8IdgIxS7qvawo++kGxBwAAJG/A
Message-ID: <CF340E42AED0874C81947E18863DE77B13340F741E@EXMB03.eu.tieto.com>
References: <20110916075854.4673.6360.idtracker@ietfa.amsl.com> <CABxaRLET3w_MhRtakjuA1Mc4sXd1-FpmorSgjK78K_6WjOX-Qg@mail.gmail.com> <CF340E42AED0874C81947E18863DE77B13340F715E@EXMB03.eu.tieto.com> <CABxaRLHFc5jin9tfjQxZV2SH-yMW80x0goe1QiOVSS7fynq_kA@mail.gmail.com>
In-Reply-To: <CABxaRLHFc5jin9tfjQxZV2SH-yMW80x0goe1QiOVSS7fynq_kA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
X-Mailman-Approved-At: Mon, 12 Dec 2011 12:09:43 -0800
Cc: 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: Fri, 09 Dec 2011 09:23:22 -0000

Hi,

Please accept the follow up below.


Hi Karen, thanks for the comment.

I think PF is not aggressive on the point you mentioned. Please point
out if I miss something.
In RFC4960, retransmitted data packets are sent to the failed
destination address and it will contribute to the
Association.Max.Retrans.

[Karen] In RFC4960 retransmitted packets will be send to most divergent pat=
h. Not to the PF path. But I suppose that you mean that as new data continu=
es to be send on "PF" path in RFC4960, then the association error count wil=
l be hurt by the failure of these like it may be hurt
by the failure of the aggressive HBs.

In PF, HBs are sent to the failed destination address instead of data
packets. The interval of HBs for the destination is RTO, which will be
the same as those of the retransmitted packets.
So, I believe both approach will have similar results on the
robustness of the association error count.

[Karen] I agree for the case where there continuously is data flowing.
But when there is not such data, then the aggressive HBs will impact the ro=
bustness of
the association error count as there is no successful data that will reset =
it, as the successful retransmissions of data would.

Generally, I have never understood why the faith of HBs should EVER contrib=
ute to the
association error counter, EXCEPT when in idle state. And in this case, the=
n in my opinion,
it would suffice if it was the HBs on the primary path which were allowed t=
o contribute to the association error counter. Indeed the association error=
 counter is not there to ascertain whether all paths are available, only it=
 should be there to ascertain whether some path of the association is avail=
able. In that respect HBs on non working (auxiliary) paths impacts the robu=
stness of the association error counter.

BR, Karen


Thanks,
--
Yoshifumi Nishida
nishida@sfc.wide.ad.jp


2011/12/8  <Karen.Nielsen@tieto.com>:
> Hi,
>
> One additional comment to the draft.
> Not sure about whether it has been raised already though.
>
> The aggressive HBs sent on a potentially failed destination address shoul=
d not contribute
> to the association overall error counter. I.e., a failed HB should not in=
crement the associations error counter.
>
> At least that it how I firmly believe that things should be as the robust=
ness of the
> association error count should not be impacted by the more aggressive HB =
probing
> (Also simply following the approach of RFC4960 Path Verification. 5.4 of =
RFC4960)
>
> Would it be possible to have this explicitly clarified in the draft ?
>
> Thanks.
> BR, Karen
>
> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of=
 Yoshifumi Nishida
> Sent: 16. september 2011 10:22
> To: tsvwg
> Subject: Re: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt
>
> Hi folks,
>
> Based on the michael's review, we have updated the sctp failover draft.
> We believe we addressed the comments we got so far.
>
> Please let us know if we overlook something or if you have more comments.
>
> Thanks,
> --
> Yoshifumi Nishida
> nishida@sfc.wide.ad.jp
>
>
> 2011/9/16 =A0<internet-drafts@ietf.org>:
>> A New Internet-Draft is available from the on-line Internet-Drafts direc=
tories.
>>
>> =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : Quick Failover Algorithm in S=
CTP
>> =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : Yoshifumi Nishida
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Preethi Natarajan
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Armando Caro
>> =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-nishida-tsvwg-sctp-failov=
er-04.txt
>> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 16
>> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-09-16
>>
>> =A0 One of the major advantages in SCTP is supporting multi-homing
>> =A0 communication. =A0If a multi-homed end-point has redundant network
>> =A0 connections, SCTP sessions can have a good chance to survive from
>> =A0 network failures by migrating inactive network to active one.
>> =A0 However, if we follow the SCTP standard, there can be significant
>> =A0 delay for the network migration. =A0During this migration period, SC=
TP
>> =A0 cannot transmit much data to the destination. =A0This issue drastica=
lly
>> =A0 impairs the usability of SCTP in some situations. =A0This memo
>> =A0 describes the issue of SCTP failover mechanism and discuss its
>> =A0 solutions which require minimal modification to the current standard=
.
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-nishida-tsvwg-sctp-failover-04=
.txt
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-nishida-tsvwg-sctp-failover-04.=
txt
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>

From Karen.Nielsen@tieto.com  Thu Dec 15 03:51:22 2011
Return-Path: <Karen.Nielsen@tieto.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 EA9F421F85C7 for <tsvwg@ietfa.amsl.com>; Thu, 15 Dec 2011 03:51:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 DNUBfXvkA8a4 for <tsvwg@ietfa.amsl.com>; Thu, 15 Dec 2011 03:51:19 -0800 (PST)
Received: from ebb06.tieto.com (ebb06.tieto.com [131.207.168.38]) by ietfa.amsl.com (Postfix) with ESMTP id 7007D21F8494 for <tsvwg@ietf.org>; Thu, 15 Dec 2011 03:51:18 -0800 (PST)
X-AuditID: 83cfa826-b7b5bae000001ca6-5c-4ee9df34027a
Received: from FIVLA-EXHUB02.eu.tieto.com ( [131.207.136.42]) by ebb06.tieto.com (SMTP Mailer) with SMTP id 07.18.07334.43FD9EE4; Thu, 15 Dec 2011 13:51:16 +0200 (EET)
Received: from EXMB03.eu.tieto.com ([169.254.1.127]) by FIVLA-EXHUB02.eu.tieto.com ([131.207.136.42]) with mapi; Thu, 15 Dec 2011 13:51:16 +0200
From: <Karen.Nielsen@tieto.com>
To: <nishida@sfc.wide.ad.jp>
Date: Thu, 15 Dec 2011 13:51:15 +0200
Subject: RE: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt
Thread-Topic: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt
Thread-Index: Acy2UbmA3f8IdgIxS7qvawo++kGxBwAAJG/AATMlUlA=
Message-ID: <CF340E42AED0874C81947E18863DE77B133419C6C6@EXMB03.eu.tieto.com>
References: <20110916075854.4673.6360.idtracker@ietfa.amsl.com> <CABxaRLET3w_MhRtakjuA1Mc4sXd1-FpmorSgjK78K_6WjOX-Qg@mail.gmail.com> <CF340E42AED0874C81947E18863DE77B13340F715E@EXMB03.eu.tieto.com> <CABxaRLHFc5jin9tfjQxZV2SH-yMW80x0goe1QiOVSS7fynq_kA@mail.gmail.com> <CF340E42AED0874C81947E18863DE77B13340F741E@EXMB03.eu.tieto.com>
In-Reply-To: <CF340E42AED0874C81947E18863DE77B13340F741E@EXMB03.eu.tieto.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: 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: Thu, 15 Dec 2011 11:51:23 -0000

Hi Nishida,

One more follow up, second thoughts :-)

I still believe that the aggressive HBs of the potentially failed feature S=
HOULD NOT contribute
to the association error counter.

One reason is the discussed situation when no data is flowing.
But actually also in the case where data IS flowing may the aggressive HBs=
=20
have impact on the robustness of the association error counter. Indeed if d=
ata retransmissions
fail on other paths (while locating a new working data transmission path) d=
ue to
failure of other paths or simply due to random packet drops, the fact that =
we may have
aggressive step up of the association error counter due to the aggressive H=
B on the
potentially failed path does impact the robustness of the association error=
 counter.

I would encourage for the aggressive HBs to be prescribed not to impact the=
 association error counter.

I also (again) do believe that it is questionable in general why HBs sent=20
on anything but towards the primary destination address should contribute
to the association error counter. But that is a general issue relevant to t=
he=20
base spec, not to this spec.

Thanks.

BR, Karen

-----Original Message-----
From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of K=
aren.Nielsen@tieto.com
Sent: 9. december 2011 10:23
To: nishida@sfc.wide.ad.jp
Cc: tsvwg@ietf.org
Subject: RE: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt

Hi,

Please accept the follow up below.


Hi Karen, thanks for the comment.

I think PF is not aggressive on the point you mentioned. Please point
out if I miss something.
In RFC4960, retransmitted data packets are sent to the failed
destination address and it will contribute to the
Association.Max.Retrans.

[Karen] In RFC4960 retransmitted packets will be send to most divergent pat=
h. Not to the PF path. But I suppose that you mean that as new data continu=
es to be send on "PF" path in RFC4960, then the association error count wil=
l be hurt by the failure of these like it may be hurt
by the failure of the aggressive HBs.

In PF, HBs are sent to the failed destination address instead of data
packets. The interval of HBs for the destination is RTO, which will be
the same as those of the retransmitted packets.
So, I believe both approach will have similar results on the
robustness of the association error count.

[Karen] I agree for the case where there continuously is data flowing.
But when there is not such data, then the aggressive HBs will impact the ro=
bustness of
the association error count as there is no successful data that will reset =
it, as the successful retransmissions of data would.

Generally, I have never understood why the faith of HBs should EVER contrib=
ute to the
association error counter, EXCEPT when in idle state. And in this case, the=
n in my opinion,
it would suffice if it was the HBs on the primary path which were allowed t=
o contribute to the association error counter. Indeed the association error=
 counter is not there to ascertain whether all paths are available, only it=
 should be there to ascertain whether some path of the association is avail=
able. In that respect HBs on non working (auxiliary) paths impacts the robu=
stness of the association error counter.

BR, Karen


Thanks,
--
Yoshifumi Nishida
nishida@sfc.wide.ad.jp


2011/12/8  <Karen.Nielsen@tieto.com>:
> Hi,
>
> One additional comment to the draft.
> Not sure about whether it has been raised already though.
>
> The aggressive HBs sent on a potentially failed destination address shoul=
d not contribute
> to the association overall error counter. I.e., a failed HB should not in=
crement the associations error counter.
>
> At least that it how I firmly believe that things should be as the robust=
ness of the
> association error count should not be impacted by the more aggressive HB =
probing
> (Also simply following the approach of RFC4960 Path Verification. 5.4 of =
RFC4960)
>
> Would it be possible to have this explicitly clarified in the draft ?
>
> Thanks.
> BR, Karen
>
> -----Original Message-----
> From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On Behalf Of=
 Yoshifumi Nishida
> Sent: 16. september 2011 10:22
> To: tsvwg
> Subject: Re: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt
>
> Hi folks,
>
> Based on the michael's review, we have updated the sctp failover draft.
> We believe we addressed the comments we got so far.
>
> Please let us know if we overlook something or if you have more comments.
>
> Thanks,
> --
> Yoshifumi Nishida
> nishida@sfc.wide.ad.jp
>
>
> 2011/9/16 =A0<internet-drafts@ietf.org>:
>> A New Internet-Draft is available from the on-line Internet-Drafts direc=
tories.
>>
>> =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : Quick Failover Algorithm in S=
CTP
>> =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : Yoshifumi Nishida
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Preethi Natarajan
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Armando Caro
>> =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-nishida-tsvwg-sctp-failov=
er-04.txt
>> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 16
>> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-09-16
>>
>> =A0 One of the major advantages in SCTP is supporting multi-homing
>> =A0 communication. =A0If a multi-homed end-point has redundant network
>> =A0 connections, SCTP sessions can have a good chance to survive from
>> =A0 network failures by migrating inactive network to active one.
>> =A0 However, if we follow the SCTP standard, there can be significant
>> =A0 delay for the network migration. =A0During this migration period, SC=
TP
>> =A0 cannot transmit much data to the destination. =A0This issue drastica=
lly
>> =A0 impairs the usability of SCTP in some situations. =A0This memo
>> =A0 describes the issue of SCTP failover mechanism and discuss its
>> =A0 solutions which require minimal modification to the current standard=
.
>>
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-nishida-tsvwg-sctp-failover-04=
.txt
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> This Internet-Draft can be retrieved at:
>> ftp://ftp.ietf.org/internet-drafts/draft-nishida-tsvwg-sctp-failover-04.=
txt
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>

From yoshifumi.nishida@gmail.com  Tue Dec 20 01:29:56 2011
Return-Path: <yoshifumi.nishida@gmail.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 B700021F8B16 for <tsvwg@ietfa.amsl.com>; Tue, 20 Dec 2011 01:29:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.47
X-Spam-Level: 
X-Spam-Status: No, score=-101.47 tagged_above=-999 required=5 tests=[AWL=0.907, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_28=0.6, RCVD_IN_DNSWL_LOW=-1, 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 8rp7dp6xBIn4 for <tsvwg@ietfa.amsl.com>; Tue, 20 Dec 2011 01:29:56 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 44A3221F8484 for <tsvwg@ietf.org>; Tue, 20 Dec 2011 01:29:56 -0800 (PST)
Received: by iaen33 with SMTP id n33so1682570iae.31 for <tsvwg@ietf.org>; Tue, 20 Dec 2011 01:29:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=OO/nS0y8eIc9sbH6gqySfh1ih2+53Kf7/+7XJhRDYNI=; b=YbEpYtuMP4TqFs2pHsGqMMYarZhN6xcVgvvVN/qt5EGYc+2JVKH+YVzKG3dkAm8zLy 3QemuboIxV1ZXSBX1M9CzTAosDRkOUxNJ+DBEVwpmtoAFZGI3eHuhPdwbxEUchi+iOHZ AUCRTZkIvantAbzZLyQutLkq34Wb/ulr/DjyY=
MIME-Version: 1.0
Received: by 10.43.58.10 with SMTP id wi10mr1337272icb.57.1324373395952; Tue, 20 Dec 2011 01:29:55 -0800 (PST)
Sender: yoshifumi.nishida@gmail.com
Received: by 10.42.224.10 with HTTP; Tue, 20 Dec 2011 01:29:55 -0800 (PST)
In-Reply-To: <CF340E42AED0874C81947E18863DE77B133419C6C6@EXMB03.eu.tieto.com>
References: <20110916075854.4673.6360.idtracker@ietfa.amsl.com> <CABxaRLET3w_MhRtakjuA1Mc4sXd1-FpmorSgjK78K_6WjOX-Qg@mail.gmail.com> <CF340E42AED0874C81947E18863DE77B13340F715E@EXMB03.eu.tieto.com> <CABxaRLHFc5jin9tfjQxZV2SH-yMW80x0goe1QiOVSS7fynq_kA@mail.gmail.com> <CF340E42AED0874C81947E18863DE77B13340F741E@EXMB03.eu.tieto.com> <CF340E42AED0874C81947E18863DE77B133419C6C6@EXMB03.eu.tieto.com>
Date: Tue, 20 Dec 2011 01:29:55 -0800
X-Google-Sender-Auth: 0bbGW-aeNG95iThidNvBAO822OU
Message-ID: <CABxaRLFy+B5y_jOpjf-4Jhsd7iHBApoJnbZ58-+EPOTnv9=E3g@mail.gmail.com>
Subject: Re: I-D Action: draft-nishida-tsvwg-sctp-failover-04.txt
From: Yoshifumi Nishida <nishida@sfc.wide.ad.jp>
To: Karen.Nielsen@tieto.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: 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: Tue, 20 Dec 2011 09:29:56 -0000

Hi Karen,

2011/12/15  <Karen.Nielsen@tieto.com>:
> Hi Nishida,
>
> One more follow up, second thoughts :-)
>
> I still believe that the aggressive HBs of the potentially failed feature SHOULD NOT contribute
> to the association error counter.
>
> One reason is the discussed situation when no data is flowing.
> But actually also in the case where data IS flowing may the aggressive HBs
> have impact on the robustness of the association error counter. Indeed if data retransmissions
> fail on other paths (while locating a new working data transmission path) due to
> failure of other paths or simply due to random packet drops, the fact that we may have
> aggressive step up of the association error counter due to the aggressive HB on the
> potentially failed path does impact the robustness of the association error counter.
>
> I would encourage for the aggressive HBs to be prescribed not to impact the association error counter.

Is it possible for you to give me some sample scenarios?
I would like to think how bad this is more precisely.

> I also (again) do believe that it is questionable in general why HBs sent
> on anything but towards the primary destination address should contribute
> to the association error counter. But that is a general issue relevant to the
> base spec, not to this spec.

I agree that this needs to go rfc4960, while I'm still not very sure
how this is effective.
In some cases, you might want to terminate association smoothly if
there's no available connections in order to save resources.
In case where you want to keep associations robust, I think you can do
it by increasing asoc.max.retr or increasing HB.interval or disabling
HB.

Thanks,
--
Yoshifumi Nishida
nishida@sfc.wide.ad.jp

From Michael.Larsen@tieto.com  Wed Dec 21 04:55:44 2011
Return-Path: <Michael.Larsen@tieto.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 52E2221F8ABD for <tsvwg@ietfa.amsl.com>; Wed, 21 Dec 2011 04:55:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 uo29SxgPJXoB for <tsvwg@ietfa.amsl.com>; Wed, 21 Dec 2011 04:55:43 -0800 (PST)
Received: from ebb05.tieto.com (ebb05.tieto.com [131.207.168.36]) by ietfa.amsl.com (Postfix) with ESMTP id C989221F8ABC for <tsvwg@ietf.org>; Wed, 21 Dec 2011 04:55:42 -0800 (PST)
X-AuditID: 83cfa824-b7cebae0000004d2-f0-4ef1d74c3cda
Received: from FIVLA-EXHUB02.eu.tieto.com ( [131.207.136.42]) by ebb05.tieto.com (SMTP Mailer) with SMTP id 55.72.01234.C47D1FE4; Wed, 21 Dec 2011 14:55:40 +0200 (EET)
Received: from ul000513.localnet (10.48.99.29) by inbound.tieto.com (131.207.136.49) with Microsoft SMTP Server id 8.3.159.2; Wed, 21 Dec 2011 14:55:40 +0200
From: Michael Vittrup Larsen <michael.larsen@tieto.com>
Organization: Tieto
To: <tsvwg@ietf.org>
Subject: Re: Fast Retransmission in SCTP
Date: Wed, 21 Dec 2011 13:55:38 +0100
User-Agent: KMail/1.13.5 (Linux/2.6.32-34-generic; KDE/4.4.5; i686; ; )
References: <CA+-pjPzogR5VLVOqX0H1jfw-CgB_CDLH1Zc=MAq0qCVoYETq-g@mail.gmail.com> <B21E99E1-05EC-42DA-A3DF-E91FB207453A@lurchi.franken.de>
In-Reply-To: <B21E99E1-05EC-42DA-A3DF-E91FB207453A@lurchi.franken.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-ID: <201112211355.39643.michael.larsen@tieto.com>
X-Brightmail-Tracker: AAAAAgW74bYZnsdP
Cc: Michael =?iso-8859-1?q?T=FCxen?= <Michael.Tuexen@lurchi.franken.de>
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, 21 Dec 2011 12:55:44 -0000

I don't believe this is a correct interpretation of the articles from Arman=
do=20
et. al ([4] of RFC4460).  I believe the correct interpretation is

  "fast retransmissions should be sent to the destination to which
   we currently are sending data"

Note that this is not the same as "...to the same destination where initial=
=20
transmissions were sent" in case of current primary path failovers.  In fac=
t,=20
if we send fast retransmissions "...to the same destination where initial=20
transmissions were sent" we may in fact be sending these on a path differen=
t=20
from where we currently are sending data - and this is exactly (to my=20
understanding) what the change in SCTP fast retransmission in RFC4960 is al=
l=20
about.

To see why we need to look behind the words used by RFC4960 and into the=20
articles and the reasoning in the articles:

1) Sending fast retransmissions (FR) on a path different from where we=20
currently are sending new data may be subject to excessive RTO values on th=
e=20
alternative path. Successful FRs do not update the RTT of the alternative p=
ath=20
due to Karns algorithm and the RTO on the alternative path is therefore=20
conservative for the majority of the association and sending FRs on such a=
=20
path is not optimal.

2) FRs do not benefit the cwnd of the path where we are sending new data bu=
t=20
instead the cwnd of the alternative path, which is less attractive.

3) Possible timeouts of FRs sent on the alternative path will delay cwnd=20
increments on the path where we are sending new data. Since these timeouts =
are=20
conservative the delay may be excessive.

Neither [4] nor RFC4960 explicitly in text describes the FR policy in case=
=20
where a change of the current primary data transfer path has occurred. But =
in=20
essence the above reasoning/discovery of [4] clearly dictates what the corr=
ect=20
interpretation should be.


Regards,
Michael

On Friday, December 09, 2011 11:34:34 Michael T=FCxen wrote:
> On Dec 9, 2011, at 8:27 AM, Maxim Proshin wrote:
> > Hi experts,
> >=20
> > here I would like to discuss the Fast Retransmission algorithm in RFC
> > 4960. Frankly this RFC does not describe clearly how to send (to which
> > destination) fast retransmissions but we can find some information in
> > RFC 4460 which says:
> >=20
> > "
> > 2.39. Retransmission Policy
> >=20
> > 2.39.1. Description of the Problem
> >=20
> > The current retransmission policy (send all retransmissions an
> > alternate destination) in the specification has performance issues
> > under certain loss conditions with multihomed endpoints. Instead,
> > fast retransmissions should be sent to the same destination, and only
> > timeout retransmissions should be sent to an alternate destination [4].
> > "
> >=20
> > Reading this article my first feeling was that fast retransmissions
> > should be sent to the same destination where initial transmissions were
> > sent.
> >=20
> > So my first question is
> >=20
> >  is my RFC interpretation correct or not?
>=20
> Yes. Fast retransmissions should be send to the same destination as the
> initial transmission. Timer based retransmissions should use an alternate
> destination.
>=20
> > Meanwhile, there are some more articles about retransmision policies
> > where RFC's authors also participated. For instance, "Retransmission
> > Policies With Transport Layer Multihoming" describes some improvements
> > in fast retransmission policy in respect to RFC 2960 and I think that
> > they were considered during RFC 4960 preparation. This analysis also
> > proposes to send fast retransmissions to the same destination: "
> > In this solution, all retransmissions are sent to the
> > same destination as their original transmissions.
> > ...
> > Instead of all
> > retransmissions following the Retransmit to Same Destination
> > policy of Solution 1, only Fast Retransmissions
> > should follow this policy.
> > "
> >=20
> > It seems that this statement confirms my initial feeling described abov=
e.
> > But at the same time it says about primary path: "
> > Using the same destination for retransmissions has
> > the added advantage that the primary destination's cwnd
> > bene=02ts from successful retransmissions.
> > "
> > and it results is some doubts. On the one hand fast retransmissions
> > should be sent to the same destination, on the other it should be sent
> > to the primary destination. In usual case "the same" and primary
> > destinations are equal. But RFC 4960 doesn't prevent primary destination
> > changing by the user so it can be changed in run-time.
> >=20
> > So my second question is
> >=20
> >  if the primary destination is changed in run-time, where SCTP should
> >  sent fast retransmissions which were detected for the previous primary
> >  destination?
>=20
> Changing the primary is normally not done at a high rate. So you are
> looking at the case where fast retransmission occur and the user changed
> the primary in between.
>=20
> I guess there is no special case on the RFC for that. So the fast
> retransmission would go to the destination to which it was initially sent.
> The same applies if the user specified a destination and therefore the
> primary was not used.
>=20
> > The mentioned above article describes one advantage in respect to sendi=
ng
> > to the primay destination, this is about cwnd benets from successful
> > retransmission. But I think that in case of fast retransmission it will
> > not be observed or the advantage is very very low.
> >=20
> > At the same time sending to the primary destination results in a big
> > disadvantage: SCTP should recalculate cwnd if it sends fast
> > retransmissions to the primary destination because RFC 4960 says: "
> > When a Fast Retransmit is being performed, the sender SHOULD ignore the
> > value of cwnd "
> > I think the reason is that it was considered during initial transmissio=
n.
>=20
> If you do a fast retransmit, you assume that the packet has left the
> network. So you would have to subtract and add it. This means ignoring...
>=20
> Best regards
> Michael
>=20
> > What do you think about this?
> >=20
> > I'm not sure whether it was discussed already or not. If yes, please
> > provide me with discussion's results.

=2D-=20
***************************************************************************=
**************
Michael Vittrup Larsen
Software Architect
=20
Tieto Denmark A/S
IP Solutions, Telecom & Media
Skanderborgvej 232, 8260 Viby J, DK-Denmark
Direct Phone / Mobile +45 3091 8469
E-mail: michael.larsen@tieto.com
***************************************************************************=
**************
www.tieto.com =20
=20
Please note: The information contained in this message may be legally=20
privileged and confidential and protected from disclosure. If the reader of=
=20
this message is not the intended recipient, you are hereby notified that an=
y=20
unauthorised use, distribution or copying of this communication is strictly=
=20
prohibited. If you have received this communication in error, please notify=
 us=20
immediately by replying to the message and deleting it from your computer.=
=20
Thank You.

From internet-drafts@ietf.org  Thu Dec 22 10:15:29 2011
Return-Path: <internet-drafts@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 6D53221F8B01; Thu, 22 Dec 2011 10:15:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 Fs5ygn+Aqcts; Thu, 22 Dec 2011 10:15:29 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B40621F8ACE; Thu, 22 Dec 2011 10:15:29 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-tsvwg-source-quench-03.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111222181529.7614.69349.idtracker@ietfa.amsl.com>
Date: Thu, 22 Dec 2011 10:15:29 -0800
Cc: 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: Thu, 22 Dec 2011 18:15:29 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Transport Area Working Group Working =
Group of the IETF.

	Title           : Deprecation of ICMP Source Quench messages
	Author(s)       : Fernando Gont
	Filename        : draft-ietf-tsvwg-source-quench-03.txt
	Pages           : 9
	Date            : 2011-12-22

   This document formally deprecates the use of ICMP Source Quench
   messages by transport protocols, formally updating RFC 792, RFC 1122,
   and RFC 1812.  Additionally, it requests that the status of RFC 1016
   be changed to "Historic".


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-source-quench-03.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-tsvwg-source-quench-03.txt


From gorry@erg.abdn.ac.uk  Thu Dec 22 11:30:15 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 A97B221F8801 for <tsvwg@ietfa.amsl.com>; Thu, 22 Dec 2011 11:30:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 2fWuli8aMg95 for <tsvwg@ietfa.amsl.com>; Thu, 22 Dec 2011 11:30:15 -0800 (PST)
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 06C0021F8488 for <tsvwg@ietf.org>; Thu, 22 Dec 2011 11:30:14 -0800 (PST)
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 pBMJU6qq008430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <tsvwg@ietf.org>; Thu, 22 Dec 2011 19:30:11 GMT
Message-ID: <4EF3853E.7040700@erg.abdn.ac.uk>
Date: Thu, 22 Dec 2011 19:30:06 +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:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: tsvwg@ietf.org
Subject: : draft-ietf-tsvwg-source-quench-03.txt - update following WGLC
References: <4EF3753F.9000801@gont.com.ar>
In-Reply-To: <4EF3753F.9000801@gont.com.ar>
Content-Type: text/plain; charset=UTF-8; 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: Thu, 22 Dec 2011 19:30:15 -0000

Fernando has just posted a revision of the SQ I-D.

This contains new text following the issues raised in the WGLC.
The chairs plan to proceed with publication of the document. If you made 
comments during the WGLC, then please do check the new rev.

Best wishes for Christmas 2011!

Gorry & James

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-source-quench-03.txt
