Jeff Morriss | 24 Feb 23:39 2015
Picon

SCTP: association restart in the SHUTDOWN_PENDING or SHUTDOWN_SENT state

Hi folks,

RFC 4960's section 5.2.4 talks about association restart (action (A)). 
My reading is that restart can happen in any state other than CLOSED.

But if the association is in the SHUTDOWN_PENDING or SHUTDOWN_SENT state 
then I'm not sure it makes sense to allow the association to restart: 
from the API perspective the application has called shutdown() and/or 
close() (possibly with SO_LINGER set) so it's unlikely to be able to 
handle a restarted association.

I saw a patch to one SCTP implementation on the web because it needed to 
add logic to shut down the association when this happens (actually the 
patch I saw only handled the SHUTDOWN_PENDING state).  Should the RFC 
explicitly cover this scenario?

Regards,
-Jeff

Eggert, Lars | 22 Feb 11:47 2015
Picon

Re: I-D Action: draft-sprecher-mobile-tg-exposure-req-arch-01.txt

Hi Nurit,

On 2015-2-21, at 18:22, Sprecher, Nurit (NSN - IL/Hod HaSharon) <nurit.sprecher <at> nokia.com> wrote:
> Please note that the document does not specify a solution protocol, but it proposes solution principles,
requirements and a reference architecture. It also present an applicability statement.
> We will submit soon an I-D with a proposed solution protocol, which is based on running code. We will share
some preliminary test results.

I'll look forward to the solution proposal. I have some general doubts about the feasibility of approaches
in this space, and so commenting on the requirements and architecture feels a bit premature. I expect the
solution proposal will add enough context to understand what is attempted.

Thanks,
Lars

Black, David | 22 Feb 02:34 2015

draft-sprecher-mobile-tg-exposure-req-arch-01.txt - discussion forum

> Also, where is this document primarily being discussed (TSVWG?) as I am interested in the work but not sure

> which WG to subscribe to in order to follow/contribute towards it?

 

The original announcement was sent to tsvwg, and it looks like Lars added tcpm and iccrg in his reply.

Let’s use tsvwg as the primary discussion forum for now.

 

Thanks,
--David (tsvwg WG co-chair)

 

From: tsvwg [mailto:tsvwg-bounces <at> ietf.org] On Behalf Of Ben Niven-Jenkins
Sent: Saturday, February 21, 2015 4:40 PM
To: Andreas Terzis
Cc: tcpm <at> ietf.org; tsvwg <at> ietf.org; iccrg <at> irtf.org; Helen Parsons; Arunachalam, Swaminathan (NSN - US/Irving); Ankur Jain; Cosimini, Peter, Vodafone Group; Flinck, Hannu (NSN - FI/Espoo); ext Smith, Kevin, (R&D) Vodafone Group; Klas, Guenter, Vodafone Group
Subject: Re: [tsvwg] [tcpm] I-D Action: draft-sprecher-mobile-tg-exposure-req-arch-01.txt

 

Andreas,

 

From a quick read of the draft it seems to me that the functional architecture is only partially described as it is not clear to me how the Throughput Guidance Provider discovers which TCP server(s) it should be providing throughput guidance to or how a TCP server might discover & register with a Throughput Guidance Provider. 

 

Will the other document you mention also cover discovery?

Also, where is this document primarily being discussed (TSVWG?) as I am interested in the work but not sure which WG to subscribe to in order to follow/contribute towards it?

 

Thanks

Ben


On 21 Feb 2015, at 08:21, Andreas Terzis <aterzis <at> google.com> wrote:

Lars,

 

To be clear, the document that Nurit submitted talks about requirements and doesn't propose any mechanism.

 

We will soon submit another document that describe one possible mechanism for providing throughput guidance

and a strawman for leveraging this information. That draft will include preliminary results from lab tests. 

 

Best regards,

 

Andreas 

 

 

 

On Fri, Feb 20, 2015 at 8:42 PM, Eggert, Lars <lars <at> netapp.com> wrote:

Also CC'ing TCPM and ICCRG. Is there any experimental evaluation and/or simulation results for the proposed mechanism?

 

Lars

 

On 2015-2-20, at 14:46, Sprecher, Nurit (NSN - IL/Hod HaSharon) <nurit.sprecher <at> nsn.com> wrote:

 

Dear all,

Please be aware of the new I-D we have submitted on “Requirements and reference architecture for Mobile Throughput Guidance Exposure”.

The draft proposes principles for a mobile throughput guidance exposure mechanism that can be used  to assist TCP in cellular networks, and help to ensure better network  efficiency and enhanced service delivery performance.  

The draft presents the problems that the rapidly-varying conditions in a cellular network can cause to the TCP behavior and to the application performance.

The draft specifies the requirements and reference architecture for the mechanism. 

While the proposed mechanism can be used to optimize any content delivery application, the draft describes its applicability to video delivery optimization in mobile networks.

Your review and comments will be much appreciated. Comments can be sent on the tsvwg list or directly to the authors.

Best regards,

Nurit

 

 

-----Original Message-----
From: I-D-Announce [mailto:i-d-announce-bounces <at> ietf.org] On Behalf Of ext internet-drafts <at> ietf.org
Sent: Friday, February 20, 2015 3:04 PM
To: i-d-announce <at> ietf.org
Subject: I-D Action: draft-sprecher-mobile-tg-exposure-req-arch-01.txt

 

 

A New Internet-Draft is available from the on-line Internet-Drafts directories.

 

 

        Title           : Requirements and reference architecture for Mobile Throughput Guidance Exposure

        Authors         : Ankur Jain

                          Andreas Terzis

                          Nurit Sprecher

                          Swaminathan Arunachalam

                          Kevin Smith

                          Guenter Klas

      Filename        : draft-sprecher-mobile-tg-exposure-req-arch-01.txt

      Pages           : 12

      Date            : 2015-02-20

 

Abstract:

   Rapidly-varying conditions in a cellular network can cause problems

   for the Transmission Control Protocol (TCP), which in turn can

   degrade application performance.

 

   This document presents the problem statement and proposes solution

   principles.  It specifies the requirements and reference architecture

   for a mobile throughput guidance exposure mechanism that can be used

  to assist TCP in cellular networks, ensuring better network

   efficiency and enhanced service delivery performance.

 

   The proposed mechanism can be applied to any content or TCP/IP based

   application content delivery.  This document describes the

   applicability of the mechanism for Intelligent Video Acceleration

   over cellular networks.

 

 

The IETF datatracker status page for this draft is:

 

There's also a htmlized version available at:

 

A diff from the previous version is available at:

 

 

Please note that it may take a couple of minutes from the time of submission

until the htmlized version and diff are available at tools.ietf.org.

 

Internet-Drafts are also available by anonymous FTP at:

 

_______________________________________________

I-D-Announce mailing list

Internet-Draft directories: http://www.ietf.org/shadow.html

 

 

_______________________________________________
tcpm mailing list
tcpm <at> ietf.org
https://www.ietf.org/mailman/listinfo/tcpm

FW: I-D Action: draft-sprecher-mobile-tg-exposure-req-arch-01.txt

Dear all,

Please be aware of the new I-D we have submitted on “Requirements and reference architecture for Mobile Throughput Guidance Exposure”.

The draft proposes principles for a mobile throughput guidance exposure mechanism that can be used  to assist TCP in cellular networks, and help to ensure better network  efficiency and enhanced service delivery performance.  

The draft presents the problems that the rapidly-varying conditions in a cellular network can cause to the TCP behavior and to the application performance.

The draft specifies the requirements and reference architecture for the mechanism.

While the proposed mechanism can be used to optimize any content delivery application, the draft describes its applicability to video delivery optimization in mobile networks.

Your review and comments will be much appreciated. Comments can be sent on the tsvwg list or directly to the authors.

Best regards,

Nurit

 

 

-----Original Message-----
From: I-D-Announce [mailto:i-d-announce-bounces <at> ietf.org] On Behalf Of ext internet-drafts <at> ietf.org
Sent: Friday, February 20, 2015 3:04 PM
To: i-d-announce <at> ietf.org
Subject: I-D Action: draft-sprecher-mobile-tg-exposure-req-arch-01.txt

 

 

A New Internet-Draft is available from the on-line Internet-Drafts directories.

 

 

        Title           : Requirements and reference architecture for Mobile Throughput Guidance Exposure

        Authors         : Ankur Jain

                          Andreas Terzis

                          Nurit Sprecher

                          Swaminathan Arunachalam

                          Kevin Smith

                          Guenter Klas

      Filename        : draft-sprecher-mobile-tg-exposure-req-arch-01.txt

      Pages           : 12

      Date            : 2015-02-20

 

Abstract:

   Rapidly-varying conditions in a cellular network can cause problems

   for the Transmission Control Protocol (TCP), which in turn can

   degrade application performance.

 

   This document presents the problem statement and proposes solution

   principles.  It specifies the requirements and reference architecture

   for a mobile throughput guidance exposure mechanism that can be used

  to assist TCP in cellular networks, ensuring better network

   efficiency and enhanced service delivery performance.

 

   The proposed mechanism can be applied to any content or TCP/IP based

   application content delivery.  This document describes the

   applicability of the mechanism for Intelligent Video Acceleration

   over cellular networks.

 

 

The IETF datatracker status page for this draft is:

https://datatracker.ietf.org/doc/draft-sprecher-mobile-tg-exposure-req-arch/

 

There's also a htmlized version available at:

http://tools.ietf.org/html/draft-sprecher-mobile-tg-exposure-req-arch-01

 

A diff from the previous version is available at:

http://www.ietf.org/rfcdiff?url2=draft-sprecher-mobile-tg-exposure-req-arch-01

 

 

Please note that it may take a couple of minutes from the time of submission

until the htmlized version and diff are available at tools.ietf.org.

 

Internet-Drafts are also available by anonymous FTP at:

ftp://ftp.ietf.org/internet-drafts/

 

_______________________________________________

I-D-Announce mailing list

I-D-Announce <at> 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

internet-drafts | 19 Feb 22:21 2015
Picon

I-D Action: draft-ietf-tsvwg-rfc5405bis-01.txt


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

        Title           : UDP Usage Guidelines
        Authors         : Lars Eggert
                          Godred Fairhurst
                          Greg Shepherd
	Filename        : draft-ietf-tsvwg-rfc5405bis-01.txt
	Pages           : 41
	Date            : 2015-02-19

Abstract:
   The User Datagram Protocol (UDP) provides a minimal message-passing
   transport that has no inherent congestion control mechanisms.
   Because congestion control is critical to the stable operation of the
   Internet, applications and other protocols that choose to use UDP as
   an Internet transport must employ mechanisms to prevent congestion
   collapse and to establish some degree of fairness with concurrent
   traffic.  They may also need to implement additional mechanisms,
   depending on how they use UDP.

   This document provides guidelines on the use of UDP for the designers
   of applications, tunnels and other protocols that use UDP.
   Congestion control guidelines are a primary focus, but the document
   also provides guidance on other topics, including message sizes,
   reliability, checksums, and middlebox traversal.

   If published as an RFC, this document will obsolete RFC5405.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc5405bis/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-rfc5405bis-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-rfc5405bis-01

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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

internet-drafts | 18 Feb 13:35 2015
Picon

I-D Action: draft-ietf-tsvwg-behave-requirements-update-01.txt


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

        Title           : Network Address Translation (NAT) Behavioral Requirements Updates
        Authors         : Reinaldo Penno
                          Simon Perreault
                          Sarat Kamiset
                          Mohamed Boucadair
                          Kengo Naito
	Filename        : draft-ietf-tsvwg-behave-requirements-update-01.txt
	Pages           : 14
	Date            : 2015-02-18

Abstract:
   This document clarifies and updates several requirements of RFC4787,
   RFC5382 and RFC5508 based on operational and development experience.
   The focus of this document is NAPT44.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-behave-requirements-update/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-tsvwg-behave-requirements-update-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-behave-requirements-update-01

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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

Lucy yong | 12 Feb 16:47 2015

FW: New Version Notification for draft-ietf-tsvwg-gre-in-udp-encap-04.txt

Hello Chairs and All,

Tom (new co-author) and I have worked out another revision and would like to get people's feedbacks on it.
This version has quite changes in technical and editorial. Here are the key changes.

1)	Adapt the text of UDP checksum with IPv6 from the MPLS/UDP draft to fit in GRE/UDP. (Section 4.2)
2)	Adapt the text of Congestion Considerations from the MPLS/UDP draft (Section 6)
3)	Change the title to GRE-in-UDP encapsulation (was: Generic UDP encapsulation in IP Tunneling)
4)	Reorder the sections.
5)	Modify the text in applicability statement (Section 1.1)
6)	Modify the text for UDP checksum with IPv4 (Section 4.1)
7)	Modify the text for UDP source port (now same as the MPLS/UDP draft)
8)	Add Tom Herbert as co-author and Gorry Fairhurst as a contributor
9)	Various editing changes  

FYI: the MPLS/UDP draft is the draft-ietf-mpls-in-udp-11 that is in RFC editing queue now. Two drafts need
to address the same issues as of a UDP application, the design term decided to work out mpls/udp first, and gre/udp.

Look forward to seeing your input here. 

Thanks,
Lucy

-----Original Message-----
From: internet-drafts <at> ietf.org [mailto:internet-drafts <at> ietf.org] 
Sent: Wednesday, February 11, 2015 6:00 PM
To: Edward Crabbe; Tom Herbert; Lucy yong; Xuxiaohu; Xuxiaohu; Lucy yong; Edward Crabbe; Tom Herbert
Subject: New Version Notification for draft-ietf-tsvwg-gre-in-udp-encap-04.txt


A new version of I-D, draft-ietf-tsvwg-gre-in-udp-encap-04.txt
has been successfully submitted by Lucy Yong and posted to the IETF repository.

Name:		draft-ietf-tsvwg-gre-in-udp-encap
Revision:	04
Title:		GRE-in-UDP Encapsulation
Document date:	2015-02-11
Group:		tsvwg
Pages:		21
URL:            http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-gre-in-udp-encap-04.txt

Status:         https://datatracker.ietf.org/doc/draft-ietf-tsvwg-gre-in-udp-encap/

Htmlized:       http://tools.ietf.org/html/draft-ietf-tsvwg-gre-in-udp-encap-04

Diff:           http://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-gre-in-udp-encap-04


Abstract:
   This document describes a method of encapsulating network protocol
   packets within GRE and UDP headers.  In this encapsulation, the
   source UDP port can be used as an entropy field for purposes of load
   balancing, while the protocol of the encapsulated packet in the GRE
   payload is identified by the GRE Protocol Type. Usage restrictions
   apply to GRE-in-UDP usage for traffic that is not congestion
   controlled and to UDP zero checksum usage with IPv6.

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and
diff are available at tools.ietf.org.

The IETF Secretariat

IETF Secretariat | 12 Feb 15:10 2015
Picon

ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-prpolicies-07.txt>

IESG state changed to RFC Ed Queue from Approved-announcement sent
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/

IETF Secretariat | 11 Feb 20:06 2015
Picon

ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-prpolicies-07.txt>

IANA action state changed to No IC
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/

IETF Secretariat | 11 Feb 20:06 2015
Picon

ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-prpolicies-07.txt>

IANA action state changed to In Progress
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/

IETF Secretariat | 11 Feb 18:50 2015
Picon

ID Tracker State Update Notice: <draft-ietf-tsvwg-sctp-prpolicies-07.txt>

IESG has approved the document and state has been changed to Approved-announcement sent
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-tsvwg-sctp-prpolicies/


Gmane